Protecting SYSLOG

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

To control SYSLOG, define a JESSPOOL profile for the data set, specifying an appropriate universal access, and then grant access to the user IDs or group names that need a different access.

For example:

RDEFINE JESSPOOL system-name.+MASTER+.SYSLOG.*.* UACC(NONE)
PERMIT system-name.+MASTER+.SYSLOG.*.* CLASS(JESSPOOL) ID(SMITH) ACCESS(ALTER)

Note: This example assumes that a SETROPTS GENERIC(classname) was previously issued to turn generics on for this class and that a SETROPTS REFRESH was then done.