John Gilmore wrote:
Is it a consensus best practice to restrict read access of syslog/operlog
data to those people with a need-to-know?
It is not, not least because the question itself is not well-formed.
Need-to-know is a useful notion for highly sensitive information that lends
itself to
On Thu, 17 May 2012 09:07:26 -0400, Mark Jacobs mark.jac...@custserv.com
wrote:
Is it a consensus best practice to restrict read access of
syslog/operlog data to those people with a need-to-know, or is it a UACC
of READ appropriate?
I think this varies on a shop by shop basis. In all shops
I believe the general case is always need-to-know. That is, there needs to be
some business/technical justification for access.
The rational is to deny information to a potential intruder. I read that most
intruders are those that already have some level of access to the system.
In 4fb4f80e.30...@custserv.com, on 05/17/2012
at 09:07 AM, Mark Jacobs mark.jac...@custserv.com said:
Is it a consensus best practice to restrict read access of
syslog/operlog data to those people with a need-to-know,
Pretty much anybody running jobs has a need to know what their jobs
put in
| Is it a consensus best practice to restrict read access of
| syslog/operlog data to those people with a need-to-know?
It is not, not least because the question itself is not well-formed.
Need-to-know is a useful notion for highly sensitive information that
lends itself to misuse in the wrong
W dniu 2012-05-15 20:33, Mark Zelden pisze:
What's wrong???
User error? :-)Did you change the SYSID or anything like that?
When you use the LOG command do you see an ISPF short message
error?
Try SYSID ? and see what it says.
Then SYSID with no operands.
1. SYSID
SYSID *was
R. Skorupka wrote:
I just noticed that syslog is dead.
Hmm, I have gone with this thread to see, but, Ok, can you perhaps explore
these other options? (if already discussed, I may have missed it, sorry) :
Did you checked your ISFPRMxx member? Or drop those exits you mentioned earlier.
Is it
http://www-01.ibm.com/support/docview.wss?uid=isg1OA39170
It's quite fresh.
BTW: very interesting problem for lawyers:
I changed sysid to meet SCRT requirements, otherwise SCRT cannot prepare
correct report for the LPAR running this system.
I can say I cannot change sysid due to error in IBM
R.Skorupka wrote:
http://www-01.ibm.com/support/docview.wss?uid=isg1OA39170
Interesting that SDSF suffers from JES2 handling of $QSE control block. Hmmm...
It's quite fresh.
Absolutely! Despite its age, it is now 'CLOSED PER'.
... and you have to carry out the local fix, which you already
W dniu 2012-05-16 12:42, Elardus Engelbrecht pisze:
[...]
I changed sysid to meet SCRT requirements, otherwise SCRT cannot
prepare correct report for the LPAR running this system.
Yuck! Could you be kind to elaborate on this required change? I'm
also using this SCRT toy every month.
SCRT
R Skorupka wrote:
SCRT does require all systems to have uniques SYSID. This requirement is
described in SCRT manual.
Oh yes, I now rereaded that part. Thanks for the reminder.
SCRT is REALLY BAD product, I know several cases where it gives false results
even if you fulfill all the
W dniu 2012-05-16 13:42, Elardus Engelbrecht pisze:
[1] - You just can't go on a C ALL '= ' '=*NONE' spree without breaking
something ...
But you can split the job stream. I moved DD * content to separate
members and DO NOT change them. Also the JCL itself is (almost) not
changed. The only
R Skorupka wrote:
[1] - You just can't go on a C ALL '= ' '=*NONE' spree without breaking
something ...
But you can split the job stream. I moved DD * content to separate members and
DO NOT change them. Also the JCL itself is (almost) not changed. The only
change is to replace object code.
On Wed, 16 May 2012 11:14:36 +0200, R.S. r.skoru...@bremultibank.com.pl wrote:
W dniu 2012-05-15 20:33, Mark Zelden pisze:
What's wrong???
User error? :-)Did you change the SYSID or anything like that?
When you use the LOG command do you see an ISPF short message
error?
Try SYSID ?
@bama.ua.edu] On Behalf Of
R.S.
Sent: Wednesday, May 16, 2012 6:57 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Syslog missing (now: SCRT)
W dniu 2012-05-16 13:42, Elardus Engelbrecht pisze:
[1] - You just can't go on a C ALL '= ' '=*NONE' spree without breaking
something ...
But you can split
On Wed, 16 May 2012 12:19:55 +0200, R.S. r.skoru...@bremultibank.com.pl wrote:
http://www-01.ibm.com/support/docview.wss?uid=isg1OA39170
It's quite fresh.
MAS panel shows:
OLD1 DRAINED,P
NEW1 ACTIVE
(system is not sysplexed, PLEXCFG=MONOPLEX)
Based on you mas display, that sounds like a
In 4fb286ac.8030...@bremultibank.com.pl, on 05/15/2012
at 06:39 PM, R.S. r.skoru...@bremultibank.com.pl said:
I just noticed that syslog is dead.
Maybe, and maybe not.
Any clue?
Yes; query the status of HAEDCPY, OPERLOG and SYSLOG. Then examine
your SDSF, taking the query results into
Do you have the HLQ.HASPINDX dataset that SDSF needs to access SYSLOG?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
R.S.
Sent: Tuesday, May 15, 2012 11:39 AM
To: IBM-MAIN@bama.ua.edu
Subject: Syslog missing
The following scenario:
On Tue, 15 May 2012 18:39:08 +0200, R.S. r.skoru...@bremultibank.com.pl wrote:
The following scenario:
z/OS 1.13 during ServerPac installation process.
The system is IPLed for second or third time, almost nothing is customized.
I just noticed that syslog is dead.
Example: I enter SDSF, LOG and
On Tue, 15 May 2012 11:45:28 -0500, Williamson, James R
james.r.william...@uscg.mil wrote:
Do you have the HLQ.HASPINDX dataset that SDSF needs to access SYSLOG?
hlq.HASPINDX is no longer used / required as of z/OS 1.11.
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
-MAIN@bama.ua.edu
Subject: Re: Syslog missing
Do you have the HLQ.HASPINDX dataset that SDSF needs to access SYSLOG?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf
Of R.S.
Sent: Tuesday, May 15, 2012 11:39 AM
To: IBM-MAIN@bama.ua.edu
Subject
Thanks.
I just went from 1.10 to 1.12
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Mark Zelden
Sent: Tuesday, May 15, 2012 11:50 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Syslog missing
On Tue, 15 May 2012 11:45:28 -0500
W dniu 2012-05-15 18:47, Mark Zelden pisze:
On Tue, 15 May 2012 18:39:08 +0200, R.S.r.skoru...@.com.pl wrote:
The following scenario:
z/OS 1.13 during ServerPac installation process.
The system is IPLed for second or third time, almost nothing is customized.
I just noticed that syslog is
What about WRITELOG START...?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
if you do a 'pre syslog' from SDSF, and then do an 'ST', do you have a
SYSLOG STC in the system?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf
Of R.S.
Sent: Tuesday, May 15, 2012 1:03 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Syslog missing
On Tue, 15 May 2012 19:02:57 +0200, R.S. r.skoru...@bremultibank.com.pl wrote:
Don't know why it broke, but have you tried this?
V SYSLOG,HARDCPY
Yes, no effect
Try W START (WRITELOG START)
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
W dniu 2012-05-15 19:25, Mark Zelden pisze:
On Tue, 15 May 2012 19:02:57 +0200, R.S.r.skoru...@.com.pl wrote:
Don't know why it broke, but have you tried this?
V SYSLOG,HARDCPY
Yes, no effect
Try W START (WRITELOG START)
I tried, no effect.
I just re-ipled system, with no
f 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
R.S.
Sent: Tuesday, May 15, 2012 2:20 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Syslog missing
W dniu 2012-05-15 19:25, Mark Zelden pisze:
On Tue, 15 May 2012 19:02:57 +0200
On Tue, 15 May 2012 20:20:28 +0200, R.S. r.skoru...@bremultibank.com.pl wrote:
W dniu 2012-05-15 19:25, Mark Zelden pisze:
On Tue, 15 May 2012 19:02:57 +0200, R.S.r.skoru...@.com.pl wrote:
Don't know why it broke, but have you tried this?
V SYSLOG,HARDCPY
Yes, no effect
Try W
On Tue, 15 May 2012 18:31:00 +, Jousma, David david.jou...@53.com wrote:
Try LOG S?Maybe your are defaulting to OPERLOG which you appear to have
turned off.
Right... didn't think about that. The IBM default is operlog if operlog is
active, but
the ISPF profile could be set to
On Tue, 15 May 2012 13:41:11 -0500, Mark Zelden m...@mzelden.com wrote:
On Tue, 15 May 2012 18:31:00 +, Jousma, David david.jou...@53.com wrote:
Try LOG S?Maybe your are defaulting to OPERLOG which you appear to have
turned off.
Right... didn't think about that. The IBM default is
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
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,HARDCOPY,ROUTE
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
V HARDCPY,SYSLOG
I think.
--
John McKown
Maranatha!
Sent from my Vibrant Android phone.
On Jun 27, 2011 9:05 AM, Oapos;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.
Hi Ted,
how often? - sems like every other week.
how much can you store? - at least one years data per system, in HSM ML2.
keeps it simple, no need to be concerned with sopme other archive system.
On Fri, 10 Jun 2011 16:36:13 +, Ted MacNEIL eamacn...@yahoo.ca
wrote:
Not sure I would want
Dunno what zip you guys use, but I zipped a 171 Million byte
file into 14 Million bytes, for a 12.2 compression ratio,
which is what I would expect for pure text with lots of blanks.
I typically see 6 or 8 to one for more complex data like SMF.
Barry Merrill
Not sure I would want SYSLOG to be trapped into an output archive.
We use SDSF to grab the previous day's log, midnight to midnight, and then
purge older data.
The data gets stored into a system/datetime stamped dataset.
Making it so very useful for data miningjust using SRCHFOR across a
Probably 6-8 years ago, I contributed a system called SOUT to the CBT tape.
I was trying to find it on the CBT site, but I'm not having much luck.
There used to be a link that listed all the files - I can't find it for some
reason. I don't know if its not there, or more likely I'm just not
On Fri, 10 Jun 2011 10:37:20 -0500, Eric Bielefeld eric-ibmm...@wi.rr.com
wrote:
Probably 6-8 years ago, I contributed a system called SOUT to the CBT tape.
I was trying to find it on the CBT site, but I'm not having much luck.
There used to be a link that listed all the files - I can't find it
Not sure I would want SYSLOG to be trapped into an output archive.
Not sure it's trapped.
Indexing by date is (usually) easier.
I've done it three ways:
1. Date stamped datasets -- preferable to:
2. GDGs and,
3. Output archivers
I prefer #3, especially with indexing and (in most) compression.
Ted,
Just a quick question. Since syslog is vbm the amount of compression would seem
to me so small (considering the content). How much compassion was seen?
Ed
Sent from my iPad
On Jun 10, 2011, at 11:36 AM, Ted MacNEIL eamacn...@yahoo.ca wrote:
Not sure I would want SYSLOG to be trapped
Since the log is generally full of text, I would expect a 2:1 ratio
like on Open systems.
On Fri, Jun 10, 2011 at 1:38 PM, Ed Gould ps2...@yahoo.com wrote:
Ted,
Just a quick question. Since syslog is vbm the amount of compression would
seem to me so small (considering the content). How much
Thanks Mark. After looking at the links you posted, one of them showed my
name. I never thought of searching on my name. That brings up 3 entries.
When I searched for SOUT, or SYSOUT, I got hundreds of entries just using
Google to search the CBT site. I finally did notice that if I click on
Since the log is generally full of text, I would expect a 2:1 ratio like on
Open systems.
2.6
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email
Sent: Wednesday, June 08, 2011 5:27 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SYSLOG saving
So more of these posts have made me think. There is no reason that
some of those other shops I mentioned that had more general products
(as opposed to some that specifically manage syslog or have components
Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Mark Zelden
Sent: Wednesday, June 08, 2011 5:27 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SYSLOG saving
So more of these posts have made me think. There is no reason that
some of those other shops I mentioned that had more general
Subject:Re: SYSLOG saving
Sent by:IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
I've worked many places over the years and have seen it all(SAR, $AVRS,
etc). Honestly, keeping a daily syslog offload in a disk based GDG,
that gets migrated to tape after 5 days still seems
Sam:
We had multiple reasons why we didn#39;t let syslog out of the systems group.
It might have been for several reasons (take your pick)
1. The production people couldn#39;t be trusted with this.
2. We needed access at times when the package was not available(systems down
time)
3. Auditors
We offload to a daily disk GDG, that migrates to tape. That way
multiple people can do syslog archaeology and not wait on each other.
_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris,
On Wed, 8 Jun 2011 08:47:38 -0500, Donald Likens dlik...@infosecinc.com wrote:
In my previous shop we used a product called $AVRS to retain SYSLOG
for an extended period of time. I assume other shops do the same. I
need it in a readable format with as much information as possible.
If you save
I do it the old fashioned way:
1. Create GDGs
2. Issue a '
Don:
I do it the old fashioned way:
1. Create GDGs
2. Issue a 'WRITELOG' and then a proc like this
//HPYCPY PROC
//IEFPROC EXEC PGM=IASXWR00,PARM='PL',REGION=200K
//*
//* WTR TO SCOOP UP SYSLOGS
//*
//IEFRDER DD
-MAIN@bama.ua.edu] On Behalf Of
Mark Zelden
Sent: Wednesday, June 08, 2011 10:07 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SYSLOG saving
On Wed, 8 Jun 2011 08:47:38 -0500, Donald Likens dlik...@infosecinc.com wrote:
In my previous shop we used a product called $AVRS to retain SYSLOG for
an extended
On Wed, 8 Jun 2011 13:43:32 -0400, Knutson, Sam sknut...@geico.com wrote:
Hi Mark,
My guess would be opposite that almost everyone has some output management
tool they leverage for SYSLOG archiving but I could be completely wrong.
Hi Sam,
Survey time? :-)
Based on my experience at well over
From: Mark Zelden m...@mzelden.com
To: IBM-MAIN@bama.ua.edu
Sent: Wed, June 8, 2011 3:35:57 PM
Subject: Re: SYSLOG saving
On Wed, 8 Jun 2011 13:43:32 -0400, Knutson, Sam sknut...@geico.com wrote:
Hi Mark,
My guess would be opposite that almost everyone has
Years ago, we brought in SAR (now CA-View) to hold customer batch report output
for viewing . So, we issue the W L command every midnight by auto command and
have View pick it up. We keep a little over 3 years of SYSLOG available, most
of that on (virtual) tape. It has worked very well for
Subject: Re: SYSLOG saving
Years ago, we brought in SAR (now CA-View) to hold customer batch report output
for viewing . So, we issue the W L command every midnight by auto command and
have View pick it up. We keep a little over 3 years of SYSLOG available, most
of that on (virtual) tape
@bama.ua.edu
Subject: Re: SYSLOG saving
Years ago, we brought in SAR (now CA-View) to hold customer batch report output
for viewing . So, we issue the W L command every midnight by auto command and
have View pick it up. We keep a little over 3 years of SYSLOG available, most
of that on (virtual) tape
We issue command W I at midnight and sweep the SYSLOG into Infopac
(ViewDirect).
We keep them for 90 days.
Greg Shirey
Ben E. Keith Company
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Mark Zelden
Sent: Wednesday, June 08, 2011 2:36 PM
Survey time? :-)
So more of these posts have made me think. There is no reason that
some of those other shops I mentioned that had more general products
(as opposed to some that specifically manage syslog or have components
that do) couldn't have used those products to store syslog. And maybe
more of those shops
Message -
From: Mark Zelden m...@mzelden.com
To: IBM-MAIN@bama.ua.edu
Sent: Wednesday, June 8, 2011 2:26:56 PM
Subject: Re: SYSLOG saving
So more of these posts have made me think. There is no reason that
some of those other shops I mentioned that had more general products
(as opposed to some
Gibney
Information Technology Services
Washington State University
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Mark Zelden
Sent: Wednesday, June 08, 2011 2:27 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SYSLOG saving
So more
that was
lacking or not even there yet, that of course has been a few years.
Scott J Ford
From: Mark Zelden m...@mzelden.com
To: IBM-MAIN@bama.ua.edu
Sent: Wed, June 8, 2011 5:26:56 PM
Subject: Re: SYSLOG saving
So more of these posts have made me think
I used to enjoy the exposure to HESC, but IBM dropped it soon after OCO.
So the committees started looking at packaged software for Windows and
*nix
that 'any third grader could maintain'. Lots of Boot Hill stories
abound...
In a message dated 6/8/2011 9:30:14 P.M. Central Daylight
John Norgauer wrote:
What is needed in the MPFLSTXX parm to suppress messages going to SYSLOG?
You can omit some of the routing codes that go to the hardcopy set and
assign those route codes to messages you want suppressed. For example:
|HARDCOPY DEVNUM(SYSLOG)
|
Turn on the no hardcopy bit in the message flagbytes 2
OICTXTRFB2,CTXTRNHC FORCE NO HARDCOPY
This will display it on the console but not on syslog
or
OICTXTRFB2,CTXTRDTMDELETE THE MESSAGE
This will not display on the console or on syslog
On Fri, Sep 18, 2009 at 8:06
John Norgauer wrote:
...
What is needed in the MPFLSTXX parm to suppress messages going to SYSLOG?
...
I do not recommend this on anything but a standalone sandbox system; it falls
under the category of tampering with evidence and an auditor would frown loudly.
That said, the literal answer
/01/2009 04:18 PM
Subject:
Re: SYSLOG-Routing codes
Sent by:
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
They are described in the introduction part of any volume of System
Messages
under Messages sent to hardcopy...: First 28 route codes.
Bob
Ron Wells wrote:
Guess I was too quick
but how does that translate to the msg??
N 0004000 XA91 09153 10:46:14.89 JOB13668
/\ how is this related to the code ??
or
N 280 XA91 09153 10:46:15.16 STC06759
/\
From:
Bob Rutledge deerh...@ix.netcom.com
To:
IBM-MAIN@bama.ua.edu
Date:
06/01/2009 04:18 PM
Subject:
Re
Ken
Thanks... a kick in the head but I got it ...
From:
Ken Porowski ken.porow...@cit.com
To:
IBM-MAIN@bama.ua.edu
Date:
06/02/2009 11:03 AM
Subject:
Re: SYSLOG-Routing codes
Sent by:
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
It's a bitmap of routing codes
0004000 is
Trying to interp routing code(s) on left side of syslog.
Is there a break down of the codes that are displayed and meanings??
example below
N C00 XA91 09152 14:33:02.95 0281 $HASP309 INIT 15
INACT
/\
Yes there is information.
In section 4.1.15 SYSLOG records
in the manual: z/OS V1R9.0 MVS Planning: Operations
Document Number: SA22-7601-08
should help you here.
Lizette
Trying to interp routing code(s) on left side of syslog.
Is there a break down of the codes that are displayed and
thanks
hit nail on the head...
From:
Lizette Koehler stars...@mindspring.com
To:
IBM-MAIN@bama.ua.edu
Date:
06/01/2009 02:46 PM
Subject:
Re: SYSLOG-Routing codes
Sent by:
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
Yes there is information.
In section 4.1.15 SYSLOG records
Guess I was too quick...
The beginning of the SYSLOG has
NR000 XA91 09152 15:10:44.93 STC06632 0080 IST097I VARY
ACCEPTED
/\ /\ This is the Prefix it talks about
/\/\/\/\/\/\/\ these are the codes from what I am
reading
But what is the 7digits ?
000filer ??
See the IHAHCLOG macro description of the format.
- Original Message -
From: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
To: IBM-MAIN@bama.ua.edu IBM-MAIN@bama.ua.edu
Sent: Mon Jun 01 15:45:44 2009
Subject: Re: SYSLOG-Routing codes
Guess I was too quick...
The beginning
see it say descriptor codes-7char guess I'm missing something..where
are the codes ?
From:
Field, Alan C. alan.c.fi...@supervalu.com
To:
IBM-MAIN@bama.ua.edu
Date:
06/01/2009 03:57 PM
Subject:
Re: SYSLOG-Routing codes
Sent by:
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
See
They are described in the introduction part of any volume of System Messages
under Messages sent to hardcopy...: First 28 route codes.
Bob
Ron Wells wrote:
Guess I was too quick...
The beginning of the SYSLOG has
NR000 XA91 09152 15:10:44.93 STC06632 0080 IST097I VARY
5 CYL is the size and has been for years.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at
Looked at all consoles and did not see any high NBUF.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at
On Sun, 26 Oct 2008 19:39:48 -0500, Mark Zelden
[EMAIL PROTECTED] wrote:
A console that was not rolling?
Mark,
That advice applied prior to the Console Restructure. After z/OS R4.2, we
moved the point where SYSLOG/OPERLOG is written -- it is now written
immediately after the SSI, prior to
On Mon, 27 Oct 2008 16:47:57 -0500, W. Kevin Kelley [EMAIL PROTECTED]
wrote:
On Sun, 26 Oct 2008 19:39:48 -0500, Mark Zelden
[EMAIL PROTECTED] wrote:
A console that was not rolling?
Mark,
That advice applied prior to the Console Restructure. After z/OS R4.2, we
moved the point where
On Sun, 26 Oct 2008 19:01:16 -0500, Salah [EMAIL PROTECTED] wrote:
Hello list, wondering if anyone had run into this before.
At 0600 we issue 'W H' command which writes the syslog to class H and start
a new syslog. All is well so far.
By 0800 the syslog stopped updating as seen in SDSF,
How large is your SYSLOG index for SDSF ??
Salah wrote:
Hello list, wondering if anyone had run into this before.
At 0600 we issue 'W H' command which writes the syslog to class H and start
a new syslog. All is well so far.
By 0800 the syslog stopped updating as seen in SDSF, although the
Subject
[EMAIL PROTECTED] Re: SYSLOG problem
.EDU
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=EZ2CMZ34DT=20031016134357
What command
: 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
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
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
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. The command
WRITELOG START perhaps???
See
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2G133/4.58.1?S
HELF=EZ2CMZ34DT=20031016134357
What command was issued to cause the problem in the first place? What
console messages did you get?
Regards,
Ulrich Krueger
-Original Message-
From:
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 IBM-MAIN@BAMA.UA.EDU
03/31/2008 01:04 PM
Please respond to
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
SYSLOG problem
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 the
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
Lizette Koehler [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
ink.net...
I have a fairly active system. Stuff going on all the time. But when
I look in my SYSLOG/OPERLOG I notice that I do not see a time stamp for
several minutes. If this system was not active, I could understand
On Wed, 20 Feb 2008 10:52:09 +0100, Vernooy, C.P. - SPLXM
[EMAIL PROTECTED] wrote:
There is something else you might look into: I think I remember that
messages for the operator console(s) appear in syslog and are
timestamped at the moment the messages is displayed on the console. So
if the
W. Kevin Kelley [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
On Wed, 20 Feb 2008 10:52:09 +0100, Vernooy, C.P. - SPLXM
[EMAIL PROTECTED] wrote:
There is something else you might look into: I think I remember that
messages for the operator console(s) appear in syslog and are
Lizette,
You could start an automatic command to do a D T (Display Time)
every 30 seconds for a day or two. That would let you know whether
you have a problem without too much additional log output.
Brent Looper
UAMS
I have a fairly active system. Stuff going on all the time. But
On Fri, 15 Feb 2008 11:39:03 -0500, Lizette Koehler
[EMAIL PROTECTED] wrote:
I have a fairly active system. Stuff going on all the time. But when I
look in my SYSLOG/OPERLOG I notice that I do not see a time stamp for
several minutes. If this system was not active, I could understand the gaps.
1 - 100 of 138 matches
Mail list logo
