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 open entry point
 - About the monitor entry point
 - About the online entry point
 - About the offline entry point
 - About the clean entry point
 - About the action entry point
 - About the info entry point
 - About the attr_changed entry point
 - About the close entry point
 - About the shutdown entry point
 - About the imf_init entry point
 - About the imf_register entry point
 - About the imf_getnotification entry point
 - About the migrate entry point
 - About the meter entry point
 
 - Return values for entry points
 - 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++
 - Data Structures
 - Syntax for C++ entry points
 - Agent framework primitives
- VCSAgGetMonitorLevel
 - VCSAgGetFwVersion
 - VCSAgGetRegVersion
 - VCSAgRegisterEPStruct
 - VCSAgSetCookie2
 - VCSAgRegister
 - VCSAgUnregister
 - VCSAgGetCookie
 - VCSAgStrlcpy
 - VCSAgStrlcat
 - VCSAgSnprintf
 - VCSAgCloseFile
 - VCSAgDelString
 - VCSAgExec
 - VCSAgExecWithTimeout
 - VCSAgGenSnmpTrap
 - VCSAgSendTrap
 - VCSAgLockFile
 - VCSAgInitEntryPointStruct
 - VCSAgSetStackSize
 - VCSAgUnlockFile
 - VCSAgValidateAndSetEntryPoint
 - VCSAgSetLogCategory
 - VCSAgGetProductName
 - VCSAgMonitorReturn
 - VCSAgSetResEPTimeout
 - VCSAgDecryptKey
 - VCSAgGetConfDir
 - VCSAgGetHomeDir
 - VCSAgGetLogDir
 - VCSAgGetSystemName
 - VCSAG_CONSOLE_LOG_MSG
 - VCSAG_LOG_MSG
 - VCSAG_LOGDBG_MSG
 - VCSAG_RES_LOG_MSG
 
 - Agent Framework primitives for container support
 
 - Creating entry points in scripts
- About creating entry points in scripts
 - Syntax for script entry points
- Syntax for the monitor script
 - Syntax for the online script
 - Syntax for the offline script
 - Syntax for the clean script
 - Syntax for the action script
 - Syntax for the attr_changed script
 - Syntax for the info script
 - Syntax for the open script
 - Syntax for the close script
 - Syntax for the shutdown script
 - Syntax for the imf_init script
 - Syntax for the imf_register script
 - Syntax for the imf_getnotification script
 - Syntax for migrate script
 - Syntax for meter script
 
 - Agent framework primitives
- VCSAG_GET_MONITOR_LEVEL
 - VCSAG_GET_AGFW_VERSION
 - VCSAG_GET_REG_VERSION
 - VCSAG_SET_RES_EP_TIMEOUT
 - VCSAG_GET_ATTR_VALUE
- To get number of keys in the key list attribute and the index of attribute in argument list
 - To get a particular key in the key list and vector attribute
 - To get the number of keys in the association attribute, and index of attribute in the argument list
 - To get a particular key or value in the association attribute:
 
 - VCSAG_SET_RESINFO
 - VCSAG_MONITOR_EXIT
 - VCSAG_SYSTEM
 - VCSAG_SU
 - VCSAG_RETURN_IMF_RESID
 - VCSAG_RETURN_IMF_EVENT
 - VCSAG_BLD_PSCOMM
 - VCSAG_PHANTOM_STATE
 - VCSAG_SET_ENVS
 - VCSAG_LOG_MSG
 - VCSAG_LOGDBG_MSG
 - VCSAG_SQUEEZE_SPACES
 
 - 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
- About building a script based IMF-aware custom agent
 - Linking AMF plugins with script agent
 - Creating XML file required for AMF plugins to do resource registration for online and offline state monitoring
- Example of amfregister.xml for registration of process-based resource with AMF for online monitoring
 - Example of amfregister.xml for registration of process-based resource with AMF for offline monitoring
 - Example of amfregister.xml for online and offline IMF monitoring for a given process
 - Examples for adding RepearName tag in amfregister.xml
 
 - Adding IMF and IMFRegList attributes in configuration
 - Monitor without IMF integration
 - Monitor without IMF but with LevelTwo monitor frequency
 - Monitor with IMF integration
 - Monitor with IMF but with LevelTwo monitor frequency
 - Installing the IMF-aware script-based custom agent
 
 - Testing agents
 - Static type attributes
- About static attributes
 - Static type attribute definitions
- ActionTimeout
 - AdvDbg
 - AEPTimeout
 - AgentClass
 - AgentDirectory
 - AgentFailedOn
 - AgentFile
 - AgentPriority
 - AgentReplyTimeout
 - AgentStartTimeout
 - AlertOnMonitorTimeouts
 - ArgList
 - AttrChangedTimeout
 - AvailableMeters
 - CleanRetryLimit
 - CleanTimeout
 - CloseTimeout
 - ContainerOpts
 - ConfInterval
 - EPClass
 - EPPriority
 - ExternalStateChange
 - FaultOnMonitorTimeouts
 - FaultPropagation
 - FireDrill
 - IMF
 - IMFRegList
 - InfoInterval
 - InfoTimeout
 - IntentionalOffline
 - LevelTwoMonitorFreq
 - LogDbg
 - LogFileSize
 - LogViaHalog
 - ManageFaults
 - Meters
 - MeterControl
 - MeterRegList
 - MeterRetryLimit
 - MeterTimeout
 - MonitorInterval
 - MonitorStatsParam
 - MonitorTimeout
 - MigrateTimeout
 - MigrateWaitLimit
 - NumThreads
 - OfflineMonitorInterval
 - OfflineTimeout
 - OfflineWaitLimit
 - OnlineClass
 - OnlinePriority
 - OnlineRetryLimit
 - OnlineTimeout
 - OnlineWaitLimit
 - OpenTimeout
 - Operations
 - RegList
 - RestartLimit
 - ScriptClass
 - ScriptPriority
 - SourceFile
 - SupportedActions
 - SupportedOperations
 - ToleranceLimit
 
 
 - 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
 
NumThreads
NumThreads specifies the maximum number of service threads that an agent is allowed to create. Service threads are the threads in the agent that service resource commands. NumThreads does not control the number of threads used for other internal purposes.
Agents dynamically create service threads depending on the number of resources that the agent has to manage. Until the number of resources is less than the NumThreads value, the addition of a new resource will make the agent create an additional service thread. Also, if the number of resources falls below the NumThreads value as a result of deletion of resources, the agent will correspondingly delete service threads. Since an agent for a type will be started by VCS HAD process only if there is at least one resource for that type in the configuration, an agent will always have at least 1 service thread. Setting NumThreads to 1 will thus prevent any additional service threads from being created even if more resources are added.
If the entry points have a locking mechanism within them for synchronization, then set the NumThreads attribute to a relatively low value, for example, 2 - 5.
The maximum value that can be set for NumThreads is 100. If NumThreads need to be increased beyond 30, please contact Arctera support.
Default is 10. The NumThreads attribute cannot be overridden.