Rob I really believe you are set on simply wasting time and effort here.
There was a judiciously placed "generally" which shades to "almost always" and I would hazard the suggestion "always" for any general purpose application as I, well, just assume something called "HTTP Server for z/OS" would be. In order for a product to limit the destination address it would accept, it would need to issue a bind() call which, rather than specifying 0.0.0.0, a.k.a. INADDR_ANY, would need to be an IP address which had been set up for a specific IP node implementation - massively unlikely, wouldn't you say? I really can't see a product mandating a particular IP address! Now it is possible for an installation to configure a particular IP address either through product customisation - although this in my experience is unusual - or by means of the BIND parameter of the PORT statement list entry for the relevant port number. These days there are "tricks" which can be introduced with the SRCIP statement with the SERVER parameter, just about the most counterintuitive naming of a statement in relation to its purpose that could have been devised! Now all of these options involves performing some sort of customisation somewhere and it is to be hoped that any such customisation would be done with the full knowledge of whomever was performing the customisation. I already indicated that the "local specialists supporting the IP component of Communications Server" should be involved. I would hope that anyone actually responsible for "HTTP Server for z/OS" would have known what he or she was doing in the generally unlikely case that the specification of an IP address through product customisation was possible. Note that the "sockaddr" or "name" structure used by the bind() call has room for only one IP address. Do you have any other suggestions? Chris Mason On Thu, 28 Apr 2011 10:08:23 -0400, Rob Schramm <[email protected]> wrote: >Chris, > >Unless you have specifically done the research for the HTTP server, there is >an assumption you are making that a Communication Server configuration is >the only way to perform any of the setup. While CS can certainly be setup >to do it and would be involved regardless, there are more than a few >products that can perform binds and have specific configuration options to >govern them. > >Rob Schramm > >On Thu, Apr 28, 2011 at 9:50 AM, Chris Mason <[email protected]>wrote: > >> Maria >> >> This is a question for your local specialists supporting the IP component >> of >> Communications Server (CS). >> >> An application running on an IP node and relying on IP-based communications >> will generally place no limitations on the IP addresses assigned to that IP >> node. >> >> Thus any of the IP addresses which appear in what is called the "home" >> list, >> that is, the IP addresses corresponding to real or virtual interfaces to >> the IP >> node, can be used as the destination IP address for the application. >> >> Perhaps you should post again and describe more clearly what your >> requirements are. >> >> Note that, since this is a question probably relating more to the IP >> component >> of CS, you should be posting for the widest audience on the IBMTCP-L list: >> >> For IBMTCP-L subscribe / signoff / archive access instructions, send email >> to >> [email protected] with the message: INFO IBMTCP-L >> >> Chris Mason >> >> On Thu, 28 Apr 2011 08:12:36 -0500, Maria Mora >> <[email protected]> wrote: >> >> >Can you use Virtual Host or multiple IP addresses in HTTP Server for z/OS >> ver >> >5.3? >> > >> >Thanks, >> >Maria >-- >Rob Schramm ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
