Automatic archiving operates on eligible z/OS® UNIX files.
You can configure which files are eligible by specifying parameters
on individual rules. You can also configure global parameters that
affect the archive process and determine the destination data sets
for each file.
Before you begin
You need to protect the syslogd archive data sets using available
data set access controls to ensure that only authorized personnel
are allowed to read these data sets. Syslogd archive data sets might
contain sensitive information.
Procedure
Perform the following steps to configure the archive
details for each z/OS UNIX file:
- Specify the BeginArchiveParms statement in the syslogd
configuration file. The BeginArchiveParms statement specifies
a data set name prefix that is extended with a unique qualifier for
each file to be archived, for the set of rules that follows this statement.
- Specify the -N parameter on each rule that uses a z/OS UNIX file,
to mark the file as eligible for automatic archiving. You
can also specify the -X parameter on a rule, to indicate that the
file should be re-initialized when an archive event occurs. If you
do not specify the -N or -X parameters on a rule, then nothing happens
to the destination file when an archive event occurs.
If you use
generation data group (GDG) data sets as an archive destination, the
GDG base must already be created. The following sample JCL creates
a GDG base called USER1.SYSARCH.
//USER1X JOB MSGLEVEL=(1,1),MSGCLASS=D,NOTIFY=USER1
//GDGA EXEC PGM=IDCAMS
//*
//GDGMOD DD DSN=USER1.SYSARCH,
// VOL=SER=CPDLB1,
// UNIT=SYSALLDA,
// SPACE=(TRK,(0)),
// DCB=(LRECL=80,RECFM=FB,BLKSIZE=6800,DSORG=PS),
// DISP=(,KEEP)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE GENERATIONDATAGROUP -
(NAME(USER77.MYGDG) -
EMPTY -
NOSCRATCH -
LIMIT(255) )
For more information about GDG
data sets, see z/OS DFSMS Using Data Sets.