scott Ford wrote: >It is still true you can do I/O , disk I/O in particular from say a RACF exit, >in particular IRREVX01 ?
You can only use what is documented. I did a quick RTFM, apparently IRREVX01 is not (or cannot!) doing disk I/O due to the nature of how it is being called in the first place. IRREVX01 receives the command issued twice during pre and post processing calls. I am not sure where the IRREVX01 is running - in the address space of the RACF command issuer or in RACF system address space. The only inputs for IRREVX01 are some flags in the parameter list and command buffer. IRREVX01 can modify the contents of the keywords of the intended command issued. Output allowed is a message area which you can place your own message. There is also a communication area for exchange between the pre and post processing. I know you're a developer, you probably should know that some exits are assembled and later called in a specific way and environment. SMF exits can for example do some I/O, issue WTOs, calling other services, etc., but then only if it is documented and usable. For what is worth, I don't know if z/OS is _actively suppressing_ undocumented things like I/O for exits or just let you have a nasty Abend plus dumps. >Or am i mistaken..I was thinking about somehow talking to LOGGER ... LOGGER? What LOGGER? System Logger? Syslog? LOGREC? SMF exits/macros used to write out something? Or something else? Or, if you can, why are you asking or what are you trying to solve? Groete / Greetings Eladus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
