InfoScale™ 9.0 Cluster Server Agent Developer's Guide - AIX, Linux, Solaris, Windows
- Introduction
- Agent entry point overview
- About agent entry points
- Agent entry points described
- About the action entry point
- About the info entry point
- Considerations for using C++ or script entry points
- About the agent information file
- About the ArgList and ArgListValues attributes
- Creating entry points in C++
- About creating entry points in C++
- Syntax for C++ entry points
- Agent framework primitives
- Agent Framework primitives for container support
- Creating entry points in scripts
- About creating entry points in scripts
- Syntax for script entry points
- Agent framework primitives
- VCSAG_GET_ATTR_VALUE
- Agent Framework primitives with container support
- Example script entry points
- Logging agent messages
- Building a custom agent
- Building a script based IMF-aware custom agent
- Creating XML file required for AMF plugins to do resource registration for online and offline state monitoring
- Testing agents
- Static type attributes
- About static attributes
- Static type attribute definitions
- AdvDbg
- ArgList
- State transition diagram
- Internationalized messages
- Troubleshooting VCS resource's unexpected behavior using First Failure Data Capture (FFDC)
- Appendix A. Using pre-5.0 VCS agents
UMI
The UMI (unique message identifier) includes an originator ID, a category ID, and a message ID.
The originator ID is a decimal number preceded by a "V-" that defines the component that the message comes from. This ID is assigned by Arctera.
The category ID is a number in the range of 0 to 65536 assigned by Arctera. The category ID indicates the agent that message came from. For each custom agent, you must contact Arctera so that a unique category ID can be registered for the agent.
For C++ messages, the category ID is defined in the VCSAgStartup function.
See Log category.
For script-based entry points, the category is set within the VCSAG_SET_ENVS function
See VCSAG_SET_ENVS.
For debug messages, the category ID, which is 50 by default, need not be defined within logging functions.
Message IDs can range from 0 to 65536 for a category ID. Each normal message (that is, non-debug message) generated by an agent must be assigned a message ID. For C++ entry points, the msgid is set as part of the VCSAG_LOG_MSG and VCSAG_CONSOLE_LOG_MSG macros. For script-based entry points, the msgid is set using the VCSAG_LOG_MSG function. The msgid field is not used by debug functions or required in debug messages.
See VCSAG_LOG_MSG.