KiwiREXXDude,
Certainly STEPLIB would work if I was able to run this REXX in Batch. However, this application must be initiated under ISPF Option 6 since there is a potential of 3000 different end-users. Also it would work to make an explicit call to the Assembler program, if it resided in the...
REXXHEAD,
Thanks for the TSOLIB suggestion! It appeared that TSOLIB was the answer until I read the documentation in 'z/OS V1R4.0 TSO/E Command Reference' stating "If the TSOLIB command is issued from any other environment, like ISPF or REXX, only the TSOLIB command with its DISPLAY operand is...
Tony,
I could manually allocate the steplib in TSO and that would work for me. However, this REXX is part of an ISPF initiated application that has hundreds of users. So that is not a viable option.
Thanks again.
MNMan
Thanks for the response Tony! I had tried LIBDEF in the format of ....
ADDRESS ISPEXEC "LIBDEF ISPLLIB DATASET ID('"LOADLIB"')"
ADDRESS ISPEXEC "SELECT PGM(PULVR)"
... where "LOADLIB" was a REXX variable defined as the DS Name to the Vendor/private library. However, this...
Can someone give me direction to resolve an issue involving REXX code initiated from ISPF. The problem I am having is during the execution of the REXX program I am calling an Assembler module(that resides in the systems LINKLIST) which in turn calls a module that resides in a library that is not...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.