Endevor 18.1 Upgrade Checklist
search cancel

Endevor 18.1 Upgrade Checklist


Article ID: 138502


Updated On:




Upgrade Checklist for Endevor 18.1 


Release:  18.1

Component:   Endevor  



Steps to prepare for your Endevor Upgrade

1.  Plan the implementation and testing strategies 

         a.  Build a test plan 

         b.  Prepare a back-out plan

         c.  Establish testing and installation dataset spacing requirements 

2.  Capture options and features from the old release

3.  Review the "Endevor 18.1 Release Notes" 

     - Review for any new features

     - Review any known issues with the new release 

 4.  Review the "Endevor 18.1 Installation Guide" for guidance on how to install the product  

 5.  Install the product

 6.  Test the new release of 18.1 with your own data. 

Installation Requirements Beginning with Endevor V18.1, ENUXSITE, all user exits, C1DEFLTS and all customized Endevor tables must:
• be assembled or compiled and linked with the RENT attribute. A non-reentrant program might encounter a system 0C4 ABEND
• reside in an APF-authorized load library. If one of these modules comes from a non-authorized library, a U0078 ABEND occurs.


Capture Options and features from the old release

Review tables as appropriate from the old release and make a copy of them in a PDS for safe keeping. Tables that typically need to review:

BC1TNEQU          (ESI - Security table)      
C1DEFLTS            (Site Defaults Table)
C1TAPGM            (Authorized Program Table)
C1UEXITS             (User Exit Table)
ENCOPTBL           (Optional Features Table)
ENDICNFG           (Dialog Configuration Table)
ESMTPTBL           (EMAIL notification Table)
ESYMBOLS          (Site Symbols Table)


If you cannot find your tables, run a batch job including the following DD statements:


These statements will produce a trace with top level information from the C1DEFLTS table, the options enabled in the ENCOPTBL, the symbolics in the ESYMBOLS table, etc.. 

Review any exits, API programs, skeletons, package ship modifications and/or customizations.

Review and Select New Release Features/Options

The best way to do this is to review the Endevor Release Notes. If your site is upgrading and there are releases between, it is recommended that you review all the release notes for all releases (For example - if you are upgrading from v18 to v18.1, review the release notes from 18.0.12). Decide which new features the site would like to implement and what is required to install them. It is suggested not to enable new features until you have completed your initial testing.


Note:  Removal of Some ENCOPTBL Options ENDICNFG_CONLIB and UNAUTH_DFLTS have been removed in order to protect the system, in accordance with system integrity best practices. The C1DEFLTS and ENCOPTBL tables must be reassembled and relinked before you run Endevor V18.1.


Testing New Releases with Your Data

As an alternative to using the Sample Application, you can use your existing production data for testing upgrades to new releases of Endevor. To do this, you must perform several post-installation steps to create a copy of the data on your test system. We recommend that you copy your largest and most active systems. If your site has many environments, you do not have to establish a test version of them all. However, you should use at least two mapped environments.

You can make copies of your production MCFs and Package File, and make copies of all the base, delta, and output libraries associated with the systems you select. If you are changing the names of these files on the test system, or if you need to establish a test bed on your production system, you must update Endevor with the new names.


Perform the following tasks to test new releases with your data:


Copy Your Element Catalog

Endevor incorporates an Element Catalog file to support long element names and to improve performance by reducing the volume of I/O operations. The Element Catalog file is required and only one is allowed per site. The Element Catalog is identified to Endevor through the ELMCATL field in the TYPE=MAIN section of the C1DEFLTS Table.  

Follow these steps:

1. Run job BC1JRCAT. You can find this member in the iprfx.iqual.CSIQJCL that is delivered with the product.

2. Edit the job to ensure that Step 2 references your production ELMCATL and EINDEX and that Steps 3A, 3B, and 4 references the test catalog you want to create.


Copy the Master Control Files

To test with copies of your MCFs, use member BC1JRMCF located in iiprfx.iqual.CSIQJCL. This job will REPRO your current MCF files into sequential data sets; create your new MCF, and then REPRO the old data from the sequential files into your new files.   Edit the JCL to ensure that Step 2 references the MCFs you are copying from and the remaining steps reference the test files you want to create.


 Copy the Package File

To test using a copy of your existing package file, use member BC1JRPKG from your iprfx.iqual.CSIQJCL library. This job backs up your existing data set to a sequential file, deletes and redefines the package file, and then populates the records back into the newly defined VSAM package file.

Follow these steps:

1. Create a new PDS member using only Step 3A in the JCL.

2. Submit it for execution.

3. Edit the JCL to ensure that Step 2 references your production package file and that Steps 3A and 3B through 5 references the test package file you want to create.


Update Your Endevor Table

1)  Before you can use any of your newly copied files, you must first identify them to Endevor through the C1DEFLTS table.

2)  Assemble and link all the customized Endevor tables using the SMP/E USERMOD process or using BC1JTABL job.


IMPORTANT NOTE NEW WITH ENDEVOR 18.1 - The updated Endevor tables must reside in the authorized library that was established during the installation process. Verify this information with the person who installed the product at your site.

Note: For more information about the C1DEFLTS Table, see How to Edit the Defaults Table (C1DEFLTS) in the Endevor 18.1 Documentation.


Synchronize the Element Catalog with Your MCFs

To ensure the Element Catalog that you just copied is properly referenced by the MCFs defined in your C1DEFLTS Table, you need to run job BC1JXCNM. Use member BC1JXCNM in irpfx.iqual.CSIQJCL.

First, run the job with the VALIDATE execution parameter. If the job ends with RC=0 in VALIDATE mode, the element catalog and MCFs are synchronized. However, if it returns an RC=4, ensure you are using the correct C1DEFLTS. RC=4 can indicate that a mismatch exists between the Element Catalog and the C1DEFLTS. If your C1DEFLTS is correct, run BC1JXCNM with execution parameter UPDATE to fix the error. In this mode, the program examines all the MCFs defined in the C1DEFLTS table and stamps the MCFs with the Element Catalog data set name.


Copy ACMQ Files

If your site is licensed for Automated Configuration Manager, and you specify ASCM=Y in your C1DEFLTS Table, the ACM query files, ACMROOT and ACMXREF, must be allocated. If you want to make copies of your existing ACMQ files, you can use IDCAMS to REPRO them to a sequential file (attributes FB 4096) and then REPRO them back into your test files. To allocate new files, use job BC1JACMD, and then use BC1JACML to populate them.


Copy Your Production Files

Use one of the following methods to make your production files available for testing:

 • Allocate new files (with new names) and copy your current data into them.

• If you are testing on an isolated LPAR, you can copy your current files to the test LPAR using their same names.

• Use IBM's DFDSS utility ADRDSSU to COPY (dump) and rename your data files.


 Allocate Base, Delta, and Source Processor Output Libraries

You can allocate new files (with new names) and copy your current data into them, or if you are testing on an isolated lpar you can copy your current files to the test lpar using their same names. Alternatively, you can use IBM's DFDSS utility ADRDSSU to COPY (dump) and rename your data files.


After processing the MCFs, Package, ACMROOT, XREF and Element Catalog files, you need to allocate your data files. Using IEFBR14 or IDCAMS, allocate empty PDS, PDSE, or ELIBS, based on your site's implementation. Copy any base, deltas, source output libraries, processor output, and load libraries associated with the systems and types you plan to use in your testing.


Note: You can use either of these processes – Allocate Base, Delta, and Source Processor Output Libraries or Copy Production Data. Alternatively, you can use IBM's DFDSS utility ADRDSSU to COPY (DUMP) and rename your data files.


Copy Production Data

Using IDCAMS, IEBCOPY, or BC1PNCPY, copy your production files over to the new empty test files. When a PDS load module is copied to a PDSE, CA Endevor SCM load module footprint information is retained only if the CA Endevor SCM processor utility BSTCOPY is used. Other utilities, such as IEBCOPY, do not have the capability to copy the *LOADMOD footprint. For more information, see

Techdoc- Article Id: 137047  How to convert from Endevor PDS to PDSe Libraries.

Note: You can use either of these processes – Allocate Base, Delta, and Source Processor Output Libraries or Copy Production Data. Alternatively, you can use IBM's DFDSS utility ADRDSSU to COPY (DUMP) and rename your data files.

Identify Test Libraries to CA Endevor SCM

After you have copied all your production files to new empty test files, change the data set names from their production name values to their new test name values. Update the data set names in each stage for each system imported for testing under each environment.


Follow these steps:

1. Start Endevor using the instructions provided by your site administrator. The Primary Options panel appears.   Endevor 18.1

2. Select option 4, Environment, and press Enter.  The Environment Options menu appears.

3. Select option 8, DATASET, and press Enter.  The Type Data Set Request panel appears.

4. Enter the name of the system and stage identifier you want to update, enter U in the Option field, and press Enter.  The Type Data Sets panel appears.

5. To rename a data set, type over the existing name in the DATA SET NAME column. Any error messages are displayed under the MSG column. Press F1 to get more information about an error message, or see Messages and Codes.

6. Repeat these steps for both stages of each environment, for each system you copied.


Note: If you decide not to use your production data files for testing, you have the option of starting from scratch. To do this you need to create all new files, and run Batch Admin (ENBE1000) to build your new environment. For more information about the Batch Admin Utility, see Execute or Validate Batch Admin SCL.


Test the New Release

After you have updated all your systems and stages, you are ready to test. Be certain to test your exits, making sure that you reassemble and relink them first.