If all of the jobs in the subsystem are 'well-behaved,' they'll all end gracefully with an unlimited ENDSBS *CONTROLLED...
We have some application programs that put themselves in a wait for 10 minutes between runs, so we have longer to wait.
Plus, if there's a hangup we'd want a chance to see what went wrong, rather than have the rug pulled out from under the job.
Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, March 07, 2012 2:45 PM
To: Midrange Systems Technical Discussion
Subject: RE: can't kill a dataq program
Nice. Don't see a lot of people coding for the shutdown op code.
When we do use ENDSBS we use controlled with two minutes. That should
give someone like you plenty of time.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.