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.
- 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.
- 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.1 product library
high-level qualifier:
//DFHRPL …
DD DSN=ccvhlq.SCCVLINK,DISP=SHR
DD DSN=ccvhlq.SCCVAlang,DISP=SHR
- Edit and submit the JCL in the following members of the V5.1 sample library
SCCVSAMP:
These delete and re-define work files for the CICS Configuration Manager server.
- 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.
- 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.
- 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
- 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 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:
- Backup the V2.1 CCV*
members (so that you can restore them if you decide later to revert
to V2.1)
- Copy the V5.1 CCV*
members from SCCVAUTH and SCCVlang to your
own APF-authorized libraries
- 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.
- 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.
- 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.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.
- Ensure that the CICS library concatenation DFHRPL
refers to the CICS Configuration Manager V5.1 product library.
- Replace the programs listed in CCVXCSDR. Either:
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.