The following steps describe how to upgrade from CICS® Configuration Manager V1.2 to V2.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 V1.2 repository
and journal with V2.1.
However, the CICS Configuration Manager server,
clients, and agents must be at the same version: you must follow the
steps below to upgrade them together. For example, you cannot use
the ISPF dialog interface supplied with V1.2 to connect
to a V2.1 server.
- Apply the following fixes to CICS Configuration Manager V1.2:
- PTF for APAR PK65882
- This PTF increases the record length of the CICS Configuration Manager V1.2 journal. You
must apply this PTF before using your existing V1.2 journal with V2.1.
- "Toleration" PTF for APAR PK86097
- CICS Configuration Manager V2.1 introduces new
record types to the CICS Configuration Manager repository,
and some modifications to existing repository records. Without this
PTF, CICS Configuration Manager V1.2 is not aware
of these changes. Applying the PTF enables you to revert to CICS Configuration Manager V1.2 after you
have used the repository with V2.1.
While it is
strongly recommended that you install this PTF to V1.2 now, before
using V2.1,
this PTF is required only if you revert to CICS Configuration Manager V1.2 using a CICS Configuration Manager repository or journal
that has been updated by V2.1. In that case,
you must apply the PTF to V1.2 before reverting
to V1.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 V2.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 V2.1 sample library
SCCVSAMP:
These delete and re-define work files for the CICS Configuration Manager server.
- Edit and submit the JCL in the following member of the V2.1 sample library
SCCVSAMP:
This deletes an obsolete control file (not, as the JNL suffix
might suggest, the journal) that was used internally by the CICS Configuration Manager V1.2 server.
- Edit the V2.1 sample
member CCVXCSDD.
This member contains the resource definitions
for group CCV210 required
by the CICS Configuration Manager V2.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 V1.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
CCV120 in the CICS Configuration Manager server
CSD file, or the version of the CCVXCSDD member that you edited when
installing V1.2.
- Edit and submit the V2.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 CCV210 in the CICS Configuration Manager server CSD file,
adds that group to the startup list, and removes the V1.1 and V1.2 groups (CCV110
and CCV120) from the startup list.
Replace the <SVRLIST>
placeholder in CCVXDUP with one of the lists specified by the group
list used at CICS startup.
- Optional: if you prefer not to have the CICS Configuration Manager server initialization
program CCVIINIT in the PLTPI, then remove it.
Previous releases
of CICS Configuration Manager required
you to add CCVIINIT to the PLTPI. This is no longer a requirement
in V2.1. You
can choose to keep CCVIINIT in the PLTPI or remove it, according to
your own preference.
If you remove CCVIINIT from the PLTPI,
then you must invoke this program manually after the CICS region
starts.
- 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 V2.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 you removed CCVIINIT from the PLTPI, then invoke CCVIINIT now
to start the CICS Configuration Manager server.
Tip: You can run program CCVIINIT by invoking the transaction
CCVI on the CICS command line.
- If you previously APF-authorized the CICS Configuration Manager V1.2 product libraries
SCCVAUTH and SCCVlang, then APF-authorize
the equivalent V2.1 libraries.
Place the V2.1 libraries
in the APF-authorized list.
If you copied the V1.2 members from
SCCVAUTH and SCCVlang to your own APF-authorized
libraries:
- Backup the V1.2 CCV*
members (so that you can restore them if you decide later to revert
to V1.2)
- Copy the V2.1 CCV*
members from SCCVAUTH and SCCVlang to your
own APF-authorized libraries
Note: - The V2.1 CCVSCRPT
member of the SCCVAUTH library is the program that creates PassTickets
for the CICS Configuration Manager ISPF
client. The V2.1 CCVSCRPT
member is compatible with both the V1.2 and V2.1 ISPF clients.
However, do not use the V1.2 CCVSCRPT member
with the V2.1 client.
- 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 V2.1 programs to connect
to a V1.2 server.
- 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 V1.2 product library
with the V2.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 V1.2 product library
with the V2.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:
- Replace the agent program CCVSREMP supplied with V1.2 with the updated
program supplied with V2.1.
This
step is necessary because the layout of the parameters that the CICS Configuration Manager V2.1 server passes
to the agent program has changed; you cannot use a CICS Configuration Manager V2.1 server to communicate
with a V1.2 agent.
- Either:
You cannot use CICS Configuration Manager to
perform this particular newcopy, because, as described above, you
cannot use a CICS Configuration Manager V2.1 server to communicate
with a region running the V1.2 agent.
- If you plan to use the new-for-V2.1 deployment analysis
reporting feature to collect runtime resource definitions from active
CSD-based CICS regions, then you need to install a new
agent program, CCVSNCCR, alongside the existing agent program CCVSREMP.
For details, see Optional: Configure the agent for CSD-based CICS regionsOptional: Configure the agent for CSD-based CICS regions.