The MVS router

The system authorization facility (SAF) provides your installation with centralized control over security processing by using a system service called the MVS™ router. The MVS router provides a common system interface for all products providing and requesting resource control.

This topic contains Product-sensitive Programming Interface and Associated Guidance Information.

The resource-managing components and subsystems (such as CICS®) call the MVS router as part of certain decision-making functions in their processing, for example access control checking and authorization-related checking. These functions are called control points. This single SAF interface encourages the use of common control functions shared across products and across systems.

If RACF® is available in the system, the MVS router might pass control to the RACF router, which in turn invokes the appropriate RACF function. The parameter information and the RACF router table, which associates router invocations with RACF functions, determine the appropriate function. However, before calling the RACF router, the MVS router calls an optional installation-supplied security-processing exit, if one has been installed.

The system authorization facility and the SAF router are present on all MVS systems, even if RACF is not installed. Although the SAF router is not part of RACF, many system components and programs, such as CICS, invoke RACF through the RACROUTE macro and SAF. Therefore, installations can modify RACF parameter lists and do customized security processing within the SAF router. For information about how to code a SAF router exit, see z/OS Security Server RACF Messages and Codes.

For more information about the MVS router, see System authorization facility (SAF) in z/OS Security Server RACROUTE Macro Reference and ICHRTX00 - MVS Router Exit.

Passing control to a user-supplied ESM

Usually, a caller (such as CICSPlex® SM) invokes the MVS router and passes it request type, requester, and subsystem parameters through the RACROUTE exit parameter list. The MVS router uses these parameters and calls the router exit. When the router exit completes its processing, it passes a return code to the router.

If the return code is 0, the router invokes RACF. RACF reports the result of that invocation to the router by entering return and reason codes in register 15 and register 0, respectively. The router converts the RACF return and reason codes to router return and reason codes and passes them to the caller. The router provides additional information to the caller by placing the unconverted RACF return and reason codes in the first and second words of the router input parameter list.

If your installation does not use RACF, you can make the MVS router exit pass control to an alternative ESM. However, if you do so you must still provide CICSPlex SM with the RACF return and reason codes that it expects to receive. You set the router exit return code so that RACF is not invoked; and you simulate the results of a RACF invocation by coding the exit so that it places the RACF return and reason codes in the first and second fullwords of the router input parameter list. RACF return and reason codes are documented in the z/OS MVS Programming: Assembler Services Reference.

For more information about passing control to a user-supplied ESM, see Exit Routine Processing in z/OS MVS Installation Exits.



dfht55j.html | Timestamp icon Last updated: Sunday, 4 June 2017