Lester, Charles (LNG-DAY) wrote:
I'm posting to the Assembler list because I mention assembler several times in this message :-) Cross-posting to IBM-MAIN.I've looked thru the archives and manuals and some SHARE presentations, and can't seem to find the answer to this one. We've got an MVS application (LE C++, calling assembler which cares nothing about LE), executing out of MVS datasets in the STEPLIB, which we're modifying, so that the assembler now calls some LE C++ code that uses a DLL which sits over in USS-land. We've successfully gotten the assembler to make the LE C++ callee think it was called from a pure LE caller (a little, but Vendor Interfaces-approved, slight of hand here :-)), but now we're trying to figure out how to combine STEPLIBs with MVS PDSEs with a PATH expression to where the DLL lives. 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. Putting the new program object (PO) into the USS library would be ugly, because this PO is only one of many PO being called when the job step runs. Anybody have any suggestions?
Well, you're right that the two don't mix. STEPLIBs must be PDS/Es, and PATH is used for DLLs. Hmmm. Can you move the DLLs into your STEPLIB and set up PATH to point to the STEPLIB? Kind regards, -Steve Comstock ---------------------------------------------------------------------- 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
