Administering
Administering is the activity in which you manage your CICS® systems by using the provided system management interfaces, such as CICS Explorer® . Use this information to manage
applications and workloads, change system settings in a CICSplex, and manage definitions in the CICSPlex® SM data repository.
Controlling CICS operation
While CICS is running, you can control its operation by changing CICS system definitions and by deleting and installing resource definitions. Use the CICS Explorer to control your CICS systems.
Starting and stopping CICS
This is information about how CICS starts and stops, the implications of different types of start and stop, and the actions you must take to handle them.
Administering CICSPlex SM
After you have configured your CICSPlex SM environment, you can use the CICS Explorer or Web User Interface to manage the environment.
Administering platforms and applications
When you have deployed applications on a platform, you can use the CICS Explorer to view, update, and remove the applications. You can also remove a platform from a CICSplex if it is no longer required. Secure a platform and its deployed applications by setting up security profiles.
Administering CICS applications
After you have deployed your applications, you can manage the environment in which they run and make updates.
Administering for intercommunication
You can manage definitions of MRO, IPIC , and APPC parallel-session connections between CICS Transaction Server for z/OS® systems using connection definitions.
Administering data tables
Information about the operational aspects of data tables.
Administering connections to other systems
After you have set up your connections to other systems, such as DB2, IMS, and IBM® MQ , you can use CICS to manage those connections.
Administering restart and recovery
Before you begin to plan and implement resource recovery in CICS, you should understand the concepts involved, including units of work, logging and journaling.
Administering output from a CICS region
Output written to the CICS transient data queues appears in JCL DDNAMEs that are allocated to a CICS region. An example of this transient data queue is CSSL, which is defined as an extra partition transient data queue and assigned to DDNAME MSGUSR. Over time the amount of data written to the data set can become very large and the data set needs to be deallocated from the region in order to reduce JES spool usage. Here are some recommendations for you to consider.