After upgrading my CA Datacom CICS Services software to the new release, I get an error: DC00130C COMPONENTS OF THE SERVICE FACILITY ARE NOT ON THE SAME RELEASE.

Products

• Datacom
• DATACOM - AD
• Ideal
• Database Analyzer (IMS Tools)
• Mainframe Configuration Manager for IMS for z/OS
• IMS TOOLS - MISC
• Compress Data Compression (IMS Tools)
• Database Analyzer for IMS for z/OS
• Database Copier for IMS for z/OS
• Database Organizer for IMS for z/OS
• Mainframe Extended Terminal Manager (IMS Tools)
• High Performance Recovery for IMS for z/OS
• Database Organizer (IMS Tools)
• Mainframe Program Restart Manager for IMS for z/OS
• Secondary Index Builder for IMS for z/OS
• Secondary Index for IMS for z/OS
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Description:

After upgrading my CA Datacom CICS Services software to the new release, I get an error:

DC00130C COMPONENTS OF THE SERVICE FACILITY ARE NOT ON THE SAME RELEASE

DBCVTPR REL = 11.0 DCCOCPR REL = 14.0

A review of the base and custom loadlibs shows that these modules are both at 14.0. How do I fix this?

Solution:

The DBCVTPR module is a customized load module for CA Datacom CICS Services, and is assembled in job B1CUS01. The SYSLMOD in the link/binder step should be the CUSLIB for the product. There are two primary causes for this error - either the module was not assembled and linked into the correct loadlib, or there is a loadlib higher in the DFHRPL concatenation that has the DBCVTPR module.

Here are steps to follow to identify the cause of the DC00130C error.

1. Review the B1CUS01 job and be sure the SYSLMOD loadlib is the same as the loadlib used in your CICS startup JCL.
2. If the loadlib is correct, it is possible you have another version of DBCVTPR in another loadlib higher in the concatenation for DFHRPL. Please follow these steps in your CICS region:
   
   * In the CICS region, issue the transaction CEMT I PROG(DBCVTPR)
   
   You should receive a screen that looks like this:
   STATUS: RESULTS - OVERTYPE TO MODIFY
   Prog(DBCVTPR )Leng(0000008464)AssProEnaPri
   Res(001)Use(0000000003)AnyCexFulQuaCic
   
   Move your cursor down beside that entry (to the left of 'Prog(...'), and hit <ENTER> to display the attributes of the program.
   Scroll down the list of attributes to find the Librarydsn. This will tell you which loadlib had the module that was picked up. It will look something like this:
   
   . . .
   Apist(Cicsapi)
   Remotesystem()
   Runtime(Native)
   Remotename()
   Library(DFHRPL)
   Librarydsn(YOURHLQ.CTS420.CUSLIB) <<---This is where DBCVTPR was found
   Jvmclass()
   . . .

Once you have identified the loadlib with the wrong-version DBCVTPR, you can take the necessary steps to either demote this loadlib or to promote the CA Datacom CICS Services CUSLIB used in B1CUS01 to a higher position in the DFHRPL list. Once you recycle the CICS region, your CA Datacom CICS Services product should be operational on the correct release.

Environment

Release: DATABB00200-14-Datacom/AD
Component: