Upgrade ADRPNL and ADRLIB VLS file

Products

• Ideal
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• 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

Which ADRPNL and ADRLIB VLS files to update in a CICS region when upgrading CA Datacom/DB, CA IPC, CA Ideal (or CA Datacom/AD and CA IPC when using CA Ideal for DB2)?

Environment

z/OS

Resolution

Upgrade of the VLS files ADRPNL and ADRLIB can be a bit tricky. 

When a site is using CA Ideal, the ADRPNL and ADRLIB are updated with the upgrades of multiple products:
CA Datacom/DB, CA IPC, and CA Ideal (or CA Datacom/AD, CA IPC, and CA Ideal for DB2).

It is usually recommended that CA Datacom/DB (or CA Datacom/DB when using CA Ideal for DB2) product is upgraded first followed by CA IPC and CA Ideal for each of the CICS environments.

Regardless of the order of the product upgrades, each product upgrade should update whatever the existing ADRPNL and ADRLIB are in the CICS region at the time of that product's upgrade.
So, the upgrade JCL for each product should correctly specify the current (sometimes referred to as "previous") VLS files in the CICS region to carry forward. 

Additional Information

Refer to each of the product's installation documentation for details.