COPE supports all IBM supported releases of IMS, Db2, and CICS. Typically, COPE is upgraded before IMS or CICS is upgraded. The following set of instructions describes how to change an IMS release, a CICS release or IMS release for a COPE system so that minimum disruption occurs to the COPE testing environment.

This section provides information about the following topics:

IMS Upgrade Procedures

Assumptions

It is assumed that the new IMS release is available in a set of datasets that have different names from the datasets used by the COPE environment. These datasets will be renamed to the COPE IMS dataset names when the upgrade has been completed.

The following table provides a checklist for the IMS release upgrade.

Task 7.1  Update EVARS (EVARS)

1. Access the COPE main menu.
2. Type EVARS on the command line.
3. Press Enter.

The EVARS command takes you into ISFP  EDIT.

EVARS Command

      4. Make a copy for backup purposes of the PDS member.
Create Backup Copy

       5. Change the following variables in the EVARS to match the new IMS dataset names:

• 
  
  • XCOPEIRS
  • XCOPEMAC
  • XIMSCLST
  • XIMSEXEC
  • XIMSMLIB
  • XIMSPLIB
  • XIMSTLIB
  • XCOPEDYN
  • XCOPEAUT
  • XCDBDMAC

      6. Press PF3 (END) to save your changes.

Task 7.2  Perform a Parallel ACBGEN (4.ACB;PAR)

When a new IMS release is installed, a ACBGEN BUILD PSB=ALL must be performed. COPE has a feature that can speed up the process (which can take days) by generating up to 9 jobs that can execute in parallel. When the jobs have completed, a tenth job can be released to combine the output from the previous job into an ACBLIB.

1. Use option 4.ACB;PAR to generate JCL.
   Access Option 4.ACB; PAR
   
2. Set the Number of Jobs to 9.
   Set Number of Jobs
   
3. Modify the generated JCL to use the new IMS RESLIB (SDFSRESL) and also to use a new set of ACBLIBs in the final combination step.
4. Submit the set of jobs. Wait for all the preparation jobs to complete and then release the final combination job to create a new set of ACBLIBS.

Task 7.3  Perform an ALL Stage 1 Generation

1. Select option 4.1E from the main menu.
   Select Option4.1E

   
   
   

2. Update IMSCTRL macro specifying ALL as shown below.
   Update IMSCTRL Macro
   
   
3. Verify the created JCL points to the IMS macro library for the new release.
   IMS Macro Library
   
4. Submit and run the IMS STAGE1 ALL SYSGEN.

Task 7.4  Perform Stage 2 Generation

1. Select option 4.2 from the main menu.
   Select Option 4.2
   
2. Verify/update the dataset names to point to the new IMS release.
   Verify SYSLIB Dataset Names
   
   
3. Submit and run STAGE2.

Task 7.5  Define Lsys Identifying Tokens (Relink-edit IMS Modules) (Option 1.6)

1. Copy module COPEPSYS from the old IMS RESLIB to the new IMS RESLIB.
2. Select option 1.6 from the main menu to access the conversion JCL COPE option.
   Select Option 1.6
   
3. Use the G (Specify Lsys tokens and generate assembly job) option to generate JCL to relink-edit IMS modules.
4. Press Enter.
   Select Option G
   
   
5. Press Enter to continue.
   Processing Message Display
   
   
6. Press PF3 (END) on the Physical system defin"tns - Table Data Panel.

Press PF3 (END)

      7. Press Enter on the PROCESSING MESSAGE DISPLAY.     

           Processing Message Display

       8. On the PGMRNAME field value - Table Data Panel, you will see the same tokens defined.

            PGMRNAME Field Value

9. Press PF3 (END) to generate a job that will recreate the COPEPSYS module and relink-edit DFSRRC00 with a COPERCFE 'front end' and copy a COPERCXL module into the new RESLIB.

          10. Press Enter.

                Processing Message Display

         11. Change the RESLIB name to the new RESLIB name.
              Processing Message Display

            12. Delete steps that relink-edit IMS utilities that are not part of IMS. (The generated job link-edits OEM software in addition to IMS modules).

            13. Review the generated JCL and submit the job.

This JCL copies authorized modules to the new IMS RESLIB.

1. Make a copy of the dataset(s) pointed to by the EVARS values COPEDYN and COPEAUT libraries using the new dataset names.

            EVARS Command

         FIND XCOPEDYN

           Update XCOPEDYN

           FIND XCOPEAUT

            Update XCOPEAUT

             2. Change the JCL to reflect these new dataset names.
                AUTHCOPY JCL
          

               3. Run the update AUTHCOPY JCL. Expected return code is 0

Task 7.7  Update IMS Exits

The COPE AOI exit, DFSAOUE0 and DFSAOE00 must be placed in the IMS RESLIB (SDFSRESL) by the COPEEXIT job. If MAINVIEW is present, use the COPEMAIN JCL instead and follow the instructions in the comments to configure MAINVIEW.

These jobs copy the exits to the IMS RESLIB and also Batch JCL for a AOI started job (COPEAOI) and a job that can issue commands to COPE (COPEBCMD).

COPEEXIT JCL

To convert the COPE IMS system from the previous release, rename the IMS system datasets to the set of names that were used previously. This will involve terminating the IMS system and renaming the datasets it used to temporary names and replacing them with the new system datasets.

Task 7.9  Update EVARS

Update the EVARS values to match the datasets for the updated system.

Db2 Upgrade Procedures

COPE supports all supported releases of Db2.

The following are the COPE requirements when upgrading Db2 versions or putting maintenance on Db2 in an existing COPE environment:

Task 8.1  Update EVARS

Task 8.1.1  Evaluate EVARS Values

The following EVARS values may need to be updated:

• XDB2LOC
• XCOPDB2N
• XCOPDB2P
• XCOPDB2M
• XDB2PASS
• XCOPEDB2
• XCOPDB2E
• XCOPDB2R
• XSCHEMA
• XOWNER

Task 8.1.2  Implement Updated EVARS

If any EVARS values are updated, go to the COPE Main ISPF menu option 1.10. Submit and run the  generated job.

Task 8.2  Db2 Binds

If the Db2 changes being implemented require Db2 BINDS to be done, the following are required for COPE:

Task 8.2.1  Specify Packages for all Logical Systems - DCCTL and DCCTL with XDCCTL=YED Only

From the ISPF COPE main menu, go to option 4.PACK. Go through each sub-option.

Task 8.2.2  Bind COPE Db2 Plans

From the ISPF COPE main menu, go to option 1.9 Bind COPE DB2 Plans. This job binds and grants authority on COPE Db2 objects. Modify the job as appropriate. Submit and run it.

CICS Upgrade

COPE supports all supported releases of CICS.

The following are the tasks required in COPE when CICS is upgraded in an existing COPE Environment:

Task 9.1  Backup

Backup the following COPE runtime libraries:

• xcope1.JCL
• xcope2.JCL
• xcope1.LOAD
• xcope2.LOAD

The values for xcope1 and xcope2 can be determined by the following:

1. Go to the COPE main ISPF screen, type EVARS on the command line, and press Enter.

• • EVARS Command

      2. Enter F ‘set xcope1’ on the command line and press Enter as shown below.
          Find ‘set xcope1’

   3. Note the values for XCOPE1 and XCOPE2 as shown below.
       XCOPE1 and XCOPE2’

Task 9.2  Assemble and Link COPEPRE, COPEPOST, and COPEREFR

1. Edit COPEx.JCL member CICSCOMP.
2. Change the DSNs to point to the correct CICS SDFHMAC and SDFHLOAD datasets.
   Member CICSCOMP may exist in the xcope1.JCL and xcope2.JCL libraries. It should be updated in the xcope1.JCL library, so if it is not there, copy it there from the xcope2.JCL library.
3. Submit the updated CICSCOMP job.

Task 9.3  Copy COPEPRE, COPEPOST, and COPEREFR (Optional)

If the xcope1.LOAD dataset is not in the CICS DFHRPL concatenation, copy the modules COPEPRE, COPEPOST and COPEREFR from the xcope1.LOAD dataset into a library in the CICS DFHRPL concatenation.

Task 9.4  CICS PLT Startup (PLTPI) Definitions

For CICS Transaction Server for z/OS releases prior to V5.5, do the following:

1. Copy member DFHPLT1 from the xcope1.JCL library to the xcope2.JCL library.
2. Modify member DFHPLT1 according to the comments in the job in the xcope2.JCL library.
3. Submit the modified DFHPLT1 member.

Most installations will have an existing PLT defined. Add a new specification for the COPEREFR program to execute in the third phase of the PLT initialization.

For CICS Transaction Server for z/OS releases V5.5 and more current, CICS reads PLTs directly from source and no longer need to be Assembled. It must be available to CICS at run time, including any COPY members it referenced. For this, either place the source in a PARMLIB member that is part of the IPL PARMLIB concatenation, or add the following DD card DFHTABLE into the CICS startup JCL that points to the PLT source:     

The following steps are needed for CICS Transaction Server for z/OS V5.5 and more current to accommodate this:

1. Ensure COPE PTF IMA098A is installed.
2. Copy member IMPLTSRC from the xcope1.JCL library to the xcope2.JCL library.
3. Modify member IMPLTSRC according to the comments in the xcope2.JCL library.
4. Rename IMPLTSRC to DFHPLTxx and point your DFHTABLE DD to it in the CICS region JCL.

Most installations will have an existing PLT defined. Add a new specification for the COPEREFR program.

Task 9.5  Recycle CICS

Recycle CICS to pick up the updated COPE modules.

Db2 Maintenance

Task 10.1  Db2 Bind

If the Db2 upgrade required re-binding, do the following (Option 1.9 - Optional, DB/TM and DBCTL only):

1. Select option 1.9 (Bind COPE DB2 Plans).
2. Submit the created job, which binds the COPE DB2 plans.
3. Submit the generated job.

Task 10.2  Db2 Bind

If the Db2 upgrade required re-binding, do the following (Option 1.9 - DCCTL and DCCTL with XDCCTL=YED only):

1. Select option 4.PACK (Specify Packages for all Logical Systems).

2. Select option 2 (Foreground Generate COPE Package Path Table).

   Warning

   Note

   This job requires Db2 bind authority. The plan name in the TSO GRANT step is generated using the Db2 version number, and should be changed if there is a user modification in place for this.

COPE Maintenance

Before applying SMP/E maintenance to COPE, we recommend doing the following:

1. Copy member IMMNTCMP from the xcope1.JCL library to the xcope2.JCL library.
2. Modify member IMMNTCMP according to the comments in the job as appropriate in the xcope2.JCL library.
3. Submit the modified IMMNTCMP member. This will compare the SMP/E target libraries to the current COPE runtime libraries to see if there are any differences. Analyze any differences to determine the correct course of action needed after the COPE maintenance is implemented updating the runtime libraries.

When maintenance is applied to COPE the SMP/E Target libraries are updated. These libraries need to be copied to the COPE running system libraries.

Task 11.1  Copy Updated Libraries

The following are the steps to copy the updated libraries.

1. Back up COPE runtime libraries.
2. Copy member IMMNTCPY from the xcope1.JCL library to the xcope2.JCL library.
3. Skip step a & b below unless your xcope1.CLIST dataset is of Variable Blocked (VB) format. Modify member IMMNTCPY according to the comments in the job as appropriate in the xcope2.JCL library. 
   1. Comment out the following steps in IMMNTCPY:
      //FILE01Z EXEC MCOPY,I=&COPEHLQ..CLIST,
      //     O=&COPEHLQ..CLIST
      //FILE01C EXEC MCOPY,I=&TZHLQ..SVIMCLST,
      //     O=&COPEHLQ..CLIST
      
      
   2. Using ISPF option 3.3, copy &TZHLQ..SVIMCLST to xcope1.CLIST, replacing the members in xcope1.CLIST.
4. Submit modified member IMMNTCPY. This job will compress the COPE xcope1.xxx runtime libraries and copy the SMP/E target libraries to the COPE runtime libraries.
5. Bring down the IMS control region.
6. If PTF IMA127A is applied skip this step. If PTF IMA127A is not applied go to the COPE ISPF Development System menu, select option 1.3, and update the job card as appropriate.
7. Start the IMS control region.
8. Perform COPE testing as appropriate. Prior to upgrading COPE maintenance ensure the tests work before the upgrade as well as after the upgrade is complete.

COPE has modules in the IMS RESLIB (SDFSRESL) dataset. It is possible IMS maintenance may affect these modules.

Task 12.1  Update COPE Modules

If IMS SYSGEN is required or is part of your normal IMS maintenance process, then perform the following steps:

1. Go to COPE Main ISPF panel Option 4.1E and change the IMSCTRL macro to specify ALL as:
   • IMSCTRL SYSTEM=(VS/2,(ALL,DB/DC),390),IRLM=YES,               *     
2. Press PF3.
3. Submit and run the jobs created.
4. From the COPE Main ISPF panel, go to option 4.2 and submit the job created (IMS stage2) .

After completion of above steps, do the following when IMS maintenance is implemented:

1. From the COPE main ISPF menu, use option 1.6 (Define Lsys Identifying Tokens (Relink-edit IMS Modules), and then enter G, follow the instructions, and run the created job.

   Warning

   In IMS DB/TM or IMS DBCTL environment, prior to running this job, copy module DFSCDLI0 from a non-COPE IMS RESLIB into the COPE IMS RESLIB so the link-edit will pick up the latest version from IMS. If this is not done, the link-edit for DFSCDLI0 may not work correctly.  

   NOTE: This is required only if DFSCDLI0 has been updated by the IMS Maintenance.

2. Run the AUTHCOPY (DB/TM or DCCTL) or AUTHDBCT (DBCTL only)  job in the xcope2.JCL dataset.
3.  Update IMS Exits. The COPE AOI exit, DFSAOUE0 and DFSAOE00 must be placed in the IMS RESLIB (SDFSRESL) by the COPEEXIT job. If MAINVIEW is present, use the COPEMAIN JCL instead. Follow the instructions in the comments of these jobs. The COPEEXIT and MAINVIEW jobs are located in the xcope2.JCL dataset.

CICS Maintenance

Task 13.1  Update CICS Modules

Do the following when CICS maintenance is implemented:

1. Reassemble COPEPRE and COPEPOST Exits and COPEREFR PLT Program (DBCTL - Optional for DB/TM).
   Every version of CICS has different offsets of some of the internal control blocks. As a result, all exits must be recompiled from the provided source. Member CICSCOMP is provided in the COPE installation JCL library that will reassemble these modules.
2. Copy member CICSCOMP from the xcope1.JCL library to the xcope2.JCL library.

IMS Tools Maintenance

Do the following when maintenance on IMS Tools is implemented:

1. From the COPE ISPF main menu, use option 1.6 (Define Lsys Identifying Tokens (Relink-edit IMS Modules), and then enter G, follow the instructions, and then run the created job. The expected return code is 4.

2.  Submit the job.

   Warning

   Note

   If the xcope1.LOAD dataset is not in the CICS DFHRPL concatenation, copy the modules COPEPRE, COPEPOST, and COPEREFR from the xcope1.LOAD dataset into a library in the CICS DFHRPL concatenation.