Hi, I have a socket program performing client side socket communication with server on my PC .
When i execute it on my virtual mvs machine, it works fine, and it can send message to my PC smoothly .
But when i execute it on the real mvs machine of our shop, error occurred with ERRNO 65.when SOCKET CONNECT command is executed.
I have examined the error code, and i found it doesnt make any sense ,as the program can be run smoothly on my virtual machine ,so ,there should be no ip Configuration problem .furthermore ,I issued PING command against my PC address from the command line of MVS, I can see it works fine .
I wonder if any special configuration required for the Real MVS system to support SOCKET program .
Please advise. THX.
Joined: 06 Jun 2008 Posts: 8154 Location: East Dubuque, Illinois, USA
1. Ping tells you two machines are able to reach each other. This is all that Ping tells you.
2. Is the PC running Windows? Is the Windows on the PC running IIS (or its equivalent)? If not, what have you done to establish server services on the PC? Server services are NOT generally provided for desktops by Microsoft, and you will not be able to connect your mainframe to the PC without some form of IIS (or its equivalent) running.
3. Telling us that it works for some virtual machine is useless -- unless you want to connect your virtual machine to the PC and not your mainframe, in which case you have no issue since the virtual machine is already connected.
4. Any particular set up to use socket connections on your mainframe would have to be established by your site support group. Contact them for assistance.
Where does your virtual machine run? Is it actually the same environment as the mainframe (most likely not)
When you run PING "from the command line" do you mean in TSO option 6? Is that the same environment from which the socket program is running (probably not)
I know that here, a given CICS (or IMS) region runs as a job on a given "box". We used to call them Logical Partitions (aka LPARs), but that's kind of obsolete. So if I run PING in TSO, then try a socket program in IMS, it's two different "boxes."
Also, you can specify different IP stacks in the start up JCL for the regions. So even the right box can have multiple IP infrastructures.
Now, even on the right box, with the right IP stack, there may be blocks put in place on purpose. You'll hear this called a firewall. Only certain ports are open, and you may have to request that.