<snip>I would expect this to fail with some format of ICH408I message. </snip> It is not right to "expect" unless you know the RACROUTE invocation that was used. In many cases, the RACROUTE requestor has RACF not issue ICH408I specifically because the application design (whether ideal or not) is that the message that the application issues covers things, such that the ICH408I was thought to be redundant (and writing redundant messages is not a good thing). Here, the IGD17061I message has a lot of information. If you feel that the design would be improved by also allowing the ICH408I, that is a good candidate for a requirement/request/idea. Peter Relson(ex) z/OS Core Technology Design
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
