Graham, Syslog is a log and history of what has been going on in your system. Jobs that have run, messages written to syslog, etc...
Some shops archive it to dasd as a GDG to keep it around in-case they need to go back and research an issue. So the choices are 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 On my test sandbox, I will typically purge it as I do not need to do historical research. In production I write it to SAR for later review if needed. So it will depend on your requirements. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Graham Hobbs Sent: Saturday, May 11, 2013 7:09 PM To: [email protected] Subject: SYSLOG Hello, NQ: Trying to keep my SD;O list short. I find 15 of the following thereon: SYSLOG STC00002 +MASTER+ 144 C STD LOCAL 70 SYSLOG STC00018 +MASTER+ 128 C STD LOCAL 3,536 SYSLOG STC00052 +MASTER+ 128 C STD LOCAL 3,499 SYSLOG STC00091 +MASTER+ 128 C STD LOCAL 3,592 I see nothing therein of interest to me except the third field seems to be a date. Mine run from 13074 to 13129. Do I need to keep them, some, none, all? Please thanks. Graham Hobbs NQ=Novice question ---------------------------------------------------------------------- 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
