> On Mon, 1 Oct 2012 16:24:13 -0500, Mark Steely wrote: >I am testing z/OS v1r13. I am also testing CA-OPS/MVS. I have something >strange happening when I try to process the OPS-LOG. I have a steplib in my >logon proc and in all the started tasks for OPS/MVS. ISRFIND finds the module >in my logon steplib and also in the LNKLST for the old release. When I execute >the process to dump the log it is picking the old release module and abending. >The process to dump the log is performed by the OSF address space which has a >steplib pointing to the new release. The search for load modules as I >understand is joblib , steplib, then lnklst. I have removed the lnklst entry >for the old release and re-ran my test and it worked correctly. So I know it >has to be going through the steplib to find the load module. > Has anyone else seen this type of behavior ? Any help would be appreciated.
CA-PDSMANs "Program Fetch Optimization facility" can change the search order. Check the "$PFO"-rules if PDSMAN is running on that system. Norbert Friemel ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
