The thread started with the question of What are the limitations/restrictions of the SETPROG LPA command? to which the answer is None that are relevant. Sam Knutson's response correctly pointed out that AMBLIST is not the right way to display LPA information, and will not work at all for dynamic LPA.
A subsequent append then stated I copied my new IEFACTRT module into SYS1.LPALIB, Issued the EXIT delete and EXIT add commands, however, I still am not seeing the new ACTRT module. This of course does nothing. Simply copying into a data set when that data set is never again going to be looked at normally during the IPL is not useful. But use of dynamic LPA following that should work. Use SETPROG LPA to add your new IEFACTRT module into LPA from whatever data set you put it. SETPROG EXIT DELETE the old one SETPROG EXIT ADD the new one Barbara Nitz's append addressed all the really pertinent issues. Regarding >About the problem of IEFACTRT, I has the same problem to add a module of >product ASG named IMPACT in Z/os 1.4, and the solution for the problem: >(PROGAS - SYS1.PARMLIB) > EXIT ADD EXITNAME (SYS.IEFACTRT) MODNAME (ASFACTRT) STATE (ACTIVE) > DSNAME (ASFH1.VS360.LOADLIB) >EXIT ADD EXITNAME (SYSSTC.IEFACTRT) MODNAME (ASFACTRT) STATE (ACTIVE) >DSNAME (ASFH1.VS360.LOADLIB) This is not a good approach. It would be better to have added ASFACTRT to LPA via (for example) SETPROG LPA ADD MOD(ASFACTRT) DSNAME(ASFH1.VS360.LOADLIB) and then not specify DSNAME on the EXIT ADD because then you will only get one copy in common storage of ASFACTRT as opposed to 2. . Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
