I, being younger than most I work with (26), would honestly prefer SMS notifications....which is what we have began to set up here (although they get kind of messy since it's going through JES2MAIL to our mail server and it appends the disclaimer at the bottom automatically....yuck). Personally, I don't think that twitter, or a twitter-like service, offers much more than a simple SMS message. If we were going a web-enabled route, I would set up a website with an RSS feed, that way (similar to the twitter approach) everything would be in a central location.
With that said, there's definitely nothing wrong with sitting in SDSF in the active queue just hitting enter again and again and again <grin> Thanks; Nathan Pfister zOS Systems Programmer AES\PHEAA - Tech Services [email protected] (717) 720-2663 From: "Miklos Szigetvari" <[email protected]> To: [email protected] Date: 01/17/2014 04:04 AM Subject: Re: Automatic Job Ended Email (detail information) Sent by: "IBM Mainframe Discussion List" <[email protected]> Maye would be interesting to know how the young people would like to be notified (Email ? Twitter ? Facebook ? ) if something happens. Old timers are sitting by the TSO and pressing the ENTER for the SDSF DA again and again. On 16.01.2014 07:57, Brian Westerman wrote: > 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 > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > -- Kind regards, / Mit freundlichen Grüßen Miklos Szigetvari Research& Development ISIS Papyrus Europe AG Alter Wienerweg 12, A-2344 Maria Enzersdorf, Austria T: +43(2236) 27551 333, F: +43(2236)21081 E-mail: [email protected] Info: [email protected] Hotline: +43-2236-27551-111 Visit our brand new extended Website at 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 Papyrus accepts no responsibility for malicious or inappropriate content. --------------------------------------------------------------- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
