Operating an IMSplex


Operating an IMSplex differs from operating a single IMS. The individual IMS subsystems in an IMSplex must be defined and set up individually; however, once this up-front work is done, they can be operated as a group, the IMSplex.

In general, you operate an IMSplex by issuing commands through the Operations Manager and analyzing the responses to those commands. You cannot issue commands directly to OM, however. OM has an application programming interface (API) that is designed to accept commands from and pass command responses to an application program. The IMS TSO SPOC application and the IMS Control Center are examples of such application programs.

The IMS Control Center, which supports IMS Version 8 and later and is part of the DB2 Universal Database Control Center, is another application program that accesses the OM API. With the IMS Control Center, you can manage your IMSplex using a graphical interface. The IMS Control Center uses the SPOC functions of the OM API. For more information about the IMS Control Center, go to www.ibm.com/ims and link to the IMS Control Center page.

You can design an application program that allows an operator to enter the commands and view the responses or you can design an automated operator program that issues commands and makes decisions based on the responses. The commands that are issued are the same in both instances. The differences are:

  • The automated application program must anticipate what the responses to the commands will be and have logic to deal with those responses.

  • The operator (issuing commands through an application) must have procedures to follow.

Recommendation:

When designing the automated operator programs or creating operator procedures, keep in mind that there might be IMSplex-wide ramifications for some actions. For example, if you tell an operator (or code your AOP) to shut down a particular SCI for a particular reason, the IMSs that used that particular SCI can no longer communicate with the IMSplex after that SCI is shut down. This might not be the solution you were hoping for, so plan accordingly.


The following list briefly covers the operations of the IMSplex.

  • Starting or restarting an IMSplex

Start an IMSplex in the following manner:

  1. Start the CSL components that are local to the IMS control region with a z/OS START command.

  2. Start the local IMS control region with the appropriate parameters specified on the appropriate PROCLIB members.

  3. Start the other individual IMSplex components (other IMSs, SCIs, OMs, and RMs).

An IMSplex or its components can be restarted (after a failure or shutdown) by either manually starting the individual components (with a z/OS START command) or by using the z/OS Automatic Restart Manager (ARM). If ARM is used for restart purposes, it is specified on the IMSplex components' startup procedures or in their individual initialization PROCLIB members.

  • Querying statistics from an IMSplex

    Any IMSplex member (for example, an Automated Operations Program [AOP]) can query statistics about the components of a CSL using a CSLZQRY request.

  • Shutting down an IMSplex

    Shut down an IMSplex using two basic steps:

    1.

    Shut down the IMS components that participate in that IMSplex (issuing a /CHE FREEZE or similar command to the individual IMSs).

    2.

    Shut down the CSL and its components.



Introduction to IMS. Your Complete Guide to IBM's Information Management System
An Introduction to IMS: Your Complete Guide to IBMs Information Management System
ISBN: 0131856715
EAN: 2147483647
Year: 2003
Pages: 226

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net