Re: Trap 5250 session disconnect in an rpg program.

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Hello,

I'm replying to my own message because I forgot to mention that this 
solution is intended for (and tested with) DEVRCYACN(*MSG).  I don't 
think it'll work with other DEVRCYACN settings.


On 12/14/2010 1:27 PM, Scott Klement wrote:
> Hello,
>
> > ie; the session is disconnecting and I'd like the rpg program
> > to know this.
> > (I don't think so but thought I'd ask anyway)
>
> You could do this:
>
>    D PERM_IO_ERROR   C                   1251
>       .
>       .
>
>       monitor;
>          exfmt MYSCREEN;
>       on-error PERM_IO_ERROR;
>          // code to delete data area
>       endmon;
>
>
> Note that the 'monitor' block doesn't *have* to be coded right on the
> exfmt.  In our shop, we have a lot of WiFi scanning guns, and like any
> wireless communication, they're subject to problems with low signal
> strength, dropping connections, etc.  So we have it coded at the
> high-level (in the "controller" component of the MVC pattern)
>
>       monitor;
>          exsr DoWork;    // all program logic is in this routine
>       on-error PERM_IO_ERROR;
>          exsr CleanIp;   // occurs if PERM_IO_ERROR happens anywhere
>                          // in program.
>       endmon;
>
> You can change the 'exsr' to 'callp' as well, as long as the procedure
> runs within the same activation group.