Interface operation

Normally, you do not need to issue commands to the interface. Sufficient defaults are built into the system so that all necessary actions are taken automatically when you start the interface. Be familiar with the functions and features of the interface.

The interface (KOIIA00) runs in its own address space. Not only the interface but also the three collectors are isolated from the IMS™ address space. They do not use any virtual storage space within the IMS control region’s private area.

The startup parameter to KOIIA00 determines which IMS system to monitor based on the IMSID. When you start the interface, it checks the dispatching sequence of address spaces to ensure that the interface precedes IMS. If it does not, the interface issues a warning message to the console and continues to work. Collector values can be accurate only if the interface has a higher priority than IMS. (See the Planning and Configuration Guide for a description of the necessary JCL.)

The interface creates an internal ID for itself by prefixing two characters to the IMSID of the IMS system it is monitoring. It notifies z/OS that it accepts z/OS MODIFY commands addressed to that ID. The default prefix is M0. If you run your IMS control region with an IMSID of IMSA, the interface asks z/OS to pass it all z/OS MODIFY commands entered for the ID of M0IMSA. The interface processes only z/OS MODIFY commands; it rejects z/OS STOP commands for the internal ID and displays an error message.

When the interface starts, it automatically runs a series of commands. These commands are in member KOImpP00 in the RKANPAR library. You receive a default series of commands that you can modify. (See the Planning and Configuration Guide.)

The interface issues its first command itself to the default startup member, so that its operation can be automatic:

EXEC KOImpP00

The startup member automatically processes only at initial region startup.

After the interface completes all the actions that are defined in KOImpP00, you can issue more interface commands through the z/OS MODIFY facility by using the OMEGAMON for IMS internal ID.

The standard OMEGAMON for IMS installation procedure requires you to start the EPILOG collector automatically. To start the EPILOG collector, remove the comment character from the EXEC KEICOLmp command in the default KOImpP00 provided.

The following is an example of a MODIFY command that uses the internal ID and default prefix:

MODIFY  M0IMSA,START EPILOG

or

F M0IMSA,START EPILOG

When you start the interface, the display active command D A,L (a system command) displays one line that contains identifiers for the IBM® monitor job and another line that shows identifiers for the internal MODIFY ID used by the interface. Suppose the IMS you are monitoring runs as a batch job, with an IMSID of IMSA and JOBname MONIMSP. The D A,L command displays:

JOBname    STEPname   PROC STEPname
MON210T    IMS        IMSPROD        NSW   J   <JOBname>
M0IMSA     M0IMSA     MONIMSP        NSW   J   <MODIFY ID>

If you start the interface as a started task, modify the STEPname to produce a unique z/OS MODIFY ID. For example, IMSMON:

START OMIMS.IMSMON

Now D A,L shows:

JOBname    STEPname   PROC STEPname
OMIMS      IMSMON     IMSPROD        NSW   S   <JOBname>
OMIMS      M0IMSA     IMSMON         NSW   S   <MODIFY ID>

Remember, in both these examples the second line is the internal MODIFY ID that the interface builds.

In this example, you can terminate the interface with one of the following MODIFY or STOP commands to the z/OS ID:

STOP IMSMON
P IMSMON 
MODIFY IMSMON,STOP
F IMSMON,STOP

The interface operates automatically and usually does not require operator intervention.