I can think of another 'important' issue with production jobs: the job is late (not started yet of started but not ended in time). So the alert cannot be done at job end and has to be guarded and generated by the scheduling system. Now when we are there, this can probably detect all the other issues and alerts of a job (like elapsetime, CPU generated output etc.) and signal them b.m.o. emails, pagers, faxes, SMTPs, twitters, whatsapp's etc.
I am afraid this thread has the potential of becoming one of those famous IBM-MAIN threads: ask a simple question and a couple of technicians convert it into a huge, unmanageable and unrealizable project ;-) Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: Thursday, January 16, 2014 16:29 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Automatic Job Ended Email (detail information) I'm with you, CPU and elapsed are at least as important as CC in signaling real or potential issues. Unusually long or short times are both a legitimate cause for further investigation, assuming other application-specific verification and notification procedures are not already in operation. IMHO unless it's a deluge, more information is better than less. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Brian Westerman Sent: Thursday, January 16, 2014 1:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Automatic Job Ended Email (detail information) Hi, We are testing our SyzMail product that provides for the sending of email when a task (JOB STC or TSO user) ends that contains all of the normal stuff you would expect to see (maxCC, stepCCs, programs used, etc.) and I was thinking that it would be great to provide the execution time (both wall clock and CPU) that the task used and the start and end times and some other information that is all just right there for the picking, but it has started some controversy here because many (most actually) think that people could care less about the details and mostly just care about the condition codes. I myself think that since the email is being generated and we have the information available, that it makes sense to send it. My thinking is that if you can see at a "glance" that the job ran a particular way that you might be more likely to save time by not having to find the job output and view it. In fact, I was thinking that sometimes seeing how much time a job used, wall and CPU, can be almost as important as the condition codes. I agree that providing information that no one will ever want is a waste, and have considered providing the option for a normal and "verbose" type of email, but I keep thinking that once the job is done and the email is dynamically generated, it's not like the user can come back and say, that they have a CC=4 in step07 so they would like to have some additional information, it's just too late by then. I figured that asking normal people (which some of you are), might be a reasonable thing to do. Any comments or suggestions? Brian -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- 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
