Endevor Package Ship PDS to PDSE conversion for COBOL v6.3 upgrade

Products

• Endevor

Issue/Introduction

Upgrading COBOL from v4.2 to COBOL v6.3.  As a pre-requisite for COBOL v6.3 implementation, all libraries holding the load modules are required to convert from PDS to PDSE.

• Is there a formal/standard procedure to convert the Endevor system-level PDS to PDSE libraries?
• Also what is the impact on Package Ship - are Endevor skeleton changes required?

Environment

 All supported Releases 

Endevor 

Cobol 6.3 

Resolution

BSTXCOPY is the recommended Endevor utility to copy COBOL load libraries from PDS to PDSE for the COBOL upgrade.  BSTXCOPY provides the same functions as BSTCOPY (including retaining footprint information) but can be executed outside of an Endevor processor.

• Related KB articles:
  Converting Endevor Load Libraries from PDS to PDSE
  How to locate load libraries used within Endevor Processors to convert to PDSE format

Package Ship
Package Ship will copy the components from the load PDS/PDSE library to a flat file using BSTCOPY. The AHnnnn files are flat files.  Then the flat file is sent to the remote LPAR and the Components are copied from the flat file to the output component libraries (PDS or PDSE).

If the components (LOADLIB or OBJECT) are PDSE the remote libraries should also be PDSE.  No skeleton changes are required for a PDS to PDSE conversion.

So, in summary for the change to COBOL v6.3, along with changing PDS to PDSE for LOADLIB and OBJECT the same needs to be done for the remote libraries using BSTXCOPY.