RE: tcp/ip ports. was exit pgm and lpar

For an interactive client I like to code a pop up window to prompt for the
remote info with defaults filled in from a control file or data area.  If
the data area does not exist, I prompt with hard coded defaults and create
the data area with what the user types in.  Non-interactive clients I use
the service data base.  If the lookup fails it defaults to hard coded
defaults.  This allows for the users to customize their application without
needing a programming change.  As far as your overrides, they can be parms
on the call or command interface with defaults that can be changes.  You can
code the program to allow the user to omit the parms and use defaults when
omitted.  This is NOT an OS function in my opinion but an application
function.


Christopher K. Bipes      mailto:ChrisB@Cross-Check.com
Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                  http://www.cross-check.com
6119 State Farm Drive     Phone: 707 586-0551 x 1102
Rohnert Park CA  94928    Fax: 707 586-1884

-----Original Message-----
From: Steve Richter [mailto:srichter@AutoCoder.com]
Sent: Saturday, August 25, 2001 6:48 AM
To: midrange-l@midrange.com
Subject: tcp/ip ports. was exit pgm and lpar


Tom,

Yes Tom it is hardcoded.

I like your idea of the dtaara. I thought of the same solution. Just a port
nbr in a dtaara in my case. This is my first socket appl and the final
design is still in flux.  But the dtaara approach does have its drawbacks:
Must code another module to rtv the dtaara and handle the not found
condition, another point of failure in the code, must document that the
dtaara is used by this pgm.  more code, more documentation, more turnover
instructions, more points of failure.

In my view, this is a job for the OS.

Create a new "IpPort" object type. ( or maybe IpLclPort and IpRmtPort. Or
just "Port" )  It would encapsulate the port nbr and maybe the ip addr. The
port name is the IpPort object name. ( also encapsulates that AF_INET and
SOCK_STREAM stuff )

Provide socket api's to call instead of the C module calls. The socket api
would have a IpPort object name parm instead of a PortNbr parm.

Similar to the CrtIcff and AddIcfDeve commands in the sna/appc world.
Provide commands like "OvrPort", "CrtPort", "ChgPort".

Steve Richter