How do I upgrade and convert from Endevor 3.9 to Endevor v16?
search cancel

How do I upgrade and convert from Endevor 3.9 to Endevor v16?

book

Article ID: 20004

calendar_today

Updated On:

Products

Bind Analyzer for DB2 for z/OS SQL-Ease for DB2 for z/OS SYSVIEW Performance Management Option for DB2 for z/OS Plan Analyzer for DB2 for z/OS Subsystem Analyzer for DB2 for z/OS PanAudit Plus Easytrieve Report Generator PAN/SQL Endevor Endevor Natural Integration Endevor - ECLIPSE Plugin Endevor - Enterprise Workbench CA 2E

Issue/Introduction

Description:

Based on client suggestions, we have developed this cross reference guide to facilitate your installation/upgrade from Endevor 3.9 to v16.

Solution:

Based on client suggstions, we have developed a cross reference guide to facilitate you installation/upgrade from Endevor 3.9 to Endevor v16.

!!!!!! IMPORTANT NOTE !!!!!!
DO NOT SHARE MCFs between release 3.9 or any other release of Endevor.
Any updates, performed under another release will cause your element catalog to be out of sync!!!

Part 1:

Steps intended to be executed by the site Systems Programmer.

Download and install CA Endevor v16 SCM from support.ca.com. Review the Install Guide Chapters 1 & 2.

Part 2:

Steps intded to be executed by the site Endevor Administrator.

Section 2a: Implement a new release Test Environment

Step to be completed: Reference Manual - Section

  1. Review the Overview V16 Installation Guide - Chapter 1
  2. Read "Testing New Release with Your Data" v16 Installation Guide - Chapter 7
  3. Optionally implement the Sample Application v16 Installation Guide - Chapter 6
  4. Review the Release Summary v16 Release Notes


SECTION 2B: Migrate your Existing Environments

Step to Be Completed Reference Manual - Section
1. Define the new Element Catalog and Catalog Index files. Sample job BC1JJB07 is located in the CSIQJCL library, delivered with v16. ADMIN Guide - Appendix B
2. Allocate new and copy R3.9 MCFs and Package files forv16 use. (Sample Jobs BC1JXMCF & BC1JXPCF in CSIQJCL lib) ADMIN Guide - Appendix B
3. Consider defining/using the Site Defined Symbolics Table. (Sample table ESYMBOLS in CSIQSRC) ADMIN Guide - Chapter 7
4. Create a new version of your C1DEFLTS Defaults table. (Do not activate security yet. ESSI=NO) (Sample table C1DEFLTS in CSIQSRC) See table/notes below: User Tables Parameter Changes ADMIN Guide - Chapter 13
5. Create a new version of your ENDICNFG ISPF Options table. (Sample table ENDICNFG in CSIQSRC) See table/notes below: User Tables Parameter Changes ADMIN Guide - Chapter 12
6. Create a new version of your ENCOPTBL Optional Features table. Review the new options in member. (Sample table ENCOPTBL in CSIQSRC. Review the member for new options available) ADMIN Guide - Chapter 6
7. Create a new version of your BC1TNEQU security table. (Sample table ENDICNFG in CSIQSRC) See table/notes below: User Tables Parameter Changes Security Guide - Chapter 6
8. Allocate ACMQ files for new release usage. - Existing users should copy their existing ACM files into new datasets. (Sample Job BC1JACMD in CSIQJCL lib to define and then IDCAMS/REPRO data from current) - New ACMQ users MUST allocate the files via the BC1JACMD job prior to loading the element catalog. Once the catalog is loaded, new users can populate the ACMQ files via the BC1JACML job. (Sample Jobs BC1JACMD & BC1JACML in CSIQJCL lib) - New ACMQ users MUST also include the ASCM, ACMROOT & ACMXREF entries in their C1DEFLTS table. ACM Guide - Chapter 2 Installation Guide - Chapter 8
9. Create and Load data into the Element Catalog Files. (Sample job BC1JXCNV in CSIQJCL lib) ADMIN Guide - Appendix B
10. Recompile all tables create above using the new release macro library (CSIQOPTN lib)(Sample job BC1JTABL in CSIQJCL lib) ADMIN Guide -
11. Recompile any exits and API programs created at your site. Using the new release macro lib. ADMIN & API Guides
12. Optionally copy your existing Base/Delta/Source Output and Processor Libraries to new datasets and change the system definitions that use these libraries to point to the new naming. (need something for testing validations before go-live) Installation Guide - Chapter 4
13. Logon to TSO using a Logon Proc with Endevor Steplibs. Execute updated ENDEVOR clist. Unless separate LPAR is used and Linklist can be used for the v16 libraries.  
14. Foreground validation of user table modifications (C1DEFLTS, ENCOPTBL, ESYMBOLS, ESMTPTBL, BC1TNEQU, ENDICNFG & C1UEXITS) - Allocate file EN$TROPT under TSO: TSO ALLOC FI (EN$TROPT) SYSOUT REUSE
  • Bring Endevor up in foreground
  • Split screen & look at trace file under you TSO session in Sysview DA queue
  • Confirm all selected options & table settings are correct
 
15. Batch Validation of user table modifications (C1DEFLTS, ENCOPTBL, ESYMBOLS, ESMTPTBL, BC1TNEQU, ENDICNFG, & C1UEXITS) - Submit an Endevor Batch job with the additional DD statements: //EN$TROPT DD SYSOUT=* //BSTERR DD SYSOUT=* After the job completes view output in SYSVIEW and do the same validation you did for foreground.  
16. If applicable, enable security in the C1DEFLTS table and reassemble. ACCSTBL & ESSI Defaults Table parms. Reassemble your existing security table BC1TNEQU using the v16 macros.  
17. Update the new release Endevor panels that were modified at your site for R3.9 (if still allowed). Remember that once you have customized a panel you are own it. CA is not responsible for fixing them.  
18. Unload/Reload and Reorg jobs. Verify LRECL.  
19. Update JCL to reference new release libraries as required.  
20. Execute Test/Validation plan  
21. Review/Update your Endevor related config/user/process documentation as needed.  
22. Execute Training plan  
23. Execute GO-LIVE plan  

Environment

Release:
Component: C21E
Powered by Wolken Software