IEW2606S 4B39 MODULE INCORPORATES VERSION 3 PROGRAM OBJECT FEATURES when copying Endevor Product libraries to a PDS

book

Article ID: 197898

calendar_today

Updated On:

Products

CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction

After implementing Endevor R18.1, the Endevor LINKLIB is in PDSE (TYPE=LIBRARY) format.  On the system the LINKLIB is in PDS Format.   When attempting to copy the Endevor LINKLIB to a PDS the following error is issued: 


IEW2606S 4B39 MODULE INCORPORATES VERSION 3 PROGRAM OBJECT FEATURES AND CANNOT BE SAVED IN LOAD MODULE FORMAT.
IGW01207E BINDER DETECTED AN ERROR WHILE PROCESSING MEMBER ENBEWMSG.  BINDER RETURN CODE = X'0000000C' REASON CODE = X'83000422'

Is there a way around this other than creating a LINKLIB of TYPE=LIBRARY (PDSE)? 

 

 

Environment

Release : 18.1

Component : CA Endevor Software Change Manager

Resolution

As of release 18.1, Endevor load libraries CSIQLOAD and ASIQLOAD must be PDS/E. This requirement was introduced during release 18.0 by fixes RO99458 and RO99459.

The Endevor logic is written in the C programming language. The above fixes changed the C compiler and environment from SAS/C to IBM C plus IBM Language Environment. This change in the C compiler and runtime changed the executable form of our C programs from 'load module' to 'program object and introduced the requirement for the load libraries to be PDS/E instead of PDS.

If the 17.0 load libraries  was PDS/E, maybe it was the choice of whoever created it, or maybe it contained members (API programs or user exits) compiled by a compiler that produced program objects instead of load modules.

If the 18.0 library was PDS, the only possible reason is that the above fixes were not applied on top of release 18.0

The 18.1 load libraries need to be PDS/E. There is no other option.