Can LIBDEF ISPLLIB be used to dynamically allocate SDSNLOAD to ISPLLIB for a DSNREXX application?
When we use LIBDEF to allocate PDB2.DSNLOAD to ISPLLIB, the allocation works, but we receive a RC -3 when ADDRESS DSNREXX is encountered. RC -3 is basically a 'module not found' condition.
The message received from entering XDB2CONN is:
HOST COMMAND ENVIRONMENT ADDED
28 *-* ADDRESS DSNREXX 'CONNECT XDB2'
+++ RC(-3) +++
When we assign PDB2.DSNLOAD to ISPLLIB in the TSO logon PROC, it works. When we use TSOLIB to assign PDB2.DSNLOAD to ISPLLIB, it works. When we use a STEPLIB in the TSO logon PROC, that also works. The problem is that we run three DB2 subsystems in one LPAR and want to dynamically allocate each xDB2.DSNLOAD as required to ISPLLIB.
DB2® REXX does not have any special code to enable ISPF LIBDEF. If you want functionality to dynamically allocate each xDB2.DSNLOAD as required to ISPLLIB, you might try a Dynamic Steplib product.
The requirement MR0828033028 has been opened to request a change in how LIBDEF works to allow dynamic steplib allocation for DSNREXX.
Feed from Retain: 5740XYR00
and PMR#: 60499
Translate this page: