Data Set Access Requirements

Starting Your Product › How to Complete the Required Manual Configuration › Configuration Tasks for the Base Component › Create Security Product Logon IDs › Data Set Access Requirements

Data Set Access Requirements

The following table summarizes the access requirements for CA OPS/MVS. When developing applications that update your own databases, then these databases 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.CCLXLOAD	Execute	OPSMAIN, OPSOSF, OPSECF, and all TSO users
OPS.CCLXEXEC	Read	OPSMAIN, OPSOSF, OPSECF, and all TSO users
OPS.CCLXCLS0	Read	OPSMAIN, OPSOSF, OPSECF, and all TSO users
OPS.OPSLOG	Read, write	OPSMAIN
OPS.SYSCHK1	Read, write	OPSMAIN
Logical Parmlib Concatenation	Read	OPSMAIN
OPS.CCLXHENU	Read	All authorized TSO users
OPS.CCLXPENU	Read	All authorized TSO users
OPS.CCLXMENU	Read	All authorized TSO users
OPS.CCLXSENU	Read	All authorized TSO users
OPS.CCLXTENU	Read	All authorized TSO users
OPS.CCLXOPEX	Read	All authorized TSO users and possibly OPSOSF

Note: If you are using SSMGA, you must also allocate the OPS.CCLXOPEX 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.