Task | TCP/IP automation and recovery scenarios |
---|---|
Startup | TCP/IP must be up before starting WebSphere Application Server for z/OS. |
Shutdown | Shutdown WebSphere Application Server for z/OS before shutting down TCP/IP. |
Handling inflight or indoubt transactions if there is a failure | Methods in flight will have their transactions rolled back when the attempt to send a response to the method fails. Other transactions will wait for a timeout. |
How to determine if TCP/IP is running | Use the display command looking for the TCP/IP procedure. |
What happens to WebSphere Application Server for z/OS if TCP/IP goes down? | If TCP/IP goes down, then WebSphere Application Server for z/OS on the system must be restarted. You will get an SVC dump because the socket layer was destroyed. |
What happens to other subsystems if TCP/IP goes down? | If TCP/IP goes down,
sessions break and transactions react as described above. Note: WebSphere Application Server for z/OS will not be able to recognize that TCP/IP is back up. Therefore, WebSphere Application Server for z/OS must be restarted. Note: If TCP/IP goes down, you should recycle LDAP before restarting WebSphere Application Server for z/OS. |