Re: Syslog/Operlog Read Access
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 misuse in the wrong hands. >For syslog/.operlog the operative question should instead be: >Who, if anyone, needs to be prevented from accessing this information? >The answer will then usually be no minimally qualified user. While 'need to know' is a good argument [1] and I agree with your argument that minimally qualified user [2] should be kept away from SYSLOG / OPERLOG, I ask another set of questions before giving accesses. When deciding WHO may need to access such resources, I ask several questions, some of them are listed: 1. Do you really need to know, so you can perform your job? Examples please. On a postcard. I'm busy. 2. Can you make *useful* usage of those resources? 3. What is the supervisor/boss opinion? I weight all answers, needs, etc. before decisions. Sometimes they get a YES, while I should give a NO. :-p Please don't jump on me: I know for a fact that some unnamed vendor software can with a tweaking of options [3] display sensitive data like userid/password, control-fields, etc. Groete / Greetings Elardus Engelbrecht [1] - If you don't have any other arguments to start with. [2] - I have in the past some nosy users who tried out career limiting things! ;-) [3] -This is by design and is turned off by default. You better protect your 'F yyy,blah' modify command of course. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Syslog/Operlog Read Access
| 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 hands. For syslog/.operlog the operative question should instead be: Who, if anyone, needs to be prevented from accessing this information? The answer will then usually be no minimally qualified user. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Syslog/Operlog Read Access
In <4fb4f80e.30...@custserv.com>, on 05/17/2012 at 09:07 AM, Mark Jacobs 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 the log. In particular, consider messages for jobs that have already been purged. YMMV. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see <http://patriot.net/~shmuel/resume/brief.html> We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Syslog/Operlog Read Access
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. -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 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 is to not stop questioning. - Albert Einstein -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: Syslog/Operlog Read Access
On Thu, 17 May 2012 09:07:26 -0400, Mark Jacobs 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've been at sysprogs and operators get syslog. In many of them application programmers get it, but not in all shops. "End users" usually rarely if ever get access to it. OPERLOG is usually restricted to operations and sysprogs more often than not in my experience. From a non-sysprog perspective, all the extra messages would probably be more confusing than anything to an application programmer.Also, with many shops, due to consolidations or maybe a service provider with a sysplex of different business units or companies in the same sysplex, you wouldn't want the average programmer to be able to get to the syslog data from another LPAR via operlog. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Syslog/Operlog Read Access
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 is to not stop questioning. - Albert Einstein -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: *CNZ4201E OPERLOG HAS FAILED
>Its a MonoPlex. The Logger storage group volume Loger01 was fully exhausted >and we deleted some orphaned Log datasets and this Error message has stopped >popping. Hi Jags, For a case of data set storage exhaustion, I would expect to see messages IXG310, IXG311, IXG312 highlighting an offload failure. In addition to allocating more volumes for logger data sets, you can run an IEAMDBLG to move operlog data out of the log stream, or set up a retention period/ autodelete policy to keep the log stream data from consuming all the data sets. >Hi Nick, in this case If want to access operlog from ZOSA, how to switch? Hi Chen, If this hypothetical situation, if you had a two system sysplex with a DASDonly Operlog you could do one of two things to allow access on another system. 1) Migrate the logstream to the other system by a) disconnecting from operlog on ZOSB (V OPERLOG,HARDCPY,OFF)and b) then connect on ZOSA - or 2) 'upgrade' the logstream to a CF by a) disconnecting from operlog on ZOSB (V OPERLOG,HARDCPY,OFF)and b) updating the LOGR policy definition of the log steam to specify a structure name, and c) connecting on ZOSA and ZOSB -Nick Jones Logger L3 -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: *CNZ4201E OPERLOG HAS FAILED
Hi Nick, in this case If want to access operlog from ZOSA, how to switch? 2011/4/6 Nick Jones > Hi Jags, > > I see: > > >SYSPLEX.OPERLOG*DASDONLY* > > SYSNAME: ZOSB > >DUPLEXING: STAGING DATA SET > > DUPLEXING: STAGING DATA SET > > GROUP: PRODUCTION > > When you configure Operlog as a dasdonly log stream, you can only access it > from > one system in your sysplex at a time. Is operlog connected on system ZOSB > and > you are trying to use it on another system in your plex, perhaps ZOSA? > > -Nick Jones > Logger L3 > > -- > 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 http://bama.ua.edu/archives/ibm-main.html > -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: *CNZ4201E OPERLOG HAS FAILED
Hi, Its a MonoPlex. The Logger storage group volume Loger01 was fully exhausted and we deleted some orphaned Log datasets and this Error message has stopped popping. On Wed, Apr 6, 2011 at 7:04 PM, Nick Jones wrote: > Hi Jags, > > I see: > > >SYSPLEX.OPERLOG*DASDONLY* > > SYSNAME: ZOSB > >DUPLEXING: STAGING DATA SET > > DUPLEXING: STAGING DATA SET > > GROUP: PRODUCTION > > When you configure Operlog as a dasdonly log stream, you can only access it > from > one system in your sysplex at a time. Is operlog connected on system ZOSB > and > you are trying to use it on another system in your plex, perhaps ZOSA? > > -Nick Jones > Logger L3 > > -- > 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 http://bama.ua.edu/archives/ibm-main.html > -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: *CNZ4201E OPERLOG HAS FAILED
Hi Jags, I see: >SYSPLEX.OPERLOG*DASDONLY* > SYSNAME: ZOSB >DUPLEXING: STAGING DATA SET > DUPLEXING: STAGING DATA SET > GROUP: PRODUCTION When you configure Operlog as a dasdonly log stream, you can only access it from one system in your sysplex at a time. Is operlog connected on system ZOSB and you are trying to use it on another system in your plex, perhaps ZOSA? -Nick Jones Logger L3 -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: *CNZ4201E OPERLOG HAS FAILED
Please hit below commands and put output.. ( D EMCS ) ( D C,KEY=OPERLOG ) ( D GRS,RES=(SYSZCNZ,*) ) Also check if there has been any Plex defined system Ipled for upgrade if yes with what version... I see no Operlog structure in your output..since not connected... -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: *CNZ4201E OPERLOG HAS FAILED
Hi,
Apology for not being more precise. Ouput for the command : /D
LOGGER,LOGSTREAM.
D LOGGER,LOGSTREAM
IXG601I 12.20.54 LOGGER DISPLAY 02
INVENTORY INFORMATION BY LOGSTREAM
LOGSTREAM STRUCTURE
- -
ATR.CTSPLEX.ARCHIVE*DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
ATR.CTSPLEX.DELAYED.UR *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
ATR.CTSPLEX.MAIN.UR*DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
ATR.CTSPLEX.RESTART*DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
ATR.CTSPLEX.RM.DATA*DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
BBO.WAS.ERROR.LOG *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
CICSTS31.CICSVR.DFHLGLOG *DASDONLY*
CICSTS31.LOG.MODEL *DASDONLY*
CICSUSER.CICS2.DFHLOG *DASDONLY*
CICSUSER.CICS2.DFHSHUNT*DASDONLY*
CICSUSER.CICS2.DFHSHUNT*DASDONLY*
CICS1USR.CICS1.DFHLOG *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
CICS1USR.CICS1.DFHSHUNT*DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
IBMUSER.CICS1.DFHLOG *DASDONLY*
IBMUSER.CICS1.DFHSHUNT *DASDONLY*
SYSPLEX.LOGREC.ALLRECS *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
SYSPLEX.OPERLOG*DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
ZOSB.DFHLOG.MODEL *DASDONLY*
ZOSB.DFHSHUNT.MODEL*DASDONLY*
NUMBER OF LOGSTREAMS: 18
Do we have any luck on stopping this error.
Regards,
Jags
On Tue, Apr 5, 2011 at 11:54 AM, Barbara Nitz wrote:
> >2) OS Version is : 1.8
> The message id might have changed since then, as 1.8 is out of service. In
> any case, the D C,HC putput clearly shows that you still have a syslog and
> hence a hardcopy log.
>
> >3) Ouput of command : /D LOGGER,LOGSTREAM.
> You neglected to provide the status of the OPERLOG log stream. You also
> neglected to provide the error you're getting in sdsf when you try to
> access
> operlog and/or syslog.
>
> From your wording ("we are having a trouble in accessing the SYSLOG"), I
> also assume that you have a problem with SDSF, not with operlog. There
> shouldn't be any problem with issuing the commands in SDSF.U (the user
> log),
> as that doesn't access the hardcopy log for display.
>
> Barbara Nitz
>
> --
> 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 http://bama.ua.edu/archives/ibm-main.html
>
--
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 http://bama.ua.edu/archives/ibm-main.html
Re: *CNZ4201E OPERLOG HAS FAILED
>2) OS Version is : 1.8
The message id might have changed since then, as 1.8 is out of service. In
any case, the D C,HC putput clearly shows that you still have a syslog and
hence a hardcopy log.
>3) Ouput of command : /D LOGGER,LOGSTREAM.
You neglected to provide the status of the OPERLOG log stream. You also
neglected to provide the error you're getting in sdsf when you try to access
operlog and/or syslog.
>From your wording ("we are having a trouble in accessing the SYSLOG"), I
also assume that you have a problem with SDSF, not with operlog. There
shouldn't be any problem with issuing the commands in SDSF.U (the user log),
as that doesn't access the hardcopy log for display.
Barbara Nitz
--
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 http://bama.ua.edu/archives/ibm-main.html
Re: *CNZ4201E OPERLOG HAS FAILED
Hi, Output of the command : D C,HC : RESPONSE=ZOSB IEE889I 11.26.51 CONSOLE DISPLAY 468 MSG: CURR=0LIM=1500 RPLY:CURR=1LIM=20 SYS=ZOSB PFK=00 CONSOLEID --- SPECIFICATIONS --- SYSLOG COND=H AUTH=CMDS NBUF=N/A ROUTCDE=ALL NO CONSOLES MEET SPECIFIED CRITERIA 2) OS Version is : 1.8 3) Ouput of command : /D LOGGER,LOGSTREAM. RESPONSE=ZOSB IXG601I 11.28.00 LOGGER DISPLAY 669 INVENTORY INFORMATION BY LOGSTREAM LOGSTREAM STRUCTURE#CONN STATUS - --- -- ATR.CTSPLEX.ARCHIVE*DASDONLY* 01 IN USE SYSNAME: ZOSB DUPLEXING: STAGING DATA SET GROUP: PRODUCTION ATR.CTSPLEX.DELAYED.UR *DASDONLY* 01 IN USE SYSNAME: ZOSB DUPLEXING: STAGING DATA SET GROUP: PRODUCTION ATR.CTSPLEX.MAIN.UR*DASDONLY* 01 IN USE SYSNAME: ZOSB DUPLEXING: STAGING DATA SET GROUP: PRODUCTION ATR.CTSPLEX.RESTART*DASDONLY* 01 IN USE The entire command output was not able to paste since we are having a trouble in accessing the SYSLOG. Regards. Jags On Tue, Apr 5, 2011 at 11:27 AM, Barbara Nitz wrote: > >Also we are > >not able to access the LOG option from SDSF panel. > > What error message are you getting in SDSF? > > > The response to a v operlog,hardcpy command is a CNZ4100I message issued in > response to the internal command D C,HC: > > CNZ4100I 07.47.57 CONSOLE DISPLAY 041 > CONSOLES MATCHING COMMAND: D C,HC > MSG:CURR=0LIM=3000 RPLY:CURR=13 LIM=99SYS= PFK=00 > HARDCOPY LOG=(SYSLOG,OPERLOG) CMDLEVEL=CMDS > ROUT=(ALL) > LOG BUFFERS IN USE: 0 LOG BUFFER LIMIT: 1000 > > > What release of z/OS are you on? > > What *status* is your operlog logstream in? D logger,logstream > Barbara Nitz > > -- > 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 http://bama.ua.edu/archives/ibm-main.html > -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: *CNZ4201E OPERLOG HAS FAILED
>Also we are >not able to access the LOG option from SDSF panel. What error message are you getting in SDSF? The response to a v operlog,hardcpy command is a CNZ4100I message issued in response to the internal command D C,HC: CNZ4100I 07.47.57 CONSOLE DISPLAY 041 CONSOLES MATCHING COMMAND: D C,HC MSG:CURR=0LIM=3000 RPLY:CURR=13 LIM=99SYS= PFK=00 HARDCOPY LOG=(SYSLOG,OPERLOG) CMDLEVEL=CMDS ROUT=(ALL) LOG BUFFERS IN USE: 0 LOG BUFFER LIMIT: 1000 What release of z/OS are you on? What *status* is your operlog logstream in? D logger,logstream Barbara Nitz -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: *CNZ4201E OPERLOG HAS FAILED
Hi, I didnt find any IXG related messages, This error message was popping out at the Console and giving the below command didnt help it anymore. Also we are not able to access the LOG option from SDSF panel. We are not in Coupling facility its a DASD-only logstream only. Prior to this message we just got a message as : IEE828E SOME MESSAGES NOW SENT TO HARDCOPY. Output of the command :v operlog,hardcpy RESPONSE=ZOSB IEE889I 11.07.03 CONSOLE DISPLAY 795 MSG: CURR=0LIM=1500 RPLY:CURR=1LIM=20 SYS=ZOSB PFK=00 CONSOLEID --- SPECIFICATIONS --- SYSLOG COND=H AUTH=CMDS NBUF=N/A ROUTCDE=ALL OPERLOGCOND=H AUTH=CMDS NBUF=N/A ROUTCDE=ALL LOG BUFFERS IN USE:0 LOG BUFFER LIMIT: 1000 On Tue, Apr 5, 2011 at 11:07 AM, Barbara Nitz wrote: > >*CNZ4201E OPERLOG HAS FAILED > >/v operlog,hardcpy but no luck. > > What message exactly are you getting in response to that command? Did > operlog work before? > > Are you using a CF log stream or a DASD-only logstream? What is the status > of the operlog logstream? > > Were there any messages prefixed IXG around the time the cnz4201e appeared? > > Barbara Nitz > > -- > 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 http://bama.ua.edu/archives/ibm-main.html > -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: *CNZ4201E OPERLOG HAS FAILED
>*CNZ4201E OPERLOG HAS FAILED >/v operlog,hardcpy but no luck. What message exactly are you getting in response to that command? Did operlog work before? Are you using a CF log stream or a DASD-only logstream? What is the status of the operlog logstream? Were there any messages prefixed IXG around the time the cnz4201e appeared? Barbara Nitz -- 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 http://bama.ua.edu/archives/ibm-main.html
*CNZ4201E OPERLOG HAS FAILED
Hi, We are getting the below error message in our SR queue, for the given below message we gave the command : * /v operlog,hardcpy but no luck. *CNZ4201E OPERLOG HAS FAILED Could anyone please guide me on. Regards, Jags * -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
Thanks, Kevin. Linda - Original Message - From: "W. Kevin Kelley" To: IBM-MAIN@bama.ua.edu Sent: Friday, March 11, 2011 6:58:28 AM Subject: Re: operlog On Fri, 11 Mar 2011 03:45:05 +, Linda Mooney wrote: > >Is there a sample that does include the OPERLOG info that does not fit into the SYSLOG format? > The OPERLOG formatting program is called IEAMDBLG and it is provided in source (Assembly language) form and you can modify it however you wish to include or exclude information. You do not have to format the OPERLOG to look like the SYSLOG; you can format it however you like, if you're willing to modify the program. The MDB mappings are IEAVG132 (in SYS1.MACLIB) and IEAVM105 (in SYS1.MACLIB). They will show you what information is available. The SYSLOG mapping is IHAHCLOG (in SYS1.MODGEN). This will show you the information that is formatted into the SYSLOG. W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development -- 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 http://bama.ua.edu/archives/ibm-main.html -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
On Fri, 11 Mar 2011 03:45:05 +, Linda Mooney wrote: > >Is there a sample that does include the OPERLOG info that does not fit into the SYSLOG format? > The OPERLOG formatting program is called IEAMDBLG and it is provided in source (Assembly language) form and you can modify it however you wish to include or exclude information. You do not have to format the OPERLOG to look like the SYSLOG; you can format it however you like, if you're willing to modify the program. The MDB mappings are IEAVG132 (in SYS1.MACLIB) and IEAVM105 (in SYS1.MACLIB). They will show you what information is available. The SYSLOG mapping is IHAHCLOG (in SYS1.MODGEN). This will show you the information that is formatted into the SYSLOG. W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
Hi We will activate operlog. Thanks a lot! Best Regards, Jason Cai On Thu, 10 Mar 2011 16:58:03 +0800, ibmnew wrote: >Hi all > > Our shop is a single image on z/OS 1.11 > > Do we need to issue 'VARY OPERLOG,HARDCPY' command? > > Do the single image need OPERLOG? > >Any suggestion would be helpful! > You never "need" OPERLOG - be it monoplex or in a sysplex. Even though the main benefit of OPERLOG is thought to be a single source of "syslog" data from multiple systems in a sysplex, there can still be benefits in a monoplex. Some benefits are: 1) An extra source of "syslog" data in case the JES2 syslog is lost for some reason (purged, save process error, catastrophic error that forces a JES2 cold start, etc.). 2) Data gets written to the operlog even after JES2 is brought down. You will never see that data in the JES2 syslog. 3) SDSF provides use of the FILTER command for OPERLOG, but does not have any filter capability for syslog. VARY OPERLOG,HARDCPY is the way to activate the OPERLOG on a running system assuming you have met the prerequisites. The prerequisite is having the system logger configured. You would need to define a DASD ONLY logstream for the operlog. After it is activated via command, you would add this to your PARMLIB's CONSOLxx member so activates at the next IPL: HARDCOPY DEVNUM(SYSLOG,OPERLOG) Hope this helps. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ *** Please note the new URL for Mark's MVS Utilities *** -- 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 http://bama.ua.edu/archives/ibm-main.html -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
Hi Kevin, Is there a sample that does include the OPERLOG info that does not fit into the SYSLOG format? Thanks, Linda - Original Message - From: "W. Kevin Kelley" To: IBM-MAIN@bama.ua.edu Sent: Thursday, March 10, 2011 5:26:47 PM Subject: Re: operlog On Thu, 10 Mar 2011 12:11:55 -0600, Mark Zelden wrote: > >You never "need" OPERLOG - be it monoplex or in a sysplex. > >Even though the main benefit of OPERLOG is thought to be a single >source of "syslog" data from multiple systems in a sysplex, there can >still be benefits in a monoplex. Some benefits are: > >1) An extra source of "syslog" data in case the JES2 syslog is lost >for some reason (purged, save process error, catastrophic error that >forces a JES2 cold start, etc.). > >2) Data gets written to the operlog even after JES2 is brought down. >You will never see that data in the JES2 syslog. > >3) SDSF provides use of the FILTER command for OPERLOG, but does >not have any filter capability for syslog. > >VARY OPERLOG,HARDCPY is the way to activate the OPERLOG on a running >system assuming you have met the prerequisites. The prerequisite is >having the system logger configured. You would need to define a >DASD ONLY logstream for the operlog. > >After it is activated via command, you would add this to your PARMLIB's >CONSOLxx member so activates at the next IPL: > >HARDCOPY DEVNUM(SYSLOG,OPERLOG) > >Hope this helps. > A few other considerations: 1) The OPERLOG contains some information which is not available in the SYSLOG (we ran out of columns in the SYSLOG in which to place any more information). In particular, the message descriptor codes are available in the OPERLOG; they are not available in the SYSLOG. You can see what information is stored in the OPERLOG by taking a look at the MDB (Message Data Block) mapping. This is the same block we use to pass information to EMCS consoles. 2) The OPERLOG typically takes up more space than an equivalent SYSLOG for the same number of messages. 3) The OPERLOG is stored in binary form and must be formatted to be read. We provide a sample program in SYS1.SAMPLIB for formatting the OPERLOG into (readable) SYSLOG format. Note that information which cannot be fit into the SYSLOG format is ignored by the program. W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development -- 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 http://bama.ua.edu/archives/ibm-main.html -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
On Thu, 10 Mar 2011 12:11:55 -0600, Mark Zelden wrote: > >You never "need" OPERLOG - be it monoplex or in a sysplex. > >Even though the main benefit of OPERLOG is thought to be a single >source of "syslog" data from multiple systems in a sysplex, there can >still be benefits in a monoplex. Some benefits are: > >1) An extra source of "syslog" data in case the JES2 syslog is lost >for some reason (purged, save process error, catastrophic error that >forces a JES2 cold start, etc.). > >2) Data gets written to the operlog even after JES2 is brought down. >You will never see that data in the JES2 syslog. > >3) SDSF provides use of the FILTER command for OPERLOG, but does >not have any filter capability for syslog. > >VARY OPERLOG,HARDCPY is the way to activate the OPERLOG on a running >system assuming you have met the prerequisites. The prerequisite is >having the system logger configured. You would need to define a >DASD ONLY logstream for the operlog. > >After it is activated via command, you would add this to your PARMLIB's >CONSOLxx member so activates at the next IPL: > >HARDCOPY DEVNUM(SYSLOG,OPERLOG) > >Hope this helps. > A few other considerations: 1) The OPERLOG contains some information which is not available in the SYSLOG (we ran out of columns in the SYSLOG in which to place any more information). In particular, the message descriptor codes are available in the OPERLOG; they are not available in the SYSLOG. You can see what information is stored in the OPERLOG by taking a look at the MDB (Message Data Block) mapping. This is the same block we use to pass information to EMCS consoles. 2) The OPERLOG typically takes up more space than an equivalent SYSLOG for the same number of messages. 3) The OPERLOG is stored in binary form and must be formatted to be read. We provide a sample program in SYS1.SAMPLIB for formatting the OPERLOG into (readable) SYSLOG format. Note that information which cannot be fit into the SYSLOG format is ignored by the program. W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
On Thu, 10 Mar 2011 16:58:03 +0800, ibmnew wrote: >Hi all > > Our shop is a single image on z/OS 1.11 > > Do we need to issue 'VARY OPERLOG,HARDCPY' command? > > Do the single image need OPERLOG? > >Any suggestion would be helpful! > You never "need" OPERLOG - be it monoplex or in a sysplex. Even though the main benefit of OPERLOG is thought to be a single source of "syslog" data from multiple systems in a sysplex, there can still be benefits in a monoplex. Some benefits are: 1) An extra source of "syslog" data in case the JES2 syslog is lost for some reason (purged, save process error, catastrophic error that forces a JES2 cold start, etc.). 2) Data gets written to the operlog even after JES2 is brought down. You will never see that data in the JES2 syslog. 3) SDSF provides use of the FILTER command for OPERLOG, but does not have any filter capability for syslog. VARY OPERLOG,HARDCPY is the way to activate the OPERLOG on a running system assuming you have met the prerequisites. The prerequisite is having the system logger configured. You would need to define a DASD ONLY logstream for the operlog. After it is activated via command, you would add this to your PARMLIB's CONSOLxx member so activates at the next IPL: HARDCOPY DEVNUM(SYSLOG,OPERLOG) Hope this helps. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ *** Please note the new URL for Mark's MVS Utilities *** -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
"McKown, John" wrote in message news:. .. > > -Original Message- > > From: IBM Mainframe Discussion List > > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of chen lucky > > Sent: Thursday, March 10, 2011 7:56 AM > > To: IBM-MAIN@bama.ua.edu > > Subject: Re: operlog > > > > en.. What differences between these two log(SYSLOG and > > OPERLOG). Seems > > OPERLOG for multi-system.. > > > > 2011/3/10 McKown, John > > > > > We use the old style SYSLOG on SPOOL. We don't use OPERLOG at all. > > > > > I agree. OPERLOG seems to be a way to have a single, merged, system log in a Parallel Sysplex. We have a __basic__ sysplex, which means no CF. Which means we cannot have a merged OPERLOG. So we don't bother. We maintain separate SYSLOGs and just merge them using DFSORT. > > -- > John McKown OPERLOG requires a LOGSTREAM, which does not necessarily requires a CF. If you don't have a CF, you can't merge the syslogs of all systems in a single sysplex wide logstream, but you can use a Dasd Only Logstream to make Operlog run on your local system. Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
> -Original Message- > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of chen lucky > Sent: Thursday, March 10, 2011 7:56 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: operlog > > en.. What differences between these two log(SYSLOG and > OPERLOG). Seems > OPERLOG for multi-system.. > > 2011/3/10 McKown, John > > > We use the old style SYSLOG on SPOOL. We don't use OPERLOG at all. > > I agree. OPERLOG seems to be a way to have a single, merged, system log in a Parallel Sysplex. We have a __basic__ sysplex, which means no CF. Which means we cannot have a merged OPERLOG. So we don't bother. We maintain separate SYSLOGs and just merge them using DFSORT. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
Operlog has some additional functions, like a powerful FILTER command, to filter out the messages you are interested in, in stead of hopping through them via FIND commands. Kees. "Stan Weyman" wrote in message news:<63f312e6f4b4674a8f5ac4512c47ec8003ebe18...@mx06a.corp.emc.com>... > For a single image setup I would suggest you stay with SYSLOG. OPERLOG is > really nice if you want a sysplexed SYSLOG that has entries, by time, for all > of the sysplexed systems. It's easier than trying to eyeball multiple > syslogs. no one at my last employer was in a hurry to set it up so I did in > my copious free time > > Stan > > Stan Weyman > Senior Software Engineer > stan.wey...@emc.com > EMC² (508)249-3966 > where information lives > It is wise to keep in mind that neither > success nor failure is ever final... > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf > Of ibmnew > Sent: Thursday, March 10, 2011 3:58 AM > To: IBM-MAIN@bama.ua.edu > Subject: operlog > > Hi all > > Our shop is a single image on z/OS 1.11 > > Do we need to issue 'VARY OPERLOG,HARDCPY' command? > > Do the single image need OPERLOG? > > Any suggestion would be helpful! > > Best Regards, > > Jason Cai > > > -- > 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 http://bama.ua.edu/archives/ibm-main.html > > -- > 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 http://bama.ua.edu/archives/ibm-main.html For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
For a single image setup I would suggest you stay with SYSLOG. OPERLOG is really nice if you want a sysplexed SYSLOG that has entries, by time, for all of the sysplexed systems. It's easier than trying to eyeball multiple syslogs. no one at my last employer was in a hurry to set it up so I did in my copious free time Stan Stan Weyman Senior Software Engineer stan.wey...@emc.com EMC² (508)249-3966 where information lives It is wise to keep in mind that neither success nor failure is ever final... -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of ibmnew Sent: Thursday, March 10, 2011 3:58 AM To: IBM-MAIN@bama.ua.edu Subject: operlog Hi all Our shop is a single image on z/OS 1.11 Do we need to issue 'VARY OPERLOG,HARDCPY' command? Do the single image need OPERLOG? Any suggestion would be helpful! Best Regards, Jason Cai -- 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 http://bama.ua.edu/archives/ibm-main.html -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
en.. What differences between these two log(SYSLOG and OPERLOG). Seems OPERLOG for multi-system.. 2011/3/10 McKown, John > We use the old style SYSLOG on SPOOL. We don't use OPERLOG at all. > > -- > John McKown > Systems Engineer IV > IT > > Administrative Services Group > > HealthMarkets(r) > > 9151 Boulevard 26 * N. Richland Hills * TX 76010 > (817) 255-3225 phone * > john.mck...@healthmarkets.com * www.HealthMarkets.com > > Confidentiality Notice: This e-mail message may contain confidential or > proprietary information. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. HealthMarkets(r) is the brand name for products underwritten and > issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake > Life Insurance Company(r), Mid-West National Life Insurance Company of > TennesseeSM and The MEGA Life and Health Insurance Company.SM > > > > > -Original Message- > > From: IBM Mainframe Discussion List > > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of ibmnew > > Sent: Thursday, March 10, 2011 2:58 AM > > To: IBM-MAIN@bama.ua.edu > > Subject: operlog > > > > Hi all > > > > Our shop is a single image on z/OS 1.11 > > > > Do we need to issue 'VARY OPERLOG,HARDCPY' command? > > > > Do the single image need OPERLOG? > > > > Any suggestion would be helpful! > > > > Best Regards, > > > > Jason Cai > > > > > > -- > > 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 http://bama.ua.edu/archives/ibm-main.html > > > > > > -- > 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 http://bama.ua.edu/archives/ibm-main.html > -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: operlog
We use the old style SYSLOG on SPOOL. We don't use OPERLOG at all. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -Original Message- > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of ibmnew > Sent: Thursday, March 10, 2011 2:58 AM > To: IBM-MAIN@bama.ua.edu > Subject: operlog > > Hi all > > Our shop is a single image on z/OS 1.11 > > Do we need to issue 'VARY OPERLOG,HARDCPY' command? > > Do the single image need OPERLOG? > > Any suggestion would be helpful! > > Best Regards, > > Jason Cai > > > -- > 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 http://bama.ua.edu/archives/ibm-main.html > > -- 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 http://bama.ua.edu/archives/ibm-main.html
operlog
Hi all Our shop is a single image on z/OS 1.11 Do we need to issue 'VARY OPERLOG,HARDCPY' command? Do the single image need OPERLOG? Any suggestion would be helpful! Best Regards, Jason Cai -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG Question
On Thu, 3 Feb 2011 09:55:34 -0500, Carson, Brad wrote: >Hello, > >We've recently implemented sysplex OPERLOG in a CF structure on Jan. 20th, 2011. This past weekend we started getting the following messages: > >IXC585E STRUCTURE LCA_OPERLOG IN COUPLING FACILITY CFB1, >PHYSICAL STRUCTURE VERSION C73599B9 8DEB1D84, >IS AT OR ABOVE STRUCTURE FULL MONITORING THRESHOLD OF 80%. >ENTRIES: IN-USE: 9421 TOTAL: 10909, 86% FULL >ELEMENTS: IN-USE: 21908 TOTAL: 32546, 67% FULL > >The log offloaded last Thursday while one system was being IPL'd. After this is when these messages started. > >Here is how LCA_OPERLOG is defined in the CF: >/* SYSPLEX OPERATOR SYSLOG (OPERLOG) */ > STRUCTURE NAME(LCA_OPERLOG) > SIZE(25600) > INITSIZE(14336) > PREFLIST(CFB1) > >And the logstream definitions: >DATATYPE(LOGR) > >DEFINE STRUCTURE NAME(LCA_OPERLOG) >LOGSNUM(1) >MAXBUFSIZE(4096) > >DEFINE LOGSTREAM NAME(SYSPLEX.OPERLOG) >STRUCTNAME(LCA_OPERLOG) >HLQ(SYS0) >LS_DATACLAS(TSDLOGR) >LS_STORCLAS(STANDARD) >LS_SIZE(4096) >STG_DATACLAS(TSDLOGR) >STG_STORCLAS(STANDARD) >STG_SIZE(4096) >HIGHOFFLOAD(80) >LOWOFFLOAD(0) >AUTODELETE(YES) >RETPD(14) > > >We're confused. Did we set this up wrong? Any help and advice would be greatly appreciated. > > >/Brad >Sorry about the company inserted disclaimer below. Don't monitor these types of logstreams (operlog, logrec etc.). You can probably find rants from Barbara Nitz in the archives about it. The fix is to add this to your structure definition: FULLTHRESHOLD(0) Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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 http://bama.ua.edu/archives/ibm-main.html
OPERLOG Question
Hello, We've recently implemented sysplex OPERLOG in a CF structure on Jan. 20th, 2011. This past weekend we started getting the following messages: IXC585E STRUCTURE LCA_OPERLOG IN COUPLING FACILITY CFB1, PHYSICAL STRUCTURE VERSION C73599B9 8DEB1D84, IS AT OR ABOVE STRUCTURE FULL MONITORING THRESHOLD OF 80%. ENTRIES: IN-USE: 9421 TOTAL: 10909, 86% FULL ELEMENTS: IN-USE: 21908 TOTAL: 32546, 67% FULL The log offloaded last Thursday while one system was being IPL'd. After this is when these messages started. Here is how LCA_OPERLOG is defined in the CF: /* SYSPLEX OPERATOR SYSLOG (OPERLOG) */ STRUCTURE NAME(LCA_OPERLOG) SIZE(25600) INITSIZE(14336) PREFLIST(CFB1) And the logstream definitions: DATATYPE(LOGR) DEFINE STRUCTURE NAME(LCA_OPERLOG) LOGSNUM(1) MAXBUFSIZE(4096) DEFINE LOGSTREAM NAME(SYSPLEX.OPERLOG) STRUCTNAME(LCA_OPERLOG) HLQ(SYS0) LS_DATACLAS(TSDLOGR) LS_STORCLAS(STANDARD) LS_SIZE(4096) STG_DATACLAS(TSDLOGR) STG_STORCLAS(STANDARD) STG_SIZE(4096) HIGHOFFLOAD(80) LOWOFFLOAD(0) AUTODELETE(YES) RETPD(14) We're confused. Did we set this up wrong? Any help and advice would be greatly appreciated. /Brad Sorry about the company inserted disclaimer below. -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: Searching OPERLOG via SDSF:LOG
You can have a look at CBT file 513, but it isn't simple. angel luis dominguez sysprog - spain -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: Searching OPERLOG via SDSF:LOG
>(or 'f xx prev') lines at a time. For the Find command, you can set the limit higher than lines -- check out FINDLIM. Unfortunately, due to screen design, you can't scroll more than . IIRC, FINDLIM will allow 99 or 999; check it out to be sure. - Too busy driving to stop for gas! -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: Searching OPERLOG via SDSF:LOG
Geoff Davis wrote: >Many years ago, when last working on Z, I was shown how to search OPERLOG from SDSF by simply typing ?? (I fogot!) from the LOG screen. This brought up a panel similar to RMF reports whereby you could set start date/start time end date/end time and it would display only messages between these values. LOCATE command. Not a panel, but it brings you to a specific place. But I think you are probably confusing that panel with the PRINT panel which shows you the fields for begin/end lines as well as date/time start and end. >It's getting a little tedious searching through millions of messages when I can only F7 or F8 (or 'f xx prev') lines at a time. Go green, conserve your PF7 / PF8 keys! ;-D Use FINDLIM 999 >Thx for any/all info and sorry it's such a basic question, It is not a basic question! ;-D Groete / Greetings Elardus Engelbrecht -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: Searching OPERLOG via SDSF:LOG
Are you thinking of LOG O command? So long as you are setup for Syslog in Logstream, it will work and you use the same commands (FIND, etc...) in it as SYSLOG. When in LOG O you can use the FILTER command on the menu bar of SDSF to get just what you want. If you have OPS/MVS and access to OPSBROWSE, it is much faster than FILTER in SDSF. Lizette > Geoff Davis Wrote > > Hi Folks, > > Wondered if anyone has used an ISPF/SDSF panel to search OPERLOG? > > Many years ago, when last working on Z, I was shown how to search > OPERLOG from SDSF by simply typing ?? (I fogot!) from the LOG > screen. This brought up a panel similar to RMF reports whereby you > could set > start date/start time end date/end time and it would display only > messages > between these values. > > I've read the SDSF manual and Syslogger manual but can't find any > reference > to this command (whatever it was). > > Was this a user-written panel or is it supplied in SDSF? > > It's getting a little tedious searching through millions of messages > when I can > only F7 or F8 (or 'f xx prev') lines at a time. > > Thx for any/all info and sorry it's such a basic question, > -- 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 http://bama.ua.edu/archives/ibm-main.html
Searching OPERLOG via SDSF:LOG
Hi Folks, Wondered if anyone has used an ISPF/SDSF panel to search OPERLOG? Many years ago, when last working on Z, I was shown how to search OPERLOG from SDSF by simply typing ?? (I fogot!) from the LOG screen. This brought up a panel similar to RMF reports whereby you could set start date/start time end date/end time and it would display only messages between these values. I've read the SDSF manual and Syslogger manual but can't find any reference to this command (whatever it was). Was this a user-written panel or is it supplied in SDSF? It's getting a little tedious searching through millions of messages when I can only F7 or F8 (or 'f xx prev') lines at a time. Thx for any/all info and sorry it's such a basic question, Geoff -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG
On Thu, 15 Apr 2010 08:54:48 -0500, Nick Jones wrote: >If I understand it correctly... > >1) the log stream was in use No, at least according to the OP and the displays he issued. You suggested that there might be a failed persistent connections, but we now know that the problem was the level of the CDS. The OP can verify the above, but look back at the first post in this thread. He removed OPERLOG definitions, IPLed and issued some display commands. >2) the UPDATE was on a parameter that works with connections with the most >recent CDS (with SMDUPLEX) Yes >3) with a down level CDS the parameter is not updatable with connections. It had no connections. The error message was misleading saying it did have connections. > >Before the function allowing dynamic updates IxgRsnCodeStreamInuse was put >out in the code path there because it made sense, changing it now would be a >compatability issue. > >IxgRsnCodeStreamInuse does point to a need for a CDS update: > >Action: > >Re-issue the request when there >are no active connections to >the log stream. >Or move to the appropriate >release and LOGR CDS format >level. >... > Okay, I accept your explanation as to why, but it is still very misleading. Right after that action the 0810 RSNCODE doc states: "If you received this reason code from IXCMIAPU, see message IXG014E" In the OP's case, this is what IXG014E indicated: IXG014E LOGSTREAM SYSPLEX.OPERLOG IS CURRENTLY IN USE The RSNCODE action doc implies that the logstream is in use regardless of the CDS level. So while the code can't be changed, the current doc certainly could be. The RSNCODE doc could/should be updated to indicate the possibility that if the function being used is UPDATE and the CDS level is not at HBB7705, the logstream may not actually be in use (ignore IGX014E) and to move to the higher CDS level. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG
If I understand it correctly... 1) the log stream was in use 2) the UPDATE was on a parameter that works with connections with the most recent CDS (with SMDUPLEX) 3) with a down level CDS the parameter is not updatable with connections. Before the function allowing dynamic updates IxgRsnCodeStreamInuse was put out in the code path there because it made sense, changing it now would be a compatability issue. IxgRsnCodeStreamInuse does point to a need for a CDS update: Action: Re-issue the request when there are no active connections to the log stream. Or move to the appropriate release and LOGR CDS format level. ... Nick Jones Logger L3 -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG
On Wed, 14 Apr 2010 09:43:15 -0500, Mark Steely wrote: >Thanks to all who replied - the answer was I had to upgrade the LOGR to the new release level and then the updates work as expected. To update the LOGR definitions I had to add ITEM NAME(SMDUPLEX) NUMBER(1) to the LOGR definitions. > I haven't looked at all the reason codes, but if it really wasn't in use and the code indicated it was, that should be APARable.There should be a separate "not supported" RSNCODE. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG
Thanks to all who replied - the answer was I had to upgrade the LOGR to the new release level and then the updates work as expected. To update the LOGR definitions I had to add ITEM NAME(SMDUPLEX) NUMBER(1) to the LOGR definitions. Thank You -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Nick Jones Sent: Wednesday, April 14, 2010 8:54 AM To: IBM-MAIN@bama.ua.edu Subject: Re: OPERLOG On Tue, 13 Apr 2010 14:00:07 -0500, Mark Steely wrote: > >I have look in the archives - still can't find the answer. I am trying >to update a few parms in the OPERLOG definition. This is dasd only structure and we are z/os V1R11. When I try to update the parms I receive messages: >IXG014E LOGSTREAM SYSPLEX.OPERLOG IS CURRENTLY IN USE IXG002E LOGR >POLICY PROCESSING ENDED WITH RETCODE=0008 RSNCODE=0810 Are you trying an UPDATE LOGSTREAM or a DELETE LOGSTREAM? Dynamic updates aren't allowed if your LOGR CDS version is below HBB7705 level. Some keywords aren't allowed on any update with log stream connections. > >I have IPL and removed the operlog option. I have done several displays >and it shows nothing is using it. > >d logger,l,strname=OPERLOG >D LOGGER,CONN,LSNAME=sysplex.operlog,D You may have some failed persistent connections. If you see: # D LOGGER,C,LSN=log-stream-name shows number of connectors on this system equal to 0. # D LOGGER,L,LSN=log-stream-name shows number of connectors to the log stream greater than 0. this might be the case. You can try a SETLOGR FORCE,DISCONNECT,LSN=SYSPLEX.OPERLOG, on systems with failed persistent connections if this is the case: http://publibfi.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2G1A0/4.42.3 Nick Jones Logger L3 -- 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 http://bama.ua.edu/archives/ibm-main.html *** CONFIDENTIALITY NOTICE *** This e-mail message and all attachments transmitted with it may contain legally privileged and confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message from your system. Thank you. -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG
On Tue, 13 Apr 2010 14:00:07 -0500, Mark Steely wrote: > >I have look in the archives - still can't find the answer. I am trying to update a few parms in the OPERLOG definition. This is dasd only structure and we are z/os V1R11. When I try to update the parms I receive messages: >IXG014E LOGSTREAM SYSPLEX.OPERLOG IS CURRENTLY IN USE >IXG002E LOGR POLICY PROCESSING ENDED WITH RETCODE=0008 RSNCODE=0810 Are you trying an UPDATE LOGSTREAM or a DELETE LOGSTREAM? Dynamic updates aren't allowed if your LOGR CDS version is below HBB7705 level. Some keywords aren't allowed on any update with log stream connections. > >I have IPL and removed the operlog option. I have done several displays and it shows nothing is using it. > >d logger,l,strname=OPERLOG >D LOGGER,CONN,LSNAME=sysplex.operlog,D You may have some failed persistent connections. If you see: # D LOGGER,C,LSN=log-stream-name shows number of connectors on this system equal to 0. # D LOGGER,L,LSN=log-stream-name shows number of connectors to the log stream greater than 0. this might be the case. You can try a SETLOGR FORCE,DISCONNECT,LSN=SYSPLEX.OPERLOG, on systems with failed persistent connections if this is the case: http://publibfi.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2G1A0/4.42.3 Nick Jones Logger L3 -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG
>>IXG014E LOGSTREAM SYSPLEX.OPERLOG IS CURRENTLY IN USE >>IXG002E LOGR POLICY PROCESSING ENDED WITH RETCODE=0008 RSNCODE=0810 If IXCMIAPU tells you that IxgRsnCodeStreamInuse then you're not looking at the right definitions, either via command or in the IXCMIAPU job. When I had to redefine operlog logstream, the things I did were: 1. Check if any TSO user was stuck in SDSF-operlog. Cancel them mercilessly. 2. ro *ALL,V OPERLOG,HARDCPY,OFF Check via D C (better route this to all systems in the sysplex, too) that all systems complied and got rid of operlog. My LOGR policy is set up in such a way that I first delete the log stream, then the structure definition and then redefine them (first structure, then log stream). If the delete doesn't go through, *something* is still using the log stream. Bring out all the D logger commands to check again. But SDSF users were the only culprits in my experience. (Oh, and once things are redefined, v operlog back on.) Best regards, Barbara -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG
On Tue, 13 Apr 2010 14:00:07 -0500, Mark Steely wrote: > >I have look in the archives - still can't find the answer. I am trying to update a few parms in the OPERLOG definition. This is dasd only structure and we are z/os V1R11. When I try to update the parms I receive messages: >IXG014E LOGSTREAM SYSPLEX.OPERLOG IS CURRENTLY IN USE >IXG002E LOGR POLICY PROCESSING ENDED WITH RETCODE=0008 RSNCODE=0810 > >I have IPL and removed the operlog option. I have done several displays and it shows nothing is using it. > >d logger,l,strname=OPERLOG >D LOGGER,CONN,LSNAME=sysplex.operlog,D > >Any help would be appreciated. > Hmmm. What does "D C" tell you? What about "V OPERLOG,HARDCPY,OFF"? -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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 http://bama.ua.edu/archives/ibm-main.html
OPERLOG
I have look in the archives - still can't find the answer. I am trying to update a few parms in the OPERLOG definition. This is dasd only structure and we are z/os V1R11. When I try to update the parms I receive messages: IXG014E LOGSTREAM SYSPLEX.OPERLOG IS CURRENTLY IN USE IXG002E LOGR POLICY PROCESSING ENDED WITH RETCODE=0008 RSNCODE=0810 I have IPL and removed the operlog option. I have done several displays and it shows nothing is using it. d logger,l,strname=OPERLOG D LOGGER,CONN,LSNAME=sysplex.operlog,D Any help would be appreciated. Thank You *** CONFIDENTIALITY NOTICE *** This e-mail message and all attachments transmitted with it may contain legally privileged and confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message from your system. Thank you. -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: Read OPERLOG console log backwards fast
7; //SYSOUT DD SYSOUT=(,),OUTPUT=(*.JCL) //SYSUDUMP DD SYSOUT=(,),OUTPUT=(*.JCL) //SYSABOUT DD SYSOUT=(,),OUTPUT=(*.JCL) //SYSDBOUT DD SYSOUT=(,),OUTPUT=(*.JCL) //SORTIN DD DSN=&&ISFIN,DISP=(OLD,PASS) //SORTOUT DD SYSOUT=* //SYSINDD * SORT FIELDS=COPY /* //* //* RETRIEVE DATAFROM SYSLOG USING SDSF COMMANDS //* //SYSLOG EXEC PGM=SDSF //ISFINDD DISP=(OLD,PASS),DSN=&&ISFIN //MSGLOG DD DSN=&&SLOG,DISP=(NEW,PASS),SPACE=(CYL,(25,05),RLSE), //UNIT=WORK,DCB=(DSORG=PS,RECFM=FBA,LRECL=134,BLKSIZE=0) //*~ THIS IS THE SDSF PANEL //ISFOUT DD SYSOUT=* /* //* //* FILE-AID BATCH: TO SEARCH FOR STRING 'MV36'. //* USING 'IF=(1,0' TELLS FILEAID ANYWHERE IN THE RECORD //* OUTY = ALL RECORDS WHERE STRING IS FOUND. //* OUTN = ALL THE OTHERS. //* //FAMPEIR EXEC PGM=FILEAID,PARM='TSO' //DD01 DD DSN=&&SLOG,DISP=(OLD,PASS) //OUTY DD DSN=MVD.MV36.TEMPLOG.STUFF, // DISP=(,CATLG),UNIT=DISK,SPACE=(TRK,(320,10),RLSE), // DCB=(DSORG=PS,RECFM=FBA,LRECL=134,BLKSIZE=0) //OUTN DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSLIST DD SYSOUT=* //SYSTOTAL DD SYSOUT=* //SYSIN DD * $$DD01 USER IF=(1,0,C'MV36'),WRITE=OUTY,DFLT_WRITE=OUTN /* Hutchison, Gregory A. Oregon DOT DMVIS phone:503-945-7081 fax:503-945-5220 gregory.hutchi...@odot.state.or.us -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Miklos Szigetvari Sent: Friday, January 22, 2010 6:37 AM To: IBM-MAIN@bama.ua.edu Subject: Read OPERLOG console log backwards fast Hi Searching a "fast" method to read the last ( 1 hour or 5000 records ) entries from the OPERLOG or SDSF log -- Miklos Szigetvari Development Team ISIS Information Systems Gmbh tel: (+43) 2236 27551 570 Fax: (+43) 2236 21081 E-mail: miklos.szigetv...@isis-papyrus.com Info: i...@isis-papyrus.com Hotline: +43-2236-27551-111 Visit our Website: http://www.isis-papyrus.com --- This e-mail is only intended for the recipient and not legally binding. Unauthorised use, publication, reproduction or disclosure of the content of this e-mail is not permitted. This email has been checked for known viruses, but ISIS accepts no responsibility for malicious or inappropriate content. --- -- 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 http://bama.ua.edu/archives/ibm-main.html -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: Read OPERLOG console log backwards fast
You could offload the OPERLOG logstream to a sequential dataset, then search that. We offload ours daily, and archive it on disk for 5 days, then it migrates to tape. Prior to OPERLOG our SYSLOG was archived directly to tape, and then every Monday morning the same various people were bumping into each other to review weekend syslog for problems. _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G p 616.653.8429 f 616.653.8497 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Miklos Szigetvari Sent: Friday, January 22, 2010 9:37 AM To: IBM-MAIN@bama.ua.edu Subject: Read OPERLOG console log backwards fast Hi Searching a "fast" method to read the last ( 1 hour or 5000 records ) entries from the OPERLOG or SDSF log -- This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- 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 http://bama.ua.edu/archives/ibm-main.html
Read OPERLOG console log backwards fast
Hi Searching a "fast" method to read the last ( 1 hour or 5000 records ) entries from the OPERLOG or SDSF log -- Miklos Szigetvari Development Team ISIS Information Systems Gmbh tel: (+43) 2236 27551 570 Fax: (+43) 2236 21081 E-mail: miklos.szigetv...@isis-papyrus.com Info: i...@isis-papyrus.com Hotline: +43-2236-27551-111 Visit our Website: http://www.isis-papyrus.com --- This e-mail is only intended for the recipient and not legally binding. Unauthorised use, publication, reproduction or disclosure of the content of this e-mail is not permitted. This email has been checked for known viruses, but ISIS accepts no responsibility for malicious or inappropriate content. --- -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG issues 2 of 5 systems missing
Absolutely Brilliant and way too easy. Thanks Lizette > >Try issuing the command 'V OPERLOG,HARDCPY' on the two systems that aren't >writing to OPERLOG. > >You may need to forcibly disconnect those logstreams from the structure, >if they're what's broken. Try issuing the command 'd >logger,l,strname=OPERLOG' and 'D LOGGER,CONN,LSNAME=,D' >--- >Kevin McKenzie > >External Phone: 845-435-8282, Tie-line: 8-295-8282 >z/OS BCP SVT, Dept FXKA, Bldg 706/2D38 > > > >Lizette Koehler >Sent by: IBM Mainframe Discussion List >04/13/2009 04:45 PM >Please respond to >IBM Mainframe Discussion List > > >To >IBM-MAIN@bama.ua.edu >cc > >Subject >OPERLOG issues 2 of 5 systems missing > > > > > > >We are using OPERLOG for our SYSLOG. It seems that 2 of 5 systems are not >writing to OPERLOG. Are there any commands I can use to get the OPERLOG >structure working again? > >I did a D XCF,STR,STRNAME=OPERLOG and can see 3 of the 5 systems >connected. I am trying to see when the other two quit. Other than an >IPL, is there anyway to reconnect the OPERLOGs? > >Lizette > -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG issues 2 of 5 systems missing
Look at the vary hardcpy commands Example 1 To include all operator commands, responses, and status displays (except dynamic status displays) in the hardcopy message set, enter: V ,HARDCPY,STCMDS Example 2 To have the hardcopy message set recorded on the system log, enter: V SYSLOG,HARDCPY Example 3 To add routing codes 11, 12, 13, 17, and 44 to the routing codes already defined for the hardcopy message set, enter: V ,HARDCPY,AROUT=(11-13,17,44) Example 4 To have the hardcopy message set recorded on the operations log, enter: V OPERLOG,HARDCPY Jerry Whitteridge Mainframe Engineering Safeway Inc 925 951 4184 jerry.whitteri...@safeway.com If everything seems under control, you're just not going fast enough. > -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Lizette Koehler > Sent: Monday, April 13, 2009 1:46 PM > To: IBM-MAIN@bama.ua.edu > Subject: OPERLOG issues 2 of 5 systems missing > > We are using OPERLOG for our SYSLOG. It seems that 2 of 5 > systems are not writing to OPERLOG. Are there any commands I > can use to get the OPERLOG structure working again? > > I did a D XCF,STR,STRNAME=OPERLOG and can see 3 of the 5 > systems connected. I am trying to see when the other two > quit. Other than an IPL, is there anyway to reconnect the OPERLOGs? > > Lizette > > -- > 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 http://bama.ua.edu/archives/ibm-main.html > > "Email Firewall" made the following annotations. -- Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. == -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG issues 2 of 5 systems missing
Try issuing the command 'V OPERLOG,HARDCPY' on the two systems that aren't writing to OPERLOG. You may need to forcibly disconnect those logstreams from the structure, if they're what's broken. Try issuing the command 'd logger,l,strname=OPERLOG' and 'D LOGGER,CONN,LSNAME=,D' --- Kevin McKenzie External Phone: 845-435-8282, Tie-line: 8-295-8282 z/OS BCP SVT, Dept FXKA, Bldg 706/2D38 Lizette Koehler Sent by: IBM Mainframe Discussion List 04/13/2009 04:45 PM Please respond to IBM Mainframe Discussion List To IBM-MAIN@bama.ua.edu cc Subject OPERLOG issues 2 of 5 systems missing We are using OPERLOG for our SYSLOG. It seems that 2 of 5 systems are not writing to OPERLOG. Are there any commands I can use to get the OPERLOG structure working again? I did a D XCF,STR,STRNAME=OPERLOG and can see 3 of the 5 systems connected. I am trying to see when the other two quit. Other than an IPL, is there anyway to reconnect the OPERLOGs? Lizette -- 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 http://bama.ua.edu/archives/ibm-main.html -- 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 http://bama.ua.edu/archives/ibm-main.html
OPERLOG issues 2 of 5 systems missing
We are using OPERLOG for our SYSLOG. It seems that 2 of 5 systems are not writing to OPERLOG. Are there any commands I can use to get the OPERLOG structure working again? I did a D XCF,STR,STRNAME=OPERLOG and can see 3 of the 5 systems connected. I am trying to see when the other two quit. Other than an IPL, is there anyway to reconnect the OPERLOGs? Lizette -- 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 http://bama.ua.edu/archives/ibm-main.html
Re: OPERLOG IEAMDBLG and z/OS V1.9
>But even so, there is no reason that should cause you to lose operlog data. >Did the systems shut >down clean? Up until this morning, I would have said that yes, if there was a normal shutdown, operlog should not have lost records, not even when you're not using staging data sets. This morning I learned that even a system that is not connected to operlog, will not write to operlog etc can definitely have a connection to the operlog logstream/structure, and what's worse, can offload log stream data that during later IPL can cause the logstream to have lost records. How? Have one system in the plex that does NOT use operlog and that has it's own SMS/catalog structure that does NOT know the HLQ used for offloading operlog. Then use SDSF and use LOG O. You will be told 'Log not active', but the system nonetheless connects to the log stream and shows the operlog such as it is written to from other systems! You won't see anythign from your 'own' system, but if you don't leave operlog in sdsf until the *other* system is IPL'd, then yours is going to offload. Regards, Barbara NItz -- GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion! http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196 -- 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
Re: OPERLOG IEAMDBLG and z/OS V1.9
On Mon, 21 Jul 2008 16:45:38 -0400, Lizette Koehler <[EMAIL PROTECTED]> wrote: >We had to POR the two Mainframe systems to add some new DMX4 Hardware into our configuration. > >We are upgrading from DMX3000 to DMX4500 storage arrays. > >As as I know there were no CF changes included in this. Just the POR. > >Lizette > If by "two Mainframe systems" you mean you also have to CPCs, then you shouldn't have needed a sysplex wide IPL. But even so, there is no reason that should cause you to lose operlog data. Did the systems shut down clean? There are several logstream loss APARs I recall seeing recently via IBMLINK ASAP so if you can't find any explanation for the data loss you may want to search IBMLINK. Othewise just delete/define the logstream and move on. If you also have syslog, losing some operlog isn't critical. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: OPERLOG IEAMDBLG and z/OS V1.9
We had to POR the two Mainframe systems to add some new DMX4 Hardware into our configuration. We are upgrading from DMX3000 to DMX4500 storage arrays. As as I know there were no CF changes included in this. Just the POR. Lizette > >>I have run into a small problem with OPERLOG. So I thought I would redo >the IEAMDBLG program. So I went looking through the manuals, REDBOOKS, all >sorts of books/manuals to see what the ASSM and LKED requirements are. So >far no luck. >> >>I am guessing it is AC(0) and a straight LKED of >> >>NAME IEAMDBLG >> >>If anyone knows specifically where I can find the information on how to >assemble and link this module that would be great. >> > >It is in the source code in samplib: > >LINKAGE EDITOR ATTRIBUTES = REUS >AMODE = 31 >RMODE = 24 > >It doesn't need AC=1. > > >>We just Cold started our PLEX this weekend and OPERLOG seems to be the one >most affect and it is losing records. >> > >>Messages we now get in our SYSLOG Offload process are: >> >>ILG0001 RECORDS NOT AVAILABLE. IXGCONN-1 RETURN CODE 004, REASON CODE 0407 >>ILG0001 RECORDS NOT AVAILABLE. IXGBRWSE-2 RETURN CODE 004, REASON CODE 0405 >> >> >>I have looked those up, but am still clueless :-O >> >> > >Since you say you looked up the codes (in MVS Sysplex Services Reference, >correct / MVS Assembler Services Reference, correct?), I won't repeat what >it says, but it is a missing data condition. You have to rebuild the >logstream. > >RO *ALL,VARY OPERLOG,HARDCPY,OFF > >Then delete / define the logstream > >RO *ALL,VARY OPERLOG,HARDCPY > > >What do you mean by cold started? All systems down then re-IPL, or >new XCF couple data sets etc. > -- 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
Re: OPERLOG IEAMDBLG and z/OS V1.9
On Mon, 21 Jul 2008 15:56:07 -0400, Lizette Koehler <[EMAIL PROTECTED]> wrote: >I have run into a small problem with OPERLOG. So I thought I would redo the IEAMDBLG program. So I went looking through the manuals, REDBOOKS, all sorts of books/manuals to see what the ASSM and LKED requirements are. So far no luck. > >I am guessing it is AC(0) and a straight LKED of > >NAME IEAMDBLG > >If anyone knows specifically where I can find the information on how to assemble and link this module that would be great. > It is in the source code in samplib: LINKAGE EDITOR ATTRIBUTES = REUS AMODE = 31 RMODE = 24 It doesn't need AC=1. >We just Cold started our PLEX this weekend and OPERLOG seems to be the one most affect and it is losing records. > >Messages we now get in our SYSLOG Offload process are: > >ILG0001 RECORDS NOT AVAILABLE. IXGCONN-1 RETURN CODE 004, REASON CODE 0407 >ILG0001 RECORDS NOT AVAILABLE. IXGBRWSE-2 RETURN CODE 004, REASON CODE 0405 > > >I have looked those up, but am still clueless :-O > > Since you say you looked up the codes (in MVS Sysplex Services Reference, correct / MVS Assembler Services Reference, correct?), I won't repeat what it says, but it is a missing data condition. You have to rebuild the logstream. RO *ALL,VARY OPERLOG,HARDCPY,OFF Then delete / define the logstream RO *ALL,VARY OPERLOG,HARDCPY What do you mean by cold started? All systems down then re-IPL, or new XCF couple data sets etc. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
OPERLOG IEAMDBLG and z/OS V1.9
I have run into a small problem with OPERLOG. So I thought I would redo the IEAMDBLG program. So I went looking through the manuals, REDBOOKS, all sorts of books/manuals to see what the ASSM and LKED requirements are. So far no luck. I am guessing it is AC(0) and a straight LKED of NAME IEAMDBLG If anyone knows specifically where I can find the information on how to assemble and link this module that would be great. We just Cold started our PLEX this weekend and OPERLOG seems to be the one most affect and it is losing records. Messages we now get in our SYSLOG Offload process are: ILG0001 RECORDS NOT AVAILABLE. IXGCONN-1 RETURN CODE 004, REASON CODE 0407 ILG0001 RECORDS NOT AVAILABLE. IXGBRWSE-2 RETURN CODE 004, REASON CODE 0405 I have looked those up, but am still clueless :-O Thanks Lizette -- 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
Re: OPERLOG staging datasets out of sync in sysplex
First: I only saw this because Kees quoted it. Unless you direct your output to ibm-main, I won't see any answer (and email to this address will get rejected). OW50564? That one even has fix for 2.10. Is that applied? As Kees stated, the only sure way to get out of the error will be to delete the operlog logstream, delete the structure, make sure all traces are gone (check that neither staging nor offload datasets for operlog are around anywhere, if necessary, delete them manually). Then redefine the structure in CFRM, redefine the logstream, turn operlog back on. Regards, Barbara Nitz -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser -- 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
Re: OPERLOG staging datasets out of sync in sysplex
Martin, First remark: Operlog does not manage the staging dataset, System Logger does. Operlog is only a user of System Logger. If you can suffer the loss of data, you can delete the logstream and structure (and the remaining staging datasets) and recreate them. Kees. Ps. This newsgroup is a mirror of a listserver. Subscribe to the listserver to address the entire Ibm-main population. See the info attached automagically at the bottom. Kees. "martin" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]> ... > We are having problems getting our OPERLOG staging datasets back 'in > sync' after a 2 day DR test - stopping and starting OPERLOG, > deallocating and reallocating the structure and even structure > rebuilds have had no effect. We've been sysplexed since God was a boy > (in fact we were one of the first UK sites to go sysplex) but this > one's got us stumped! > > Documentation on how OPERLOG manages its staging datasets, or how we > can override what generations it uses, is nonexistent as far as we can > see. If anyone can shed any light on how we sort this we'd be very > grateful - we are still on OS/390 2.10 (its a long story, don't ask) > so any 'official' IBM support has long since ceased to exist! > details follow. > > > Martin Jackson > Mainframe team manager > Vertex IT Operate > Grove House, Dawson House, Great Sankey > Warrington WA5 3LW > Tel: 01925 233599 / int 33599 > mailto:[EMAIL PROTECTED] > > > - > > IXCMIAPU reports OPERLOG is using gen A0017374 of the staging dataset, > status 'pending delete', even though the dataset didn't exist. We have > tried creating the dataset so OPERLOG can delete it and clear the > 'pending' but what happens is it deletes it but still leaves it as the > current log stream in 'delete pending' state. It then abends next time > it tries to delete it. Its creating new generations of the staging > dataset but they are LOWER gen. numbers than the one it thinks its > using and IXCMIAPU lists them as 'orphans' > > IXCMIAPU output is :- > LOG STREAM CONNECTION INFO: > > SYSTEMS CONNECTED: 1 > > SYSTEMSTRUCTURE CON CONNECTION CONNECTION > NAME VERSION ID VERSION STATE > -- -- -- > PRD1 C2B1DE6E418155C0 01 00010128Active > > > LOG STREAM DATA SET INFO: > > DATA SET NAMES IN USE: LOGGER.SYSPLEX.OPERLOG. > > Ext. Lowest BlockidHighest GMTHighest > Local Status > - - > - > *1 A0017374 0004B6C59819 07/05/08 09:52:51 07/05/08 > 10:52:51 DELETE PENDING > > NUMBER OF DATA SETS IN LOG STREAM: 1 > > > POSSIBLE ORPHANED LOG STREAM DATA SETS: > DATA SET NAMES: > > LOGGER.SYSPLEX.OPERLOG.A0017215 > LOGGER.SYSPLEX.OPERLOG.A0017253 > > NUMBER OF POSSIBLE ORPHANED LOG STREAM DATA SETS: 2 > > > Our structure definition is :- > > .DEFINE STRUCTURE NAME(LOGGER_OPERLOG) > LOGSNUM(1) > MAXBUFSIZE(4096) > AVGBUFSIZE(535) > EFFECTIVE > AVERAGE > BUFFER > SIZE(535) > >DEFINE LOGSTREAM NAME(SYSPLEX.OPERLOG) > STRUCTNAME(LOGGER_OPERLOG) > LS_DATACLAS(DCLOGGER) > LS_MGMTCLAS() > LS_STORCLAS(SCSTAND) > HLQ(LOGGER) > MODEL(NO) > LS_SIZE(1000) > STG_MGMTCLAS() > STG_STORCLAS(SCSTAND) > STG_DATACLAS(DCLOGGER) > STG_SIZE(0) > LOWOFFLOAD(20) > HIGHOFFLOAD(80) > STG_DUPLEX(YES) > DUPLEXMODE(COND) > RMNAME() > DESCRIPTION() > RETPD(0) > AUTODELETE(NO) > DASDONLY(NO) > > Error from IXGLOGR when it tries deleting the (nonexistent) gen > A0017374 of the staging dataset is :- > > IXG251I IKJ56228I DATA SET LOGGER.SYSPLEX.OPERLOG.A0017374 NOT IN > CATALOG OR CATALOG CAN NOT BE ACCESSED > IXG063I LOGGER ABENDED AND REQUESTED AN SVC DUMP WHILE PROCESSING 450 > LOGSTREAM: SYSPLEX.OPERLOG > STRUCTURE: **UNKNOWN** > MODULE=IXGI3DSC,ABEND=S01C5,REASON=0009000C > IXG301I SYSTEM LOGGER FAILED TO OFFLOAD DATA FOR LOG STREAM 451 > SYSPLEX.OPERLOG IN STRUCTURE LOGGER_OPERLOG. RETURN CODE: 000C > REASON CODE: DIAG1: 001C DIAG2: 17080002 DIAG3: > 0107001B
Re: SYSLOG/OPERLOG Time Stamps
"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 > >timestamped at the moment the messages is displayed on the console. So > >if the console is full and does not recieve messages, these messages are > >held up until the operator clears the screen. If no other (non-console) > >messages are produced in that interval, this might explain the gap in > >syslog/operlog. > > > >Kees. > > Kees, > > You are incorrect. The timestamp is generated as soon as the WQE control > block is created that represents the message. This occurs before the message > is written to the SYSLOG and well before the message is queued to any > consoles. Since z/OS R4, messages are written to SYSLOG before they are > queued to consoles. > > W. Kevin Kelley IBM POK Lab -- z/OS Core Technical Development > Thanks for the update! Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- 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
Re: SYSLOG/OPERLOG Time Stamps
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 console is full and does not recieve messages, these messages are >held up until the operator clears the screen. If no other (non-console) >messages are produced in that interval, this might explain the gap in >syslog/operlog. > >Kees. Kees, You are incorrect. The timestamp is generated as soon as the WQE control block is created that represents the message. This occurs before the message is written to the SYSLOG and well before the message is queued to any consoles. Since z/OS R4, messages are written to SYSLOG before they are queued to consoles. W. Kevin Kelley IBM POK Lab -- z/OS Core Technical Development -- 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
Re: SYSLOG/OPERLOG Time Stamps
"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 the gaps. > > Does anyone have any thoughts as to why that might be? > > > 2008046 11:22:37.53 > 2008046 11:22:37.57 > 2008046 11:22:52.05 > 2008046 11:22:52.31 > 2008046 11:22:52.59 > 2008046 11:25:58.65 > 2008046 11:25:58.67 <-- > 2008046 11:26:49.66 <-- > 2008046 11:27:26.17 <-- > 2008046 11:28:14.67 <-- And starts again > 2008046 11:28:14.67 > 2008046 11:28:14.67 > 2008046 11:28:14.68 > 2008046 11:28:14.67 > 2008046 11:28:14.98 > 2008046 11:28:18.19 > 2008046 11:28:18.27 > 2008046 11:28:18.27 > 2008046 11:28:18.27 > 2008046 11:28:18.28 > 2008046 11:28:18.47 > 2008046 11:28:18.96 > > Lizette Lizette, 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 console is full and does not recieve messages, these messages are held up until the operator clears the screen. If no other (non-console) messages are produced in that interval, this might explain the gap in syslog/operlog. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- 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
Re: SYSLOG/OPERLOG Time Stamps
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 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. > >Does anyone have any thoughts as to why that might be? > > > 2008046 11:22:37.53 > 2008046 11:22:37.57 > 2008046 11:22:52.05 > 2008046 11:22:52.31 > 2008046 11:22:52.59 > 2008046 11:25:58.65 > 2008046 11:25:58.67 <-- > 2008046 11:26:49.66 <-- > 2008046 11:27:26.17 <-- > 2008046 11:28:14.67 <-- And starts again > 2008046 11:28:14.67 > 2008046 11:28:14.67 > 2008046 11:28:14.68 > 2008046 11:28:14.67 > 2008046 11:28:14.98 > 2008046 11:28:18.19 > 2008046 11:28:18.27 > 2008046 11:28:18.27 > 2008046 11:28:18.27 > 2008046 11:28:18.28 > 2008046 11:28:18.47 > 2008046 11:28:18.96 > >Lizette Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -- 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
Re: SYSLOG/OPERLOG Time Stamps
On Fri, 15 Feb 2008 15:16:43 -0600, Brian Peterson <[EMAIL PROTECTED]> wrote: >In my opinion, the simple "lack" of messages in syslog / operlog is actually >evidence of a system which is well behaved. Absent any other symptom, you >should be pleased. I would be! That's a good point. Of course just seeing a post about this to begin with made me believe that this was very unusual situation and there was some sort of problem. On one of my sandbox LPARs I went an hour and 47 minutes without a message this morning. :-) Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: SYSLOG/OPERLOG Time Stamps
On Fri, 15 Feb 2008 11:39:03 -0500, Lizette Koehler 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. > >Does anyone have any thoughts as to why that might be? > (snip) > >Lizette > Are there any other symptoms? Why do you think you even have a problem? In normal operation, applications should not issue WTO messages to the console / syslog / operlog in a well-behaved system. If any of the wild theories mentioned in reply to your post were actually happening, you would likely have other symptoms. For example, trivial TSO transactions (say, hitting "enter" at the ISPF main menu) would be delayed for several seconds. In my opinion, the simple "lack" of messages in syslog / operlog is actually evidence of a system which is well behaved. Absent any other symptom, you should be pleased. I would be! Brian -- 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
Re: SYSLOG/OPERLOG Time Stamps
On Fri, 15 Feb 2008 14:56:08 -0600, Patrick O'Keefe <[EMAIL PROTECTED]> wrote: >On Fri, 15 Feb 2008 13:47:18 -0500, Lizette Koehler ><[EMAIL PROTECTED]> wrote: > >>No Spin Loops or other issues. RMF looks good. I will just monitor for >now to see if anything comes of it. >>... > >Synchonous SVCDUMPs? Seems like a long time for an SVCDUMP, >though. > Not to mention it would be hard to miss that in the syslog/operlog. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: SYSLOG/OPERLOG Time Stamps
On Fri, 15 Feb 2008 13:47:18 -0500, Lizette Koehler <[EMAIL PROTECTED]> wrote: >No Spin Loops or other issues. RMF looks good. I will just monitor for now to see if anything comes of it. >... Synchonous SVCDUMPs? Seems like a long time for an SVCDUMP, though. Pat O'Keefe -- 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
Re: SYSLOG/OPERLOG Time Stamps
No Spin Loops or other issues. RMF looks good. I will just monitor for now to see if anything comes of it. Thanks. Lizette >>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. >> >>Does anyone have any thoughts as to why that might be? >> >> > > >Spin loop during that time? Check logrec. > -- 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
Re: SYSLOG/OPERLOG Time Stamps
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. > >Does anyone have any thoughts as to why that might be? > > Spin loop during that time? Check logrec. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: SYSLOG/OPERLOG Time Stamps
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. > >Does anyone have any thoughts as to why that might be? > > > 2008046 11:25:58.65 > 2008046 11:25:58.67 <-- > 2008046 11:26:49.66 <-- > 2008046 11:27:26.17 <-- > 2008046 11:28:14.67 <-- And starts again > 2008046 11:28:14.67 > 2008046 11:28:14.67 I looked at my PROD Lpar and see gaps of 10, 11, 14, 15 seconds at times, even at this hour (11:45 a.m. EST). TTFN, Mark -- 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
SYSLOG/OPERLOG Time Stamps
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. Does anyone have any thoughts as to why that might be? 2008046 11:22:37.53 2008046 11:22:37.57 2008046 11:22:52.05 2008046 11:22:52.31 2008046 11:22:52.59 2008046 11:25:58.65 2008046 11:25:58.67 <-- 2008046 11:26:49.66 <-- 2008046 11:27:26.17 <-- 2008046 11:28:14.67 <-- And starts again 2008046 11:28:14.67 2008046 11:28:14.67 2008046 11:28:14.68 2008046 11:28:14.67 2008046 11:28:14.98 2008046 11:28:18.19 2008046 11:28:18.27 2008046 11:28:18.27 2008046 11:28:18.27 2008046 11:28:18.28 2008046 11:28:18.47 2008046 11:28:18.96 Lizette -- 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
Re: OPERLOG stops after IPL
On Thu, 28 Jun 2007 12:54:30 -0500, Carmen Vitullo <[EMAIL PROTECTED]> wrote: >WOW! I may as well answer myself, since it appears I'm talking to myself, it >funny how much attention is being paid to a tread about windows, and I ask a >bonified question about the MAINFAME and get zilch. sorry if I piss in anyone's >cerial. I thought by subscribing to the list like I've done with so many other >lists, I could get some help for the so called experts, Steve has help me out a >bunch, but I guess that's his mistake for knowing me, Bob Richards, if your out >there hello to you too. guess I'll have to find another group of folks that know >something about a SYSPLEX. thanks, now back to your regular windows >thread! > >Carmen WOW! You waited an entire day for some free help from people who do this on their own time and you didn't get a resolution to your problem? Excuse us! It's probably not that you are being ignored, it may be you didn't provide enough information or someone who was willing to take the time to answer wasn't sure and didn't want to give you wrong information. Did you open a PMR with logger support and try a little extra RTFM before you posted this? I personally didn't answer because I don't know the answer. Running OPERLOG on a monoplex or basic sysplex is probably not the norm. I've never used it except in a parallel sysplex. You aren't trying to share a DASD-only logstream between 2 or more systems- are you? -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group: G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: OPERLOG stops after IPL
And, Carmen, even if you _are_ perturbed because we didn't solve your problem for you, there are more polite ways to express it. Most of us have our own fires to fight, for employers who put money in the bank, so forgive us if our volunteer work comes second. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 -- 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
Re: OPERLOG stops after IPL
Oh, and lastly, if you don't get the response you want here, and you feel this is a problem, maybe you should open an ETR with IBM, and ask them the question. I'm rubbed a little bit the wrong way, when you have waited one whole day for a response, and get upset when one is not given. Dave Jousma Principal Systems Programmer [EMAIL PROTECTED] 616.653.8429 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jousma, David Sent: Thursday, June 28, 2007 2:46 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: OPERLOG stops after IPL Carmen, I'm going to ask the obvious, but I'm going to assume by the tone of your email, that you have already read the FINE manual in detail. Did you update the CONSOLxx member to include HARDCOPY DEVNUM(SYSLOG,OPERLOG) ROUTCODE(ALL) CMDLEVEL(CMDS)HCFORMAT(YEAR) (SYSLOG is optional if you don't want it). - or - Via automation or COMMNDxx a V HC command? Dave Jousma Principal Systems Programmer [EMAIL PROTECTED] 616.653.8429 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Carmen Vitullo Sent: Thursday, June 28, 2007 1:55 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: OPERLOG stops after IPL WOW! I may as well answer myself, since it appears I'm talking to myself, it funny how much attention is being paid to a tread about windows, and I ask a bonified question about the MAINFAME and get zilch. sorry if I piss in anyone's cerial. I thought by subscribing to the list like I've done with so many other lists, I could get some help for the so called experts, Steve has help me out a bunch, but I guess that's his mistake for knowing me, Bob Richards, if your out there hello to you too. guess I'll have to find another group of folks that know something about a SYSPLEX. thanks, now back to your regular windows thread! This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- 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
Re: OPERLOG stops after IPL
Carmen, I'm going to ask the obvious, but I'm going to assume by the tone of your email, that you have already read the FINE manual in detail. Did you update the CONSOLxx member to include HARDCOPY DEVNUM(SYSLOG,OPERLOG) ROUTCODE(ALL) CMDLEVEL(CMDS)HCFORMAT(YEAR) (SYSLOG is optional if you don't want it). - or - Via automation or COMMNDxx a V HC command? Dave Jousma Principal Systems Programmer [EMAIL PROTECTED] 616.653.8429 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Carmen Vitullo Sent: Thursday, June 28, 2007 1:55 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: OPERLOG stops after IPL WOW! I may as well answer myself, since it appears I'm talking to myself, it funny how much attention is being paid to a tread about windows, and I ask a bonified question about the MAINFAME and get zilch. sorry if I piss in anyone's cerial. I thought by subscribing to the list like I've done with so many other lists, I could get some help for the so called experts, Steve has help me out a bunch, but I guess that's his mistake for knowing me, Bob Richards, if your out there hello to you too. guess I'll have to find another group of folks that know something about a SYSPLEX. thanks, now back to your regular windows thread! This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- 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
Re: OPERLOG stops after IPL
According to "Setting up a Sysplex" If SMS is not active when you attempt to use a system logger application, system logger issues system messages that indicate allocation errors. If the SMS address space is not active when you attempt to use a system logger application, system logger issues system messages that indicate allocation errors and the application will not be able to use the logger function. -- 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
Re: OPERLOG stops after IPL
WOW! I may as well answer myself, since it appears I'm talking to myself, it funny how much attention is being paid to a tread about windows, and I ask a bonified question about the MAINFAME and get zilch. sorry if I piss in anyone's cerial. I thought by subscribing to the list like I've done with so many other lists, I could get some help for the so called experts, Steve has help me out a bunch, but I guess that's his mistake for knowing me, Bob Richards, if your out there hello to you too. guess I'll have to find another group of folks that know something about a SYSPLEX. thanks, now back to your regular windows thread! Carmen -- 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
OPERLOG stops after IPL
I've been trouble shooting an OPERLOG issue on one system that uses OPERLOG as a DASDLONLY structure, the operlog right after IPL time become inative, I can't see any sysplex related reason why the operlog becomes inactive, we vary operlog, hardcpy and logging becomes active. looking thru the time events during this system's IPL, I realize the OPERLOG is in fact a DASDONLY log and the datasets are SMS managed, I see that SMS is not active for a full minute after the operlog strucutre attemts allocation, I'm thinking the OPERLOG datasets cannot be allocated until SMS is active, or am I on the wrong track. thanks all! Carmen -- 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
Re: OPERLOG and MSGIEE316I CODE 0008-0891
Hi Jose, I'm curious, do you use native IBM PPRC commands or Hitachi's Business Continuity Manager ( BCM ) to control your PPRC environment? Also, am I correct in assuming that the IEA494I messages are created as a result of the Suspend/Resync of the Primary to Secondary PPRC sessions? The reason I ask the above questions is that I have almost the exact configuration. I have a HDS9980V at the primary site and a HDS9980V at the secondary site. We have 1328 volumes in the HDS TrueCopy ( the primary to secondary ) session that are running PPRC sync mode and we have 1359 volumes in the HDS ShadowImage ( the secondary to tertiary ) session. We initially ( June 2004 ) tried using IBM PPRC commands to control the PPRC sessions. We had issues with in-consistent data when we would perform the suspend on the primary to secondary session and the secondary to tertiary session. HDS indicated that their HDS BCM product ( previously named: Copy Central ) would provide the consistent data for the TrueCopy and ShadowImage sessions. We tried the HDS BCM product and I have to say it has provided us with exactly what HDS promised. We have performed a D/R test every month for the last 2+ years with zero issues with consistent data. If you have any specific questions regarding the above information, feel free to contact me off-list. Glenn Miller --- This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. ABN AMRO Bank N.V, which has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587, including its group companies, shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. ABN AMRO Bank N.V. (or its group companies) does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. --- -- 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
Re: OPERLOG and MSGIEE316I CODE 0008-0891
On Tue, 12 Dec 2006 16:38:26 +0100, Jose Martinez <[EMAIL PROTECTED]> wrote: We've been active OPERLOG users since 1999. OPERLOG gave us sysplex wide view of all our systems from the begining, and allows consolidation of System Log. Everything went well till May, 2005, when our message traffic increased dramatically from 2K to more than 5K MDBs at thevery beginning of IPL time. You all might wonder where did that huge amount of MDBs come from. Well, all that stuff came from PPRC. We manage two sites, using HDS-9980V boxes at both ends and copying data from site1 to site2. As all you probably know, PPRC sends a MSGIEA494I every time a PPRC pair is duplexed/suspended. Yes, one MSGIEA494I per every dasd >copied; so, if you have 1K devices using PPRC you'll get 1K MSGIEA494I when PPRC copy is established. And 1K MSGIEA494I when PPRC copy is suspended. Why do we implement that DUPLEX/SUSPEND policy? because we need to have a third, time consistent copy for recovery purpouses. So, imagine if you don't have just 1K devices in PPRC mode, but 2, 3 or even more Ks, and you IPL one of your systems just when your PPRC is bombing you with thousands of MSGIEA494I messages. Yes, that is: OPERLOG initialisation fails with MSGIEE316I CODE 0008-0891. We openned a PMR for this reason at IBM and got the following answer from them: I'm surprised this isn't APARable. How hard did you try? > Has anybody suffer the same problem and got a way to solve it? I don't have a way to solve the problem, but how about leaving the OPERLOG specification out of CONSOLxx and using automation to "V OPERLOG,HARDCPY" at some point after the IPL. You will not have all your data in OPERLOG from the start of IPL, but if it is mostly IEA494I messages how many of them do you need to see in there? OPERLOG will still be a valuable tool and you can always use the syslog if there is something you need to see from early in the IPL of the system. Regards, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - GITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: OPERLOG and MSGIEE316I CODE 0008-0891
Jose Martinez wrote: We've been active OPERLOG users since 1999. OPERLOG gave us sysplex wide view of all our systems from the begining, and allows consolidation of System Log. Everything went well till May, 2005, when our message traffic increased dramatically from 2K to more than 5K MDBs at thevery beginning of IPL time. You all might wonder where did that huge amount of MDBs come from. Well, all that stuff came from PPRC. [snip] We openned a PMR for this reason at IBM and got the following answer from them: "I investigated the corresponding modules and the value of 5000 is still valid (up to HBB7709) and up to now I couldn't find a hint (in our databases) that there is a requirement or a plan to increase this value. The RC8 RSN891 indicates that the IXGLOGR asid is initializing at the point that Commtask tried to connect the hardcopy to OPERLOG. The OPERLOG task, which runs as a TCB in the CONSOLE asid, will wait for an ENF Signal from Logger, but if more than 5000 messages are queued during that time, then you will receive the IEE316I message indicating EXCESSIVE WAIT. Typically IXGLOGR will come up in sufficient time such that OPERLOG will not have to wait, so there may be something that is causing a slight delay. The internal logic is well documented in APAR OW28165; in the APAR you can find the mechanism of connecting and working with System Logger." So, OPERLOG keeps on failing when all that message traffics occurs at IPL time. We have no means to filter that stuff so early, or we just don't know how to do that, and IBM has no plan to increase that 5K upper line. Has anybody suffer the same problem and got a way to solve it? What do you think about asking IBM to increase that limit? This sounds APARable to me. Reminds me of the message overrun/loss problems that used to occur in large JES3 installations after the switchover to MCS consoles but before the LOGLIM= keyword was added to IEASYSxx. The addition of that parameter *might* have been via APAR as well, though ISTR it was discovered during ESP for MVS/ESA V5. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- 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
OPERLOG and MSGIEE316I CODE 0008-0891
We've been active OPERLOG users since 1999. OPERLOG gav Hello listers. We've been active OPERLOG users since 1999. OPERLOG gave us sysplex wide view of all our systems from the begining, and allows consolidation of System Log. Everything went well till May, 2005, when our message traffic increased dramatically from 2K to more than 5K MDBs at thevery beginning of IPL time. You all might wonder where did that huge amount of MDBs come from. Well, all that stuff came from PPRC. We manage two sites, using HDS-9980V boxes at both ends and copying data from site1 to site2. As all you probably know, PPRC sends a MSGIEA494I every time a PPRC pair is duplexed/suspended. Yes, one MSGIEA494I per every dasd copied; so, if you have 1K devices using PPRC you'll get 1K MSGIEA494I when PPRC copy is established. And 1K MSGIEA494I when PPRC copy is suspended. Why do we implement that DUPLEX/SUSPEND policy? because we need to have a third, time consistent copy for recovery purpouses. So, imagine if you don't have just 1K devices in PPRC mode, but 2, 3 or even more Ks, and you IPL one of your systems just when your PPRC is bombing you with thousands of MSGIEA494I messages. Yes, that is: OPERLOG initialisation fails with MSGIEE316I CODE 0008-0891. We openned a PMR for this reason at IBM and got the following answer from them: "I investigated the corresponding modules and the value of 5000 is still valid (up to HBB7709) and up to now I couldn't find a hint (in our databases) that there is a requirement or a plan to increase this value. The RC8 RSN891 indicates that the IXGLOGR asid is initializing at the point that Commtask tried to connect the hardcopy to OPERLOG. The OPERLOG task, which runs as a TCB in the CONSOLE asid, will wait for an ENF Signal from Logger, but if more than 5000 messages are queued during that time, then you will receive the IEE316I message indicating EXCESSIVE WAIT. Typically IXGLOGR will come up in sufficient time such that OPERLOG will not have to wait, so there may be something that is causing a slight delay. The internal logic is well documented in APAR OW28165; in the APAR you can find the mechanism of connecting and working with System Logger." So, OPERLOG keeps on failing when all that message traffics occurs at IPL time. We have no means to filter that stuff so early, or we just don't know how to do that, and IBM has no plan to increase that 5K upper line. Has anybody suffer the same problem and got a way to solve it? What do you think about asking IBM to increase that limit? Thanks in advance to all of you. Jose Martinez z/OS System Programmer __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com -- 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
Re: OPERLOG search filter in batch
Perhaps you manage operlog like syslog and copy / delete every 24 hours using IEAMBDLG. If you want all the records since that last copy, (the "live" operlog) then just run the program without the delete to get the current operlog and scan the flat file using any number of utilities (including REXXSCAN from my CBT file / web site). If you don't currently use IEAMBDLG (just manage via RETPD in the logstream), then you can find the source / doc in SYS1.SAMPLIB. Example: //SCANOLOG JOB (ACCT),CLASS=A,... //* //OPERLOG EXEC PGM=IEAMDBLG, //PARM='COPY(2006291,2006291),HCFORMAT(YEAR)' //SYSLOG DD DSN=&&OPERLOG, // UNIT=SYSDA,DISP=(NEW,PASS), // SPACE=(CYL,(200,200),RLSE), // DCB=(BLKSIZE=0) // //SCAN EXEC PGM=IRXJCL,PARM='REXXSCAN IOS452I' //SYSTSIN DD DUMMY //SYSTSPRT DD SYSOUT=* //SYSEXEC DD DSN=ZELDEN.CBT.FILE434,DISP=SHR //SCANOUT DD SYSOUT=* //SCANIN DD DSN=&&OPERLOG,DISP=(OLD,DELETE) HTH, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - GITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: OPERLOG search filter in batch
Hi Thank you very much -- 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
Re: OPERLOG search filter in batch
Hi I know, I tried this and I was unable to filter messages in batch from the SDSF OPERLOG -- 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
OPERLOG search filter in batch
You have some programs in SAMPLIB and can have some usefull information at CBT TAPE Files 513 (ispf and batch) and 642. angel luis dominguez bbva - spain Hi Is there any tool to search or filter messages from the operlog (in batch ) ? -- Miklos Szigetvari - LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com -- 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
Re: OPERLOG search filter in batch
SDSF can run in batch. Jim McAlpine On 10/18/06, Miklos Szigetvari <[EMAIL PROTECTED]> wrote: Hi Is there any tool to search or filter messages from the operlog (in batch ) ? -- Miklos Szigetvari Development Team ISIS Information Systems Gmbh tel: (+43) 2236 27551 131 Fax: (+43) 2236 21081 E-mail: [EMAIL PROTECTED] Info: [EMAIL PROTECTED] Hotline: +43-2236-27551-111 Visit our Website: http://www.isis-papyrus.com --- This e-mail is only intended for the recipient and not legally binding. Unauthorised use, publication, reproduction or disclosure of the content of this e-mail is not permitted. This email has been checked for known viruses, but ISIS accepts no responsibility for malicious or inappropriate content. --- -- 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
OPERLOG search filter in batch
Hi Is there any tool to search or filter messages from the operlog (in batch ) ? -- Miklos Szigetvari Development Team ISIS Information Systems Gmbh tel: (+43) 2236 27551 131 Fax: (+43) 2236 21081 E-mail: [EMAIL PROTECTED] Info: [EMAIL PROTECTED] Hotline: +43-2236-27551-111 Visit our Website: http://www.isis-papyrus.com --- This e-mail is only intended for the recipient and not legally binding. Unauthorised use, publication, reproduction or disclosure of the content of this e-mail is not permitted. This email has been checked for known viruses, but ISIS accepts no responsibility for malicious or inappropriate content. --- -- 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
