>That does not solve all my problems, though.
What makes you believe BPX1EXM would be available to
non-UNIX users? My guess is, it is not. Why? Well, ...
... it starts with BPX, which denotes it as belonging to
the z/OS UNIX component.
... it is described in the z/OS UNIX Assembler Services Ref.
... it's description talks about process, process image,
uid, gid, set-uid, etc. ... all this is related to
UNIX.
IIRC, attach_exec, attach_execmvs and execmvs functions have
been implemented to do what a local spawn() can do now (apart
from the explicit loading of a loadmodule from an MVS "load
library"). spawn() wasn't available in the first releases of
OpenEdition.
So, even if BPX1EXM would honor STEPLIB as you'd like, it would
not help for the "non-UNIX-user" case.
I wouldn't want the program to need write authority to the file
system solely to create the external link. If I understood
correctly, you're planning to deliver said program as part of
your product. So, you'd need the customer to install it into
the file system anyway, why not just create the external link
as part of the installation process; it needs to be done only
once, doesn't it?
Apart form all that, I consider your idea of having different
functions in separate load modules all having the identical
load module name and only distinguish by library name a bit error
prone. I as a customer would defninitely not like it.
--
Peter Hunkeler
Credit Suisse
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
