ECO NUMBER: DSNLINKC012 ----------- PRODUCT: DSNlink for VMS -------- UPDATED PRODUCT: DSNlink for VMS 1.2 ---------------- APPRX BLCK SIZE: 2754 ---------------- ____________________________________________________ DSNlink Version 1.2C ECO Kit for OpenVMS Release Notes This document contains release information concerning the DSNlink Version 1.2C ECO Kit for OpenVMS software. Revision/Update Information: This document supersedes all previous versions. Operating System and Version: OpenVMS AXP[TM] Version 1.0 or greater OpenVMS VAX Version 5.2 or greater Software Version: DSNlink Version 1.2C ECO Kit for OpenVMS. ________________________________________________________________ October 1993 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Copyright © Digital Equipment Corporation 1993 Printed in U.S.A. All Rights Reserved. Alpha AXP, AXP, DEC, DECnet, DECserver, DECsystem, Digital, OpenVMS, VAX, VAX DOCUMENT, VMScluster, VMS, VT, VTX, and the DIGITAL logo are trademarks of Digital Equipment Corporation: This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... v 1 Installing the Kit 1.1 Kit Contents..................................... 1-1 1.2 New ECOs in This Kit............................. 1-1 1.3 Prerequisites.................................... 1-1 1.4 Installation Procedure........................... 1-2 1.5 Sample Installation.............................. 1-2 2 Messages During Installation 2.1 Repeating the Installation....................... 2-1 2.2 Applying the Kit on a DAN Node................... 2-1 2.3 No DSNlink Logical Names......................... 2-2 2.4 You Do Not Have the Prerequisite Version of DSNlink.......................................... 2-2 3 Post-Installation Actions 4 ECOs Contained in This Kit Examples 1-1 Sample Installation ........................... 1-2 iii _________________________________________________________________ Preface DSNlink Version 1.2C ECO Kit for OpenVMS software corrects certain reported problems with DSNlink Version 1.2 for OpenVMS software. These problems are listed as engineering change orders (ECOs) for tracking purposes. This document contains the following information about this kit: o Chapter 1 - The kit contents - A brief list of the new ECOs - Prerequisites - Installation procedures - A sample installation o Chapter 2-Possible messages during installation o Chapter 3-Post-installation procedures o Chapter 4-Descriptions of the ECOs and the corrected problems This document is intended to supplement existing DSNlink Version 1.2 for OpenVMS documentation. v 1 _________________________________________________________________ Installing the Kit 1.1 Kit Contents This kit includes the engineering change orders (ECOs) in the previous patch kits. Therefore, this kit installs all the new ECOs, as well as those in the previous DSNlink Version 1.2A and Version 1.2B kits. 1.2 New ECOs in This Kit The following ECOs are the additions to the DSNlink Version 1.2B kit that are new in this kit: o Problem 2 in B15 (Duplicate File Copies) o B129 (DSN COPY Does Not Detect File Node Names Correctly) o B172 (DSN Mail Subprocesses Loops) o B182 (HASH_SHIFT Not Initialized in DSN$NET_ COMPRESS.B32) o B191 (COPY Requeue Fails on Unpopulated Files) o B195 (COPY Requeue Fails When Partial File Is Deleted) For descriptions of the ECOs, see Chapter 4. 1.3 Prerequisites These are the prerequisites to installing this kit: o Be sure DSNlink Version 1.2 for OpenVMS is installed and running before installing this ECO kit. You can install this kit if the DSNlink version number is Version 1.2, Version 1.2A, or Version 1.2B. Use the DSN SHOW VERSION command to check the installed version. Installing the Kit 1-1 Installing the Kit 1.3 Prerequisites o Be sure all DSNlink logical names are present. To check the logical names, enter this command: $SHOW LOG/TABLE=DSN* If you see definitions of logical names, you can proceed with the installation. If no definitions are present, enter the following command from a privileged account: $ @SYS$STARTUP:DSN$STARTUP If the logical names are not present when you start the installation, the procedure stops and an error message is displayed on your terminal. For more information, see Chapter 2. 1.4 Installation Procedure Use the following procedure to install the ECO kit: 1. Note any ACLs (access control lists) you placed on the current versions of the DSNlink files. The kit replaces the files shown in Chapter 3, but does not preserve your ACLs. 2. Install this ECO kit with the VMSINSTAL command procedure. This is described in Chapter 3 of the VMS System Manager's Manual (AA-LA00A-TE). 3. Shut down and restart DSNlink immediately after installing this kit. During the kit installation, you are asked if you wish to have the installation procedure do this for you. Digital recommends you answer "Yes" to this prompt. Improper operation of DSNlink may occur if you do not shut down and restart DSNlink. 1.5 Sample Installation Here is a sample installation of this ECO kit: Example 1-1 Sample Installation (continued on next page) 1-2 Installing the Kit Installing the Kit 1.5 Sample Installation Example 1-1 (Cont.) Sample Installation Username: SYSTEM Password: . . . $ SET DEFAULT SYS$UPDATE: $ @SYS$UPDATE:VMSINSTAL VAX/VMS Software Product Installation Procedure V5.5-1 It is 21-SEP-1993 at 12:22. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: DSN$NETWORK * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? y * Where will the distribution volumes be mounted: dua1:[system] Enter the products to be processed from the first distribution volume set. * Products: DSNLINK V1.2C The following products will be processed: DSNLINK V1.2C Beginning installation of DSNLINK V1.2C at 12:31 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This is the DSNlink V1.2C ECO Kit DSNlink will be updated to DSNlink V1.2C at the completion of this installation. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ (continued on next page) Installing the Kit 1-3 Installing the Kit 1.5 Sample Installation Example 1-1 (Cont.) Sample Installation %DSNLINKC-I-NEWFILIMG, Providing updated files and images... %DSNLINKC-I-NEWSTARTUP, Creating your new DSN$STARTUP.COM (USA variant)... %DSNLINKC-I-SECFILDIR, Securing files and directories... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... In order for the V1.2C fixes and updates to take effect, DSNlink should be shut down and restarted. * Do you want to shut down and restart DSNlink now [Yes]? y DSNlink V1.2C for OpenVMS VAX Copyright (c) 1989, 1992 by Digital Equipment Corporation Digital Equipment Corporation Proprietary Service Tool All Rights Reserved DSNlink network process is shutting down Job DSN$STARTUP (queue SYS$BATCH, entry 128) started on SYS$BATCH DSNlink has just been shut down, and the startup procedure has been submitted as a batch job to SYS$BATCH. DSNlink should be running again soon. If you do not have a SYS$BATCH queue on this node, please restart DSNlink at your earliest convenience. Installation of DSNLINKC V1.2 completed at 12:37 Enter the products to be processed from the next distribution volume set. * Products: Ctrl/Z Pressing Ctrl/Z ends the installation procedure. 1-4 Installing the Kit 2 _________________________________________________________________ Messages During Installation The following are messages you see under the specified conditions. 2.1 Repeating the Installation If you repeat the kit installation, you see the following message: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! This collection of fixes and updates has *already* been applied to this system. However, this kit will continue to reinstall the fixes and updates, replacing the already replaced files and images. Although unnecessary, no harm will occur by doing this reinstallation. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2.2 Applying the Kit on a DAN Node If you apply this kit to a DSNlink Applications Node (DAN), you see the following message: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The installation has determined that you are installing this kit on a DSNlink Applications Node (DAN). If this node shares a common system disk with your DSNlink Communications Node (DCN), you do NOT need to install the kit on this node. You only need to install it on the DCN. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ A prompt asks if you want to continue. Messages During Installation 2-1 Messages During Installation 2.3 No DSNlink Logical Names 2.3 No DSNlink Logical Names If there are no DSNlink logical names defined on the system, you see this message: *************************************************************** This is the DSNlink V1.2C ECO Kit All DSNlink logicals must be present on your system before this kit can be installed. Please restart DSNlink to create these logicals. From a privileged account, use the command: $ @SYS$STARTUP:DSN$STARTUP Then reinstall this patch kit. *************************************************************** 2.4 You Do Not Have the Prerequisite Version of DSNlink If you try to install on a system running a version of DSNlink other than Version 1.2, 1.2A, or 1.2B, you see this message: *************************************************************** This is the DSNLINK V1.2C kit This collection of fixes and updates may only be applied to systems running DSNlink V1.2, V1.2A or V1.2B. DSNlink will be updated to DSNlink V1.2C at the completion of this installation. *************************************************************** 2-2 Messages During Installation 3 _________________________________________________________________ Post-Installation Actions After you install this kit, do the following: 1. Review the changes made to DSN$STARTUP.COM to ensure that your specific customizations, if any, have been preserved. 2. This kit does not purge any of the files that it replaces. When you feel comfortable with the new images provided by this kit, you may purge old versions of the files. The following files are replaced by this kit: SYS$LIBRARY:DSN$SHARE.EXE SYS$LIBRARY:DSN$ITSSHR.EXE SYS$LIBRARY:DSN$COPYSHR.EXE SYS$LIBRARY:DSN$DECNET_SHARE.EXE SYS$LIBRARY:DSN_MAILSHR.EXE SYS$SYSTEM:DSN$MAIN.EXE SYS$SYSTEM:DSN$NETWORK.EXE SYS$SYSTEM:DSN$COPY_QUEUE.COM SYS$SYSTEM:DSN$COPY_SERVER.COM SYS$SYSTEM:DSN$START_VTX.COM SYS$MANAGER:DSN$FORMAT_TRANSACTION_LOG.COM SYS$STARTUP:DSN$STARTUP.COM You get a new DSN$STARTUP.COM file only if you apply the kit to a system running DSNlink Version 1.2 or 1.2A. If your system has DSNlink Version 1.2B or 1.2C, no new DSN$STARTUP.COM is created, and DSNlink continues to use the current file. Post-Installation Actions 3-1 Post-Installation Actions 3. Note that the installation does not preserve the access control lists (ACLs) you place on files. If you applied ACLs to any files that are replaced by the kit installation, you need to reapply the ACLs to the new files. 3-2 Post-Installation Actions 4 _________________________________________________________________ ECOs Contained in This Kit The following fixes and updates are provided by this kit: o ECO B11- ITS_SHOW_DATABASE/FULL_Synchronization_Loss It was possible for an ITS SHOW DATABASE/FULL command to cause the ITS server on the host to lose synchronization with the ITS client causing the eventual abort of the client. This kit corrects this problem. o ECO B14- Null_Log_File_Created_When_DSNlink_Starts Empty files named ".LOG" (no file name, just the .LOG file type) were created whenever the DSNlink modem transport was started. This kit corrects this problem. o ECO B15- Duplicate_File_Copies Problem 1: Occasionally, a File Copy or Problem Submission job successfully delivered the information more than once. This kit correctly detects and recovers from this situation. Problem 2: A file copy was repeated unnecessarily if the volume cluster size of the sending and receiving disks was not the same. When a file copy was requeued, the sender and receiver compared allocated block sizes of the files. If the sizes did not agree, the File Copy application assumed the file was bad or corrupted and started the transfer again. This kit detects and avoids this situation. o ECO B16a- COPY_Gives_SYSTEM-F-BADPARAM_and_Keeps_Requeuing It was possible for a File Copy or Problem Submission job to get a "Bad Parameter" error and then requeue. Each attempt to transfer the information resulted in this status until the job's requeue limit was reached. This kit correctly recovers from this situation. ECOs Contained in This Kit 4-1 ECOs Contained in This Kit o ECO B16b- DSN_COPY_Leaving_Files_with_FAT$L_EFBLK_Field Set_to_Zero When a DSN COPY job failed leaving a partially copied file, and if the actual amount copied was a multiple of 32 blocks, the file header of the file on the receiving side could get its end-of-file block incorrectly set upon the next retry of the job. This caused the job to restart from the very first block because another part of the code detected the corruption and began recovery. This kit corrects this problem. o ECO B18- ITS_PRINT_to_Nonexistent_Queue_Causes_ACCVIOs If the ITS PRINT command was entered and the destination print queue did not exist, ITS aborted with an access violation. This kit corrects this problem. o ECO B19- ITS_SHOW_DATABASE_XXX_Errant_Byte Versions of ITS clients prior to Version 1.2 could see a nonessential character, such as an asterisk or a percent sign, preceding a database description when a SHOW DATABASE XXX command was done. This kit corrects this problem in the ITS server. o ECO B50- Transaction_Log_File_Closed_by_Nonprivileged_Users If a user without sufficient privileges to access the transaction log file ran a DSNlink application, an error occurred when DSNlink tried to close the log file when the user exited the application. A security alarm was also tripped if security auditing was enabled for failed accesses. This kit corrects this problem. o ECO B51- DSN$FORMAT_TRANSACTION_LOG_Loops_Indefinitely The DSNlink Transaction Log File Formatter utility, DSN$FORMAT_TRANSACTION_LOG.COM, could enter a state when it looped indefinitely, displaying DCL errors. This kit corrects this problem. o ECO B58- X.25_Log_Files_Not_in_DSN$LOGS The application server log files for incoming DSNlink X.25 connections had been written to the SYS$SYSTEM directory. This kit has the files placed in the DSN$LOGS directory. 4-2 ECOs Contained in This Kit ECOs Contained in This Kit o ECO B61- No_Termination_Status_for_DECnet_and_X.25_Transports DSNlink sites that use the DSNlink DECnet or DSNlink X.25 transport did not receive the remote system's termination status reason if the remote site aborted the connection. This kit corrects this problem. o ECO B62- DSN$FORMAT_TRANSACTION_LOG.COM_Did_Not Clean_Up_on_Ctrl/Y The DSNlink Transaction Log File Formatter utility, DSN$FORMAT_TRANSACTION_LOG.COM, did not correctly clean up after itself when it was aborted with a Ctrl/Y. This kit corrects this problem. o ECO B65- Deferred_Hangup_Was_10_Seconds,_Should_Be_90_Seconds The deferred hangup time for DSNlink file copies across the DSNlink modem transport has been increased to 1½ minutes. This generally will improve the timeliness of responses to problem submissions. o ECO B66- Failure_to_Recognize_Deferred_Hangups_on_Lines If an application link terminated for an incoming connection that specified a deferred hangup time, and no other coexistent application links were known to the line manager, then the line hangup deferral occurred but the line manager did not recognize this state, causing the next outgoing connect attempt to select an alternate line. Although this problem is only apparent on host nodes, it could be forced to occur on nonhost nodes. This kit corrects this problem. o ECO B72- SAVE/ALL_Done_Twice_Causes_VTX_Protocol_Error When the SAVE/ALL command was done twice in DSN VTX, a VTX protocol error could occur. This kit corrects this problem. o ECO B102- DSN_COPY_Creates_New_File_Version_if_It_Fails This problem was a side effect of the problem corrected by ECO B16b. o ECO B107- Registration_Server_Did_Not_Perform_an_Orderly_Shutdown The server for the REGISTER application just aborted the connection when it was done, instead of performing an orderly shutdown. This caused an additional exchange ECOs Contained in This Kit 4-3 ECOs Contained in This Kit of "unexpected termination" messages to be initiated by the REGISTER client. Although this exchange did not cause any noticeable problems, this kit corrects this behavior. o ECO B108- DSN$COPY_DIRECTORY_Should_Have_G:RE,_Not_G:RWE The protection on the DSN$COPY_DIRECTORY directory should have G:RE protection, not G:RWE protection. This kit changes the protection on this directory. o ECO B111- DSN_VTX_Displays_Command_File_if_SET_VERIFY If a user had the SET VERIFY state enabled and then entered a DSN VTX command, part of the command file that invokes the VTX client was displayed. This kit corrects this problem. o ECO B118- Startup_Symbol_DSN_COMMUNICATIONS_NODE Wrongly_Set_to_DSN$CURNODE The kit installation procedure built a startup file on DCN nodes that incorrectly defined the DSN_ COMMUNICATIONS_NODE symbol to DSN$CURNODE. This ECO kit creates a new startup file containing this correction. o ECO B120- Startup_Needs_to_Check_for_SYSLCK_Privilege Your DSN$STARTUP.COM is modified by this ECO kit to check for the SYSLCK privilege. o ECO B123- Resource_Name_Translation_Limit_Too_High If 127 resource paths were defined for a DSNlink DECnet Gateway connection to a single resource name, and none of these 127 paths were available, the connection failed with an invalid index error instead of a resource-not- available error. This kit corrects this problem. o ECO B126- ITS_Word_Highlighting_Problems It was possible for an incorrect highlighting map to be used when applying the highlights to your ITS document under these conditions: a document read from an ITS database was read a second time from internal cache after reading intervening documents; the database you had open was remotely served by your DSNlink Host from somewhere else (not coresident with the host); and you used keyword highlighting when reading the documents. This kit corrects this problem. 4-4 ECOs Contained in This Kit ECOs Contained in This Kit o ECO B129- DSN_COPY_Does_Not_Detect_File_Node_Names_Correctly Because the File Copy application does not permit files to be copied from another node, the application contains a test for the presence of a node name. If present, the error NODNAMNOTALLOW is issued. However, the check did not always work, and this error was not issued at times. Instead, the file copy aborted with an unrelated error. This release corrects this problem. o ECO B146- ITS_Boolean_Search_Text_Line_Corruption Under circumstances similar to ECO B126, text lines returned from the ITS server could be cached at inappropriate relative positions in the cache list. This kit corrects this problem. o ECO B172- DSN_Mail_Subprocesses_Loop Incoming DSNlink mail is handled by DSN$MAIL_xx subprocesses on your system. Those subprocesses could enter an infinite loop if they received certain incorrectly formatted destination mail addresses. This release corrects this problem. o ECO B182- HASH_SHIFT_Not_Initialized_in_DSN$NET_COMPRESS.B32 An internal hash table initialization problem caused sporadic network link failures, such as "unknown link" errors or "change cipher key" requests. These errors always resulted in premature link aborts or prevented the establishment of new links. This release corrects this problem. o ECO B191- COPY_Requeue_Fails_on_Unpopulated_Files If a File Copy job was aborted just after it allocated the space for the file but had not filled any blocks, the subsequent requeued job created another new file. The first empty file, with full space allocation, was not deleted. This kit prevents this problem. Additionally, the old in-progress file was locked by the server subprocess that populated the new in-progress file. This problem is also fixed. ECOs Contained in This Kit 4-5 ECOs Contained in This Kit o ECO B195- COPY_Requeue_Fails_When_Partial_File_Is_Deleted If a DSNlink Copy job partially copies a file, the file is requeued. If the partial file was deleted on the receiving end before the copy job restarted, the job errored out with a DSN-F-BADDATA error and a corrupt file was placed in the incoming files directory. This kit corrects this problem. 4-6 ECOs Contained in This Kit Copyright (c) Compaq Computer Corporation 1999. All Rights reserved. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. This ECO has not been through an exhaustive field test process. Due to the experimental stage of this ECO/workaround, Compaq makes no representations regarding its use or performance. The customer shall have the sole responsibility for adequate protection and back-up data used in conjunction with this ECO/workaround.