Re: wrkqry/runqry and 5250 emulation ending

I would set the controlled ending to 60 or 120 seconds.
When it reaches that max, if not yet ended, will switch to *immed.
jim

To: <Midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, April 11, 2006 3:17 PM
Subject: wrkqry/runqry and 5250 emulation ending

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.