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
SupportedActions
The SupportedActions (string-keylist) attribute lists all possible actions defined for an agent, including those defined by the agent developer. The HAD process validates the action_token value specified in the hares -action resource action_token command against the SupportedActions attribute. For example, if action_token is not present in SupportedActions, HAD will not allow the command to go through. It is the responsibility of the agent developer to initialize the SupportedActions attribute in the resource type definition and update the definition for each new action added to the action entry point code or script. This attribute serves as a reference for users of the command line or the graphical user interface.
See About the action entry point.
An example definition of a resource type in a VCS ResourceTypeTypes.cf file may resemble:
Type DBResource ( static str ArgList[] = { Sid, Owner, Home, User, Pwork, StartOpt, ShutOpt } static keylist SupportedActions = { VRTS_GetRunningServices, DBRestrict, DBUndoRestrict, DBSuspend, DBResume } str Sid str Owner str Home str User str Pword str StartOpt str ShutOpt )
In the SupportedActions attribute definition, VRTS_GetRunningServices is a Veritas predefined action, and the actions following it are defined by the developer. The SupportedActions attribute value cannot be overridden.