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 » MQ V7 and 5.3

Post new topic  Reply to topic
 MQ V7 and 5.3 « View previous topic :: View next topic » 
Author Message
itsme_001
PostPosted: Mon Aug 09, 2010 12:12 am    Post subject: MQ V7 and 5.3 Reply with quote

Disciple

Joined: 02 Feb 2009
Posts: 157

HI,

I'm trying to connect a client machine on Linux with MQ Client V7 with an AIX 5.3 machine which has MQ Server V5.3.

I'm able to put messages from the client machine onto the MQ server machine. but not able to see the msgs.

Can we connect V7 client to a V5.3 server.
Back to top
View user's profile Send private message
exerk
PostPosted: Mon Aug 09, 2010 12:18 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

What do you mean by "...not able to see the msgs..."? Do you see depth? Do you see uncommitted messages?

And you've answered your own question - if you were able to put messages, then you connected
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
itsme_001
PostPosted: Mon Aug 09, 2010 9:43 pm    Post subject: Reply with quote

Disciple

Joined: 02 Feb 2009
Posts: 157

When i try to put a msg in the client server(Linux with MQ client V7):

[mqm@ mqm]$ set MQSERVER='PROFILE.CLNTCONN.CHL/TCP/x.x.x.x.(1452)'
[mqm@ mqm]$ cd /opt/mqm/samp/bin
[mqm@ bin]$ ./amqsputc MIBK.INCOMING.QUEUE IBSPROD.QMGR
Sample AMQSPUT0 start
target queue is MIBK.INCOMING.QUEUE
* please do not use *

Sample AMQSPUT0 end
[mqm@ bin]$

Now when I try to retieve the same msg from the server side(AIX with MQ Server V5.3):

$ cd /usr/mqm/samp/bin
$ ./amqsgetc MIBK.INCOMING.QUEUE IBSPROD.QMGR
Sample AMQSGET0 start
MQCONN ended with reason code 2058


Don't know why?????????????????????
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Mon Aug 09, 2010 10:17 pm    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

you are local to your queuemanaager with the local queue holding the messages, but you used amqsgetc which is the client version . so you must also set the MQSERVER variable, otherwise amqsgetc is not able to connect to your qmgr, even if you are local.

or use amqsget which is the bindings mode version if you are local ..... no need to use the client version ........
_________________
Regards, Butcher
Back to top
View user's profile Send private message
exerk
PostPosted: Mon Aug 09, 2010 11:06 pm    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

OK, I'm confused...

itsme_001 wrote:
[mqm@ bin]$ ./amqsputc MIBK.INCOMING.QUEUE IBSPROD.QMGR


...is the name of the queue you are putting to, yet the output reports...

itsme_001 wrote:
target queue is MIBK.INCOMING.QUEUE


So what gives? And if the answer is a QALIAS, please put that kind of information in because it's too early in the morning here for puzzles!
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Mon Aug 09, 2010 11:31 pm    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

did you miss the blank as this is queue and qmgr name in your first quote on amqsputc?
_________________
Regards, Butcher
Back to top
View user's profile Send private message
itsme_001
PostPosted: Tue Aug 10, 2010 2:37 am    Post subject: Reply with quote

Disciple

Joined: 02 Feb 2009
Posts: 157

Its too weird:

[mqm@01 bin]$ ./amqsputc MIBK.INCOMING.QUEUE IBSPROD.QMGR Sample AMQSPUT0 start
test message 1000







[3]+ Stopped ./amqsputc MIBK.INCOMING.QUEUE IBSPROD.QMGR
[mqm@01 bin]$



On the server side:
$ pwd
/usr/mqm/samp/bin
$ amqsget MIBK.INCOMING.QUEUE IBSPROD.QMGR
Sample AMQSGET0 start






[3] + Stopped (SIGTSTP) amqsget MIBK.INCOMING.QUEUE IBSPROD.QMGR
$
Back to top
View user's profile Send private message
exerk
PostPosted: Tue Aug 10, 2010 3:06 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Mr Butcher wrote:
did you miss the blank as this is queue and qmgr name in your first quote on amqsputc?


I did say it was too early in the morning

Looking back at the original post I now see it. I don't bother with a specific queue manager name when the MQSERVER variable is set (not that I tend to use it anyway), hence reading it as a single input - doh!
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
itsme_001
PostPosted: Tue Aug 10, 2010 3:16 am    Post subject: Reply with quote

Disciple

Joined: 02 Feb 2009
Posts: 157

Here's the installed MQ Client components:

[root@ /]# rpm -qa | grep MQ
MQSeriesSamples-7.0.0-0
MQSeriesClient-7.0.0-0
MQSeriesJava-7.0.0-0
MQSeriesSDK-7.0.0-0
MQSeriesRuntime-7.0.0-0


anything more needed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

itsme_001 wrote:
Its too weird:

[mqm@01 bin]$ ./amqsputc MIBK.INCOMING.QUEUE IBSPROD.QMGR Sample AMQSPUT0 start
test message 1000







[3]+ Stopped ./amqsputc MIBK.INCOMING.QUEUE IBSPROD.QMGR
[mqm@01 bin]$



On the server side:
$ pwd
/usr/mqm/samp/bin
$ amqsget MIBK.INCOMING.QUEUE IBSPROD.QMGR
Sample AMQSGET0 start






[3] + Stopped (SIGTSTP) amqsget MIBK.INCOMING.QUEUE IBSPROD.QMGR
$
Back to top
View user's profile Send private message
exerk
PostPosted: Tue Aug 10, 2010 3:18 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

What is weird? You want help yet continually fail to post anything that may help us to help you

SIGSTP suggests to me that you may have suspended/terminated the amqsget...

EDIT: Apply maintenance, 7.0.0.0 is not a good level to be at when the current release is 7.0.1.2
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
itsme_001
PostPosted: Tue Aug 10, 2010 3:29 am    Post subject: Reply with quote

Disciple

Joined: 02 Feb 2009
Posts: 157

hi,

amqsget is suspended since after typing some message text followed by blank line I can't see the message: Sample amqsput0 end.
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Tue Aug 10, 2010 3:30 am    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

imho, you are either on the wrong queuemanager, or someone is consuming your message before you can do so with amqsget

display the queue and queuestatus and check ipprocs. you may also do that during amqsputc to verify there is a opprocs while you are putting
_________________
Regards, Butcher
Back to top
View user's profile Send private message
itsme_001
PostPosted: Tue Aug 10, 2010 4:30 am    Post subject: Reply with quote

Disciple

Joined: 02 Feb 2009
Posts: 157

Tried chkinig the q status:

dis qstatus(MIBK.INCOMING.QUEUE)
3 : dis qstatus(MIBK.INCOMING.QUEUE)
AMQ8450: Display queue status details.
QUEUE(MIBK.INCOMING.QUEUE) IPPROCS(0)
OPPROCS(0) CURDEPTH(0)
UNCOM(NO)


No use. all the input process are still running in the client server since I've terminated them. Killed all the processs; still not able to put msgs into this QM
Back to top
View user's profile Send private message
exerk
PostPosted: Tue Aug 10, 2010 4:45 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

1. On the client: run the amqsputc sample but do not put any messages in the queue.

2. On the server: check that OPPROCS gt 0, IPPROCS eq 0, and check that amqsputc is showing as the connected application (APPLTAG).

3. On the client: put one message and use Enter/CR to end the amqsputc sample.

4. On the server: check that CURDEPTH gt 0.

5. On the server: run the amqsget sample and wait for it to end gracefully.

6. Post the result of each of the above steps.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.


Last edited by exerk on Tue Aug 10, 2010 4:49 am; edited 1 time in total
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Aug 10, 2010 4:48 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

You still haven't told us if the amqsputc has actually put a message - i.e. that you see an increase in qdepth after amqsputc has finished.

You still haven't told us if the amqsputc is actually connected to the queue manager you are trying to get from - for example by looking at qstatus while it is running.
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 » MQ V7 and 5.3
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.