Why are some datasets allocated as PDS while others as PDSE?
search cancel

Why are some datasets allocated as PDS while others as PDSE?

book

Article ID: 94856

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



I'm looking at SAMPJCL installation job DCM2ALL and noticed that some of the files are allocated as standard PDS datasets while others are being allocated as DSNTYPE=LIBRARY (PDSE).   Why are they not all PDS or LIBRARY?

Environment

Release: IPC...00200-15.1-IPC
Component:

Resolution

In previous releases of  CA Datacom there was no requirement to use PDSE (LIBRARY) datasets so users had a choice to allocate files as either PDS or PDSE. The installation JCL allocated all files as PDS by default. 

As from release 15.0 we now deliver some modules as binder library objects instead of load modules so this requires some files be in PDSE format. The installation JCL now allocates the CA Datacom files as PDSE, the SMP/E and LPA datasets are still allocated as PDS.