Using System State Manager › Create Other Resource and Action Tables › Add User Columns to an Existing SSM Table

Previous Topic: Sample SQL statement defining an action table

Next Topic: Parameters That Control SSM Operation

Add User Columns to an Existing SSM Table

You may need to insert additional user control columns within an SSM resource table after the initial SSM implementation.

To add additional user columns to an existing SSM table

  1. Enter OPSVIEW option 2.6 to list all RDF tables
  2. Type an I (Insert) beside the SSM table (using STCTBL as example), tab to the 'New Table' column, and enter a new table name (such as STCTBL_NEW).
  3. Press enter from the 'Specify Attributes Panel.'

    The table structure of the current STCTBL that you are modifying displays.

  4. Use ISPF edit to insert new column names and their corresponding structures and then press PF3.

    Important! Do not remove or modify any required SSM monitor columns as documented. Do not name any new column with values that may be used as the desired or current state value of a resource.

    The table is saved with the new column names and their corresponding structures.

  5. Type a T (Transfer) beside the STCTBL, tab to the 'New Table Column,' and then enter the name of the newly created table, which is STCTBL_NEW in this example.

    All existing data is transferred from the old table to the new table and the new table is ready to be placed in SSM control.

  6. Place the new table in SSM control by first removing the existing STCTBL from SSM control using the OPSVIEW option 4.11.1 SSM control panel.
  7. Once removed from SSM control, rename the existing STCTBL to a back-up name such as STCTBL_OLD using option R in the RDF table editor (OPSVIEW option 2.6).
  8. Rename STCTBL_NEW to STCTBL using the same R option in the RDF table editor.
  9. Re-add the new STCTBL back to SSM control. Keep in mind that depending on the user SSM automation that is in place, the SSMBEGIN routine may fire upon the re-adding of the table. You should first verify what the impact of any user code within this routine may perform. The SSMBEGIN rule can be safely disabled prior to re-adding the table using 4.11.1 if the automated logic path is unknown. Upon the re-adding of the table to SSM control, both the CURRENT_STATE and DESIRED_STATE columns are set to UNKNOWN.

    To re-prime these states to their current values:

    1. Set the SSM global MODE column to PASSIVE using the OPSVIEW 4.11.1 panel.
    2. Issue the TSO command 'OPSQL UPDATE STCTBL SET DESIRED_STATE = CHKPOINT_STATE'.

      This sets the DESIRED_STATE column to the value that it was in prior to the table renaming.

    The SSMSTATE (UNKNOWN action) will fire and set the CURRENT_STATE to the true state of the resource (UP or DOWN). After the CURRENT_STATE and DESIRED_STATES are synchronized correctly, the mode of SSM should be set back to ACTIVE.