In order to validate a resource, the following fields in the AIPL must be supplied:
Contains AI$RES
Contains the hex resource code as defined in the RDT for the resource being checked. (CA-defined resources are found in the #AFLAGS macro in TSSVM MACLIB.)
Contains the two-byte resource code as defined in the RDT for he resource being checked. If a two-byte resource code is being used, AIREST must be set to x'FF' to signify the fact.
Contains the name of the resource to be validated.
Note: If you are indicating the name of an SFS resource (such as SFSCMD or DIRECTRY), the resource name cannot exceed 44 characters in length.
Contains the MACHINE LENGTH (actual length - 1) of the resource being validated
Contains composite one byte result of all access levels required to satisfy the request
Contains composite two byte result of all extended access levels required to satisfy the request (see note below).
Optionally contains the VOLSER if the resource being validated is an O/S data set
Contains the class for USERx validation
Note: Your application may use either AIRRACC or AIRRACCE, but not both. AIRRACC is maintained for existing applications that were written with support for one byte access levels. All new applications, or existing applications that require the two byte expanded access levels, should set AI$EXT in AIFLAG1 and use AIRRACCE instead.
Additionally, the following bit settings for AIFLAG1 are honored:
Do not log this resource validation request
The validation is being done for the privileged form of a CP command or diagnose.
AIACID contains a VM userid
An AI$INIT function was previously done for this ACID.
AIPL contains "extended access levels" in AIRRACCE.
If the resource is being validated on behalf of a logged on virtual machine, the AIACID field should contain the name of that virtual machine and AIF$VMID should be set in AIFLAG1. If the AIACID field is not filled in, the validation is processed against the issuer of the diagnose.
If the request is being done on behalf of another virtual machine, and the issuer has the MASTFAC attribute, the check is made under the restrictions (mode, facility, etc.) of the MASTFAC facility.
For more details on the use of MASTFAC, refer to the Command Functions Guide.
Other than access to the security diagnose (X'A0'), issuer needs no special authority from CA Top Secret in order to validate the resource access.
|
Copyright © 2008 CA.
All rights reserved.
|
|