Search results for query: *

Alternatively, if you look at the jobs running in the QMQM subsystem you should see one called runmqlsr. Look at the joblog for this job and it should show the parameters that it was started with. If you don't see anything that means it was started without a port so will default to 1414...

Depending upon the platform you are running this on, if you run the command mqrc passing the Reason code as a parameter it will give you the meaning of the error message. In this case, mqrc 2035 returns "MQRC_NOT_AUTHORIZED". Your userid is not authorised to connect to the remote QMgr. As this...

That's pretty much what you need to do. Presumably if you're using J2EE you'll be using the MQ JMS classes?

Firstly you need to get the MQM Java classes installed onto your client machine. This is normally done by downloading the relevant IBM support pac for your platform and installing the Java option. Install the Developers Toolkit too. This will provide you with several examples of JMS code which...

What version of MQ are you using for your Java client? Only version 6 uses the chanel table.

If it's binary data that's being revesed it's probably the ENCODING attribute of the Message Descriptor that needs to be corrected. This is unusual as the source and target encodings are normally correct. Make sure that the encoding for the message as sent and as received are correct for the...

Don't forget that Reference messages are not supported on the Mainframe. Although not necessarily the best solution, a common method of doing this is for the putting program to read the first n bytes of the file, append a header detailing e.g. segment number 1, total bytes in file etc. and then...

The -b parameter means start dumping from the start of the active log. You need to specify -s or -n instead. Check out the System Admin guide for full details. MQ 5.1 is very very old and long out of support so I can't guarantee that these options were available then. You really should be...

This is a bit old but I was wondering if you've sorted it out HS. Can you start all 3 pairs of channels simultaneously (with no messages flowing)? aixmurderer ( :-) )- You can have multiple Receiver channels and a single sender. The Receiving QMgr maintains one sequence number for each sender...

What you've done should work fine, as long as the 3 sending QMgrs are on different hosts. I think that MQ keeps track of the different Channels by their IP addresses. Are your senders on different hosts?

Are you specifying CONVERT for the browse? If not, it will fill in the CCSID of your Message Descriptor structure with the original CCSID of the message. Then unless you reset this to your local CCSID subsequent GETs will not convert as the message is already in this CCSID. If the first Browse...

Just to be sure, the format needs to be 'MQSTR '. Cheers, Paul

... and... is it in the exits directory or are you providing a fully qualified path as well? Cheers, Paul

How are you specifying it on the channel? If this is Windows and you linked this into a DLL called myexits.dll I would expect you to specify it like this: alter channel .... scyexit('myexits(ChannelExit)') Cheers, Paul

I've not heard of any incompatibilities between the 2 releases. Are you sure you haven't enabled SSL on the 5.3 channel? Is there anything in either of the logs that might indicate the problem? You could post the channel defs for both channels and we can take a look at them. Cheers, Paul

1) No, a JMS app can exchange messages with a C++ app. However, JMS messages are in a specific format (using XML). See the FAQ for what you need to specify to send a on-JMS messge from a JMS application. 2) JMS applications can use cluster queues but you must ensure that the QMgr name for the...

You could try using the AMQICLEN command to delete the IPC resources instead. I believe it taks a QMgr name as one of the parameters. Note that although it doesn't say so, you need to run it as root! Cheers, Paul

A reasonably simple way to do this is to use the supplied Dead Letter Handler (runmqdlq - assuming you're not on the mainframe or AS/400). You just need to set up a simple rules table and tell it to retry the messages you're interested in. See the System Administration manual for full details...

Kevin is correct that a Remote Queue definition with a blank RQueueuName is a QMgr Alias. Any messages put to such a queue would actually be put onto the XmitQ with the same name as the RemoteQMgr field of this QMgr alias. Just tried to put a message to a Remote queue with no RemoteQueueName...

Agree entirely with KK but would just add that you need to make sure that you have made your data 'safe' before you commit the MQGET. E.g. if you get a message, commit and then due to some delay in processing your app dies before you've written it to wherever it needs to go then you've lost your...