Registry conversion utility

The TOM version 1.x registry is not compatible with TOM version 2.x. If you want to use version 1.x registry in TOM version 2.x, the registry must be converted by using the MAMRCONV utility that is provided in the BBSAMP data set. If you have a calendar definition base named DEFAULT in TOM version 1.x, the calendar definition base will be renamed to DEFAULTCAL during the conversion. Submitting the MAMRCONV utility requires RTCS to be active.

Figure 1. BBSAMP JCL MAMRCONV

//MAMRCONV JOB ,                              <=== CHANGE          
//*                                                                
//*---------------------------------------------------------------+
//* THIS JOB CAN BE USED TO CONVERT TOM VERSION 1 REGISTRY TO     |
//* TOM VERSION 2 REGISTRY FORMAT                                 |
//*                                                               |
//*---------------------------------------------------------------+
//* BEFORE SUBMITTING THE JCL UPDATE:                             |
//*                                                               |
//* #mvtomlib# - TOM Version 2 Load Library                       |
//*                                                               |
//* #mvtomv1r# - TOM Version 1 Registry data set to be converted  |
//*                                                               |
//* #mvtomv2r# - Predefined Sequential data set with attributes:  |
//*              Organization:  PS                                |
//*              Record format: VB                                |
//*              Record length: 8192                              |
//*              Block size:    27998                             |
//*                                                               |
//* AFTER SUBMITTING THE JCL:                                     |
//*                                                               |
//* The data set, specified as #mvtomv2r# can be used in the      |
//* PRIMEDD parameter of Parmlib member MAMINIxx to upload the    |
//* Registry to TOM Version 2.                                    |
//*---------------------------------------------------------------+
//MAMRCONV EXEC PGM=MAMRCONV                                      
//*----------------------------------------------------------------
//STEPLIB  DD  DISP=SHR,DSN=#mvtomlib#       <=== CHANGE           
//SYSUT1   DD  DISP=SHR,DSN=#mvtomv1r#       <=== CHANGE           
//SYSUT2   DD  DISP=SHR,DSN=#mvtomv2r#       <=== CHANGE           
//SYSABEND DD  SYSOUT=*

To convert TOM registry 1.x to 2.x

  1. Edit MAMRCONV and update the lines marked with CHANGE as documented in the JCL.
  2. Submit MAMRCONV where MainView Infrastructure version 6.xx is installed and RTCS is running. Review the Job Log to ensure conversion ran successfully.

    After MAMRCONV completes execution, the TOM objects, sets, calendars, and so on will be written to the SYSUT2 sequential data set in TOM version 2.xx format.

  3. Upload the SYSUT2 data set into TOM 2.x by using the PRIMEDD parameter of MAMINIxx BBPARM.

    Note

    The REGSTYxx BBPARM member is no longer used by TOM. The REGSTYxx parameters have been moved to the new BBPARM member MAMINIxx and MAMPLXxx

    All Debug options have been moved to the new BBPARM member MAMDBGxx.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments