NetView Distribution Manager/2 Version 2.0 Documentation Update Corrective Service Diskettes PTF XR20465 15 February 1995 CONTENTS CONTENTS ABOUT THIS FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . III Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Trademarks and Service Marks . . . . . . . . . . . . . . . . . . . . . iii IBM Service Support . . . . . . . . . . . . . . . . . . . . . . . . . . iv Additional Support . . . . . . . . . . . . . . . . . . . . . . . . . . iv Online Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv ----------------------------------------------------------------------------- PART 1. CORRECTIVE SERVICE DISKETTES . . . . . . . . . . . . . . . . . . 1 CHAPTER 1. THE NETVIEW DM/2 CSD . . . . . . . . . . . . . . . . . . . . 2 What is New in this CSD . . . . . . . . . . . . . . . . . . . . . . . . . 3 Maintenance level serviced by this CSD . . . . . . . . . . . . . . . . . 4 Preparing NetView DM/2 for the CSD . . . . . . . . . . . . . . . . . . . 4 Installing the CSD . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Upgrading CDM Online Helps When Servicing Product Images by CSD . . . . . 9 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Migration from a CSD to Another . . . . . . . . . . . . . . . . . . . . 10 Preparing the Database Manager . . . . . . . . . . . . . . . . . . . . 11 Installing this CSD on Top of Previous CSDs . . . . . . . . . . . . . . 11 Upgrading DOS CC Client File Only or Related Images . . . . . . . . . . 13 Implementing DOS CC Client Microsoft Windows Support . . . . . . . . . 14 Implementing CC Server Support for DOS Installation on Pristine Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Quick Help For Installation of IBM Products Via NetView DM/2 . . . . . 16 CHAPTER 2. CORRECTIONS TO THE CDM USER'S GUIDE . . . . . . . . . . . . 18 PAGE 315 - TOPIC A.2.4 - NVDMCOPY C:\IBMNVDM2\SHARE_A\IMG\NVDM2V2 . . . 18 PAGE 232 - TOPIC 8.14 - CONVERSION TABLE FOR INITIATE PARAMETERS . . . 18 PAGE 288 - TOPIC 9.4.2 - PROCEDURE_PARMS FOR NVDMDCAM . . . . . . . . . 18 PAGE 217 - TOPIC 8.6.4.3 - The Change File Profile in the BUILD Command 19 PAGE 221 - TOPIC 8.8.3 - The CATALOG Command . . . . . . . . . . . . . 19 PAGE 332 - TOPIC A.3.4 - DOS Version 6.1 Installation on Pristine Workstations in a Stand-Alone LAN . . . . . . . . . . . . . . . . . . 19 PAGE 361 - TOPIC A.4.5 - OS/2 Migration from Version 2.0 to Version 2.1 Using NetView DM/2 . . . . . . . . . . . . . . . . . . . . . . . . . . 19 PAGE 393 - TOPIC A.8.2 - DOS Migration from Version 4.0.1 to Version 5.0.2 Using NetView DM/2 in a Stand-Alone LAN . . . . . . . . . . . . 20 PAGE 401 - TOPIC A.8.5 - A New Scenario: MS-DOS Migration from Version 5.00 to 6.00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 PAGE 426 - TOPIC A.13.4 - DOS Version 6.1 Installation Using CID on Pristine Workstations in a Stand-Alone LAN . . . . . . . . . . . . . . 21 PAGE 433 - TOPIC A.14.1 - DOS Migration from Version 5.0.2 to Version 6.1 Using CID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 PAGE 191 - TOPIC 4.8.2.2 - CDM Commands . . . . . . . . . . . . . . . . 21 PAGE 161 - TOPIC 7.3.2 - connection id . . . . . . . . . . . . . . . . 22 PAGE 224 - TOPIC 4.8.2.2 - CDM Commands . . . . . . . . . . . . . . . . 22 PAGE 291 - TOPIC 9.6 - FORMAT,PARAMETERS . . . . . . . . . . . . . . . 23 NEW APPENDIX - LAN Server Security Support . . . . . . . . . . . . . 23 CID Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Enabling NetView DM/2 to Run in Privileged Mode . . . . . . . . . . . . 25 (C) Copyright IBM Corp. 1991, 1995 ii ABOUT THIS FILE ----------------------------------------------------------------------------- PART 2. LDU USER'S GUIDE . . . . . . . . . . . . . . . . . . . . . . . 26 Considerations for Migrating to Communications Manager/2 on a Focal Point-Attached Workstation . . . . . . . . . . . . . . . . . . . . . . 26 CHAPTER 3. CORRECTIONS TO THE LDU USER'S GUIDE . . . . . . . . . . . . 28 PAGE 22 - TOPIC 3.5.3 - OS/2 SE 2.0 or 2.1 with LAN Services 3.0 or Later, or with NTS/2 1.0 . . . . . . . . . . . . . . . . . . . . . . . 28 PAGE 46 - TOPIC 4.3.11 - TIMEOUT . . . . . . . . . . . . . . . . . . . 28 ----------------------------------------------------------------------------- PART 3. INSTALLATION GUIDE . . . . . . . . . . . . . . . . . . . . . . 30 CHAPTER 4. NETVIEW DM/2 INSTALLATION CONTROL . . . . . . . . . . . . . 31 Copying the Client Feature from 3.5-Inch to 5.25-Inch Diskettes . . . . 31 CHAPTER 5. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE . . 33 PAGE 127 - TOPIC 2.2.4 - Copying files before installation: Sourcedir . 33 PAGE 199 - TOPIC 2.4.7.2 - WRONG NETBIOS TABLE . . . . . . . . . . . . 33 PAGE 30 - TOPIC 1.1.5.5 - Copying the Client Feature from 3.5-Inch to 5.25-Inch Diskettes . . . . . . . . . . . . . . . . . . . . . . . . . 34 PAGE 139 - TOPIC 2.2.6.2.2 - Using NVDMIDOS . . . . . . . . . . . . . . 35 PAGE 140 - TOPIC 2.2.6.2.2 - Using NVDMIDOS . . . . . . . . . . . . . . 35 PAGE 148 - TOPIC 2.2.8 - The AgentTimeout Parameter . . . . . . . . . . 36 PAGE 240 - TOPIC 2.4.4.9.5 Required NetBIOS Values . . . . . . . . . . 36 PAGE 139 - TOPIC 2.2.6.2.2 - NVDMIDOS command . . . . . . . . . . . . . 37 PAGE 179 - TOPIC 2.3.3 - Customizing the CDM Message Exit Routine . . . 37 PAGE 213 - TOPIC 2.4.9.9.5 - NETBIOS Profile . . . . . . . . . . . . . 38 PAGE 214 - TOPIC 2.4.9.9.5 - NETBIOS Profile . . . . . . . . . . . . . 39 ----------------------------------------------------------------------------- PART 4. MESSAGES AND ERROR RECOVERY GUIDE . . . . . . . . . . . . . . 40 CHAPTER 6. USER'S MESSAGES AND CODES . . . . . . . . . . . . . . . . . 41 New Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Changed Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Deleted Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 CHAPTER 7. INSTALLER'S MESSAGES AND CODES . . . . . . . . . . . . . . 44 New Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Changed Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Deleted Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 PAGE 324 - TOPIC 2.1.1.2 - messages . . . . . . . . . . . . . . . . . . 44 Changed Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 PAGE 297 - TOPIC 2.1.1.2 - messages . . . . . . . . . . . . . . . . . . 45 Deleted Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 CHAPTER 8. CORRECTIONS TO THE MESSAGES AND ERROR RECOVERY GUIDE . . . 46 PAGE 245 - SECTION xxxxx - Error Scenarios . . . . . . . . . . . . . . 46 PAGE 105 - TOPIC 1.1.1.4 - messages . . . . . . . . . . . . . . . . . 46 PAGE 103 - TOPIC 1.1.1.4 - messages . . . . . . . . . . . . . . . . . . 46 PAGE 84 - TOPIC 1.1.1.4 - messages . . . . . . . . . . . . . . . . . . 47 PAGE 84 - TOPIC 1.1.1.4 - messages . . . . . . . . . . . . . . . . . . 47 PAGE 84 - TOPIC 1.1.1.4 - messages . . . . . . . . . . . . . . . . . . 47 CONTENTS iii ABOUT THIS FILE INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 CONTENTS iv ABOUT THIS FILE ABOUT THIS FILE Introduction This file (README.TXT) tells you how to install the Corrective Service Diskettes (CSD). It also provides information which corrects or is supplementary to the following NetView* DM/2 manuals dated December 1993: o Concepts and Overview (GH19-4009) o CDM User's Guide (SH19-5048) o LDU User's Guide (SH19-5049) o Installation and Customization Guide (SH19-6915-03) o Messages and Error Recovery Guide (SH19-6924-03) A page reference for the hardcopy documentation and a topic reference for the online manuals are given for each amended or deleted item. NOTE: Certain characters in this file may not print correctly, or not at all, depending on your printer configuration, for example: the backslash (\), the square brackets ([,]), the pound sterling sign (¶), and the "at" symbol (@). If these characters do not print, you can view this README.TXT file on your screen using an OS/2 editor in order to see them. Trademarks and Service Marks The following terms, denoted by an asterisk (*) in this publication, are trademarks of the IBM* Corporation in the United States or other countries or both: +-------------------------------------+-------------------------------------+ | BookManager | Personal Computer XT | | IBM | Personal System/2 | | Library Reader | Presentation Manager | | NetView | PS/2 | | Operating System/2 | RETAIN | | OS/2 | Systems Application Architecture | | Personal Computer AT | | +-------------------------------------+-------------------------------------+ The following terms, denoted by a double asterisk (**) in this publication, are trademarks of other companies as follows: Microsoft Microsoft Corporation Microsoft Windows Microsoft Corporation Windows Microsoft Corporation (C) Copyright IBM Corp. 1991, 1995 v ABOUT THIS FILE IBM Service Support Please contact the Local IBM Service Support Center before installing this CSD to determine if there is any additional information or changes to the instructions in this document. Additional Support To assist you with product installation and general information, the following telephone number is available Monday through Friday, from 09.00 to 18.00 hours, Central European Time. Country Code (Italy) 39 Area Code (Rome) 6 Local IBM number 5966 Extension 2352 Product support is provided through the RETAIN* PMR (Problem Management Record). The NetView DM/2 Customer Support (Level 3) RETAIN queue is: NDM2,206 Online Manuals The NetView DM/2 publications are available in displayable softcopy form (BookManager*) and are shipped on diskettes as part of the basic machine-readable material. The diskette labels and contents are as shown in Table 1 on page v. ABOUT THIS FILE vi ABOUT THIS FILE +---------------------------------------------------------------------------+ | Table 1. Contents of Online Manual Diskettes | +-----------------------------+---------------+-----------------------------+ | DISKETTE LABEL | FILE NAME | DESCRIPTION | +-----------------------------+---------------+-----------------------------+ | NetView DM/2 Backup 001 of | "ANX0INST.EXE"| Backup of the first part of | | CDM User's Guide and | | the unpacking program for | | Install. & Custom. Guide | | the Installation and | | | | Customization Guide online | | | | manual | +-----------------------------+---------------+-----------------------------+ +-----------------------------+---------------+-----------------------------| +-----------------------------+---------------+-----------------------------+ | NetView DM/2 Backup 002 of | "ANX0INST.EXE"| Backup of the remaining | | CDM User's Guide and | and | part of the unpacking | | Install. & Custom. Guide | "ANX0CDMG.EXE"| program for the | | | | Installation and | | | | Customization Guide, and | | | | the unpacking program for | | | | the CDM User's Guide online | | | | manuals | +-----------------------------+---------------+-----------------------------+ +-----------------------------+---------------+-----------------------------| +-----------------------------+---------------+-----------------------------+ | NetView DM/2 Concepts, LDU | "ANX0CPTS.EXE"| Unpacking program for | | User's Guide, Msgs. and | | Concepts and Overview, | | Error Recovery Guide | | containing the online | | | | manual | +-----------------------------+---------------+-----------------------------+ | | "ANX0LDUG.EXE"| Unpacking program for LDU | | | | User's Guide, containing | | | | the online manual | +-----------------------------+---------------+-----------------------------+ | | "ANX0MSGS.EXE"| Unpacking program for | | | | Messages and Error Recovery | | | | Guide, containing the | | | | online manual | +-----------------------------+---------------+-----------------------------+ +-----------------------------+---------------+-----------------------------| +-----------------------------+---------------+-----------------------------+ | NetView DM/2 Bookshelf and | "ANX0BOOK.BKS"| NetView DM/2 Bookshelf | | Bookindex | | | +-----------------------------+---------------+-----------------------------+ | | "ANX0BOOK.BKI"| NetView DM/2 Bookindex | +-----------------------------+---------------+-----------------------------+ +-----------------------------+---------------+-----------------------------| +-----------------------------+---------------+-----------------------------+ | Library Reader* | Program and | Program that enables you to | | | installation | read the online books | | | files | without BookManager | +-----------------------------+---------------+-----------------------------+ +-----------------------------+---------------+-----------------------------| +-----------------------------+---------------+-----------------------------+ ABOUT THIS FILE vii ABOUT THIS FILE These are the memory requirements of the Library Reader and the online books, after they have been unpacked: FILES SIZE ANX0CDMG 4.5MB ANX0INST 6.5MB ANX0CPTS 426KB ANX0LDUG 205KB ANX0MSGS 622KB ANX0BOOK.BKI 688KB ANX0BOOK.BKS 0.7KB Library Reader Files 1.3MB The *.EXE files of Table 1 on page v are the unpacking programs that incorporate the packed versions of the NetView DM/2 manuals. When they are unpacked (see instructions below), they create the corresponding book files with the same name and extension, .BOO. The first two diskettes contain the unpacking programs for the NetView DM/2 ____________ Installation and Customization Guide and the NetView DM/2 Change Distribution ____________________________________ ________________________________ Manager User's Guide in a backed-up format, and therefore these two programs ____________________ must be restored from the diskettes to your hard disk, before you unpack them. You can use the RESTORE command of any OS/2 version from 1.3 to 2.1. The books, when unpacked and ready for use, are: "ANX0CDMG.BOO" NetView DM/2 CDM User's Guide "ANX0INST.BOO" NetView DM/2 Installation and Customization Guide "ANX0CPTS.BOO" NetView DM/2 Concepts and Overview "ANX0LDUG.BOO" NetView DM/2 LDU User's Guide "ANX0MSGS.BOO" NetView DM/2 Messages and Error Recovery Guide To browse the manuals, you need to have BookManager (OS/2* or DOS) installed on your workstation. Follow the instructions in the BookManager documentation to access the Bookshelf, the Bookindex, and the online manuals. IMPORTANT: In order to read the NetView DM/2 books, you must have the courier font installed in your OS/2 system (this is not required in a DOS machine). If you "DO" have BookManager perform the following steps to install the online books: 1. Restore the contents of the BACKUP 001 and 002 diskettes onto your hard disk. At the C: prompt (or wherever your OS/2 is installed), type: RESTORE a: ABOUT THIS FILE viii ABOUT THIS FILE The RESTORE command will guide you to introduce the two diskettes. Introduce first the diskette labeled "NetVIEW DM/2 Backup 001 of CDM user's Guide and Install. & Custom. Guide," and then "NetVIEW DM/2 Backup 002 of CDM user's Guide and Install. & Custom. Guide." Once the command has completed, you will find the two files, ANX0INST.EXE and ANX0CDMG.EXE, on your root directory. 2. Unpack the file containing the Installation and Customization online manual from the root directory into the directory where the books will be stored. Enter: ANX0INST <path>:dirname where "dirname" is the directory name where the books will be stored. 3. Unpack the file containing the CDM User's Guide online manual from the root directory into the directory where the books will be stored. Enter: ANX0CDMG <path>:dirname where "dirname" is the directory name where the books will be stored. 4. At the C: prompt, type: cd\dirname where "dirname" is the directory name where the books will be stored, and press enter to change directory 5. Insert the Bookshelf and Bookindex diskette and enter: copy A:\ANX0BOOK.* 6. Insert the Concepts, LDU User's Guide, and Messages and Error Recovery Guide online manuals diskette, and enter the following to unpack the books and make the remaining online manuals ready for use: A:ANX0CPTS A:ANX0LDUG A:ANX0MSGS If you do not have BookManager, you need to install the Library Reader software, which is provided with the CSD diskettes. The Library Reader diskette contains the following files: README.TXT General information on how to use the product. This file can be viewed with any editor (for example, the OS/2 editor). ABOUT THIS FILE ix ABOUT THIS FILE BOOKENG.AGR Information on authorized use of IBM online books. This file can be viewed with any editor (for example, the OS/2 editor). PLALRENG.AGR Program License Agreement. This file can be viewed with any editor (for example, the OS/2 editor). EZ2INST Directory This directory contains all the Program and Installation files. Before installing Library Reader, read the Program License Agreement (PLALRENG.AGR) carefully. To install the Library Reader, do the following: 1. At the C: prompt, insert the Library Reader diskette and enter: A: 2. From the A: drive, enter: cd\ez2inst 3. Enter: install 4. On the second panel enter "4" in the "Selection Field Number." 5. On the next panel: o Replace the default value with the letter of the drive that will contain your IBM Books. o Update your CONFIG.SYS (or AUTOEXEC.BAT for DOS) file. 6. Press "F10" when you are ready to install. 7. Restore the contents of the BACKUP 001 and 002 diskettes onto your hard disk. At the C: prompt (or wherever your OS/2 is installed), type: RESTORE a: The RESTORE command will guide you to introduce the two diskettes. Introduce first the diskette labeled "NetVIEW DM/2 Backup 001 of CDM user's Guide and Install. & Custom. Guide," and then "NetVIEW DM/2 Backup 002 of CDM user's Guide and Install. & Custom. Guide." Once the command has completed, you will find the two files, ANX0INST.EXE and ANX0CDMG.EXE, on your root directory. 8. Position yourself in the directory where Library Reader has been installed; if you are using OS/2, enter: <path>:cd\readibm2 ABOUT THIS FILE x ABOUT THIS FILE Or if you are using DOS, enter: <path>:cd\readibm 9. From the Library Reader directory enter: c:\ANX0INST to unpack the NetView DM/2 Installation and Customization Guide from the root directory where it was restored into the Library Reader directory. You can erase ANX0INST.EXE from your root directory, if you wish to do so, after it has unpacked into the book file. 10. From the Library Reader directory enter: c:\ANX0CDMG to unpack the NetView DM/2 CDM User's Guide from the root directory where it was restored into the Library Reader directory. You can erase ANX0CDMG.EXE from your root directory, if you wish to do so, after it has unpacked into the book file. 11. Insert the diskette containing "ANX0CPTS.EXE", "ANX0LDUG.EXE", and "ANX0MSGS.EXE", and enter, in the following sequence: "A:ANX0CPTS" to copy the NetView DM/2 Concepts and Overview into the Library Reader directory. "A:ANX0LDUG" to copy the NetView DM/2 LDU User's Guide into the Library Reader directory. "A:ANX0MSGS" to copy the NetView DM/2 Messages and Error Recovery Guide into the Library Reader directory. 12. Insert the diskette containing the "ANX0BOOK.BKS" and "ANX0BOOK.BKI" files and enter: copy A:ANX0BOOK.* to copy the Bookshelf and Bookindex into the Library Reader directory. 13. Restart your system. To read the online books, do the following. On an OS/2 1.3 workstation: 1. Open the "IBM Online Library Group" from the Desktop Manager. ABOUT THIS FILE xi ABOUT THIS FILE 2. From the "IBM Online Library", double-click on "All Available Bookshelves". The "ANX0BOOK NetView DM/2 Bookshelves" appears. 3. Double-click on it to see a list of the NetView DM/2 books. On an OS/2 2.0 or 2.1 workstation: 1. Open the "IBM Online Library" folder from the Workplace shell. 2. From the "IBM Online Library", double-click on "All Available Bookshelves". The "ANX0BOOK NetView DM/2 Bookshelves" appears. 3. Double-click on it to see a list of the NetView DM/2 books. On a DOS workstation: o Enter the command READIBM at the DOS prompt to see the Library Reader screen with a list of the NetView DM/2 books. ABOUT THIS FILE xii CSD PART 1. CORRECTIVE SERVICE DISKETTES This Corrective Service Diskette set (CSD) improves the performance of NetView DM/2 in several areas. Many of the changes will be transparent to you, as they improve the way NetView DM/2 functions without changing how you use it. Some of the changes involve amending the way you use NetView DM/2 and thus require the documentation also to be amended. (C) Copyright IBM Corp. 1991, 1995 1 CSD CHAPTER 1. THE NETVIEW DM/2 CSD WARNING: THE NETVIEW DM/2 CSD IS DELIVERED ON 3.5 INCH DISKETTES. IF YOUR CC CLIENT MACHINE HAS ONLY 5.25 INCH DRIVES, OR ONLY LOW CAPACITY 3.5 INCH DRIVES, YOU MUST USE ONE OF THE UNATTENDED INSTALLATION METHODS DESCRIBED BELOW, OR USE THE COMMUNICATION NETWORK TO TRANSFER THE CSD TO THE CC CLIENT WORKSTATION. To apply a CSD requires two stages: o The product files must be refreshed o The SYSLEVEL files must be updated The descriptions that follow encompass both of these tasks in a variety of ways. IMPORTANT NOTE: The product directory name for this version of NetView DM/2 is IBMNVDM2, thus any reference to IBMANX throughout the documentation has to be considered obsolete. Among the other tasks, this NetView DM/2 CSD allows you to perform the following ones: o Refreshing the product image The NetView DM/2 product diskettes can be copied to the fixed disk of a workstation to create a NetView DM/2 product image. A disketteless installation of NetView DM/2 can be performed from this product image, either on the local system or on remote workstations. The CSD can be applied to the product image, creating a "refreshed" product image that is at the same level as the CSD. o Applying the CSD by installing the refreshed product image. Previous CSDs could only be applied on top of an installed release of a product. In order to install new systems, you: 1. Installed the original product diskettes 2. Applied the CSD. The refreshed product image can now be installed on systems without NetView DM/2, or reinstalled on systems that already have NetView DM/2. The version of NetView DM/2 on these systems will be the same level as the CSD. Thus, the following processes will produce the same version of NetView DM/2: o Process A) Installing the original product diskettes plus applying the CSD o Process B) Installing the refreshed product image. (C) Copyright IBM Corp. 1991, 1995 2 CSD Another consideration is whether NetView DM/2 will be installed in an attended or unattended environment: o An attended environment assumes that a person is physically present at a workstation in order to respond to requests from the software and to change diskettes o An unattended environment assumes that a person is NOT physically present at the workstation. The installation must thus be controlled other than by responding to software requests, and cannot be diskette-based. The process of installing the CSD also involves preparing NetView DM/2 for the CSD before using it, and, after using it, rebinding Database Manager to the upgraded NetView DM/2. What is New in this CSD This CSD, XR20465, distributes some product fixes as referenced in the FIXES.TXT file located in the last CSD diskette, labelled CC Server APAR FIXES. In addition, this CSD cumulates the NetView DM/2 Version 2.0 support of the Access Control Lists (ACLs), made available since previous CSD XR20354, available with LAN Server 3.0 product. NetView DM/2 ensures that existing ACLs are maintained at the target during installation by replication operations. ACLs are not included in change files during the build process and therefore cannot be distributed from a source to a target. In addition, no ACL information is transmitted with an object during file services operations (RETRIEVE and SEND). However, NetView DM/2 has no control over the writing of files during CID installations or installations by external programs. During such installations, NetView DM/2 simply runs the install program, which must manage the ACL information itself. Refer to the documentation provided with the external program for additional information. The LAN administrator must ensure that either NetView DM/2 is started as an administrator process or that it has the proper authorizations to perform the operations on ACLs. Furthermore,this CSD distributes fixes to guarantee current product to be compatible with its future releases. Moreover, this CSD cumulates the DOS CC enhancement to support Microsoft Windows**, as well as the CC server enhancement to support DOS installation on pristine workstations made available since CSD XR20334 issue. For more information about the new supports, refer to "Implementing DOS CC Client Microsoft Windows Support" on page 14 and "Implementing CC Server Support for DOS Installation on Pristine Workstations" on page 16. CHAPTER 1. THE NETVIEW DM/2 CSD 3 CSD Maintenance level serviced by this CSD This CSD cumulates fixes and enhancements since CSD XR20273; then, it applies to any maintenance level from XR00000_ to XR00006_ . Once implemented, any product full configuration or images, selected at CSD installation time, will result as upgraded at XR00007_ . Preparing NetView DM/2 for the CSD Before servicing NetView DM/2, you MUST close all current NetView DM/2 programs in order to avoid the possibility that some files (the CDM dialogs, the transmission controller, Communications Manager, Database Manager, and other components or corequisites of NetView DM/2) will remain locked. CHAPTER 1. THE NETVIEW DM/2 CSD 4 CSD Installing the CSD +--- WARNING -----------------------------------------------------+ | | | While upgrading NvDM/2 from a previous Level it is very import|nt | upgrade FIRST CC Server and ONLY AFTER THIS the CC Client. | | | | In fact it is possible to run NvDM/2 in the following scenario|: | | | New Server <----------------------> New Client (DOS and OS/2) | | New Server <----------------------> Old Client (DOS and OS/2) | | Old Server <----------------------> Old Client (DOS and OS/2) | | | | WHILE IT IS NOT POSSIBLE TO RUN IN THE FOLLOWING SCENARIO | | | | Old Server <----------------------> New Client (DOS and OS/2) | | | | where Old means previous CSD (or previous ones) and New means | | current CSD (This CSD). | | | +-----------------------------------------------------------------+ +--- WARNING -----------------------------------------------------+ | | | DOS CC Client, File Only or related diskette images on | | CC Server, must be upgraded by invoking respectively | | NVDMIDFO or NVDMDCPY from the first CSD diskette labelled | | 'DOS CC Client APAR FIXES' : | | | | DESELECT PATHS, RELATED TO DOS CC CLIENT ON CC SERVER, | | FROM THE MAIN SERVICE MENU IF ANY DETECTED BY SERVICE. | | | | Pls refer to NVDM/2 Installation and Customization Guide | | for a complete overview of the aforementioned commands. | | | | | +-----------------------------------------------------------------+ +--- WARNING -----------------------------------------------------+ | | | IF YOU CHOSE TO REFRESH THE CODE AS PER ABOVE, PLEASE BE | | AWARE THAT YOU LOOSE ANY CHANGE YOU HAVE INTRODUCED INTO | | FILES ANXIDMCF.CNF AND ANXIDMCF.AUT | | | +-----------------------------------------------------------------+ ATTENDED INSTALLATION OF THE NETVIEW DM/2 CSD The attended methods for installing the NetView DM/2 CSD utilize the OS/2 Corrective Service Facility (CSF). This is a utility that applies fixes (service) to the OS/2 operating system and other OS/2-based products. CHAPTER 1. THE NETVIEW DM/2 CSD 5 CSD The Corrective Service Diskette can be installed by the CSF in one of three ways, depending on whether NetView DM/2 is installed or has been copied to a diskette image directory, and on whether you want to use the default installation or to modify it. NETVIEW DM/2 INSTALLED - DEFAULT CSD INSTALLATION VIA REBOOT This method will apply the CSD to the installed version of NetView DM/2 Version 2.0 and product images as well. If you want to install the CSD using the standard defaults, a default response file has been created, which you use as follows: 1. Insert the Corrective Service Diskette #1 in the A: drive 2. Restart the workstation The CSD will be applied according to response file information. If you choose to use the default response file (RESPONSE.FIL) on the 2nd CSD diskette set, the CSD results as applied to all the installed versions and product images as well that are detected on local Hard Disk. NOTE: Refer to REDBOOK GG24-3780 (Remote Installation and Maintenance) for more information on how to create response file. NETVIEW DM/2 IMAGE ON FIXED DISK - DEFAULT CSD INSTALLATION (NVDMRCSD.EXE) This method will apply the CSD to the installed version and also to a diskette image of NetView DM/2. If you want to install the CSD using the standard defaults, a default Response File has been created, which you use as follows: 1. Insert the Corrective Service Diskette #2 in the A: drive 2. Enter A:\NVDMRCSD The CSD will be installed on the diskette image of NetView DM/2, using the FSERVICE utility. The CSD will be applied according to response file information. CHAPTER 1. THE NETVIEW DM/2 CSD 6 CSD If you choose to use the default response file (RESPONSE.FIL) on the 2nd CSD diskette set, the CSD results as applied to all the installed versions and product images as well that are detected on local Hard Disk. NOTE: Refer to REDBOOK GG24-3780 (Remote Installation and Maintenance) for more information on how to create response file. NETVIEW DM/2 IMAGE ON FIXED DISK - MODIFIED CSD INSTALLATION (NVDMPCSD.EXE) This method will apply the CSD to the installed version and also to a diskette image of NetView DM/2. The CSD will be installed on the diskette image of NetView DM/2, using the SERVICE utility. To change the level of NetView DM/2 or the default directories, take the following steps: 1. Insert the Corrective Service Diskette #1 in the A: drive 2. Enter A:\NVDMPCSD. This displays a window containing a list of the products on the workstation that are eligible for service. 3. Select NetView DM/2 by highlighting the appropriate entries in the Products list. All eligible products are initially selected. 4. To view the current levels of the products on your system, select CURRENT from the LEVELS menu. To view the new level of NetView DM/2 on the CSD, select NEW from the LEVELS menu. 5. The service utility updates files in a set of directories associated with each selected product. To view or change the set of directories, choose SELECT DIRECTORIES from the OPTIONS menu. 6. When all selections have been made, select SERVICE to start the service process. You WILL NOT be able to terminate the service process after it has been started. The CSD will be installed on the diskette image of NetView DM/2. A service log is provided for installation verification: <bootdrive>:\OS2\INSTALL\SERVICE.LOG, where <bootdrive> is the partition from which you IPLed. Subsequent installs will be appended to the service log. CHAPTER 1. THE NETVIEW DM/2 CSD 7 CSD UNATTENDED INSTALLATION OF NETVIEW DM/2 CSD The unattended method of installing the NetView DM/2 CSD utilizes the standard installation programs supplied with NetView DM/2: o NVDMEINS to install the Entry Base o NVDMREC to install the LDU Receiver o NVDMINST to install the Extended Base o NVDMCLT to install the Change Control Client All of these programs can be invoked from the refreshed product images, and the release level they install from the refreshed product image will be that of the CSD. WARNING: THE UNATTENDED INSTALLATION OF NETVIEW DM/2 (REFRESHED WITH THE CSD) CAN ONLY BE ACCOMPLISHED USING THESE PROGRAMS. THE PROGRAMS DESCRIBED PREVIOUSLY (FSERVICE, SERVICE, NVDMPCSD, AND NVDMRCSD) CANNOT BE USED TO INSTALL A NETVIEW DM/2 CSD IN AN UNATTENDED WAY, ALTHOUGH FSERVICE AND SERVICE CAN STILL BE USED FOR THE UNATTENDED INSTALLATION OF CSDS FOR OTHER PRODUCTS SUCH AS OS/2 2.0. The recommended process for the unattended installation of a NetView DM/2 CSD in a local area or wide area environment requires the use of an administrative workstation. This is a workstation installed with either the NetView DM/2 Entry Base or Extended Base, with connectivity to the other Entry/Extended Base workstations that require an unattended CSD installation. 1. Create a diskette image of NetView DM/2, if it does not already exist. 2. Refresh the NetView DM/2 product image using one of the attended methods described above (either NVDMRCSD or NVDMPCSD). 3. Use NetView DM/2 to distribute the refreshed product image to the NetView DM host. 4. If the administrative workstation is the CC server of a CC domain, use NetView DM/2 at the Administrative Workstation to install the refreshed product at any CC clients in the administrative workstation's CC Domain, by using the appropriate installation program (NVDMEINS, NVDMINST, or NVDMCLT) and by using the same response files that were used to install NetView DM/2 on these systems originally. 5. Use NetView DM at the host to distribute and install the refreshed product at all workstations to which it is connected, either directly by APPC or indirectly through a LAN, by using the appropriate installation program (NVDMEINS, NVDMINST, or NVDMCLT) and by using the same response files that were used to install NetView DM/2 on these systems originally. CHAPTER 1. THE NETVIEW DM/2 CSD 8 CSD For details about how to execute these steps see the scenarios and descriptions provided in the "NetView DM Overviews and Scenarios Manual" and the "NetView DM/2 Installation and Customization Guide." NOTE: If you want to install the refreshed NetView DM/2 on new workstations, use the refreshed product image and the appropriate installation program. Upgrading CDM Online Helps When Servicing Product Images by CSD The CDM online help files are normally installed under the "CMLIB" directory during a fully configured installation of NetView DM/2, and only if the installer decides he wants them. The files are NOT upgraded automatically by the CSD when servicing product images. This task is left to the user, with the aid of two files: CLIHLP.EXE and SRVHLP.EXE that It can find in the CSD diskette labelled CDM ON LINE MESSAGES. To apply the refreshed Help files, proceed in the following manner: 1. open a OS/2 window or full-screen session 2. go into the "CMLIB" directory 3. copy "CLIHLP.EXE" if your workstation is configured as a NetView DM/2 CC client, or "SRVHLP.EXE" if your workstation is configured as a NetView DM/2 CC server or CDM Base 4. invoke either "CLIHLP" as <path>\CLIHLP -o or "SRVHLP" as <path>\SRVHLP -o CHAPTER 1. THE NETVIEW DM/2 CSD 9 CSD Limitations 1. Whereas OS/2 V.1.3 and V.2.0 are serviceable either from command line (with the A:\SERVICE command) or by restarting with the first CSD diskette, OS/2 V.1.2 is only serviceable by restarting with the first CSD diskette. 2. If a system has been configured with the 386 HPFS, it is not possible to install the CSD restarting the system; for more information please refer to RETAIN APAR II06607. Moreover, if LOCAL SECURITY for the 386 HPFS is installed, before starting installation with the A:\SERVICE command, it is necessary to log on to the server with an administrator's privilege level. 3. When running NetView DM/2 on OEM or newer IBM (PC/VP, industrial PC, or other) workstations, it is not possible to install the CSD restarting the system; for more information please refer to RETAIN APAR II06709. 4. The CSD can only be installed on IBM model 9557 and Thinkpad from the command line. Please refer to the NetView DM/2 product PSP (Preventive Service Planning) for additional information. 5. The programs NVDMPCSD and NVDMRCSD cannot be used to update the NetView DM/2 images on a remote drive, because the OS/2 Corrective Service Facility, used to apply the CSD to the target drives, supports service FROM a remote drive but not TO a remote drive. +--- IMPORTANT -------------------------------------------------------------+ | | | Please refer to the NetView DM/2 product PSP (Preventive Service | | Planning) for additional information. | | | +---------------------------------------------------------------------------+ Migration from a CSD to Another If you are migrating from one CSD to another, you cannot use an INITIATE command, because that would generate an error. The installation command to be used is EXTERNAL INSTALL. CHAPTER 1. THE NETVIEW DM/2 CSD 10 CSD Preparing the Database Manager If either of the attended installation processes is used to apply the NetView DM/2 CSD to the installed release, the following steps are required to bind the new version of NetView DM/2 to the database. These steps must be completed before restarting NetView DM/2 after the CSD has been installed, by issuing commands from the OS/2 command line: 1. Shut down any active components of CDM 2. Log on to Database Manager with database administrator access. NOTE: The database administrator ID should be the same as that used when NetView DM/2 was installed. 3. Enter STARTDBM 4. Insert the last CSD diskette into drive A: 5. Enter the following commands: SQLBIND A:\ANXCSCD1.BND <dbname> SQLBIND A:\ANXCSCD3.BND <dbname> SQLBIND A:\ANXCSCD4.BND <dbname> SQLBIND A:\ANXCSCD5.BND <dbname> SQLBIND A:\ANXCSCD6.BND <dbname> SQLBIND A:\ANXCSCD8.BND <dbname> SQLBIND A:\ANXCSCD9.BND <dbname> SQLBIND A:\ANXCSCDC.BND <dbname> SQLBIND A:\ANXCSCDD.BND <dbname> SQLBIND A:\ANXCSCDG.BND <dbname> SQLBIND A:\ANXCSCDJ.BND <dbname> SQLBIND A:\ANXCSCDL.BND <dbname> SQLBIND A:\ANXCSCDN.BND <dbname> SQLBIND A:\ANXCSCDP.BND <dbname> SQLBIND A:\ANXCSCDR.BND <dbname> Failure to execute these SQLBIND statements before database reorganization will result in an SQL error code 805. 6. Start NetView DM/2 Installing this CSD on Top of Previous CSDs CHAPTER 1. THE NETVIEW DM/2 CSD 11 CSD +--- WARNING ---------------------------------------------------------------+ | | | This section applies if you have previously serviced the installed | | version of NetView DM/2 CC server with the XR20273 or XR20276 CSD. You | | do not need to use the following instructions if you have applied any | | previous CSD version only to the NetView DM/2 image directory on the | | fixed disk and then used the NetView DM/2 installation program to refresh | | the installed version of the CC server. You can skip this section if you | | have a stand-alone CC server installed (without the Transmission | | Controller component installed). | | | +---------------------------------------------------------------------------+ The Transmission Controller component of NetView DM/2 has some working files under the TCDATA directory; these files have the extension ".SNA". Before starting the installation you should ensure that you have the backup copies ("*.BAK") of the corresponding "*.SNA" files used by the Transmission Controller. The "*.SNA" files are customized at installation time with the name of the product directory in which the product is being installed. When the installation is complete, you can use the "*.BAK" files to restore the corresponding "*.SNA" files in one of the following ways: 1. Copy the "*.BAK" files as "*.SNA". 2. Run NVDMINST /CO /DTR. 3. Run NVDMPMS with "Installation Type = Configuration Only" and "Delete Options = Transmissions." Restoring the "*.SNA" files deletes any remote destinations already configured; you must therefore again add your remote destinations through the dialog interface or the CDM CONFIG command. Previous NetView DM/2 CSDs had a problem in updating the backup files of the transmission controller ("*.BAK" files under the TCDATA directory). In fact, the XR20273 and XR20276 CSDs, when applied directly to an installed version of NetView DM/2, replace the "*.BAK" files losing some information. This means that in this situation you cannot restore the "*.SNA" files any more. If you have installed only the XR20273 or XR20276 CSDs to the image directory, then you don't have this problem because the NetView DM/2 installation program customizes these files at installation time. To recover the overwritten "*.BAK" files you have to run the CUSTSNBK.EXE tool that is on the last CSD diskette. The CUSTSNBK.EXE tool is not installed automatically by the CSD. You have to copy it on the CC server workstation affected by the problem and simply execute it with no parameters. This tool will look for the installed version of NetView DM/2 and properly update the "*.BAK" files. CHAPTER 1. THE NETVIEW DM/2 CSD 12 CSD The CUSTSNBK.EXE tool appends its log to the SERVICE.LOG under the OS2\INSTALL directory. If you have restored the "*.SNA" files after the "*.BAK" files were overwritten by the CSD service, then you need to run the CUSTSNBK.EXE tool and again restore your "*.SNA" files. Important Information About Installing This CSD on Top of CSD XR20303 The following considerations apply when installing the current CSD on top of CSD XR20303, shipped in June '93. After CSD XR20303 installation, you may have performed a manual installation of DOS Version 6.1. If this is the case, no unattended migration is provided to the new DOS CC client level of this CSD, because CSD XR20303 only supports DOS 4.0.1 and 5.0.2. In this particular situation, the installation of the DOS CC client must be performed locally at the target workstation, or, alternatively, you can discard NetView DM/2 files and perform a remote installation using the pristine diskettes. For further information about the creation of pristine diskettes, refer to the Appendix A, Detailed Scenarios, of the NetView DM/2 CDM User's Guide (SH19-5048-00), supplied as a softcopy with this CSD. Users wishing to upgrade to DOS 6.0 or 6.1 should first migrate their workstations to the DOS CC client code provided with this CSD, and then upgrade to the new level of DOS. This scenario is supported in a fully unattended fashion. Upgrading DOS CC Client File Only or Related Images DOS CC Client, File Only or related diskette images on CC Server, must be upgraded by invoking respectively NVDMIDFO or NVDMDCPY from the first CSD diskette labelled 'DOS CC Client APAR FIXES'. Command syntaxes : NVDMIDFO /T:target_path /L:logfile /S:source_dir NVDMDCPY /S:source_dir /T:target_path NOTE: Pls refer to NVDM/2 Installation and Customization Guide for a complete overview of the aforementioned commands. CHAPTER 1. THE NETVIEW DM/2 CSD 13 CSD Implementing DOS CC Client Microsoft Windows Support The new support can be implemented either in an attended or unattended way, depending on your environment and requirements. Attended Implementation The attended implementation can be performed reinstalling the DOS CC client using the subset diskettes of CSD XR20465 labelled DOS CC Client APAR FIXES. The steps are as follows: 1. Insert the first CSD diskette labelled DOS CC Client APAR FIXES in the A: drive. 2. If a DOS CC client already exists, and you want to keep its configuration, enter the following command: A:NVDMIDOS If you want to refresh the product code and the configuration, enter the following command: A:NVDMIDOS R:<ResponseFile> where <ResponseFile> is the appropriate response file for the DOS CC client. +--- WARNING -----------------------------------------------------+ | | | IF YOU CHOSE TO REFRESH THE CODE AS PER ABOVE, PLEASE BE | | AWARE THAT YOU LOOSE ANY CHANGE YOU HAVE INTRODUCED INTO | | FILES ANXIDMCF.CNF AND ANXIDMCF.AUT | | | +-----------------------------------------------------------------+ +--- NOTE TO IMPLEMENT FIX FOR PTR 2M04114 -----------------------+ | | | TO HAVE THE PTR 2M04114 (NVDMWCAM FAILS WITH GRP | | WITH SPECIAL CHARACTERS) IMPLEMENTED AND FULL | | EFFECTIVE, ANXIDMCF.CNF IS TO BE UPDATED. | | IF YOU HAVE CUSTOMIZED THIS FILE BEFORE, JUST | | RUN NVDMIDOS COMMAND WITHOUT PARAMETERS AND | | THEN MANUALLY UPDATE ANXIDMCF.CNF REMOVING | | PARENTHESIS AND VALUES AT COUNTRY.SYS LINE WHILE | | ADDING THE LAST LINE YOU COULD RETRIEVE FROM | | ANXIDMCF.BKC FILE. | | OTHERWISE, RUN NVDMIDOS WITH /RRF PARAMETER | | | +-----------------------------------------------------------------+ CHAPTER 1. THE NETVIEW DM/2 CSD 14 CSD NOTE: When using NVDMIDOS, you are prompted to insert diskettes with a numbering that does not match the one in this CSD. This is because the installation programs refer to the product refresh available in January 1994. The CSD diskettes that are to be used according to the messages displayed during the installation process are as follows: DISKETTE NUMBERS IN CSD XR20465 (THOSE LABELLED 'DOS CC CLIENT APAR FIXES') 1-5 DISKETTE NUMBERS IN JANUARY PRODUCT REFRESH 13-17 For a complete overview of the NVDMIDOS command syntax, refer to the NetView DM/2 Installation and Customization Guide, (SH19-6915-03) supplied as a softcopy with this CSD. Unattended implementation The unattended implementation can be performed by executing a CID External Install of the DOS CC client from the appropriate images upgraded by this CSD XR20465. NOTE: The DOS CC client images MUST be located on one of the CC server shared areas. The steps are as follows: 1. Apply the CSD XR20465 on the DOS CC client images 2. Prepare a change file to install the refreshed code, using a change file profile as the following one: TargetDir = C:\IBMNVDD2 Section Install Begin Program = $(SourceDir)\NVDMIDOS.EXE Parms = /S:$(SourceDir) /R:$(ResponseFile) > /T:$(TargetDir) ResponsFile = $(SourceDir)SAMPLE.RSP SourceDir = SA:\ End 3. Run an INSTALL command on the DOS CC client to refresh the code. For a complete overview of a CID External Install, refer to NetView DM/2 CDM User's Guide (SH19-5048-00), supplied as a softcopy with this CSD. CHAPTER 1. THE NETVIEW DM/2 CSD 15 CSD Implementing CC Server Support for DOS Installation on Pristine Workstations This CSD allows to enhance the CC server directory structure to support DOS CC client pristine workstations. This implementation can be performed either in an attended or unattended way, using respectively the enhanced NVDMRCSD or NVDMPCSD utilities when applying this CSD on a fully configured product installation of any CC server. Refer to "Installing the CSD" on page 5 for a complete overview of the installation methods that use these commands. For a complete overview of DOS installation on pristine workstations, refer to Appendix A of the NetView DM/2 CDM User's Guide (SH19-5048-00), supplied as a softcopy with this CSD. Quick Help For Installation of IBM Products Via NetView DM/2 This publication, written by the IBM Enterprise LAN Integration Test (ELITE) team, explains how to install a number of IBM products with NetView DM/2. The installation scenarios and the related samples provided in this book will help "quick" start NetView DM/2 users when investigating the remote installation of an IBM product. For your convenience, this CSD contains both a softcopy and a postscript version of Quick Help, and a self-unpacking file with sample profiles, REXX utilities, and response files. Look for the following files in the CSD diskettes: o NDM2QUIK.BOO, the softcopy version of the Quick Help manual o NDM2QUIK.EXE, the zipped, self-unpacking postscript version of the Quick Help manual o ELITE.EXE the zipped, self-unpacking file containing the samples o NDMDHLP1.BOO, the softcopy version of the Quick Help manual for DOS CC Client. o NDMDHLP1.EXE, the zipped, self-unpacking postscript version of the Quick Help manual for DOS CC Client. o ELITEDOS.EXE the zipped, self-unpacking file containing the samples for DOS CC Client. CHAPTER 1. THE NETVIEW DM/2 CSD 16 CSD The Quick Help Softcopy Version You can display NDM2QUIK.BOO or NDMDHLP1.BOO with IBM BookManager or IBM Library Reader. Just copy NDM2QUIK.BOO and NDMDHLP1.BOO from the CSD diskette into your workstation's BookManager or Library Reader BOOKS directory. The Quick Help Postscript Version If you choose to print Quick Helps on your PostScript printer unpack NDM2QUIK.EXE and NDMDHLP1.EXE onto your workstation's hard disk. To do this, from the CSD diskette containing this file run this command: A:\NDM2QUIK <outpath on your hard disk> A:\NDMDHLP1 <outpath on your hard disk> The zipped NDM2QUIK file will unpack into file NDM2QUIK.PS which is ready to print. NDM2QUIK.PS occupies 3.6 Mbytes. The zipped NDMDHLP1 file will unpack into file NDMDHLP1.LPS which is ready to print. NDMDHLP1.LPS occupies 1.5 Mbytes. The Quick Help Samples The sample REXX utilities, response files and profiles shown in the books are gathered in ZIP files called ELITE and ELITDOS. This files in the book are referenced as ELITE.ZIP and ELITEDOS.ZIP . For your convenience, both ELITE.ZIP and ELITDOS.ZIP have been made as self-extracting ones called ELITE.EXE and ELITEDOS.EXE in this CSD. Unpack it using the -d option to maintain the original directory structure with the following command: A:\ELITE -d <outpath> A:\ELITEDOS -d <outpath> CHAPTER 1. THE NETVIEW DM/2 CSD 17 CSD CHAPTER 2. CORRECTIONS TO THE CDM USER'S GUIDE PAGE 315 - TOPIC A.2.4 - NVDMCOPY C:\IBMNVDM2\SHARE_A\IMG\NVDM2V2 In the User's Guide Appendix A under "Detailed Scenarios" step 1 preparing server environment which reads: A:NVDMCOPY /S:A: /T:\IBMNVDM2\SHARE_A\IMG\NVDM2V2 the /S:A: should be changed into /S:A:\. PAGE 232 - TOPIC 8.14 - CONVERSION TABLE FOR INITIATE PARAMETERS As the initiate didn't work for a DBCS CP, a code change has been made in order to allow it. If a DBCS codepage is found it is converted into a SBCS CP. The following conversion table has to be added in the User's Guide for the INITIATE description: MAP OF CONVERSION FOR INITIATE PARAMETERS: ------------------------------------------ SBCS TO SBCS - converted to the target SBCS CP SBCS TO DBCS - converted to the first prepared SBCS CP or to 850 DBCS TO DBCS - not converted DBCS TO SBCS - not converted PAGE 288 - TOPIC 9.4.2 - PROCEDURE_PARMS FOR NVDMDCAM In the User's Guide is not clear specified at Chapter 9:CDM UTILITIES NVDMDCAM section, that the procedure parms have to be included into the double quotes. (C) Copyright IBM Corp. 1991, 1995 18 CSD PAGE 217 - TOPIC 8.6.4.3 - The Change File Profile in the BUILD Command At the very end of the section, ADD the following note: NOTE: As shown in this section, the preparation of a change file profile requires including many parameters with different values. It is recommended that you carefully check for all parameters to be set correctly, before starting to build a change file. In this way, you can avoid the time-consuming process of detecting and solving problems that sometimes are merely caused by an incorrect parameter. PAGE 221 - TOPIC 8.8.3 - The CATALOG Command In the RULES section, ADD the following after the list: Generally, it is recommended that you carefully check for all parameters to be set correctly, before starting to catalog an object. In this way, you can avoid the time-consuming process of detecting and solving problems that sometimes are merely caused by an incorrect parameter. PAGE 332 - TOPIC A.3.4 - DOS Version 6.1 Installation on Pristine Workstations in a Stand-Alone LAN After Step b.3 at the top of the page, ADD the following: c. Restart the preparation site under the DOS partition (C). Then, CHANGE the number of the following step from 4 to 1. In the same step, CHANGE the "SETUP" command to read: SETUP C:\DOS DELETE the line corresponding to Step C, and ADD a number 2 to the following sentence, as specified below: 2) Perform the following actions: PAGE 361 - TOPIC A.4.5 - OS/2 Migration from Version 2.0 to Version 2.1 Using NetView DM/2 After the first paragraph, ADD the following note: NOTE: Because of a Japanese OS/2 limitation, this scenario cannot be used to migrate from OS/2 2.0J to 2.1J. CHAPTER 2. CORRECTIONS TO THE CDM USER'S GUIDE 19 CSD PAGE 393 - TOPIC A.8.2 - DOS Migration from Version 4.0.1 to Version 5.0.2 Using NetView DM/2 in a Stand-Alone LAN In the "Prerequisites" section, CHANGE the fourth bullet as follows: The CC client workstations are all different models of PS/2*. PAGE 401 - TOPIC A.8.5 - A New Scenario: MS-DOS Migration from Version 5.00 to 6.00 At the end of the scenario about DOS migration from Version 4.01 to 5.02 using NetView DM/2 in a stand-alone LAN, ADD the following section: MS-DOS Migration from Version 5.00 to 6.00 The previous scenario can be used also to migrate MS-DOS from Version 5.00 to 6.00. You can refer to the scenario steps starting on page 395 (topic A.8.5), bearing in mind the following considerations: o The files to be copied under the \SYSTEM directory of the SHARED_A area are the following: - IO.SYS (without its attributes) - MSDOS.SYS (without its attributes) - DBLSPACE.SYS (without its attributes) - COMMAND.COM - SYS.COM o The change file profiles must refer to MS-DOS and not to DOS o You need to build a fourth change file profile (DOSSETVER.PRO) for the SETVER.EXE program, as follows: TargetDir =C:\ Section Install Begin Program = C:\DOS\SETVER.EXE Parms = SYS.COM 6.00 End Section Catalog Begin ObjectType =SOFTWARE GlobalName =MSDOS.600.SETVER.REF.1 Description ='DOS 6.00 Installation' End CHAPTER 2. CORRECTIONS TO THE CDM USER'S GUIDE 20 CSD o In addition to the ones specified in Step 1.f on page 397, (topic A.8.5), you need to build the following change file: CDM BUILD C:\DOSSETVER.PRO FS:DOSSETVER.PKG o In addition to the commands issued in Step 2 on page 397 (topic A.8.5), enter the following: CDM SEND MSDOS.600.SETVER.REF.1 ITIBM0PC.PS2SVR o You don't need to apply Step 3 o When installing the packages at the target nodes, submit the following commands in addition to the ones specified in Step 4 on page 399 (topic A.8.5): CDM INSTALL MSDOS.600.SETVER.REF.1 /WS:@C:\PS2WS.LST CDM ACTIVATE /WS:@C:\PS2WS.LST CDM INSTALL MSDOS.600.INST.SYS.REF.1 /WS:@C:\PS2WS.LST PAGE 426 - TOPIC A.13.4 - DOS Version 6.1 Installation Using CID on Pristine Workstations in a Stand-Alone LAN In the list under Step e., at the top of the page, CHANGE the last bullet as follows: Menu Timeout = -1 PAGE 433 - TOPIC A.14.1 - DOS Migration from Version 5.0.2 to Version 6.1 Using CID In the "Objectives" section, CHANGE the second bullet of the first list as follows: The LAN Support Program (LSP) from Version 1.2, 1.33, or 1.34 to Version 1.35 PAGE 191 - TOPIC 4.8.2.2 - CDM Commands At the very end of the page, ADD the following paragraph: CHAPTER 2. CORRECTIONS TO THE CDM USER'S GUIDE 21 CSD Workstation parameter Some parameter refer to workstation names. They can be specified in the following way 1. /WS:ws_id; it identifies a workstation in the CC Domain to which the command must be applied 2. /WS alone; it means that the command must be applied to all the CC Clients. (Up to 1000 workstations can be defined in the CC Domain) 3. /WS:@file_name; it means that the command must be applied to all the workstations listed in the specified file name. The file must have the following format: PS2CLT2 PS2CLT3 PS2CLT4 The file cannot contain more that 255 workstation names. PAGE 161 - TOPIC 7.3.2 - connection id Add the following note after CONNECTION description NOTE: The first character of the connection cannot be the "at-sign" character as Communications Manager does not allow a LU alias beginning with that character. PAGE 224 - TOPIC 4.8.2.2 - CDM Commands Add the following note after LU_ALIAS description NOTE: The first character of the LU_Alias cannot be the "at-sign" character as Communications Manager does not allow a LU alias beginning with that character. CHAPTER 2. CORRECTIONS TO THE CDM USER'S GUIDE 22 CSD PAGE 291 - TOPIC 9.6 - FORMAT,PARAMETERS At the very end of the section, ADD the following note: NOTE: NVDMLZW utility must be invoked as described below: >> NVDMLZW ---S:<SourceFile>------------------------------------>< | | | | -- /C --- --- /T:<TargetFile>-- | | -- /D --- NEW APPENDIX - LAN Server Security Support NetView DM/2 Version 2.1 supports the implementation of Access Control Lists (ACLs) in the LAN Server 3.0 product. NetView DM/2 ensures that existing ACLs are maintained at the target during installation by replication operations. ACLs are not included in change files during the build process and therefore cannot be distributed from a source to a target. In addition, no ACL information is transmitted with an object during file services operations (RETRIEVE and SEND). However, NetView DM/2 has no control over the writing of files during CID installations or installations by external programs. During such installations, NetView DM/2 simply runs the install program, which must manage the ACL information itself. Refer to the documentation provided with the external program for additional information. The LAN administrator must ensure that either NetView DM/2 is started as an administrator process or that it has the proper authorizations to perform the operations on ACLs. See "Enabling NetView DM/2 to Run in Privileged Mode" on page 25 for details. The following change management and file services scenarios illustrate the handling of ACLs by NetView DM/2: Nonremovable Install in Active Area When an installation takes place in the active area, ACLs at the target are preserved if the object already exists. If the target object does not already exist, ACLs are created according to the LAN Server rules. Removable Install in Active Area During this type of installation, only the files and their extended attributes (EAs) are packed in the backup file, not the ACL information. CHAPTER 2. CORRECTIONS TO THE CDM USER'S GUIDE 23 CSD Remove in Active Area During a Remove operation, all the objects contained in the backup are preserved, along with their EAs. ACLs are maintained at the target as they exist at Remove time. Install in Service Area (Removable and Nonremovable) + Activate During this type of install, the ACL information present at Activate time, not at Install time, is preserved at the target Install in Trial Area During this type of installation, all ACL information is preserved. You cannot add ACL information to the trial area (workstationname.trl) created by ___________________ NetView DM/2 on the target drive. You can add information to the target directory or to any of the subdirectories or files under it, then NetView DM/2 transfers the ACLs from the trial area to the active area or from the trial area to the service area (plus Activate) during installation. CID Installation In the case of CID installations, you can use the PREPACL utility, which is supplied with the LAN Server 3.0 product, to backup ACL information before installation and to restore it after installation. The syntax, which must be performed manually, is the following for Backup: PREPACL /P /D:<NvDM/2 Installation dir> /B:<backup file> and is the following for Restore: PREPACL /R /B:<backup file> During the first call to PREPACL (for preprocessing), the ACLs are backed up in the "backup file" and are deleted from the NvDM/2 installation directory and from its files. During the second call to PREPACL (for postprocessing), the ACLs are restored on the NetView DM/2 installation directory and on its files. See the LAN Server 3.0 documentation for additional details. CHAPTER 2. CORRECTIONS TO THE CDM USER'S GUIDE 24 CSD Enabling NetView DM/2 to Run in Privileged Mode When LAN Server 3.0 with local security is installed, NetView DM/2 must start with administrator privileges. The procedure to start a privileged program is documented in the LAN Server manual Network Administrator Reference Volume ______________________________________ 3: Network Administrator Tasks. Following is a summary of that procedure. ______________________________ A program can be run as privileged from the command line or at startup. In any case, this can be done only by the administrator. FROM THE COMMAND LINE: After the administrator logs on, he issues the command: PRIV cdm start NetView DM/2 starts with administrator privileges and maintains them even after the administrator logs off. AT STARTUP: When LAN Server 3.0 with local security is installed, a file named PRIVINIT.CMD is created in the boot root directory. In this file, the administrator must insert the statement: CDM START In the file STARTUP.CMD you must insert the statement: ___________ RUNPRIV.EXE At startup, the RUNPRIV.EXE is invoked and only this program is enabled to run PRIVINIT.CMD. NetView DM/2 starts with administrator privileges and keeps them also if the administrator doesn't log on. It is important to remember that the NetView DM/2 server change controller is inoperative if the administrator is not logged on, because the NetView DM/2 server requires the database manager, which requires the administrator to be locally logged on. CHAPTER 2. CORRECTIONS TO THE CDM USER'S GUIDE 25 CID MIGRATION TO COMMUNICATIONS MANAGER/2 PART 2. LDU USER'S GUIDE This part details changes that need to be made to the LDU User's Guide to reflect changes and corrections made after the documentation for NetView DM/2 Version 2.0 was sent for publication. Considerations for Migrating to Communications Manager/2 on a Focal Point-Attached Workstation This section shows how to migrate from Communications Manager of Extended Services to Communications Manager/2 on a NetView DM/2 CC server in a focal point-attached workstation. It is also applicable to a release refresh of Communications Manager/2 (for example, to install Communications Manager/2 1.1 on top of 1.0). The purpose of this section is to address the problem of reinstalling Communications Manager from the NetView DM/2 CC server, when this process at the same time requires Communications Manager itself to be active for NetView ______ DM/2 to receive the installation request, and to be inactive for the CMSETUP ________ procedure that upgrades Communications Manager. Communications Manager receives the installation request and the CDM agent processes the request without the change controller being active. If a failure occurs on the Communications Manager/2 installation, the change controller is reactivated to report back to the host the result of the installation. NOTE: The change controller needs Communications Manager to receive the request from the focal point; the CDM agent does not. Copy the ANXCM2.CMD procedure, provided with this CSD in its last CSD diskette of those labelled "CC Server & OS/2 CC Client APAR FIXES", under the CM/2 image directory where CMSETUP.EXE is stored. The procedure ANXCM2.CMD is called instead of the CMSETUP.EXE program. The parameters passed to the procedure are the same as CMSETUP plus the /BD:<b> (boot drive) that is needed by the procedure itself. The procedure calls CMSETUP, passing it the same parameters except the /BD:, which is filtered out. Then you can run the Communications Manager/2 installation using either the NetView DM/2 change file profile (ANXCM2.PRF) and CM/2 response file (ANXCM2.RSP) that are also provided in the last CSD diskette of those labelled "CC Server & OS/2 CC Client APAR FIXES" or your own similar files. ANXCM2.CMD first backs up your CONFIG.SYS file, then changes the current CONFIG.SYS file removing the parameter PROGRAM from the SET AUTOSTART key in _______ _____________ order to not allow automatic call to any program. ANXCM2.CMD also backs up your STARTUP.CMD file, and then creates a new minimal STARTUP.CMD, allowing only the CDM agent to be started after the reboot to process the CM/2 install request. (C) Copyright IBM Corp. 1991, 1995 26 CID MIGRATION TO COMMUNICATIONS MANAGER/2 In certain cases, you might need some of the original functions in your STARTUP.CMD (NET USE commands) to stay intact while allowing only the CDM agent to be started at the end of the new minimal STARTUP.CMD. ANXCM2.CMD is flexible enough to allow you to change the way it works to cater to your environment. In the procedure, you will find two defined STEM variables: "dropword." and "addline." They are used by the procedure in the following way: Each statement that includes one of the "dropword.i" words is deleted from the new minimal STARTUP.CMD. The dropword.0 must be set to the number of "dropword." to analyze. If "dropword.0" is set to 0, the original STARTUP.CMD is renamed to STARTUP.ANX and replaced with a minimal STARTUP.CMD with only the lines defined by the "addline." stem variable. If "dropword.0" is different from 0, then all the statements containing the "dropword." words are dropped, and at the bottom of the minimal STARTUP.CMD file, the "addline" is added. Pay special attention to the EXIT condition in your original STARTUP.CMD and drop the extra EXIT if necessary; otherwise, the CDM agent will not be executed at all because it is added at the very bottom of the file. The ANXCM2.CMD procedure already has "dropword." samples for the current NetView DM/2 installation. PART 2. LDU USER'S GUIDE 27 CHAPTER 3. CORRECTIONS TO THE LDU USER'S GUIDE PAGE 22 - TOPIC 3.5.3 - OS/2 SE 2.0 or 2.1 with LAN Services 3.0 or Later, or with NTS/2 1.0 CHANGE the note at the end of the section as follows: NOTE: It is possible to create a 4MB startup diskette with a seed of the OS/2 2.0 or 2.1 operating system. SEDISK does not provide an automatic way to create it. You must create it as follows, after you have built the two startup diskette as described above: 1. Copy the first startup diskette to a temporary directory of a hard disk. 2. Copy the second startup diskette to the same temporary directory. 3. Insert the target 4MB diskette to the A: drive. 4. Enter the following commands: CD <TempDir> SYSINSTX A: where <TempDir> is the temporary directory. 5. Copy all files from the temporary directory to A:. 6. Rename the file OS2KRNLI to OS2KRNL on the target 4MB diskette. PAGE 46 - TOPIC 4.3.11 - TIMEOUT TIMEOUT=<n>,<m> | OFF,OFF Use the <n> TIMEOUT variable to change the maximum length of time that an LDU distributor waits for a receiver connection request. This value is initialized when a receiver connection request is accepted. When the distributor is started, receiver connection requests are processed in the order in which they are received. When the length of time equal to the value <n> of TIMEOUT elapses with no connection request, the distributor stops waiting for connection requests and starts the distribution process, if at least one receiver is connected. Use the <m> TIMEOUT variable as a multiplier of <n> to determine how long the distributor should wait before cancelling the distribution, if no receiver is connected. When the length of time equal to <m>*<n> elapses, without a receiver connected, the distributor stops. (C) Copyright IBM Corp. 1991, 1995 28 The <n> variable is an integer in the range 10-9999 while the <m> variable is an integer in the range 10-9999, where the time interval is expressed in seconds. You can press F10 to start the distribution process at any time before the number of seconds specified in both the variables has elapsed. If you set both the TIMEOUT variables to OFF, the distributor waits for connection requests until you press F10. If a qualifying file list is used and all receivers in the qualifying file list are connected, the distribution is started, even if the TIMEOUT condition has not been satisfied. Similarly, if all the sessions specified by the SESSIONS variable are used, by receiver connections, the distribution is started. The default values for TIMEOUT are <15>,<OFF> CHAPTER 3. CORRECTIONS TO THE LDU USER'S GUIDE 29 INSTALLATION GUIDE PART 3. INSTALLATION GUIDE This part details changes that need to be made to the Installation Guide to reflect changes and corrections made after the documentation for NetView DM/2 Version 2.0 was sent for publication. (C) Copyright IBM Corp. 1991, 1995 30 INSTALLATION GUIDE CHAPTER 4. NETVIEW DM/2 INSTALLATION CONTROL Copying the Client Feature from 3.5-Inch to 5.25-Inch Diskettes This CSD is delivered on 3.5-inch diskettes only, but it includes a utility to copy the DOS CC client onto 5.25-inch diskettes, should one prefer to use this type of media. This utility, named NVDMCDSK, is located in the last diskette of the CSD, labelled "CC Server and OS/2 CC Client APAR Fixes." The DOS CC client is contained in the diskettes labelled "DOS CC Client APAR Fixes" of the CSD. When NVDMCDSK is invoked, a number of messages instructs you to insert the source and destination diskettes, piloting the copy. The 5.25-inch destination diskettes must have been already formatted before invoking NVDMCDSK. You will need five 5.25-inch diskettes, formatted to 1.2 MB. The syntax of NVDMCDSK is as follows: +---------------------------------------------------------------------------+ | | | >>--NVDMCDSK--hdrive:--source:--target:--feature-->< | | | +---------------------------------------------------------------------------+ Parameters HDRIVE: The letter identifying the hard disk partition to be used as a temporary file repository during the copy process. The utility does not check that there is enough free space in the partition; ensure that there is enough free storage before invoking NVDMCDSK. The amount of hard disk storage required to copy the DOS CC client is 3.0MB. SOURCE: The name of the drive where the source 3.5-inch diskettes will be inserted. TARGET: The name of the drive where the destination 5.25-inch diskettes will be inserted. FEATURE The name of the client feature that is to be copied; with this CSD the only available choice is DOS (for the DOS CC client) (C) Copyright IBM Corp. 1991, 1995 31 INSTALLATION GUIDE NOTES: 1. All the listed parameters are mandatory. 2. Be sure to enter the correct drive letters; NVDMCDSK does not check for drive letter validity. 3. Be sure to insert the correct source diskettes; NVDMCDSK does not check for diskette content. CHAPTER 4. NETVIEW DM/2 INSTALLATION CONTROL 32 INSTALLATION GUIDE CHAPTER 5. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE PAGE 127 - TOPIC 2.2.4 - Copying files before installation: Sourcedir The default source dir for NVDMDCPY has been changed so: the sourcedir item in the Installation and Customization Guide must be changed into: "if this parameter is not specified, the current directory is assumed." PAGE 199 - TOPIC 2.4.7.2 - WRONG NETBIOS TABLE In the table at page 199 of the Installation Manual (SH19-6915-02) are reported bad values to calculate the NetBIOS resources needed by NetView DM/2 at the CC Server and at the CC Client. Hereafter you will find the real formulas to calculate the resources for the CC Server: CC Server ----------------- Sessions MaxClients + 2 (as in the table) Link Stations MaxClients + 1 (as in the table) Commands MaxRequests + 29 2 more than in the table Names 7 3 more than in the table To better understand how this resources are requested, this are the details: 1) For each instance of the Command Line doing a LIST_WS or each instance of the Dialog with the CCDomain window open: Sessions = 1, Commands = 10, Names = 1. 2) For the ANXIFS Server component: Sessions = MaxClients, Commands = MaxRequests + 7, Names = 2. 3) For the CC Server component: Sessions = 1, Commands = 12, Names = 4. This basically means that, if you look at the NetBIOS resources with our product down and than look again after a CDM START, you'll see an increment like the following: Sessions = MaxClients + 1, Commands = MaxRequests + 19, Names = 6. Stated this, it's easy to understand that the table refers to the needed resources with only one instance of the Command Line LIST_WS or Dialog CC Domain window running. (C) Copyright IBM Corp. 1991, 1995 33 INSTALLATION GUIDE Hereafter you will find the real formulas to calculate the resources for the CC Client: CC Client ----------------- Sessions 2 (as in the table) Link Stations 2 (as in the table) Commands 13 4 more than in the table Names 6 2 more than in the table To better understand how this resources are requested, this are the details: 1) For the ANXIFS Requester component: Sessions = 1, Commands = 1, Names = 2. 2) For the CC Server component: Sessions = 1, Commands = 12, Names = 4. The suggestion in the note 1 should change highlighting the fact that 10 GDTs are required for one instance of Command Line LIST_WS or Dialog CC Domain window refresh. PAGE 30 - TOPIC 1.1.5.5 - Copying the Client Feature from 3.5-Inch to 5.25-Inch Diskettes CHANGE the syntax diagram as follows: +---------------------------------------------------------------------------+ | | | >>--NVDMCDSK--hdrive:--source:--target:--feature-->< | | | +---------------------------------------------------------------------------+ CHAPTER 5. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 34 INSTALLATION GUIDE PAGE 139 - TOPIC 2.2.6.2.2 - Using NVDMIDOS CHANGE the second paragraph as follows: The following considerations apply when the AUTOEXEC.BAT file is updated by the NetView DM/2 installation process: o The statement that runs NetView DM/2 at the DOS CC Client ("ANXCMLDR") may be placed after a statement that runs a batch file, such as "DOSSHELL", which does not return control to "AUTOEXEC.BAT". In this event NetView DM/2 cannot run. To correct this problem, you must manually edit "AUTOEXEC.BAT", moving any batch files so that they are executed after NetView DM/2. o The command RUN for Microsoft Windows** is not inserted in "AUTOEXEC.BAT", even if Microsoft Windows was already installed at the moment of NetView DM/2 installation. You can edit the AUTOEXEC.BAT file and add it manually. In this case, ensure to insert the RUN command after the NETBIND command (if existing), and after the PATH statement, so that the NetView DM/2 statements are correctly inserted after NETBIND and PATH, and before RUN. PAGE 140 - TOPIC 2.2.6.2.2 - Using NVDMIDOS At the top of the page, ADD the following note to the existing one: NOTE: If the workstation where you are going to use NVDMIDOS has the SHARE program installed, you must remove SHARE from the workstation memory before starting NetView DM/2 installation, as follows: o If you started SHARE from the command line, restart the workstation o If statements related to SHARE are included in the AUTOEXEC.BAT and CONFIG.SYS files, remove them, using the REM command. You can restore the SHARE references into the system files after completing NetView DM/2 installation and before restarting the workstation. CHAPTER 5. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 35 INSTALLATION GUIDE PAGE 148 - TOPIC 2.2.8 - The AgentTimeout Parameter In the paragraph referrring to the AgentTimeout parameter, ADD the following note before the existing one: NOTE: It is recommended to set the AgentTimeout value to -1, if you want to perform CM requests on the CC server in an unattended mode. This is because, when the CDM Agent terminates (according to the value specified for this parameter) on a CC Server, it is not automatically restarted when the Transmission Controller receives a request for the network. The Transmission Controller starts the Change Controller only, and, if the request is addressed to the CC Server, the CDM Agent will remain inactive and the request will remain in pending status until you issue a CDM START AGENT command locally. PAGE 240 - TOPIC 2.4.4.9.5 Required NetBIOS Values One more command is requested on the CC Client so the table of required NetBIOS parameter is: +---------------------------------------------------------------------------+ | Table 2. Required NetBIOS Values | +------------------+------------+-----------+----------------+--------------+ | | CC SERVER | CC CLIENT | LDU | LDU RECEIVER | | | | | DISTRIBUTOR | | +------------------+------------+-----------+----------------+--------------+ | Maximum sessions | Maximum | 2 | Maximum number | 1 | | | number of | | of LDU | | | | CC clients | | receivers | | | | (as in | | | | | | .INI file) | | | | | | + 2 | | | | +------------------+------------+-----------+----------------+--------------+ | Maximum link | Maximum | 2 | Maximum number | 1 | | stations | number of | | of LDU | | | | CC clients | | receivers | | | | (as in | | | | | | .INI file) | | | | | | + 2 | | | | +------------------+------------+-----------+----------------+--------------+ | Maximum commands | 28 + | 11 | Maximum number | 1 | | | MaxRequests| | of LDU | | | | (as in | | receivers | | | | .INI file) | | | | +------------------+------------+-----------+----------------+--------------+ | Maximum names | 6 | 5 | 1 | 2 | +------------------+------------+-----------+----------------+--------------+ | GDT selectors | At least | Default | Default | Default | | | 10 | | | | +------------------+------------+-----------+----------------+--------------+ CHAPTER 5. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 36 INSTALLATION GUIDE CHANGE the end of the paragraph as follows: To improve NetView DM/2 performance on a DOS CC Client set PBA (PiggyBackAcknowledgement) to a greater-than-zero value, when customizable. The parameter that controls this function has values between zero and five, with three being the default, and zero indicating that the facility should not be used. Thus, PBA should be customized in the following manner when the product providing NetBIOS allows to do so: DEVICE=\DXMT0MOD.SYS S=16 C=14 PBA=a value from 1 to 5 ___________________ PAGE 139 - TOPIC 2.2.6.2.2 - NVDMIDOS command The syntax of the NVDMIDOS command must be changed adding the following parameters on the command line. This parameters can be used in both the full or configuration only installation. 1. ServerName __________ 2. ClientName __________ NOTE: This two parameters has been added to give the opportunity to install the (CC) DOS Client without write a response file NVDMIDOS /Servername:SRV1 /ClientName:CLT1 PAGE 179 - TOPIC 2.3.3 - Customizing the CDM Message Exit Routine After bullet 5., ADD the following note. NOTE: Your message user-exit can prevent warning blue pop-up panels from being displayed after during an ACTIVATE or INSTALL which requires a reboot. That occurs when the user-exit returns code "2" when the message id is ANX0150 ANX1312 CHAPTER 5. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 37 INSTALLATION GUIDE PAGE 213 - TOPIC 2.4.9.9.5 - NETBIOS Profile In the table 18 are reported bad values to calculate the NetBIOS resources needed by NetView DM/2 at the CC Server and at the CC Client. Hereafter can be found the real formulas to calculate the resources for the CC Server: CC Server ----------------- Sessions MaxClients + 2 Link Stations MaxClients + 1 Commands MaxRequests + 29 Names 7 To better understand how this resources are requested, this are the details: 1. For each instance of the Command Line doing a LIST_WS or each instance of the Dialog with the CCDomain window open: Sessions = 1, Commands = 10, Names = 1. 2. For the ANXIFS Server component: Sessions = MaxClients, Commands = MaxRequests + 7, Names = 2. 3. For the CC Server component: Sessions = 1, Commands = 12, Names = 4. This basically means that, if you look at the NetBIOS resources with our product down and than look again after a CDM START, you'll see an increment like the following: Sessions = MaxClients + 1, Commands = MaxRequests + 19, Names = 6. Stated this, it's easy to understand that the table refers to the needed resources with only one instance of the Command Line LIST_WS or Dialog CC Domain window running. Hereafter can be found the real formulas to calculate the resources for the CC Client: CC Client ----------------- Sessions 2 Link Stations 2 Commands 13 Names 6 To better understand how this resources are requested, this are the details: CHAPTER 5. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 38 INSTALLATION GUIDE 1. For the ANXIFS Requester component: Sessions = 1, Commands = 1, Names = 2. 2. For the CC Server component: Sessions = 1, Commands = 12, Names = 4. The suggestion in the note 1 should change highlighting the fact that 10 GDTs are required for one instance of Command Line LIST_WS or Dialog CC Domain window refresh. Any reference to this table in the whole manual should be changed as well PAGE 214 - TOPIC 2.4.9.9.5 - NETBIOS Profile NOTE: Sometimes, when performing the CDM LIST_WS command to see the WS status (or showing them from the dialog) only about half of them result as active even if all are up. This is normally due to an incorrect setting in the NetBIOS configuration file (PROTOCOL.INI) The parameters that has to be checked are the following: DATAGRAMPACKETS default=2 NvDM/2 suggested(Client/Server)=15 NETBIOSTIMEOUT default=500 NvDM/2 suggested(Server)=(see below) NETBIOSRETRIES default=8 NvDM/2 suggested(Server)=(see below) There is no way to tell exactly which value to use for NETBIOSTIMEOUT and NETBIOSRETRIES. When a given Client is checked with the LIST_WS command a UI frame is sent over the Network. The Client must answer that frame in NETBIOSTIMEOUT * NETBIOSRETRIES milliseconds to be shown as ACTIVE at the Server. Therefore these values has to be trimmed in conformity with the typical delays of the Network. Regarding the DATAGRAMPACKETS parameter, the value of 15 has been proved to be big enough to serve the NetView DM/2 purposes. Anyhow, it should be increased if there are other programs that uses the NetBIOS Datagram support. CHAPTER 5. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 39 MESSAGES AND ERROR RECOVERY GUIDE PART 4. MESSAGES AND ERROR RECOVERY GUIDE This part details changes that need to be made to the Messages and Error Recovery Guide to reflect changes and corrections made after the documentation for NetView DM/2 Version 2.0 was sent for publication. (C) Copyright IBM Corp. 1991, 1995 40 USER'S MESSAGES AND CODES CHAPTER 6. USER'S MESSAGES AND CODES New Messages The following messages have been added: Message ANX1322 ANX1322 THE FILE '%1' COULD NOT BE OPENED. '%0'. EXPLANATION: The system could not open the file containing the list of directories to remove. SYSTEM ACTION: No directories are removed. USER RESPONSE: Look for more details in the NetView DM/2 error log. Message ANX1323 ANX1323 THE DIRECTORY '%1' COULD NOT BE REMOVED. RC = '%2'.'%0'. EXPLANATION: These directories cannot be removed during the execution of the ACTIVATE command after a REMOVE IN SERVICE. SYSTEM ACTION: No directories are removed. USER RESPONSE: Find the reason for rc='%2'. Message ANX1324 ANX1324 EMPTY DIRECTORIES WERE NOT REMOVED. '%0'. EXPLANATION: No directory could be removed because there was a problem in creating the directory list file. SYSTEM ACTION: No directories are removed. USER RESPONSE: Look for more details in the NetView DM/2 error log. Changed Messages The following messages have been changed: (C) Copyright IBM Corp. 1991, 1995 41 USER'S MESSAGES AND CODES Message ANXW5215 This message has been modified, and should read: ANXW5215 THE MAXIMUM HAS BEEN REACHED FOR THE NUMBER OF ITEMS THAT CAN BE MAINTAINED IN THE LIST. THE LIST CONTAINS THE FIRST '%1' ENTRIES OF THE COMPLETE LIST. EXPLANATION: Only a limited number of items can be displayed in the listbox. USER RESPONSE: Select fewer items. SYSTEM ACTION: Only a subset of selected items are displayed in the dialog box. Message ANX0203 This message has been modified, and should read: ANX0203 THE QUALIFIER NAME '%1' IS NOT ALLOWED TO BE GREATER THAN 8 CHARACTERS.%0. EXPLANATION: The Qualifier Name must not be greater than 8 characters because the Database Manager truncates the name and could overwrite another database. SYSTEM ACTION: The CDM Agent processes the next request. USER RESPONSE: Change the Qualifier Name to a valid name. Message ANX1264 This message has been modified, and should read: ANX1264 ANX1264I: THE VALID CDM SUB-COMMANDS ARE: ACCEPT INSTALL REMOVE ACTIVATE LIST REROUTE ADD_DEST LIST_DEST RETRIEVE ADD_IT LIST_IT SEND BUILD LIST_QUEUE SHUTDOWN CATALOG LIST_REQ START CONFIG PURGE STATUS DELETE RELEASE_REQ STOP DELETE_DEST QUERY_CF TRACE_OFF DELETE_IT QUERY_REP TRACE_ON DELETE_REQ QUERY_REQ TRANSMISSION CHAPTER 6. USER'S MESSAGES AND CODES 42 USER'S MESSAGES AND CODES HOLD QUIESCE UNCATALOG HOLD_REQ RELEASE UNCATALOG_CM INITIATE EXPLANATION: not available SYSTEM ACTION: not available USER RESPONSE: not available Message ANX0253 This message has been modified, and should read: ANX0253 THE EXTERNAL PROGRAM '%1' FAILED WITH EXIT CODE '%2'. REFER TO THE LOG FILE(S) PRODUCED BY THE EXTERNAL PROGRAM FOR ADDITIONAL DETAILS ON THE ERROR. CHECK THE CHANGE FILE PROFILE TO LOCATE THEM.%0 ANX0253H: EXPLANATION: The External Install Program ended with the reported exit code. Details on the error can be found in the specific log produced by the installation program that the CDM Agent was running. This log is specified in the change file profile via the "/Lx:LogFilex" parameter that is passed to the program. Normally the log is produced at the remote server site for a central problem determination. SYSTEM ACTION: The request fails and an INSTALL report is sent to the Host with the appropriate SNA code if the exit code is CID-architected. USER RESPONSE: Check the produced log and the External Application documentation for more detailed information on the error. Deleted Messages No messages have been deleted. CHAPTER 6. USER'S MESSAGES AND CODES 43 INSTALLER'S MESSAGES AND CODES CHAPTER 7. INSTALLER'S MESSAGES AND CODES New Messages The following messages have been added: Message ANX7280 This message has been added, and should read: ANX7280 IBM NETBIOS RESULTS NOT INSTALLED QUERYING INSTALLATION BOOT DRIVE. PLEASE BE SURE THAT A SUPPORTED NETBIOS IS ACTUALLY INSTALLED.%0 EXPLANATION: The installation program has detected that no IBM NetBIOS results installed while checking system files found in target machine bootdrive. SYSTEM ACTION: The installation continues. USER RESPONSE: User is asked to verify that IBM or one those supported NetBIOS is installed. Changed Messages No messages have been changed. Deleted Messages No messages have been deleted. PAGE 324 - TOPIC 2.1.1.2 - messages Message ANXE7841 (C) Copyright IBM Corp. 1991, 1995 44 INSTALLER'S MESSAGES AND CODES ANXE7841 THE SOURCE DIR IS INVALID. PLEASE TRY AGAIN INSERTING THE DOS (CC) CLIENT INSTALLATION DISKETTE EXPLANATION: The DOS (CC) Client installation has been started not using the program stored on the installation diskette. SYSTEM ACTION: The operation is not executed. USER RESPONSE: Insert The DOS (CC) Client installation diskette Changed Messages No messages have been changed. PAGE 297 - TOPIC 2.1.1.2 - messages Message ANXE8289 This explantion of this message has been modified. It must be added read: The message can be displayed also if the NetBIOS is not configured Deleted Messages No messages have been deleted. CHAPTER 7. INSTALLER'S MESSAGES AND CODES 45 CHAPTER 8. CORRECTIONS TO THE MESSAGES AND ERROR RECOVERY GUIDE PAGE 245 - SECTION xxxxx - Error Scenarios After the section "Power Failure at a PWS During OS/2 Installation"; ADD the following: Problems during the Reboot when Migrating from OS/2 EE 1.3 to OS/2 2.1 on a CC Client When migrating from OS/2 EE 1.3 to OS/2 Version 2.1 on a CC Client, a problem occurs during last reboot. This happens because the "CONFIG.SYS" file includes the statement "LOG" which is not recognized as valid in the migration process. The problem can be solved by pressing the Enter key at the system request, during the reboot. PAGE 105 - TOPIC 1.1.1.4 - messages Change explanation of message ANX0308; replace the sentence "the special characters are $, &lsterling., &sect., _..." with the sentence "the special characters are $, @, #, _..." PAGE 103 - TOPIC 1.1.1.4 - messages Message ANXI0292 ANXI0292 THE NVDMLZW ALGORITHM IS NOT EFFICIENT TO COMPRESS THE FILE <NAME FILE> RELATED TO GLOBAL NAME <NAME>. EXPLANATION: The algorithm used to compress the file is not efficient. The file will be sent decompressed. SYSTEM ACTION: Processing continues. USER RESPONSE: None (C) Copyright IBM Corp. 1991, 1995 46 PAGE 84 - TOPIC 1.1.1.4 - messages Message ANXE0168 The explanation of the message has been modified, and should read: The operation has not been completed; processing continues with other requests. The request originator is notified with a report PAGE 84 - TOPIC 1.1.1.4 - messages Message ANXE0169 The explanation of the message has been modified, and should read: The operation has not been completed; processing continues with other requests. The request originator is notified with a report PAGE 84 - TOPIC 1.1.1.4 - messages Message ANXE0170 The explanation of the message has been modified, and should read: The operation has not been completed; processing continues with other requests. The request originator is notified with a report CHAPTER 8. CORRECTIONS TO THE MESSAGES AND ERROR RECOVERY GUIDE 47 Index (C) Copyright IBM Corp. 1991, 1995 48