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 » WebSphere Message Broker (ACE) Support » MQInput node problem

Post new topic  Reply to topic
 MQInput node problem « View previous topic :: View next topic » 
Author Message
dn415
PostPosted: Fri Feb 07, 2003 2:30 pm    Post subject: MQInput node problem Reply with quote

Novice

Joined: 01 Jul 2002
Posts: 10

Hi all,

Quick question. I have an MQInput node listening to a local queue on a
Solaris QM with option to Convert CCSID to 1208.

95% of the files I send from my MVS QM (ccsid 500) to this qm go thru fine
and gets converted. But sometimes one message gets held up and then routed
to dead-letter and this shows up in mq log (2times per message):

02/07/03 14:39:30
AMQ6174: The library /var/mqm/exits//MQSTR was not found. The queue manager
will continue without this module.

EXPLANATION:
The dynamically loadable file /var/mqm/exits//MQSTR was not found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory.
----------------------------------------------------------------------------
---
02/07/03 14:39:30
AMQ6174: The library /var/mqm/exits//MQSTR was not found. The queue manager
will continue without this module.

EXPLANATION:
The dynamically loadable file /var/mqm/exits//MQSTR was not found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory.


Any ideas why or what this means? Thanks for your time!

Thanks,
Duke
dn415@ucla.edu
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger
EddieA
PostPosted: Mon Feb 10, 2003 12:17 pm    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

Make sure the Format field in the MQMD is MQSTR follwed by 3 blanks or nulls.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
whiting
PostPosted: Tue Feb 11, 2003 5:50 am    Post subject: Message format Reply with quote

Acolyte

Joined: 26 Mar 2002
Posts: 64
Location: Greenville, SC

The error messages indicate that MQSeries is looking for a conversion exit to handle the message.

Make sure that the message format is SPACE padded, not NULL padded.
Back to top
View user's profile Send private message Send e-mail
jfluitsm
PostPosted: Wed Feb 12, 2003 5:16 am    Post subject: Reply with quote

Disciple

Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands

Even better is not to use the Convert-options and let the conversion to the broker instead of the queue-manager.
_________________
Jan Fluitsma

IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6
Back to top
View user's profile Send private message Send e-mail
whiting
PostPosted: Wed Feb 12, 2003 5:39 am    Post subject: Message format Reply with quote

Acolyte

Joined: 26 Mar 2002
Posts: 64
Location: Greenville, SC

Although I haven't tested it, I expect that letting MQ do the string conversion would be more efficient than having the broker do it.

//Bill
Back to top
View user's profile Send private message Send e-mail
jfluitsm
PostPosted: Wed Feb 12, 2003 7:06 am    Post subject: Reply with quote

Disciple

Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands

That is not entirely true, the broker uses UCS-2 as encoding, so UTF-8 is translated again to UCS-2, this translation howerver will be quick as this conversion can be done by bit-manipulation.

There are more reasons for converting by the broker:
- It is the recommended method and there are knwon issues when using the convert option (especially when converting from SBCS to DBCS or UTF-8, see readme.txt in the WMQI directory, 'All operating systems' section, item 30).
- You don't have to worry about the conversion and what CCSID to use as long as the input message has the correct CCSID.
- The conversion depends on messagedomain instead of MQMD.Format, BLOB isn't converted, XML is converted, MRM is converted according to the message definition.
- Non-text message can be converted (MRM-messages)
- The conversion is done during parsing, when a message is only partially parsed or not parsed at all it is converted partially or not at all.
- When converting by the qmanager to a non-Unicode CCSID you might compromise the message content.
_________________
Jan Fluitsma

IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQInput node problem
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.