On 27/06/2024 10:54 am, Farley, Peter wrote:
I am not asking about batch jobs that can start long-lasting or somehow
disconnected Unix processes that outlive the batch job execution. I am only
asking about synchronous processes started and completed in the course of one
batch job. Your reference to “sshd” is what has confused me. What does the
“ssh” demon process have to do with a simple batch job that runs shell commands
and a python (or go, etc.) program for some application-specific reasons?
SSHD was an example of a BPXBATCH job/stc where the resulting tasks far
outlive the job that started them.
Even for a simple batch job: BPXBATCH -> shell -> shell script -> Python,
the different parts are running in separate address spaces, and I don't
think that the system can be sure which order they will end. How can it
tell the difference between a simple batch job and something that
behaves like sshd?
It would be nice if the CPU etc was rolled up into the BPXBATCH job, but
I think it would make writing the SMF records when unix tasks end very
complex.
The CPU/IO etc for the cp, Python etc. steps is recorded, but it is in
separate SMF records with SMF30WID = OMVS. IEFACTRT could presumably
process them, but there are potentially thousands per second.
--
Andrew Rowley
Black Hill Software
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
