Re: QRCVDTAQ (Receive Data Queue) program

Hello,

I found this thread in the archives. I refer to the following quote from "rob":

> (I always go on alert when I see this API as the subject in a forum.
> Not so much lately, but MCH3601 and MCH0601 due to misuse of this API
> used to be a very commonly reported problem in forums and in PMRs.)I have a 
> CL calling the QRCVDTAQ API to receive an entry on a keyed data queue. I get 
> an MCH3601 error on the line immediately after the call. It doesn't seem to 
> matter what that line of code is.
When I check the data queue, the entry has been successfully received (ie its 
not on the queue any more).
My code is as follows:

DCL VAR(&QNAMEO)  TYPE(*CHAR) LEN(10)
DCL VAR(&KEY)     TYPE(*CHAR) LEN(87) (key passed in)
DCL VAR(&WAITQ)   TYPE(*DEC)  LEN(5 0) (passed in - set to 7 seconds)
DCL VAR(&RPYDTA)  TYPE(*CHAR) LEN(2378) VALUE(' ')
DCL VAR(&SENDER)  TYPE(*CHAR) LEN(10)  VALUE(' ')
DCL VAR(&SNDLEN)  TYPE(*DEC)  LEN(3 0) VALUE(0)  
DCL VAR(&RPYLEN)  TYPE(*DEC)  LEN(5 0) VALUE(0)
DCL VAR(&RPYLEC)  TYPE(*CHAR) LEN(5) VALUE(' ')
:
:
CALL PGM(QRCVDTAQ) PARM(&QNAMEO '*LIBL     ' &RPYLEN &RPYDTA &WAITQ 'EQ' +
                        &KEYLEN &KEY &SNDLEN &SENDER)
CHGVAR VAR(&RPYLEC) VALUE(&RPYLEN) (MCH3601 on this line)

The data queue in &QNAMEO is a standard, keyed queue, key length=87, 
include_sender_id=*no, max_length=11721.

Can anyone see a problem with the above? If not, what else could be the cause 
of the problem. Any help would be greatly appreciated.

Nathan Hiley
----------------------------------------------------------------------
This message is intended for the addressee named and may contain
confidential information. If you are not the intended recipient,
please delete it and notify the sender. Views expressed in this
message are those of the individual sender, and are not necessarily
the views of REVS and the Office of Fair Trading.

The contents of this message has been automatically scanned, and
whilst all care is taken, it is the recipient's responsibility to
ensure that any attachments are scanned for viruses prior to use.
----------------------------------------------------------------------