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
Comments
Log in or register to comment.