IEFU29 exits are cheap, or free. Automation can get very expensive. And
the exits are easier to test in a new release of z/OS and have smaller
impact on the overall performance of your system. I've used the same
mechanisms because my organization didn't buy automation. We just set up
our job streams so that each job, upon normal completion, submitted the
successor job via IEBGENER to an internal reader.
Rick
-----------------------------------------------
Elardus Engelbrecht wrote:
Kelman, Tom wrote:
We have it set up via the IEFU29 exit to submit a started task to dump the
MAN file when a switch takes place. I do believe that this is the common
process.
While it is a common process to start dumping when a switch takes place, we
here are making use of an automation package to pickup the message(s) and
kick off a job (or STC) to relieve the MANx datasets of their data.
Question: Why using an IEFU29 exit? Is it better than using Automation?
Groete / Greetings
Elardus Engelbrecht
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
