copy and paste this google map to your website or blog!
Press copy button and paste into your blog or website.
(Please switch to 'HTML' mode when posting into your blog. Examples: WordPress Example, Blogger Example)
RACROUTE REQUEST=VERIFY (standard form) - IBM RACROUTE REQUEST=VERIFY processing returns the same RACROUTE return code, informational error message, and auditing as done for a normal system entry attempt with an incorrect password
RACROUTE REQUEST=VERIFY: Identify and verify a RACF-defined user - IBM The RACROUTE REQUEST=VERIFY macro provides RACF® user identification and verification The macro instruction identifies a user and verifies that the user is defined to RACF and has done either of the following tasks:
RACROUTE REQUEST=VERIFY - IBM The RACROUTE macro with the REQUEST=VERIFY parameter determines if a userid is defined to an external security product and if the user has supplied a valid password, group name, submitter node, security label, or operator identification
RACROUTE (standard form) - IBM These return codes represent return codes from all invocations of the RACROUTE macro; for example, REQUEST=AUTH, REQUEST=VERIFY For specific information on the success or failure of the invocation in question, see the topic of this information that describes that invocation
RACROUTE REQUEST=AUTH (standard form) - IBM The most common way to create an ACEE is to issue a RACROUTE REQUEST=VERIFY, specifying ENVIR=CREATE After all RACROUTE invocations are complete, the invoker should issue RACROUTE REQUEST=VERIFY with ENVIR=DELETE specified, to delete the ACEE previously created
RACROUTE REQUEST=VERIFY (標準形式) - IBM RACROUTE REQUEST=VERIFY, ENVIR=CREATE 要求で ICR 付きの ICRX が指定されると、VERIFY はその ICR を使用して適切な RACF ユーザー ID を判別します。
RACROUTE REQUEST=VERIFY (execute form) - IBM Refer to the standard form of the RACROUTE REQUEST=VERIFY macro to determine additional parameters that are required by the time the RACROUTE service is invoked using the execute form of the macro
Activating and using the IDTA parameter in RACROUTE REQUEST=VERIFY - IBM The following is guidance information for application programmers looking to utilize the IDTA parameter in RACROUTE REQUEST=VERIFY The Identity Token (IDT) has many different scenarios for authentication, however the following two are the most useful:
RACROUTE REQUEST=VERIFY (Standard Form) - IBM specifies the name of the application issuing the RACROUTE REQUEST=VERIFY to verify the user's authority to access the application This saves the application from having to do a separate RACHECK