In another thread Barbara Nitz wrote "If TCPIP services are needed for successful shutdown [of a vendor product], then the product MUST be shutdown before TCPIP services go away." I admit to having given little thought (so far -- it's fairly early in the design process) to this issue.
Is there a way to do that other than documentation and/or suggesting the use of an automation product? (Not that there's anything wrong with documentation and automation.) Programming-wise, we should make sure that STOP never gets us into a stupid "waiting for TCP/IP to come up" situation. Other than that sort of thing, is there anything else we should be doing relative to shutdown and dependencies? Charles Mills ---------------------------------------------------------------------- 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
