Charles, With TCP/IP there are a few things to help when host is not up or unexpectedly removed (eg the UEEXIT parm on the INITAPI), however I have found that it suffers from a couple of issues, namely the length of time between host IP shutdown and the UEEXIT being driven and, of course, the wonderful "which ERRNO shall I use today to indicate that host is unavailable for this service?"
Rob Scott Lead Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: [email protected] Web: www.rocketsoftware.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Charles Mills Sent: 28 September 2010 14:59 To: [email protected] Subject: Shutdown and dependencies 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 ---------------------------------------------------------------------- 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
