What are the Endevor limitations with using IEBCOPY?

Products

• Endevor

Issue/Introduction

When can IEBCOPY be used to copy members from a PDS to PDSE library and when should the Endevor utilities like BSTCOPY, BSTXCOPY, and BC1PNCPY be used?

Environment

Release : All Supported Releases

Component : Endevor Software Change Manager

Resolution

IEBCOPY can be used to copy any FB or VB formatted library from PDS to PDSE such as Endevor Base, Delta, Source output libraries, or Listing libraries without compromising the Endevor Footprints.    HOWEVER,  IEBCOPY can NOT be used to convert Load libraries from PDS to PDSE.

 

IEBCOPY can also be used to copy like formatted load library -  PDS to PDS   or  PDSE to PDSE , without compromising the load modules and program objects Footprints.  

 

BSTXCOPY must be used to convert Load libraries from PDS to PDSE  because IEBCOPY will wipeout the Footprints of the program objects created in the PDSE.

 

BC1PNCPY should be used when working with ELIBs. Converting ELIBs to PDS or PDSE  or converting PDS or PDSE libraries to ELIBs. 

 

Note:   BSTCOPY is a processor utility and can only be used in an Endevor processor.

            BSTXCOPY  is an external utility program that is used in batch jobs outside of Endevor. 

 

 

IEBCOPY usage limitations  -

1)   IEBCOPY  CANNOT   be used to convert LOADLIBs from PDS to PDSE as it may truncate the footprint. Results may truncate the stage number, VVLL, time and site ID were missing.

      BSTXCOPY must be used for converting Load libraries from PDS to PDSE.

 

2)  BSTCOPY must be used  instead of IEBCOPY in a processor if Endevor Automated Configuration Manager (ACM Processor keywords  FOOTPRNT, MONITOR or BACKOUT) are used, or if package backout has been enabled for the output library. This is because Endevor cannot determine which members are changed by IEBCOPY.