I'm not sure how I would separate out the enqueue and resource waits at job end time, that information is not as readily available so the overhead might be noticeable to get at it. It's kind of out of scope for this type of product.
The way the product works, I can generate the MaxCC at job end, or at any point during the execution of the job, the only difference being that instead of "ended" in the subject (and the body of the message), it will state "executing" and will only show the steps that have executed to that point in time, so if it's a 50 step job and we get called to process things due to some event (other than job end), at say, step 5, then the best we can do is tell the user that at this time the job is executing in step5 and that the MaxCC, (so far) is whatever it happens to be and name that step for them. Sometimes and event will happen to a task that being able to be called before the actual end of the task makes sense, and when the email is being generated from something like SyzCMD/z (our command scripting product), and we want to know what the MaxCC or the stepCC's were, SyzCMD/z will call this product's APIs to get that information and can use it all programatically, plus it can generate it's own email using variables (some of which can be individual stepCC's) without ever needing the SyzMAIL/z email capabilities at all. The SyzCMD/z implementation of the APIs were to provide a "better" mousetrap for JCL condition code processing, since you can interrogate the codes along with about 90 other "things" to decide what needs to be done in the script, which will allow the site to programatically decide to run a step or skip it on the fly. To provide that kind of ability to SyzCMD/z meant that we needed a API that could do that type of thing, and then I wanted to give the user the ability to also send an email from SyzCMD/z (and SyzMPF/z) programatically. That's what drove the SyzMAIL/z product into being, SyzCMD/z didn't really need that because it can write to SMTP all on it's own, but you can't do that from a console directed task, so I needed an intermediary and SyzMAIL/z is it. After that point the rest of it made sense to add as capabilities. My only real problem was deciding where to stop, and the marketing people think I crossed that line already. :) I have code for SyzCMD/z (via these APIs) that allows it to see the MaxCC of any (or all) currently running tasks and to interrogate any or all of the StepCCs, but that code will sit on the shelf for now, because I have not thought of a reason that anyone would want to use it (yet). Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
