Re: Causing (and detecting) a workstation failure

--
Joe,

If you mean: a user closes a session without signing off? You cannot do
this in the programme itself.

A solution might be to track the joblog of that particular jobs. There is a
Control Job Log API that can change the output to a file in any (secured)
library. Monitor for new files in that library and send a message to
QSYSOPR. Of course this is all after the fact.

Perhaps exit points on workstations, if they exist, can do a similar thing
you like to accomplish.

Regards,
Carel Teijgeler.

>This should be relatively easy.  I'm trying to test for when a user shuts
>off a workstation.  I've coded an error indicator in the EXFMT, and am
>testing fo the indicator.  If an error occurs, I send a message to *SYSOPR.
>
>Unfortunately, I never get there.  As soon as I shut off the tube (that is,
>as soon as I disconnect the CAX session), the job ends and I don't seem to
>get to my *IN90 test.
>
>How quickly does the system kill jobs when they lose connection?  Shouldn't
>there be an opportunity for cleanup?  Or am I coding incorrectly?
--