Thanks Peter, actually this is normally what happens, (they normally type "W" which defaults to CLOSE if it is running )and it is supposed to immediately open a new one, but because of the circumstances, this time it did not open the new one. (that was a first for us in the 8 years I've been here that it didn't open the new one) That's where our problem began.
We ended up doing a W START followed by a VARY SYSLOG,HARDCPY,CMDS to finally get it working. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Hunkeler Peter (KIUK 3) Sent: Tuesday, April 01, 2008 6:14 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: SYSLOG problem You don't need to stop the syslog (WRITELOG CLOSE). A WRITELOG command w/o operands closes and frees the current syslog and immediately opens a new one. Your process can then archive that just closed syslog file. -- Peter Hunkeler CREDIT SUISSE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
