Previous Topic: Create Security Product Logon IDs

Next Topic: Provide TSO OPER Authority

Data Set Access Requirements

The following table summarizes the access requirements for CA OPS/MVS. If you develop applications that update your own databases, then they also need access. After you have started to use the product and written your own applications, you will need to provide access to your own REXX, CLIST, OPSEXEC, and possibly user ISPF data sets.

Data Set Name

Access

User IDs

OPS.xxx.RULES

Read, write

OPSMAIN and authorized TSO users

OPS.LOAD

Execute

OPSMAIN, OPSOSF, OPSECF and all TSO users

OPS.REXX

Read

OPSMAIN, OPSOSF, OPSECF and all TSO users

OPS.FBCLIST

Read

OPSMAIN, OPSOSF, OPSECF and all TSO users

OPS.OPSLOG

Read, write

OPSMAIN

OPS.SYSCHK1

Read, write

OPSMAIN

Logical Parmlib Concatenation

Read

OPSMAIN

OPS.HELP

Read

All authorized TSO users

OPS.OPSPLIB

Read

All authorized TSO users

OPS.OPSMLIB

Read

All authorized TSO users

OPS.OPSSLIB

Read

All authorized TSO users

OPS.OPSTLIB

Read

All authorized TSO users

OPS.OPSEXEC

Read

All authorized TSO users and possibly OPSOSF

Note: If you are using SSMGA, you must also allocate the OPS.OPSEXEC data set to the OPSMAIN procedure.

Important! Running CA OPS/MVS without giving its various address spaces enough authorization to access their data sets is the most common installation problem.