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
Attribute dimensions
VCS attributes have the following dimensions.
Scalar | A scalar has only one value. For example: MountPoint = "/Backup" |
Vector | A vector is an ordered list of values. Each value is indexed using a positive integer beginning with zero. Use a comma (,) or a semi-colon (;) to separate values. A set of brackets ([]) after the attribute name denotes that the dimension is a vector. Example snippet from the type definition file for an agent: str BackupSys[] When values are assigned to a vector attribute in the main.cf configuration file, the attribute definition might resemble: BackupSys[] = { sysA, sysB, sysC } For example, an agent's ArgList is defined as: static str ArgList[] = {RVG, DiskGroup, Primary, SRL, Links} |
Keylist | A Keylist is an unordered list of strings, and each string is unique within the list. Use a comma (,) or a semi-colon (;) to separate values. For example, to designate the list of systems on which a service group will be started with VCS (usually at system boot): AutoStartList = {SystemA; SystemB; SystemC} For example: keylist BackupVols = {} When values are assigned to a keylist attribute in the main.cf file, it might resemble: BackupVols = { vol1, vol2 } |
Association | An association is an unordered list of name-value pairs. Use a comma (,) or a semi-colon (;) to separate values. A set of braces ({}) after the attribute name denotes that an attribute is an association. For example, to designate the list of systems on which the service group is configured to run and the system's priorities: SystemList = {SystemA=1, SystemB=2, SystemC=3} For example: int BackupSysList {} When values are assigned to an association attribute in the main.cf file, it might resemble: BackupSysList{} = { sysa=1, sysb=2, sysc=3 } |