On Fri, 1 Dec 2017 15:09:07 -0600, John McKown <[email protected]> wrote:
>I didn't go into the really weird experimentation that I'm doing. I'm a >just "messing around" with the BPX1EXM (execmvs) UNIX function. This is a >real weirdie (to me). It basically terminates the current job step, then >_inserts_ a new job step (which shows up with *OMVSEX as the step name) >immediately _after_ the current job step and _before_ the next JCL job >step. I'm still in the same ASID, but all the JCL has disappeared and all >the user allocated memory is gone (non APF can't get LSQA which would >survive). Now, I can pass up to 32767 bytes from my program to the next >program via the standard "batch" PARM= equivalent. This can be arbitrary >byte values (range x'00' to x'FF'). So I'll probably just use that >facility. Hopefully I will never need more than 32767 bytes. Hum, could it >really be x'FFFF' bytes? I'll need to check that out. > >I'm just messing around with this and wanted an easy way for my invoker to >send more data to the invokee. I could cheat and use UNIX message queues. >But they are not cleaned up at job end. Wouldn't it be more "UNIX-ish" if you forked, then did the execmvs in the new address space? You could create a pipe to transfer the data between the two. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
