You should use a cron job to signal syslogd at midnight, along with date stamps in the log file directory names, to organize log files by year (%Y), month (%m), and day (%d), only if you do not use the automatic archive function of syslogd. See z/OS Communications Server: IP Configuration Guide for more information about configuring syslogd for automatic archiving. Because both of these methods rely on creating new log files, results could be unpredictable if you try to use both methods together.
The -F parameter specifies the access permissions (modes) for the file if the file must be created dynamically. This parameter has no effect if the file already exists.
Restriction: You cannot specify the -F parameter with the -N or -X parameter.
The -D parameter specifies the access permissions (modes) for the directory part of the file name if the directory (or directories) containing the file must be created dynamically. This parameter has no effect on a directory that already exists.
Restriction: You cannot specify the -D parameter with the -N or -X parameter.
auth.* /tmp/syslogd/auth.log -F 640 -D 770You can specify the -N parameter following the file name to specify automatic archival options. The -N parameter is mutually exclusive with the -X parameter.
You should use the -N or -X parameter only if you do not use a cron job to signal syslogd at midnight, along with date stamps in log file directory names, to organize log files by year (%Y), month (%m), and day (%d). See z/OS Communications Server: IP Configuration Guide for more information about offloading log files. Because both of these methods rely on creating new log files, results could be unpredictable if you try to use both methods together.
Restriction: You cannot specify the -N parameter with the -F or -D parameter.
The -N parameter specifies a unique qualifier to append to the data set prefix specified on the previous instance of the BeginArchiveParms statement. This prefix forms the base archive data set name. Additional information is appended to the base name to form the complete archive data set name. The format of the additional information depends on the type of data set. You can specify either a GDG or a sequential data set.
The syslogd application requires the correct SAF authorization to create the target data sets that are needed for archival purposes.
For a GDG data set, specify (+1) at the end of the qualifier value. For example, -N TRACE(+1). The GDG specifiers (+0) and (-n) are not valid. The complete archive data set name for a GDG data set is:
prefix.qualifier.gdg_suffix
If you use GDG data sets as an archive destination, the GDG BASE must already have been created. Also, be aware of the maximum number of generation data sets to be kept for the GDG. It is possible for syslogd to write more than one archive to the GDG per day, because of the multiple triggers used to perform archives. For example, if you keep five generation data sets, and syslogd performs five archives in one day, you are effectively retaining only a single day's worth of data.
See the information about configuring syslogd for automatic archival in z/OS Communications Server: IP Configuration Guide for sample JCL to create a GDG BASE. See z/OS DFSMS Using Data Sets for more information about GDG data sets.
For a sequential data set do not specify the GDG indicator (+1). The complete archive data set name for a sequential data set is as follows:
prefix.qualifier.date_suffix.time_suffix
auth.* /tmp/syslogd/auth.log -N TRACEYou can specify the-X parameter following the file name to indicate that the contents of the z/OS UNIX file should be deleted when an archive event occurs. This effectively reinitializes the file without saving the contents. The -X parameter is mutually exclusive with the -N parameter.
Restriction: You cannot specify the -X parameter with the -F or -D parameter.
Requirement: The MVS operlog stream must be active for syslogd to be able to write to it.
bpxroot.*.*.crit;uswmaint.*.*.crit $SMF