May 11, 2006. Because I only want the messages that are not automatically responded to to break on the display in the computer room for the operator to respond to. If an *inq message breaks on the qsysopr message queue the operator will assume a response is needed. But if the background job is responding every. A SNDBRKMSG command can also cause a break, but SNDBRKMSG can only be used to send a message to a Work Station message queue (QSYSOPR is not a Work Station message queue). The TAAMSHXC2 program in TAATOOL is used as the break handling program. To set a message queue to this function, enter:.

Re: msgq break handling program • From: 'gb' • Date: Thu, 11 May 2006 21:39:29 GMT scott1328@xxxxxxx wrote: The command help for CHGMSGQ says specifically to not assign a break handling program for the QSYSOPR message queue. That seems to be overly restrictive wording on the part of IBM. Or perhaps IBM knew that it wasn't going to be that easy to do it - as you are now finding out.;-) because I only want the messages that are not automatically responded to to break on the display in the computer room for the operator to respond to. If an *inq message breaks on the qsysopr message queue the operator will assume a response is needed. But if the background job is responding every interval to some messages things could ge confusing.

So, why not have a second message queue (QSYSOPR2) also in break mode in the QSYSOPR job. In your break handing program, pass any messages that need attention to the QSYSOPR2 queue. In your break handling program, loop around before returning and read any messages that have arrived in the meantime. This (should) hopefully get around the not-being-called-if-already-active problem and the operator will still respond to break messages in his/her usual way. • Follow-Ups: • • From: Steve Richter • References: • • From: Steve Richter • • From: Jonathan Bailey • • From: Steve Richter • • From: scott1328 • • From: Steve Richter • • From: scott1328 • • From: Steve Richter • Prev by Date: • Next by Date: • Previous by thread: • Next by thread: • Index(es): • •.

You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the and the. Mode for every 'Job completed. Kaspersky Com Keygen. ' However, I don't want inquiry messages sitting without response for long periods.

Instead, I have a break-handling program that manages incoming messages according to what kind of message is received. Messages requiring a response will break into my current job. Other messages display, as they are received, on the message line without interrupting me. /* The following three input parameters are standard for a + 'Break Handling' program.

*/ PGM PARM(&MSGQ &MSGQLIB &MSGKEY) DCL &MSGQ *CHAR 10 /* Queue where the msg is. */ DCL &MSGQLIB *CHAR 10 /* Queue library. */ DCL &MSGKEY *CHAR 4 /* Key of the received msg.

*/ DCL &MSGID *CHAR 7 /* ID of the received msg. */ DCL &RTNTYPE *CHAR 2 /* Type of the received msg. */ DCL &MSG *CHAR 78 /* Msg text.

*/ DCL &OPEN *CHAR 1 VALUE(X'21') /* Rev img. */ DCL &CLOSE *CHAR 1 VALUE(X'20') /* Normal attrib. */ /* When your message queue is in *BREAK mode and a + break handling program is assigned, the program + is automatically called when a message arrives + and the three parameters are apssed so that the + message can be received. */ RCVMSG MSGQ(&MSGQLIB/&MSGQ) MSGKEY(&MSGKEY) + RMV(*NO) MSG(&MSG) MSGID(&MSGID) + RTNTYPE(&RTNTYPE) /* Message type '05' is an *INQ type message. Show + the 'Display Messages' screen so that the message + can be responded to. */ IF COND(&RTNTYPE = '05') THEN(DSPMSG + MSGQ(&MSGQLIB/&MSGQ)). /* When a batch job you have submitted gets an error + message in QSYSOPR, you get a CPI2404 sent to you.