On Sun, Dec 3, 2017 at 3:17 AM, Peter Hunkeler <[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. > > > > What specifically are you trying to achieve so that you need to use > BPX1EXM and cannot use BPX1EXC? The latter can invoke a load module > residing in a load library or LPA via external link. All the UNIXish > features like passing arguments, environment variables, open files > descriptors are availeble. >
I don't have an actual program or system which I'm trying to write. I am not doing much during "Open Enrollment" and so I'm just looking at some of the various z/OS MVs & z/OS UNIX facilities with which I am not really familiar. In this thread, that is the BPX1EXM callable UNIX service. Why did I choose this? No real reason. Why am I curious about in-memory data passing (in this or other environments)? I just am. IOW, this entire thread is just for my learning. Even a 65 - 1 fortnight, I still like to learn new stuff. Basically what I've learned in this thread, at least so far, is that the only thing I can pass to the invoked program is the equivalent of the data which can come in via the PARM= on a JCL EXEC PGM=, and in that same format. From the doc on BPX1EXM, that is, at most, 4096 bytes. > > -- > Peter Hunkeler > > -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
