Running 2 releases of Endevor Concurrently


Article ID: 125317


Updated On:


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)


I am upgrading Endevor v17 to Endevor V18.0.12 and I would like to test and run them concurrently.  Can I do this and how? 


Component: ENDBAS


Concurrent Release Considerations 
In many cases, it is necessary to run two different releases of CA Endevor SCM at the same time. You can do this by adding your CSIQAUTH/CSIQAUTU and CSIQLOAD data sets to the respective STEPLIB and CONLIB statements in a test TSO logon procedure. Member [email protected] in the CSIQSENU and CSIQJCL installation libraries were tailored by BC1JJB03 of the installation process to point to your STEPLIB/CONLIB concatenations. The Skeleton JCL members installed imbed CSIQJCL member [email protected] to point to your STEPLIB/CONLIB concatenations. Stand-alone JCL members include CSIQJCL member [email protected] for your STEPLIB/CONLIB concatenations. The CSIQJCL member [email protected] 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. 

You cannot access both releases in the same TSO/ISPF session. After working with one release, before you can work with the other, log off TSO and log on again, making sure to change the logon procedures. If you do not change your logon procedures, a message indicates an incompatible C1DEFLTS Table. 

ISP Command Table Considerations 
CA Endevor SCM 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, CA ACF2 has a facility named TSO Command Limiting, which may need modification. 

It is strongly reccommended that you test using your own data. For more information on how to do this please review the docops link below: