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 » URGENT!! Unique Sender Error

Post new topic  Reply to topic Goto page 1, 2  Next
 URGENT!! Unique Sender Error « View previous topic :: View next topic » 
Author Message
insertcoin
PostPosted: Wed Oct 10, 2007 1:13 am    Post subject: URGENT!! Unique Sender Error Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

Hi Guys

Please help me with this:

Unexpected return code, '20', from command 'RUNMQCHI -qSYSTEM.CHANNEL.INITQ -m xxxxx'.

An unexpected return code, '20', was returned by command 'RUNMQCHI -qSYSTEM.CHANNEL.INITQ -m xxxxxxx'. This command was issued by the WebSphere MQ service for queue manager 'xxxxxx'.

Verify that the command and parameters are correct.


I cant get my sender channel back up, I keep getting an "in use" error.
Error Code: 4063.....

MQRC 4063 - MQRCCF_MQSET_FAILED


This is super urgent!
How do I get them back up? I guess I have to successfully close them 1st... how?

Much appreciated!
Justin
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 1:20 am    Post subject: Reply with quote

Grand High Poobah

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

What's already failed? There's no point us suggesting stuff that's not worked.

I'm thinking here of stopping the sender & receiver, checking for indoubt transactions, killing the channel initiator and/or the command server, restarting the queue manager, etc, etc, etc

How much of that have you tried (and that list is not intended as exhaustive!)?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Oct 10, 2007 1:21 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Are there error messages in the AMQERR file? Are there FDCs thrown? Does runmqsc list channels in a running state?

Did you run out of MaxActiveChannels? Is the channel initiator running already? Are you trying to start it manually? What version of WMQ? What platform?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 1:21 am    Post subject: Reply with quote

Grand High Poobah

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

You might also want to share:

- level of MQ
- platform
- any FDC files or log entry contents
- what happened immediately prior to the problem manifesting

Context is always useful.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 1:34 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

ok woah!

Windows 2000
MQ 5.0 service pack 4

Prior to the problem: Umm, I found out the reason why the one sender channel was failing: I did a few things and the messages started going again... then my other senders went down.

I have tried stopping, back out, starting... I havent reset the message number as the files on the channel are really important!
should anything happen to these messages, Im dead.

I have to talk to the banks to get their CURLUWID.
If the ID's are mismatched, how to I get them to match up again?
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 1:39 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

I have pinged the other side successfully, so that isnt the problem.

Is there a way for me to check the ID of the receiver from my side?

Whats an FDC?

No, the status is now inactive... and everytime I try start it I get 4063.

I killed the services: Listener and Channel Initiator, I then restarted them...
Is there something I should do when the channel initiator is stopped?

I havent done anything with the Command Server service, im not sure what the impact of switching that off would be.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 1:44 am    Post subject: Reply with quote

Grand High Poobah

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

insertcoin wrote:
MQ 5.0 service pack 4


If you're serious, I've found your problem. That version is so old on distributed platforms Noah used it to control functions on the ark.

insertcoin wrote:
should anything happen to these messages, Im dead.


Where do you want the flowers sent? The out of support software just blew in your face.

insertcoin wrote:
If the ID's are mismatched, how to I get them to match up again?


Banks? Do they know what version you're on?

You need to resolve the channels BUT if the PCF error you're getting means what I think it means that may not help. I certainly would want to guarantee they'll be no message loss.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 1:50 am    Post subject: Reply with quote

Grand High Poobah

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

insertcoin wrote:
Is there a way for me to check the ID of the receiver from my side?


No

insertcoin wrote:
Whats an FDC?


Queue manager dump file - look for *.FDC

insertcoin wrote:
No, the status is now inactive... and everytime I try start it I get 4063.


The channel is now is an inconsistant state sender <-> receiver so it won't start anyway. That 4063 from the START command is bad news, I'm uncertain that the RESOLVE won't go the same way and even if it works I'm highly uncertain that you could rely on the data being recovered at one end or the other. I suspect you've found a bug in the MCA software.

Under other circumstances I'd suggest a PMR with IBM, but v5.0 is so far out of support it's not funny.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 1:52 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

Yes Im serious, Ive been handed 3 peoples mess ups for the past 3-5 years and now im trying to bring everything up to speed.

Suggestions? Its a production MQ so upgrading would 1st have to go through Dev and QA before changes go to PROD. Im planning on upgrading Dev and QA to Version 6... but thats still a work in progress.

Flowers:
57 Sloane Street Bryanston
1st Floor, Wanderers Building
Interfile
The Campus

I dont know if they are aware of the version Im working on.
The channels were working when I logged in this morning!

How do I go about RESOLVING the channel?
PCF Error?
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 1:56 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

Yea, I checked the FDC file and there is just a whole lot of info I have no idea to understand.

Would the MQM Trace History help?
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 1:59 am    Post subject: Reply with quote

Grand High Poobah

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

insertcoin wrote:
Yes Im serious, Ive been handed 3 peoples mess ups for the past 3-5 years and now im trying to bring everything up to speed.


I'd say it's been left to late. v5.0 in production?

insertcoin wrote:
How do I go about RESOLVING the channel?
PCF Error?


RESOLVE is a admin command issued via runmqsc - it's in the system admin manual. I repeat that I am highly uncertain of what will happen data wise if you try it and accept no responsibility if you try it.

PCF error seems to be the root cause of your 4063, which is why I was asking about the command server.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Oct 10, 2007 2:01 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Unless you're seeing specific error messages that tell you that the channels are out of sequence, then don't try and reset the channel sequence number.

I assume that these messages are persistent?

I think you need to shut down the queue manager entirely, take a good solid backup of the system as it is right now (including the log files and the q files!), and then since this is Windows, reboot the machine. Then see what comes up automatically, what happens when you start the qmgr, and what happens when you try to start channels again.

In the meantime, restore the backup somewhere else, so you can attempt message recovery. One possible tool for this is made by our premier sponsor, Cressida.

If your messages are non-persistent, then you're out of luck... but clearly they weren't THAT important to begin with.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Oct 10, 2007 2:02 am    Post subject: Reply with quote

Grand High Poobah

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

insertcoin wrote:
Yea, I checked the FDC file and there is just a whole lot of info I have no idea to understand.


The probe id at the top is worth a Google. I have this contact admin feeling any hits will contain the phrase "fixed in ...."

insertcoin wrote:
Would the MQM Trace History help?


Not really.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 2:03 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

yea, 5.0 in prod.

I have already tried that command. Its something like this:

RESOLVE CHSTATUS(channelName) ACTION(BACKOUT)

and... I tried to commit too... nothing.

So you are suggesting I stop the Command Server and then restart it?
Back to top
View user's profile Send private message
insertcoin
PostPosted: Wed Oct 10, 2007 2:08 am    Post subject: Reply with quote

Acolyte

Joined: 07 Jun 2007
Posts: 61
Location: who knows!?

...

All of them say that it was fixed in V5.3 pack 6-13....

I always told myself I want a nice bouquet of yellow and red roses on my coffin!

I only want to let the banks know about this if I can tell them how to fix it.
Instead of them being aware of it, and then timing me and following up and escalating and all the rest.

Would a stop on both sides and a reset on both sides correct this?

If I could get the upgrade to go into prod tonight, what kind of complications could arise?!
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » General IBM MQ Support » URGENT!! Unique Sender Error
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.