To start CICS® as a started
task, you use the MVS™ START command. For example, to start CICS from the
MVS console:
S|START procname[.identifier][,SUB=subsystemname][,keyword=option
[,keyword=option] . . .]
- procname
- The name of the cataloged procedure that defines the CICS job to be
started.
- identifier
- The name you choose to identify the CICS task.
- SUB=subystemname
- The name of the subsystem that is to select the job for processing.
If you omit this parameter, the primary job entry subsystem is used.
- keyword=option
- Any appropriate keyword to override the corresponding parameter in the
procedure. You can use this parameter to override symbolic parameters defined
in the cataloged procedure.
Notes:
- Using this method, your startup job stream must be coded according to
the rules for coding procedures, and the procedure must be installed in an
MVS procedure library.
- You must do either of the following:
- Give the MVS started task procedure a name different from the subsystem
name in IEFSSNaa (default ‘CICS’)
- Issue the START command with the parameter SUB=JES2 or SUB=JES3 as appropriate.
For information about the complete syntax of the START command, and all
the keywords and options you can use, see the z/OS MVS System Commands.
To start CICS, you only need to code procname.identifier,keyword(s)=option.
For example, you could use the following start command to start the CICS
tasks listed in Figure 2:
START CICS640
Figure 2. Procedure to start a CICS TOR, two AORs, and an ROR
//CICS640 PROC //* //DUMMY EXEC PGM=IEFBR14 //* // START
CICSTASK.CICSHTH1,SYSIDNT='HTH1',CLONE='HT##' //* START=COLD // START
CICSTASK.CICSHAH1,SYSIDNT='HAH1',CLONE='HA##' //* START=COLD // START
CICSTASK.CICSHAH2,SYSIDNT='HAH2',CLONE='HA##' //* START=COLD // START
CICSTASK.CICSHRH1,SYSIDNT='HRH1',CLONE='HR##' //* START=COLD //* //*
END OF CICS START PROCEDURE
In this example of the MVS START command:
- CICSTASK is the name of a cataloged CICS startup procedure, tailored from
the CICS-supplied sample startup procedure.
- The following CICS regions are started:
- Terminal-owning region, CICSHTH1
- Application-owning region, CICSHAH1
- Application-owning region, CICSHAH2
- Resource-owning region, CICSHRH2.
- SYSIDNT is the qualifier used to identify CICS system data sets that are
unique to each CICS region.
- CLONE is the qualifier of the member in the SYSIN data set, CICSTS31.CICS.SYSIN,
that has system initialization parameters unique to each type of CICS region.
For information about the CICS-supplied startup procedure, see the CICS Transaction Server for z/OS® Installation Guide.
If you are running CICS with RACF®, you must associate the cataloged procedure
name with a suitably authorized RACF user through the RACF table, ICHRIN03.
For details about this association, see the CICS RACF Security Guide.
[[ Contents Previous Page | Next Page Index ]]