Ed, Barbara, Lizette,
Thanks, am comfortable to know that I'm not purging anything critical since
if anything does go wrong am at Dallas's IIC disposal.
Cheers,
Graham
----- Original Message -----
From: "Ed Jaffe" <[email protected]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Sunday, May 12, 2013 11:03 AM
Subject: Re: SYSLOG
On 5/11/2013 7:40 PM, Lizette Koehler wrote:
1) Leave it on spool
2) Write it off to dasd (GDG or Source manager like $AVERS) using the
External Writer process.
3) Purge it
The "poor man's" approach to syslog management is to periodically kick off
a job that issues the 'W L' command ('L' would be your 'log' class') and
then copies syslog output to GDG via external writer. For example:
// COMMAND 'W L'
//WAIT10S EXEC PGM=BPXBATCH,PARM='pgm /bin/sleep 10s'
//IEFPROC EXEC PGM=IASXWR00,REGION=6M,PARM='PL'
//IEFRDER DD DSN=SYSLOG.ARCHIVE(+1),
// DATACLAS=SLOGARCH,
// LRECL=136,BUFNO=5,RECFM=VB,BLKSIZE=27998,
// DISP=(NEW,CATLG)
Some folks amend this process slightly to limit the archiving to logs over
'n' days old.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
