You can use CICS® DA
to start a CICS region as a
started task, or by submitting JCL in a data set member. The method
that is used to start the CICS region
is called the start policy.
The CICS region must be in the CICS DA system model. You must update the model
to provide the information about the start policy before you can start
a CICS region. CICS DA submits the processing to run the start
policy on the z/OS® system that
is associated with the CICS DA
connection.
Before you begin
You must have an active CICS DA
connection and a local copy of the system model before you can save
the start policy. For more information, see Running discovery and loading the system model.
Note: CICS DA issues the z/OS MODIFY command to shut
down a CICS region. If your
organization uses multiple CICS regions
with the same job name, then you cannot stop these regions by using
the default stop policy. You must change the default stop policy to
the command you use to stop your region. For example, you might change
the stop command for the region to be: F jobname.identifier,CEMT
P SHUT.
Procedure
- In the DA Explorer view, expand the system model to show
the CICS region for which you
want to record the start policy. Double-click the CICS region, or right-click the region and click Open. The CICS region
editor opens showing the details of the selected region.
- In the Start and Stop policies section, click Specify
Start policy or Update Start policy.
You see the Update Start policy option only
if your CICS region is run
as a started task and the discover operation generated a start policy
for that CICS region. The Specify
start policy window is displayed.
- Select the appropriate option and enter the start policy
details:
- If the CICS region
is started by submitting a batch job, click Batch Job and
enter the data set name in the field. The data set name must be in
the following form:
JT1.CICS42.JCL(LMASGV8)
JT1.CICS42.JCL contains
the data set qualifiers and LMASGV8 is the member
name. Alternatively, you can enter one or more of the qualifiers and
click Browse to find the data set.CICS DA submits the job to run
the start policy on the z/OS system
that is associated with the CICS DA
connection. You might need to edit the JCL and add JES control statements
to ensure that the job runs on the correct MVS™ image. For example:
- For JES2: /*JOBPARM SYSAFF=MVS1
- For JES3: //*MAIN SYSTEM=MVS1
For more information about the JCL JES control statements,
see the MVS JCL Reference.
- If the CICS region
is started as a started task, click Started Task.
In the field, type the start command that is prefixed with the MVS ROUTE command. The MVS ROUTE command ensures that CICS starts on the correct image. For example,
if your started task is CICSA and it runs on MVS1,
you would type:
RO MVS1,S CICSA
For more
information about the MVS ROUTE
command, see the MVS System
Commands Reference.
- If the CICS region
is run as a started task and the discovery operation generated a start
policy, the generated start policy is displayed. To generate the start policy, CICS DA requires read access to
the CICS region JES output
that it is generating the start policy for. However, if you want to
use a different start policy for the CICS region,
click Started Task and enter the start command.
This start command is then used instead of the generated start policy.
Note: Whenever
the discover operation is run, if discover detects changes to the CICS region started task procedure
it updates the generated start policy. If you enter a start policy
for a specific CICS region, CICS DA does not alter or overwrite
the start policy.
- When you are finished, click OK to
add the start policy to the region editor. Press Ctrl+S, or click
the Save icon to save your changes in the model.
Results
The CICS region
start policy is updated in the model on the CICS DA server. You can now use the CICS region editor to add the region
to a CICSplex, start the region, or clone the region.