A sample CICS startup procedure

As an alternative to submitting a batch job to the MVS internal reader, you can use the MVS START command to start CICS® as a started task. 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.

About this task

If you intend to start CICS with the START command you must either:
  • Give the MVS started task procedure a name different from the subsystem name in IEFSSNaa (default 'CICS'), or
  • Issue the start command with the parameter SUB=JES2 or SUB=JES3 as appropriate.
You can use the following form of the MVS START command to start a job from the console:
S|START procname[.identifier][,SUB=subsystemname][,keyword=option
 [,keyword=option] . . .]
where:
procname
The name of the cataloged procedure that defines the job to be started.
identifier
The name you choose to identify the 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.

For guidance information about the complete syntax of the START command, and all the keywords and options you can use, see z/OS MVS System Commands.

To start CICS, you only need to code procname.identifier,keyword(s)=option.

For example:
START DFHSTART.CICSA,SIP=T,REGNAME1=IDA,REGNAM2=IDA
In this example of the MVS START command:
  • DFHSTART is the name of the CICS-supplied cataloged startup procedure.
  • CICS is being started with a task ID of CICSA.
  • SIP is the suffix of the DFH$SIPx member in the SYSIN data set, CICSTS53.CICS.SYSIN, to be used by this CICS region.
  • REGNAM1 and REGNAM2 are qualifiers added to the CICS system data sets specified in the procedure (for example, CICSTS53.CICS.CICSHTH1.DFHTEMP) to identify uniquely the data sets for this CICS region. REGNAM1 is set to the same value as REGNAM2 for an MRO region.
For information about the DFHSTART procedure, see the CICS startup procedure, DFHSTART.

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 information about this association, see Authorizing CICS procedures to run under RACF .