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
RegList
RegList is a type level keylist attribute that can be used to store, or register, a list of certain resource level attributes. The agent calls the attr_changed entry point for a resource when the value of an attribute listed in RegList is modified. The RegList attribute is useful where a change in the values of important attributes require specific actions that can be executed from the attr_changed entry point.
By default, the attribute RegList is not included in a resource's type definition, but it can be added using either of the two methods shown below.
Assume the RegList attribute is added to the FileOnOff resource type definition and its value is defined as PathName. Thereafter, when the value of the PathName attribute for a FileOnOff resource is modified, the attr_changed entry point is called.
Method one is to modify the types definition file (types.cf for example) to include the RegList attribute when VCS is not running. Add a line in the definition of a resource type that resembles:
static keylist RegList = { attribute1_name, attribute2_name,...}
For example, if the type definition is for the FileOnOff resource and the name of the attribute to register is PathName, the modified type definition would resemble:
. . . type FileOnOff ( str PathName static keylist RegList = { PathName } static str ArgList[] = { PathName } ) . .
Method two is to use the haattr command to add the RegList attribute to a resource type definition and then modify the value of the type's RegList attribute using the hatype command when VCS is running; the commands are:
haattr -add -static resource_type RegList -keylist
To set value
# hatype -modify resource_type RegList attribute_name1 attribute_name2
To add a new key
# hatype -modify resource_type RegList -add attribute_name3
For example:
# haattr -add -static FileOnOff RegList -keylist
# hatype -modify FileOnOff RegList PathName
# hatype -modify FileOnOff RegList -add PathName
The RegList attribute cannot be overridden.