MIGRATE with Monitoring Configuration Manager

The MIGRATE action enables you to import existing legacy PARMGEN RTE configuration settings from a specific WCONFIG member into the new "batch only" Monitoring Configuration Manager rte_plib_hilev.RTEDEF.

MIGRATE process

Before performing a MIGRATE action, make sure you have a backup of your existing legacy PARMGEN RTE in place.

In general, to migrate a legacy PARMGEN runtime environment (RTE) to a Monitoring Configuration Manager RTE, follow these steps:
  1. Modify the KFJJMCM sample job in TKANSAM (see example below) to select a MIGRATE action.
  2. Specify the source WCONFIG in the KFJ_MIGRATE_WCONFIG parameter.
  3. Run the KFJJMCM job to perform the migration and generate the new RTEDEF dataset.

    The MIGRATE action reads WCONFIG and other datasets from a former legacy PARMGEN installation and creates the sparse descriptors for it containing the parameters, hiding every parameter setting that is considered a default or has not been changed. It also copies other files for System Variables support, embed overrides, and security exits that are required to support the migration.

Note: If you want to migrate embed overrides, see https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/zmcm/zmcm-parm-embed.html for more information.

The MIGRATE action accepts PARMGEN RTEs with system variables. However, system variables are not copied unless you have chosen to override them in your legacy PARMGEN configuration. Variables are copied to the RTEDEF member VAR$GLOB.

If MIGRATE detects that a specified target RTEDEF dataset already exists, MIGRATE issues an error message and stops. If you want to use the existing RTEDEF dataset, change the CONFIRM parameter in KCIVARS to "Y". In this case, MIGRATE will first delete the existing RTEDEF dataset and then re-create it using the migrated parameters.

The MIGRATE action supports migrating one RTE at the time. It does not support migrating multiple legacy PARMGEN RTEs into a single RTEDEF configuration. Therefore the MIGRATE action will create members of type "Kpp$PARM" in the respective created RTEDEF data set, along with the rte_name member for the RTE-specific parameters.

The migration will work only for the OMEGAMON products that are supported by Monitoring Configuration Manager. If the migration source contains other products configured by the legacy PARMGEN that are not supported by Monitoring Configuration Manager, a warning message is issued as part of the MIGRATE action in the KCIPRINT output, but the MIGRATE action will continue to perform as expected for supported products.

Note: After MIGRATE, the generated RTEDEF dataset members must be carefully checked to see if the parameters have the expected values. Extra care must be taken with dataset high-level qualifiers, dataset names, and USS paths, as a subsequent GENERATE action might overwrite existing files.

Example of MIGRATE JCL

The following JCL is used to MIGRATE an existing legacy PARMGEN configuration pointed to by highlevel.WCONFIG into an RTEDEF library TSOUID.MONSUITE.RTEDEF.

During the MIGRATE action, the contents of the RTEDEF dataset will contain the respective parameters for the products configured in the legacy PARMGEN source.

Figure 1. Example JCL to perform the MIGRATE action
Monitoring Configuration Manager
/*JOBPARM SYSAFF=ZOS1
//S1       EXEC PGM=KCIOMEGA,REGION=0M,DYNAMNBR=256
//STEPLIB  DD DISP=SHR,DSN=MONSUITE.TKANMOD
//KCIFLOW  DD DISP=SHR,DSN=MONSUITE.TKANCUS(KFJOMEGA)
//KCIVARS  DD *                                        
ACTION            MIGRATE * CREATE|DISCOVER|GENERATE|DELETE|MIGRATE
RTE_NAME          RTE1
RTE_PLIB_HILEV    TSOUID.MONSUITE

* Required for the DELETE/MIGRATE actions, ignored by other actions: 
CONFIRM              N  * Y|N 
KFJ_MIGRATE_WCONFIG  'highlevel.WCONFIG'                                    
 
/*