z/OS JES2 Initialization and Tuning Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Protecting SYSLOG

z/OS JES2 Initialization and Tuning Guide
SA32-0991-00

Your security policy might require that you protect SYSLOG because it is the record of your systems daily activities.

To control SYSLOG, your security administrator defines a RACF® JESSPOOL profile for the data set, an appropriate universal access, and then grants access to the userids or groupids that need a different access. NODEB's SYSLOG profile could look like this:
NODEB.+MASTER+.*.*.*.?
If you also use security labels for controlling your data, note that the SYSLOG data set(s) also has the highest (SYSHIGH) security label in your installation, a label it inherited from the master address space when created.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014