2079 (081F) (RC2079): MQRC_TRUNCATED_MSG_ACCEPTED

puneetvirmani143 · New User Joined: 24 Jul 2007 Posts: 55 Location: noida

Hello Everyone

Details of the issue

One of the application program abended with issue mentioned in subject line.
On an MQGET call, the message length was too large to fit into the supplied buffer. Message length was too long for program to handle.

My requirement is to increase the bufferlength for a queue at application (program) level. I am not aware how parameter buffer length is handled in program.

Can anyone please advice how can we increase the buffer length in program.

puneetvirmani143 · New User Joined: 24 Jul 2007 Posts: 55 Location: noida

Hello Everyone

Can anyone help me out to resolve on this. Would be really appreciated

Robert Sample · Posted: Thu Mar 05, 2015 5:20 pm

The replies on this forum are by volunteers -- people who answer IF they have the knowledge, and the time, to post a reply. If you are not getting replies, it may be that nobody has the knowledge -- or time -- to respond to your post. Or it could mean that nobody wants to try to take the time to figure out what you mean by "bufferlength". You have not posted very much to help us -- no code, no exact error message (just your paraphrased interpretation). You don't even show us the MQGET code so we could see what you've put in it.

enrico-sorichetti · Posted: Thu Mar 05, 2015 6:41 pm

if instead of soliciting/waiting lazily for a forum reply You had googled
with ( for example ) MQGET CALL PARAMETERS

the first link returned

puneetvirmani143 · New User Joined: 24 Jul 2007 Posts: 55 Location: noida

Hi Robert

First time I am using MQseries in mainframes so I want to learn it from experts like you

I would explain the issue whatever I know

In one of our application, cobol program abended with below reason
2079 (081F) (RC2079): MQRC_TRUNCATED_MSG_ACCEPTED
2004 (07D4) (RC2004): MQRC_BUFFER_ERROR

While MQGET call ,The message length was too large for the application program to handle.
However I am not sure then how message was placed into message queue. Probably the message got truncated and then placed on Message queue.
But while MQPUT call the cobol program was not able to handle the length of message on queue.

Screen shot for MQGET call

MOVE MQCI-NONE TO MQMD-CORRELID.

COMPUTE MQGMO-OPTIONS = MQGMO-WAIT
+ MQGMO-ACCEPT-TRUNCATED-MSG
+ MQGMO-FAIL-IF-QUIESCING
+ MQGMO-CONVERT.

MOVE LENGTH OF W-MSGBUFFER OF W-INN-MSG TO W-MSGLENGTH.
COMPUTE W-HOBJ = W-HOBJ-APPL.

MOVE 'MQGET' TO W-MQ-KALL.

EXEC SQL
SET :W-MQWAIT-START = CURRENT TIMESTAMP
END-EXEC.

CALL 'MQGET' USING W-HCONN
W-HOBJ
MQMD
MQGMO
W-MSGLENGTH
W-INN-MSG
W-DATALENGTH
W-COMPCODE
W-REASON.
------------------------------------------------------------------ --> MQPUT call

COMPUTE W-MSGLENGTH =
LENGTH OF W-JLOG-HEADER + W-DATALENGTH.
COMPUTE W-HOBJ = W-HOBJ-JURLOGG.

MOVE 'MQPUT' TO W-MQ-KALL.

CALL 'MQPUT' USING W-HCONN
W-HOBJ
MQMD
MQPMO
W-MSGLENGTH
W-JLOG-MSG
W-COMPCODE
W-REASON.

COMPUTE W-COMPCODE-DISP = W-COMPCODE.
COMPUTE W-REASON-DISP = W-REASON.

I am not sure changing what parameter in program will resolve the issue.
It was my assumption that changing bufferlength can do this.

Please suggest how it can be fixed. Your suggestion would be really apprecisated.

karthick1990 · New User Joined: 12 Jun 2014 Posts: 4 Location: India

Also post how W-MSGLENGTH is declared. Is it S9(09) Comp ? . If not change it and try.

Marso · Posted: Mon Mar 09, 2015 6:45 pm

dbzTHEdinosauer · Posted: Mon Mar 09, 2015 8:24 pm

you can determine the max msg length established by the mq manager parms with an mqinq (i think, you have to look it up). that will tell you, among other things, the max msg length supported by the particular queue upon which you run the inq.

as several people have already stated,
your buffer size is set by the program executing the mget. this is working storage allocated by the program (or another addressed via linkage section).

so after determining the max size allowable by the queue manager for this queue, allocate the working storage buffer to the same length.

SIDE NOTE:
why people think they are clever and write programs allocating a length for their current project msg size, instead of allocating the max size???
the days of 16k memory are long gone......

puneetvirmani143 · New User Joined: 24 Jul 2007 Posts: 55 Location: noida

Thanks everyone for your suggestion.

I checked for the max msg length for the queue and below is the statitics

Maximum queue depth . . . . : 10000000 0 - 999999999
Maximum message length . . : 4194304 0 - 104857600

And below is the declaration of working storage variables in program

01 W-MSGLENGTH PIC S9(9) BINARY VALUE 0.

01 W-MSGLENGTH-MAX PIC S9(9) BINARY VALUE 4194304.
01 W-INPUTLENGTH PIC S9(9) BINARY VALUE 0.

05 W-MSGBUFFER.
10 W-MSGBUFFER-ARRAY PIC X(1) OCCURS 32767 TIMES.
10 W-MSGBUFFER-ARRAY PIC X(1) OCCURS 32647 TIMES.

Max message length (4194304) can come max upto 7 bytes and W-MSGLENGTH can hold value upto 9 bytes.

I am not sure why then pgm abended with 2079 and 2004 MQRC issue. Any suggestions