Question & Answer
Question
We need to know what, if any, address spaces must be active before we can start the TCP/IP stack.
Answer
The IP Configuration Guide addresses this issue in the section Required steps before starting TCP/IP:
"TCP/IP uses services from other address spaces in its processing. While TCP/IP waits for availability of those services, it is recommended that you verify that the OMVS, resolver, and VTAM address spaces have completed initialization before starting TCP/IP. If using automation to start TCP/IP, have it look for the BPXI004I, EZZ9291I, and IST020I messages, respectively, before issuing the START command."
The complete texts of these messages are shown below:
BPXI004I OMVS INITIALIZATION COMPLETE
EZZ9291I RESOLVER INITIALIZATION COMPLETE
IST020I VTAM INITIALIZATION COMPLETE FOR level
In addition, the IP Configuration Guide states the following: "If you configure VMCF and TNF as restartable subsystems and you want the VMCF node name to be used as a default host name during TCP/IP initialization (when no other host name can be located), VMCF must be started before TCP/IP."
Finally, "The following TCP/IP applications and commands will abend if VMCF is not active:
LPD servers
TSO HOMETEST, LPQ, LPR, LPRM, LPRSET, TELNET, and TESTSITE commands"
Product Synonym
ZOSCS COMMSERVER
Was this topic helpful?
Document Information
Modified date:
12 October 2018
UID
dwa1209936