Starting CICS as a batch job

Procedure

  1. Create a job to start CICS. In your job you can either:
    • Include the CICS startup procedure inline.
    • 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 perform a cold start 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
    //*********************************************************************
    //*
    // CICS710 EXEC CICSTASK,
    // START=COLD,
    // SYSIDNT='HTH1',            SYSID OF CICS REGION
    // CLONE='HT##'               CLONE CICS REGION TYPE
    //*
    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.
    • 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, CICSTS54.CICS.SYSIN, that has system initialization parameters unique to each type of CICS region.
  2. Submit the job through the MVS internal reader. This starts CICS® as a batch job.


dfha601.html | Timestamp icon Last updated: Sunday, 4 June 2017