In
<[EMAIL PROTECTED]>,
on 02/07/2006
at 12:16 PM, "Lester, Charles (LNG-DAY)"
<[EMAIL PROTECTED]> said:
>I'm posting to the Assembler list because I mention assembler several
>times in this message :-) Cross-posting to IBM-MAIN.
uses a DLL which sits over in USS-land.
>uses a DLL which sits over in USS-land.
ITYM Unix-land. USS is something quite different.
>but now we're trying to figure out how to combine STEPLIBs with MVS
>PDSEs with a PATH expression to where the DLL lives.
AFAIK the STEPLIB DD is restricted to PDS and PDSE, There are Unix
commands to dynamically extend the STEPLIB, and those do support Unix
files.
>All the examples I can find never mix the two types of program
>object libraries in an execution environment. We get:
> IEF689I JOB xxxxxxxx FAILED STEPLIB DID NOT OPEN.
>if we try to put the PATH statement into the STEPLIB concatenation.
That's what I would expect.
>Putting the new program object (PO) into the USS library would be
>ugly,
What are you trying to say? If the program object is in a PDSE then
you can include that PDSE in STEPLIB. If you don't want it in a Unix
file then why would you care that you can't concatenate a Unix file?
>Anybody have any suggestions?
Use the Unix steplib facility if you can't put the DLL in a PDSE.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patr
>
>--
> Shmuel (Seymour J.) Metz, SysPro
iot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
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
