RE: Trap 5250 session disconnect in an rpg program.

Brian,

You've stirred the pot.

I think I could change my 'single-user-at-a-time' only mechanism
to check for an object lock on the display file instead of the
data area existence scheme. If there is a lock on the display file
then I could tell the other user to try again in a few minutes.

Then, the DEVRCYACN of *ENDJOB should free up the lock on the display file
by default and the other user would be able to get into the rpg progam
if the original user disconnects the 5250 session by Xing the window.

In theory :-)

John B

All you need is exception handling around your display file I/O statements.
Inspect the job log of a job so-ended to see what exceptions (*ESCAPE
messages) are sent to the program.

If you want to enable reconnect, check the Device recovery action
(DEVRCYACN) attribute used for your users. Start with their job description
to see how DEVRCYACN is set. Hint: pick one of the disconnect options. In
addition you will want to make sure their emulation sessions specify a
specific device name so they will attempt to use the disconnected session
when the relaunch their emulation session.