VS TCP/IP Services Release 1.85.03 FTP and SMTP Applications Customer Software Release Notice Copyright, Wang Laboratories, Inc., 2000 Disclaimer of Warranties and Limitation of Liabilities ______________________________________________________ The staff of Wang, 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-3 Hardware ................................................. 1-3 Software ................................................. 1-3 CHAPTER 2 ENHANCEMENTS AND SPECIAL CONSIDERATIONS Enhancements ............................................... 2-1 FTP Enhancements ......................................... 2-1 SMTP Enhancements ........................................ 2-2 Consideration and Restrictions ............................. 2-2 Retrieving VS Files to Remote Systems ...................... 2-7 Converting Files Received at the VS ........................ 2-9 CHAPTER 3 PROBLEMS CORRECTED FTP Problems Corrected ..................................... 3-1 SMTP Problems Corrected .................................... 3-2 CHAPTER 4 MEDIA CONTENTS Data Files Created During Installation and Run Time ........ 4-4 CHAPTER 5 INSTALLATION iii TABLES Table 4-1 Media Contents ............................................. 4-2 Table 4-2 Data Files Created During Install and Run Time ............. 4-4 Table 5-1 INSTALL Program Return Codes ............................... 5-3 iv PREFACE This Customer Software Release Notice (CSRN) provides information specific to Release 1.85.03 of VS TCP/IP FTP and VS TCP/IP SMTP. This notice is intended for system and networking administrators who will install and maintain the Release 1.85.03 VS TCP/IP FTP and SMTP 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. - VS TCP/IP FTP/SMTP User's Guide, Release 1.6 (715-0899B) - VS FTP API Programmer's Guide, Release 1.6 (715-5090) - VS TCP/IP Stack, Release 1.8 Customer Software Release Notice - VS TCP/IP 1.8 Enhancements (715-5292) - VS TCP/IP FTP API, Release 1.8 Customer Software Release Notice Other product names mentioned in this CSRN may be trademarks or registered trademarks of their respective companies. v CHAPTER 1 INTRODUCTION The File Transfer Protocol (FTP) and Simple Mail Transfer Protocol (SMTP) application programs are part of the VS TCP/IP Services, Release 1.85 product. FTP supports the transfer of file data throughout a TCP/IP network. This facility is provided to enable files to be transferred across a TCP/IP network to Wang and other systems that support FTP. SMTP is a protocol that supports the reliable and efficient transfer of electronic mail over TCP/IP. VS FTP allows the transfer of the following types of files from a VS system: consecutive fixed or variable record length files containing ASCII text or binary data, program files, print files, and Wang WP and WP Plus documents. All documents are automatically converted to text files before transmission to another system. When a FTP file is received on the VS system, you may want to convert it to a VS format before using the file. The VS FTP file conversion program allows you to convert and store files as follows: - A 36-Bit format file may be converted to a variable-length compressed sequential data file. - An image file may be converted to and stored as a consecutive file (maximum record size of 2048 bytes), a print file, or a program file. NOTE: Image in this sense means any file that is sent as is, without translation. It does not specifically refer to, nor exclude, a VS Wang Integrated Image System (WIIS) file. For example, a program file is best sent as an image file to the VS system. Once it is received, it is run through the conversion utility and converted to a VS program file. - An ASCII transfer type file can be converted to and stored as a consecutive file (maximum record size of 2024 bytes), or a print file. 1-1 - An ASCII record structure file can be converted to and stored as a consecutive file (maximum record size of 2024 bytes), a print file, or a program file. VS FTP is accessed through a menu-driven interface that shields the user from most variations in data links, file-storage systems, and file naming systems. This interface queues requests for file transfers, allowing users full use of their workstations while transfers are in progress. File transfer requests remain in the queue until the transfer is successful, the user deletes the request, or a status is returned with an explanation of the failed attempt. VS SMTP enables the transfer of electronic mail between systems operating in a TCP/IP network. VS SMTP uses Wang OFFICE to provide a consistent, menu-driven user interface for the exchange of mail between VS and SMTP users on other TCP/IP systems. The VS SMTP software enables Wang VS OFFICE user to send the following types of electronic mail to SMTP users on other TCP/IP systems: - Wang OFFICE memos, invitations, and phone messages - Data processing (DP) files (these should be limited to Fixed or Variable record length files containing ASCII text only) - Wang WP and WP Plus documents - Packages, which can combine memos, invitations, phone messages, documents, and DP files Both blind and freeform addressing have been implemented. A VS administrator has the capability to perform FTP and SMTP administrative functions from the same menu. These functions, accessible from the FTP/SMTP main menu, are: - Create and maintain the SMTP directory which cross references Wang Office IDs with internet IDs. - Submit and cancel the FTP background task. - Submit and cancel the SMTP background task. - Define the time zone for the date and time stamp used by SMTP. 1-2 The FTP and SMTP software packages consist of user interface programs and background tasks. The user interface allows the user to submit file transfer requests, to view the status of such requests, and to define the SMTP directory. The background tasks handle FTP requests to transfer files across the network, and SMTP requests to transfer mail to remote recipients and to receive mail for local recipients. HARDWARE AND SOFTWARE PREREQUISITES The VS FTP and SMTP software is customer installable. Before the software can operate, however, the components listed in this section must be installed. Hardware For hardware requirements, refer to the VS TCP/IP Stack, Release 1.85.00 CSRN. Software Before the VS TCP/IP FTP and SMTP software can operate the components listed in this section must be installed. - The VS TCP/IP Stack, Release 1.85 or later should be installed first on the VS system. For software requirements, refer to the VS TCP/IP Stack, Release 1.85.00 CSRN. - Copyplus, Release 3.00.00 or later is required for SMTP (note that Copyplus is needed for FTP, only if you plan on transferring WP documents) - VS OFFICE, Release 3.02.00 or later is required for SMTP, along with the following software required by VS Wang Office: - VS Directory Services, Release 3.02.00 or later - VS Package Distribution Services, Release 3.07.00 or later 1-3 CHAPTER 2 ENHANCEMENTS AND SPECIAL CONSIDERATIONS This chapter lists enhancements made to this version of the VS TCP/IP FTP and SMTP, Release 1.85 products and discusses special considerations that apply to their configuration, operation, and administration. 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 sections list the enhancements made to Release 1.85 of VS TCP/IP FTP and SMTP. FTP Enhancements Release 1.85.01 of VS TCP/IP FTP has the following enhancement: The "work file allocation" enhancement that was implemented in release 1.85.00 has been changed to the following: Users can now specify default FTP file characteristics such as number of records and record size for received FTP files. The FTP foreground program is used to set the default file record size and number of records. At the Administrative Functions screen select More Options. From the Administrative Functions More Options select FTP File Characteristics. At the FTP File Characteristics screen, the user can specify the values to be used by FTP when opening a file created during data transfer. The transfer can be initiated via API requests or through the FTP foreground program. 2-1 For files transferred in image mode (fixed record files), the file record size will be one. The New SIZEINBYTES value will specify the size of the file initially allocated for the file. In this case since the record s one, the number of records will be the size in bytes of the file. The range of this value is 1 to 16777215. For files created as a result of an ASCII mode data transfer (variable record files), the New DEFAULTRECSIZE will be the default record size of the file. The range of this value is 1 to 2024. The New SIZEINBYTES value specify the size of the file initially allocated. The number of records this initial allocation can hold would be New SIZEINBYTES divided by New DEFAULTRECSIZE. Specifying values outside the valid ranges may result in file open errors. The values specified will apply to all files created during data transfer. These values get stored in the CONTROL file. Release 1.85.00 of VS TCP/IP FTP has the following enhancements: 1. VS TCP/IP FTP and SMTP are year 2000 compliant. 2. The FTP LOG function from the FTP foreground program allows the user to page forward and backwards through the screens 3. Users can now specify FTP work file allocations for initial allocations of received FTP files. This is done through the FTP foreground program. Under Administrative Functions chose More Options. From the Administative Functions More Options chose FTP Work File Allocation, From this screen, the user can specify the values to be used by FTP when allocating disk space for any FTP work file created during data transfer. This applies only to work files, not to the file ultimately created as part of the transfer. The transfer can be initiated via API requests or through the FTP foreground program. For variable record files, the record size will be the value specified as new default, and the number of records will be the new default number of records divided by the new default record size. For fixed record files the record size will be one and the default number of records will be the new default number of records specified. These values get stored in the CONTROL file. Release 1.80.00 of VS TCP/IP FTP has the following enhancements: 1. FTP now supports Internationalization of data transfers. The installation program will prompt the user for whether this function is desired and a new menu selection from the FTP administrative menu allows for changing this selection. In addition, the FTP Convert Utility will ask if translation is also required during the conversion. See the VS TCP/IP 1.8 Enhancements Guide for information on how to customize the international defaults. 2-2 2. FTP will now allow a user who queues his request through the FTP APIs the ability to rename a file after transfer. Please see the VS TCP/IP FTP API 1.8 CSRN. 3. FTP now allows use of Dynamic Name Services (DNS) for Domain name resolution and if DNS is installed will use this service to resolve the domain names specified in FTP requests. SMTP Enhancements Release 1.85.00 of VS TCP/IP SMTP has the following enhancements: 1. VS TCP/IP SMTP is year 2000 compliant. Release 1.80.00 of VS TCP/IP SMTP has the following enhancements: 1. SMTP now needs a 4096 initiator and as such has been changed to use a class Z initiator (the same as TCP/IP). 2. SMTP now allows use of Dynamic Name Services (DNS) for Domain name resolution and if DNS is installed will use the MX records for each destination domain to determine the internet address to be used for the domain name. 3. SMTP now supports the Reply To address as required in RFC 822 _ section 4.4.3 instead of the from address field. 2-3 CONSIDERATIONS AND RESTRICTIONS This section lists restrictions and special considerations that apply to the configuration, operation, and administration of the VS TCP/IP FTP and SMTP, Release 1.85 software. The considerations are notes of special interest. The restrictions are descriptions of either hardware or software limitations. 1. When installing FTP/SMTP 1.85, the install procedure must be executed. 2. VS TCP/IP Stack, Release 1.8 and its hardware and software prerequisites must be installed prior to installing VS FTP and VS SMTP. VS Wang OFFICE and VS Directory Services must be installed prior to the installation of SMTP. 3. The administrator maintaining the SMTP directory must be a Wang OFFICE directory administrator. 4. The administrator submitting the SMTP background task must be a Wang OFFICE administrator. 5. The administrator for FTP and SMTP operations must have VS Security Administrator privileges. 6. FTP will send any size file that can be created on a VS (the VS maximum is fixed-length records of 2048 data bytes) but is limited to receiving a maximum of 2024 data bytes in a record. Any files that have a record or line length greater than 2024 bytes must be transferred to the VS using Image type (generally, at remote select binary type transfer) and File structure. The received file may then be restructured with an appropriate record length using the FTP File Conversion utility. 7. The conversion of a document from WP Plus to DP file format may not function properly if the document consists of more than approximately 800 pages. The exact limit depends upon the number of DP file records which will be produced. COPYPLUS is limited to 32767 records. 8. When the FTPLOG, FTPQUEUE, HISTORY, SMTPLOG, SMTPQUE, or SMTPDIR file needs to reorganized, the program which first detects the problem (FTPSCRN, @FTP@, or @SMTP@) renames the file, replacing the first 2 characters with "$$", in the library FTPSMTP. The reorganization is then performed by the VS COPY utility, which copies this file to the original file with the REORG option set to yes. The temporary file is then deleted. If a second program attempts to reorganize the same file, it will detect the existence of the temporary file. This causes the second program to wait for the temporary file to disappear. If the first program is cancelled prior to the successful completion of the reorganization, any of the three programs will wait forever since the $$ file still exists. 2-4 To solve this problem, first try to manually copy, with the REORG option set to Yes, the temporary file. If this fails, you will need to re-install FTP/SMTP in order to recreate the files. 9. If there is a file TCPCNFIG in library @TCPIP#A on any volume other than the TCP/IP install volume, the wrong copy of the configuration file may be opened by the FTP and SMTP programs. Backup copies of TCPCNFIG should be created using TCPREORG. If a copy is created in any other manner, the file and/or the library of the copy MUST be named differently. 10. In VS/TCPIP release 1.60, FTP history log and queue file formats changed so that any user programs that accessed these files on prior releases either directly or indirectly, will no longer function properly. 11. During installation, if an earlier release of FTP exists (specifically Release 1.00 or 1.50) on the system, the installation program will upgrade any records in the queue and log files to the Release 1.60 and greater format. This can be time consuming and can cause installation problems if insufficient free space is remaining on the disk volume. It is recommended that the log file be purged before running the install program. 12. If more than one VS TCP/IP gateway is present on a Wang OFFICE network, the SMTP dummy user accounts (created when SMTP Freeform is installed) are duplicated in the address screen of VS OFFICE. The user is unable to tell which dummy user belongs to which gateway. The system administrator may wish to use VS OFFICE Directory Services to change the display names for each dummy user in order to distinguish them. 13 If the host VS is IPL'd and the indexed files used by FTP or SMTP were not closed prior to the IPL, the file structure may be damaged in a way that is not detectable by the FTP or SMTP programs. Normally, FTP and SMTP will check to see if a file needs to be reorganized. The operating system will sometimes fail to set the bit that indicates that a file was not properly closed. If that occurs, the program cannot detect that a reorganization is required, and will log errors when accessing the file. If the log file shows access errors to any of the data files, the administrator should run VERIFY to check the validity of the file, and reorganize it if necessary. 14. The background task @FTP@ and the file FTPSCRN must be given system administrator rights during installation. If not, the following security checks will indicate that access is denied even though access should have been granted: 2-5 - VRFUSRPW - The logon id/password of a remote user trying to access the local system will be rejected as invalid. - ACTEST - A user's access to a file which could be queued locally will be denied when the program tries to open the file for transfer. 15. The INSTALL program does not update the time zone that will be used on SMTP messages; the time zone may be updated using the time zone option on the FTP/SMTP Administrative Menu. 16. The SMTP DATE: field is currently two digits instead of four and does not use a numeric time zone offset, as specified by RFC 1123, section 5.2.14. (P100026071) 17. SMTP: User names with non-ASCII characters are not mapped or translated correctly (P100026073). For example, "From: Rick NoV1 (RICK.NOEL@office.wang.com)" (The V is an e-umlaut) should be translated to "Rick Noel". RFC 822 specifies that headers should contain only ASCII. 18. FTP conversion of variable length ASCII text files into fixed-record length files may have unpredictable results if some text lines are longer than the specified record size. 19. Transfer of a VS Print file to some systems as an ASCII FILE may result in unpredictable behavior if the file contains Wang extended characters that are not part of the NVT ASCII character set (for example, e accent grave). The file may be transferred as an IMAGE FILE but the received text will not be very useful since all end-of-line information will be lost in the conversion. 20. The following commands were supported in release 1.6 and greater of VS TCP/IP FTP: USER PASS ACCT A VS only implementation PASV SITE A VS only implementation PORT MODE STREAM & BLOCK for VS only ALLO STRU FILE & RECORD only STOR TYPE ASCII & IMAGE only RETR QUIT ABOR 2-6 The following additional commands are supported in release 1.7 and greater of VS TCP/IP FTP: NLIST CWD PWD LIST CDUP RNFR RNTO DEL PUT, GET, MPUT, and MGET are not FTP commands so they do not appear in the list above. However PUT and GET generate the FTP STOR and RETR commands respectively which are supported. MPUT and MGET work in release 1.7 or greater in the following manner. MGET MPUT FTP VS FTP VS cd volume.library cd volume.library mget * mput path Enter Y or N for each file Enter y or n for each file 21. FTP will now work with LAN Workplace under Microsoft Windows, since the commands listed in #19 are now implmented. 22. Explicit library creation using the CWD command is not supported in VS FTP. Libraries may only be created implicitly when the volume, library and file name are supplied. 23. SMTP will now send records for the actual length of the record (not to exceed the maximum of 1024) instead of 80 bytes. 24. VS SMTP will not send error messages due to unsupported Office 3.0 functions (i.e. distribution lists) or for X.400 packages. It will remove the unsupported mail type from the package, and will transmit the remainder of the package. 25. Print files can now be included in a Wang OFFICE package as a DP file. 26. VS FTP users have reported a problem when transferring large files to an RS 6000. TCPMON displays the following error messages: RETRANSMIT LIMIT EXCEEDED CONNECTION TIMED OUT REMOTE HOST NO LONGER RESPONDING The RS 6000 was not implementing the window parameter, thus the window never decreased and the VS kept sending the 16K buffers until eventually the RS 6000 could not keep up. The RS 6000 had the window size set to 16K. When the window size was decreased to 4K, the problem did not occur. 2-7 To check the size of this window on the RS6000 you can use the following command(issued at the RS 6000): no -a. The response to this command will show the default settings in network options. Look at the following parameters: TCP SENDSPACE=16,384 _ TCP RECVSPACE=16,384 _ You can adjust these parameters by issuing the following commands: no -o tcp sendspace=4096 _ no -o tcp recvspace=4096 _ NOTE: You must run TCP STOP then TCP START to activate the change on the RS 6000. 27. SMTP now needs a 4096 initiator and as such has been changed to use a class Z initiator (the same as TCP/IP). 28. SMTP now supports the Reply To address as required in RFC 822 _ section 4.4.3 instead of the from address field. 29. SMTP cannot handle DP files whose record length is greater than 1024 characters. 30. SMTP does not support certain Wang OFFICE 3.0 features (SMTP will return error message stating "Invalid Mail Item Type 1090). Reply To Recipients is not supported nor is the external distribution list. 31. When a file transfer is received inbound to the VS, the default is not compressed. 32. Some UNIX implementations begin a multiline response with a reply message followed by a hyphen (for example, 230-) but before completing the multiline response, they send a "226 transfer complete message". This is a violation of the protocol, and the VS will continue to wait for the multiline response to complete. It will not recognize the 226 message. The transfer stays in progress forever, and the VS does not close the data or the control port. 33. Problems may be experienced when transmitting a file to a remote system which does not have enough space for the received file. 2-8 Retrieving VS Files to Remote Systems Remote users of the VS FTP, Release 1.85 product should be aware of the following considerations: The VS file system is based on a 3-level hierarchy of Volume, Library and File. Node names are limited to the upper-case alphanumeric character set plus the special characters $, @, and # (A-Z, 0-9, $, @, #). To store a file on, or retrieve a file from a VS system, that system's pathname must always be fully qualified and entered in the format 'VOLUME.LIBRARY.FILE'. For example, to copy a file from a (typical) UNIX system to the VS, the FTP command put file VOLUME.LIBRARY.FILE must be entered. Note that file names with DOS or Unix extensions (e.g. test.exe) must be renamed in the process of transferring the file, because the VS does not support file name extensions. Unpredictable results can occur if this is not done. For example: put test.c VOLUME.LIBRARY.test To retrieve a WP document from a VS system, the shadow volume 'WPVOL' is used. Document IDs are then mapped into a VS library and file as follows: - The filename has a prefix of 'DOCMNT' followed by the single alphabetic characters if it is uppercase. If it is lowercase, use the uppercase character twice (VS filenames are case insensitive). For example, to retrieve document 1000a from a VS system, enter the FTP command get WPVOL.DOCMNTAA.1000 file If the volume name is known, this can be specified, but there is no advantage to doing so. For example, if WPLIB 'a' is on volume WORK, then the command get WORK.DOCMNTAA.1000 file is also valid. To retrieve a WP Plus document from a VS system, the shadow volume 'WPPVOL' is used. The FTP command to retrieve document 57 from library 'MEMOS' would be get WPPVOL.MEMOS.57 Note that the full name AF000057 also may be specified. 2-9 If the document has a password, this must be sent with an 'ACCT' command before the document can be retrieved. On many systems this will require use of the 'QUOTE' directive. For example, to retrieve document 1000a with a password of 'mumble', the FTP user must enter the following commands: quote ACCT mumble get WPVOL.DOCMNTAA.1000 file 2-10 Converting Files Received at the VS The FTP File Conversion screen may be initially confusing to the new VS FTP user. With this release FTP creates two types of received files. If the file is sent to the VS with TYPE I and STRU F (usually specify BINARY at the remote system), it is stored as fixed length records with a record length of 1 byte. In all other cases it is stored as variable length records with a maximum record length of 2024 bytes. The FTP conversion function has been updated to handle both of these input file structures. Conversion to a VS IMAGE (i.e. WIIS image) file should no longer be required unless the file was incorrectly transferred using the STRU R (i.e. record structure). In this case, you should use conversion to a source/consecutive file with output length of 1. Wang Integrated Image System (WIIS) image files are a special case of DP fixed-length consecutive record files, most commonly with a record size of 1 byte. Conversion is not required if they are transferred with IMAGE type and FILE structure. The 'image' conversion should not be used with VS FTP, Release 1.80. This conversion option has been retained for purposes of compatibility with files previously received by an earlier version of VS FTP. In some cases, it may be preferable to create WIIS image files with a record length of 2048 bytes. This can only be done if the input file is of the fixed length 1 byte record format. In this case, you should use conversion to a source/consecutive file with output length of 2048. Program source code files that are to be stored on the VS should be transferred using TYPE A (ASCII, NON PRINT - the default setting) and then converted to a source/consecutive file with output length of at least the size of the longest text line, the records will be padded using the space character to the specified output length. Note that the file should be 'de-tabbed' before it is transferred, there is no provision in FTP to convey the original TAB stop information with the file and the tab stops will not be translated. If a file has been inadvertently transferred using the wrong structure, you may be able to restructure it by first converting it to source/consecutive with an output length of 1, thus removing the original record size information, and then converting it again to the desired record type. The 36-bit conversion is rarely required. On a machine with 36-bit words, two words are generally assembled into nine bytes. This conversion takes these nine bytes and reduces them to eight bytes by dropping the rightmost four bits of each of the original 36 bits. The result should be binary data that is usable on the 32-bit machine. 2-11 Conversion to other file types not discussed in this section requires a user to provide his own conversion program or make use of other VS utilities. This limitation includes, but is not limited to, WP and WP Plus documents (which may be converted using WPCOPY or COPYPLUS). 2-12 CHAPTER 3 PROBLEMS CORRECTED The following problems were corrected in VS FTP and SMTP, respectively: FTP PROBLEMS CORRECTED The following problem was corrected in version 1.85.03 of FTP: The NLST and LIST commands have been corrected to send the correctly formatted date information. The following problem was corrected in version 1.85.02 of FTP: The RENAME function has been corrected so that subsequent pathnames will no longer be invalid. The following problems were corrected in version 1.85.00 of FTP: M200023666 A 'last' function and a 'prev' function have been added to FTP for displaying the FTP log. M200023660 Transferring files in record mode could result in a write error, file status = 96. M200023636 NLIST command would result in a write error, file status = 96. no PTR FTP would fail on a write error, file status = 60. M800027316 FTP would send the account field up to the first blank. FTP was changed to send the account field up to the first double blank. M800027415 FTP would log a transfer as successful if FTP received a reply code of '552'. '552' is now treated as an error code. The following problems were corrected in version 1.80.00 of FTP: Internal No local errors were being reported in the FTP Log. M800026785 FTP files sent from an HP to a VS are stored incorrectly if the file contains less than 80 byte records. M200022686 When adding a user to the SMTP directory the FTPSCRN program returns with an 'Error finding host name -retry' message. M200023331 Change made to stop installation if the CONTROL file is already opened. 3-1 M800026465 FTP ignores the '150' message and processes the '226' message if messages are in same buffer. M200023255 When using FTP API and specifying IP addresses, consecutive requests to the same system could be delayed. M200023143 LIST command could display an incorrect volume name. M800023309 Stack overflow task crash. M200022904 Sending a print file with options Image/File resulted in corrupted data. M200023031 FTP user not able to retrieve a zero byte file. M200022765 When the data session is closed, FTP leaves the session id in the SCB until the control session closed. This could cause confusion as the session id is available. M200022815, M200023593 -- LIST command releases buffers when through with them. M200022357 Corrected block length on the last block in a file during transfers. M200022251 Allow for acceptable errors from the open function. M200021931 Occasionally FTP would lose the last record of a file being transferred to the VS. M410012066 When storing files on the VS, after 16 errors had occurred an incorrect error message would be used. M800024577 When transferring a print file from the VS, print control characters on a blank line were being sent to the remote system. M200021614 Able to retrieve a DP file in record mode. M200021738 PC04 task crash. M200021798 Sending a file from SCO to VS, an extra hex'0A' was being placed into the file. M200021759 A message is now sent to the network logger when the FTPLOG reaches 13 extents. M800023485 Attempting to retrieve a WP documnent results in a response code of 451 being sent. M200021733 Following a 'File Status 60 - Write Failed', a response of 250 requested file action okay was being sent. M200021665 Certain DP files were transfered incorrectly. M410011936, M800024096 -- Buffer allocation exhausted. M800024097, M410011935 -- When a file with record length of two are sent, an additional two random characters were sent. Internal A CLIF related module CLEVT 3.00.25 was linked into FTP. M410011739 When a response of 502 is received from an ALLOC command, treat it as a 202 response and continue with the transfer. M410011496 A new version of the Connection Layer Interface (CLIF - 3.00.31) was linked into FTP. M800023485 When unable to gain file access a control block was not being released. M410011331 The logic dealing with multi-line responses was modified. 3-2 SMTP PROBLEMS CORRECTED The following problems are corrected in version 01.80.00 of SMTP: M200023502 SMTP has problems when queue exceeds the extent limit. M410012244 Mail item sent continually if user is not known to UNIX host system. Internal SMTP log files now have unique names for each SMTP session instead of deleting the current log file. M410012075 When a user attempts to reply to an SMTP user that was auto added, whose name contains quotes, a PC05 would result. M200021662 The SMTP error message when the record size of a DP file exceeds 1024 characters now indicates an invalid mail item type and a log message has been added to indicate the record length was invalid. G200021643 A new version of the Connection Layer Interface (CLIF - 3.00.31) and TCPAPIs were linked into SMTP. G410011808, M410011793 -- The logic dealing with multi-line responses was modified. 3-3 CHAPTER 4 MEDIA CONTENTS This chapter provides a list of the files contained in Release 1.85.03 of the VS FTP and SMTP products. The software is available on the following media types: Designation Media Type (-7) 9-track tape (-G) Streamer cartridge (-Q) 4mm dat Table 4-1 lists the media contents. The release tape contains several libraries: FTPSMTP which contains the body of the release, and SMTPFFRM which contains the freeform addressing code which must reside on each system from which freeform addressing is to be available. In the table, Protection Class represents the value of the file on the tape. Changes to the protection classes of these files may affect the operational characterstics of the FTP and SMTP applications. To verify the version numbers, run DISPLAY and specify the appropriate file, library, and volume. The version number and date will be visible in the first record displayed. 4-1 Table 4-1. Media Contents File Version Description -------------------------------------------------------------------------- Library = FTPSMTP @FTP@ 01.85.03 FTP server program @SMTP@ 01.85.00 SMTP server program CANFTP 01.85.00 Program to quiesce the FTP server CANSMTP 01.85.00 Program to quiesce the SMTP server ERRORMSG 01.85.00 Error Message file FCANFTP 01.85.00 Program to cancel the FTP server FCANSMTP 01.85.00 Program to cancel the SMTP server FINDID1 01.85.00 Used internally by FTPSCRN FTPCONV 01.85.00 FTP file conversion program FTPLCNTL 01.85.00 FTP logging control procedure FTPSCREN 01.85.01 Screen file for FTPSCRN FTPSCRN 01.85.00 FTP/SMTP admin program HAUSFRAU 01.85.00 SMTP directory housekeeping program INSTALL 01.85.00 FTP/SMTP installation program INTRFTP None FTP International File INTRFTPS None FTP International File source LDWOSTRS 01.85.00 Used internally by FTPSCRN PERSONAL None Optional personality file. NOTE: This file can be loaded to the user's workstation to avoid seeing underlined characters as some other character for inbound mail. -------------------------------------------------------------------------- (continued) 4-2 Table 4-1. Media Contents (continued) File Version Description -------------------------------------------------------------------------- SMTPDUPD 01.85.00 Program to update the SMTP directory SUBFTP 01.85.00 Program to submit the FTP server SUBHFRAU 01.85.00 Program to submit the SMTP housekeeper SUBSMTP 01.85.00 Program to submit the SMTP server Library = SMTPFFRM FFSCRN 01.85.00 Screen file for SPFFORM INSTALL 01.85.00 Freeform addressing installation program SPFFORM 01.85.00 Freeform addressing user interface Library = VSSUBS MESSAGE 06.40.09 MESSAGE USERSUB required by FTPLCNTL Library = CSRNLIB FTPSMTP 01.85.03 VS TCP/IP FTP/SMTP CSRN 1.85.03 -------------------------------------------------------------------------- 4-3 Data Files Created During Installation and Run Time Table 4-2 lists files created in the library FTPSMTP on the install volume, except where noted. Some are created during installation; others are created at run time as needed. Table 4-2. Data Files Created During Install and Run Time File Library Volume Creation time -------------------------------------------------------------------------- CONTROL FTPSMTP system volume installation FTPLOG FTPSMTP installed volume runtime FTPQUEUE FTPSMTP installed volume installation HISTDEL FTPSMTP installed volume run time/after history purge HISTOLD FTPSMTP installed volume run time (purge log file) HISTORY FTPSMTP installed volume installation SMTPDIR FTPSMTP installed volume installation SMTPFFL SMTPFFRM installed volume run time (Freeform lists saved) SMTPLOG FTPSMTP installed volume run time SMTPQUE FTPSMTP installed volume installation CONVxxxx FTPSMTP installed volume run time @xxxxuid @TCPIPB work volume run time CONFIG SMTPFFRM installed volume installation ------------------------------------------------------------------------- Notes: FTPLOG and SMTPLOG are the background running log files for FTP and SMTP, respectively. The CONFIG file is created in the library SMTPFFRM at install time. It must be created before the library is moved to other systems for freeform installation. ------------------------------------------------------------------------- 4-4 CHAPTER 5 INSTALLATION The VS TCP/IP FTP and SMTP products are customer installable. This chapter provides you with information about the software installation. The installer chooses the volume on which to place the FTP/SMTP programs and files for installation, generally the TCP/IP volume. The following steps must be taken in order to install the software: NOTE: To install, you must be both a VS security administrator, and a Wang Office/Directory Services administrator on the system you are installing to. TCP/IP, FTP, and SMTP should not be running. 1. VS TCP/IP Stack, Release 1.85.00 or higher must already be installed on the target system. 2. Log on the system as a VS Security Administrator and a Wang OFFICE/Directory Services Administrator. 3. Mount the release tape and set the following values based on whether you received the VS TCP/IP 1.85 Upgrade or the VS TCP/IP Services package (check the tape label): Set Volume = UPGRD or SRVCE Label = NL (for tape) or SL (for disk) Mode = EX 4. Run BACKUP with Function = RESTORE to copy the libraries from the release media to the volume from which the FTP/SMTP software is to run. If this is an upgrade, specify DUPFILES=SCRATCH and you may wish to backup the existing libraries. 5. When the procedure completes, dismount the input volume. 6. Run INSTALL from library FTPSMTP on the selected disk. 5-1 7. The displayed screen requests the name of the volume to which the software has been copied, either the local time zone or differential from Greenwich time, and whether international translation will be required. Select either PF5, to install only FTP, or PF8, to install both FTP and SMTP. If this is the gateway system to the TCP/IP network and Wang OFFICE is installed, then you must select PF8 to install SMTP. PF5 is provided for those installations which do not wish to use the SMTP mail system and for installing FTP on additional systems within the local network. If you chose to install SMTP, a second screen is displayed that requests the blind addressing delimiter field, the blind addressing descriptor field, and the freeform addressing title. These appear with appropriate defaults, but may be modified. The two blind addressing values are required by any users doing blind addressing; the freeform title is used internally when freeform addressing is used. The INSTALL program generates a procedure, called FTP, in library @SYSTEM@ on the system volume. This procedure will run the user interface program. The install program also creates the data files FTPQUEUE, SMTPQUE (if SMTP installation is selected), and HISTORY. If one of the files FTPQUEUE, or HISTORY already exists from a previous installation, then these files will not be recreated. However, if the previous installation is a pre-1.60 version, then these files will be renamed to QUEUEX and HISTORYX and the records upgraded to 1.60 format. If you chose to install SMTP, the file SMTPQUE is created, and a file called CONFIG is created in the library SMTPFFRM. This file is used when installing freeform addressing on other systems. Also, the SMTP application is automatically added to the Wang OFFICE directory, and freeform addressing for SMTP is installed on the local system. The INSTALL program will exit with a return code if errors occurred during the installation. Table 5-1 lists the possible return codes and their meanings. 5-2 Table 5-1. INSTALL Program Return Codes Return Code Meaning ----------------------------------------------------------------- 1 Fatal User running the install is not a VS security administrator. 2 Warning The freeform addressing information could not be installed in Wang OFFICE. 3 Fatal Wang Office has not been installed. 4 Fatal Can't add the SMTP application to the Wang Office directory. 5 Fatal Can't write needed information to the SMTP control file. 6 Fatal Can't open FTP/SMTP screens file (FTPSCREN). 7 Fatal Can't add the SMTP organization to the Wang Office directory. 8 Fatal Can't add dummy user for blind addressing to the Wang Office directory. 80 Fatal User terminated installation using PF16 304 Warning Can't set security classes on some of the files. 308 Fatal Can't set security classes on some of the files. ----------------------------------------------------------------- Errors resulting in some of the error codes in Table 5-1 can be corrected by the user, and the INSTALL program re-executed. These error codes are re-listed below, this time with a correcting action. 5-3 Return Code 4 Can't add the SMTP application to the Wang OFFICE directory. Run Wang OFFICE, and go to the Directory Administration menu. Select Applications. Select Add an Application. Fill in the data fields as follows: Description: SMTP Simple Mail Xfer Action: Notify Name: SMTP Run Name: $SMTP Notification: No File: @SMTP@ ITMU: SMTP Library: FTPSMTP Volume: the install volume Auto Confirmation: Yes Class: Y Rcv. Route Pkg: No Status: Run Password: Default Reference Info: as displayed during INSTALL Return Code 7 Can't add the SMTP organization to the Wang Office directory. Run Wang OFFICE, and go to the Directory Administration menu. Select 'Organizations', then select 'Add an Organization'. Fill in the screen as follows: Organization name: SMTP Description: SMTP Simple Mail Xfer Return Code 8 Can't add dummy user for blind addressing to the Wang Office directory. Run Wang OFFICE and go to the Directory Administration menu. Select 'Users', then select 'People', then select 'Add a Person'. The default field values on each of the several screens displayed should be used, except for the following: First screen: Last name: SMTP Organization: SMTP First name: SMTP Display name: SMTP blind address recip Mailbox screen: Mailbox type: Application Application name: SMTP When the necessary information has been added, run the INSTALL program in library FTPSMTP on the install volume. This is the installation program used by FTPINST, so follow the directions regarding installation. 5-4 8. After the primary SMTP installation is complete, freeform addressing for SMTP can be installed on other VS systems in the network. To install freeform addressing on other systems, you must copy the entire library SMTPFFRM from the primary SMTP installation system to each of the other systems, placing it on the same volume as the main Wang OFFICE library, WOLIB. NOTE: If the file SMTPFFL exists in the SMTPFFRM library on another system, do not copy this file from the primary SMTP installation system. 9. Wang OFFICE must be installed before attempting to install freeform addressing. With OFFICE installed, run INSTALL in the library SMTPFFRM. No screen display is done by this freeform addressing install program unless an error occurs. 10. Define the POSTMASTER, the administrator who is to be responsible for handling SMTP administrative messages. Run FTPSCRN in library FTPSMTP on the install volume and select Administrator Services from the FTP/SMTP Main Menu. Select SMTP Directory, then Modify SMTP Directory, then Add New User. Select the person from the Wang OFFICE directory who is to be the POSTMASTER. Enter POSTMASTER as the DDN name and the local domain name as the local domain. The file "SMTPDIR" is created at this time. If the file exists already, it will not be destroyed. 11. Add SMTP recipients to the SMTP directory. All recipients must be in the Wang OFFICE directory prior to being added to the SMTP directory. Those recipients that are accessible solely through SMTP should have application mailboxes of SMTP; those who receive their mail through Wang OFFICE should have interactive mailboxes. Wang OFFICE users who will use SMTP only occasionally need not be added to the directory; people who use SMTP often should be added. User access through the directory is more efficient than user access with SMTP-generated user names. The @FTP@ server must run in a background initiator that has at least 2048 KB of modifiable data area (MDA). The @SMTP@ server must run in a background initiator that has at least 4096 KB of modifiable data area. The housekeeping task can run in a process with 1024 KB of MDA. The FTP and SMTP administrative function to submit these background tasks will do so to class Y and Z initiators respectively. Adequate initiators must exist with appropriate class and MDA size to assure task slots in which @FTP@ and @SMTP@ can run. 5-5 To create an initiator 1. At a VS operator's console, select PF7 (Background Tasks) 2. At the displayed screen, place the cursor on an empty initiator (titled 'Available'), or on a background task if no empty initiators are available. Press PF11 (Initiators). 3. At the Initiator menu, choose PF 7 (Create Initiator). 4. At the initiator data screen, set the Class to 'Y' for FTP, 'Z' for SMTP. Set the Dump parameter to either 'Y' or 'N'. Set the MDA parameter to 2048 for FTP and 4096 for SMTP, then press ENTER to create the initiator. 5-6