Previous Topic: Add User Columns to an Existing SSM TableNext Topic: Manage Tables with the OPSSMTBL Command


Parameters That Control SSM Operation

The following CA OPS/MVS parameters affect the operation of SSM directly. You can set these parameters at product initialization, and you can change these parameters at any time.

Note: For more detailed information on these parameters, see the Parameter Reference.

SSMACTIVEGLOBAL

Sets a globally visible status for the local system and immediately transmits the status to all CA OPS/MVS systems that are connected through MSF.

SSMAUDIT

If YES, causes OPS7914T messages to send to OPSLOG for every significant change to the resource tables or directory table.

SSMAUXTBLPREFIX

Specifies an auxiliary table name prefix, making that RDF table eligible for change monitoring by the SSM engine.

SSMDEBUG

Causes messages OPS7913T, OPS7914T, and OPS9999T to be sent to OPSLOG.

SSMGLOBALEXITTBL

Specifies a valid 1-to-18-character RDF table name. The specified table is used to process the SSMGLOBALEXITS parameter.

SSMGLOBALEXITS

Determines whether the global exit facility remains active while SSM is executing.

SSMGLVPREFIX

Specifies a global variable name prefix that substitutes for the & when the string &.nnnn is found in an action string.

SSMMONITOREDCOLn

Five parameters that each specify a 1- to 18-character RDF table column name. Columns specified here will be actively monitored for changes by SSM.

SSMPLEXNAME

Sets the SSMplex name of the local system name and then transmits that name to all systems that have an MSF connection to the local system.

SSMPRIORITY

Sets a global priority for the local system and transmits this value to all CA OPS/MVS systems that are connected through MSF.

SSMSUBPREFIX

Specifies an RDF table name prefix that awakens the SSM subtask manager from a wait state.

SSMSUBRULE

Specifies the name of an enabled AOF request rule to that the SSM subtask manager executes whenever the subtask manager is awakened.

SSMVERSION

Specifies the version of SSM to activate. Currently 2 is the only supported version.

STATEGROUPMAN

Determines whether SSM automatically maintains Group Manager tables.

STATEIGNOREMPRE

Controls whether nonexistent SSM resource prerequisites are considered missing when prerequisite processing that the SSM engine task performs.

STATEMAN

Controls the overall mode SSM uses to monitor resources. The default monitoring mode is ACTIVE.

STATEMATCHPREFIX

Controls whether SSM prerequisite and subrequisite processing uses the defined UP and DOWN states for a resource table as states that must match exactly or as prefix values that must match only up to the length of the state names.

STATEMAXACTION

Limits the number of actions per minute that SSM can take for any resource that it manages (five is the default). When this limit is exceeded, SSM issues the message OPS7903W STATEMAN ACTION LIMIT EXCEEDED FOR table.name.

STATEMAXACTION lets SSM detect and correct any repetitive actions for a problem task. You can write a rule that message OPS7903W triggers that updates the CURRENT_STATE value to ERROR, which could then trigger some action to take care of the problem task.

STATEMAXWAIT

Determines how often SSM scans its tables to detect resources with mismatched CURRENT and DESIRED states.

STATETBL

Names the directory table. The default name is SSM_MANAGED_TBLS.

STATETBLLOG

Determines whether messages are produced in OPSLOG when a change is made to the active SSM directory table using the OPSSMTBL command.