IBM Support

CCV5210E with CCVTD520 for any CICS CM 5.1 function after upgrading to CICS CM 5.2

Question & Answer


Question

Why am I receiving message CCV5210E when I attempt to perform any function with CICS Configuration Manager for z/OS (CICS CM) V5.1 after upgrading my test environment to CICS CM V5.2? It seems like my CICS CM V5.1 production environment is trying to load a CICS CM V5.2 module CCVTD520 from our upgraded test environment.

Following are the messages in my CCVLOG:

CCV5210E Severe error for Command LIST. Processing terminated.
CCV9999I TASKNO=00031519
CCV9999I RC=ERR
CCV9999I MODID=X'0005'
CCV9999I RSN=X'0005'
CCV9999I INFO=X'01000501'
CCV9999I INFO2=X'C3C3E5E3C4F5F2F0' CCVTD520
CCV9999I USERID=EOT03
CCV9999I EIBFN=X'0E06'
CCV9999I RESP=00000027
CCV9999I RESP2=00000003

Answer

When CICS CM writes a record to its CCVDDD repository file, the record is stamped with the version number of the CICS CM system that did the write. This allows CICS CM to read records written at varying releases, and interpret them correctly.

When you see message CCV5210E with CCVTD520, this indicates that the production CICS CM system (running at v510) has encountered a record written at v520. To interpret the record, the CCVTD520 program (the data definition layouts for v520) is loaded, but the program is not found.

A CICS CM V5.1 fallback (or toleration) APAR is available that provides the V5.2 translation program CCVTD520. When upgrading to CICS CM V5.2, this APAR in the previous release (in this case CICS CM V5.1) allows you to fallback or revert from CICS CM V5.2, and enables the CICS CM V5.1 system to tolerate the v520 records.

The toleration APAR for CM 5.1 is PI13261 (PTFs UI18586,UI18587,UI18588) and should be applied.

You will encounter the error condition whenever a v520 record is processed. The problem might appear intermittent, as some requests might not encounter the record. Say (for example) the offending v520 record is a change package, then listing CICS Configurations from the repository might not be affected.

The problem could also extend to records in the CCVJNL journal file, as these too are stamped with the v520 markers to denote the CICS CM release that wrote the record, again to enable record conversion (or interpretation) across CICS CM releases.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS2L7A","label":"CICS Configuration Manager for z\/OS"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICSCM CICS CM

Document Information

Modified date:
08 January 2016

UID

dwa1245386