MIDRANGE dot COM Mailing List Archive



MIDRANGE-L » January 2013

Re: PWRDWNSYS - job termination



Rob,
a technique to handle the "went to lunch" that I want
to get to is adding the data queue to my display files,
changing my EXFMT to WRITE screen, wait on data queue, READ screen,
if data queue times out, RETURN to previous screen...

We tried using the SIGTERM to our interactive programs, but we hit a
roadblock in that "once in a blue moon" a job would get stuck trying to
spawn another thread with the shutdown process, but the end was happening after we did a ENDSBS *CNTRLD command (i.e. no more new threads...)





On 1/17/2013 12:39 PM, rob@xxxxxxxxx wrote:
That rpg feature does what it should, but it doesn't do what we need. If
someone's sitting on a 5250 screen for program INVxxx and went to lunch
and someone kicks off a *CNTRLD end that program will sit there until the
time out ends on the *CNTRLD and autoinitiates an *IMMED. I'd rather a
simple indicator would be activated, like function keys are. That would
then return control back to the program, as if someone hit a function key
or some such thing.


Rob Berendt






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact