Re: 5250 emulation locks up on XP

I am guessing that by multi-session you mean more than one PC5250
session on the PC, rather than the use of SysReq/1 for multiple
sessions on the same workstation job.

This seems like a lark, but given that you only see the problem with
multi-session users, it may be worth a try.   On the communication
configuration screen, there are options to control the device name and
avoid duplicate names on the workstation and with other workstations. 
Perhaps playing with them might get you somewhere.  I usually check
them both, and set the device name to be the computer name.

The only other thing I can suggest is to make sure that the iSeries
and the clients are at the latest PTF level.  If they are, perhaps
removing service packs from the client or removing PTF's from the
server will fix it.

Take care, good luck.

On 12/6/05, Jim Damato <jdamato@xxxxxxxxxxxxxxxxx> wrote:
> * Happens on different apps.
> * Not easily replicated.  We can bang on a workstation for hours and not
> lock.  It does, however, only happen to multi-session users.
> * No predictable buffer behavior -- can happen when they key one screen
> or four screens ahead.
> * I'm gonna get our PCS group to try Win 2K.
> * The PC models are probably the same.  I'll see if I can get someone to
> try unlike hardware.
> * The applications will never be improved.
>
> I'll keep you posted.  Much thanks...
>
> -Jim
>
> -----Original Message-----
> From: midrange-l-bounces+jdamato=dollargeneral.com@xxxxxxxxxxxx
> [mailto:midrange-l-bounces+jdamato=dollargeneral.com@xxxxxxxxxxxx] On
> Behalf Of Paul Morgan
> Sent: Tuesday, December 06, 2005 9:24 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Re: 5250 emulation locks up on XP
>
> Jim,
>
> I haven't seen anything like this but other things I'd be trying to
> isolate
> the problem:
>
> Does it always happen with the same app or different apps?  Or maybe it
> always happens on the same screen?  (If lockup occurs with different
> applications or screens then you can likely rule out the application as
> the
> problem).
>
> Could you replicate the problem by just holding down a key on the
> keyboard?
> (maybe it's a certain sequence of keys causing the problem)
>
> Does it happen when the users type too far ahead? (could be filling up
> the
> type ahead buffer)
>
> Maybe the buffer problem is in Windows XP.  It didn't happen on Windows
> 2000?  Could you install Windows XP on some of the old hardware and see
> if
> you get the overflow problem with the old hardware but with Windows XP?
>
> Maybe it's a PC hardware problem.  Are all the new Windows XP machines
> the
> same model?  Do you have a different model of PC running Windows XP that
> also has the lockup?  Could you install Windows 2000 on the new hardware
> and
> see if you get the lockup?
>
> Also, have you taken a look at these applications to see if you can
> speed up
> their interactive performance?  If they are doing a lot of updates that
> take
> awhile maybe throw some data in a data queue and let a batch program do
> the
> updates.  Maybe the screen I/O could be tweaked with some changes to the
> display file and the way the program formats the screen.
>
> Paul
>
>
> --
> 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.
>
>


--
Tom Jedrzejewicz
tomjedrz@xxxxxxxxx