iNCORPORATING SSM INTO A CURRENT OPS/MVS ENVIRONMENT USING SSMV2.

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

What is the best way to incorporate, or copy, System State Manager into an existing OPSMVS environment?  Would using writetable/readtable into a new copy of the current syschk1 work without overlaying any global variables they currently use? 

We are using SSMV2.  Not sure if only the SSM table would be replaced. Don't want the global variables overridden also. 

Resolution

There are 2 possible approaches to incorporate a new SSM into the environment:

1. In the first, you could just implement SSMV3 and run the discovery to build the new tables.

2. In the second approach, you could copy the tables from your test environment to the production environment via one of the following methods:

1. If the systems are connected via MSF, use the =2.1 panel and the MC command
2. If the systems are not connected via MSF, or you prefer this method, then you should use the WRITETBL function to export the tables to a sequential dataset, transfer the dataset to the production system, where you use the READTBL function to restore the tables.  Of course, it is recommended to use the WRITETBL on the production system, before commencing, so that you have a backup of it should you need it for some unforeseen reason. 
    

 - Note that neither of these procedures will affect the current global variables since you do not copy the entire SYSCHK1.

 

If you are not using the MSF related procedure, review the OPS REXX Programs section of the OPS/MVS manual for more information.

 

Below is sample REXX code that may be used to copy the resource and action tables:

/* rexx */

address osf

'OI WRITETBL TABLE(STCTBL) DSNAME(your_HLQ.STCTBL)',

'SPACE(10,1) UNIT(SYSDA) SUBSYS(OPSS)'

address osf

'OI WRITETBL TABLE(STCTBL_ACT) DSNAME(your_HLQ.STCTBL.ACT)',

'SPACE(10,1) UNIT(SYSDA) SUBSYS(OPSS)'

Exit