Thanks Duane. That's *exactly* what I'm doing at this moment.
:)
On Tuesday, October 03, 2000 10:27 AM, Duane Percox wrote:
: David,
:
: When you call ipccreate you can specify the port#
: in the 4th parm (opt). Check the 'address option'
: which is what you want to supply to fix a particular
: port. Otherwise, as you have discovered, you will
: get a port# assigned for you.
:
: Duane Percox wk: 650.372.0200x608 fax: 650.372.3386
: [log in to unmask]
: www.qss.com
: qwebs.qss.com
:
:
: -----Original Message-----
: From: David Burney [mailto:[log in to unmask]]
: Sent: Tuesday, October 03, 2000 6:23 AM
: To: [log in to unmask]
: Subject: Re: [HP3000-L] Socket work
:
:
: Mark and John, thanks for the info. I instead used the
: 'showconn' (great little bit of code for socket work) utility
: and indeed, the COBOL server program was listening on a
: different port. Each time I start the COBOL process, regardless
: of the port I have coded for the NetIPC calls to use, it selects
: a different one.
:
: Hence, as soon as I fire up (geek speak) the COBOL server and use
: 'showconn' to determine which port it has picked, I can then modify
: my Perl CGI code to the correct port. Then when I execute my XML
: post to Apache on the e3000, from Personal Web Server, it fires
: off (more geek speak) the Perl CGI and connects on the correct port,
: parses the XML document and passes the data to the COBOL server via
: a socket connection for Image work.
:
: Apparently I've got a tad bit more work to do on the server
: side. I can't have it thinking for itself when it comes to
: assigning ports :) Not unless, of course, there's no way around
: this. Then I'll have to devise a method for passing the port
: address. Actually, this may be preferable, for more than one
: reason.
:
: Thanks !
:
: I love this list :)
:
: <We now return you to your regularly scheduled diatribe>
:
:
: On Tuesday, October 03, 2000 12:08 AM, Mark Bixby wrote:
: :
: :
: : David Burney wrote:
: : > But I'm having a heck of a time connecting between
: : > one process that uses the NetIPC intrinsics and one
: : > that doesn't. In this case the above mentioned Perl
: : > CGI and a COBOL program using NetIPC intrinsics.
: : >
: : > The error I get is :
: : >
: : > Couldn't connect to [IP:PORT] Connection refused
: :
: : Seeing the Berkeley sockets calling sequence of the Perl
: program side-by-side
: : with the NetIPC calling sequence of the COBOL program would
: be helpful.
: :
: : Sounds like the COBOL side isn't actively listening for
: connections on the
: : same
: : port that the Perl side is trying to connect to.
: :
: : You can run SOCKINFO.NET.SYS to verify that the COBOL
: program is listening to
: : the expected port.
: :
: : - Mark B.
:
:
: ---------------------------------------------------------------
: -------------
: -------
: David Burney
: [log in to unmask]
: Summit Racing Equipment http://www.summitracing.com
: -----------
: Madness continues to take it's toll.
: Please have exact change.
: -----------
: All opinions expressed herein are my own and reflect,
: in no way, those of my employer.
:
----------------------------------------------------------------------------
-------
David Burney [log in to unmask]
Summit Racing Equipment http://www.summitracing.com
-----------
Madness continues to take it's toll.
Please have exact change.
-----------
All opinions expressed herein are my own and reflect,
in no way, those of my employer.
|
