On Tue, 7 Oct 2014 12:38:52 -0500, John McKown wrote: > >Hum. Interesting. The failure seems to be related to the REXX code in some >way SEC6 RSN=801D8018 > >. Most interesting is the PSW being in key 0! The phrase "NO ACTIVE MODULE >FOUND - PRIMARY NOT EQUAL TO HOME" indicates to me that the REXX code is >running in a fork()'d address space instead of the batch region. This is >further shown because if I remove the two lines which set up the SYSCALL >environment, the REXX code runs, albeit with the 'sleep 5' failing. This is >beginning to make sense. Since the REXX is running in a separate address >space, and apparently the ADDRESS SYSCALL does not set up any kind of >environment to route the stdin, and stdout/stderr from and to the TSO >address space > But if I allocate SYSTSPRT to SYSOUT (two keystrokes to swap DDNAMEs in my example) no ABEND occurs. Should I conclude that if SYSTSPRT=SYSOUT Rexx doesn't fork? Surely it's easier for a forked address space to inherit a descriptor than a DD SYSOUT.
>(bpxbatch apparently does do this), then the SAY does not have an active >stdout (file descriptor 1) to which to send output. Which results in the >SEC6 abend? > I can see that this is indeed a "BAD". > I should have asked for a DOC APAR as well as PRS. But they'd probably point out that there's no specific statement in any manual allowing allocation of SYSTSPRT to PATH. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
