We have the same sort of issue with our product documentation. We have found though that you really shouldn't tell they site where to put it. Instead, we point out where they CAN put it to have it start up at the correct time.
It's more work to tell them multiple places that it can go, but it leaves it up to the site to decide what works best for them. We even have a small derivative of one of our products (SyzCMD/z) that can be run as a step before any job that checks for dependencies and waits for things to be the way the site (or we) need them to be before things go forward, like (but not limited to) TCP is up (or not), VTAM is up (or not), some other task is running (or not running), etc. In the end though I think it's best to let the site decide. Brian ---------------------------------------------------------------------- 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
