TCP/IP Level 410 - Publication Updates and Discrepancies

Note: Support for TCP/IP Level 410 ended on 30 June, 2003.

The information presented here describes TCP/IP Level 410 characteristics and items of significance which are not documented or accounted for in existing TCP/IP Level 3A0 publications.

Note:

Level-specific TCP/IP publications have not been produced for TCP/IP Level 410. Therefore, existing TCP/IP Level 3A0 publications must be used and referenced when using TCP/IP Level 410.

In the context of using any TCP/IP Level 3A0 publications in conjunction with TCP/IP Level 410, references to Level 3A0 should be construed as Level 410.

Although the items that follow have been addressed within the TCP/IP for z/VM, Level 410 Program Directory, they are reiterated here for heightened awareness:

• No action is required to activate (enable) the TCP/IP component of z/VM Version 4 Release 1.0.

• No action is required to activate (enable) the TCP/IP 410 NFS server.

• TCP/IP source files are now supplied and installed as part of the z/VM Version 4 Release 1.0 System DDR.

• The TCPBLMPR and TCPBLNFC EXEC files (VMSES/E build lists) have been replaced, respectively, by the TCPBLP91 and TCPBLP92 EXEC files.

General Topics

• References to the TCP/IP Feature for Z/VM, Level 3A0 Program Directory should instead be construed as references to the TCP/IP for z/VM, Level 410 Program Directory.

Chapter 3. General TCP/IP Server Configuration

• The first entry in Table 2. Required Virtual Machines on page 17 should reflect 4TCPIP10 as the TCP/IP installation and service user ID, instead of 3TCPIPA0.

• Processing for the DTCPARMS file :Attach. tag has been enhanced to allow virtual addresses to be identified as either REQUIRED or OPTIONAL. The :Attach. tag and values can now be specified as follows:

  :Attach.raddr (option),raddr AS vaddr
  (option), raddr1-raddr2 (option)

  where (option) can be specified as either:

  • REQuired: indicates that raddr is a required device. If a problem is encountered during the attach of this device, server initialization is terminated. This is the default.

  • OPTional: indicates that raddr is an optional device. If a problem is encountered during the attach of this device, an error message is displayed and server initialization continues.
  If option is specified, it must be enclosed within parentheses.

  For example: :attach.1500 AS 500, 400-403 (req), 800-803

Chapter 4. Configuring the TCP/IP Server

• The note that cites TCP/IP as an optional feature that must be enabled prior to use is not applicable to TCP/IP Level 410. Please disregard this step when the Level 410 TCP/IP server is customized.

• A new parameter is added on page 53 for the ASSORTEDPARMS statement, as follows:
  • SECURELOCAL

    Causes TCP/IP to check if local connections are destined for a secure port or user ID. If so, the connection is routed to the SSL server. If this operand is not specified, local connections are bypassed for SSL processing.

Chapter 17. Configuring the NFS Server

• The step titled Step 1: Enable the NFS Server Feature on page 407 is not applicable to TCP/IP Level 410. Please disregard this step when the TCP/IP Level 410 NFS server is customized.

• In the section titled Source Code Modifications on page 426, the first list item should appear as follows:

  1. Modify the NFSFHCIP ASSEMBLE file to employ suitable calling conventions for the encryption program that is to be used.

  (The text regarding placement of the NFSFHCIP ASSEMBLE file is no longer relevant; this file now resides on the 4TCPIP10 2B3 "Source code" minidisk as do other supplied TCP/IP for VM source files.)

Chapter 23. Configuring the SSL Server

• The fourth paragraph at the beginning of this chapter (page 525) which discusses use of the Linux operating system, has been changed. This paragraph should read as follows:

  The SSL server runs on the Linux operating system, which runs as a guest in the SSL server virtual machine. Thus, a suitably configured Linux kernel and file system must be installed on your z/VM system. Detailed information about Linux requirements and preparation for use by the SSL server are available at the TCP/IP Feature home page on the World Wide Web.

• A new SSLADMIN is supported for TCP/IP Level 410. Documentation for this command should be noted on page 528:

  SSLADMIN LOG Command

  Use the SSLADMIN LOG command to obtain the message log from the SSL server. The message log contains all messages written by the SSL server, as well as any output generated by the SSLADMIN TRACE command.

   >>---SSLadmin---LOG---------------------------------------------------><
  

  The SSLADMIN LOG command has no operands.

  Usage Notes

  1. Output is written to a file, SSLADMIN OUTPUT, on the first read/write disk or directory in the CMS search order.
  2. If the file SSLADMIN OUTPUT already exists, it is overwritten.

Chapter 31. Using Source Code Libraries

• The first paragraph of this chapter, on page 605, should reflect the TCP/IP Level 410 installation and service user ID; it should appear as follows:

  TCP/IP source code is located (by default) on the 4TCPIP10 2B3 minidisk, whereas TCP/IP object code is located on the 4TCPIP10 2B2 minidisk.

Chapter 9. Using the Remote Execution Protocol

• The -w option should be included in the REXEC syntax diagram, after the -s operand:

           .-- -w 80 -----.
   >-------+--------------+----------------------------------------------><
           '-- -w width --'
  

  In addition, a description for the -w operand should be present following that for the -s description under the Operands heading:

  -w width

  Specifies the maximum width to use for lines written by REXEC. The minimum acceptable width is 1, while the maximum is 32767; the default is 80. Note that circumstances on the remote host continue to affect or restrict output when the w operand is used.

The new messages that follow are added for TCP/IP Level 410.

Chapter 3. FTP Messages

• Message:
  

  451 Error closing BFS data set. System error.

  Severity: Error.

  Explanation: BFS System Error.

  System Action: None.

  User or Operator Response: Retry the command. If the problem persists, contact your system support personnel.

Chapter 15. SMTP (Server) Messages

• Message:
  

  Terminating: Unable to properly establish UDP connection for Nameserver queries

  Severity: Error.

  Explanation: The server was unable to complete initialization because it could not establish a working UDP connection for use during Nameserver queries.

  System Action: SMTP terminates.

  System Programmer Response: Restart the SMTP server.

Chapter 18. SSL Messages

• Message:
  

  DTCSSL092E Log file flush failed

  Explanation: While processing the SSLADMIN LOG command, an attempt to write a buffer to a file within the SSL server machine failed.

  System Action: The SSLADMIN LOG command fails.

  System Programmer Response: Contact IBM Service.

• Message:
  

  DTCSSL093E Log file copy (cp) failed rc: rc

  Explanation: While processing the SSLADMIN LOG command, an attempt to copy the message log within the SSL server machine failed.

  System Action: The SSLADMIN LOG command fails.

  System Programmer Response: Contact IBM Service.

• Message:
  

  DTCSSL094E Log file read failed rc: rc errno: err_number

  Explanation: While processing the SSLADMIN LOG command, an attempt to read the message log within the SSL server machine failed.

  System Action: The SSLADMIN LOG command fails.

  System Programmer Response: Contact IBM Service.

Chapter 19. TCP/IP Server Messages

• Message:
  

  DTCOCP092I Conn nnn: LU Name LuName LDEV LdevNumber has been dropped because TN3270E data string is too long

  Severity: Informational.

  Explanation: A TN3270E message was found to be fragmented and was saved in a temporary buffer until remaining data could be obtained. However, the length of the data obtained from an ensuing packet, combined with that from the still unprocessed TN3270E message, exceeded the size of the buffer used for processing such data. The buffer size in question is defined by the DATABUFFERPOOLSIZE statement within the TCP/IP server configuration file. Within this message:

  nnn	represents a connection ID
  luname	is the name of the logical device that represents the client
  ldevnumber	is the hexadecimal number of the logical device that represents the client.

  System Action: The offending client is disconnected.

  User or Operator Response: Check the client for a bad emulator level.