Lance, I don't think so. I displayed all the existing SLIPs in the system, all defaults of IBM (the Xnnn SLIPs). All of them are non-PER.
I did find the following, however, in the MVS System Commands manual: ---------- SLIP allows specification of NUCMOD, PVTMOD, and LPAMOD on the trap. However for PVTMOD, the cross memory lock (CML) of the primary address space that existed at the time of the PER interrupt must be immediately obtainable in order to search for the specified load module. If the CML is obtainable but the system does not find the specified load module, it puts the target trap into an enabled but inactive state. ---------- So, it would appear that it's not finding load module DSNXGRDS. I've tried LPAMOD, too. Same results. Anyway, I know that the DB2 SDSNLOAD library isn't in the LPA. Any suggestions, anyone? The only other thing I can think of is dumping the DB2DBM1 address space, finding the CSECT in the dump and specifying the address with the SLIP's RANGE parameter. Any better mousetraps? On Mon, 8 Oct 2007 09:10:28 -0600, Lance Kopplin <[EMAIL PROTECTED]> wrote: >ENABLED(INACTIVE) > >means that there is already a PER type slip active in the system. Disable >or >delete it. ---------------------------------------------------------------------- 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
