> I've got a REXX exec that sets up an IPCS environment for z/ > OS levels other than my current release. We have SYSRES volumes for > every release but don't have all the levels IPLed. With this REXX > exec I can select a version of IPCS modules/panels/.... for every > release of z/OS from 2.10 up to 1.13. The REXX pre-allocates the > uncataloged datasets, LIBDEF/ALTLIB/TSOLIBs them, and then kicks off > IPCS. This rexx works fine on every system where the IPLed OS is > anything to z/OS 1.11 and I can work on any level of IPCS > corresponding to the level of the dump I'm looking at from any LPAR, > up do and including dumps generated for z/OS 1.13. > > On a z/OS 1.13 LPAR the exec seems to work, i.e. no errors reported, > but it always runs the 1.13 version of IPCS. Using ISRDDN while in > IPCS I can see the the BLSG module is being loaded from ISPLLIB, > which contains the 1.13 version. On a z/OS 1.11 LPAR BLSG is loaded > from IPCSLIBS, which is the DD pointing to the non-cataloged older > IPCS level, which is made available via "TSOLIB ACTIVATE DDNAME > (IPCSLIBS)" command before starting ISPF. > > TSOLIB DISPLAY shows - > Current load library not established by TSOLIB. > TSOLIB search order (by DDNAME) is: > DDNAME = IPCSLIBS > in all cases. > > Adding a "LIBDEF ISPLLIB LIBRARY ID(IPCSLIBS) STACK" before the > "ISPEXEC SELECT PGM(BLSG)" causes the older/correct version of BLSG > to be loaded from IPCSLIBS but other modules appear to be 1.13 versions.
In the archives: http://bama.ua.edu/cgi-bin/wa?A2=ind1201&L=ibm-main&P=R62902&I=1&X=-&Y=d10jhm1%40us.ibm.com An ISPF application that needs their LINKs, LOADs, ATTACHes and XCTLs to search the ISPLLIB should be started via SELECT CMD(youprog) rather than SELECT PGM(yourprog). With the CMD approach, the program runs with a TASKLIB of ISPLLIB and any LINKs, LOADs, and XCTLs done under that task will thus search ISPLLIB. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
