Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
RACROUTE REQUEST=VERIFY or VERIFYX processing z/OS Security Server RACF System Programmer's Guide SA23-2287-00 |
|
The RACROUTE REQUEST=VERIFY function does identification and verification
of users and determines whether work is allowed to enter the system.
Some of the events that can cause VERIFY request processing to occur
are:
Some of the checks done by REQUEST=VERIFY processing are:
For certain callers (RACROUTE REQUEST=VERIFY), specifying SYSTEM=YES on the RACROUTE requests can provide better performance. For more information, see z/OS Security Server RACROUTE Macro Reference. Specifying a session type of OMVSSRV can also improve performance.
When a RACROUTE REQUEST=VERIFY or RACROUTE REQUEST=VERIFYX macro specifies
the OMVSSRV session type:
Callers of RACROUTE REQUEST=VERIFY may also realize improved performance when the impact of INITSTATS statistics recording is lessened. An installation can specify that, when a user is verified by a particular application, statistics should be recorded only if no recording has been done for that user that day. When an application specifies the APPL operand on the RACROUTE REQUEST=VERIFY request, the system administrator can use a profile in the APPL class to control which users can access the application, and can limit INITSTATS processing to collect daily statistics only. To limit INITSTATS processing to collect daily statistics only, the system administrator specifies the string 'RACF-INITSTATS(DAILY)' in the APPLDATA field of the APPL class profile. For more information, refer to z/OS Security Server RACF Security Administrator's Guide, |
Copyright IBM Corporation 1990, 2014
|