Upgrading from V5.2
Upgrading CICS® Configuration Manager involves upgrading the product itself, and then updating various items that refer to the product.
Upgrading CICS Configuration Manager
The following steps describe how to upgrade from CICS Configuration Manager V5.2 to V5.3.
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 check mark next to the step number to mark it as complete.
You can continue to use your existing CICS Configuration Manager V5.2 repository and journal with V5.3. 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 V5.2 to connect to a V5.3 server.
- Apply the PTF for APAR PI47700 (V5.3
"toleration") to CICS Configuration
Manager
V5.2.
CICS Configuration Manager V5.3 introduces changes to the CICS Configuration Manager repository and journal records. Without this PTF, CICS Configuration Manager V5.2 is not aware of these changes. Applying the PTF enables you to revert to CICS Configuration Manager V5.2 after you have used the repository with V5.3.
While it is strongly recommended that you install this PTF to V5.2 now, before using V5.3, this PTF is required only if you revert to CICS Configuration Manager V5.2 using a CICS Configuration Manager repository or journal that has been updated by V5.3. In that case, you must apply the PTF to V5.2 before reverting to V5.2.
- Stop the CICS region that runs the CICS Configuration Manager server, if it is not already stopped.
- 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.3 product library
high-level qualifier:
//DFHRPL … DD DSN=ccvhlq.SCCVLINK,DISP=SHR DD DSN=ccvhlq.SCCVAlang,DISP=SHR
- Edit the V5.3 member CCVXCSDD of
the sample library SCCVSAMP.
This member contains the resource definitions for group CCV530 required by the CICS Configuration Manager V5.3 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 V5.2 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 CCV520 in the CICS Configuration Manager server CSD file, or the version of the CCVXCSDD member that you edited when installing V5.2. - Edit and submit the V5.3 member CCVXDUP of
the sample library SCCVSAMP. 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 CCV530 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.
- Start the CICS Configuration
Manager server:
- Perform a cold start or an initial start of the CICS region that runs the CICS Configuration Manager server.
- 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.
- If your installation uses the CICS Configuration
Manager agent, then in
each of the remote regions running the CICS Configuration
Manager agent:
- Ensure that the resources listed in V5.3 sample member CCVXCSDR are defined in an appropriate group and installed in the remote region.
- Ensure that the CICS library concatenation DFHRPL refers to the CICS Configuration Manager V5.3 product library.
- 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.3 server to communicate with a region running the V5.2 agent.
- Restart the region
Updating your CICS Configuration Manager exit programs
If you have attached programs to the CICS Configuration Manager exit points, then you need to update those programs to work with CICS Configuration Manager V5.3:
- Recompile, or reassemble, and link edit all exit programs. Ensure that any references in the JCL to the CICS Configuration Manager SCCVSAMP library refer to the V5.3 library rather than the V5.2 library.
- If you have resource attribute update exit programs that use rules based on member CCVXPRAR of the sample library SCCVSAM2, then you need to regenerate those rules for CICS Configuration Manager V5.3. To regenerate the rules, see member CCVXPRAJ of the sample library SCCVSAMP.
- If you have operations qualification exit programs that use rules based on member CCVXPOQR of the sample library SCCVSAM2, then you need to regenerate those rules for CICS Configuration Manager V5.3. To regenerate the rules, see member CCVXPOQJ of the sample library SCCVSAMP.
Updating your command to start the CICS Configuration Manager ISPF dialog
Update the command that you use to start the CICS Configuration Manager ISPF dialog interface program CCVOREXX: replace the high-level qualifier of the CICS Configuration Manager V5.2 product library with the V5.3 high-level qualifier.
Updating your personal CICS Configuration Manager ISPF dialog settings
Each CICS Configuration Manager ISPF dialog user must update their STEPLIB setting to refer to the CICS Configuration Manager V5.3 libraries. To update the STEPLIB setting, select CICS Configuration Manager ISPF dialog option 0 Settings.
To automatically update this setting when users start the CICS Configuration Manager ISPF dialog, see member CCVDEFLT of the sample library SCCVSAMP.
Updating your JCL that calls CICS Configuration Manager
Update any JCL that you have created that calls CICS Configuration Manager programs, such as the batch client interface program CCVBMAIN or the batch housekeeping program CCVBHKP: replace the high-level qualifier of the CICS Configuration Manager V5.2 product library with the V5.3 high-level qualifier.
For JCL that uses the sample CCVXXMLC REXX procedure to send ad hoc CICS Configuration Manager SOAP API requests:
- Review the CCVXXMLx samples. The enhanced samples require the IP address of the CICS Configuration Manager server to be supplied as an input parameter.
- To make your existing batch jobs compatible with the updated CCVXXMLC sample, specify LOCALHOST as the IP address.
- To enable your existing batch jobs to take advantage of the updated CCVXXMLC sample, and be capable of running on other z/OS systems, specify the CICS Configuration Manager server IPv4 address or host name.