Re: Easier timeout, Re: Some fine points of dealing with Telnet jobs

James,

> Well, I was under the impression that my "sentinel" job
> would have to recognize and get rid of orphaned jobs, and
> that there wasn't a way to have the application recognize
> when it had been orphaned.

It this is for inactivity timeouts, beware the MAXRCD method is only
effective while your application is active.  If a user has access to
other displays (eg spool file displays or whatever), you have lost
control.

The dspf timeout or dtaq technique is useful (IMHO) for things like
auto-refresh and a timeout for things like putting up a message but
wanting to take a default action if the user does not reply within a
given time constraint.

For more general inactivity as you seem to be implying, consider the
system value for inactivity.  While this is system global in nature,
you can use a break-handling pgm on the QINACTMSGQ to decide on a more
intelligent level what action to take, based on the user or device
name or time of day or whatever.

Doug