That's clear: you changed the hardcopy device from Syslog to Operlog, i.s.o. adding operlog. Writelog started SYSLOG as hardcopy device.
When you see all log in SDSF's LOG O, it is available in the logstream, no doubt about that. Getting it out seems to be a IEAMDBLG problem. Maybe someone has a working example. Is there no utility, like IFASMFDL for SMF, to read Operlog parameter driven? Grtn, Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Sean Gleann > Sent: 20 July, 2018 14:41 > To: [email protected] > Subject: Re: SYSLOG and LOGR query > > Hi Kees > > Regarding your second point first - > When I went to the SDSF LOG panel, I saw that was in the OPERLOG, > probably > resulting from something I'd done yesterday. Command LOG SYSLOG switched > me > to the SYSLOG, where just one line was given - the one that says > "IEE042I > SYSTEM LOG DATA SET INITIALIZED", with nothing before or after. It was > at > that point that the concepts of 'SYSLOG' and 'OPERLOG' rang a bell for > me, > and I checked my CONSOLxx member. > There, I had HARDCOPY DEVNUM(OPERLOG) ROUTCODE(ALL) CMDLEVEL(CMDS) > HCFORMAT(CENTURY) specified. I changed the DEVNUM specification to > DEVNUM(SYSLOG,OPERLOG), then 'T'-d that modified member in to play. Now > I've got the buffered SYSLOG being written whenever I use the 'W L' > command. > > As far as the retrieving the data is concerned, I've been taking a > closer > look at the source code for the IEAMDBLG program. Granted, this program > is > supplied on an 'as is' basis, but the general quality is not what I > would > call 'high'. I can see see a number of questionable code sequences, and > I'll probably be writing my own program to replace it in the near > future. > > Sean > > On 20 July 2018 at 12:08, Vernooij, Kees (ITOPT1) - KLM < > [email protected]> wrote: > > > This does not sound logical to me. Messages are written to the > logstream > > (possibly in blocks) and should be retrievable immediately. > > The W L (operator) command writes the internally buffered SYSLOG to > JES2 > > sysoutclass L. > > > > Grtn, > > Kees. > > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List [mailto:IBM- > [email protected]] On > > > Behalf Of Sean Gleann > > > Sent: 20 July, 2018 12:21 > > > To: [email protected] > > > Subject: Re: SYSLOG and LOGR query > > > > > > Well, I went home yesterday without making much progress and then > > > returned > > > to work this morning to find that the darned thing had sprung in to > > > life! > > > > > > I've now got four 'offload' files (is that the right terminology? > Files > > > with names like "xxxxxxxx.SYSPLEX.OPERLOG.A0000000"), and using > IEAMDBLG > > > actually produces a data file and goes to RC0. > > > A 'W L' command in SDSF produces a SYSLOG file on my Hold queue, > that > > > contains a single line with the message "IEE042I SYSTEM LOG DATA SET > > > INITIALIZED". > > > > > > My only misgiving at present is that IEAMDBLG can only 'see' data up > to > > > midnight yesterday/today. Any attempt to retrieve data beyond that > point > > > results in a U0001 abend again. I'm not too worried about that, > since > > > 'data > > > up to midnight' exactly fits my requirements. I'll keep an eye on > the > > > situation and make sure that I can retrieve for today when tomorrow > > > comes > > > around. > > > > > > > > > Thank you all for the help, comments and pointers - things appear to > be > > > going as expected (for now!) > > > > > > Sean > > > > > > On 20 July 2018 at 07:27, Vernooij, Kees (ITOPT1) - KLM < > > > [email protected]> wrote: > > > > > > > Skip, > > > > I know that. > > > > > > > > Kees. > > > > > > > > > > > > > -----Original Message----- > > > > > From: IBM Mainframe Discussion List [mailto:IBM- > > > [email protected]] On > > > > > Behalf Of Jesse 1 Robinson > > > > > Sent: 19 July, 2018 17:56 > > > > > To: [email protected] > > > > > Subject: Re: SYSLOG and LOGR query > > > > > > > > > > You get OPERLOG recording not just 'if' JES2 is down. OPERLOG > starts > > > > > recording very early in an IPL--before JES starts--and continues > > > until V > > > > > XCF,OFF--after JES has shut down. SYSLOG can eventually write > out > > > very > > > > > early IPL-time messages stored by MVS before JES starts but > quits as > > > > > soon as JES terminates. That alone should make the effort > > > worthwhile. > > > > > > > > > > . > > > > > . > > > > > J.O.Skip Robinson > > > > ******************************************************** > > > > 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: INFO IBM- > MAIN > > > > > > > > > > -------------------------------------------------------------------- > -- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO IBM- > MAIN > > ******************************************************** > > 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: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** 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: INFO IBM-MAIN
