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
Return values for info entry point
If the info entry point exits with 0 (success), the output captured on stdout for the script entry point, or the contents of the info_output argument for C++ entry point, is dumped to the Msg key of the ResourceInfo attribute. The Msg key is updated only when the info entry point is successful. The State key is set to the value: Valid.
If the entry point exits with a non-zero value, ResourceInfo is updated to indicate the error; the script's stdout or the C++ entry point's info_output is ignored. The State key is set to the value: Invalid. The error message is written to the agent's log file.
If the info entry point times out, output from the entry point is ignored. The State key is set to the value: Invalid. The error message is written to the agent's log file.
If a user kills the info entry point (for example, kill -15 pid), the State key is set to the value: Invalid. The error message is written to the agent's log file.
If the resource for which the entry point is invoked goes offline or faults, the State key is set to the value: Stale.
If the info entry point is not implemented, the State key is set to the value: Stale. The error message is written to the agent's log file.