Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Cluster Server Agent Developer's Guide - AIX, Linux, Solaris, Windows
Last Published:
2025-04-13
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: 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
Agent messages: format
An agent log message consists of five fields. The format of the message is:
<Timestamp> <Mnemonic> <Severity> <UMI> <MessageText>
The following is an example message, of severity ERROR, generated by the FileOnOff agent's online entry point. The message is generated when the agent attempts to bring online a resource, a file named "MyFile":
Sep 26 2010 11:32:56 VCS ERROR V-16-2001-14001 FileOnOff:MyFile:online:Resource could not be brought up because,the attempt to create the file (filename) failed with error (Is a Directory)
The first four fields of the message above consists of the timestamp, an uppercase mnemonic that represents the component, the severity, and the UMI (unique message ID). The subsequent lines contain the message text.