It looks like you didn't specify a channel when you
used the -client option.  I'm not sure if it has a
default or not, but it would be safer to specify it.

Ron

--- Meital Geron-Issers
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am using Windows2000 on the server & client
> machines.
> I searched on the installation guide but I could not
> find something helpful.
> I am getting this error when I am trying to run the
> IVTRun program with the
> -client option. Otherwise, I mean without -client ,I
> success to run this
> program.
> In addition to this, I success to use the
> amqsput.exe program and put a
> message in the queue.
>
> Enclosed a part of the error log I found under
> <installation
> dir>\qmgrs\queue!manager\errors folder:
>
> AMQ9503: Channel negotiation failed.
>
> EXPLANATION:
> Channel '' between this machine and the remote
> machine could not be
> established
> due to a negotiation failure.
> ACTION:
> Tell the systems administrator, who should attempt
> to identify the cause of
> the
> channel failure using problem determination
> techniques.  For example, look
> for
> FFST files, and examine the error logs on the local
> and remote systems where
> there may be messages explaining the cause of
> failure.  More information may
> be
> obtained by repeating the operation with tracing
> enabled.
>
> AMQ9228: The TCP/IP responder program could not be
> started.
>
> EXPLANATION:
> An attempt was made to start an instance of the
> responder program, but the
> program was rejected.
> ACTION:
> The failure could be because either the subsystem
> has not been started (in
> this
> case you should start the subsystem), or there are
> too many programs waiting
> (in this case you should try to start the responder
> program later). The
> reason
> code was 0.
>
>
> Do you have any clue what could be the problem?
> What do they mean by writing 'subsystem'?
>
> Thanks
> Meital
>
> -----Original Message-----
> From: Arvind Chaudhary
> [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 04, 2003 12:21 PM
> To: [EMAIL PROTECTED]
> Subject: Re: failed to connect queue manager
>
>
>
> "consult the FDC file to obtain more detail about
> the problem."
>
> You will find it under <installation dir>\Errors on
> Windows. Don't remember
> on others. You can check the respective installation
> guide.
>  Which platforms are you working on?
>
> -Arvind.
>
>
>
>
>                       "Carroll, Y.
>                       (Yvette)"                To:
> [EMAIL PROTECTED]
>                       <[EMAIL PROTECTED]         cc:
>    (bcc:
> arvind.chaudhary/Polaris)
>                       COM>
> Subject: Re: failed to
> connect queue manager
>                       Sent by:
>                       MQSeries List
>                       <[EMAIL PROTECTED]
>                       en.AC.AT>
>
>
>                       12/04/03 12:11
>                       PM
>                       Please respond
>                       to MQSeries List
>
>
>
>
>
>
> It means unexpected error.  I know, not very
> explanatory:
>
>
> MQRC_UNEXPECTED_ERROR
> The call was rejected because an unexpected error
> occurred.
>
>
> Corrective action: Check the application's parameter
> list to ensure, for
> example, that the correct number of parameters was
> passed, and that data
> pointers and storage keys are valid. If the problem
> cannot be resolved,
> contact your system programmer.
>
>
> On z/OS, check whether any information has been
> displayed on the console.
> If this error occurs on an  MQCONN  or  MQCONNX
> call, check that the
> subsystem named is an active WebSphere MQ subsystem.
> In particular, check
> that it is not a DB2 subsystem. If the problem
> cannot be resolved, rerun
> the application with a CSQSNAP DD card (if you have
> not already got a dump)
> and send the resulting dump to IBM.
>
>
> On OS/2 and OS/400, consult the FFST record to
> obtain more detail about the
> problem.
> On Compaq OpenVMS Alpha, Compaq NonStop Kernel, and
> UNIX systems, consult
> the FDC file to obtain more detail about the
> problem.
>
>
> -----Original Message-----
> From: Meital Geron-Issers
> [mailto:[EMAIL PROTECTED]
> Sent: 03 December 2003 03:06
> To: [EMAIL PROTECTED]
> Subject: Re: failed to connect queue manager
>
>
>
>
>
> Hello,
>
>
> Sorry, but I've just noticed the link exception
> which is MQJE001:
> Completion
> Code 2, Reason 2195.
>
>
> Do you know what does it mean?
>
>
> Thanks
> Meital
>
>
> -----Original Message-----
> From: Arvind Chaudhary
> [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 01, 2003 10:02 AM
> To: [EMAIL PROTECTED]
> Subject: Re: failed to connect queue manager
>
>
>
>
>
>
> Meital, there would be a linked exception to the JMS
> exception that you are
>
> getting which would give the real (MQSeries) reason
> why the MQClient could
> not connect to server. It will give more
> information, if you could print
> the linked exception or the complete exception
> stack.
>
=== message truncated ===


__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to