Re: wrkqry/runqry and 5250 emulation ending

[Al Mac <macwheel99@xxxxxxxxxxx>]

I also having intermittent problems of similar nature.
I think ours are partly because
* We do not have IBM equipment end to end between AS/400 and end users some 
of whom are on Client Access, Twinax, and VPN
* We have flaky phone connection service
* The UPS protects the CPU but perhaps not the modem simulation gear
* Different pieces of hardware have some kind of "time out" when connection 
lost
* Different tasks take different lengths of time to do their thing, and 
some users THINK something has locked up when in fact it has not.
* Very few users remember that when there is an error message on bottom of 
screen, cursor on it, the F1 can be very illuminating

We rarely vary off inactive user jobs because this can crash whatever they 
were updating.  I wish we had this utility 
http://www.precosis.com.au/rv1.htm which permits us to transit to the 
abandoned session commands like F24 F12 F3 F6 F7 or whatever is needed to 
bring the task to closure without messing up the last whatever that the 
user was entering.

WRKSYSVAL has some settings you might want to check
* QDEVRCYACN  is *DSCMSG for us, meaning user has opportunity to try to 
recover the job
*  QDSCJOBITV is 90 minutes for us, meaning if the user not get back on in 
that time period, pull their plug
*  QSTRPRTWTR is 1 for us (we restart print writers after any downage)
* QSVRAUTITV  ours is  2,880 minutes
There may some others relevant to your OS/400 version

Check WRKCFGSYS on all your devices ... are they configured to be varied 
back on after a power outage, or re-IPL for other reasons?

> I'm having an intermittent problem with users 5250 sessions being ended
> while in query400 and the interactive job on the Iseries staying active.
> My users are either ending their 5250 sessions themselves or they are
> getting ended for some other reason, I'm not sure.  However, after the
> session is ended on their PC and the job on the Iseries is staying
> active.  This causes other jobs to fail because of records locks and
> other reasons.
>
>
>
> We have a routine that kills inactive device sessions, but it is not
> ending these jobs, I think it's because the end job command is doing a
> *CTLD end instead of an *IMMED end.
>
>
>
> Has anyone come across this problem in their shops?
>
>
>
> Joel B. Harvell
>
> Food Lion, LLC
>
> (704) 633-8250 x2709
>
> jbharvell@xxxxxxxxxxxx
>
>
>
>
> **************************************************************************
> This electronic message may contain confidential or privileged information
> and is intended for the individual or entity named above.  If you are
> not the intended recipient, be aware that any disclosure, copying,
> distribution or use of the contents of this information is prohibited.
> If you have received this electronic transmission in error, please notify
> the sender immediately by using the e-mail address or by telephone
> (704-633-8250).
> **************************************************************************
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.