> 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". 2 remarks to that: *Someone* within IBM should have done *some* quality control on what is released on unsuspecting ADCD customers. The system came preinstalled, we had nothing to do with it and no control over what they installed. This isn't the only thing that is wrong - Marna already forwarded a list of my obvious grievances to the ADCD team. Secondly, I *do* like HC. (Guess why I went to all the trouble complaining about bad checks? Not because I don't like it but because I wanted it to be better!) Unfortunately, it doesn't come installed on the ADCD system. I did install it on our old system but due to lack of DASD not on the new system yet. Again unfortunately, the ADCD system setup flies in the face of just about everything HC deems 'good practise' - as in: No RACF profiles defined for any system HLQs, so RACF always comes back with RC12. Rightly so. I could name other things that are obviously set up worst practise.
> 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. Yes, in the meantime I found the module. And I still wonder why ftp works with the old definitions when there is quite obviously a missing definition in */PROGRAM. Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
