How to access Endevor 18.1 concurrently with an older version of Endevor

Products

• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench

Issue/Introduction

The current linklist points to an older release of Endevor  libraries CSIQAUTH, CSIQAUTU and  CSQILOAD.  
The new libraries for Endevor 18.1 for (CSIQAUTH, CSIQAUTU, and  CSIQLOAD) are all APF libraries 
When executing the clist to bring up the new version (18.1) of Endevor or Quickedit, it is abending and referencing the older release. 
How can Endevor 18.1 be started for testing purposes without referencing the previous (current) release? 

Below is an example of the abend recieved when attempting to access Quickedit 18.1

BC1PINIT FAILURE, RC=7144.
ENDIE000: F000 ABEND CODE=INIT NUMBER=0001
BST PRODUCT: CA Endevor VERSION: 15.1 RELEASE: B1501C
OPERATING SYSTEM: MVS/ESA  RELEASE: SP7.2.2  TASK/JOB/USERID: VGCFJM
LOADED MODULES SUMMARY: LOAD SVCS:0000002 DELETE SVCS:0000000
  MODULE SERVICE REQUESTS: LOAD:0000002 DELETE:0000000 IDENTIFY:0000000
  PRESENT: RMODE HI:0000000 RMODE LO:0000002 HLL PGMS:0000000 IDENTIFY:0000000
  OVERALL: RMODE HI:0000000 RMODE LO:0000002 HLL PGMS:0000000 IDENTIFY:0000000
CALL FROM $FUNC=$BABEND  EPA=000A4C00 R1=000AEA40 R14=800A4EB4 STACK=000AE9E8  CSECT=BSTPMPGM  08/03/12
CALL FROM $FUNC=BSTPOPSV EPA=000A11D8 R1=000AE7D0 R14=800A126A STACK=000AE988  CSECT=BSTPOPSV  05/17/12
CALL FROM $FUNC=CALLTHRU EPA=17A24768 R1=000AE7D0 R14=97A24A16 STACK=000AE778
CALL FROM $FUNC=ENDIE000 EPA=17A24590 R1=000AD658 R14=97A2461A STACK=000AD5F8
CALL FROM PROGM=ENDIE000 ASM DT=05/17/12 VERS=0003 EPA=97A24480 RET=97A24584
ABEND U0001 OCCURRED IN PROGRAM ENDIE000
CALL FROM $FUNC=CALLTHRU EPA=17A24768 R1=000AE7D0 R14=97A24984 STACK=000AE778
CALL FROM $FUNC=ENDIE000 EPA=17A24590 R1=000AD658 R14=97A2461A STACK=000AD5F8
CALL FROM PROGM=ENDIE000 ASM DT=05/17/12 VERS=0003 EPA=97A24480 RET=97A24584

Environment

Release : 18.1

Component : CA Endevor Software Change Manager

Resolution

Endevor loads must be authorized. So this demands that they be either in the Linklist, used in a Steplib or used in a Dynamic Steplib utility(3rd party purchase).

If a site does not have a Dynamic Steplib allocation utility, 2 TSO logon PROCs must be used. One would be the standard logon proc. The Endevor loads would be in the linklist for this release.(ie v15) and the another would be a copy of the 1st TSO logon proc except pointing to the other version's libraries. The Endevor loads(ie.v18.1) would be in a STEPLIB.

** Note the IBM Utility ISPLLIB will not work as the Endevor loads are APF authorized.

Additional Information

See chapter "How to configure the installation environment"