As has been mentioned, this module should not be in IEAVTRML. In fact *nothing* should be in IEAVTRML. This has been true for quite a while. I know Barbara does not like the IBM HC for z/OS, but it has a check specifically to point out things that are in IEAVTRML since it should be "empty".
We actually encountered a case several months ago where a customer had something in IEAVTRML that had apparently been introduced in a beta about 20 years ago and no one ever noticed. The module in question is surely somewhere in LPA or LNKLST since otherwise you'd be really tired of the CSV003I messages and 806 abends that you would be getting on every task termination if the module did not exist. Barbara very likely tried the obvious things like DISPLAY PROG,LPA and SETPROG LNKLST,TEST, so I don't know where to go from there. Further, the RACF checks that relate to program control are done after a "find" operation has determined that the module is actually findable (by the normal system module search rules). So the LINK to the module must have found it and then determined that it was not allowed to be used in that environment. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
