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 entry points
The following table summarizes the return values for each entry point.
Table: Return values for entry points
Entry Point | Return Values |
---|---|
Monitor | C++ Based Returns ResStateValues:
Script-Based Exit values:
|
Info | 0 if successful; non-zero value if not successful |
Online | Integer specifying number of seconds to wait before monitor can check the state of the resource; typically 0, that is, check resource state immediately. |
Offline | Integer specifying number of seconds to wait before monitor can check the state of the resource; typically 0, that is, check resource state immediately. |
Clean | 0 if successful; non-zero value if not successful If clean fails, the resource remains in a transition state awaiting the next periodic monitor. After the periodic monitor, clean is attempted again. The sequence of clean attempt followed by monitoring continues until clean succeeds or CleanRetryLimit is not reached if it is set to non-zero value. For detailed descriptions of internal transition states, See State transitions. |
Action | 0 if successful; non-zero value if not successful |
Attr_changed | None |
Open | None |
Close | None |
Shutdown | None |
imf_init | 0 if successful; 1 if unsuccessful |
imf_register | 0 if successful; 1 if unsuccessful |
imf_getnotification | 0 if successful; 1 if failure; 3 if interrupted (failure case); 4 if critical failure |
migrate |
All other values in the range of 101 to 254 are reserved for future use. Agent framework ignores any value returned between this range and returns to previous state to continue with rest of the operations. Refer to MigrateWaitLimit and MigrateTimeout, before implementing this entry point. See MigrateTimeout. See MigrateWaitLimit. See SupportedOperations. |
meter |
All other values in the range of 1 to 253 are reserved for future use. The Agent framework considers those values as failure with unsupported value and sets the METER FAILED flag. These failure with unsupported value will not be counted against the MeterRetryLimit, so meter entry point should not use these values. See MeterRetryLimit. |