Personally I believe that exits are very expensive and introduce risk. But so are long running tasks, and especially those looking at sensitive data. Both are popular audit targets.
In addition, this sounds like one of those gee-whiz things that is a fad that soon falls into disuse. Things to consider as you flip that coin :-) -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Brian Westerman Sent: Tuesday, July 19, 2011 4:48 AM To: [email protected] Subject: Automatic email of condition codes and stats 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 SyzEMAIL) for a few years now, and clients have asked for a way to do this automatically, so I figured out a few ways to do it and boiled it down to two prototypes which I designed and wrote. Option 1: 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. (and the condition codes), build the data in memory (because it's not really a good idea to dynamically allocate the email from this particular spot:) ) and then at a "user specified" interval (default is 15 seconds), a "always running" task looks at the data and merges it with data from the security system and/or user defined table(s) (to decide who gets the email) and sends one (or more) off to whatever address(es) were found and cleans up the memory related data. Option 2: Is really just an addition to our already existing SyzEMAIL (which already sends the email of the CC's etc.) program that adds JES exit and allows you to specify a //*EMAIL=emailaddress card which, if found, will generate a final step that executes the newer version of SyzEMAIL which does the same processing above, but has no need for the "always running" task, nor for storing any data in memory. The final step just gathers and builds it all and sends it. The JES exit isn't really mandatory, it just allows you the option of adding the //*EMAIL card, and it places the last step there for you unless one is found there already executing SyzEMAIL. Both ways run fine, and have advantages and disadvantages. There are some extra bells and whistles like keeping the email address in RACF and keying off the job owner ID, or deciding by task name, programmer information or accounting data who gets the email but they all exist in both implementations. The main advantage to the JES exit version is that it has less pieces, the disadvantage is that I have found that sites don't like putting in exits if they can get around it. The advantage internally (here) to the JES exit option is that the SyzEMAIL program gets a small upgrade (adds more information and optional HTML output), but no other code (beyond the exit) is needed, thus less maintenance on our end. The advantage to option #1 is that I like it and think it's really kind of cool but that appears (internally) to be one of the disadvantages. A disadvantage to Option 2 is that the exit is tied to JES releases so we would end up maintaining (potentially) a lot of version! s (one for each JES release). 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 the real world feels about the options. What do you think? If you would rather tell me off-list, that's okay as well. I see good points to each method and having designed the code, I have found that it's sometimes difficult (or impossible) to see that bad points. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
