How to verify the PTF level of CA Datacom PC Call module DBPCCPR?

Products

• Datacom
• DATACOM - AD
• 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

How to verify the PTF level of CA Datacom Program Call Module DBPCCPR?

Environment

z/OS

Resolution

After applying maintenance to module DBPCCPR, CAIRIM must be run for the new version of the code to take effect. Refer to CA Datacom/DB job BDRIM01 or CA Datacom/AD job AXRIM01.

 

To verify that the execution of CAIRIM has placed the updated DBPCCPR into effect, the CA Datacom DBUTLTY REPORT MEMORY=MVS report function can be run before and after the CAIRIM execution to compare the assembly date of DBPCCPR between the two runs. The post-CAIRIM execution should have a later assembly date.  

 

Example partial MEMORY=MVS report output:

CA DATACOM/DB SUBSYSTEM IS PRESENT

COMMON MEMORY USAGE  (NOT SVC OR MUF SPECIFIC)
  ADDRESS      SIZE  TEXT
38567000      7710  DBPCCPR  15.0   20160712 14.21  CROSS MEMORY  PC=PROD  

 

In the above example, DBPCCPR 15.0 at 20160712 14.21 is via PTF RO89818.  

Additional Information

There is no need to cycle the Datacom Multi-User (MUF). Any executing code in the old DBPCCPR continue executing in the old one but the next call is done in the new.

 

Refer to CA Datacom® Core - 15.0 section "Establishing Communication with z/OS"
https://docops.ca.com/ca-datacom/15-0/en/administrating/ca-datacom-db-database-and-system-administration/establishing-communication-with-z-os