search cancel

Can I copy CA Datacom 15.0 installation library (CABDLOAD) to a PDS?

book

Article ID: 33292

calendar_today

Updated On:

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:  

Can I copy the CA Datacom 15.0 installation library (CABDLOAD) to a PDS?

 

When I run a IEBCOPY job to copy CA Datacom 15.0 members from the original PDSE to a PDS library, it returns the following messages:

IGW01207E BINDER DETECTED AN ERROR WHILE PROCESSING MEMBER DBPLIPR 

.  BINDER RETURN CODE = X'0000000C' REASON CODE = X'83000422'      

IGW01207E BINDER DETECTED AN ERROR WHILE PROCESSING MEMBER DBXMMPR 

.  BINDER RETURN CODE = X'0000000C' REASON CODE = X'83000422'      

 

while the related binder message is:

IEW2606S 4B39 MODULE INCORPORATES VERSION 3 PROGRAM OBJECT FEATURES AND CANNOT BE SAVED IN LOAD MODULE FORMAT.

 

Answer:

  

The modules that get the errors use features that can be exploited on a PDSE type dataset only.  So they cannot be moved/copied to a PDS.

Datacom Server 15.0 has the same requirement.

Environment

Release:
Component: DB