The SSMPLEXNAME parameter sets a visible SSMplex name for the local system and immediately transmits the name to all systems that have an MSF connection to the local system. Every CA OPS/MVS system has its own setting for this parameter. To programmatically retrieve the SSMplex name of all systems, issue the ADDRESS OPSCTL MSF LIST command.
This setting is intended for use by SSMGA. However, customers who do not use SSMGA can use this setting as a configurable option for their own application that applies coordinated automation procedures to multiple connected systems
NONE
Any 1- to 8-character name
Anytime
Example: SSMPLEXNAME
This function assigns an SSM group name to the local SSM task:
OPSPRM('SET','SSMPLEXNAME','PROD001')
There are five of these parameters named SSMMONITOREDCOL1 to SSMMONITOREDCOL5. Each SSMMONITOREDCOLn parameter can specify an eighteen-character SQL column name. Columns specified within these parameters are actively monitored by System State Manager. User-defined exits may be written to react to the global events generated by changes to these columns. Changes to these columns may also be logged to the OPSLOG using the trace message OPS7914T if SSMAUDIT is set to YES.
Blank ' '
The default value of blank indicates that no column name is specified on this parameter.
Up to eighteen character column name.
This value indicates that System State Manager should monitor changes within the column specified in all SSM-managed tables on this subsystem.
Important! Consider your choice of additional monitored columns carefully. Monitoring a column involves waking up the main SSM processing cycle each time a change is detected. Frequently modified columns are unsuitable for monitoring and may result in poor performance. Examples of inappropriate SSM columns to monitor include MISSING_PREREQ and INTERNAL_DATA
|
Copyright © 2014 CA.
All rights reserved.
|
|