Skip to Content
Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

Setting up security

This section describes how to set up security for RUV.

In many processes that RUV performs, update access to secured files is required. If your site uses a security package, you may need to alter access availability for users who submit backups or other processing requests. You must ensure that all jobs which perform logging have access to the journal and log data sets.

RUV components, especially repository data sets, often require security beyond the security that is provided by the system security manager. The system security manager is typically compatible with the Resource Access Control Facility (RACF).

Success

Tip

Use of RUV product security is not required, but BMC Software recommends that you use it.

RACF/ACF2 requirements should be documented for the IEESYS process that is used by the BLDINDEX function.

For information about the correct procedure for defining a user ID for a started task in your environment, see your security system (RACF/ACF2) manual. The IEESYSAS associated address space has its security profile propagated from the address space that spawns it, and it has the same access as the spawning address space.

The ISPF interface can run in INQUIRE mode or UPDATE mode. Mode selection is determined at execution by preestablished RACF authorization to the subsystem data sets (REGISET and REGISET2).

Warning

Note

To customize ACF2, you can use the RUVSAF macro. See examples in the RUVZFAC member of the HLQ.SOURCE library.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Recovery for VSAM 4.1