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
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?
--
Mark Jacobs
Time Customer Service
Tampa, FL
Learn from yesterday, live for today, hope for tomorrow.
The important thing
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
.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Mark Jacobs
Sent: Thursday, May 17, 2012 8:07 AM
To: IBM-MAIN@bama.ua.edu
Subject: Syslog/Operlog Read Access
Is it a consensus best practice to restrict read access of syslog/operlog data
to those
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
| 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
SYSID WRNG - and could not enter LOG (no msg)
MAS panel shows:
OLD1 DRAINED,P
NEW1 ACTIVE
(system is not sysplexed, PLEXCFG=MONOPLEX)
2. SYSLOG - OPERLOG
My log default is SYSLOG, previously I had OPERLOG only if Operlog is
active on your system.
I enter syslog by typing LOG or LOG S.
WHen I
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
issued SYSID NEW1 - no effect
I issued SYSID OLD1 - and could not enter LOG (no msg)
I issued SYSID WRNG - and could not enter LOG (no msg)
MAS panel shows:
OLD1 DRAINED,P
NEW1 ACTIVE
(system is not sysplexed, PLEXCFG=MONOPLEX)
2. SYSLOG - OPERLOG
My log default is SYSLOG, previously I had OPERLOG
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.
SYSID NEW1 - no effect
I issued SYSID OLD1 - and could not enter LOG (no msg)
I issued SYSID WRNG - and could not enter LOG (no msg)
MAS panel shows:
OLD1 DRAINED,P
NEW1 ACTIVE
(system is not sysplexed, PLEXCFG=MONOPLEX)
2. SYSLOG - OPERLOG
My log default is SYSLOG, previously I had OPERLOG only
@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
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 issue /D A,L - the results are not
recorded in the log (last entry in the log
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
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
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
mailto:m
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
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
to OPERLOG from a past use or from the parms.
I always forget about that because I've had an exit in place since OS/390 1.2
that
forces SYSLOG as the default unless you explicitly use LOG O.
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:m...@mzelden.com
is operlog if operlog is
active, but
the ISPF profile could be set to OPERLOG from a past use or from the parms.
I always forget about that because I've had an exit in place since OS/390 1.2
that
forces SYSLOG as the default unless you explicitly use LOG O.
After thinking about this a little
hi all,
is it possible to issue a console command via CONSOLE+GETMSG in a rexx
without the resulting messages occurring in the syslog?
thanks for your help
stephen
---
Dr. Stephen Fedtke
Enterprise-IT-Security.com
Seestrasse 3a
CH-6300 Zug
Switzerland
Tel. ++41-(0)41-710-4005
www.enterprise
hi all,
is it possible to issue a console command via CONSOLE+GETMSG in a rexx
without the
resulting messages occurring in the syslog?
thanks for your help
stephen
---
Dr. Stephen Fedtke
Enterprise-IT-Security.com
I am not sure about your environment, but in mine we have CA
Stephen,
you wrote syslog, -- I write SYSLOG in majuscel as seen in IBM manuals
as abbrevation for system log. You did not ask for OPERLOG, hardcopy
log, operator console, master console etc (I am not sure about
permutation of minuscel and majuscel). Then, SYSLOG as described in MVS
Planning
From: Robert Payne
Sent: Friday, February 17, 2012 2:46 PM
To: Fred Hoffman
Subject: RE: Assembler Control of SYSLOG Messages
Looks like DESC code 11 on the WTO macro would work;
DESC=(descriptor code...) Specifies one or more descriptor codes as
decimal numbers in the range 1-16
On Wed, 25 Jan 2012 11:24:22 -0500, Graham Hobbs gho...@cdpwise.net wrote:
Am an app developer on Dallas VIC, they clutter my O option, always seems to
be around sixteen of them
You may want to ask the question to zTech zt...@us.ibm.com. In my experience
the people there are competent and very
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@bama.ua.edu
Sent: Thursday, January 26, 2012 6:27 AM
Subject: Re: SDSF;O SYSLOG files?
On Wed, 25 Jan 2012 11:24:22 -0500, Graham Hobbs gho...@cdpwise.net
wrote:
Am an app developer on Dallas VIC, they clutter my O option, always seems
=
NP JOBNAME JobIDOwnerPrty C FormsDest Tot-Rec
SYSLOG STC2 +MASTER+ 144 C STD LOCAL 70
SYSLOG STC00018 +MASTER+ 128 C STD LOCAL
Graham,
Those output files are used to pull together the syslog that you see in S.LOG.
There's nothing in the system that automatically deletes them, but you may have
a an automated command in your shop that purges them, say, after 5 days.
In our shop, we purge them after three days with a JES
=* SYSNAME=
NP JOBNAME JobIDOwnerPrty C FormsDest Tot-Rec
SYSLOG STC2 +MASTER+ 144 C STD LOCAL 70
SYSLOG STC00018 +MASTER+ 128 C STD LOCAL
In 0325CA44BA4240A3B3FB8684A49D05C2@graham, on 01/25/2012
at 11:24 AM, Graham Hobbs gho...@cdpwise.net said:
May I safely purge them?
Your system programmer may hate you if he needs to diagnose a problem
and the history is gone. Same for the dumps. Ask the people who will
be looking at them
25, 2012 11:24 AM
Subject: SDSF;O SYSLOG files?
Hello,
Newby question please .. I have these SYSLOG's on my SDSF ..
SDSF OUTPUT ALL CLASSES ALL FORMSLINES 291,034 LINE 1-21 (35)
COMMAND INPUT ===SCROLL ===
CSR
PREFIX=* DEST=(ALL) OWNER
The ASID is available at the point just before the message is sent to the
console. Our SyzMPF/z product gets the messages before they go to hardcopy
(you can have SyzMPF/z keep them from getting there if you want), and one of
the fields that I have access to (and we allow you to use in the
-
From: IBM Mainframe Discussion List
[mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Brian Westerman
Sent: Wednesday, October 19, 2011 2:38 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: z/OS SYSLOG observation / thought
The ASID is available at the point just before the message is
sent
Sent: Wednesday, October 19, 2011 8:20 AM
Subject: Re: z/OS SYSLOG observation / thought
We don't have that product. And we basically have no money for any new product.
But we do have CA-OPS/MVS. Maybe I can pervert it to do that.
--
John McKown
Systems Engineer IV
IT
Administrative Services
Life and Health Insurance Company.SM
-Original Message-
From: IBM Mainframe Discussion List
[mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Scott Ford
Sent: Wednesday, October 19, 2011 8:25 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: z/OS SYSLOG observation / thought
John,
Yeah, I
Columns 41 through 48 in the z/OS SYSLOG (formatted with a 4 digit year in
columns 21-27) have various information in them. For many messages, it is the
JES assigned number such as JOB12345. For a commands and command responses it
appears to the be console name or for a MLWTO response
On 18 October 2011 13:29, McKown, John john.mck...@healthmarkets.com wrote:
Columns 41 through 48 in the z/OS SYSLOG (formatted with a 4 digit year in
columns 21-27) have various information in them. For many messages, it is the
JES assigned number such as JOB12345. For a commands and command
@bama.ua.edu
Sent: Tuesday, October 18, 2011 1:29 PM
Subject: z/OS SYSLOG observation / thought
Columns 41 through 48 in the z/OS SYSLOG (formatted with a 4 digit year in
columns 21-27) have various information in them. For many messages, it is the
JES assigned number such as JOB12345. For a commands
.
would have far too complex although I had started to look that way. The above
method is perfect (so far!) in that all commands that are executed by the
NetView user which would normally also show in the SYSLOG are now suppressed
from the SYSLOG (using ECHOONLY is nice as it does show what command
Sebastian,
One item that you may want to consider. Display commands might be fine for
something like this, but consider commands that do something like z rod or
confit etc. These commands IMO should be logged so you can have accountability.
Auditors should be asking about items like this.
Ed
running as he's
the one that actually implements this feature. However, you can still use
MVSPARM.MSGIFAC=SYSTEM if you so desire.
Regards,
Alan.
Is there anyway I can suppress the output from
these commands from the SYSLOG
TIA,
Sebastian
from joblog
to keep the message from the entire SYSLOG:
OICTXTRFB2,CTXTRDTM Suppress from hardcopy syslog
The other way, (which is much simpler) is to use a product that can do this for
you. Strangely enough, we happen to market a very inexpensive one that does
the above and many
Hi,
I am trying to locate the SYSLOG format of different verions of the MVS, XA, SP,
OS/390. Z/OS, etc, Operating system. Is this documented anywhere?
Specifically I need to know the offset of the SYSID, DATE, and TIME fields.
Thanks,
Bill
On Thu, 1 Sep 2011 08:28:42 -0500, Bill Hecox bill.he...@mail.com wrote:
Hi,
I am trying to locate the SYSLOG format of different verions of the MVS, XA,
SP,
OS/390. Z/OS, etc, Operating system. Is this documented anywhere?
Specifically I need to know the offset of the SYSID, DATE, and TIME
Or look at HCL in the Data Areas manual.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at
There's a description at the start of each of the System Messages manuals
also.
- Don Imbriale
On Thu, Sep 1, 2011 at 11:45 AM, Gerri Booth - State of Wisconsin
gerri.bo...@wisconsin.gov wrote:
Or look at HCL in the Data Areas manual.
--snip-
I am trying to locate the SYSLOG format of different verions of the MVS, XA, SP,
OS/390. Z/OS, etc, Operating system. Is this documented anywhere?
Specifically I need to know the offset of the SYSID, DATE, and TIME
Hello,
I am running z/OS 1.12. and I use SYS1.MODGEN(IEZVX100) when I write
programs to go against the SYSLOG.
*/* DESCRIPTIVE NAME: COMMUNICATIONS TASK INSTALLATION EXIT @P6C*/
*/*ROUTINE PARAMETER LIST@P6A*/
Thanks...Guy M. Gates Jr.
TTI Z/OS
in the plex, the
SYSLOG is just full of these commands and their output making it hard to read
(as in problem determination in other areas.) Along with that we're also
implementing some JES2 monitoring which also issues JES2 commands via NetView
and these also show up in the SYSLOG
In a former life I was able to issue commands from the Netview automation table
and suppress them from syslog.
Not sure if this will work for you.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Sebastian Welton
Sent: Wednesday, August
OK, I couldn't find it in the two obvious places I looked, but where is the
default print class set for the SYSLOG dataset. I expected JESPARM, but it is
not making itself obvious.
Thanks,
Neal
--
For IBM-MAIN subscribe
Check out LOGCLS in IEASYSxx.
- Don Imbriale
On Thu, Aug 11, 2011 at 8:46 AM, Neal Eckhardt neckha...@cnyric.org wrote:
OK, I couldn't find it in the two obvious places I looked, but where is the
default print class set for the SYSLOG dataset. I expected JESPARM, but it
is not making itself
Neal,
what about using LOGCLS=x in your IEASYSxx (in your hlq.PARMLIB) ?
ciao Lutz
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Thanks guys, Not the obvious place, but as soon as you said it.
Neal
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the
Also look at you commands. ===W L
Is part of the midnight mover.
In a message dated 8/11/2011 8:37:31 A.M. Central Daylight Time,
neckha...@cnyric.org writes:
but as soon as you said it.
--
For IBM-MAIN
I think we will. Thank you all for commenting.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
R.S.
Sent: Sunday, July 10, 2011 11:29 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: DS8XXX Syslog Mirroring Question
W dniu 2011-07-08 23:22, Ward
start on JES and we don't have a
copy of syslog. We are a z/os V1.11 shop. Has anyone done this type of
DR before? If yes what are doing about the syslog? We stand to lose a
days worth of syslog information. Any comments, etc... welcome. Thanks
in advance.
My comment: why don't you mirror
We are mirroring our DISK and tape to a remote location for DR purposes.
About 3 weeks ago we did an exercise and brought the system up at the
remote location. It went great, except for one thing. Since we don't
mirror our page and spool we do a cold start on JES and we don't have a
copy of syslog
have a
copy of syslog. We are a z/os V1.11 shop. Has anyone done this type of
DR before? If yes what are doing about the syslog? We stand to lose a
days worth of syslog information. Any comments, etc... welcome. Thanks
in advance.
Could you offload your DR syslog to a mirrored disk and receive
We started down this path in the late 90s. At the time we were concerned
about the extra traffic required to mirror spool, so we didn't--and had to
cold start JES2 each time. Aside from losing syslog, we had no way of
telling where batch processing had left off. It might make a big
difference
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
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=IEA2BKA0DN=SA22-7627-21DT
Allan,
My colleague tried your suggestion, no joy.
V SYSLOG,HARDCPY,ROUT=ALL
D C,HC,L=Z
CNZ4100I 10.34.56 CONSOLE DISPLAY 609
CONSOLES MATCHING
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
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.
Yes, it may be 'trapped
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
it.
Eric Bielefeld
Sr. Systems Programmer
IBM Global Services Division
Dubuque, Iowa
414-477-7259
- Original Message -
From: Bruce Hewson bruce_hew...@hotmail.com
Not sure I would want SYSLOG to be trapped into an output archive.
We use SDSF to grab the previous day's log, midnight
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
Is it the Only option ?
On Thu, Jun 9, 2011 at 10:55 AM, Gibney, Dave gib...@wsu.edu wrote:
SYSLOG does
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of jagadishan perumal
Sent: Wednesday, June 08, 2011 9:46 PM
To: IBM-MAIN
Looking at the active SYSLOG task output is only a suggestion as to a work
around to see what is blocking your normal access. You have not provided
sufficient information for me to speculate as to what your actual problem is.
-Original Message-
From: IBM Mainframe Discussion List
Jag, can you go to SDSF.O, enter prefix syslog, and paste the top 5 lines?
Mine looks like:
SDSF OUTPUT ALL CLASSES ALL FORMS LINES 66,774,055 LINE 1-17 (556)
COMMAND INPUT ===, ,SCROLL ===,CSR
PREFIX=SYSLOG* DEST=(ALL) OWNER=* SORT=ISys
Hi,
JOBNAME JobIDOwnerPrty C FormsDest Tot-Rec
SYSLOG S0043748 +MASTER+ 96 L STD LOCAL 1,000,001
SYSLOG S0043748 +MASTER+ 96 L STD LOCAL 1,000,003
SYSLOG S0043748 +MASTER+ 96 L STD LOCAL 1,000,014
Jags, I need the heading lines:
, Display, Filter, View, Print, Options, Search, Help
---
SDSF OUTPUT ALL CLASSES ALL FORMS LINES 0 LINE 0-0 (0)
COMMAND INPUT ===,tso pigs
Its just the Log option from SDSF which hangs whenever we try to Open and
see any
error message or any system related messages.
Regards,
Jags
Jags
Are you using OPERLOG or SYSLOG? Are you issuing a LOG O command or just
the LOG command?
Since we cannot see your system you need to give
* DEST=(ALL) OWNER=* SYSNAME=
NP JOBNAME JobIDOwnerPrty C FormsDest Tot-Rec
SYSLOG S0043748 +MASTER+ 96 L STD LOCAL 1,000,001
SYSLOG S0043748 +MASTER+ 96 L STD LOCAL 1,000,003
SYSLOG S0043748 +MASTER+ 96
Jag, you have a good sized spool there. If you let the command go for a
minute or two, does it eventually come up?
Aside from that, I agree with the other poster who mentioned haspindx. Try
deleting it and reallocating it, then when the first person goes into SDSF,
it will be initialized, so
CONSOLES MATCHING COMMAND: D C
x this line isn't important
HARDCOPY LOG=(SYSLOG,OPERLOG) CMDLEVEL=CMDS
ROUT=(ALL)
Can you see the same
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 the most flexible.
We save something like 45 days worth of syslog.
It allows:
- more than one person
We have several GDDR/GDPS lpars that they did not want to spend any money on
output collection products. My solutions was to write a REXX SDSF exec to spin
thru SDSF output for SYSLOG, allocate a dataset and XD them all to it. The
exec then runs an IDCAMS to LISTC the dataset level and deletes
A bank I used to work for deemed syslog to be a 'legal document' that
needed exceptional care and feeding. My current shop does not take that
view (of course, I've never asked), but every shop should consider the
legal/audit side of the issue when determining how long to keep a day's
worth
1 - 100 of 349 matches
Mail list logo
