A colleague asked me to post the following:
After an IPL this weekend one of our systems has no data in syslog. We user IOF
and if we look at SYSLOG it shows a MSGFILE and a LOG file but no data file. A
WRITELOG gets an error:
W L
Hi Everyone,
We have an issue with our syslog. The command was issued to stop the syslog
to write it out. Normally a new syslog is created. Unfortunately this time
that didn't happen. We are now using the logger data set on this partition,
just the hard copy. Does anyone know how to get a new
A "V SYSLOG,HARDCOPY,ROUTE=ALL" command should do the trick (or at
least give you a message for problem determination).
Check the MVS System Commands Manual SA22-7627-21 available here:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2G1A0/CCON
TENTS?SHELF=IEA2BKA0&DN=SA22-7627-21&
BUFFER LIMIT: 1000
No change.
Thank You,
Dave O'Brien
NIH Contractor
From: Staller, Allan [allan.stal...@kbmg.com]
Sent: Monday, June 27, 2011 10:22 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Syslog problem
A "V SYSLOG,HARD
On 6/27/2011 7:04 AM, O'Brien, David W. (NIH/CIT) [C] wrote:
After an IPL this weekend one of our systems has no data in syslog. We user IOF
and if we look at SYSLOG it shows a MSGFILE and a LOG file but no data file.
Did you try to start the log via the WRITELOG START command?
--
Edward E Ja
V HARDCPY,SYSLOG
I think.
--
John McKown
Maranatha! <><
Sent from my Vibrant Android phone.
On Jun 27, 2011 9:05 AM, "O'Brien, David W. (NIH/CIT) [C]" <
obrie...@mail.nih.gov> wrote:
A colleague asked me to post the following:
After an IPL this weekend one of our systems has no data in syslog.
Yukus, Mary J CIV USMEPCOM wrote:
Hi Everyone,
We have an issue with our syslog. The command was issued to stop the syslog
to write it out. Normally a new syslog is created. Unfortunately this time
that didn't happen. We are now using the logger data set on this partition,
just the hard copy.
Yukus, Mary J CIV USMEPCOM wrote:
Hi Everyone,
We have an issue with our syslog. The command was issued to stop the syslog
to write it out. Normally a new syslog is created. Unfortunately this time
that didn't happen. We are now using the logger data set on this partition,
just the hard copy.
"W START" possibly.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Yukus, Mary J CIV USMEPCOM
Sent: Monday, March 31, 2008 11:21 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SYSLOG problem
Hi Everyone,
We have an issue with our syslog. T
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Yukus, Mary J CIV USMEPCOM
Sent: Monday, March 31, 2008 09:21
To: IBM-MAIN@BAMA.UA.EDU
Subject: SYSLOG problem
Hi Everyone,
We have an issue with our syslog. The command was issued to stop the syslog
to write it out. Norm
Mary,
Look at the WRITELOG command in MVS to force the syslog to spool and start
another one.
To have the hardcopy message set recorded on the system log, enter:
V SYSLOG,HARDCPY
This should be all you need.
Lizette
>
>Hi Everyone,
>We have an issue with our syslog. The command was
Hey Mary,
Try command 'W START'
Jerry
"Yukus, Mary J CIV USMEPCOM" <[EMAIL PROTECTED]>
Sent by: IBM Mainframe Discussion List
03/31/2008 01:04 PM
Please respond to
IBM Mainframe Discussion List
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
SYSLOG problem
Hi Every
On Mon, 31 Mar 2008 11:20:32 -0500, Yukus, Mary J CIV USMEPCOM
<[EMAIL PROTECTED]> wrote:
>Hi Everyone,
>We have an issue with our syslog. The command was issued to stop the syslog
>to write it out. Normally a new syslog is created. Unfortunately this time
>that didn't happen. We are now using
Thanks for the help, we got it.
Mary
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Yukus, Mary J CIV USMEPCOM
Sent: Monday, March 31, 2008 11:21 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: SYSLOG problem
Hi Everyone,
We have an issue with our
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
-
:[EMAIL PROTECTED] On Behalf
Of Ulrich Krueger
Sent: Monday, March 31, 2008 12:18 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SYSLOG problem
WRITELOG START perhaps???
See
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2G133/4.58.1?S
HELF=EZ2CMZ34&DT=20031016134357
What command
keler 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 archiv
Discussion List Subject
<[EMAIL PROTECTED] Re: S
18 matches
Mail list logo
