Starting CICS as a batch job

To start CICS® as a batch job, you submit the job through the internal reader. Your CICS startup job can contain the CICS startup procedure inline, or can invoke a cataloged startup procedure. This latter method has the advantage that several CICS startup jobs (for example, for different CICS regions) can use the same procedure, tailoring the procedure through startup parameters. For example, Figure 1 shows a CICS startup job that invokes the cataloged procedure, CICSTASK, to cold start a terminal-owning with the startup parameters SYSIDNT=HTH1 and CLONE=HT##1. By altering the SYSIDNT and CLONE parameters, the same job could be used to start other CICS regions with the same procedure.

Figure 1. Job to start a CICS TOR, HTH1
//CIDCTOR  JOB (accounting information),userid,MSGCLASS=A,MSGLEVEL=(1,1),
//         CLASS=C,NOTIFY=userid
//*********************************************************************
//* THIS JOB CAN BE USED TO START UP A CICS REGION
//*********************************************************************
//*
//CICS640  EXEC CICSTASK,
// START=COLD,
// SYSIDNT='HTH1',            SYSID OF CICS REGION
// CLONE='HT##'               CLONE CICS REGION TYPE
//*

In this example of the MVS™ START command:

For information about the CICS-supplied startup procedure, see the CICS Transaction Server for z/OS® Installation Guide.

Related tasks
Starting CICS
Specifying system initialization parameters before startup
Starting CICS as a started task
Overriding system initialization parameters during startup
System console messages for CICS startup
[[ Contents Previous Page | Next Page Index ]]