[z/OS]

TCP/IP automation and recovery scenarios

This table provides automation and recovery scenarios for TCP/IP configurations.

Table 1. Automation and recovery scenarios for TCP/IP configurations. To prepare TCP/IP on z/OS®, read about the information in the Preparing TCP/IP on z/OS topic.
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 might have their transactions rolled back when the attempt to send a response to the method fails. Other transactions might 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?

Restart TPC/IP. After TCP/IP is restarted, you also must restart WebSphere Application Server.

If you are using another product to supplement WebSphere Application Server for z/OS, you might need to restart the application server for the other programs to re-initialize the TCP/IP settings.

What happens to other subsystems if TCP/IP goes down? If TCP/IP goes down, sessions break and transactions react as described.
Note: If TCP/IP goes down, LDAP functionality might be affected. You might need to recycle LDAP and restart WebSphere Application Server for z/OS if this occurs.

Icon that indicates the type of topic Reference topic



Timestamp icon Last updated: March 5, 2017 17:55
File name: rtrb_tcpipars.html