Using SSM Global Application › SSMGA Setup Requirements › Step 4: Set the Parameters

Step 4: Set the Parameters

You will need to adjust the CA OPS/MVS parameter settings.

To set the parameters

1. Assign an SSMPLEXNAME and SSMPRIORITY to each system that participates in an SSMGA global status management complex.

   SSMPLEXNAME=SSMplex name
   

   SSMplex name (8 chars max) is the collective name for all systems in an SSMplex. To be an SSMplex member, a system must have an MSF connection to at least one other system, and both must have the same SSMPLEXNAME.

   SSMPRIORITY=priority value
   

   Global selection priority (0-999).

   A priority of zero prevents a system from becoming a global system. If no global system is active, or if the active global system goes offline, the eligible system having the highest SSMPRIORITY will become the global system. For a system to be eligible, it must have an MSF connection to all other systems in the SSMplex, and be operating normally. If after a global system is selected, a higher priority system becomes eligible to be the global system, the global system will not change automatically. To select any eligible system as the new global system, use the special priority of 1000. SSMGA will make the system that you set to priority 1000 the new global system, and then restore the original priority of the new global system.

   Once you move a global system, the new system needs to gather data from the other systems. During this time, it is normal for the SETSYS processing display to show two global systems for a short period of time in the OPSLOG.

2. Activate the subtask for SSMGA. SSM provides the ability to create a separate SSM subtask whose primary function is to perform asynchronous operations on behalf of the primary SSM task.

   To activate the subtask for SSMGA, specify the following parameters:

   SSMSUBRULE=SSMGAGBL
   

   SSMSUBPREFIX=RDF table name prefix (6 chars max)
   

   Suggested RDF table name prefix: 'SSMGA_'

   The subtask is activated by specifying a request rule name other than 'NONE' for the SSMSUBRULE parameter. Each time the SSM subtask is posted, the specified request rule will be invoked. The SSMSUBPREFIX specifies an RDF table name prefix that results in a post of the SSM subtask whenever a prefix matching table modification is made by any task other than SSM and the SSM subtask. In addition, a POST(SSMSUB) operand is available on the OPSSMTBL POI command for on-demand posting of the SSM subtask from any environment without a table modification.

   Note: You may want to leave the SSMSUBRULE parameter set to NONE (the default value) until after you have made all other changes to an existing SSM configuration and set the STATEMAN parameter back to ACTIVE. See Step 10.

   SSMGA creates the following GLOBAL TEMPORARY tables using the SSMSUBPREFIX value specified:

   • LST - local status table on all systems

     prefix||#L#_STATUS
     

   • GST - global status table on global system

     prefix||#G#_STATUS
     

   • GRT - global group membership table on global system

     prefix||#G#_GROUPS
     

   • GCT - global command table on global system

     prefix||#G#_CMDS
     

3. Increase the value of the AOFSIZE parameter.

   The AOFSIZE parameter determines the size of the AOF workspace, which is used to store REXX variables. You may find that you will have to increase the value of the AOFSIZE parameter, depending on its current value and the number of SSM resources you have defined. Error message OPS0998E indicates that the value of parameter AOFSIZE needs to be increased.

4. Increase the value of the GLOBALTEMPMAX parameter.

   The GLOBALTEMPMAX parameter determines the maximum number of temporary global variables that OPS/MVS can create. Temporary global variables are used to store RDF tables. You may find that you will have to increase the value of the GLOBALTEMPMAX parameter, depending on its current value and the number of SSM resources you have defined. Error message OPS7593O indicates that the value of parameter GLOBALTEMPMAX needs to be increased.

5. Increase the value of the SQLPOOLSIZE parameter.

   The SQLPOOLSIZE parameter determines the size of the storage pool used by the RDF to contain SQL data. You may find that you will have to increase the value of the SQLPOOLSIZE parameter, depending on its current value and the number of SSM resources you have defined. Error message OPS3032T indicates that the value of parameter SQLPOOLSIZE needs to be increased.

6. Increase the value of the MSFPOOLSIZE parameter.

   The MSFPOOLSIZE parameter determines the size of the storage pool used by MSF to contain data being passed between OPS/MVS systems through MSF. You may find that you will have to increase the value of the SQLPOOLSIZE parameter, depending on its current value and the number of SSM resources you have defined. Error message OPS3032T indicates that the value of parameter MSFPOOLSIZE needs to be increased.