ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » mqrc 2119, AMQ7924: Bad length in the PCF header

Post new topic  Reply to topic
 mqrc 2119, AMQ7924: Bad length in the PCF header « View previous topic :: View next topic » 
Author Message
gerimqseries
PostPosted: Mon Jan 04, 2016 2:41 am    Post subject: mqrc 2119, AMQ7924: Bad length in the PCF header Reply with quote

Apprentice

Joined: 03 Aug 2009
Posts: 30

Dear Support Team,

Our application gets segmented MQ messages by the queuemanager.
The MQ produced an FDC file, and the AMQ7924 error message in the AMQERR01.LOG, but I cannot find relevant information about the solution.
I could reproduce the problem, so I was trace the MQ, but it is too big to attach here, I should send if someone need it.
I copied the errors below, if someone need more information, please ask me to send it.
Any help would be appreciated!

AMQERR01.LOG
*************************
12/23/15 14:31:56 - Process(3351.432) User(mqm) Program(amqrmppa)
Host(lxveld1)
AMQ7924: Bad length in the PCF header (length = 4206866).

EXPLANATION:
Message data conversion cannot convert a message in Programmable Command Format
(PCF) because the PCF header structure contains an incorrect length field.
Either the message has been truncated, or it contains data that is not valid.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Do not discard these files
until the problem has been resolved. Use the file containing the Message
Descriptor of the message to determine the source of the message and to see how
data that is not valid became included in the message.


MQ trace - AMQ3351.0.FMT:
***************
09:24:26.222056 3351.407 RSESS:000174 fromCCSID:870 toCCSID:1208, in length:4193792, out length:33554432 options: 00000001
09:24:26.222062 3351.407 RSESS:000174 EBCDIC->ASCII conversion uses new line as in tables, not LF.
09:24:26.291072 3351.407 RSESS:000174 translated out length:4206866
09:24:26.291080 3351.407 RSESS:000174 -----------} xcsConvertString rc=OK
09:24:26.291083 3351.407 RSESS:000174 ----------} vxtConvertCharsFn rc=OK
09:24:26.291086 3351.407 RSESS:000174 ---------} vwb_string rc=OK
09:24:26.291089 3351.407 RSESS:000174 --------} vwaConvert rc=OK
09:24:26.291095 3351.407 RSESS:000174 --------{ xcsFFST
09:24:26.291107 3351.407 RSESS:000174 ErrorCode :- 20007924 Numeric Insert1 :- 00403112 (4206866) Numeric Insert2 :- 003ffe00 (4193792)
09:24:26.291111 3351.407 RSESS:000174 ---------{ xcsGetMessage
09:24:26.291116 3351.407 RSESS:000174 msgid:20007924 a1:00403112 a2:003FFE00 c1:(null) c2:(null) c3:(null)


FDC:
****************
09:24:26.295486 3351.407 RSESS:000174 | Date/Time :- Tue December 22 2015 16:33:48 CET |
09:24:26.295491 3351.407 RSESS:000174 | UTC Time Offset :- 60 (CET) |
09:24:26.295494 3351.407 RSESS:000174 +-----------------------------------------------------------------------------+
09:24:26.295497 3351.407 RSESS:000174 | |
09:24:26.295500 3351.407 RSESS:000174 | WebSphere MQ First Failure Symptom Report |
09:24:26.295503 3351.407 RSESS:000174 | ========================================= |
09:24:26.295505 3351.407 RSESS:000174 | |
09:24:26.295508 3351.407 RSESS:000174 | Date/Time :- Wed December 23 2015 09:24:26 CET |
09:24:26.295511 3351.407 RSESS:000174 | UTC Time :- 1450859066.292579 |
09:24:26.295514 3351.407 RSESS:000174 | UTC Time Offset :- 60 (CET) |
09:24:26.295517 3351.407 RSESS:000174 | Host Name :- lxveld1 |
09:24:26.295519 3351.407 RSESS:000174 | Operating System :- Linux 3.0.101-65-xen |
09:24:26.295522 3351.407 RSESS:000174 | PIDS :- 5724H7230 |
09:24:26.295525 3351.407 RSESS:000174 | LVLS :- 7.0.1.11 |
09:24:26.295535 3351.407 RSESS:000174 | Product Long Name :- WebSphere MQ for Linux (x86-64 platform) |
09:24:26.295538 3351.407 RSESS:000174 | Vendor :- IBM |
09:24:26.295541 3351.407 RSESS:000174 | Probe Id :- VP000002 |
09:24:26.295544 3351.407 RSESS:000174 | Application Name :- MQM |
09:24:26.295547 3351.407 RSESS:000174 | Component :- vpiConvertData |
09:24:26.295549 3351.407 RSESS:000174 | SCCS Info :- lib/zst/amqvcona.c, 1.30.12.6 |
09:24:26.295552 3351.407 RSESS:000174 | Line Number :- 1017 |
09:24:26.295555 3351.407 RSESS:000174 | Build Date :- Sep 25 2013 |
09:24:26.295558 3351.407 RSESS:000174 | CMVC level :- p701-111-130925 |
09:24:26.295561 3351.407 RSESS:000174 | Build Type :- IKAP - (Production) |
09:24:26.295564 3351.407 RSESS:000174 | Effective UserID :- 501 (mqm) |
09:24:26.295566 3351.407 RSESS:000174 | Real UserID :- 501 (mqm) |
09:24:26.295570 3351.407 RSESS:000174 | Program Name :- amqrmppa |
09:24:26.295573 3351.407 RSESS:000174 | Addressing mode :- 64-bit |
09:24:26.295576 3351.407 RSESS:000174 | Process :- 3351 |
09:24:26.295578 3351.407 RSESS:000174 | Process(Thread) :- 10449 |
09:24:26.295581 3351.407 RSESS:000174 | Thread :- 407 |
09:24:26.295584 3351.407 RSESS:000174 | ThreadingModel :- PosixThreads |
09:24:26.295587 3351.407 RSESS:000174 | QueueManager :- LXVELD1QM |
09:24:26.295590 3351.407 RSESS:000174 | UserApp :- FALSE |
09:24:26.295593 3351.407 RSESS:000174 | ConnId(1) IPCC :- 2788 |
09:24:26.295596 3351.407 RSESS:000174 | ConnId(3) QM-P :- 612538 |
09:24:26.295599 3351.407 RSESS:000174 | Last HQC :- 3.0.0-48064 |
09:24:26.295602 3351.407 RSESS:000174 | Last HSHMEMB :- 0.0.0-0 |
09:24:26.295604 3351.407 RSESS:000174 | Major Errorcode :- vrcE_BAD_LENGTH_1 |
09:24:26.295607 3351.407 RSESS:000174 | Minor Errorcode :- OK |
09:24:26.295610 3351.407 RSESS:000174 | Probe Type :- MSGAMQ7924 |
09:24:26.295613 3351.407 RSESS:000174 | Probe Severity :- 2 |
09:24:26.295616 3351.407 RSESS:000174 | Probe Description :- AMQ7924: Bad length in the PCF header (length = |
09:24:26.295618 3351.407 RSESS:000174 | 4206866). |
09:24:26.295622 3351.407 RSESS:000174 | FDCSequenceNumber :- 4 |
09:24:26.295624 3351.407 RSESS:000174 | Arith1 :- 4206866 (0x403112) |
09:24:26.295627 3351.407 RSESS:000174 | Arith2 :- 4193792 (0x3ffe00) |
09:24:26.295631 3351.407 RSESS:000174 | |
09:24:26.295634 3351.407 RSESS:000174 +-----------------------------------------------------------------------------+


Thank You!
Back to top
View user's profile Send private message
smdavies99
PostPosted: Mon Jan 04, 2016 3:50 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

So why would a segmented message have a PCF header? That does not sound right to me
Can you take a dump of the offending message(s) with something like amqsbcg?

Otherwise, it looks like a PMR Issue.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon Jan 04, 2016 5:06 am    Post subject: Re: mqrc 2119, AMQ7924: Bad length in the PCF header Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

gerimqseries wrote:
Dear Support Team


We're not a support team. Or even your support team.

We're a random collection of strangers on the internet, who may or may not help you, and may or may not be nice about responding to you.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
gerimqseries
PostPosted: Mon Jan 04, 2016 6:06 am    Post subject: Re: mqrc 2119, AMQ7924: Bad length in the PCF header Reply with quote

Apprentice

Joined: 03 Aug 2009
Posts: 30

mqjeff wrote:
gerimqseries wrote:
Dear Support Team


We're not a support team. Or even your support team.

We're a random collection of strangers on the internet, who may or may not help you, and may or may not be nice about responding to you.


Yes I know, but I did not find a better addressee. Next time I will pay more attention.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon Jan 04, 2016 6:08 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

"Folks", "experts", "random strangers on the internet", "people with too much time on their hands", anything really.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Jan 04, 2016 6:20 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

mqjeff wrote:
"Folks", "experts", "random strangers on the internet", "people with too much time on their hands", anything really.


"Chaps"?

"All"?

What my most worthy associate is correctly trying to do is underline that we're not any kind of support team with any kind of SLA, nor does our advice come with any kind of backing save our perceived wisdom.

In contrast with (for example) the support team on the back of a PMR, which has clearly defined SLAs and who's advice comes with the full weight of IBM behind it.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Jan 04, 2016 6:21 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

smdavies99 wrote:
So why would a segmented message have a PCF header? That does not sound right to me
Can you take a dump of the offending message(s) with something like amqsbcg?




smdavies99 wrote:
Otherwise, it looks like a PMR Issue.



_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
gerimqseries
PostPosted: Mon Jan 04, 2016 6:28 am    Post subject: Reply with quote

Apprentice

Joined: 03 Aug 2009
Posts: 30

smdavies99 wrote:
So why would a segmented message have a PCF header? That does not sound right to me
Can you take a dump of the offending message(s) with something like amqsbcg?

Otherwise, it looks like a PMR Issue.


I checked the code with a developer, which creates the message, it is not manipulating any MQEPH fields.
Unfortunately, the 7.0.1 mq version is unsupported right now, I can not open a PMR.
If You want to get extra data, please write me to gerimqseries@gmail.com.

Now the workaround is to set the queues and channels MAXMSGL property to a higher value, then the message will be not segmented, and there is no error when mqget issued.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » mqrc 2119, AMQ7924: Bad length in the PCF header
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.