RE: 5250 emulation locks up on XP

["Jim Damato" <jdamato@xxxxxxxxxxxxxxxxx>]

I'll give it a try, but I think our @#$%! software package has *BREAK
built into the master menu program.

-Jim 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tom Bishop
Sent: Tuesday, December 06, 2005 11:24 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: 5250 emulation locks up on XP

   It's a long shot but a few years ago my Client Access session would
lock
   up if I happened to be typing when a *break message occurred.
   I would submit a compile, open another source member, start making
   changes, and if I was typing when the break message arrived to tell
me the
   compile had completed, session locked.
   I changed my signon program to put my message queue in *notify mode
and
   the problem went away. I'm still using *notify.
   Here are the lines of code from my signon clp.

   CHGMSGQ    MSGQ(*WRKSTN) DLVRY(*NOTIFY)
   MONMSG     MSGID(CPF0000)              
   CHGMSGQ    MSGQ(*USRPRF) DLVRY(*NOTIFY)
   MONMSG     MSGID(CPF0000)              

   Thomas