Upgrading from V2.1

The following steps describe how to upgrade from CICS® Configuration Manager V2.1 to V5.1.

Print and fill in the table presented in Information you will need for installation, then print this topic and follow the instructions carefully. After performing each step, write a checkmark next to the step number to mark it as complete.

You can continue to use your existing CICS Configuration Manager V2.1 repository and journal with V5.1. However, the CICS Configuration Manager server, clients, and agents must be at the same version: you must perform the following steps to upgrade them together. For example, you cannot use the ISPF dialog interface supplied with V2.1 to connect to a V5.1 server.

  1. Apply the PTF for APAR PM74451 (V5.1 "toleration") to CICS Configuration Manager V2.1.

    CICS Configuration Manager V5.1 introduces changes to the CICS Configuration Manager repository and journal records. Without this PTF, CICS Configuration Manager V2.1 is not aware of these changes. Applying the PTF enables you to revert to CICS Configuration Manager V2.1 after you have used the repository with V5.1.

    While it is strongly recommended that you install this PTF to V2.1 now, before using V5.1, this PTF is required only if you revert to CICS Configuration Manager V2.1 using a CICS Configuration Manager repository or journal that has been updated by V5.1. In that case, you must apply the PTF to V2.1 before reverting to V2.1.

  2. Stop the CICS region that runs the CICS Configuration Manager server, if it is not already stopped.
  3. Edit the startup job for the CICS region that runs the CICS Configuration Manager server, and change the CICS library concatenation DFHRPL to refer to the CICS Configuration Manager V5.1 product library high-level qualifier:
    //DFHRPL   …
               DD DSN=ccvhlq.SCCVLINK,DISP=SHR
               DD DSN=ccvhlq.SCCVAlang,DISP=SHR
  4. Edit and submit the JCL in the following members of the V5.1 sample library SCCVSAMP:
    • CCVXBTS
    • CCVXWORK

    These delete and re-define work files for the CICS Configuration Manager server.

  5. Edit the V5.1 sample member CCVXCSDD.

    This member contains the resource definitions for group CCV510 required by the CICS Configuration Manager V5.1 server.

    Edit the DSNAME attributes for the following file resource definitions in CCVXCSDD to refer to the data set names of your existing CICS Configuration Manager V2.1 repository and journal:

    • CCVDDD (repository file)
    • CCVJNL, CCVPT1, CCVPT2 (journal files)
    Tip: To find out the existing data set names, look at the corresponding file resource definitions in the existing group CCV210 in the CICS Configuration Manager server CSD file, or the version of the CCVXCSDD member that you edited when installing V2.1.
  6. Edit and submit the V5.1 sample member CCVXDUP. In addition to editing the <label> placeholders, "uncomment" (remove the asterisk from) the REM commands near the bottom of the member. Expect return code 4 from this job.

    This job creates the group CCV510 in the CICS Configuration Manager server CSD file, adds that group to the startup list, and removes from the startup list the corresponding groups for previous releases of CICS Configuration Manager.

    Replace the <SVRLIST> placeholder in CCVXDUP with one of the lists specified by the group list used at CICS startup.

  7. If necessary, update the value of the SIT parameter CSDLSRNO.

    Previous releases of CICS Configuration Manager required you to specify CSDLSRNO=NONE.

    In CICS Configuration Manager V5.1, the values of CSDLSRNO that you can specify depend on the release of CICS Transaction Server that runs the CICS Configuration Manager server region:

    • V3.2, or earlier: you can specify any value allowed by CSDLSRNO
    • From V4.1: you can specify any value allowed by CSDLSRNO, with the following exception: if you specify the SIT parameter TRANISO=YES, then you cannot specify CSDLSRNO=NONE
  8. Start the CICS Configuration Manager server:
    1. Perform a cold start or an initial start of the CICS region that runs the CICS Configuration Manager server.
    2. If the program CCVIINIT is not in the PLTPI, then run CCVIINIT now to start the CICS Configuration Manager server.
      Tip: To run program CCVIINIT, invoke the CICS Configuration Manager transaction CCVI on the CICS command line.
  9. If you previously APF-authorized the CICS Configuration Manager V2.1 product libraries SCCVAUTH and SCCVlang, then APF-authorize the equivalent V5.1 libraries. Place the V5.1 libraries in the APF-authorized list.

    If you copied the V2.1 members from SCCVAUTH and SCCVlang to your own APF-authorized libraries:

    1. Backup the V2.1 CCV* members (so that you can restore them if you decide later to revert to V2.1)
    2. Copy the V5.1 CCV* members from SCCVAUTH and SCCVlang to your own APF-authorized libraries
    Note:
    • The V5.1 CCVSCRPT member of the SCCVAUTH library is the program that creates PassTickets for the CICS Configuration Manager ISPF client. The V5.1 CCVSCRPT member is compatible with both the V2.1 and V5.1 ISPF clients.

      While the V2.1 and V5.1 CCVSCRPT members are functionally equivalent, it is recommended that you implement the V5.1 member.

    • The CCVBMAIN (batch client interface program) and CCVBHKP (batch housekeeping program) members of the SCCVAUTH library are version-specific: the version of the program must match the version of the CICS Configuration Manager server that the program connects to. You cannot, for example, use the V5.1 programs to connect to a V2.1 server.
  10. Update the command that you use to invoke the CICS Configuration Manager ISPF dialog interface program CCVOREXX: replace the high-level qualifier of the CICS Configuration Manager V2.1 product library with the V5.1 high-level qualifier.
  11. Update any JCL that you have created to call the CICS Configuration Manager batch client interface program CCVBMAIN or the batch housekeeping program CCVBHKP: replace the high-level qualifier of the CICS Configuration Manager V2.1 product library with the V5.1 high-level qualifier.
  12. If your installation uses the CICS Configuration Manager agent, then in each of the remote regions running the CICS Configuration Manager agent:
    1. Ensure that the resources listed in V5.1 sample member CCVXCSDR are defined in an appropriate group and installed in the remote region.
      Note: The program CCVSXCSD attribute EXECKEY has been changed to USER in V5.1.
    2. Ensure that the CICS library concatenation DFHRPL refers to the CICS Configuration Manager V5.1 product library.
    3. Replace the programs listed in CCVXCSDR. Either:
      • Restart the region

        or

      • Use the CEMT transaction supplied with CICS Transaction Server for z/OS® to perform a newcopy of the programs. For example:
        CEMT SET PROGRAM(CCV*) NEWCOPY

      You cannot use CICS Configuration Manager to perform this particular newcopy, because you cannot use a CICS Configuration Manager V5.1 server to communicate with a region running the V2.1 agent.


Information Information

Feedback


Timestamp icon Last updated: Friday, 1 November 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic//ccv-install-upgrade-prev.htm