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
About the close entry point
The close entry point is called whenever the Enabled attribute for a resource changes from 1 to 0, or when a resource is deleted from the configuration on a running cluster and the state of the resource permits running the close entry point.
Note that a resource is monitored only if it is managed by an agent. For an agent to manage a resource, the resource's Enabled attribute value must be set to 1.
See the table below to find out which states of the resource allow running of the close entry point when the resource is deleted on a running cluster. It receives a resource name and ArgList attribute values as input and returns no value. This entry point typically deinitializes the resource if implemented. Most agents do not require this functionality and will not implement this entry point.
Table: States in which CLOSE entry point runs - based on operations type of resource
Resource Type | Online State | Offline State | Probing | Going Offline Waiting | Going Online Waiting |
---|---|---|---|---|---|
None (persistent) | Yes | N/A | Yes | Yes | N/A |
OnOnly | Yes | Yes | Yes | Yes | Yes |
OnOff | Yes | Yes | Yes | Yes | Yes |
The open and close entry points are related in the sense that the open entry point creates the environment needed for other entry points, while the close entry points clean the setup created by the open entry point.