RE: Sessions locked after DSPMSG -- MIDRANGE-L

I have had this problem on my client access sessions for a long time.  I use a 
break handling
program to do a SNDPGMMSG with parameters TOPGMQ(*EXT) MSGTYPE(*STATUS.  This 
causes my normal
messages to appear in the message line 25.

If I happen to be typing, or already input inhibited, it will lock my session.

It stinks.

Art Tostaine, Jr.
CCA, Inc.
Jackson, NJ 08527


-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of Brad Bird
Sent: Wednesday, March 29, 2000 3:07 PM
To: midrange-L@midrange.com
Subject: Sessions locked after DSPMSG


Got a puzzler!  Please help:

We have a 720 at V4R4.  Our users have a break message handling program that
checks for a special 1st character in a message to pop-up a window.  If not
one of the special characters (\,@,+) then it just executes the DSPMSG
command.  Since going to the 720 and V4R4, our users will "on occasion" get
their screens locked (input inhibited) when they receive a message.  The job
log will show the DSPMSG command as the last statement, the invocation stack
will show:
...
RMCITYI      IL         .DRVRX01
QWSGET       QSYS
QT3REQIO     QSYS
QWTPECTL     QSYS
QMHDLVMS     QSYS
CBRKMSG1     IL         6500
QMHDSMSS     QSYS
QWSSPEND     QSYS
QT3REQIO     QSYS

or

  DISHIS       IL         0000001988
< X_WS_EXFMT   QSYS       0000000061
    Procedure: _QRNX_WS_EXFMT
  QWSGET       QSYS
  QT3REQIO     QSYS

The first shows the break handler, CBRKMSG1 and the message display screen
QMHDSMSS displayed.  The second only shows as waiting on the user for entry.

I am unable to recreate the situation with my own job but it happens enough
with the users that we've got to find a solution.  I had one instance where
it sorta happened to my job, received a message that when I pressed enter it
left my screen with input inhibited.  I was executing a WRKSPLF command when
I got the message and that's what the screen showed as input inhibited,
however the WRKSPLF never showed up in my job log, only the DSPMSG command
from the break handler.

Our operator says when it sent job info to IBM they said it looked like we
had a break handler program causing the problem.  I don't see how.  Can
anyone help?

-------------------------
Brad Bird                         mailto:bbird@primeinc.com
Prime, Inc.                                http://www.primeinc.com
2740 N Mayfair
Springfield, MO  65803
phone:(417) 866-0001 x3211
fax:  (417) 521-6863

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---