BDNEW02 job getting File Not Found JCL error in step ADRPNLBU.

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

Question: 

While running CA Datacom/DB installation job BDNEW02, I received a JCL error and this message in step ADRPNLBU:

IEF212I BDNEW02 ADRPNLBU STEP2 VLSFILE - DATA SET NOT FOUND  

This is a new installation, and I must have missed something – where does this file come from?

Answer: 

The ADRPNL VLS file that you have as "Not Found" in this BDNEW02 job is originally created in the CA IPC installation, through job VQNEW02 (version 14.0) or job VQNEW01 (version 15.0). This job is responsible for creating the ADRPNL, ADROUT, ADRLIB and ADRTRC files, so if you have a “File Not Found” error on any of these, this is the job to check. Since you should have completed the CA IPC installation first, you should check the VQNEW* job to see what filename you used there, and then use that filename as noted in this BDNEW02 flowerbox instruction #4 (version 14.0) or #10 (version 15.0):

   PERFORM A GLOBAL CHANGE OF "CAI.VHLQ"
    TO THE HIGH LEVEL QUALIFIER OF THE VLS DATASETS.

As always, please contact CA Technologies support for CA Datacom if you have further questions.

 

***

Environment

Release:
Component: DB