Refreshing the Control-O Security Cache

Control‑O security modules use a security block to identify each user for which an authority check is performed. The first time a user’s security authorization is checked, Control‑O creates a security block for that user. The security block can then optionally be saved for the next time the user’s security authorization is checked.

Security blocks saved for subsequent checks are kept in the Control‑O Security Cache. The size of the security cache is defined in the RUNTCACH parameter in member CTOPARM. If 0 is specified for the RUNTCACH parameter, no security blocks are saved. For information, see the RUNTCACH parameter in the Control‑O chapter of the INCONTROL for z/OS Installation Guide: Installing.

The Control‑O Security Cache holds security blocks for only the last n users to have their security authorization checked, where n is the value specified for parameter RUNTCACH. For example, if parameter RUNTCACH contains a value of 10, the security cache holds a security block for each of the last ten users that were checked.

Changes made to a user’s security authorization since the last time that user’s security block was created are not automatically included in the information in the user’s security block in the Control‑O Security Cache. However if a user’s security authorization has been changed, and there is no security block in the Control‑O Security Cache for that user, changes made to the user’s security authorization are put into effect the next time that user’s security authorization is checked.

To immediately include new user authorization information in the Control‑O security cache, refresh the security cache using operator command

This command refreshes all user authorization information in the Control‑O security cache.

When the modification is accepted, the following message is displayed on the operator console: