RE: Issue with SNDUSRMSG not breaking for response.

That's what the person is running into.  They are not using a MESSAGE FILE,
just a custom typed message.  So the severity level isn't set.  Is it set
to 00 when using a custom message?  Plus, the severity level filter is set
to 40.

Michael Schutte
Work 614-492-7419
email  michael_schutte@xxxxxxxxxxxx


                                                                           
             "Jim Wiant"                                                   
             <Jim.Wiant@foodst                                             
             uffs.co.nz>                                                To 
             Sent by:                  "Midrange Systems Technical         
             midrange-l-bounce         Discussion"                         
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>           
                                                                        cc 
                                                                           
             03/23/2006 03:16                                      Subject 
             PM                        RE: Issue with SNDUSRMSG not        
                                       breaking for response.              
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
             <midrange-l@midra                                             
                 nge.com>                                                  
                                                                           
                                                                           




I wrote a module to send messages to QSYSOPR and wait for responses. I
built it around the QMHSNDM api (Send Non-Program Message) - but
SNDUSRMSG works too. It allows you to specify the message queue of
*SYSOPR. You don't want to send it to the user *SYSOPR.

One issue you might be running into is that not all messages allow a
response. That's determined by how the message is set up in the message
file. Some messages don't allow a reply value, therefore no intervention
is required from the QSYSOPR message queue to respond to the message.
Other messages have default values the system enters for you.

For example, there's a generic message CPF9898 located in the message
file QSYS/QCPFMSG. That message allows 1 parm, but does not define any
responses. If you send that message ID, no response will be allowed.

Try This:
            PGM

            DCL        VAR(&BLA) TYPE(*CHAR) LEN(1)
            SNDUSRMSG  MSGID(CPA3708) MSGF(QSYS/QCPFMSG) +
                         MSGDTA('TEST   TEST2     ') +
                         TOMSGQ(*SYSOPR) MSGRPY(&BLA)
EXIT:       ENDPGM

The variable &BLA will have the entered response.

To work with messages and allow response values, the command is WRKMSGF.
To see how the message example I used is set up to allow responses and
the input display values, enter WRKMSGF QSYS/QCPFMSG, locate the CPA3708
command, and take a look.

Best wishes

JPW





The bitterness of poor quality remains long after low pricing is
forgotten!



Cautillo, Leon M.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Imtiaz Ahmed
Sent: Friday, 24 March 2006 4:50
To: midrange-l@xxxxxxxxxxxx
Subject: Issue with SNDUSRMSG not breaking for response.


Can any one please let me know what I am missing here? I am using a
simple CL program to send an inquiry message to QSYSOPR message queue.
It sends the message but does not wait for a response. I ran the program
in Debug and the &REPLY value returned is *N. I also tried with a MSGID
CPF9898 but still the same results. I did check the message queue
setting for QSYSOPR and the delivery option is set for *BREAK. Any help
in this regards is most appreciated.

>

>             PGM        PARM(&MSG)


>

>             DCL        VAR(&RPLY) TYPE(*CHAR) LEN(1)


>

>             DCL        VAR(&MSG)  TYPE(*CHAR) LEN(99)


>

>


>

>             SNDUSRMSG  MSG(&MSG) VALUES(Y) MSGTYPE(*INQ) +


>

>                          TOUSR(*SYSOPR) MSGRPY(&RPLY)


>

>


>

>             ENDPGM


>



Imtiaz M.Ahmed

Senior Programmer Analyst

Dollar General Corporation

100 Mission Ridge

Goodlettsville, TN 37072

615.855.4358

iahmed@xxxxxxxxxxxxxxxxx



--
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.


######################################################################
This message was scanned for compliance with Foodstuffs email policies
######################################################################
This message has been sent from Foodstuffs (Auckland) Limited
("Foodstuffs").

The information contained in this message and or attachments
is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other
use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended
recipient is prohibited. If you received this in error,
please contact the sender and delete the material from any
system and destroy any copies.

The views and opinions expressed in this message may be those
of the individual and not necessarily those of Foodstuffs,
and are not given or endorsed by it.

Please note that this communication does not designate an
information system for the purposes of the Electronic
Transactions Act 2002.

--
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.