This isn't a 'problem' per se, just an observation that someone else may be
able to shed some light on...
In SDSF, the DA panel presentation can be modified using the 'View' option.
For my logon id I have brought the column named 'Tran-Act' in to view, and
then sorted the display so that Tran-Act is in ascending sequence.
An excerpt for a current display is: (hoping this doesn't get
reformatted...)
NP JOBNAME StepName ProcStep JobID Tran-Act CPU% CPU-Time
BUILD5 *OMVSEX STC24665 0:00:00 0.34 0.01
BUILD2 STEP1 STC23744 0:00:14 22.72 9.53
OMVS OMVS OMVS 5:35:02 0.21 1228.64
BUILD9 *OMVSEX STC23888 14:07:22 2.50 1458.22
SSHD6 STEP1 STC23925 14:07:22 0.00 3.49
IMS14J11 IMS14J11 JMPRGN JOB23674 34:44:13 0.00 0.44
IMS14F11 IMS14F11 IFP JOB23671 34:44:21 0.00 0.01
At the bottom of this excerpt, there are two tasks associated with an IMS
region that was started shortly after the system was IPL'd, nearly 35
hours ago. In the full display, there are a number of other tasks below
this that all have Tran-Act times that are roughly the same.
Above the IMS-related tasks, there are two tasks that have been running for
a bit over 14 hours.
The OMVS task above that has apparently been running for only five and half
hours or so, and that is the curiosity...
OMVS is started at IPL time, just like the IMS region in the example above,
and it is never terminated until we shut the system down again. (in the
shutdown sequence, it is the last thing to be terminated before JES can be
stopped).
So why isn't OMVS's "Tran-Act" time in the same ball park as the IMS tasks?
Regards
Sean
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
