Author |
Message
|
bobbee |
Posted: Thu Sep 21, 2006 11:43 am Post subject: Client Connect z/OS |
|
|
 Knight
Joined: 20 Sep 2001 Posts: 545 Location: Tampa
|
I am running an Emulated z/OS system on a LINUX box.
First Client Attachment is installed.
So, I installed and configured the Boker and ConfigMgr. QMGR was there. I set up the TOOLKIT on the LINUX system and tried to set up a DOMAIN. N/G. Cannot connect, TIMEOUT.
Set up the MQClient on the same LINUX machine, N/G. TIMEOUT
Set up MQServer on the same LINUX machine. Set up a QMGR. I can client to the Linux QMGR. Cannot Client to the z/OS box. TIMEOUT
Set up a Server to Server SDR.REC channel pair. Write messages to XMIT Q and start channel. N/G TIMEOUT connecting to z/OS QMGR.
Pings back and forth from both sides work
I have FTP'd from the Linux side to z/OS and GET/PUT files.
CSQ6CHIN is running.
LIDTENER is running on Port 1416
Telenet from LINUX to z/OS 192.168.252.171(1416) hangs as expected
Any connection I try I can see it in NETSTAT on the z/OS box.
So.....any suggestions???
bobbee |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Sep 21, 2006 1:47 pm Post subject: |
|
|
Guest
|
Look for syslog error msgs in both CHIN and MSTR address spaces on zOS.
If you are not a mainframe person, have one of 'em do it. There needs to be SVRCONN channel(s) defined on zOS MQ, listener, ip stack, lots of mainframe stuff.
Post relevant messages. |
|
Back to top |
|
 |
bobbee |
Posted: Thu Sep 21, 2006 2:28 pm Post subject: |
|
|
 Knight
Joined: 20 Sep 2001 Posts: 545 Location: Tampa
|
Yes I am a mainframe person. I just got done installing the Broker from the REL images. Worked out all the issues. Which were alot and have the Broker and ConfigMgr up and running.
Now I am down to the connectivity between the Linux Toolkit and the z/os QMGR. I would have at least thought I would get a 2035 because I have not run the BIPCRACL job yet.
I have tried simple Client install on the Linux side and a connection. That did not work. The I deinstalled Client and installed Server. Tried Client and then set up the DQM between the two thinking the Client Attachment feature was not working. That was a bust.
The connection just times out. I see it though in "NETSTAT" on z/OS under option 6. I can also PING and FTP between the two from either side.
I need some z/OS networking suggestions.
bobbee |
|
Back to top |
|
 |
wschutz |
Posted: Thu Sep 21, 2006 3:45 pm Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
BOBBEEEEE... do you see anything in the CHIN log when you do the telnet? ----wayneeeee _________________ -wayne |
|
Back to top |
|
 |
bobbee |
Posted: Fri Sep 22, 2006 10:23 am Post subject: |
|
|
 Knight
Joined: 20 Sep 2001 Posts: 545 Location: Tampa
|
nope, noting in the CHIN, or anywhere for that matter. I can see the connecting in netstat but no information elsewhere |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Sep 22, 2006 10:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
In my limited experience working MQ on z, it is always MF security that takes the longest time to resolve and is the hardest to troubleshoot.
So are you seeing any RACF violations? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Sep 22, 2006 12:39 pm Post subject: |
|
|
Guest
|
MVS (z/OS) syslogs will contain channel start/stop/error, along with listener activity and security (RACF) stuff. RACF messages are crystal-clear about what rule was violated, and by whom.
How did you start the client? With MQSERVER=? Post the MQSERVER environment variable you used.
When you say "I have tried simple Client install on the Linux side and a connection. That did not work." What symptoms did you see on zOS?
Did the listener start? Post the CHIN syslog about the listener starting/failing...
Post the SVRCONN channel definition you used on the mainframe qmgr. Is channel-auto def on/off?
MQ z/OS is very chatty. The syslog from MSTR address space and CHIN are loaded with useful info for doing problem determination. Look also at the TCPIP address space syslog. |
|
Back to top |
|
 |
pinhead |
Posted: Thu Oct 19, 2006 7:05 am Post subject: |
|
|
 Newbie
Joined: 30 Dec 2004 Posts: 8 Location: Hartford, CT
|
Are you sure Client is installed on the z/OS side? Believe it or not, it is a seperately installed (and charged) feature unique to the mainframe. You'd have to check with your z/OS system programmers to see if they also installed the Client attach feature, or you can't use client on the mainframe. I don't know why IBM did this (it's free on all distributed platforms), but it's always been this way. |
|
Back to top |
|
 |
kevinf2349 |
Posted: Thu Oct 19, 2006 9:29 am Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
Quote: |
I don't know why IBM did this (it's free on all distributed platforms) |
V6 is also a big upgrade charge on z/OS too. I suspect it is because z/OS shops are cash cows for IBM Always have been and so they just stick-it-to-the-big-guys to fund the smaller shops. At least that is what it seems like to me.  |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Oct 19, 2006 11:14 am Post subject: |
|
|
Guest
|
There is no MQ client for the mainframe. But, you can use the client from a midrange platform to connect to the mainframe.
To help resolve your problem, please read prior posts in this thread, and provide some documentation on the symptoms (object definitions, error messages, etc.). |
|
Back to top |
|
 |
pinhead |
Posted: Thu Oct 19, 2006 11:19 am Post subject: More specific z/OS client info |
|
|
 Newbie
Joined: 30 Dec 2004 Posts: 8 Location: Hartford, CT
|
You cannot use the mainframe as a client to connect to a distributed queue manager, but you can connect to a mainframe queue manager as a client. To do that, you have to have the z/OS client attach feature, which is not part of the base MQ install, you have to order (and pay for) it separately. |
|
Back to top |
|
 |
pinhead |
Posted: Thu Oct 19, 2006 11:26 am Post subject: Further SMP/E z/OS MQ Client info |
|
|
 Newbie
Joined: 30 Dec 2004 Posts: 8 Location: Hartford, CT
|
Have whoever is responsible for the z/OS SMP/E MQ install check to see if JMS6007 (the client attach feature) is installed as part of HMS6000(MQ Base product). If not, you won't be able to client connect your toolkit to a z/OS qmgr. Info for this is in the z/OS MQ 6.0 program directory ((GI10-2584-00) |
|
Back to top |
|
 |
kevinf2349 |
Posted: Thu Oct 19, 2006 11:31 am Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
Quote: |
There is no MQ client for the mainframe. |
Yes there is....but it is seperately orderable feature....which Bobbee has already says he has.
Quote: |
But, you can use the client from a midrange platform to connect to the mainframe. |
No you can't....not without CAF.
I think the issue is that he is trying to go from z/OS as a client. I don't know enough about CAF to know if this is possible. From what I read here it seems that CAF allows client connections to a z/OS qmgr only.
 |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Oct 19, 2006 12:16 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
kevinf2349 wrote: |
I think the issue is that he is trying to go from z/OS as a client. I don't know enough about CAF to know if this is possible. From what I read here it seems that CAF allows client connections to a z/OS qmgr only.
 |
No he is trying to reach z/OS from Linux. (The toolkit only runs on windows or Linux platforms and I don't think zLinux is one of them...)
This would have to do with security and MQ setup...
Make sure as well that the user running the toolkit has the authority for the configmgr (see mqsicreateaclentry ...). Make the first entry with the service user for the configmgr. The user creating the acl entry must be authorized to do so.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
kevinf2349 |
Posted: Thu Oct 19, 2006 12:32 pm Post subject: |
|
|
 Grand Master
Joined: 28 Feb 2003 Posts: 1311 Location: USA
|
I stand corrected. I see what he is trying now.
I kind of got carried away while I was on my soapbox about software charges  |
|
Back to top |
|
 |
|