You see me confused. Either I'm missing some recent change or, I have never understood how comand processing really works and am just about to discover this...
This is my understanding (leaving out sysplex routing to drop that level of complexity): - SVC 34 (MGCR, MGCRE) is the programming interface to issue commands. It verifies the arguments and sends the command onto its journey through the system. No command authorization processing done yet. - The commands are presented to the SSI command listener routines (SSI function 10) in subsystem sequence, on after the other. - Finally the command is queued to the MVS command handler. SSI processing: - Each subsytem interested in commands sees each and every command (unless MGCEFAST has been set). - When a subsystem detects on if its commands, it marks it as "processed" (and of course, does whatever needs to be done to process the command). - When a subsystem sees a command marked "processed" it ignores the command. MVS command handler: - When the MVS command handler sees a command marked "processed" it ignores it. Otherwise it tries to interpret it as an MVS command (one of those commands described in the "MVS System Commands" manual). If this is correct, then neither SVC34 nor the MVS command handler can do authorization checking for subsystem commands. Each subsystem is responsible to do its own authorization checking (if at all). Again if this is correct, MGCEFAST can never be set for a "non-MVS" command, i.e. a command recognized by a SSI command listener, since it is "suppressing SSI" (BTW, I haven't found where MGCEFAST is documented.) Happy to learn where I'm wrong and how it really works. -- Peter Hunkeler CREDIT SUISSE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
