VS TCP/IP Stack Release 1.85.00 Customer Software Release Notice Copyright, Wang Laboratories, Inc., 2000 Disclaimer of Warranties and Limitation of Liabilities ______________________________________________________ The staff of Wang Laboratories, Inc., has taken due care in preparing this document. However, nothing contained herein modifies or alters in any way the standard terms and conditions of the Wang purchase, lease, or license agreement by which the product was acquired, nor increases in any way Wang's liability to the customer. In no event shall Wang or its subsidiaries be liable for incidental or consequential damages in connection with or arising from the use of the product, the accompanying document, or any related materials. Software Notice _______________ All Wang Program Products (software) are licensed to customers in accordance with the terms and conditions of the Wang Standard Software License. No title or ownership of Wang software is transferred, and any use of the software beyond the aforesaid license, without the written authorization of Wang, is prohibited. CONTENTS PREFACE CHAPTER 1 INTRODUCTION Hardware and Software Prerequisites ........................ 1-2 Hardware ................................................. 1-2 Software ................................................. 1-3 CHAPTER 2 ENHANCEMENTS AND SPECIAL CONSIDERATIONS Enhancements ............................................... 2-1 Considerations and Restrictions ............................ 2-2 CHAPTER 3 PROBLEMS CORRECTED CHAPTER 4 MEDIA CONTENTS CHAPTER 5 SOFTWARE INSTALLATION AND OPERATION Software Installation ...................................... 5-1 Software Operation ......................................... 5-4 Files Created During Operation ........................... 5-4 Recovery from System Crash ............................... 5-5 Regular Maintenance ...................................... 5-6 Software Diagnosis ....................................... 5-7 Support Aids ............................................. 5-7 APPENDIX A VS DYNAMIC NAME SERVICE (VS DNS) AND THE NSLOOKUP UTILITY VS Dynamic Name Service .................................... A-1 NSLOOKUP Utility ........................................... A-2 NSLOOKUP Examples .......................................... A-4 iii TABLES Table 4-1 Media Contents........................................ 4-2 iv PREFACE This customer software release notice (CSRN) provides information specific to Release 1.85.00 of VS TCP/IP Stack. This notice is intended for system and networking administrators who will maintain the Release 1.85.00 VS TCP/IP Stack software. It gives an overview of the product, discusses its hardware and software requirements, explains enhancements since the previous release, discusses special considerations for its use, and lists the product's media contents. Finally, there is a chapter about software operation. The following publications are referenced within this CSRN or are suggested as prerequisite reading. - Wang Systems Networking VS Network Configuration Guide (715-0165) - DMS/TX Reference manual (800-1128-01) - VS TCP/IP Operations Guide, Release 1.6 (715-0915B) - VS TCP/IP Configuration Guide, Release 1.8 (715-0900C) - VS System Operator's Guide (715-0418C) - VS TCP API Programmer's Guide, Release 1.6 (715-4620) - VS TCP/IP 1.8 Enhancements (715-5292) v CHAPTER 1 INTRODUCTION The VS TCP Stack product consists of the Transmission Control Protocol (TCP), the Internet Protocol (IP) and the support program TCPEDIT. TCP and IP form the central core of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. Positioned above this core are components of the VS TCP Services product such as the File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP), Dynamic Name Service (DNS) and TELNET. TCPEDIT is a configuration editor that is used to configure the TCP/IP operating environment. DNSCFG is a configuration editor that is used to configure the VS Dynamic Name Service. VS TCP/IP 1.85 is year 2000 compatible. TCP provides a reliable connection-oriented transport protocol for use in ethernet and X.25 networks. IP supports the interconnection of communication subnetworks by providing routing, fragmentation and reassembly, and addressing services to the TCP. In routing received IP messages, VS TCP/IP acts as an endpoint node or as a gateway (dependant upon configuration). The TCP/IP configuration editor TCPEDIT consists of two primary components: - a menu providing options for creating/editing the TCP/IP configuration file, manipulating TCP/IP "starter kits", and accessing associated utilities required for complete configuration - the PACE application which creates and maintains information in the TCP/IP database. Refer to the VS TCP/IP Configuration Guide, Release 1.8 for more information about TCPEDIT. 1-1 HARDWARE AND SOFTWARE PREREQUISITES The VS TCP/IP Stack, Release 1.85 software is customer installable. Before the software can operate, however, the components listed in this section must be installed. Hardware The VS TCP/IP Stack, Release 1.85 will run on the following Wang systems: VS6, VS 65, VS 85, VS 100, VS 300, VS 5000, VS 6000, VS 7000, VS 8000, VS 9000, VS 10000 VS 12000, and VS 16000 Series. These systems require standard VS configurations with at least 4096K of physical memory and at least 16 megabytes of virtual address space. To run TCP/IP in the foreground with the correct data area, run the VS SECURITY utility and specify a modifiable data area of 4096. For 802.3 networks, a VS LAN controller is required. For X.25 networks, a VS 128K Telecommunications Controller (VS-TC1 or a VS-6550) can be used on any VS. If a VS-TC1 board is used, it must be installed in a VS external chassis (VS-6554) and connected as follows: - For VS85/100 systems, a connection to a serial IOP - For VS300/7000/8000/9000/10000/12000/16000 systems, a connection to a serial IOC - For a VS5000/6000 Series system, a TC1 Telecommunications Coprocessor - For VS 6/65, a Telecommunications Device Adapter (TCDA) internal board can be used instead of the VS-TC1. In this case, no external chassis or serial port is required. 1-2 Software VS TCP/IP Stack requires the following software components: - VS Operating System, Release 7.21.09 or later, Release 7.42.00 or later, or Release 7.53.00 or later on all VS systems in the network NOTE: The Inter-Process Communications (IPC) mechanism within the VS Operating System has a finite number of buffers available to it. If problems occur relating to applications exhausting the available IPC buffers on VS OS 7.21.09, either apply OS patch RSDP 0728 (MCO BM05) or consider an upgrade to the Operating System. VS OS Release 7.53.00 and later have additional IPC buffer space available. - VS Device Support Package, Release 3.60 or later - PACE Runtime, Release 02.00.80 is required by VS TCP/IP and is is provided on the release media. - Either: - VS OSN NETCORE, Release 9.20.00 or later - Either: -VS OSN X.25 data link software, Release 3.40.65 or later or -VS OSN 802.3 data link software, Release 3.0 or later - Optional software: Non-Wang VS systems using the Berkley UNIX version 4.2 BSD TCP/IP implementation may also operate within a VS TCP/IP environment. 1-3 CHAPTER 2 ENHANCEMENTS AND SPECIAL CONSIDERATIONS This chapter lists enhancements made to this version of the VS TCP/IP Stack, Release 1.85.00 and discusses special considerations that apply to the configuration, operation, and administration of this release of the software. The enhancements are the major improvements that have been made to the product since its previous release. The special considerations are notes of special interest about the software or required hardware. ENHANCEMENTS The following enhancements have been made to VS TCP/IP Stack 1.85.00 product: - VS TCP/IP Stack 1.85.00 has been compiled and linked using year 2000 compliant compilers and linker. - The TCPTOOL utility has been enhanced to support creating a trace file larger than 5,000 records. The record count range has been changed to 100 - 99,999,999. - VS TCP/IP Stack no longer submits the TCPSTART procedure if it is unable to attach to the network link. See Restrictions and Special Considerations item 22. The following enhancements have been made to VS TCP/IP Stack 1.80.00 product: - Support for concurrent X.25 and 802.3 networks. VS TCP/IP 1.8 allows routing through the Stack which provides the ability to access systems over 802.3 and X.25 systems simultaneously. Previous releases restricted TCP/IP access to a single network type. 2-1 - VS Dynamic Name Service (VS DNS) provides the VS with client support of the Domain Name Service. Domain Name Service (DNS) provides the ability to easily send and receive data from systems in a TCP/IP network that are not pre-configured on the VS. This is accomplished by a server process that runs an application known as the Domain Name Server. Associated with this is a database known as a Directory Information Base (DIB) which contains the information necessary to map the names of any network or organization on the internet to its internet address. - Recognition and support of standard subnetting. Subnetting is a method that makes it possible to divide a single network into multiple logical networks or subnets. - VS TCP/IP 1.8 allows the user to increase the number of 802.3 devices from the default of two. This provides the ability to spread the workload over multiple ILC devices and can improve Inbound TELNET response time. For users doing Inbound TELNET using an ILC they will find better response time if they reserve 4 or more devices on the controller. This value can be changed in the procedure $TCPIP$ in @TCPIP@. With TCP/IP 1.8 the number of supported Inbound TELNET sessions is increased from 6-10 sessions to 16-32. - Tracing is timestamped in the unformatted TCP Trace log. CONSIDERATIONS AND RESTRICTIONS This section describes considerations and restrictions for the configuration and operation of systems running VS TCP/IP Stack software. 1. The following software needs to be installed on the VS prior to installing the VS TCP/IP Stack, Release 1.85 software: - Either: - VS OSN NETCORE, Release 9.20.00 or later - Either: -VS OSN X.25 data link software, Release 3.40.65 or later or -VS OSN 802.3 data link software, Release 3.0 or later 2. TCPEDIT makes use of the VS PACE Runtime, Version 2.0 to manipulate the TCP/IP configuration database. The user is not required to purchase PACE; the necessary components are included with the VS TCP/IP Stack product. If PACE 2.0 has been purchased and installed on the system, TCPEDIT will not affect any current databases or PACE applications. 3. In TCPEDIT when a new item is added to a list, the list remains positioned as it was prior to the Add operation rather than at the new object. 2-2 4. The following services are not available to users of VS TCP/IP, Release 1.85: - UDP - active open with data - precedence and security inputs are accepted but not used - urgent data - user is not informed of contents of ICMP status messages - the following status information is not available: - amount of data willing to be accepted by local TCP - amount of data allowed to send to remote TCP - amount of data awaiting acknowledgment - amount of data pending receipt by local task - urgent state - precedence - security - task timeout 5. For each link defined in the TCP/IP configuration, the user is required to run the WSNEDIT configuration editor (part of the OPEN Systems Networking (OSN) NETCORE product or Wang Systems Networking (WSN) CNS product) to define a corresponding OSN data link in the active Wang Systems Networking (WSN) configuration file. NOTE: The OSN NETCORE product is designed to support non-WSN (Wang Systems Networking) programs, such as TCP/IP, that have a requirement for some of the NETCORE components. This OSN data link definition includes the protocol-specific parameters for the link and identifies the Data Link Processor (DLP) which services the link. The Link Name and Type values defined in the VS TCP/IP configuration must be exactly the same as the corresponding Data Link name and Type values in the OSN configuration. For information about OSN/WSN configuration, refer to the Wang Systems Networking VS Network Configuration Guide. 6. Due to a restriction in OSN NETCORE, there must be at least one "WSN System" defined on the OSN data link (see Item #4) in order for microcode to be loaded into the DLP for that link. In operating environments where the link is shared by VS TCP/IP and WSN, there is no special configuration necessary for TCP/IP. However, if the link is to be used by VS TCP/IP exclusively, a dummy "WSN System" must be defined and added to the data link definition in the OSN NETCORE configuration, using WSNEDIT. 7. Backup copies of the configuration file TCPCNFIG in library @TCPIP#A should be created using TCPREORG (from the TCPEDIT main menu chose to reorganize the TCP configuration file, the reorganized file is placed in library TCPREORG with the name of TCPCNFIG). If a copy is created in any other manner, the file and/or the library of the copy MUST be named differently. 2-3 8. The VS system must be re-IPLed whenever changes are made to the "Data link" definition in the OSN NETCORE configuration (see Items #4 and #5). Changes to the TCP/IP configuration do NOT require an IPL. Starting and stopping the TCP/IP software will activate any changes to the TCP/IP configuration. 9. A limited X.25 Parameter Negotiation is supported by the current release. Inbound X.25 connect requests must request a packet size of 512 or greater and a window size of 7 or greater. The limited negotiation will respond with packet negotiation of packet size 512 and window size of 7. Outbound X.25 calls will attempt a packet size of 512 and a window size of 7. Any negotiation done to lower these amounts will cause undetermined problems. 10. The VS TCP/IP Stack software currently has a limit of 512 items for the internal host table. When the configuration file TCPCNFIG in library @TCPIP#A contains more than 512 adjacent hosts, the TCPIP stack at initialization will bring 512 items into the internal host table; on the attempt to bring in the 513th, the following log message is issued "290: NSIFINIT: Host table overflow!!!!!!!!!" 11. Load considerations -- It is not recommended that an I/O intensive program such as PING be run indefinitely. PING should be used as a functional test of a network link, not as an application. Programs like PING flood the network with traffic. This flooding impedes the processing of requests for new sessions via FTP, SMTP or TELNET. 12. Multiple reloads of an 802.3 controller may cause TCP/IP to crash. 13. The Inter-Process Communications (IPC) mechanism within the VS Operating System has a finite number of buffers available to it. If problems occur relating to applications exhausting the available IPC buffers on VS OS 7.21.09, it may be necessary to upgrade the Operating System or apply patch RSDP0728 (MCO BM05). VS OS Release 7.42.00 and later have additional IPC buffer space available. 14. When configuring an IBM AIX system, be aware that AIX makes a distinction between Ethernet and IEEE 802.3 data packets. The VS TCP/IP implementation uses Ethernet packets. 2-4 15. This version of TCPEDIT performs limited data validation. Range checking for Internet Addresses, and validation of Link Types is performed. However, the following items are not validated: - The syntax of domain names (for hosts), network names, link names, SMTP relay paths, X.25 DTE addresses and 802.3 cable addresses - The existence of duplicate DTE or cable addresses - The existence of a link connection definition for each host definition by which the local system is identified. 16. TCPEDIT error messages are very generic in nature. For example, "Cannot Insert. Duplicate Key" is displayed if a host is defined with a duplicate domain name or Internet address, and the duplicate field blinks. In the following two cases, however, the wrong field will blink: - when attempting to define the same link connection for a given host a second time, - when attempting to define the same gateway connection for a given network a second time. In both cases, the host and network internet addresses blink, while it is the link name and gateway names that are actually in error. 17. When using the VS TCP API, note that the Stack has limited buffer resources and can not simultaneously support 64 NETLISTENs and NETOPENs. 18. When changing the cache size in DNSCFG, the user must stop and then restart both the Resolver and the VS TCP/IP Stack for the change to become activated. If the Resolver only is stopped and restarted, the Resolver will crash with a PC05. To stop the VS TCP/IP Stack, run TCPSTOP. This will terminate all VS TCP/IP tasks. 19. If your local VS host is connected to more than one network (that is has an X.25 and a 802.3 link for TCP/IP use), you will need to define a local host for each of these links. Each local host should specify a link and the internet address of the host on that network. 2-5 20. System administrators can turn on the activity probe message (keep alive) by patching the executable file. Run EZPATCH specifying TCPIP in @TCPIP@ on the installed volume as input. Search for all occurences of the string "TCP NO ACTIVITY TIMER OPTION IS SET TO OFF". To turn on the activity probe, change the word OFF to ON in all occurences. Note that this is a change from previous releases. Previously the no activity timer defaulted to on. Note that it is recommended that the activity probe is set to off. 21. System administrators can turn off the routing aspect of multiple link support (use of both an X.25 and a 802.3 link) if this is not needed on their system. Run EZPATCH specifying TCPIP in @TCPIP@ on the installed volume as input. Search for the string "IP GATEWAY IS SET TO ON ". To turn off the routing function, change the word ON to OFF. 22. (E119936) In prior releases it could appear that TCP tasks were multiplying in the procedure queue when the network link was not active at startup. This was because TCP/IP would detect that it was unable to attach to the link and would resubmit TCPSTART in an attempt to reattach to the link. If the link was not active, the TCP procedure would be resubmitted repeatedly. Customers were advised to provide extra initiators or to rename the TCPSTART procedure. In release 1.85, VS TCP/IP no longer resubmits the TCPSTART procedure when it is unable to attach to the network link. Customers may want to rename their TCP start procedure back to TCPSTART or readjust the number of initiators available (Z and Y class). 23. If your local host is on a subnet and you do not want TCP/IP to ascertain the subnet mask or there is no system on the subnet that will respond to an ICMP address mask request, you must define the subnet mask. To define the subnet mask, after the network link for the host is defined, specify a second link with a linkname whose first eight characters are "ZZSUBNET". The type of link is not significant. Enter the subnet mask in the DTE Address field. For example, ZZSUBNET-MASK-LI, Type 802.3, Address 255.255.80.0. Note that ZZSUBNET marks the definition as a subnet mask definition. 2-6 24. TCP/IP has an internal buffer trace which can be set (the default is: do not trace). To patch module TCPIP to trace buffers look for "TRACEFLAG". Somewhere after TRACEFLAG, look for '00001ABC0000000000003ABC'. Any of the 8 bytes following 1ABC should be non-zero to enable the trace. This trace should only be enabled if a Wang analyst requests it. The tracing is done internally and a dump is required to view the tracing. The trace format is not documented. 25. NSLOOKUP help text may be displayed. There is no facility to print the help text. For additional information on NSLOOKUP please see Appendix A. 26. DNS Resolver works as follows: if RETXTM = 5, RETXCNT = 3, and QUERYCT = 9, then the resolver will transmit a query to the name server using name. If there is no response in 5 seconds (RETXTM) the reolver will retry to the name server using a variation on the name. The resolver will query the primary name server 3 times, 5 seconds between queries. It will then try the other name servers, once again using derivatives of the name if the first query times out until it has sent out 9 queries. 27. The FTP foreground program uses DNS settings for the source host. 2-7 CHAPTER 3 PROBLEMS CORRECTED The following problem was corrected in Release 1.85.00 of VS TCP/IP Stack: E119936 VS TCP/IP Stack re submits itself if attach to network link fails. M200023698 After advertising a window size of zero, TCPIP would not advertise a larger window size. M200023692 TCPTOOL displays port numbers greater than 32767 incorrectly. The following problems were corrected in General Release 1.80.00 of VS TCP/IP Stack: M800026718 TCPIP stack transmits SYNs at the appropriate time. M200023537 Out of sequence FIN processing corrected. Internal TCP/IP has an internal buffer trace which can be set. M200023020 The keyword "SUBNET" was changed to "ZZSUBNET". M200022952 User can not Ping past the gateway. M200023501, M200023088 TCPIP stack crash running X.25 transport. M200023199 Support for user specified length for the ICMP Echo request. M200023304 When TCP/IP retransmits a FIN segment with no data, the sequence number is not incremented. M410012454 If TCP/IP receives a RST segment in response to an ACK/FIN segment, the ACK/FIN is not retransmitted. M200023259 If TCP/IP received a FIN segment on an unknown connection, TCP/IP now replies with valid sequence and ack numbers. M410012388 TCP/IP no longer retransmits buffers too soon. M200022511 TCP/IP uses EVTalloc to get buffers for ECB's and BCB's. M200022596 TCP/IP sends Reset commands with the value of the last ack received on the Reset. M200022404 Multiple copies of the same TCP segment are not sent when a blocked condition detected at the subnetwork layer interface. Internal Tracing is now timestamped in the raw logs. Internal The forwarding aspect of multiple links may be turned off. G410011545, M410012036, M410012047, M410012064, M200022045 -- KEEP ALIVE default is OFF. 3-1 M200021817 TCPIP header zeroed out. Internal CLEVT 3.00.25 linked in. M410011707 TCPECHO not stopping via TCPSTOP. Internal Trace message added, "FATAL ERROR IN EVTCHECK, TCP/IP TERMINATING, RC = %D". Internal CLIF 3.00.31 linked into TCPIP, TCPECHO, and TCPOPEN. M410011461 PC06 when using RSMANAGE, null pointer in use. M410011527 TCP tasks would multiply in the procedure queue when a link was not active at startup. M410011962, M200023308 -- TCPEDIT problems on OS 7.50. M200023544 If FIND not found in VSSUBS on SYSTEM, install fails. 3-2 CHAPTER 4 MEDIA CONTENTS This chapter provides a list of the files contained in Release 1.85.00 of the VS TCP/IP Stack product. The VS TCP/IP Stack software is available on the following media types: Designation Media Type (-7) 9-track tape (-G) Streamer cartridge (-Q) 4 mm dat Table 4-1 lists the media contents of the VS TCP/IP, Release 1.85 product. In the table, Protection Class represents the value of the file on the tape; during installation the class may be changed. Changing the protection class of these files may affect the operational characteristics of TCP/IP on your system. Version numbers for most files may be found by displaying the first record of the file. 4-1 Table 4-1. Media Contents File Version Description -------------------------------------------------------------------------- Library = @TCPINST @PACECAT None Empty PACE Catalog @PACEDEF 02.00.60 PACE Catalog Data Definition @PACEMSG None Message file for PACE run-time system. CASEFLIP None Required PACE file CHKDMSTX 06.00.05 Required install program DBFIND 01.02.13 Required install program LOADDEF None Used in install PACE 02.00.80 PACE Manager PACEFRM None PACE Manager Screen File PACERTL 02.00.80 PACE Runtime SSL PROCGEN 06.00.02 Required install program REMOUNT 07.30.06 Required install file SSLUTIL 01.97.49 Install utility to catalog the SSL alias TCPEDIT None TCPEDIT AB program - core editor and PACE runtime TCPEDIT1 None TCPEDIT AB program - core editor, uses PACE runtime SSL TEMP 01.85.00 Used in install Library = @TCPIP@ $RESOLV$ 01.85.00 Procedure to run RESOLVER in background $TCPIP$ 01.85.00 TCP/IP Start procedure @TCPDIAG 01.85.00 TCP/IP inbound test program DNSCFG 01.85.00 Configuration editor to configure VS DNS DNSINST None Procedure to install VS DNS EXTRACT 07.30.09 Used in TCPSTART FIND 07.30.10 Used in install GETSTATS None TCP/IP Buffer Usage Statistics INSTALL 01.85.00 TCP/IP install procedure -------------------------------------------------------------------------- (continued) 4-2 Table 4-1. Media Contents (continued) File Version Description -------------------------------------------------------------------------- Library = @TCPIP@ (continued) NSLOOKUP 01.85.00 Executable providing user direct access to VS DNS PAUSE 06.00.03 Used in TCPSTART PING 01.85.00 VS-based Ping program README None General information - install order and mailing lists RESOLVER 01.85.00 Client process of the Domain Name System RESSTART None Procedure to start RESOLVER RESSTOP 01.85.00 Executable to stop RESOLVER SESSTRC None TCP/IP Session Statistics SETGEN 04.01.00 Required install program TCPDBG 01.85.00 Diagnostic tool, used by TCPTOOL TCPECHO 01.85.00 Echo and disc Server TCPEND 01.49.70 TCP/IP task killer TCPIP 01.85.00 TCP/IP Network Access Task TCPLOG 01.49.70 TCP/IP log control utility TCPMON 01.85.00 TCP/IP logging display TCPOPEN 01.85.00 Open Test procedure TCPSTART 01.85.00 TCP/IP start procedure TCPSTOP 01.85.00 TCP/IP stop program TCPTOOL 01.85.00 TCP/IP Diagnostic Tool Library = @TCPIP#3 @DBMSG 01.09.07 PACE messages Library = @TCPIP#4 $NEWS 01.85.00 Installation News file TCPCONUP 01.06.05 SRI-NIC host table reader TCPEDIT 01.85.00 Procedure to invoke the TCPEDIT AB program TCPREORG 01.85.00 Procedure to reorganize the TCP/IP configuration file -------------------------------------------------------------------------- (continued) 4-3 Table 4-1. Media Contents (continued) File Version Description -------------------------------------------------------------------------- Library = VSSUBS FIND 07.30.10 Find Utility MESSAGE 06.40.09 Message Routine Library = @TCPIP#A NEWCNFIG 01.00.03 Template for new TCP/IP Configuration file Library = @TCPIP#D @DBSSL None PACE Shared Subroutine Lib @PACEDDO None TCP/IP Data Dictionary @PACEDEF 02.00.60 TCP/IP Data Definition Library = @TCPIP#J HOSTNAME None PACE Table exit object NICKNAME None PACE Table exit object Library = @TCPIP#K DDNACCES 01.01.13 TCP/IP Database access SSL Library = @TCPIP#Z TCPEDIT 01.01.04 TCPEDIT AB Program - the screenfile Library = CSRNLIB TCPIP 01.85.00 VS TCP/IP STACK CSRN 1.85.00 -------------------------------------------------------------------------- 4-4 CHAPTER 5 SOFTWARE INSTALLATION AND OPERATION This chapter provides you with a procedure for installing the VS TCP/IP Stack, Release 1.85 software. It also discusses certain features of the software's operation after it is installed. SOFTWARE INSTALLATION To install the VS TCP/IP Stack software on your system, follow these steps: NOTES: You must have VS security administrator rights on the system you are installing to. If this is a re-installation of the TCP/IP software on a volume that is different from the one that the currently installed version of TCP uses, then you must backup the configuration file TCPCNFIG in the Library @TCPIP#A on the current install volume to the new install volume (see the note below on creating backup copies of the TCP/IP configuration file. If this is a re-installation, ensure that no users are running TCPEDIT or any VS TCP/IP tasks (FTP for example). TCPSTOP will terminate all VS TCP/IP tasks. If this is an upgrade, this is an ideal time to backup your TCP/IP configuration file. NOTE: Backup copies of the configuration file TCPCNFIG in library @TCPIP#A should be created using TCPREORG (from the TCPEDIT main menu chose to reorganize the TCP configuration file, the reorganized file is placed in library TCPREORG with the name of TCPCNFIG. If a copy is created in any other manner, the file and/or the library of the copy MUST be named differently. 5-1 Ensure that the VS system you are installing to supports DMSTX. The file DMSTX must be in the system library on the system volume. 1. Log on to the system as a VS System Administrator. 2. Run GENEDIT. At the System Options Main Menu, the DMS/TX option must be set to YES. At the System Options/DMS Options screen, the 'Use SPECIAL I/O mode' option must be set to YES. 3. Mount the tape containing the stack software, and set the following values: Set Volume = Volume name (UPGRD or STACK depending on order) Label = NL (for TAPE) Mode = EX 4. Run BACKUP with Function = RESTORE and Dupfiles = SCRATCH on the release tape to copy all files from the release tape to the installation disk. 5. Dismount the input tape volume. 6. Run INSTALL in @TCPIP@. The following screen appears: ----------------------------------------------------------------------- *********************************************************************** TCP/IP & TCP/IP Configuration Editor Installation Version 01.85.00 (c) Copyright, Wang Laboratories, Inc., 1998 TCP/IP installation will proceed on volume Volname when ENTER is pressed, or press PF16 to exit without installing TCP/IP ----------------------------------------------------------------------- 7. If the TCP/IP (output) volume does not have enough space, cancel the install and reorganize the output volume before retrying the installation. 8. A special consideration or "News" file is displayed at the end of the installation process. Press PF16 to exit after reading the file. 9. The library @TCPINST may be deleted after installation to save space. 5-2 10. The TCP/IP background task must run in a process with a modifiable data area (MDA) of at least 4096K. TCPSTART in the system library on the system disk will normally submit the TCP/IP task to a class Z initiator. (In TCPSTART the default initiator class is Z, so the user should have a Class Z initiator and a modifiable data area of in the range of 4096 - 6144.) For instructions on how to create an initiator, see the VS System Operator's Guide. If you wish to change the initiator class that TCP/IP runs in to a class other that Z, you must edit the TCPSTART procedure and create an initiator with a new class not used for any other initiators to assure a task slot in which TCP/IP can run. To edit TCPSTART, run the EDITOR program from the Command Processor screen. Edit TCPSTART in @SYSTEM@ and press PF1 to display the following screen: (1)Disp (2)First (3)Last (4)Prev (5)Next (6)Down (7)Up (8)Find Display (9)Mod (10)Chng (11)Ins (12)Del (13)Move (14)Copy (15)Col (16)Menu 001700 if &VERSION < "072109" goto NOIPC 001800 if not exists file $TCPIP$ in &PROGLIB on &PROGVOL goto NOPROC 001900 if not exists file TCPIP in &PROGLIB on &PROGVOL goto NOPGM 002000 002100 *********************************************************************** 002200 * The following line must be changed if all background initiators on the 002300 * system do not have at least 4096K of MDA. If they do not 002400 * create initiator with at least 4096K of MDA with a class 002500 * unused by other applications. Modify the class below to this class. 002600 *********************************************************************** 002700 002800 submit $TCPIP$ in &PROGLIB on &PROGVOL, CLASS = Z 002900 goto ENDPROC 003000 003100 NOIPC: 003200 PROMPT PFKEY = &PFKEY 003300 CENTER BRIGHT "VS OS RELEASE 07.21.09 OR GREATER REQUIRED";;; 003400 CENTER "TCPIP will not be submitted";;;; 003500 CENTER "Press ENTER to continue" a. Press PF9 to edit the screen and position the cursor under the Z in the Class = Z clause of the submit statement on line 2800. b. Change this value to the class of the newly created initiator. c. Press Enter to save the modification. d. Press PF16 to return to the main menu. e. Press PF6 to replace the file. f. Press PF16 to exit. 5-3 11. If a configuration file does not already exist, run TCPEDIT and create a TCP/IP configuration file before starting TCP/IP. 12. To install DNS (Note: it is recommended that you run TCP/IP 1.85.00 initially without activating any enhancements introduced by 1.85.00 to verify its stability in your environment): - run DNSINST in @TCPIP@ (for more information on parameters see Appendix A) - The Resolver task requires another class Y background initiator (2048K modifiable data area or MDA) 13. To verify a successful installation, a. Start TCP/IP (TCPSTART). WSN should already be started and your TCP/IP link should be enabled. (Refer to the VS TCP/IP Operations Guide, Release 1.6 for additional information.) b. Run TCPOPEN in library @TCPIP@ to a node on your network. SOFTWARE OPERATION The procedures TCPSTART, TCPSTOP, TCPMON, and TCPEDIT are automatically created during the install process and placed in the system library on the system volume. They run the respective programs which are installed on the TCP/IP volume. For more information about TCPSTART, TCPSTOP, and TCPMON, refer to the VS TCP/IP Operations Guide, Release 1.6. For information about TCPEDIT, refer to the VS TCP/IP Configuration Guide, Release 1.8. Files Created During Operation During the normal operation of the TCP/IP Network Access Task (TCPIP), the following files are used: File Library Volume Description TCPCNFIG @TCPIP#A tcp/ip Active TCP/IP configuration file Lyymmdd @LOG@ system Daily log file (where yy=year, mm=month, dd=day) $TCPEND @SYSTEM@ system Procedure file created by TCP/IP and run by TCPSTOP to terminate the background TCP task 5-4 During normal operation of TCPEDIT, the following files are used on the system, TCP/IP install, or PACE volumes. If PACE was already installed prior to the VS TCP/IP, Release 1.8 installation, it remains on the same volume; if installed by the TCP/IP Stack INSTALL software, it will be on the system volume. File Library Volume Description TCPEDIT @SYSTEM@ system System startup procedure TCPEDIT @TCPIP#4 tcp/ip TCPEDIT Menu procedure TCPEDIT @TCPIP#Z tcp/ip TCPEDIT Pace screenfile TCPEDIT @TCPIP## tcp/ip TCPEDIT program and PACE runtime @PACEDEF @@P0200D system TCP/IP database data definition @PACEDDO @TCPIP#D tcp/ip TCP/IP database data dictionary @PACECAT @PACE@ system PACE database catalog TCPCNFIG @TCPIP#A tcp/ip Active TCP/IP configuration file PACERTL @@P0200D system PACE Runtime SSL PACE @@P0200D system PACEFRM @@P0200D system During normal operation of TCPEDIT, two temporary files are created. They are deleted automatically upon normal termination of TCPEDIT. The two file are: File Library Volume Description @dddduuu @TCPIPB tcp/ip DMS/TX BIJ for the TCP/IP database Wdddduuu @TCPIP#A tcp/ip "Work" copy of TCP/IP configuration file where, dddd is a unique four digit number uuu is the user's three character logon id Recovery from System Crash If TCPEDIT is terminated abnormally due to a system crash, two types of recovery need to be performed. Failure to perform this recovery may result in abnormal operation of the VS TCP/IP products (e.g. TCP/IP, FTP, SMTP, TELNET and TCPEDIT). First, DMS/TX recovery must be performed on the TCP/IP database. To do so, log on as a VS Security Administrator, run TCPEDIT, and select PF6 (Recover TCP/IP database). Upon notification of successful recovery, subsequent operation of the TCP/IP products will proceed normally. If recovery does not complete successfully, refer to the DMS/TX Reference manual for an explanation of the displayed DMS/TX failure code. 5-5 NOTE: This recovery action is required when any VS TCP/IP products are in operation when a system crashes. Only a VS Security Administrator can run the "Recover TCP/IP database" procedure (PF6). Second, changes to the TCP/IP configuration using TCPEDIT are applied to a "work" copy of the configuration file instead of the actual configuration file. Therefore, any changes not explicitly saved prior to the the abnormal termination (system crash) of TCPEDIT will not be contained in the actual TCP/IP configuration file. It is still possible to recover most of the changes, however. The "work" copy of the TCP/IP configuration file is in library "@TCPIP#A" on the TCP/IP volume. It contains all changes made to the TCP/IP configuration up to, but not including, any change that was in progress at the time of the system crash. Work files can be identified by the logon id used at the time of the system crash, as described in the "Files Opened/Created During Operation" section above. To recover the configuration as it exists in the work file, run TCPEDIT and select PF3 (Create TCP/IP Configuration from Starter Kit). Specify the file name, library and volume of the work file, then press ENTER. At this point, the state of configuration changes has been restored to that at the time of the system crash. Since the retained work file is essentially used as a "starter kit" in this case, it will not be deleted upon normal termination of TCPEDIT. Therefore, it should be deleted manually, using the Manage Files/Libraries function from the VS Command Processor. Regular Maintenance TCP/IP and TELNET create logging entries to a daily dated file in library @LOG@. These files need to be purged periodically. If there have been no problems with TCP/IP, the files may be discarded. Regular maintenance should include periodic reorganization of the TCP/IP configuration file. Whenever changes are made to the TCP/IP configuration, the file may become more and more fragmented (a side effect of VS indexed files). This reduces the efficiency with which information is retrieved from the file and takes up valuable disk space. Potentially, the maximum number of extents for a VS index file could be exceeded if the file is not periodically reorganized. 5-6 Another reason for periodically running the reorganization function is to insure against loss of the TCP/IP configuration file. If the active configuration file (TCPCNFIG in @TCPIP#A on volume on which TCP/IP is installed) is ever accidentally scratched or damaged, the backup copy created during reorganization can be used as a "starter kit" to restore the TCP/IP configuration. To reorganize the TCP/IP configuration file, run TCPEDIT and select PF5 (Reorganize TCP/IP Configuration). Upon completion of this process, a backup copy of the existing active TCP/IP configuration file will be placed in the TCPREORG library in the system volume; the existing active copy will be replaced with the newly reorganized (compacted) copy. Software Diagnosis If TCP/IP should crash, a dump file will be created in the print library on the work volume of the user who started the tasks. Contact your local Wang Customer Engineering representative for disposition of the dump file and to determine what other diagnostic materials will be needed to determine the problem. Should TCPEDIT functions PF2 (Create configuration from starter kit), PF3 (Edit/Create configuration manually), or PF4 (Export starter kit from configuration) be run after a system crash without first performing the recovery process described in the "Recovery from System Crash" section, a program check will likely occur. This program check is generated by the PACE run-time system and will indicate that the TCP/IP database needs to be recovered. To correct the situation, perform the recovery process and re-run the desired TCPEDIT function. Support Aids The VS TCP/IP Stack includes the following administrative programs to help configure, monitor, and test the TCP network: TCPMON - Provides the ability to access error and event information logged by the TCP stack components and FTP. TCP Test Programs - Provide the ability to run echo and discard diagnostic functions that test the connectivity and throughput of the network. PING - Provides the ability to test a specific internet address to see if the network connection is functioning. VS NSLOOKUP - Utility that can assist the network administrator in diagnosing VS DNS problems. 5-7 APPENDIX A: VS DYNAMIC NAME SERVICE (VS DNS) AND THE NSLOOKUP UTILITY This section provides you with information on the VS Dynamic Name Service and the NSLOOKUP Utility. The option descriptions outlined here superscede the descriptions appearing in the VS TCP/IP Configuration Guide 1.80. This information is meant to augment or correct the information provided in the VS TCP/IP Configuration Guide 1.80. This information should be used in combination with the information provided in the Configuration Guide. VS Dynamic Name Service (VS DNS) VS Dynamic Name Service (VS DNS) provides the VS with client support of the Domain Name System. Domain Name System (DNS) provides the ability to easily send and receive data from systems in a TCP/IP network that are not pre-configured on the VS. This is accomplished by a server process that runs an application known as the Domain Name Server. Associated with this is a database known as a Directory Information Base (DIB) which contains the information necessary to map the names of any network or organization on the internet to its internet address. RFC1123 provides additional information on DNS. DNSCFG is a configuration editor that is used to configure the VS Dynamic Name Service. The following is an example of the configuration information you provide to DNSCFG. The System Administrator will be prompted for this information when running DNS Install (DNSINST) or DNSCFG. CACHESZ = 1000000 size in bytes, of the cache file to be created. SWEEPTM = 0086400 number of seconds between cache cleanup (86400 = 1 day). RETXTIM = 05 number of seconds to wait before resending queries. RETXCNT = 03 number of times per name server to resend queries. QUERYCT = 09 number of times to retry a query before failing. Enter/Modify the name and internet address of this host. HOSTNAM = w0000600.wang.com HOSTIP = 150.124.163.26 Enter/Modify the domain name of this host. DOMAIN = wang.com A-1 Enter/Modify the primary name server and ip address for the domain. NSNAME1 = ns3 NSIP1 = 150.124.52.18 Enter/Modify secondary name server and ip address for domain (optional). NSNAME2 = ns1 NSIP2 = 150.124.4.12 Enter/Modify tertiary name server and ip address for domain (optional). NSNAME3 = ns2 NSIP3 = 150.124.52.16 Enter/Modify up to three aliases for this host (optional). ALIAS1 = sesame ALIAS2 = w600 ALIAS3 = w0000600 Enter/Modify three alternate ip addresses for this host (optional). HOSTIP2 = HOSTIP3 = HOSTIP4 = When changing the cache size in DNSCFG, the user must stop and then restart both the Resolver and the VS TCP/IP Stack for the change to become activated. If the Resolver only is stopped and restarted, the Resolver will crash with a PC05. NSLOOKUP Utility NSLOOKUP is a utility to assist the network adminstrator in diagnosing VS DNS problems. This utility is modeled after an UNIX utility NSLOOKUP. NSLOOKUP can only be run by System Administrators. If a user without System Administrator privileges runs NSLOOKUP and requests resolution of an address or domain name, the following erro message will be displayed " *** FATAL!! Resolver not running." A-2 The NSLOOKUP utility uses the following abbreviations for NSLOOKUP operations: OPTION DESCRIPTION help or ? displays NSLOOKUP information set OPTION set an option help displays information on common NSLOOKUP options all displays all the current settings used by NSLOOKUP. Also displays the local host's official name and Internet address as defined in DNSCFG. (not TCPEDIT) (no)def (no)defnames: appends the domain name to the query name if the query name does not contain any periods (no)recu (no)recurse: querys additional name servers if the remote name server cannot resolve the query (no)dnsr (no)dnsrch: appends the domain name to the query name if the query name does not contain a period at the end of the query name (no)pas (no)passcache: does not search for query name before querying the remote name server (no)try (no)tryddn: searches TCPEDIT configuration file if the query name is not resolved by a remote name server ti=x timeout=x: sets time out interval for waiting for a response before abandoning the query. (Note: any queries resolved after the utility times out are lost; cache is updated with new information) ty=x type=x: sets the type of query information requested: a (address) query submits a host name and response is an Internet address ptr (name) query submits an Internet address and response is a host name mx (mail exchange) query submits a mail name and response is a list of addresses of hosts that can receive mail for the mail name quer=x querytype=x: same as ty=x exit exits NSLOOKUP utility Several options are supported that will affect how searches will be performed: If a RECURSIVE SEARCH is desired (the default), the VS resolver will ask the domain name server to search for the name using additional name servers to resolve the request. If this is not set, the VS resolver will attempt to resolve the request using the more limited information it has available to it. A-3 If DEFAULT NAMES is set (the default), the resolver will append the domain name to the query name if the query name does not contain any dots (.) and search the current domain to locate the requested name. If DOMAIN NAME SEARCH is set (the default), the resolver will append the domain name to the query name if the query name does not contain a dot (.) at the end of the query name and search the current domain and the parent domain to locate the requested name. NSLOOKUP Examples 1. set all Note that these options are in effect for the rest of the examples unless overriden by a set command as part of the example. Set options: defnames recurse dnsrch timeout=10 nopassche port=53 querytype=A class=IN tryddn Local Host Name: W0000600.WANG.COM Local Host Address(es): 150.124.163.26 2. td600 TD600 is on this network Name: td600.wang.com Address(s): 150.124.163.34 TCPMON Messages: DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: td600.wang.com. DNS:044 Resolver has processed a response to query: td600.wang.com, Response code: 0. A-4 3. 199.210.153.34 Although Query Type is A, an internet address can be processed. 199.210.153.34 is not a known internet address in this network so a timeout to the query is reasonable. Note that "34.153.210.199.IN-ADDR.ARPA" is not a mistake. *** Timeout attempting to get information. Try Again. TCPMON Messages: DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: 34.153.210.199.IN-ADDR.ARPA. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: 34.153.210.199.IN-ADDR.ARPA.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: 34.153.210.199.IN-ADDR.ARPA.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: 34.153.210.199.IN-ADDR.ARPA. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: 34.153.210.199.IN-ADDR.ARPA. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: 34.153.210.199.IN-ADDR.ARPA. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: 34.153.210.199.IN-ADDR.ARPA. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: 34.153.210.199.IN-ADDR.ARPA. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: 34.153.210.199.IN-ADDR.ARPA. DNS:031 Resolver has queried maximum number of name servers seeking to resolve: 34.153.210.199.IN-ADDR.ARPA DNS:044 Resolver has processed a response to query: 34.153.210.199.I N-ADDR.ARPA, Response code: 0. A-5 4. aol.com AOL.COM is not part of this network and is not defined in the configuration file *** Unable to satisfy query from TCPIP configfile. TCPMON Messages: DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.com.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.com.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.com. DNS:043 Resolver has queried name server with ip address: 150.124.4. 11 in an attempt to resolve: aol.com.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.8. 99 in an attempt to resolve: aol.com.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.8. 99 in an attempt to resolve: aol.com.com. DNS:043 Resolver has queried name server with ip address: 150.124.8. 99 in an attempt to resolve: aol.com. DNS:043 Resolver has queried name server with ip address: 137.39.1.3 in an attempt to resolve: aol.com.wang.com. DNS:043 Resolver has queried name server with ip address: 137.39.1.3 in an attempt to resolve: aol.com.wang.com. DNS:031 Resolver has queried maximum number of name servers seeking to resolve: aol.com.wang.com DNS:044 Resolver has processed a response to query: aol.com.wang.com , Response code: 0. A-6 5. aol. Notice the difference when the period is included as part of the name. *** Unable to satisfy query from TCPIP configfile. TCPMON Messages: DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol. DNS:022 Resolver query count has expired attempting to locate aol. DNS:044 Resolver has processed a response to query: aol, Response co de: 0. A-7 6. set nodnsrch wd600 *** Unable to satisfy query from TCPIP configfile. TCPMON Messages: DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: wd600.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: wd600.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: wd600. DNS:043 Resolver has queried name server with ip address: 150.124.4. 11 in an attempt to resolve: wd600.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.4. 11 in an attempt to resolve: wd600.com. DNS:043 Resolver has queried name server with ip address: 150.124.4. 11 in an attempt to resolve: wd600. DNS:043 Resolver has queried name server with ip address: 137.39.1.3 in an attempt to resolve: wd600.wang.com. DNS:043 Resolver has queried name server with ip address: 137.39.1.3 in an attempt to resolve: wd600.wang.com. DNS:043 Resolver has queried name server with ip address: 137.39.1.3 in an attempt to resolve: wd600.wang.com. DNS:031 Resolver has queried maximum number of name servers seeking to resolve: wd600.wang.com DNS:044 Resolver has processed a response to query: wd600.wang.com, Response code: 0. A-8 7. set dnsrch set nodefnames aol *** Unable to satisfy query from TCPIP configfile. TCPMON Messages: DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.com. DNS:043 Resolver has queried name server with ip address: 150.124.4. 11 in an attempt to resolve: aol.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.4. 11 in an attempt to resolve: aol.wang. DNS:043 Resolver has queried name server with ip address: 137.39.1.3 in an attempt to resolve: aol.wang.com. DNS:043 Resolver has queried name server with ip address: 137.39.1.3 in an attempt to resolve: aol.wang.com. DNS:043 Resolver has queried name server with ip address: 137.39.1.3 in an attempt to resolve: aol.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.wang.com. DNS:043 Resolver has queried name server with ip address: 150.124.52 .18 in an attempt to resolve: aol.com. DNS:022 Resolver query count has expired attempting to locate aol.wa ng.com. DNS:044 Resolver has processed a response to query: aol.wang.com, Re sponse code: 0. A-9