Re: Automatic email of condition codes and stats

2011-07-21 Thread Shmuel Metz (Seymour J.)
In 9218149210800952.wa.brianwestermansyzygyinc@bama.ua.edu, on 07/19/2011 at 04:48 AM, Brian Westerman brian_wester...@syzygyinc.com said: I wait for the ENDED console message to appear and run the control blocks getting all of the tasks information, Name, Number, execution stats, etc.

Re: Automatic email of condition codes and stats

2011-07-21 Thread Brian Westerman
It's not particularly a good idea to dynamically allocate the spool output dataset (which contains the email itself) from where the code is running at the time. Brian -- For IBM-MAIN subscribe / signoff / archive access

Re: Automatic email of condition codes and stats

2011-07-20 Thread Brian Westerman
You can do that with our other product (SyzSPOOL), but it's not really the same thing, we wanted to (and did) put together an easy to read synopsis of what the task did. Also, there are some tasks that don't have JOBLOGs, but still require notification when/if they come down. The product is

Re: Automatic email of condition codes and stats

2011-07-20 Thread Brian Westerman
Hi, That's a good idea, but SysREXX can't get to the job's control blocks by the time the ended message comes out, many of them are already gone and/or (even worse) in the process of being freed. I originally implemented it as a SysREXX, but was limited to just the MAXCC, none of the

Automatic email of condition codes and stats

2011-07-19 Thread Brian Westerman
Hi all, I have a small dilemma. I have designed and written a semi-new facility that automatically sends the task condition codes (including the max CC) and stats via email. I currently have it implemented and in Alpha testing in two modes. We have provided this via a manual method (via

Re: Automatic email of condition codes and stats

2011-07-19 Thread Elardus Engelbrecht
Brian Westerman wrote: My dilemma is that I have been told that we will not be using both methods and we have to choose one or the other. I asked everyone here and got almost an even three-way split (option 1, option 2, and whats an exit?), so I thought I would go out to the list and see how

Re: Automatic email of condition codes and stats

2011-07-19 Thread Richards, Robert B.
For those what's an exit?, show them the exit ('door') :-D Or as my boss likes to say Give me some of that money back! :-) Bob -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: Automatic email of condition codes and stats

2011-07-19 Thread Miklos Szigetvari
Just one addition: We put the JOBLOGs for the important daily backup etc jobs into a special SYSOUT class, and a JES writer sends this JOBLOGS automatically to the originating user On 7/19/2011 11:48 AM, Brian Westerman wrote: Hi all, I have a small dilemma. I have designed and written

Re: Automatic email of condition codes and stats

2011-07-19 Thread Miklos Szigetvari
On 7/19/2011 11:48 AM, Brian Westerman wrote: Hi all, I have a small dilemma. I have designed and written a semi-new facility that automatically sends the task condition codes (including the max CC) and stats via email. I currently have it implemented and in Alpha testing in two modes. We

SV: Automatic email of condition codes and stats

2011-07-19 Thread Thomas Berg
   Specialist   A M   SWEDBANK -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] För Brian Westerman Skickat: den 19 juli 2011 11:48 Till: IBM-MAIN@bama.ua.edu Ämne: Automatic email of condition codes and stats Hi all, I have a small

Re: Automatic email of condition codes and stats

2011-07-19 Thread Hal Merritt
. Things to consider as you flip that coin :-) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Brian Westerman Sent: Tuesday, July 19, 2011 4:48 AM To: IBM-MAIN@bama.ua.edu Subject: Automatic email of condition codes and stats Hi all, I have

Re: Automatic email of condition codes and stats

2011-07-19 Thread Brian Westerman
Unfortunately the SyzEMAIL part of things is different depending on which implementation is used which means that we would end up with maintaining two completely different SyzEMAIL programs which are drastically different, but so close in function that it's possible that things could get