The SDSF "TranAct" column is based entirely on the R791TTOD field returned by
ERBSMFI (which in turn is based on OUCBTMO).
This 32-bit value contains the number of milliseconds since the "last
transaction".
The meaning of "last transaction" varies with the workload, so for some address
spaces in might reflect the initial program execution and could be used to
estimate its "up-time".
For TSO users, the "last transaction" will be updated each time ENTER is
pressed and it is entirely possible that other workloads , for example z/OS
Unix, have methods to inform WLM to update OUCBTMO.
Note that R791TMO can only hold x'FFFFFFFF', so for systems that have not been
IPLed for many months this figure is either going to wrap or stay static (I am
not sure which happens).
(For what it is worth, when SDSF detects that a job has been active for more
than x'FFFFFFFF' milliseconds, then we show zeroes for the TRANACT and TRANRES
columns)
Note that SDSF "DA" now has the "Start Date" column in z/OS 2.5 to aid users
trying to work out the up-time of the ASIDs.
Rob Scott
Rocket Software
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Sean Gleann
Sent: 21 February 2023 10:01
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: An SDSF curiosity...
EXTERNAL EMAIL
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
================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support:
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences -
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================
This communication and any attachments may contain confidential information of
Rocket Software, Inc. All unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please notify Rocket
Software immediately and destroy all copies of this communication. Thank you.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
