by steve-myers » Tue Dec 20, 2016 10:19 pm
I did a project of this nature back in the 1980s. It was never updated to MVS/XA or more recent releases and the code has long since disappeared. In any event, what I think you want is rather indeterminate, so I'm not sure you'll get anything useful.
Just to give you an idea of the problem, JCL like this is all too common.
// EXEC PGM=SORT
//SORTIN DD – An existing tape data set -
//SORTOUT DD DISP=NEW,UNIT=TAPE,...
You'll see messages like this -
10:00:00.00 MOUNT vvvvvv ON iiii
10:00:00.00 MOUNT scrtch ON oooo
10:00:30.00 iiii READY
The presumptive time for the iiii READY message was typical of the robots of the era. In any event, while it's perfectly accurate and meaningful in that context, let's look at the output tape. Sort just needs SORTIN to start. Sort won't touch SORTOUT until it has read all of SORTIN. This is why you often see
//SORTOUT DD DISP=NEW,UNIT=AFF=SORTIN,...
The SORTOUT tape may be physically mounted while sort is reading through the SORTIN tape, but there will not be any indication of this in SYSLOG. Of course, sooner or later sort will finish with SORTIN. Then you'll see the messages for device oooo. Now what's the delay here? In practice, 0, because OPEN does not have to wait for the operator, or a robot, to mount the tape. But how do you measure it?
Like you I had hoped to use SYSLOG, but it was incomplete. I do not know if CA1 had come up with a mod for a dev xxxx READY message like you talk about, but I certainly didn't have it, but it wouldn't be seen until the data set was opened, which was too late much of the time. What I ultimately did was monitor the real UCBs.