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 open entry point
The status of the open entry point is passed as an argument to the next monitor entry point. The name of the argument is OpenStatus. The possible value for OpenStatus is 0 and 2. A value of 0 means that the open entry point completed successfully. A value of 2 means that the open entry point has timed out.
When an agent starts, the open entry point of each configured and enabled resource is called before its online, offline, or monitor entry points are called. This allows you to include initialization for specific resources. Most agents do not require this functionality and will not implement this entry point.
The open entry point is also called whenever the Enabled attribute for the resource changes from 0 to 1. The entry point receives the resource name and ArgList attribute values as input and returns no value.
A resource can be brought online, taken offline, and monitored only if it is managed by an agent. For an agent to manage a resource, the value of the resource's Enabled attribute must be set to 1. The open entry point creates the environment needed for other entry points to function. For example, the entry point could create files required by other entry points for the resource, or perform some resource-specific setup.