What is the best way to incorporate, or copy, ssm into an existing opsmvs environment? Would be using writetable/readtable into a new(copy of the current syschk1 work,without overlaying any global variables they currently use? ) Currently testing the install on a test lpar,with no current globals defined. Using SSMV2. Not sure if only the ssm table would be replaced. Don't want the global variables overridden also.
Release : 13.5
Component : OPS/MVS
There are 2 possible approaches to incorporate a new SSM into the environment:
In the first, you could just implement SSMV3 and run the discovery to build the new tables.
In the second approach, you could copy the tables from your test environment to the production environment via one of the following methods:
It should be noted that neither of these procedures will affect the current global variables, as you are not copying the entire SYSCHK1.
If you are not using the MSF related procedure, please see this link for more information: https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-ops-mvs-event-management-and-automation/14-0/reference-information/command-and-function-reference/relational-data-framework-reference/ops-rexx-programs.html
Here is a sample REXX 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