The following procedure explains how to use backups of existing production files in the new Control‑M/Analyzer environment:

1. Prepare all relevant Control‑M/Analyzer data sets from supported earlier versions (Vxxx) for use in the current release. The following table identifies the data sets to prepare.

   Table 24 Control‑M/Analyzer data sets

   Data set name	Data file name	Index file name
   Group	GRPD	GRPI
   Model Variables Definition	MODD	MODI
   Database Variables Generations	VARD	VARI
   Rule Activity	JAFD	JAFI
   Report	REPD	REPI
   Active Balancing	ABF	ABFBKP

   Note: If you are using the dual database option, files with D000 and E000 suffixes (one for each of the dual files you have), must be handled together in order to keep them synchronized. In the following procedure, information regarding the D000 parts of dual files is shown in bold. For example, if the current naming for Vxxx is as shown below for the GRP file (and this file is used in this procedure as a continuing example), dual files are identified as follows:

   CTB.Vxxx.GRPD.D000

   CTB.Vxxx.GRPD.E000

2. The files shown in the previous table can be migrated in one of the following ways:
   • Create backups (not simple copies) of your current Vxxx environment, to be used in the current release environment.

     If you only copy the current file you still need the current release (rather than Vxxx) qnames and file names.

     Note: If you do copy the files, you should set the internal qname and file name using a zap utility, and not a standard editor.

   • Use the IOADBF utility in the current release environment to create file names, which enables you to use current release (rather than Vxxx) qnames and file names, instead of manually allocating those names. This procedure, which BMC recommends that you use, will also create, in a single operation, both D000 and E000 files, provided that you specified DUAL=Y in the new IOAP.version 8000.INSTWORK(DEF*) members.

     Note: Use the following syntax to create backup copies. The names of the files are set in the DEF* members and according that IOADBF can create new files for you.

     //EXEC IOADBF,FUNC=INIT,D=INSTCTB,M=DEFGRPD

3. Use the following procedure to copy the Vxxx GRP file you just created, to the target Vyyy data sets.

   /STEP1    EXEC  PGM=IEBGENER

   //SYSPRINT DD  SYSOUT=*

   //SYSIN    DD  DUMMY

   //SYSUT1   DD  DISP=SHR,DSN=CTB.Vxxx.GRPD.D000

   //SYSUT2   DD  DISP=SHR,DSN=CTB.V9000.GRPD.D000

     

   //STEP1    EXEC  PGM=IEBGENER/

   //SYSPRINT DD  SYSOUT=*

   //SYSIN    DD  DUMMY

   //SYSUT1   DD  DISP=SHR,DSN=CTB.Vxxx.GRPD.E000

   //SYSUT2   DD  DISP=SHR,DSN=CTB.V9000.GRPD.E000

4. Adjust the qname and file name in the files.

   Note: Since these are not the original files, you cannot use IOADBF to make the adjustments. Instead of using the CREGRP1 migration step, you should use the AMASZAP or ABSDUMPT utility combination, and so on, to zap the data in both new data sets (CTB.V9000.GRPD.E000 and (CTB.V9000.GRPD.D000 in dual mode)) to the qname and file name of your Vyyy environment, as shown in the following table.

   There is no need to adjust the DISK or VOLSER fields.

   Table 25 QNAME and file name changes

   Field	Offset	Length
   QNAME	1C	8
   FILENAME	2C	44

5. Repeat steps 1 - 4 for the rest of your files.