On Mon, 12 Mar 2012 04:15:59 -0500, Ron MacRae <[email protected]> wrote:
>Mark, > Your CLIST is almost identical to my REXX exec. Except I have to > push the TSOLIB command onto the stack as it won't run under rexx, even with > an address TSO in front, and I therefore also push "ISPF" as well. > >I tried typing in your commands at the TSO ready prompt. Still no joy >ISPF/IPCS just isn't 'seeing' the TSOLIB. > >It works fine on LPARS running z/OS 1.11. >It just doesn't work at z/OS 1.13 as BLSG gets loaded from ISPLLIB insted of >the library set with TSOLIB. > >Unless I can work out what's wrong I'll have to resort to messing with ISPLLIB >etc. I'm not sure I understand why your approach even works on 1.11, but it's a complex topic. As previously mentioned, if you have done a LIBDEF for ISPLLIB then in order to get that library concatenation used as a tasklib you have to use SELECT CMD, not SELECT PGM. However, if my understanding is correct, if you had an ISPLLIB DD allocated before you started ISPF, that library concatenation would be a tasklib for anything invoked under ISPF, either via SELECT PGM or SELECT CMD. So, if your correct IPCS library (proper SYS1.MIGLIB) is allocated as ISPLLIB before you start ISPF, or is allocated via LIBDEF and you use SELECT CMD, then everything should work. Your TSOLIB should be irrelevant if you have the wrong level of IPCS allocated as ISPLLIB before ISPF starts, and that should be true with either 1.11 or 1.13. The ISPLLIB allocated when ISPF starts is a tasklib for ISPF and its subtasks, and the TSOLIB as a higher level tasklib would only come into play when modules are not found in the pre-allocated ISPLLIB. -- Walt Farrell IBM STSM, z/OS Security Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
