CICS® must be defined as an MVS™ subsystem before you can use any of following facilities:
Also, if you are running CICS with XRF in a multi-MVS environment or a two-CPC (central processing complex) configuration, defining CICS as an MVS subsystem can reduce operator intervention during takeover if MVS or a CPC fails while more than one CICS is running.
For information about the console message-handling facility see The console message-handling facility.
For information about MRO, see the CICS Intercommunication Guide.
Defining CICS as an MVS subsystem involves three members of the SYS1.PARMLIB partitioned data set: IEASYSxx, IEFSSNaa , and DFHSSIyy. You only need member DFHSSIyy if you want the console message-handling facility.
Note that if you intend to start CICS with the START command you must either:
For more information about the subsystem interface, see the z/OS MVS Using the Subsystem Interface .
The following topics cover:
[[ Contents Previous Page | Next Page Index ]]