If it is truly the case that the new version of the module is not being used, then clearly the old version is being found somewhere.
If you have replaced the copy in the only data set where it lives and refreshed LLA, then these are the possibilities that come to mind -- you are not re-fetching at all because your jobstep has already fetched the previous copy and that copy is still usable -- you do have a tasklib, steplib, or joblib -- the fetch is being done identifying an opened DCB within which concatenation the previous copy exists -- the original copy is in LPA and your updated copy is not (whether by PLPA, MLPA, FLPA, or dynamic LPA) I presume that if the Cobol compiler found your new version but didn't like it in some way (so reverted to old behavior) it would tell you. Various fetch monitoring tools can provide some clue of where a module was found when it was fetched. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
