Using SSM Global Application › How to Set Up SSMGA › Using the SSM Subtask

Using the SSM Subtask

You control the starting and stopping of the SSM subtask using the following SSMSUBRULE parameter values:

• A value other than 'NONE' starts the SSM subtask
• Setting the value to 'NONE' stops the SSM subtask

Note: The value of the SSMSUBRULE parameter must be an enabled AOF request rule name in order for any productive work to be performed.

The SSM subtask is posted for an event by any of the following conditions:

• An explicit post by the OPSSMTBL command with the keyword operand POST(SSMSUB).
• Anytime an MSF connection with the same SSMPLEXNAME value changes to INACTIVE status.
• Anytime an MSF connection's SSMPLEXNAME, SSMACTIVEGLOBAL, or SSMPRIORITY value changes.
• Anytime an external RDF table modification SQL statement changes a table whose name matches the table name prefix specified in the SSMSUBPREFIX parameter. Table modifications that originate from the local SSM main task and the SSM subtask do not cause a post event.

Although the new SSMGA feature will use this subtask for transmitting status information from system to system, the use of the SSM subtask is not limited to SSMGA. You can use this subtask to perform continuous auxiliary automation in support of SSM events.

Some possible uses for the subtask are as follows:

• Execute a designated AOF request rule each time it is posted
• Handle repetitive SSM processing that involves long execution times that could impede the performance of the primary SSM task
• Implement an alternate automation procedure such as MSF connection management