On 12-Dec-2015 10:18 -0600, Puga Sankara wrote:
<<SNIP>> Basically this user is logged on to a session through Telnet
and due to weak wifi signal gets disconnected.
Now the client is disconnected, however the job is still running in
the server.
Is there a way the user can log back to the same session and job that
he was on and continue from where he left off?

The job that is "still running" needs to go into Disconnected (DSC) status; typically the job needs to learn that the device is no longer actively communicating, and then be impacted by the chosen setting for the Device I/O Error [Recovery] Action (QDEVRCYACN) System Value -- conspicuously, a choice of DSCxxx or MSG vs an ENDxxx setting is required, to enable a named-device session to reestablish attachment to the current job that was disconnected vs ended.

Does the "still running" job show a device I\O error in the active joblog? If the job at the device is not doing any I\O to the device, then I think that, though I can not recall, the TCP/IP keepalive setting on the server can be reduced to cause the detection of the non-active comm to be manifest quicker as a device [IIRC, a msg CPF5140] error.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].