On 30/10/2020 11:10 pm, Kirk Wolf wrote:
In the SDSF PS display for the COZBATCH example, all the PIDS ran in the
same AS except for the one you asked about:
ANDREWRB STC03080 RUNNING ANDREWR 1R 16843329 16843349 79
004F /bin/sh /home/andrewr/breakit.sh
the parent of this is process:
ANDREWRB JOB03101 WAITING FOR CHILD ANDREWR 1W 16843349 50397780 51
0033 /bin/sh /home/andrewr/breakit.sh
Both of these are what you see when you run a shell script file with
/bin/sh. I'm not sure what breakit.sh does, but these two are what you
would see if the /bin/sh shell forked itself without doing an exec.
This is what the shell would do for cases like using a builtin in a pipe.
breakit.sh is described in the write up I linked previously.
@wizardofzos found what looked like a bug in the shell and posted a
script to trigger it. I tried to reproduce it but could not, however the
script produced some interesting SMF data.
I assumed the first link in the pipe would run in the same address
space, with the subsequent link in other address spaces. Cut is the
final command so I was surprised that it ran in the original address
space. I guess it makes as much sense - maybe more - that the last piped
command runs in the original address space, not the first.
I didn't see the 2 breakit.sh PS entries when running under BPXBATCH -
only COZBATCH. Maybe it is fast enough that I was unable to catch it.
Andrew Rowley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
