OMEGAMON DB2 Operations - Object Analysis

Answer

Object Analysis (OA) is a feature of OMEGAMON DB2 (OMPE) that provides DASD volume and dataset level DB2 performance data. OA is dependent on the Event Manager (EMGR) subtask of the OMPE address space.

The Event Manager (EMGR) subtask is typically started when the OMPE server is started. In the hilev.RKD2PAR dataset is a member by the same name as the started task (the startup member). Within the startup member are a number of
EXEC xxxxxxxx
lines where xxxxxxxx is the name of another member in the same dataset. These EXEC statements start the various subtasks that run within the OMPE address space. An asterisk (*) in column 1 of the line will comment out the line and the command will not be executed.

EXEC EMGRssid is the command that will start the Event Manager for LPAR ssid.

If the EMGR is not started at OMPE start-up, it can be started via a MODIFY command issued to the OMPE task. The command format is
/F canso2,EXEC EMGRssid

In V510 and beyond the command is
/F canso2,EXEC STRTOA
RKD2PAR(STRTOA) now includes the start for the Event Manager and the Object Analysis task(s).

The following messages in the OMPE server JESMSGLG will indicate that Event Manager is started regardless of how the start is performed
KO2E3000I EVENTMGR INITIALIZATION IN PROGRESS
KO2E3001I EVENTMGR INITIALIZATION SUCCESSFUL

To determine if the EMGR is already running issue the following command to the OMPE server task
/F canso2,DISPLAY
The Event Manager is running in this OMPE task if you see this message in the JESMSGLOG
CI0594: ID=EVENTMGR PROGRAM=KO2EINTB

Only one Event Manger can run per LPAR. If another OMPE task has already started the EMGR on that LPAR, the OMPE JESMSGLG will show the following message when an attempt to start another EMGR is tried.

KO2E3000I EVENTMGR INITIALIZATION IN PROGRESS
KO2E3005W EVENTMGR V410 IS ALREADY ACTIVE IN SERVER DBS02BF4 - START REQUEST REJECTED

To stop the Event Manager (EMGR) without cycling the OMPE task the following command can be issued.
/F canso2,P EVENTMGR
This will result in the following messages in the OMPE JESMSGLG
KO2E3003I EVENTMGR STOP PROCESSING IN PROGRESS
CI0592: TASK ID=EVENTMGR HAS BEEN STOPPED VIA POST

If Object Analysis is running when the EMGR is stopped, OMPE will also stop Object Analysis.
Object Analysis can be started from the startup member. The command for this is
EXEC ssid|dbid
which is the LPAR id (ssid) concatenated to the DB2 subsystem id (dbid).

OA can also be started by operator MODIFY command as follows
/F canso2,EXEC ssid|dbid

In V510 the start-up of the Object Analysis tasks are included in the RKD2PAR(STRTOA) member. There are no longer individual RKD2PAR(ssid|dbid) start-up members.

When OA successfully starts, the OMPE JESMSGLG will show the following messages
KO2E3040I VOLUME ANALYSIS INITIALIZATION COMPLETE
KO2E3070I D71D OBJECT ANALYSIS INITIALIZATION IN PROGRESS
KO2E3050I D71D OBJECT ANALYSIS PHASE1 INITIALIZATION COMPLETE
KO2E3051I D71D OBJECT ANALYSIS PHASE2 INITIALIZATION COMPLETE
KO2E3071I D71D OBJECT ANALYSIS INITIALIZATION SUCCESSFUL

To prevent OA from automatically starting, comment out the EXEC ssid|dbid lines in the startup member by placing an * in column 1 of the line.

In V510
To prevent OA from automatically starting, comment out the appropriate
F EVENTMGR,START DB2=DBA1,INTERVAL=15,THREAD=YES
statement in RKD2PAR(STRTOA)

OA can also be started by a logged on user. A user navigates to Object Analysis, then to Collector Control to issue the start command. This is a level 3 secured command so the user will need the appropriate authorization or password. The command looks like this
OJIN INTERVAL=5
A successful start will result in the following message back to the user’s console
>> KO2O1611I START REQUEST SUCCESSFULLY PROCESSED (OJCNOJIN) <<

If there is no EMGR running on the LPAR the user will get this message at the console
+ >> KO2O1610E EVENTMGR O2ECNTL IS NOT ACTIVE. START REQUEST IGNORED ( <<
+ >> OJCNOJIN) <<

When the EMGR is not running in the same OMPE task as the OA, the only method to start OA is from with in the product using the OJIN command as shown above.
When using either the startup member line EXEC ssid|dbid or the modify command to start OA, if the EMGR is running in a different OMPE server, or the EMGR is not started the result will be a message
CI0552: TASK TO MODIFY NOT FOUND

To stop OA when it is running, the user should logon to the VTAM interface, select Object Analysis and then Collector Control. Select option B to stop OA and follow the instructions on the screen.

When OA is terminated the OMPE JESMSGLG will display the following messages
KO2E3061I D71D OBJECT ANALYSIS TERMINATION IN PROGRESS
KO2E3062I D71D OBJECT ANALYSIS PHASE1 TERMINATION COMPLETE
KO2E3063I D71D OBJECT ANALYSIS PHASE2 TERMINATION COMPLETE
KO2E3064I D71D OBJECT ANALYSIS TERMINATION SUCCESSFUL