How QUERY SECURITY works
- Whether SEC=YES or SEC=NO is specified in the system initialization parameters
- The value that is specified for the SECPRFX system initialization parameter
- Which resource classes are active
- Whether the transaction that is issuing the request is subject
to transaction routing, and if so:
- Which ATTACHSEC parameter was specified on the connection definition
- For RESTYPE('PSB') only, whether the PSBCHK system initialization parameter is specified as YES or NO
- QUERY SECURITY RESTYPE
- QUERY SECURITY RESCLASS
The SEC system initialization parameter
The SEC system initialization parameter specifies what level of external security you want CICS to use.
| SEC | RACF® Access | Query Security Read | Query Security Update | Query Security Control | Query Security Alter |
|---|---|---|---|---|---|
| YES |
NONE |
notreadable |
notupdatable |
notctrlable |
notalterable |
| NO | n/a | readable | updatable | ctrlable | alterable |
The SECPRFX system initialization parameter
QUERY SECURITY RESTYPE('FILE') RESID('PAYFILE')
- When SECPRFX=YES, CICS® applies the CICS region userid as a prefix, and calls RACF to check the user's access to cics_region_userid.PAYFILE.
- When SECPRFX=prefix, CICS applies the prefix that is supplied, and calls RACF to check the user's access to prefix.PAYFILE.
- If SECPRFX=NO is specified, CICS does not apply a prefix, and calls RACF to check the user's access to PAYFILE.
Resource class system initialization parameters
Table 1 shows how the QUERY SECURITY RESTYPE command works if the system initialization parameter for the relevant resource class (for example, XFCT) is active. If, however, the relevant Xname parameter is not active (for example, if XFCT=NO was specified), the resource is READABLE, UPDATABLE, CTRLABLE and ALTERABLE.
Transaction routing
When the QUERY SECURITY command is issued from a transaction that was routed to a remote system, CICS checks the link user's access to the specified resource, and the terminal user's access to the resource, if appropriate.
For more information, see IPIC link security, , or Link security with MRO, depending upon the environment you are using.
- ATTACHSEC on the connection definition must not be LOCAL (that is, it can be IDENTIFY, PERSISTENT, MIXIDPE, or VERIFY).
- PSBCHK=YES must be specified as a system initialization parameter in the remote system.