TCP/IP startup

The figure contains a sample of typical startup messages for TCP/IP.

The TCP/IP procedure (or procedures) might also be started through automation. A sample is shown in Figure 1.

Unlike VTAM, TCP/IP does not take any parameters with respect to its configuration (other than tracing options). Instead, the TCP/IP task locates its parameters from the PROFILE DD statement within the startup JCL itself. The profile is read, as outlined by the EZZ0309I and EZZ0316I message pair. Afterwards, significant configuration attributes found within the TCP/IP profile are identified with a series of messages.

The EZZ4202I message is of some interest; TCP/IP not only depends upon VTAM, but it also requires that z/OS UNIX System Services be active and functioning.

Figure 1. Some of the TCP/IP startup messages

 S TCPIP
 08.32.34 STC07499 ---- WEDNESDAY, 11 MAY 2005 ----          
 08.32.34 STC07499  IEF695I START TCPIP    WITH JOBNAME TCPIP
 08.32.34 STC07499  $HASP373 TCPIP    STARTED 
 08.32.56 STC07499  EZZ0300I OPENED PROFILE FILE DD:PROFILE        
 08.32.56 STC07499  EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE        
 08.32.58 STC07499  EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE    
 08.32.58 STC07499  EZZ0641I IP FORWARDING NOFWDMULTIPATH SUPPORT IS ENABLED    
 08.32.58 STC07499  EZZ0335I ICMP WILL IGNORE REDIRECTS            
 08.32.58 STC07499  EZZ0350I SYSPLEX ROUTING SUPPORT IS ENABLED    
 08.32.58 STC07499  EZZ0352I VARIABLE SUBNETTING SUPPORT IS ENABLED FOR OROUTED 
 08.32.58 STC07499  EZZ0624I DYNAMIC XCF DEFINITIONS ARE ENABLED   
 08.32.58 STC07499  EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED    
 08.32.58 STC07499  EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED    
 08.32.59 STC07499  EZZ4202I Z/OS UNIX - TCP/IP CONNECTION ESTABLISHED FOR TCPIP
 08.32.59 STC07499  EZZ4313I INITIALIZATION COMPLETE FOR DEVICE IUTSAMEH
 08.32.59 STC07499  EZZ4313I INITIALIZATION COMPLETE FOR DEVICE OSA2380         
 08.33.01 STC07499  EZZ4313I INITIALIZATION COMPLETE FOR DEVICE IUTIQDIO        
 08.33.03 STC07499  EZB6473I TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE.   
 08.33.03 STC07499  EZAIN11I ALL TCPIP SERVICES FOR PROC TCPIP ARE AVAILABLE.
 08.33.04 STC07499  EZZ0400I TELNET/ VTAM (SECOND PASS) BEGINNING FOR FILE:
 08.33.05 STC07499  EZZ6003I TELNET LISTENING ON PORT    23        
 08.33.05 STC07499  EZZ0403I TELNET/VTAM (SECOND PASS) COMPLETE FOR FILE:
 08.33.05 STC0749   S OMPROUTE
 08.33.05 STC0749   S FTPD

As with VTAM, TCP/IP has a message indicating that it has completed its startup and is ready to accept operator commands: EZAIN11I.

Note the messages that continue after EZAIN11I. The TN3270E server can be configured as part of the TCP/IP address space, as is the case in this example. After TCP/IP has started up, the TN3270E server configuration statements are then processed. The EZZ4313I messages are of significant interest here--a network administrator would want to make certain that all devices come active during the startup.

Finally, in this sample, TCP/IP has been configured to automatically start (AUTOLOG) the OMPROUTE and FTPD started tasks. This could also be accomplished through an external automation package.

Tip: How might external automation work? In Figure 1, an automation package could be configured to look for message EZAIN11I. As soon as the automation software finds that message, it could then issue a start of OMPROUTE and FTPD, and any other software that depends upon TCP/IP.