I had a case where I had implemented a nice message for access-not-allowed so my RACROUTE told RACF not to write a message. After quite some time, I realized that my "nice message" did not have a bunch of valuable information that ICH408I did have, so in a later release I changed the implementation to have the ICH408I message too. That was much easier than changing my "nice message". Thus you could say that there is precedence to making the sort of change you might request. 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
