How to Run 2 releases of Endevor Concurrently

Products

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

Issue/Introduction

How to test and run 2 Endevor versions concurrently, when upgrading.

Environment

All supported Releases 

Resolution

Concurrent Release Considerations 
In many cases, it is necessary to run two different releases of Endevor at the same time.

To do this, 

• Add the CSIQAUTH/CSIQAUTU and CSIQLOAD data sets to the respective STEPLIB and CONLIB statements in a test TSO logon procedure
• For any jobs submitted via Endevor panels, from CSIQJCL or Stand-alone JCL, review the following points:
  • Ensure member SCMM@LIB in the CSIQSENU and CSIQJCL installation libraries that were tailored by BC1JJB03 during the installation process to point to your STEPLIB/CONLIB concatenations
  • Review any JCL for in-stream STEPLIB/CONLIB to ensure they reflect the proper CSIQAUTH/CSIQAUTU and CSIQLOAD
  • The CSIQJCL member SCMM@LIB can be copied to a JES PROCLIB or a JCLLIB statement can be added to each stand-alone JCL member to point to the library where this member resides. 

Remember - Both releases can not be run in the same TSO/ISPF session.
After working with one release, before working with the other, log off TSO and log on again, making sure to change the logon procedures.
When using the same logon procedures, a message indicates an incompatible C1DEFLTS Table. 

ISP Command Table Considerations 
Endevor uses an ISP Command table (allocated under the ISPTLIB DD) for some commands (such as ESORT, EONLY, EPRINT, ACMQ, BC1PACMI, EMSGS, and so on).
However, unless this facility is specifically enabled, it may be prevented from working by your site's security package. For example, ACF2 has a facility named TSO Command Limiting, which may need modification. 

It is strongly recommended that you test using your own data. For more information on how to do this please review the link below: 
Testing New Releases with Your Data