Hi Yves,
David said
> Seems like it oughta work.
I won't disagree BUT I would strongly discourage you from including code
that does a STATUS stop in your own IEFUTL exit code. IMHO you are
adding something that is more likely to cause an outage or an unexpected
failure or ABEND than it is to solve the problem. Don't muck around with
other people dispatching if you can avoid it. This is a good ROT for
both customer exits and vendors. The variety of things that get
processed by your exit will almost certainly exceed what you see during
testing and what you expect. At some point your exit will stop a unit
of work that impacts something important. Consider that IEFUTL will
run for multi-tasking authorized address spaces doing all sorts of
things that might not have been a good idea but your exit it going to
get blamed for any system problems. Keep it simple. Keep it short. If
you need to raise a flag externally do a WTO not a WTOR and let your
Operator or Automation make a decision to CANCEL this task not try to
stop the clock while you wait for a decision. If you want to keep the
policy for how things are treated external to the exit put it in RACF in
a RACLISTed class like FACILITY and check a resource but if you can make
it really simple and avoid even that do so.
Have fun but remember success here is that the exit is boring, easy to
read, well documented, just works and doesn't need to be touched again
for a long time:-)
Best Regards,
Sam Knutson, GEICO
Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office) 301.986.3574
Every program is either trivial or it contains at least one bug.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Yves Colliard
Sent: Monday, January 15, 2007 6:04 AM
To: [email protected]
Subject: Status Stop and REXX
Hello everyone!
I'm trying within IEFUTL Exit to stop the address space (all other TCBs)
from working; because in certain circumtances I'm asking the operators
(WTOR) to decide if the address space have the right to use more CPU.
To do this I use the status stop macro and it works fine... but not with
a batch TSO Rexx programm; this one (only this TCB) is running and
running.
Using a SVC Dump I've seen, that the TCB Stop is delayed.
Does someone have an idea how to even stop such a TCB?
Regards, Gruesse, salutations
Yves Colliard
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
----------------------------------------------------------------------
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
