... and also messages after JES2 ended and SYSLOG was closed.

Kees.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Anthony Thompson
Sent: 19 August, 2016 8:40
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: OPERLOG vs SYSLOG

More significant for us was the ability to look at any system's log via SDSF 
from any other system in the 'plex (we're not MASPOOL). Also the ability to 
diagnose IPL errors from another system by being able to scroll through and 
eyeball the problem system's IPL messages prior to its JES initializing.

Ant.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Zahir Hemini
Sent: Friday, 19 August 2016 2:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: OPERLOG vs SYSLOG

We found that we preferred the direct access to Operlog data for report and 
analytical programs, to the two step process you have suggested. After the 
Operlog was set up and identified we never had any inclination to go back to 
Syslog.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to