RE: Sockets problem (what is)

>We do the translation to ASCII before sending.

Do they expect ASCII?

>They see the connection on their end OK, it's
>just the connection stays on port 5550 so
>they don't get the data when we send it.
>They still see us connected to 5550
>even after they've handed us off to another port.

Right.  How do "they" know they've handed you off to another port?

>Here's what the vendor told us to do: ( I
>don't understand the part about setting
>the socket to some unique value e.g.,
>34567)
>
>Looking at what should be done at CPU's side, the logic should be:
>
>// Create an unconnected socket for TCP/IP
>m_Sockfd = ::socket(AF_INET, SOCK_STREAM, 0);
>
>// Connect to serv_addr (xxx.xxx.xxx.xxx, 5550) and
>// set m_Sockfd to some unique value (e.g., 34567)
>connect(m_Sockfd, (struct sockaddr*)&serv_addr, sizeof(serv_addr));
>
>// Send messages to 34567
>send(m_Sockfd, outBuffer, ::strlen(outBuffer), 0)

The reference to 34567 is difficult to understand.
m_Sockfd is returned by socket() as the handle to your local client socket
connexion.
connect() links you (m_Sockfd) to the server (servaddr)
send() transmits the contents of outbuffer to the far side.

I think they mean that you can't hard-code a socket ID in place of m_Sockfd.

Use Telnet and see how the server reacts.  Send it whatever the
documentation says it expects.  Once you have a firm grasp on how the
dialogue should go, you can code that up in the RPG program.  There's
nothing obviously wrong with the RPG snippets you've posted; it looks like a
bulk transfer of some kind.  Do try the Telnet route with one hand-typed
record (cut & paste works).
  --buck