MVSFORUMS.com

[apoorvakhatri]

Hi,
One of my friend's job is taking days to finish. On digging through Omegamon, I realized many things. In order to unearth further secrets, I would like to go through Omegamon Manual for mainframe. I would apprecite if someone can supply it.
Apoorva.

[kolusu]

apoorvakhatri,

Omegamon is a product of CANDLE. The manuals can only viewed by registered users. But I would this tool is useful only if the program is accessing DB2. I guess the program is in an infinite loop. So first check the program logic. If you still think that the program is ok , use STROBE ( a tool from compuware) for half an hour on the job and check the report. This tool gives you exact details of each and every instruction , with cpu time and elapsed times.

Any way check this link for omegamon

http://www.candle.com/www1/cnd/portal/CNDportal_Channel_Master/0,2258,2683_2867,00.html

Hope this helps...

Kolusu

[Meera]

As suggested by Kolosu, probable cause is a buggsy-loop. You may want to share more detail abt the code - especially the commit-rollback logic and cursors (if any).

[apoorvakhatri]

Appreciate your suggestions. Here is the genesis:
We turned the strobe ON. And measured the performance of the job. Out of the myriad sorts and normal processing steps, one executes DB2 program. Only the queries in this program consume more than 75% time of the entire JOB. This is the reason I am interested in Omegamon : to find out why.
For a different job - takes whopping 15-17 hours - there's only one job step : DFSRRC00. So, that's the grey area where the problem can be with anything : DB2, JCL, datadefinition, program coding, parameters or system side. I believe omegamon can be helpful in this case too - in a different way though - to determine whether the problem is with DB2 or not (rule of elimination).
I believe since my shop uses Omegamon, we SHOULD have the manual for the same.
Again,
Appreciate your suggestions.
Apoorva.