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 » Mainframe, CICS, TXSeries » MQ Server to Server connection from Windows to Mainframe

Post new topic  Reply to topic
 MQ Server to Server connection from Windows to Mainframe « View previous topic :: View next topic » 
Author Message
suriv
PostPosted: Thu Oct 25, 2007 10:36 pm    Post subject: MQ Server to Server connection from Windows to Mainframe Reply with quote

Newbie

Joined: 27 Sep 2007
Posts: 8

Hi,

We are trying to connect to MQ server on windows to MQ server on mainframe. We have done all the set up and the port on mainframe is opened as well. CAF is installed on mainframe.

For some reason the connection is not successful. Can you please throw some light as to what else could be the problem or what other setup do we have to make?

THnaks.
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Oct 25, 2007 10:53 pm    Post subject: Re: MQ Server to Server connection from Windows to Mainframe Reply with quote

Grand High Poobah

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

suriv wrote:
CAF is installed on mainframe.


If you're trying to connect 2 queue managers you don't need CAF. Is the Windows server running a queue manager, or is there an application on the Windows server trying to establish a client connection to the mainframe queue manager?

suriv wrote:
For some reason the connection is not successful.


What reason? Are you getting an error code? Are there log messages? There are a wide variety of reasons why this might not be working, from network issues through to security. Without more information it's impossible to tell.

But, as you say you've done "all the set up" may I perhaps foolishly assume that in addition to the port being open the network names resolve properly, all the required channels are in place for the connection you're trying to establish, security (especially on the mainframe side) is set up correctly and will accept the Windows id, the application is using the right connection and you've tested all of this going Windows -> Windows and it works?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
suriv
PostPosted: Fri Oct 26, 2007 1:07 am    Post subject: Reply with quote

Newbie

Joined: 27 Sep 2007
Posts: 8

We are not running any application on windows. just trying to connect from the queue manager on windows to the mainframe queue manager.

The required channels are in place. But am not quite sure about the security ie inorder to accept the windows id, not sure what set up needs to be done. Can you please help.

We are getting an RC 2195(amq4048).

Thanks.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Oct 26, 2007 1:25 am    Post subject: Reply with quote

Grand High Poobah

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

suriv wrote:
We are getting an RC 2195(amq4048).


A 2195 (as I'm sure your research will have revealed) is an unexpected error. There should be a matching FDC file on the queue manager throwing the error - you don't say which queue manager is throwing the error. You also don't say what versions of MQ you're using, what version of Windows you're using, under what circumstances the 2195 is thrown or much else that's useful.

Within the FDC is a Probe Id which is a detailed explaination of the error. Google that, search this forum for it or contact IBM & raise a PMR.

On the plus side, it's unlikely to be a security issue - that's a 2035. You'll probably hit that when this is fixed. You might want to review the Security & z/OS System Setup manuals, that will tell you all you need to know.

And make sure the mainframe's RACF admin is in the loop.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
suriv
PostPosted: Fri Oct 26, 2007 2:40 am    Post subject: Reply with quote

Newbie

Joined: 27 Sep 2007
Posts: 8

I am sorry for not providing complete information. The error is on the windows queue manager. MQ version running on windows is V6.0 and that running on mainframe is V5.3. Will this be an issue?

Also, please find below the FDC

WebSphere MQ First Failure Symptom Report |

Host Name :- A1MD02503 (Windows XP Build 2600: Service Pack 2) |
PIDS :- 5724H7200 |
| LVLS :- 6.0.0.0 |

| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- CO052000 |
| Application Name :- MQM |
| Component :- cciTcpReceive |
| SCCS Info :- lib/comms/amqccita.c, 1.255 |
| Line Number :- 3380 |
| Build Date :- May 24 2005 |
| CMVC level :- p000-L050524 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqrmppa.exe |
| Process :- 00002068 |
| Thread :- 00000018 |
| Major Errorcode :- rrcE_BAD_DATA_RECEIVED |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9207 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9207: The data received from host '192.168.5.18' is not valid
| FDCSequenceNumber :- 0 |
| Comment1 :- 192.168.5.18 |
| |
| Comment2 :- TCP/IP |
| Comment3 :-


Last edited by suriv on Fri Oct 26, 2007 3:02 am; edited 1 time in total
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Oct 26, 2007 3:02 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Wrong FDC, or you are not sending MQ data through the MQ port.
This FDC gets typically created if you try a telnet to the MQ port which is one way of verifying the access (firewall and all) to the MQ manager...

The FDC might however correspond to the MQ reason code you mentioned and both might relate to that telnet attempt.

What do the MQ logs show? (<MQinstall>/data/qmgrs/<qmgr>/errors/*01.LOG)

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
suriv
PostPosted: Fri Oct 26, 2007 4:20 am    Post subject: Reply with quote

Newbie

Joined: 27 Sep 2007
Posts: 8

I have checked the log. It is complaining about the channel definition. The channel definition looks perfectly OK. But apart from this it is not giving any more information.

I have googled for the PROBE ID CO052000 and the link http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg1IC48803

is talking about some fix. I am downloading this fix from the above link and will try if this works.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri Oct 26, 2007 6:55 am    Post subject: Reply with quote

Guest




Quote:
It is complaining about the channel definition. The channel definition looks perfectly OK.


Did you successfully ping (the MQ ping) your sender channel?
Back to top
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Mainframe, CICS, TXSeries » MQ Server to Server connection from Windows to Mainframe
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.