Converting the CICSPlex SM data repository

You can run the EYU9XDUT utility to convert the CICSPlex® SM data repository from any release of CICSPlex SM to this release, and back again. That is, you can upgrade the data repository to the current release of CICSPlex SM, and you can convert it back to a previous release. For example, after you have upgraded to CICSPlex SM for CICS® Transaction Server for z/OS®, Version 3 Release 1, you can convert the data repository back to CICSPlex SM for CICS Transaction Server for z/OS Release 2.3 for use with a CMAS running the that level of CICSPlex SM code.

Start of changeThe conversion is controlled by the TARGETVER parameter and the DD statements you use to execute EYU9XDUT. To convert between a previous release and CICSPlex SM for CICS Transaction Server for z/OS, Version 3 Release 1 requires the EYUDREP, NEWREP, and BYPASS DD statements in the JCL. The EYUDREP statement must reference an existing input data repository, and the NEWREP statement must reference the output data repository.End of change

Start of changeCRESxxxx is a CICSPlex SM Topology Manager object that describes instances of a resource within a CICS system. All CRESxxxx resource table objects are deleted during the conversion process. These deleted records are rebuilt the first time the MAS connects or joins to the CMAS. The following message is then output to the SYSPRINT DD statement with a count of how many records were not converted:

EYUXD0708I CRESxxxx Resource Table nnnnn records not converted
End of change

Start of changeEYU9XDUT Return codes:

0
execution completed normally. This return code is accompanied by message:
EYUXD0702I Repository successfully converted
indicating the repository was successfully converted. This message may also be preceded by the message:
EYUXD0708I CRESxxxx Resource Table nnnnn records not converted
4
some records could not be converted. This return code is accompanied by message:
EYUXD0706W DDNAME NEWREP  nnnnn records were bypassed
indicating the repository was successfully converted but some records were bypassed and not written to the new repository. These records are written to the BYPASS DD statement. This message can also be preceded by message:
EYUXD0708I CRESxxxx Resource Table nnnnn records not converted
8
EYU9XDUT has failed. Check the joblog for error messages that indicate the cause of the error. For example, DD statement missing, or invalid NEWREP dataset.
End of change
Note:
Shutdown the CMAS that is using EYUDREP before running EYU9XDUT, otherwise, X'A8' is returned when the dataset is opened.

Use JCL similar to that in Figure 51 to convert from Release 2 of CICSPlex SM to CICSPlex SM for CICS Transaction Server for z/OS, Version 3 Release 1. This sample JCL assumes that you have already allocated the VSAM cluster that is referenced by the NEWREP DD statement. Start of changeThe file identified by the NEWREP DD statement must be an empty file.End of change

Figure 51. Example JCL to run EYU9XDUT
Start of change//DREPCNVT EXEC   PGM=EYU9XDUT,
//                     PARM=('TARGETVER=0310')
//STEPLIB   DD    DISP=SHR,DSN=CICSTS31.CPSM.SEYUAUTH
//EYUDREP   DD    DISP=SHR,DSN=CPSM310.EYUDREP.cmasname
//NEWREP    DD    DISP=OLD,DSN=CICSTS31.CPSM.EYUDREP.cmasname
//BYPASS    DD    SYSOUT=*
//SYSPRINT  DD    SYSOUT=*End of change

In the JCL, use a value for TARGETVER that indicates the release you are converting to. For example:

To convert to.. Use:
Release 3 TARGETVER=0130
CICSPlex SM for CICS TS Release 3 TARGETVER=0140
CICSPlex SM for CICS Transaction Server for z/OS Release 2.1 TARGETVER=0210
CICSPlex SM for CICS Transaction Server for z/OS Release 2.2 TARGETVER=0220
CICSPlex SM for CICS Transaction Server for z/OS Release 2.3 TARGETVER=0230
CICSPlex SM for CICS Transaction Server for z/OS Release 3.1 TARGETVER=0310

When the data repository is updated from a previous release to the current release, information stored in the earlier version is carried over to the current version of the data repository. When the data repository reverts back from the current release to a previous release, and the record in which information is changed is identical in both releases, the changes are carried back to the earlier version. Likewise, if a field in a record exists in both releases, later changes to the information in a field are carried back to the earlier version. However, when the data repository is converted from the current release to a previous release and either the record or a field in it did not exist in the previous release, the information contained in the later version is permanently lost.

(For more information about the data repository, see Creating the CICSPlex SM data repository and Expanding the CICSPlex SM data repository.)

[[ Contents Previous Page | Next Page Index ]]