X hits on this document

968 views

0 shares

0 downloads

0 comments

36 / 236

Interface Operation

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

EXEC KOIM0P00 The startup member automatically processes only at initial region startup.

After the interface performs all the actions defined in KOImpP00, you can issue more interface commands through the MVS MODIFY facility using the OMEGAMON II internal ID.

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

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

MODIFY M0IMSA,START EPILOG

or

F M0IMSA,START EPILOG

Displaying active interface commands

Once you start the interface, the display active command D A,L (a system command) displays one line that contains identifiers for the Candle 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 MON210T M0IMSA

STEPname PROC STEPname

IMS M0IMSA

IMSPROD MONIMSP

NSW J <JOBname> NSW J <MODIFY ID>

Starting the interface as a started task

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

START OMIMS.IMSMON Now D A,L shows:

NSW S

<JOBname>

NSW S

<MODIFY ID>

JOBname

STEPname PROC STEPname

OMIMS

IMSMON

IMSPROD

OMIMS

M0IMSA

IMSMON

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

36

OMEGAMON II for DBCTL Historical Component (EPILOG) Reference Manual Version 510

Document info
Document views968
Page views968
Page last viewedFri Dec 09 03:20:34 UTC 2016
Pages236
Paragraphs8116
Words69808

Comments