Copyright (c) IBM Corporation 1991 - 1995 All rights reserved NetView Distribution Manager/2 Version 2.1 Documentation Update Corrective Service Diskettes PTF XR20466 (Syslevel XR00002) April 21, 1995 CONTENTS CONTENTS ABOUT THIS FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . V Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v IBM Service Support . . . . . . . . . . . . . . . . . . . . . . . . . . . v Additional Support . . . . . . . . . . . . . . . . . . . . . . . . . . . v ----------------------------------------------------------------------------- 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 . . . . . . . . . . . . . . . . . 5 Preparing NetView DM/2 for the CSD . . . . . . . . . . . . . . . . . . . 5 Installing the CSD . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Upgrading CDM Online Helps When Servicing Product Images by CSD . . . . 10 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Migration from One CSD to Another . . . . . . . . . . . . . . . . . . . 11 Configuring The CC Server . . . . . . . . . . . . . . . . . . . . . . . 11 Upgrading DOS CC Client, File Only, or Related Images . . . . . . . . . 12 Servicing a DOS CC Client . . . . . . . . . . . . . . . . . . . . . . . 12 Getting Started Samples Diskette . . . . . . . . . . . . . . . . . . . 14 Quick Help For Installation of IBM Products Via NetView DM/2 . . . . . 14 ----------------------------------------------------------------------------- PART 2. CONCEPTS AND OVERVIEW . . . . . . . . . . . . . . . . . . . . 16 CHAPTER 2. CORRECTIONS TO THE CONCEPTS AND OVERVIEW BOOK . . . . . . . 17 PAGE 29 - TOPIC 3.3 - Workstations and Interconnections Supported by the Remote Administrator . . . . . . . . . . . . . . . . . . . . . . . . . 17 PAGE 33 - TOPIC 3.10 - Using a Remote Administrator Workstation in a Multiserver Network . . . . . . . . . . . . . . . . . . . . . . . . . 17 PAGE 121 - TOPIC C.1 - Software Requirements . . . . . . . . . . . . . 17 PAGE 125 - TOPIC C.3 - Hardware Requirements . . . . . . . . . . . . . 18 ----------------------------------------------------------------------------- PART 3. CDM USER'S GUIDE . . . . . . . . . . . . . . . . . . . . . . . 21 CHAPTER 3. WHAT TO LOOK FOR WHEN MIGRATING TO NETVIEW DM/2 VERSION 2.1 22 Software Prerequisites for NetView DM/2 Version 2.1 . . . . . . . . . . 22 NetView DM/2 Version 2.1 Commands . . . . . . . . . . . . . . . . . . . 22 The CDM Dialog Interface for a CC Server . . . . . . . . . . . . . . . 26 CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS . . . . . . . . . . . . . . . 29 The NVDMRDSK Utility . . . . . . . . . . . . . . . . . . . . . . . . . 29 The NVDMUPO Utility . . . . . . . . . . . . . . . . . . . . . . . . . . 36 The Enhanced NVDMUFM Utility . . . . . . . . . . . . . . . . . . . . . 46 DOS Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 DiskCamera Limitation . . . . . . . . . . . . . . . . . . . . . . . . 50 CDM Local CC Domain: Shows Workstation Status Only if Explicitly Requested . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 CDM Message Log: Filtering Messages According to the Severity . . . . 52 Language Support: Light Locale Support for English and Kanji . . . . . 53 (C) Copyright IBM Corp. 1991, 1995 ii CONTENTS NVDMUPFS: File System Configurator for Maintenance Systems . . . . . . 54 OS/2 DiskCamera . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 New NetView DM/2 Force Install Parameter with the INSTALL Task . . . . 62 CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE . . . . . . . . . . . . 66 Page 98 - TOPIC 4.8.4.1 - Deleting the Installation History . . . . . . 66 Page 100 - TOPIC 4.8.5.1 - Listing All the Objects Installed on a Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Page 222 - TOPIC 8.5 - ADD_DEST or ADDDEST . . . . . . . . . . . . . . 66 Page 230 - TOPIC 8.8 - BUILD . . . . . . . . . . . . . . . . . . . . . 67 Page 235 - TOPIC 8.8 - BUILD . . . . . . . . . . . . . . . . . . . . . 67 Page 252 - TOPIC 8.12 - CONFIG . . . . . . . . . . . . . . . . . . . . 67 Page 253 - TOPIC 8.12 - CONFIG . . . . . . . . . . . . . . . . . . . . 67 Page 285 - TOPIC 8.27 - LIST_WS or LISTWS . . . . . . . . . . . . . . . 67 Page 289 - TOPIC 8.30 - QUERY_REP or QUERYREP . . . . . . . . . . . . . 68 Page 355 - TOPIC A.1 - Detailed Scenarios . . . . . . . . . . . . . . . 68 Before Migrating NetView DM/2 from Version 2.0 to 2.1 . . . . . . . . . 69 Page 373 - TOPIC A.2 - Installing and Migrating Software for Multiple CID-Enabled Products . . . . . . . . . . . . . . . . . . . . . . . . . 70 Page 421 - TOPIC A.4 - Installing TCP/IP Version 2.0 . . . . . . . . . 70 Page 423 - TOPIC A.4 - Installing TCP/IP Version 2.0 . . . . . . . . . 70 Page 429 - TOPIC A.4 - Detailed Scenarios . . . . . . . . . . . . . . . 70 TCP/IP Version 2.0 Maintenance Environment Scenario . . . . . . . . . . 70 Page 327 - Chapter 9 - CDM Utilities . . . . . . . . . . . . . . . . . 105 ----------------------------------------------------------------------------- PART 4. LDU USER'S GUIDE . . . . . . . . . . . . . . . . . . . . . . . 106 CHAPTER 6. LDU USER'S GUIDE ENHANCEMENTS . . . . . . . . . . . . . . . 107 ANXADM: A New Tool to Prepare LDU Packages More Easily . . . . . . . . 107 ----------------------------------------------------------------------------- PART 5. INSTALLATION AND CUSTOMIZATION GUIDE . . . . . . . . . . . . . 111 CHAPTER 7. NETVIEW DM/2 INSTALLATION CONTROL . . . . . . . . . . . . . 112 Additional Configuration Parameters for Installation by Response File 112 Compatibility with Obsolete Software and Data Deletion Parameters . . . 113 New NOSTARTUP Installation Parameter . . . . . . . . . . . . . . . . . 113 CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE . . 114 PAGE 21 - TOPIC 1.1.6 - Prerequisites . . . . . . . . . . . . . . . . . 114 Incorrect Sample List Files for ADD_DEST Command . . . . . . . . . . . 117 PAGE 142 - TOPIC 2.2.4 - Copying Files Prior to Installation . . . . . 119 PAGE 154 - TOPIC 2.2.9.2.2 - Uploading of ANXCMLDR.COM By NVDMIDOS . . 119 PAGE 345 - TOPIC 2.5.3.3.1 - ANXLUSER.C . . . . . . . . . . . . . . . . 120 APPENDIX F - TOPIC APPENDIX1.6.3 - Locating Some Important Files . . . 123 ----------------------------------------------------------------------------- PART 6. MESSAGES AND ERROR RECOVERY GUIDE . . . . . . . . . . . . . . 125 CHAPTER 9. MESSAGES AND CODES . . . . . . . . . . . . . . . . . . . . 126 Changed Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 New Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 CONTENTS iii CONTENTS CHAPTER 10. INSTALLATION MESSAGES AND CODES . . . . . . . . . . . . . 151 New Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Changed Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 CHAPTER 11. CORRECTIONS TO THE MESSAGES AND ERROR RECOVERY GUIDE . . . 153 PAGE 304 - Topic 1.3.3.7 - Transmission Controller . . . . . . . . . . 153 ----------------------------------------------------------------------------- PART 7. NVDM/2 GETTING STARTED BOOK . . . . . . . . . . . . . . . . . 154 CHAPTER 12. CORRECTIONS TO THE NVDM/2 GETTING STARTED BOOK . . . . . . 155 PAGE 80 - Using More Functions of NetView DM/2 . . . . . . . . . . . . 155 INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 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 that corrects, or is supplementary to, the following NetView* DM/2 manuals dated July 1994: o Concepts and Overview (GH19-4009-01) o Getting Started (SH19-4067-00) o CDM User's Guide (SH19-5048-01) o LDU User's Guide (SH19-5049-01) o Installation and Customization Guide (SH19-6915-04) o Messages and Error Recovery Guide (SH19-6924-04) 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. IBM Service Support Please contact the local IBM Service Support Center before installing this CSD to determine if additional information or changes to the instructions in this document are available. 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 (C) Copyright IBM Corp. 1991, 1995 v 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 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 is obsolete. Among the other tasks, this NetView DM/2 CSD allows you to perform the following: 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 Another consideration is whether NetView DM/2 will be installed in an attended or unattended environment: (C) Copyright IBM Corp. 1991, 1995 2 CSD 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 in some manner 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, configuring the CC server when a CC server has been serviced. What is New in this CSD This CSD, XR20466, distributes some product fixes as referenced in the FIXES.TXT file located in the last CSD diskette, labelled CC Server RA & OS/2 CC Client APAR FIXES. In addition, this CSD distributes: Cumulated from CSD XR20460 o The refresh of the Getting started samples diskette labeled NetView DM/2 V2.1 Getting Started Samples. o The refresh of the CDM help panels for logging under Communication Manager in the Extended Services in the diskettes labeled CDM Communication Manager Helps disk 1, 2 and 3. o Microsoft NetBIOS is supported on DOS/WINDOW PWS. o The enhanced Unique-File Management facility which allows you to prepare response files for other workstations. See the NetView DM/2 Usage chapter for details. o The new NVDMUPO utility that helps you modify operating system files by entering specific keys in your response file. See the NetView DM/2 Usage chapter for details. o The new NVDMRDSK utility that creates DOS or OS/2 CC client boot diskettes from your OS/2 command line. See the NetView DM/2 Usage chapter for details. o The install function on OS/2 CC Client has been enhanced in order to support the installation of CID DOS and Windows applications. o The initiate function on OS/2 CC Client has been enhanced in order to support the execution of DOS and Windows programs. o A Quick Help manual and sample response files for installing IBM products with NetView DM/2. This manual is distributed in: CHAPTER 1. THE NETVIEW DM/2 CSD 3 CSD 1. A softcopy version that you can display on your workstation with IBM BookManager or IBM Library Reader 2. A Postscript version that you can print on your Postscript printer 3. An INF file that you can read with VIEW command of OS/2 The samples are distributed as a unique self-unpacking file. See "Quick Help For Installation of IBM Products Via NetView DM/2" on page 14 later in this chapter for details. New with CSD XR20466 o CDM Message Log,filter the messages according to the severity 'Include Messages' is the new dialog which permit filtering the messages in the MESSAGE.DAT according to severity (Error, Informational, or Warning). It may be displayed from the new function 'View/Include' in the CDM Message Log window. o Language Support: Light locale support for English and Kanji It is possible to request the NetView DM/2 to display the messages in the proper language. Actually only two languages are available: Kanji and English. If you want English commands, type LOCALE ENG from any OS/2 Command Prompt. If you want Kanji messages type LOCALE KNJ from any OS/2 Command Prompt. NOTE: The command must be processed with CDM stopped - Limitations The LOCALE support is only available at a CC Server. o NVDMUPFS: File System Configurator for maintenance systems NVDMUPFS is a procedure to configure the PWS in an unattended fashion. It has the same function of NVDMUPO and refers to the same messages. The only verb that cannot be used is AddProgram. o OS/2 Disk Camera Disk Camera for OS/2 is a component of NetView DM/2 that simplifies the process of replicating the installation of an OS/2 application package on a large number of workstations. o ANXADM, a tool to easily prepare LDU packages ANXADM is a utility to easily prepare LDU packages following a set of instructions collected in profile. o New NetView DM/2 Force Install parameter for the INSTALL task CHAPTER 1. THE NETVIEW DM/2 CSD 4 CSD NetView DM/2 V2.1 and NetView DM/MVS R6 have been enhanced to force the reinstallation of an object that has been already installed in production (that is, at the end of the installation cycle). For more information about the enhancements, see the detailed sections in this README.TXT file. +--- WARNING ---------------------------------------------------------------+ | | | CSD XR20466 enables NetView DM/2 2.1 code to run on OS/2 WARP v3.0 | | operating system in a standalone LAN environment. To run with all the | | other Host attached environments you need to apply a DB2/2 fix that is in | | progress while we are writing this document. Please check INFO APARs | | II08201 and II08454 to be updated on this subject. | | | +---------------------------------------------------------------------------+ Maintenance Level Serviced by This CSD This CSD cumulates fixes and enhancements since CSD XR20460; then, it applies to any maintenance level from XR00000_ to XR00001_ . Once implemented, any product full configuration or images, selected at CSD installation time, will be upgraded at the XR00002_ level. 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. Installing the CSD CHAPTER 1. THE NETVIEW DM/2 CSD 5 CSD +--- WARNING -----------------------------------------------------+ | | | While upgrading NetView DM/2 from a previous level it is very | | important to upgrade FIRST the CC Server and ONLY AFTER THIS | | the CC Client. | | | | In fact it is possible to run NetView DM/2 in the following | | scenarios: | | | | 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 GA or NetView DM/2 2.1 and "new" means | | CSD XR20466 (this CSD). | | | +-----------------------------------------------------------------+ +--- WARNING -----------------------------------------------------+ | | | DOS CC Client, File Only or related diskette images on | | a 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 THE DOS CC CLIENT ON THE CC SERVE|, | FROM THE MAIN SERVICE MENU, IF ANY ARE DETECTED BY SERVICE.| | | | Please refer to NetView DM/2 Installation and Customization Gu|de | for a complete overview of the aforementioned commands. | | | | | +-----------------------------------------------------------------+ +--- WARNING -----------------------------------------------------+ | | | IF YOU CHOSE TO REFRESH THE CODE AS DESCRIBED ABOVE, BE | | AWARE THAT YOU LOSE ANY CHANGES YOU HAVE INTRODUCED INTO THE| | 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 6 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 applies the CSD to the installed version of NetView DM/2 Version 2.1 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 is applied according to response file information. If you choose to use the default response file (RESPONSE.FIL) on the second CSD diskette set, the CSD is applied to all the installed versions and product images as well that are detected on the local hard disk. NOTE: Refer to REDBOOK GG24-3780 (Remote Installation and Maintenance) for more information on how to create a response file. NETVIEW DM/2 IMAGE ON FIXED DISK - DEFAULT CSD INSTALLATION (NVDMRCSD.EXE) This method applies the CSD to the installed version and also to a diskette image of NetView DM/2 V2.1 by booting the system from the first CSD diskette. 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 is installed on the diskette image of NetView DM/2, using the FSERVICE utility. CHAPTER 1. THE NETVIEW DM/2 CSD 7 CSD NETVIEW DM/2 IMAGE ON FIXED DISK - MODIFIED CSD INSTALLATION (NVDMPCSD.EXE) This method applies the CSD to the installed version and also to a diskette image of NetView DM/2 V2.1 from the command line. The CSD is 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, do the following: 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 is 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. UNATTENDED INSTALLATION OF THE 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 NVDMREC to install the LDU Receiver o NVDMINST to install CC Server or Entry Base CHAPTER 1. THE NETVIEW DM/2 CSD 8 CSD 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 (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 (NVDMINST or NVDMCLT) and by using the same response files that were used to install NetView DM/2 on these systems originally. 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. CHAPTER 1. THE NETVIEW DM/2 CSD 9 CSD 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 to install them. The files are NOT upgraded automatically by the CSD when servicing configured product installation or product images. You can choose to log NetView DM/2 messages and errors under CMLIB by upgrading your installation, using three supplemental diskettes labelled CDM COMMUNICATION MANAGER HELPS. To apply the refreshed Help files, proceed as follows: Step 1. Open an OS/2 window or full-screen session. Step 2. Insert the first diskette of those labelled CDM COMMUNICATION MANAGER HELPS into drive A:. Step 3. Switch to the A: drive. Step 4. Invoke COPYCLI or COPYSRV, passing the full path to install Helps, respectively to upgrade NetView DM/2 CC Client for OS/2 or NetView DM/2 CC server. Examples: COPYCLI C:\CMLIB COPYSRV C:\CMLIB Repeat steps 2 through 4 for all diskettes labelled CDM COMMUNICATION MANAGER HELPS Limitations 1. Whereas OS/2 V.1.3 and V.2.0 are serviceable either from the 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 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 certain non-IBM or newer IBM (PC/VP, industrial PC) workstations, it is not possible to install the CSD CHAPTER 1. THE NETVIEW DM/2 CSD 10 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. 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. Migration from One CSD to Another If you are migrating from one CSD to another, you cannot use the INITIATE command, because that generates an error. Use a remote INSTALL command. Configuring The CC Server If you have installed this CSD on a CC server in an attended manner, you need to run NVDMINST /CO from any OS/2 session to conclude the installation. You do not need to do this if you have installed the CSD in an unattended manner. WARNING: FAILING TO EXECUTE THIS STEP WILL RESULT IN PRODUCT FAILURE WHENEVER STARTING IT OR EXECUTING OTHER TASKS (FOR EXAMPLE, CDM LISTWS OR CDM STATUS). MESSAGE ANX1454 (UNEXPECTED ERROR) IS ISSUED AND THE FOLLOWING ERROR IS LOGGED INTO THE ERROR.DAT FILE: ** NETVIEW DM/2 LOGGED AT 17:18:20 28/03/1995 ** ERROR DETECTED IN NETVIEW DM/2 CM COMPONENT. THE ERROR WAS GENERATED IN MODULE ANXCLCC1. ADDITIONAL DATA : 41 4E 58 43 4C 43 43 31 30 30 30 34 F8 07 00 08 ANXCLCC10004›... 41 4E 58 43 53 30 44 42 41 4E 58 43 4C 43 43 31 ANXCS0DBANXCLCC1 41 4E 58 43 53 43 44 4E 10 00 14 00 CE FC FF FF ANXCSCDN........ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ .... 00 00 00 00 00 .... CHAPTER 1. THE NETVIEW DM/2 CSD 11 CSD NOTE: TO RECOVER FROM THIS FAILING EVENT RUN NVDMINST /CO FROM THE <PRODUCT_ROOT_DIR>\BIN PATH. 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 formats : NVDMIDFO /T:target_path /L:logfile /S:source_dir NVDMDCPY /T:target_path NOTE: Refer to the NetView DM/2 Installation and Customization Guide for a complete description of these commands. Servicing a DOS CC Client The service can be done 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 XR20466 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. CHAPTER 1. THE NETVIEW DM/2 CSD 12 CSD +--- WARNING -----------------------------------------------------+ | | | IF YOU CHOOSE TO REFRESH THE CODE AS DESCRIBED ABOVE, BE | | AWARE THAT YOU LOSE ANY CHANGES THAT YOU MADE TO THE | | FILES ANXIDMCF.CNF AND ANXIDMCF.AUT. | | | +-----------------------------------------------------------------+ NOTE: When using NVDMIDOS or NVDMDCPY,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 package. The CSD diskettes that are to be used according to the messages displayed during the installation process are as follows: DISKETTE NUMBERS IN CSD XR20466 1-5 DISKETTE NUMBERS IN AUGUST GA CODE 13-17 For a complete overview of the NVDMIDOS command syntax, refer to the NetView DM/2 Installation and Customization Guide, (SH19-6915-04). 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 XR20466. 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 XR20466 on the DOS CC client images 2. Prepare a change file to install the refreshed code, using a change file profile such as the following: 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 the NetView DM/2 CDM User's Guide (SH19-5048-01). CHAPTER 1. THE NETVIEW DM/2 CSD 13 CSD Getting Started Samples Diskette A refresh of the diskette included with the Getting Started book is shipped with this CSD. Quick Help For Installation of IBM Products Via NetView DM/2 These publications, written by the IBM Enterprise LAN Integration Test (ELITE) team, explain how to install a number of IBM products with NetView DM/2. The installation scenarios and the related samples provided in these books will help you plan the remote installation of IBM products. For your convenience, this CSD contains both softcopy (Bookmanager and INF) and postscript versions of the Quick Help, and self-unpacking files with sample profiles, REXX utilities, and response files. Look for the following files in the CSD diskettes: o NDM2QUIK.BOO, the Bookmanager version of the Quick Help manual, located on the NetView DM/2 V2.1 Quick Help Bookmanager Format And Samples diskette. o NDM2QUIK.INF, the .INF version of the Quick Help manual, located on the NetView DM/2 V2.1 Quick Help PostScript And INF Formats diskette. o NDM2QUIK.EXE, the zipped, self-unpacking postscript version of the Quick Help manual, located on the NetView DM/2 V2.1 Quick Help PostScript And INF Formats diskette. o ELITE.EXE the zipped, self-unpacking file containing the samples, located on the NetView DM/2 V2.1 Quick Help Bookmanager Format And Samples diskette. o NDMDQUIK.BOO, the Bookmanager version of the Quick Help manual for DOS CC Clients, on the NetView DM/2 V2.1 Quick Helps And Samples For DOS CC Clients diskette. o NDMDQUIK.INF, the .INF version of the Quick Help manual for DOS CC clients, on the NetView DM/2 V2.1 Quick Helps And Samples For DOS CC Clients diskette. o NDMDQUIK.EXE, the zipped, self-unpacking postscript version of the Quick Help manual for DOS CC clients, on the NetView DM/2 V2.1 Quick Helps And Samples For DOS CC Clients diskette. o ELITEDOS.EXE the zipped, self-unpacking file containing the samples for DOS CC clients, on the NetView DM/2 V2.1 Quick Helps And Samples For DOS CC Clients diskette. CHAPTER 1. THE NETVIEW DM/2 CSD 14 CSD The Quick Help Bookmanager Versions You can display NDM2QUIK.BOO or NDMDQUIK.BOO with IBM BookManager or IBM Library Reader. Just copy NDM2QUIK.BOO and NDMDQUIK.BOO from the CSD diskettes into your workstation's BookManager or Library Reader BOOKS directory. The Quick Help .INF Versions You can also display the .INF versions of the Quick Helps with the VIEW command available with OS/2. From an OS/2 session, copy the .INF files from the CSD diskettes onto your hard disk and enter: VIEW NDM2QUIK or VIEW NDMDQUIK The Quick Help Postscript Versions If you choose to print the Quick Helps on your PostScript printer, unpack NDM2QUIK.EXE and NDMDQUIK.EXE onto your workstation's hard disk. To do this, run these commands from the from the CSD diskettes: A:\NDM2QUIK <outpath on your hard disk> A:\NDMDQUIK <outpath on your hard disk> The zipped NDM2QUIK file unpacks into the file NDM2QUIK.PS which is ready to print. NDM2QUIK.PS occupies 3.6MB. The zipped NDMDQUIK file unpack into the file NDMDQUIK.PS which is ready to print. NDMDQUIK.PS occupies 1.5MB. The Quick Help Samples The sample REXX utilities, response files and profiles shown in the books are packed in the ZIP files called ELITE and ELITEDOS. Both ELITE.ZIP and ELITEDOS.ZIP are self-unpacking files called ELITE.EXE and ELITEDOS.EXE. Unpack them 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 15 CONCEPTS AND OVERVIEW PART 2. CONCEPTS AND OVERVIEW This part describes changes to make to the Concepts and Overview book to reflect changes and corrections made after the documentation for NetView DM/2 Version 2.1 was sent for publication. (C) Copyright IBM Corp. 1991, 1995 16 CONCEPTS AND OVERVIEW CHAPTER 2. CORRECTIONS TO THE CONCEPTS AND OVERVIEW BOOK PAGE 29 - TOPIC 3.3 - Workstations and Interconnections Supported by the Remote Administrator In the last bullet before the figure in this section, change the first sentence to the following: o OS/2, DOS, DOS-Windows, and NetWare workstations attached to a NetView for NetWare CC Server in a LAN configuration, where IPX is used. PAGE 33 - TOPIC 3.10 - Using a Remote Administrator Workstation in a Multiserver Network At the end of the section, add the following item to the list of limitations and recommendations: o A further consideration is that the NetView DM/2 Remote Administrator does not provide the Transmission Plan capability and automation that is provided by NetView DM/MVS. You would have to write REXX procedures to have the NetView DM/2 Remote Administrator provide functions similar to NetView DM/MVS. To assist you with this, some sample programs are provided with the product demonstrating how these functions can be performed. You can then tailor this sample code to meet the requirements for your specific environment. PAGE 121 - TOPIC C.1 - Software Requirements PAGE 121 - TOPIC C.1.2 - SOFTWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY CLIENT Change the last item in the list of software prerequisites for the LDU receiver to: o DOS J4.01, or J4.01/V, and subsequent versions, and an IBM NetBIOS driver PAGE 122 -TOPIC C.1.4 - SOFTWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED CLIENT Change the last item in the list of software prerequisites to: o DOS J4.01, or J4.01/V, and subsequent versions, and an IBM NetBIOS driver (C) Copyright IBM Corp. 1991, 1995 17 CONCEPTS AND OVERVIEW PAGE 122 - FOLLOWING TOPIC C.1.5 After the section on software requirements for the NetView DM/2 Remote administrator, add the following section: Connectivity with NetView DM/MVS If any of the NetView DM/2 V2.1 program packages (Entry, Extended or Remote Administrator) are used in conjunction with NetView DM/MVS acting as a focal point, then the software level of NetView DM/MVS used must be Version 1 Release 5. In addition, if the DASD Space Checking function provided with NetView DM/2 V2.1 is used, then APAR PN58771 must also be installed with NetView DM/MVS V1R5. PAGE 122 - TOPIC C.2 - COMPATIBILITY Add to the end of the first paragraph: This is true also with respect to the NetView DM/2 J2.0 Entry and Extended programs. You must be aware, however, that all screens and messages are in English. PAGE 124 - TOPIC C.2.1.3 - SUMMARY OF SOFTWARE REQUIREMENTS In the explanation of the NetBIOS software requirements for NetView DM/2 when OS/2 is installed, replace the list of products that provide NetBIOS with the following: o OS/2 LAN Enabler 1.0, and later o OS/2 LAN Server 3.0, and later o NTS/2 1.0, and later PAGE 125 - TOPIC C.3 - Hardware Requirements PAGE 125 - TOPIC C.3.1 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY BASE Change the minimum storage recommended for the Change distribution manager (CDM) to 150MB of hard disk space. This figure includes the storage requirements to run NetView DM/2 and the software prerequisites for this NetView DM/2 component, as described in the Software Requirements section. This number may be increased depending upon the functions used. PAGE 126 - TOPIC C.3.1 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY BASE Add the following items to the list of products providing the NetBIOS driver that support appropriate communication adapters for the NetView DM/2 LDU distributor: o OS/2 LAN Server 3.0, and later o NTS/2 1.0, and later CHAPTER 2. CORRECTIONS TO THE CONCEPTS AND OVERVIEW BOOK 18 CONCEPTS AND OVERVIEW PAGE 126 - TOPIC C.3.1 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY CLIENT Change the second item in the list of system units for the LDU receiver to: o Or any IBM Personal System/55 system unit (supporting Microchannel Architecture) supported by OS/2 Extended Edition J1.3 or by OS/2 Version J2.0 and later, or by DOS J4.01, or J4.01/V, and subsequent versions. PAGE 126 - TOPIC C.3.1 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY CLIENT Change the last two items showing the minimum storage requirements for the LDU receiver to: o 80MB of hard disk space, when running OS/2 o 20MB of hard disk space, when running DOS This figure includes the storage requirements to run NetView DM/2 and the software prerequisites for this NetView DM/2 component, as described in the Software Requirements section. This number may be increased depending upon the functions used. PAGE 127 - TOPIC C.3.1 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY CLIENT Replace the list of products providing the NetBIOS driver that support appropriate communication adapters for the NetView DM/2 LDU receiver with: o OS/2 LAN Enabler 1.0, and later o OS/2 LAN Server 3.0, and later o NTS/2 1.0, and later o IBM LAN Support Program or other compatible product (when DOS is installed) PAGE 127 - TOPIC C.3.3 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED BASE Change the minimum storage recommended for the Change distribution manager (CDM) to 200MB of hard disk space. This figure includes the storage requirements to run NetView DM/2 and the software prerequisites for this NetView DM/2 component, as described in the Software Requirements section. This number may be increased depending upon the functions used. PAGE 127 - TOPIC C.3.3 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED BASE Add the following items to the list of products providing the NetBIOS driver that support appropriate communication adapters for the Change distribution manager when LAN-attached: CHAPTER 2. CORRECTIONS TO THE CONCEPTS AND OVERVIEW BOOK 19 CONCEPTS AND OVERVIEW o OS/2 LAN Enabler 1.0, and later o OS/2 LAN Server 3.0, and later o NTS/2 1.0, and later PAGE 128 - TOPIC C.3.4 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED CLIENT Change the second item in the list of system units for a CC client to: o Or any IBM Personal System/55 system unit (supporting Microchannel Architecture) supported by OS/2 Extended Edition J1.3 or by OS/2 Version J2.0 and later, or by DOS J4.01, or J4.01/V, and subsequent versions. PAGE 129 - TOPIC C.3.4 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED CLIENT Change the last two items showing the minimum storage requirements for a CC client to: o 80MB of hard disk space, when running OS/2 o 20MB of hard disk space, when running DOS This figure includes the storage requirements to run NetView DM/2 and the software prerequisites for this NetView DM/2 component, as described in the Software Requirements section. This number may be increased depending upon the functions used. PAGE 129 - TOPIC C.3.4 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED CLIENT Replace the list of products providing the NetBIOS driver that support appropriate communication adapters for the NetView DM/2 Extended client with: o OS/2 LAN Enabler 1.0, and later o OS/2 LAN Server 3.0, and later o NTS/2 1.0, and later o IBM LAN Support Program or other compatible product (when DOS is installed) CHAPTER 2. CORRECTIONS TO THE CONCEPTS AND OVERVIEW BOOK 20 CDM USER'S GUIDE PART 3. CDM USER'S GUIDE This part describes changes to make to the CDM User's Guide to reflect changes and corrections made after the documentation for NetView DM/2 Version 2.1 was sent for publication. (C) Copyright IBM Corp. 1991, 1995 21 CDM USER'S GUIDE CHAPTER 3. WHAT TO LOOK FOR WHEN MIGRATING TO NETVIEW DM/2 VERSION 2.1 In addition to the new features and support for other products of the NetView DM family, NetView DM/2 Version 2.1 also provides a number of other enhancements. This chapter discusses some of the changes that have been implemented in NetView DM/2 Version 2.1 for CC servers. These changes involve the operation of the product and must be taken into consideration when you migrate from NetView DM/2 Version 2.0 to Version 2.1, or if you have Version 2.1 workstations coexisting with Version 2.0 workstations. See the NetView Distribution Manager/2 Installation and ___________________________________________________ Customization Guide for information about coexistence between Versions 2.0 ____________________ and 2.1 of NetView DM/2. Software Prerequisites for NetView DM/2 Version 2.1 NetView DM/2 requires OS/2 Version 2.0 or later to run the CDM Base component. This includes any workstations running as a remote administrator, CC server, or APPC-connected workstation. CC clients can still run on OS/2 Version 1.3 EE. Install the REXX command interpreter option with OS/2 if you plan to have REXX procedures that either call NetView DM/2 commands or take some sort of action depending on the outcome of a NetView DM/2 command. The interaction between a workstation running Version 2.1 and the NetView DM focal point requires NetView DM Version 1.5. NetView DM/2 Version 2.1 Commands Version 2.1 includes: o Changes to the command format (such as addition or modification of parameters) o Changes in command output o Addition of new commands o Removal of existing commands In general, in Version 2.1 all commands that originate a file services action are recorded in the NetView DM/2 catalog and return, among other things, a request ID; this makes it easier to track them. At the same time, however, you can choose to disregard the recording of operations in the NetView DM/2 catalog through the Track History option. You (C) Copyright IBM Corp. 1991, 1995 22 CDM USER'S GUIDE can select the Track History option by setting AutomaticPurgeReports to YES. Besides erasing the report file for an operation, setting this option to YES also deletes the related entry from the NetView DM/2 catalog as soon as the request has completed. All commands that originate a change management action need the workstation ID as known in the CC domain, while those originating file services actions need the full destination ID of the node, consisting of RGN.REN. This is because while all change management requests from a CC server are local, file services requests can also be remote. Upon completion, all CDM commands return a code that reports their outcome. The code is returned to the OS/2 session from which the NetView DM/2 command was entered. This makes it possible to test the return code in a user REXX procedure to condition the flow of the program. See the NetView DM/2 ____________ Messages and Error Recovery Guide for information on return codes generated _________________________________ by CDM commands. The /SDT Parameter For a number of commands you can now specify the date and time when the particular request is to be submitted, as well as the date and time when the request is to be executed. The commands that include this option, using the /SDT parameter, are: o Accept o Activate o Change_Req o Initiate o Install o Remove o Retrieve o Send The /APPLID Parameter You can use the /APPLID parameter to define the name of a user exit to be called upon completion of the request. The CDM commands used with parameter are: o Accept o Activate o Delete o Initiate o Install o Remove o Retrieve o Send With the use of /APPLID, and the ability to test the result of the request CHAPTER 3. WHAT TO LOOK FOR WHEN MIGRATING TO NETVIEW DM/2 VERSION 2.1 23 CDM USER'S GUIDE provided by the command return code, you can write REXX procedures or user exits based on these NetView DM/2 commands. The ACTIVATE Command With the ACTIVATE command the user at the target workstation can now decide whether to have the workstation restarted immediately, or to have the restart deferred by a length of time, from 0 to 30 minutes, that can be customized beforehand in the RebootDelay keyword in IBMNVDM2.INI. If you select the Force parameter, /F, when entering ACTIVATE, a window at the target _____ workstation presents the option to restart immediately or not. In NetView DM/2 Version 2.0, CDM ACTIVATE caused the immediate restart of the target workstation. The /SZ Parameter Use the /SZ parameter, available with CDM CATALOG, to specify the size in kilobytes of the object being cataloged. This information is also recorded in the NetView DM/2 catalog and can be seen with the LIST command. You can use it, for example, to determine if there is enough space at a target workstation to send or install an object. In addition, with the /USZ parameter of CDM INSTALL for nondatabase files, you can update the size specified previously with /SZ. This can be useful if the object was compressed when cataloged or if you know that the actual file requires more space when installed. The /CHK Parameter The /CHK parameter in CDM INSTALL and CDM REMOVE can be useful to verify if there is enough hard disk space to complete a request. By default, /CHK checks the available space against the value entered with /USZ, if available. When invoked, this parameter subtracts the size of the object as cataloged in IRU status from the size of the same object as cataloged in backlevel status. CHAPTER 3. WHAT TO LOOK FOR WHEN MIGRATING TO NETVIEW DM/2 VERSION 2.1 24 CDM USER'S GUIDE CDM LIST_WS CDM LIST_WS displays a more thorough output than it did in Version 2.0. The information displayed now includes: o For the CC server: - Destination ID (RGN.REN) - Description - Workstation type - Operating system o For CC clients: - Destination ID (RGN.REN) - Server name - Description - Workstation type - Operating system - Status Other New Commands A number of new commands are now available for the management of local and remote destinations. The ADD_DEST command defines other local or remote NetView DM/2 nodes to the CC server (as well as to a remote administrator workstation or to a CDM-based workstation). This command replaces the ADD_WS and CONFIG commands of Version 2.0; moreover, it adds: o The definition of the destination node to the workstation table of the CC server o Information on the routing and connection of the destination node to the transmission controller tables of the CC server In general, there is no longer any need to use the ADD_WS and CONFIG commands except to add a workstation that acts strictly as an intermediate node. In fact, if the intermediate node is used only to pass change management requests between NetView DM/2 nodes, there is no purpose to define it in the NetView DM/2 tables of the other nodes. If, however, the intermediate node is the target for change management operations as well, then it should be defined to the other nodes by means of the ADD_DEST command. Other commands are available to change, delete, or list destinations in the NetView DM/2 tables of a CC server. The tracking of requests has become much more powerful because many commands return a request ID and new commands are provided to manage them. New commands for request management are: o With CHANGE_REQ you can reschedule a request by: CHAPTER 3. WHAT TO LOOK FOR WHEN MIGRATING TO NETVIEW DM/2 VERSION 2.1 25 CDM USER'S GUIDE - Specifying the date and time when the command is to be executed; with NetView DM/2 Version 2.0 this was accomplished by canceling first, and then resubmitting a request. - Specifying the date and time when the command is to be submitted. o DELETE_REQ has the function that was previously provided by the CDM CANCEL and the PURGE_REQ /F commands. o HOLD_REQ enables you to hold a request that is in WAITING FOR EXECUTION status. It uses the request ID string returned by the command that entered the specific request for identification. You can also see the request ID using LIST_REQ. o QUERY_REQ displays information about all local and remote requests that have been submitted. o RELEASE_REQ releases requests that are in HELD status. The CDM Dialog Interface for a CC Server The CDM dialogs in Version 2.1 include a number of new or revised functions that facilitate the monitoring of change management activities. These functions are provided by: o A revised CDM Message Log window o A new CDM Error Log window o A new CDM Request Status window These functions are available for the CC server and all the workstations in its CC domain that are included in the WORKSTATIONS list. Previously information was given only for pending requests; now it also is provided for requests that have completed. A brief description of what you can accomplish with each window follows. CHAPTER 3. WHAT TO LOOK FOR WHEN MIGRATING TO NETVIEW DM/2 VERSION 2.1 26 CDM USER'S GUIDE CDM Message Log Window This window displays all messages logged in the MESSAGE.DAT file of NetView DM/2. Enhancements include: o Different types of messages are preceded by specific icons that facilitate their identification. o For each message the following information is displayed: - Date and time of origin - Message number - Message type - Message text o A secondary window provides details on each message; clicking twice on a specific message or selecting DETAILS on a chosen message displays: - Message explanation - System action - User response CDM Error Log Window This window displays all errors logged in the ERROR.DAT file of NetView DM/2. Characteristics include: o Specific icons differentiate errors by component type to facilitate their identification. o For each error the following information is displayed: - Date and time of origin - Component in error - Module in error o A secondary window provides details on each error; clicking twice on a specific error, or selecting DETAILS on a chosen error displays: - Return codes - Additional information in hexadecimal format CHAPTER 3. WHAT TO LOOK FOR WHEN MIGRATING TO NETVIEW DM/2 VERSION 2.1 27 CDM USER'S GUIDE CDM Request Status Window This window displays all the requests entered from the CDM Dialog windows or from an OS/2 prompt. It replaces the Pending Requests window selectable under Engine in the CDM Dialog action bar of Version 2.0. Unlike Pending Requests, this window traces all requests in all statuses or in the status you specify by the user in the Include function. Characteristics include: o Specific icons differentiate requests by status and result to facilitate their identification. o For each request the following information is displayed: - Request ID - Scheduled date and time of submission - Request type - Application ID o An Include function filters the requests that are listed according to: - Status/result - Type - Application ID o A secondary window provides details on a selected request such as: - Global name - Request options o For each request a report can be displayed to show: - Destination ID - SNA condition report - Reply file name o Request management capabilities enable you to: - Delete requests from the list - Hold and release functions in pending status - Change the scheduled time to execute a request CHAPTER 3. WHAT TO LOOK FOR WHEN MIGRATING TO NETVIEW DM/2 VERSION 2.1 28 CDM USER'S GUIDE CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS This chapter describes the new NetView DM/2 utilities and the enhancements added by this CSD or cumulated from previous ones. The NVDMRDSK Utility The purpose of NVDMRDSK is to create a minimal CC client startup diskette. You can use this utility to create startup diskettes to install software on a pristine workstation, that is, a workstation that has no operating system installed. NVDMRDSK inserts the minimal CC client code into startup diskettes (one diskette only for DOS) that you can create using DOS or OS/2 utilities. This minimal CC client is customized by the parameters contained in the IBMNVDM2.INI file. The IBMNVDM2.INI file is also created on the diskette. Format +---------------------------------------------------------------------------+ | | | >>--NVDMRDSK--.----------------------------.----------------------------> | | '-/OS--:--Target Environment-' | | | | >--.----------------------.--.---------------------.--------------------> | | '-/TD--:--Target Drive-' '-/SN--:--Server Name-' | | | | >--.---------------------.--.--------------------------.----------------> | | '-/CN--:--Client Name-' '-/AttT--:--Attach Timeout-' | | | | >--.---------------------------.--.---------------------------.---------> | | '-/RcvT--:--Receive Timeout-' '-/ReqT--:--Request Timeout-' | | | | >--.---------------------------.--.------------------------.------------> | | '-/RcvT--:--Request Timeout-' '-/AN--:--Adapter Number-' | | | | >--.-------------------------.--.-------------------------.-------------> | | '-/FFn--:--Key stoke file-' '-/FDn--:--Key stoke file-' | | | | >--.------------------------.-->< | | '-/MenT--:--Menu Timeout-' | | | +---------------------------------------------------------------------------+ Parameters (C) Copyright IBM Corp. 1991, 1995 29 CDM USER'S GUIDE OS Specifies the operating system you want to install on the pristine workstation. The allowed values are DOS and OS2 and the default is OS2. TD Specifies the drive where the startup diskette is inserted. Drive A is the default value. SN Specifies the name of the CC server of the standalone LAN that the pristine workstation is connected to. The default is a question mark (?). If you leave the default question mark, you will be prompted for the name of a CC server at the time of startup. This facility allows you to create a startup diskette that can be used on different LANs regardless of the CC server name in those LANs. The server name must be of up to 8 characters; the first character must be alphabetic and the following characters can be alphanumeric or $, @, or #. CN Specifies the name of the CC client. The default is a question mark (?). If you leave the default question mark, you are prompted for the name of a CC client at the time of startup. This facility allows you to create a startup diskette that can be used on different LANs regardless of the CC client name in those LANs. The client name must be of up to 8 characters; the first character must be alphabetic and the following characters can be alphanumeric or $, @, or #. AN Specifies which LAN adapter on the pristine workstation will be used by NetView DM/2. o 0 indicates that the primary LAN adapter will be used. o 1 indicates that the secondary LAN adapter will be used. If you have OS2 as the operating system at the target, you use the following parameters: ATTT specifies the minimum time period that can elapse (in milliseconds) between the sending of an Attach command to the pristine workstation and the receipt of a reply. When this time period has elapsed, the CDM agent terminates and the request fails, because NetView DM/2 assumes that the pristine workstation is not active. This value must be in the range -1 to 2000000000. The default value is -1. It disables the time-out. RCVT specifies the maximum time period that can elapse (in milliseconds) between the sending of a NetBIOS request to the pristine workstation and the receipt of a reply. When this time period has elapsed, the CDM agent terminates and the request fails, because NetView DM/2 assumes that the pristine workstation is not active. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 30 CDM USER'S GUIDE This value must be in the range 5000 to 2000000000, or the special value, -1. This special value disables the timeout. REQUEST TIMEOUT specifies the time period (in milliseconds) that the CDM agent on a CC client is to remain idle, waiting for requests, before terminating. This value must be in the range -1 to 2000000000. The following values have special meanings: o -1 indicates that the CDM agent is active indefinitely. o 0 indicates that the CDM agent ends immediately if no further requests are pending. If you have DOS as the operating system at the target, you can take advantage of the following parameters: FDN specifies the full path of a key stroke file for the FDISK command. FFN specifies the full path of a key stroke file for the FORMAT command. MENU TIMEOUT specifies the length of time (in seconds) that the pristine machine menu displays before ending. This value must be in the range -1 to 90. The following values have a special meaning: o -1 indicates that the menu remains indefinitely on the screen. o 0 indicates that menu disappears immediately from the screen. After NVDMRDSK has generated the startup diskettes, you can use them to start a minimal CC client in the following way: o If you are installing DOS, insert the startup diskette and turn the workstation on. o If you are installing OS/2: 1. Insert the first startup diskette and turn the workstation on. 2. When the prompt appears, insert the second startup diskette and remove it as soon as the message ANX1317 is issued by the minimal CC client. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 31 ANX2015I O ANX2019E NVDMRDSK messages ----------------------------------------------------------------------------- ANX2015I NVDMRDSK HAS ENDED SUCCESSFULLY EXPLANATION: NVDMRDSK has created the CC Client boot diskette SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: none. ----------------------------------------------------------------------------- ANX2016E NVDMRDSK SYNTAX IS INCORRECT EXPLANATION: NVDMRDSK has been invoked using an incorrect syntax SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct syntax ----------------------------------------------------------------------------- ANX2017E NVDMRDSK HAS ENDED FOR UNEXPECTED CONDITION EXPLANATION: NVDMRDSK has ended for unexpected condition SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Contact your product administrator ----------------------------------------------------------------------------- ANX2018E NVDMRDSK HAS ENDED FOR INTERNAL ERROR LOADING THE DBCS DLLS EXPLANATION: NVDMRDSK has ended for unexpected condition loading DLLs SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Contact your product administrator ----------------------------------------------------------------------------- ANX2019E NVDMRDSK HAS BEEN INVOKED WITH A WRONG SERVER NAME VALUE FOR SN PARAMETER EXPLANATION: Server Name is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Server Name value CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 32 ANX2020E O ANX2024E ----------------------------------------------------------------------------- ANX2020E NVDMRDSK HAS BEEN INVOKED WITH A WRONG CLIENT NAME VALUE FOR CN PARAMETER EXPLANATION: Client Name is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Client Name value ----------------------------------------------------------------------------- ANX2021E NVDMRDSK HAS BEEN INVOKED WITH A WRONG OPERATING SYSTEM FOR OS PARAMETER EXPLANATION: Operating System is not allowed SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Operating System ----------------------------------------------------------------------------- ANX2022E NVDMRDSK HAS BEEN INVOKED WITH A WRONG ATTACH TIMEOUT VALUE FOR OS PARAMETER EXPLANATION: Attach Timeout is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Attach Timeout ----------------------------------------------------------------------------- ANX2023E NVDMRDSK HAS BEEN INVOKED WITH A WRONG ATTACH TIMEOUT VALUE FOR ATTT EXPLANATION: Attach Timeout is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Attach Timeout ----------------------------------------------------------------------------- ANX2024E NVDMRDSK HAS BEEN INVOKED WITH A WRONG RECEIVE TIMEOUT VALUE FOR RCVT PARAMETER EXPLANATION: Attach Timeout is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Receive Timeout CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 33 ANX2025E O ANX2029E ----------------------------------------------------------------------------- ANX2025E NVDMRDSK HAS BEEN INVOKED WITH A WRONG REQUEST TIMEOUT VALUE FOR REQT PARAMETER EXPLANATION: Attach Timeout is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Request Timeout ----------------------------------------------------------------------------- ANX2026E NVDMRDSK HAS ENDED FOR AN ERROR OCCURRED ACCESSING THE CONFIG.SYS EXPLANATION: NVDMRDSK has ended for an error occurred accessing the CONFIG.SYS on the target Drive SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Verify the CONFIG.SYS on the Target Drive ----------------------------------------------------------------------------- ANX2027E NVDMRDSK HAS BEEN INVOKED WITH A WRONG MENU TIMEOUT VALUE FOR MENT PARAMETER EXPLANATION: Menu Timeout is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Menu Timeout ----------------------------------------------------------------------------- ANX2028E NVDMRDSK HAS BEEN INVOKED WITH A WRONG MENU TIMEOUT VALUE FOR MENT PARAMETER EXPLANATION: Menu Timeout is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Menu Timeout ----------------------------------------------------------------------------- ANX2029E NVDMRDSK HAS BEEN INVOKED WITH A WRONG FDISK KEY STOKE VALUE FOR FDN PARAMETER EXPLANATION: FDISK key stoke file is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct FDISK key stoke file CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 34 ANX2030E O ANX2034E ----------------------------------------------------------------------------- ANX2030E NVDMRDSK HAS BEEN INVOKED WITH A WRONG FORMAT KEY STOKE VALUE FOR FDN PARAMETER EXPLANATION: FORMAT key stoke file is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct FORMAT key stoke file ----------------------------------------------------------------------------- ANX2031E NVDMRDSK HAS BEEN INVOKED WITH A WRONG FORMAT KEY STOKE VALUE FOR FDN PARAMETER EXPLANATION: FORMAT key stoke file is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct FORMAT key stoke file ----------------------------------------------------------------------------- ANX2032E NVDMRDSK HAS BEEN INVOKED WITH A WRONG ADAPTER NUMBER VALUE FOR AN PARAMETER EXPLANATION: Adapter Number is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Adapter Number ----------------------------------------------------------------------------- ANX2033E NVDMRDSK HAS BEEN INVOKED WITH A WRONG TARGET DRIVE VALUE FOR TD PARAMETER EXPLANATION: Target Drive is invalid SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command using the correct Target drive ----------------------------------------------------------------------------- ANX2034E NVDMRDSK HAS FAILED BECAUSE THERE IS NO ROOM ON THE TARGET DRIVE EXPLANATION: there is no room on the Target Drive SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Free space on the Target Drive and resubmit command CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 35 ANX2035E O ANX2037E ----------------------------------------------------------------------------- ANX2035E NVDMRDSK HAS FAILED BECAUSE NETBIOS IS NOT INSTALLED ON THE TARGET DRIVE EXPLANATION: NetBios is not installed on the Target Drive SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Install NetBios on the Target Drive and resubmit the command ----------------------------------------------------------------------------- ANX2036E NVDMRDSK HAS FAILED CREATING THE DIRECTORY STRUCTURE ON THE TARGET DRIVE EXPLANATION: NVDMRDSK has failed creating the directory structure on the Target Drive SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command ----------------------------------------------------------------------------- ANX2037E NVDMRDSK HAS FAILED COPYING FILES ON THE TARGET DRIVE EXPLANATION: NVDMRDSK has failed copying files on the Target Drive SYSTEM ACTION: Processing terminates normally and the control returns to OS/2 USER RESPONSE: Resubmit the command The NVDMUPO Utility The NVDMUPO utility runs on the application site and uses a modification file to change the following system files on an OS/2 CC client: o CONFIG.SYS o STARTUP.CMD o AUTOEXEC.BAT o WIN.INI o PROGMAN.INI o SYSTEM.INI Moreover, you can invoke NVDMUPO to add groups and icons to the OS/2 desktop or to delete files. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 36 Use the utility when you install an application that requires configuration file changes. NVDMUPO backs up the following system files, before changing them: o CONFIG.SYS o STARTUP.CMD o AUTOEXEC.BAT o WIN.INI o PROGMAN.INI o SYSTEM.INI The utility creates a log file, NVDMUPO.LOG in the< ProductDir >\BIN directory. Format +---------------------------------------------------------------------------+ | | | >>--NVDMUPO--modification_file_name--.-------------------------.-->< | | '-/T--:--target_directory-' | | | +---------------------------------------------------------------------------+ Parameters o modification_file_name: specifies the fully qualified name of the ______________________ modification file. o target_directory: specifies a target directory to be used by the ________________ $(TargetDir) macro in the modification file. If this parameter is not specified, then $ is defaulted to boot_drive:\ Modification File Statements This section describes the syntax of the statements that you can use in the modification file. [SYSTEM_FILE_NAME] identifies the system file or the system object to modify. The following names are possible: o CONFIG.SYS CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 37 o STARTUP.CMD o AUTOEXEC.BAT o WIN.INI o PROGMAN.INI o SYSTEM.INI o DESKTOP o FS The square brackets are mandatory. All the statements that follow the specified [system_file_name] statement are applied to the named system file until a new [system_file_name] statement is found. For example: [CONFIG.SYS] All statements thereafter are applied to the system file CONFIG.SYS until another [ system_file_name] statement is found. ADDSTATEMENT(CMD_ATTRIB, CMD_NAME) adds a system file line containing the command cmd_name. In processing AddStatement, NVDMUPO looks for a line containing cmd_name; if it does not find it, it adds it to the file. Command attributes (cmd_attrib) that can be used with AddStatement are: o TOP the line with cmd_name is added at the top of the system file ___ o BOTTOM the line with cmd_name is added at the bottom of the system ______ file o N:X the statement is added in the X position __ o AFTER:X the statement is added after statement X in the file ______ o BEFORE:X the statement is added before statement X in the file _______ EXAMPLE: [CONFIG.SYS] AddStatement(TOP,<DEVICE=C:\SMARTDRV.SYS>) Adds the statement DEVICE=C:\SMARTDRV.SYS at the top of CONFIG.SYS NOTE: not all the statements are valid for both the CONFIG.SYS and STARTUP.CMD and not all the attributes are valid for every statement. Refer to "Attributes and Statements Relationships" on page 42 for a compatibility list between attributes and commands. _____________ CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 38 UPDATESTATEMENT( CMD_ATTRIB,< CMD_VARIABLE >,< CMD_TOKEN >) updates a system variable cmd_variable by adding cmd_token. In processing UpdateStatement, NVDMUPO looks for a variable cmd_variable containing the cmd_token; if it does not find the cmd_token, it adds it to the variable. Command attributes (cmd_attrib) that can be used with UpdateStatement are: o LEFT the token cmd_token is added to the left of the < ____ cmd_variable> o RIGHT the token cmd_token is added to the right of the _____ <cmd_variable> o X:LEFT the token is added to the left of the first X < ____ cmd_variable> o X:RIGHT the token is added to the right of the first X < _____ cmd_variable> EXAMPLE: [CONFIG.SYS] UpdateStatement(RIGHT,<SET PATH>,<C:\>) Adds the token =C:\ to the right of variable PATH DELETESTATEMENT( CMD_ATTRIB, CMD_NAME) deletes a system file line containing the specified cmd_name value. Command attributes (cmd_attrib) that can be used with DeleteStatement are: o ALL: occurrences of cmd_name are deleted from the system file ___ o N:X the first X occurrences of cmd_name are deleted from the system __ file EXAMPLE: [STARTUP.CMD] DeleteCommand(ALL,<START CM>) All the occurrences of the START CM command are deleted from STARTUP.CMD CUTSTATEMENTINROW( CMD_ATTRIB, CMD_VARIABLE, CMD_TOKEN) updates a system file line containing the command cmd_variable by deleting cmd_token. Command attributes (cmd_attrib) that can be used with CutStatementInRow are: o ALL all occurrences of cmd_Token are deleted in the cmd_variable ___ o N:X the first X occurrences of cmd_Token are deleted in the __ cmd_variable CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 39 EXAMPLE: [CONFIG.SYS] CutStatementInRow(RIGHT,<SET PATH>,<C:\>) Deletes token =C:\ at the right of the variable PATH ADDPROGRAM( CMD_ATTRIB, GROUP_NAME, FILE_NAME, FILE_PATH) creates the specified group group_name and adds to it the icon joined to the file with name file_name in file_path. Command attributes (cmd_attrib) that can be used with AddProgram are: o DESKTOP to add the group to the OS/2 Desktop _______ EXAMPLE: AddProgram(DESKTOP,<Smalltalk>,<VPM>,<C:\ VOS2\ V.EXE>) DELETEFILE( CMD_ATTRIB, FILE_PATH_NAME) deletes the file with file_path_name Command attributes (cmd_attrib) that can be used with DeleteFile are: o FS to delete the file from the OS/2 File system __ EXAMPLE: DeleteFile(FS,<C:\VOS2\V.EXE>) Rules for Writing Modification File Statements 1. You must write the parameters in the order shown. 2. An application directory macro, with keywords $(TargetDir), is available to install application software in different directories depending on the OS/2 CC client. Yuo invoke this macro in the modification file. The macro $(TargetDir) is resolved by NVDMUPO at execution time with the value provided through the /T parameter. For example: o Given the following modification file named NVDMUPO.MOD: [CONFIG.SYS] AddStatement(TOP,<DEVICE=$(TargetDir)\\SAMPLFIL.SYS>) o You invoke NVDMUPO in the following manner: NVDMUPO NVDMUPO.MOD /T:C:\SAMPLDIR CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 40 o NVDMUPO adds the statement DEVICE=C:\SAMPLDIR\SAMPLFIL.SYS at the TOP of CONFIG.SYS. 3. You can use blanks in the modification file to separate statements and rows. Conversely, if a blank must be part of a statement, the whole statement must be included between < and >. For example: [CONFIG.SYS] Add Statement(TOP, <DEVICE=$(TargetDir)\SAMPLFIL.SYS>) is the equivalent to [CONFIG.SYS] AddStatement(TOP,<DEVICE=$(TargetDir)\SAMPLFIL.SYS>) but [STARTUP.CMD] AddStatement(TOP,<START CM>) is different from [STARTUP.CMD] AddStatement(TOP,START CM) In this last example, if you do not enclose START CM between < and >, the utility will write STARTCM, instead of START CM, in STARTUP.CMD. 4. You can write comments in the modification file. Comments must be preceded by the # character. For example: AddStatement(TOP,START CM) # this is a comment CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 41 Attributes and Statements Relationships The following tables show which attributes are available for which statement within the system files, the desktop and File system. o Statement and attribute relationship table for: - CONFIG.SYS - STARTUP.CMD - AUTOEXEC.BAT - WIN.INI - PROGMAN.INI - SYSTEM.INI +-------------------------------------------------------+ | Table 1. Statement and Attribute Relationship For | | System Files - Part 1 | +-------------------+-------+------+-----+--------+-----+ | STATEMENT | RIGHT | LEFT | TOP | BOTTOM | ALL | +-------------------+-------+------+-----+--------+-----+ | AddStatement | | | | | | | | | | &che|k&check.| | +-------------------+-------+------+-----+--------+-----+ | UpdateStatement | | | | | | | | &check| &chec|. | | | +-------------------+-------+------+-----+--------+-----+ | DeleteStatement | | | | | | | | | | | | &che|k. +-------------------+-------+------+-----+--------+-----+ | CutStatementInRow | | | | | | | | | | | | &che|k. +-------------------+-------+------+-----+--------+-----+ CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 42 ANX2037I O ANX2037I +-----------------------------------------------------------------+ | Table 2. Statement and Attribute Relationship For System Files | | - Part 2 | +-------------------+---------+----------+--------+---------+-----+ | STATEMENT | AFTER:X | BEFORE:X | X:LEFT | X:RIGHT | N:X | +-------------------+---------+----------+--------+---------+-----+ | AddStatement | | &check. | | | | | | &check. | | | | &che|k. +-------------------+---------+----------+--------+---------+-----+ | UpdateStatement | | &check. | | | | | | | | &check.| | | +-------------------+---------+----------+--------+---------+-----+ | DeleteStatement | | | | | | | | | | | | &che|k. +-------------------+---------+----------+--------+---------+-----+ | CutStatementInRow | | | | | | | | | | | &check. | | +-------------------+---------+----------+--------+---------+-----+ o Statement and attribute relationship table for the OS/2 desktop +-----------------------------------------------------------------------+ | Table 3. Statement and Attribute Relationship For DESKTOP | +-----------------------------------------------+-----------------------+ | STATEMENT | DESKTOP | +-----------------------------------------------+-----------------------+ | AddProgram | &check. | +-----------------------------------------------+-----------------------+ o Statement and attribute relationship table for the OS/2 file system +-----------------------------------------------------------------------+ | Table 4. Statement and Attribute Relationship For FS | +-----------------------------------------------+-----------------------+ | STATEMENT | FS | +-----------------------------------------------+-----------------------+ | DeleteFile | &check. | +-----------------------------------------------+-----------------------+ Messages ----------------------------------------------------------------------------- ANX2037I NVDMUPO HAS ENDED SUCCESSFULLY EXPLANATION: NVDMUPO has ended successfully SYSTEM ACTION: Program terminates USER RESPONSE: none CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 43 ANX2038E O ANX2042E ----------------------------------------------------------------------------- ANX2038E NVDMUPO HAS ENDED FOR INCORRECT PROGRAM INVOCATION EXPLANATION: NVDMUPO has ended for incorrect program invocation SYSTEM ACTION: Program terminates USER RESPONSE: Resubmit the program with the correct syntax ----------------------------------------------------------------------------- ANX2039E NVDMUPO HAS ENDED BECAUSE OF AN ERROR OPENING THE RESPONSE FILE EXPLANATION: NVDMUPO has ended because of an error opening the response file SYSTEM ACTION: Program terminates USER RESPONSE: Resubmit the program after verifying the path of the response file ANX2040E: (E) NVDMUPO has found an incorrect syntax in the response file%0 ----------------------------------------------------------------------------- ANX2040E NVDMUPO HAS FOUND AN INCORRECT SYNTAX IN THE RESPONSE FILE EXPLANATION: NVDMUPO has found an incorrect syntax in the response file SYSTEM ACTION: Program terminates USER RESPONSE: Resubmit the program after verifying the syntax in the response file ----------------------------------------------------------------------------- ANX2042E NVDMUPO HAS ENDED FOR AN ERROR OPENING THE CONFIG.SYS EXPLANATION: NVDMUPO has ended for an error opening the CONFIG.SYS SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command ----------------------------------------------------------------------------- ANX2042E NVDMUPO HAS ENDED FOR AN ERROR OPENING THE CONFIG.SYS EXPLANATION: NVDMUPO has ended for an error opening the CONFIG.SYS SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 44 ANX2043E O ANX2048E ----------------------------------------------------------------------------- ANX2043E NVDMUPO HAS ENDED FOR AN ERROR ACCESSING THE DESKTOP EXPLANATION: NVDMUPO has ended for an error accessing the DESKTOP SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command ----------------------------------------------------------------------------- ANX2044E NVDMUPO HAS ENDED FOR AN ERROR ACCESSING THE CONFIG.SYS EXPLANATION: NVDMUPO has ended for an error accessing the CONFIG.SYS SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command ----------------------------------------------------------------------------- ANX2045E NVDMUPO HAS ENDED FOR AN ERROR OPENING THE AUTOEXEC.BAT EXPLANATION: NVDMUPO has ended for an error opening the AUTOEXEC.BAT SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command ----------------------------------------------------------------------------- ANX2046E NVDMUPO HAS ENDED FOR AN ERROR ACCESSING THE AUTOEXEC.BAT EXPLANATION: NVDMUPO has ended for an error accessing the AUTOEXEC.BAT SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command ----------------------------------------------------------------------------- ANX2047E NVDMUPO HAS ENDED FOR AN ERROR OPENING THE WIN.INI EXPLANATION: NVDMUPO has ended for an error opening the WIN.INI SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command ----------------------------------------------------------------------------- ANX2048E NVDMUPO HAS ENDED FOR AN ERROR ACCESSING THE WIN.INI EXPLANATION: NVDMUPO has ended for an error accessing the WIN.INI SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 45 ANX2049E O ANX2052E ----------------------------------------------------------------------------- ANX2049E NVDMUPO HAS ENDED FOR AN ERROR OPENING THE PROGMAN.INI EXPLANATION: NVDMUPO has ended for an error opening the PROGMAN.INI SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command ----------------------------------------------------------------------------- ANX2050E NVDMUPO HAS ENDED FOR AN ERROR ACCESSING THE PROGMAN.INI EXPLANATION: NVDMUPO has ended for an error accessing the PROGMAN.INI SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command ----------------------------------------------------------------------------- ANX2051E NVDMUPO HAS ENDED FOR AN ERROR OPENING THE SYSTEM.INI EXPLANATION: NVDMUPO has ended for an error opening the SYSTEM.INI SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command ----------------------------------------------------------------------------- ANX2052E NVDMUPO HAS ENDED FOR AN ERROR ACCESSING THE SYSTEM.INI EXPLANATION: NVDMUPO has ended for an error accessing the SYSTEM.INI SYSTEM ACTION: Program Terminates USER RESPONSE: Verify the system file and resubmit the command The Enhanced NVDMUFM Utility NVDMUFM is a NetView DM/2 utility provided in previous releases that generates a workstation-unique file starting from a template file and a Node Dependent Information (NDI) file. During the unique-file generation process, NVDMUFM replaces the placeholders in the template file with the values contained in the NDI file. See the NetView DM/2 CDM User's Guide for further details. _____________________________ The existing version of NVDMUFM runs strictly on the workstation where the unique file must be generated and used. The enhanced version of NVDMUFM, distributed with this CSD, can generate unique files that will be used by other workstations. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 46 The enhanced NVDMUFM can be used to generate workstation-specific response files for an entire CC domain. The syntax of the enhanced command is: +---------------------------------------------------------------------------+ | | | >>--NVDMUFM--template_file--unique_file_dir--.-----------------.--------> | | '-/NDI:--ndi_file-' | | | | >--.------------------------------------.--.------------------.-->< | | '-/WS:--ws_name--/WSL:--ws_list_file-' '-/EXT:--extension-' | | | +---------------------------------------------------------------------------+ The meanings of the new parameters are: UNIQUE_FILE_DIR is the name of the directory where the unique-files are generated. The name of the unique-file is the ws_name followed by the extension. /WS:WS_NAME is the name of the workstation for which to prepare the unique_file. This name can be any name of up to 8 characters and must correspond to the workstation id of the NODE keyword in the NDI file. /WSL:WS_LIST_FILE is the name of a file containing a list of workstations for which to prepare the unique_file. The names of the workstations follow the same rules as ws_name and must be separated by blanks, tab, new-line. /EXT:EXTENSION is the extension that must follow ws_name when generating the unique_file names. The workstation name and the extension will make up the complete name of each unique_file. NOTE: Using the new syntax (/WS or /WSL options), precludes using the NVDMUFM system variables, such as the environment variables, and the LAN server and Communications Manager variables. All variables must be defined manually in the NDI file. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 47 An Example of Using NVDMUFM With the enhanced NVDMUFM utility you can generate response files; for example, you can use NVDMUFM at a CC server to generate response files to install a product, and a list of CC Clients, provided that you have written a template file for the response files of that product. In the template file placeholders you replace the values for the response file keywords that you want to define for the CC clients. The placeholder name can be the keyword name enclosed between "&"s (ampersand). 1. Using the template file as a model, create an NDI file where you give a workstation-specific value for each placeholder. 2. Create a workstation list file where each line is the name of a CC client for which you want to generate a response file. 3. To generate response files in the RSP\CM2 subdirectory of a directory named CID, type the following command: NVDMUFM CM2.TMP \CID\RSP\CM2 /NDI:CM2.NDI /EXT:RSP /WSL:CM2.WSL where: o CM2.TMP is the name of the template file. o CM2.NDI is the name of the node-dependent information file. o CM2.WSL is name of the file containing the list of CC clients for which the response files will be prepared. Each response file will have the same name as the workstation in CM2.WSL followed by the extension .RSP. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 48 DOS Limitation The installation command in a change file profile cannot be greater than 128 characters due to a DOS limitation. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 49 DiskCamera Limitation DiskCamera fails when monitoring zero-byte files due to an OS/2 and DOS limitation. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 50 CDM Local CC Domain: Shows Workstation Status Only if Explicitly Requested NetView DM/2 tries to contact all its clients when the CDM local CC domain is opened. If the number of clients is high, the connection time may be expensive. This performance problem may be bypassed using the environment variable ANX_WS_STATUS. If ANX_WS_STATUS environment variable is set to 'N' before NetView DM/2 CDM dialog is started, connection with clients is not established when the CDM local CC domain is opened. In this case the local CC domain displays the list of clients associated with a bitmap indicating that the status for the particular client is unknown. NOTE: A question mark in the bitmap indicates that the status for the related workstation is unknown. When the environment variable ANX_WS_STATUS is set to 'N' the workstation status can be retrieved through the 'Selected/Show Status' function in the CDM local CC domain. When invoked, the 'Selected/Show Status' function displays the current status for the selected workstations. When the environment variable ANX_WS_STATUS is not set to 'N', the 'Selected/Show Status' function in the local CC domain can be used to update the current status with any recent changes. In this case this function may be used as a partial refresh of the list of workstations. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 51 CDM Message Log: Filtering Messages According to the Severity 'Include Messages' is the new dialog which permits filtering messages in the MESSAGE.DAT according to their severity (Error, Informational, Warning). It may be displayed from the new function 'View/Include' in the CDM Message Log window. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 52 Language Support: Light Locale Support for English and Kanji It is possible to request NetView DM/2 to display the messages in one of two desired languages: Kanji or English. If you want English commands, type LOCALE ENG from a any OS/2 Command Prompt. If you want Kanji messages type LOCALE KNJ from any OS/2 Command Prompt. The command must be processed with the CDM stopped. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 53 NVDMUPFS: File System Configurator for Maintenance Systems NVDMUPFS is a procedure to configure the PWS in an unattended manner. It has the same function of NVDMUPO and refers to the same messages. The only verb that cannot be used is AddProgram. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 54 OS/2 DiskCamera Introduction General description Disk Camera for OS/2 is a component of NetView DM/2 that simplifies the process of replicating the installation of an OS/2 application package on a large number of workstations. The DiskCamera component supports the following process: 1. The package to be replicated is first installed on the preparation site workstation. 2. DiskCamera monitors the installation process for OS/2 programs to identify the list of files being installed and to record the changes applied to the common files (CONFIG.SYS, STARTUP.CDM, AUTOEXEC.BAT, WIN.INI, SYSTEM.INI, PROGMAN.INI). 3. DiskCamera records the information collected in monitoring the installation phase at the preparation site in a form that NetView DM/2 can process (the change file and change file profile). 4. The execution of NetView DM/2 at the target workstations with information collected in the previous steps replicates the installation of the package. 5. To allow the workstation user to apply some changes to specific target workstations, an option is provided to edit the objects created by Disk Camera for OS/2 (the modification file and the change file profile). Areas of applicability and Limitations The Disk Camera for OS/2 model is ideally suited for installing, in an unattended fashion, application packages on large number of workstations with similar hardware and software configurations. If the application package is provided with a response file driven installation procedure and differences among target workstations are significant, than the CID process is clearly more effective. The following limitations needs to be taken into account: 1. It is assumed that the whole installation takes place on a single drive. 2. Only the following text common files are tracked: o CONFIG.SYS CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 55 o STARTUP.CDM o AUTOEXEC.BAT o WIN.INI o SYSTEM.INI o PROGMAN.INI 3. If the installation process modifies other .INI files (for instance, PROTOCOL.INI, IBMLAN.INI, etc.) the related changes are not applied on the companion file of the target workstation, but the whole file of the preparation site is distributed. 4. The capture of the information used for the replication takes place in comparing the situation before starting the installation program and after its completion. Given the multitasking nature of OS/2, other tasks may modify the common files during this phase. Disk Camera for OS/2 has no means to distinguish the origin of all these changes therefore it takes a picture of all of them, and reapplies them at the target workstations. 5. The way DiskCamera records the changes in a common file addresses a limited subset of all possible changes. Operational Scenario When you use Disk Camera for OS/2, the following events occur: o NVDMPRE must be invoked specifying the target drive. See "Commands and Syntax" for more information about command formats and parameters. o Run the OS/2 application installation at the preparation site. NOTES: The user is required to install the software on the same target drive passed to NVDMPRE. o NVDMPOST must be invoked specifying the target drive. See "Commands and Syntax" for more information about command formats and parameters. o The log file NVDMUPO.LOG is created or appended. This file contains messages pertaining to the software package's installation. It is created under the current directory. o The modification file NVDMUPO.MOD is created. This file contains a list of the modifications made to the system files during the installation of the software package. The system files are CONFIG.SYS and STARTUP.CDM. The modification file is created in the \NVDMTMP directory on the installation target drive. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 56 o The change file profile NVDMUPO.PRO is created. This file contains a list of the software package files that were copied over to the preparation site, the modification file itself, and the name of a program to invoke to update the system files on the client workstation, based on the statements created in the modification file. This file can be used later by NetView DM/2 to build the change file for subsequent delivery using the install action to the OS/2 clients. It is created in the \NVDMTMP directory on the installation target drive. NOTE: Refer to NetView DM/2 User's Guide for more information about the structure of change file profiles. Both the modification file and the change file profile can be edited. Usage Using Disk Camera for OS/2 at the Preparation Site The following steps show how to use Disk Camera for OS/2 to install a software package at the preparation site: 1. Insert the diskette, if any, containing the installation procedure. The installation procedure could also be in a different partition of the hard disk. 2. Run Disk Camera for OS/2 NVDMPRE specifying the target drive. Example: NVDMPRE C: 3. Run the OS/2 application installation procedure. Example: A:\SETUP C: The User is required to install the software on the same target drive passed to NVDMPRE. 4. Run Disk Camera for OS/2 NVDMPOST specifying the target drive. Example: NVDMPOST C: At the end of the installation, Disk Camera for OS/2: o Creates the directory NVDMTMP on the target drive. This directory contains two files: - The modification file NVDMUPO.MOD - The change file profile NVDMUPO.PRO CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 57 When the installation completes, Disk Camera for OS/2 resumes control of the workstation. To keep all of the information that Disk Camera for OS/2 has saved, do not restart the workstation when asked by the installation program. Wait instead until NVDMPOST has finished its processing: ________________________________________________________ o Adds the change file profile NVDMUPD.PRO to the catalog section o Builds the change file using the NVDMUPO.PRO change file profile o Installs the change file at the CC Clients Other Considerations When Using DiskCamera The following considerations apply to using Disk Camera for OS/2. o Disk Camera for OS/2 detects the changes made to the system files by the installation program, but cannot interpret the logic behind them. For example, if one of the actions performed during installation is the addition of a statement to the preparation site's CONFIG.SYS file in the third record, Disk Camera for OS/2 notes the addition of this statement to the system file. The target system's CONFIG.SYS file, however, may be different from that of the preparation site, and adding a new record in its third position may be incorrect (for example, if there was only one line in the file) or even impossible. In this case, Disk Camera for OS/2 adds a statement to the modification file, such as: AddStatement(BOTTOM,<stmt>) ( for the CONFIG.SYS ) or AddStatement(TOP,<stmt>) ( for the STARTUP.CMD ) You can change the string BOTTOM with TOP and TOP with BOTTOM . Similarly, if an installation procedure inserts a token in a central position of a SET command, Disk Camera for OS/2 is not able to replicate the event at the CC client workstation. For example, suppose that this procedure inserts the token C:\TOKEN in the second position of the SET PATH statement because it must follow the first token, C:\IBMLAN: PATH C:\IBMLAN;C:\TOKEN;C:\OS2 In this case, Disk Camera for OS/2 does not provide a statement to replay the event on a CC client workstation, but instead inserts the statement: UpdateStatement(RIGHT,<SET PATH>,<C:\TOKEN>) CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 58 o Disk Camera for OS/2 cannot monitor a change that replaces a file with another having the same size, full path, date, and time attributes. o Every time you use Disk Camera for OS/2 on target drive, the modification files and change file profiles created by the previous execution of Disk Camera for OS/2 are overwritten. o When running at the preparation site, DiskCamera creates on the target drive the NVDMTMP directory, containing the NVDMUPO.MOD and NVDMUPO.PRO files. If you rename the directory and the files before building the software package, you must also change the names in the profile generated by DiskCamera. For example, if you are installing SmallTalk using DiskCamera and you choose to rename the NVDMTMP directory and the NVDMUPO.MOD and NVDMUPO.PRO files respectively to SMALLTALK, SMALLTALK.PRO, and SMALLTALK.MOD, the profile created by DiskCamera may look like this: TargetDir = C:\ Section Install Begin Program = NVDMUPO.EXE Parms = $(TargetDir)NVDMTMP\NVDMUPO.MOD /T:$(TargetDir) End Section FileSpecList Begin \VDOS\*.* /is \NVDMTMP\NVDMUPO.MOD End YOU MUST CHANGE IT AS FOLLOWS: TargetDir = C:\ Section Catalog Begin ObjectType = SOFTWARE GlobalName = SMALLTALK.10.PERM.PRODUCT.REF.1.0 Description = 'Smalltalk' End Section Install Begin Program = NVDMUPO.EXE Parms = $(TargetDir)SMALLTALK\SMALLTALK.MOD /T:$(TargetDir) End Section FileSpecList Begin \VDOS\*.* /is \SMALLTALK\SMALLTALK.MOD End o If a file changes its size and time on the target drive during the application installation but it is not a application file ( for example SWAPPER.DAT ), Disk Camera for OS/2 inserts it in the profile. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 59 Commands and Syntax NVDMPRE This utility allows you to monitor the system before the application software is installed. A log file, NVDMUPO.LOG, is created in the <ProductDir>\BIN directory. Format +---------------------------------------------------------------------------+ | | | >>--NVDMPRE--Installation_target_drive-->< | | | +---------------------------------------------------------------------------+ Parameters The parameters for this utility are: o INSTALLATION_TARGET_DRIVE Specifies the name of the drive where the software is to be installed. For example, if you install your application under the C:\TMP directory, you must specify C: as the installation target drive. NVDMPOST This utility allows you to prepare a change file profile to install an OS/2 application. This installation replicates the effects of the application installation that was performed at the preparation site. A log file, NVDMUPO.LOG, is created in the <ProductDir>\BIN directory. Format +---------------------------------------------------------------------------+ | | | >>--NVDMPOST--Installation_target_drive-->< | | | +---------------------------------------------------------------------------+ CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 60 Parameters The parameters for this utility are: o INSTALLATION_TARGET_DRIVE Specifies the name of the drive where the software is to be installed. For example, if you install your application under the C:\TMP directory, you must specify C: as the installation target drive. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 61 New NetView DM/2 Force Install Parameter with the INSTALL Task NetView DM/2 V2.1 and NetView DM/MVS 1.6 have been enhanced to allow you to force the reinstallation of an object that has been already installed in production (that is at the end of the install cycle). This provides you with a way to specify that an object can be reinstalled if it is already in INRU status. EXTERNAL CHANGES: A new option can be specified for the Install action: o NetView DM/MVS - ForceInstall = Y/N (SPMF) - ForceInstall = YES | DESIRED | NO (GIX or BATCH) o /F by command line (NetView DM/2) Example: Let's suppose that the object IBM.NVDM2.V21.REF.1 is installed on workstation CLIENT1 with INRU status; the following command invocation allows to reinstall the object disregarding the INRU status: CDM INSTALL IBM.NVDM2.V21.REF.1 /WS:CLIENT1 /F o No Force / Force by CDM Dialog submenu (NetView DM/2) This option can be set: o At NetView DM/MVS from GIX, Batch Utilities or the C-API NOTE: The FORCE install is supported at NetView DM/MVS by Release 1.6. o At a NetView DM/2 remote administrator workstation, from the dialogs or the Command line o At a NetView DM/2 CC Server, from the dialogs or the command line NetView DM/2 also accepts the DESIRED value, processing it as if it were ALLOWED. However, the NetView DM/2 dialogs allow only the specification of ALLOWED and NO values. If the key is set to ALLOWED in the request and a change file is already INRU, then the change file is reinstalled. If the object was simply cataloged the Force option has no effect and it is accepted. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 62 To summarize: o An object can be reinstalled if the request contains the option ForceInstall = ALLOWED or DESIRED. o Any kind of change file (REF FIX UPD) is accepted. o Only a refresh is accepted for relational tables. o Any kind of new install options are accepted. o The object is cataloged or already installed in use in active area. The following picture shows the state transition when you reinstall an already-installed global name. +==========================================================+ | | | *------* After Change | | | | Controller Check Installation is | | | INRU |--------* successful *------* | | | | | |FINAL | | | *------* | *---------|STATUS| | | | *----* | *------* | | *-->---|CAT |--->--* | | *-->---| |--->--* *------* | | | *----* | | CAT | | | *------* | *---------| | | | | | | *------* | | | CAT |--------* Installation | | | | fails | | *------* | | | | | +==========================================================+ If the object is successfully installed all the side effects apply. If the object is not installed, the new object status is CATALOGUED; in a host connected environment, NetView DM is notified of that as a side effect in the Agent Object of Reporting and it updates the DRD. Also in a remote administrator environment NetView DM/2 remote administrator is notified and updates the status to CATALOGUED. If the installation involves corequisites, and the installation of one object fails, all the objects in the corequisite group change status from SCHEduled back to CATALOGUED. CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 63 Limitations to the Current Implementation If the installation of an object fails, the object is always tracked as not installed; this happens also when the installation fails because the external install program is not found (that is, an error occurs even if the reinstallation has been performed). This behavior is correct because, if an object is to be reinstalled, this may mean that the software was corrupted on that work-station (so the tracking information before the reinstallation is not congruent with what was really on the workstation). CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 64 CHAPTER 4. CDM USER'S GUIDE ENHANCEMENTS 65 CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE Page 98 - TOPIC 4.8.4.1 - Deleting the Installation History In the Delete Install History window, information on the catalog status and the installation date and time of the selected object is also displayed. Page 100 - TOPIC 4.8.5.1 - Listing All the Objects Installed on a Workstation In the Installed Objects window, information on the installation date and time of the selected object is also displayed. Page 222 - TOPIC 8.5 - ADD_DEST or ADDDEST In the Parameters section, add the following example for the @file_name parameter: +---------+-----------+----+---------+---------+----+-----------------------+ | NETWK1 | NDM1 | S | NDM1 | LU62 | M | Focal Point | +---------+-----------+----+---------+---------+----+-----------------------+ | NETWK1 | SERV1 | S | SERV1 | LU62 | O | CC Server - Workst. A | +---------+-----------+----+---------+---------+----+-----------------------+ | NETWK1 | CLIENTB | C | NETWK1 | SERV1 | O | Client B - Workst. B | +---------+-----------+----+---------+---------+----+-----------------------+ | NETWK1 | CLIENTC | C | NETWK1 | SERV1 | D | Client C - Workst. C | +---------+-----------+----+---------+---------+----+-----------------------+ NOTE: No comment lines are allowed in the file. A description of each column of the file follows: o Column 1: RGN o Column 2: REN o Column 3: ROLE o Column 4: For a server, its LU name; for a client, the RGN of its server o Column 5: For a server, its LU mode; for a client, the REN of its server o Column 6: Operating system o Column 7: Description (C) Copyright IBM Corp. 1991, 1995 66 Page 230 - TOPIC 8.8 - BUILD In the Catalog Section Statements section, make the following change: o Replace the keyword "ObjectSize" with "ProcessingSize". Page 235 - TOPIC 8.8 - BUILD In the section Using Variables in the Install Section: o Remove all references to the ANXDRIVE variable, which no longer exists. In the section Example Change File Profiles, add the following information after the first paragraph: o You can also include comments in change file profiles. A comment always begins with a semicolon (;) and extends to the end of the line, for example: ResponseFile=SA:\RSP\NVDM2\SAME.RSP;The same RF Page 252 - TOPIC 8.12 - CONFIG Add the following paragraph to the beginning of the introductory material: o In NetView DM/2 2.0, the CONFIG command added both remote destinations and transmission queues. In NetView DM/2 2.1, this command adds transmission queues only. Use the ADDDEST command to add remote destinations. Page 253 - TOPIC 8.12 - CONFIG In the Control File Layout section, note that the CDM CONFIG command does not act upon the destination table. This command adds transmission queues, but not remote destinations. Page 285 - TOPIC 8.27 - LIST_WS or LISTWS In the Example section, replace the example output with the following: CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 67 Destination id : ITIBM0PC.I9RL00E4 Description : This is the Server Workstation type : Server Operating system : OS/2 Destination id : ITIBM0PC.MYCLIENT Server name : ITIBM0PC.I9RL00E4 Description : test client Workstation type : Client Operating system : OS/2 Status : Inactive Page 289 - TOPIC 8.30 - QUERY_REP or QUERYREP Replace the second paragraph in the introductory section with the following: o Use this command to display the contents of a report on a request (SNACR or the contents of the reply file), which can contain sense code data, as well as the request ID and destination ID of a particular request. Under the Example section, replace the existing command syntax and example with the following: CDM QUERYREP SND00000 Request ID : SND0000 Request Type : SEND Destination id : ITIBMCEN.SNASASA SNA Condition Report : 089A0001 Reply File Name : REP0001 Page 355 - TOPIC A.1 - Detailed Scenarios At the begin of the section, ADD the following sections. CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 68 Before Migrating NetView DM/2 from Version 2.0 to 2.1 This section illustrates some actions that must be taken to optimize the accesses to the NetView DM/2 Version 2.1 catalog and consequently enhance the performance of the product. The objective is to change the value for the parameter SQLENSEG in the Database Manager configuration of a CC server from 25 (default value) to 40. Be sure to do this before performing any of the scenarios that involve either the migration from NetView DM/2 Version 2.0 to 2.1 or the Version 2.1 installation. If you already installed Version 2.1 after changing the configuration of Database Manager, you have to reinstall NetView DM/2 Version 2.1 with the option configuration only (/CO). Follow these steps: o CHANGING THE DATABASE MANAGER CONFIGURATION IN AN ATTENDED WAY From the OS/2 command line issue the commands: 1. DBM UPGRADE DATABASE MANAGER CONFIGURATION USING SQLENSEG 40 2. STOPDBM 3. STARTDBM o CHANGING THE DATABASE MANAGER CONFIGURATION IN AN UNATTENDED WAY Create a change file profile and a command procedure as follows: 1. DBMCFG.PRO change file profile TargetDir = SA:\ Section Catalog Begin ObjectType = SOFTWARE GlobalName = IBM.NDM2_21.DB.CONFIG.REF.1 Description = Change file for changing DBM configuration End Section Install Begin Program = $(SourceDir)\DBMCFG.CMD SourceDir = SA: PhaseEnd = Yes End Section FileSpecList Begin DBMCFG.CMD End 2. DBMCFG.CMD command procedure CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 69 CALL DBM UPGRADE DATABASE MANAGER CONFIGURATION USING SQLENSEG 40 return x2d('FE00') Build the change file from the directory where the command procedure is stored and perform the installation of the change file IBM.NDM2_21.DB.CONFIG.REF.1 on the target server. The installation on the target server can be driven either by another CC server running NetView DM/2 Version 2.1 with the Remote administrator feature installed or by the NetView DM host by means of an appropriate plan. Page 373 - TOPIC A.2 - Installing and Migrating Software for Multiple CID-Enabled Products In the step "To copy the NetView DM/2 Version 2.1 product image," make the following change: o In the example, replace the "/FP" parameter with "/RA". Page 421 - TOPIC A.4 - Installing TCP/IP Version 2.0 in a Pristine Environment Under the Prerequisites section, second bullet, change the fifth sub-bullet as follows: o IBM NetBIOS Version 2.08 (Driver release 1.5) for TCP/IP for OS/2, CSD level UB09313 (under C:\NBTCP2) Page 423 - TOPIC A.4 - Installing TCP/IP Version 2.0 in a Pristine Environment Under the Scenario Steps section, Step 2, part b, add the following file to the list: o ACSNETB.DLL (C:\NBTCP2\NBTCP) Page 429 - TOPIC A.4 - Detailed Scenarios ADD the following scenario after the "Installing TCP/IP Version 2.0 in a Pristine Environment" scenario. TCP/IP Version 2.0 Maintenance Environment Scenario CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 70 Introduction This scenario shows you how to create a maintenance environment on a CC client workstation running TCP/IP Version 2.0, along with OS/2 Version 2.1 and NetView DM/2 Version 2.1. You can perform all the scenario steps at the OS/2 command prompt, or you can select the appropriate options using the CDM dialogs. Objectives The main purpose of this scenario is to set up a seed system on a CC client workstation attached to a CC server, both of which are running TCP/IP Version 2.0 transmission protocol and OS/2 Version 2.1, in order to allow the unattended installation or migration of CSDs or new releases of OS/2. This scenario describes the unattended migration from OS/2 Version 2.1 to OS/2 Version 2.11, by creating a maintenance system before installing the new level of OS/2 in the production environment. The steps include the following: 1. Loading the code images of the following products under the CC server shared areas: o OS/2 Version 2.11 o NetView DM/2 Version 2.1 o IBM TCP/IP Version 2.0 base kit o LAPS kit of TCP/IP Version 2.0 o IBM NetBIOS for TCP/IP for OS/2 Version 2.08 2. Preparing, at the CC server, the change file profiles, the response files, and the REXX procedures needed for the installation process. 3. Submitting, from the CC server, the request for installing at the CC client workstation the following software: o OS/2 Version 2.11 (maintenance environment) o LAPS kit of TCP/IP Version 2.0 (maintenance environment) o TCP/IP Version 2.0 base kit CSD level UN50832 (maintenance environment) o NetBIOS for TCP/IP for OS/2 Version 2.08 (maintenance environment) o NetView DM/2 Version 2.1 client code (maintenance environment) o OS/2 Version 2.11 (production environment) 4. Ensuring that the installed objects have the correct status. NOTE: TCP/IP Version 2.0 and NetBIOS for TCP/IP do not directly provide a maintenance environment, but the maintenance environment can be created by copying the TCP/IP and NetBIOS/TCP modules to the C:\SERVICE directory and updating the CONFIG.SYS with a REXX procedure. CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 71 Environment The network configuration assumed for this scenario is a stand-alone LAN, and LT0054A0 is the name of the CC client workstation as defined at the CC server LT0064A0. Prerequisites For this scenario it is assumed that: o NetView DM/2 is installed at the CC server as a CC server in a stand-alone LAN. o The CC server has the following software installed: - OS/2 Version 2.1 (in the C:\OS2 directory) - DB2/2 for OS/2 Version 1.0 - Communication Manager/2 Version 1.0 - IBM TCP/IP Version 2.0 base kit for OS/2 Versions 2.1, CSD level UN50832 (in the C:\TCPIP directory) - IBM NetBIOS Version 2.08 (Driver release 1.5) for TCP/IP for OS/2, CSD level UN09313 (in the C:\NETBIOS2 directory) - LAPS kit for TCP/IP Version 2.0 o The CC client has the following software installed: - OS/2 Version 2.1 (in the C:\OS2 directory) - IBM TCP/IP Version 2.0 base kit for OS/2 Versions 2.1, CSD level UN50832 (in the C:\TCPIP directory) - IBM NetBIOS Version 2.08 (Driver release 1.5) for TCP/IP for OS/2, CSD level UN09313 (in the C:\NETBIOS2 directory) - LAPS kit for TCP/IP Version 2.0. o The CC client is currently attached to the CC server. CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 72 Scenario Steps Step 1. PREPARING THE CC SERVER ENVIRONMENT Refer to NetView DM/2 Version 2.1 CDM User's Guide, "Step 1. _______________________________________________ Preparing the Environment for the CC Servers" on page 369, and "Step 2. Copying OS/2, DOS and Other CID Software Product Images" on page 371, for all the steps to be performed at the CC server, for creating the recommended directory structure under C:\SHARE_A and C:\SHARE_B., and for copying the product images. The directory names related to the products for which you need code images, profiles, response files, and log files include: o OS2V211 (OS/2 Version 2.11) o NVDM2V21 (NetView DM/2 Version 2.1) o TCPIPV20 (TCP/IP Version 2.0 Base CSD level UN50832) o LAPS7045 (LAPS at CSD level 7045 with TCP/IP device drivers applied) o NBTCP208 (NetBIOS for TCP/IP for OS/2 Version 2.08) OS/2 V2.11, LAPS7045 and NBTCP208 are not mentioned. You need to create IMG, PRF, and RSP directories under C:\SHARE_A and a LOG directory under C:\SHARE_B for both of them. To copy OS/2 V2.11 code image to the C:\SHARE_A\IMG\OS2V211 directory, follow this procedure: a. Copy the OS/2 CID Utility to the CC server as follows : o Insert OS/2 V2.11 diskette 2 into drive A: and issue the following commands from an OS/2 session: C: CD C:\SHARE_A\IMG\OS2V211 UNPACK2 A:\CID C:\SHARE_A\IMG\OS2V211 UNPACK2 A:\REQUIRED C:\SHARE_A\IMG\OS2V211 /N:RSPINST.EXE This step unpacks the following programs to the OS/2 V2.11 code image directory: - SEIMAGE.EXE - SEDISK.EXE - SEMAINT.EXE - SEINST.EXE - RSPINST.EXE b. Copy the OS/2 V2.11 product image to the CC server as follows: o Issue the following command from an OS/2 session: C:\SHARE_A\IMG\OS2V211\SEIMAGE /S:A: /T:C:\SHARE_A\IMG\OS2V211 SEIMAGE copies each diskette into a separate subdirectory with the same name as their volume labels. CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 73 c. Apply APAR PJ13412: o Insert the PJ13412 diskette into drive A: and issue the following command from an OS/2 session: CD C:\SHARE_A\IMG\OS2V211 RENAME SEMAINT.EXE SEMAINT.OLD COPY A:\SEMAINT.EXE APAR PJ13412 fixes an SEMAINT problem that causes failures on systems that do not have the newer UNPACK and UNPACK2. This APAR provides a new SEMAINT that accesses this files from the Service Directory, or you can provide a procedure to copy the newer UNPACK, UNPACK2 into C:\OS2 before running SEMAINT. To copy LAPS V2.20 (CSD Level 7045) code images from the LAPS diskette into the C:\SHARE_A\IMG\LAPS7045 directory, enter the command: A:\LAPSDISK A:\ C:\SHARE_A\IMG\LAPS7045 To copy NetBIOS for TCP/IP code images from the NetBIOS diskette from the C:\SHARE_A\IMG\NBTCP208 directory enter the command: A:\NBTCP208 This command unpacks all the files of NetBIOS for TCP/IP Version 2.08 under the C:\SHARE_A\IMG\NBTCP208 directory. NOTE: The TCP/IP protocol drivers are supplied only with the LAPS (V2.13) that comes with TCP/IP V2.0. You must follow the procedure below to incorporate the TCP/IP drivers to the LAPS code image on the CC server. a. Retrieve TCP/IP driver from the TCP/IP LAPS diskette as follows: o Insert the TCP/IP diskette into drive A: and issue the following commands from an OS/2 session: C: MD C:\TEMP CD C:\TEMP PKUNZIP2 A:\IBMCOM\PROTOCOL\PROTOCOL.ZIP This step UNZIPs the TCP/IP driver from the TCP/IP LAPS diskette to a temporary directory called C:\TEMP. The following four files should be added to the C:\TEMP directory: - ifndis.sys - ifnet.sys - NETBIND.EXE CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 74 - tcpip.nif b. Integrate the TCP/IP drivers to the LAPS image previously created under the directory C:\SHARE_A\IMG\LAPS7045: o Issue the following command from an OS/2 session: C: CD C:\SHARE_A\IMG\LAPS7045\IBMCOM\PROTOCOL PKZIP2 -a PROTOCOL.ZIP C:\TEMP\IFNDIS.SYS PKZIP2 -a PROTOCOL.ZIP C:\TEMP\IFNET.SYS PKZIP2 -a PROTOCOL.ZIP C:\TEMP\TCPIP.NIF This step adds the TCP/IP drivers to the PROTOCOL.ZIP of the LAPS code image. Step 2. PREPARING THE RESPONSE FILES Following are the response files that are used during the migration process: C:\SHARE_A\RSP\LAPS7045\$(WORKSTATNAME).RSP ------------------------------------------------------------------------------- INST_SECTION = ( UPGRADE_LEVEL = old INSTALL = product ) PROTOCOL = ( [PROT_MAN] DRIVERNAME = PROTMAN$ [IBMLXCFG] LANDD_nif = LANDD.NIF tcpip_nif = tcpip.nif IBMTOK_nif = IBMTOK.NIF [LANDD_nif] DriverName = LANDD$ Bindings = IBMTOK_nif NETADDRESS = "t400065600054" ETHERAND_TYPE = "I" SYSTEM_KEY = 0x0 OPEN_OPTIONS = 0x2000 TRACE = 0x0 LINKS = 68 MAX_SAPS = 5 MAX_G_SAPS = 0 CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 75 USERS = 5 TI_TICK_G1 = 255 T1_TICK_G1 = 15 T2_TICK_G1 = 3 TI_TICK_G2 = 255 T1_TICK_G2 = 25 T2_TICK_G2 = 10 IPACKETS = 250 UIPACKETS = 100 MAXTRANSMITS = 6 MINTRANSMITS = 2 TCBS = 64 GDTS = 30 ELEMENTS = 0800 [tcpip_nif] DriverName = TCPIP$ Bindings = IBMTOK_nif [IBMTOK_nif] DriverName = IBMTOK$ ADAPTER = "PRIMARY" MAXTRANSMITS = 6 RECVBUFS = 2 RECVBUFSIZE = 256 XMITBUFS = 1 ) ------------------------------------------------------------------------------- C:\SHARE_A\RSP\TCPIPV20\$(WORKSTATNAME).RSP ------------------------------------------------------------------------------- TARGETDIR=C:\SERVICE HOST_NAME=LT0054A0 IP_ADDRESS=150.5.100.54 BR_ADDRESS=150.255.255.255 ------------------------------------------------------------------------------- C:\SHARE_A\RSP\NVDM2V21\$(WORKSTATNAME).RSP ------------------------------------------------------------------------------- ServerName = LT0064A0 ClientName = LT0054A0 ------------------------------------------------------------------------------- CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 76 C:\SHARE_A\RSP\OS2V211\OS211UPG.RSP ------------------------------------------------------------------------------------------------------------------------------- ************************************************************** ************************************************************** * * * * * Advance Power Management * * Mouse * * * * * * Specifies whether or not to install APM. * * Specifies which mouse device driver, if any, to * * * * install * * Valid Parms: * * * * * * Valid Parms: * * 0=Don't install * * * * 1=Autodetect (DEFAULT) * * 0 = No pointing device support * * 2=Install * * 1 = PS/2 Style Pointing Devicee (DEFAULT) * * * * 2 = Bus Version * ************************************************************** * 3 = Serial Version * * 4 = InPort Version * APM=1 * 5 = Logitech (tm) 'C' Series Serial Mouse * * 6 = IBM PS/2 Touch Display * *************************************************************** * 7 = Logitech 'M' Series Mouse * * * * 8 = PC Mouse Systems (tm) Mouse * * AlternateAdapter * * 9 = Other Pointing Device for Mouse Port * * * * * * Specifies secondary adapter for two display systems. * ************************************************************** * This should be a lower or equal resolution display since * * the highest resolution display will be primary for PM. * Mouse=1 * * * Valid Parms: * ************************************************************** * * * * * 0=None (DEFAULT) * * MousePort * * 1=Other than following (DDINSTAL will handle) * * * * 2=Monochrome/Printer Adapter * * Specifies to which port a serial-type mouse should * * 3=Color Graphics Adapter * * be attatched (valid for serial or Logitech(tm) mice) * * 4=Enhanced Graphics Adapter * * * * 5=PS/2 Display Adapter * * Valid Parms: * * 6=Video Graphics Adapter * * * * 7=8514/A Adapter * * 0 = No port necessary (DEFAULT) * * 8=XGA Adapter * * 1 = COM1 * * 9=SVGA Adapter * * 2 = COM2 * * * * 3 = COM3 * *************************************************************** * 4 = COM4 * * * AlternateAdapter=0 ************************************************************** ************************************************************** MousePort=0 * * * BaseFileSystem * ************************************************************** * * * * * Specifies which file system should be used to format * * OptionalFileSystem * * the install partition * * * * * * Specifies whether or not to install optional file * * Valid Parms: * * system(s) i.e. HPFS * CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 77 * * * * * 1=HPFS (DEFAULT) * * Valid Parms: * * 2=FAT * * * * * * 0=Do Not Install Optional File System(s) * ************************************************************** * 1=Install Optional File System (DEFAULT) * * * BaseFileSystem=1 ************************************************************** *************************************************************** OptionalFileSystem=1 * * * CDROM * ************************************************************** * * * * * Specifies which, if any, CD ROM devices you wish to * * OptionalSystemUtilities * * install support for. * * * * * * Specifies whether or not to install the following * * Valid Parms: * * system utilities. * * * * * * 0 = None * * Valid Parms: * * 1 = Autodetect * * * * 2=CDTechnology T3301 * * 0=Install none * * 3=HitachiCDR-1650,1750,3650 * * 1=Install all (DEFAULT) * * 4=HitachiCDR-3750 * * 2=Backup Hard Disk * * 5=IBMCD-ROM I * * 3=Change File Attributes * * 6=IBMCD-ROM II * * 4=Display Directory Tree * * 7=NEC25,36,37,72,73,74,82,83,84 * * 5=Manage Partitions * * 8=NECMultiSpin 38,74,84 * * 6=Label Diskettes * * 9=PanasonicCR-501,LK-MC501S * * 7=Link Object Modules * * 10=PioneerDRM-600 * * 8=Picture Utilities * * 11=PioneerDRM-604X * * 9=PMREXX * * 12=SonyCDU-541,561,6211,7211 * * 10=Recover Files * * 13=SonyCDU-6111 * * 11=Restore Backed-up Files * * 14=TexelDM-3021,5021 * * 12=Sort Filter * * 15=TexelDM-3024,5024 * * 13=Installation Aid * * 16=Toshiba3201 * * * * 17=Toshiba3301,3401 * * Example: * * 18=OTHER * * OptionalSystemUtilities=2,9,4 * * * * would install Backup, PMREXX and Tree utilities. * * NOTE: Autodetection is enabled only when all scsi * * * * device drivers are loaded. * ************************************************************** *************************************************************** OptionalSystemUtilities=1 CDROM=0 ************************************************************** * * ************************************************************** * OS2IniData * * * * * * CountryCode * * Specifies a profile string to be written to the * * * * user configuration file OS2.INI. There may be * * Specifies which country should be installed. This * * multiple occurrences of this keyword. * * causes all country information to be installed. * * * * * * Valid Parms: * * Valid Parms: * * * * * * KEYWORD = /AppName/KeyName/KeyValue/ * * 3 digit country code (DEFAULT shipped version) * * * CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 78 * * * NOTE: Since each of these names can contain * ************************************************************** * imbedded blanks and whitespace, the "slash" * * character must be used as a delimiter. There * CountryCode=039 * must be three tokens delineated on all sides or * * this keyword will be ignored. * ************************************************************** * * * * ************************************************************** * CountryKeyboard * * * OS2IniData=/AppName/KeyName/KeyValue/ * Specifies which country keyboard should be installed. * * This causes all keyboard information to be installed. * ************************************************************** * * * * * Valid Parms: * * PCMCIA * * * * * * 2-5 character keyboard code (DEFAULT="US") * * Specifies whether or not to install PCMCIA. * * * * * ************************************************************** * Valid Parms: * * * CountryKeyboard=IT141 * 0=Don't install * * 1=Install (DEFAULT) * ************************************************************** * * * * ************************************************************** * DefaultPrinter * * * PCMCIA=1 * Specifies which default printer to install * * * ************************************************************** * Valid Parms: * * * * * * PrimaryCodePage * * 0=None * * * * or * * Specifies whether "national" or "multi-lingual" code * * * * page is primary (first active code page before * * Keyvalue=printer driver index (DEFAULT=line # of * * switching). * * 42XX) in PRDESC.LST shipped on first printer diskette* * * * * * Valid Parms: * * NOTE: the driver index is the same as the line * * * * number in the ASCII PRDESC.LST file that * * 1=National (DEFAULT) * * the desired printer name appears on * * 2=Multilingual * * * * * ************************************************************** ************************************************************** DefaultPrinter=0 PrimaryCodePage=1 ************************************************************** ************************************************************** * * * * * DiagnosticAids * * PrinterPort * * * * * * Specifies whether or not to install certain RAS * * Specifies to which printer port the default printer * * utilities. * * should be attached * * * * * * Valid Parms: * * Valid Parms: * * * * * * 0=Don't install * * 1=LPT1 (DEFAULT) * * 1=Install (DEFAULT) * * 2=LPT2 * CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 79 * * * 3=LPT3 * ************************************************************** * 4=COM1 * * 5=COM2 * DiagnosticAids=1 * 6=COM3 * * 7=COM4 * ************************************************************** * * * * ************************************************************** * DisplayAdapter * * * PrinterPort=1 * Specifies which adapter should override the primary * * adapter detected by the install process * ************************************************************** * * * * * Valid Parms: * * ProcessEnvironment * * * * * * 0=Accept as correct (DEFAULT) * * Each of the Keyword/Keyvalue statements specified in * * 1=Other than following (DDINSTAL will handle) * * this response file may be added to the environment as * * 2=Color Graphics Adapter * * environment variables. * * 3=Enhanced Graphics Adapter * * This makes it possible for user programs, batch files, * * 4=Video Graphics Adapter * * etc. (UserExit) to access response file settings. * * 5=8514/A Adapter * * * * 6=XGA Adapter * * Valid Parms: * * 7=SVGA Adapter * * * * * * 0 = Do not add keyword/keyvalue statements specified * ************************************************************** * in this response file to environment. * * 1 = Add all keyword/keyvalue statements specified * DisplayAdapter=0 * in this response file to environment (DEFAULT). * * * ************************************************************** ************************************************************** * * * Documentation * ProcessEnvironment=1 * * * Specifies which documentation should be installed * ************************************************************** * * * * * Valid Parms: * * ProgressIndication * * * * * * 0=None * * Specifies whether or not to display progress indicators * * 1=All (DEFAULT) * * during the installation. Disabling this will allow a * * 2=OS/2 Command Reference * * frontend program to display something else while we do * * 3=OS/2 Tutorial * * our job in an unattended environment. * * 4=Rexx Documentation * * * * * * Valid Parms: * ************************************************************** * * * 0 = No progress indication * Documentation=1 * 1 = Progress indication (DEFAULT) * * * ************************************************************** ************************************************************** * * * DOSSupport * ProgressIndication=1 * * * Specifies whether or not to install DOS Box. * ************************************************************** * * * * * Valid Parms: * * RebootRequired * * * * * * 0=Don't install DOS * * Specifies if the machine should be automatically * CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 80 * 1=Install DOS (DEFAULT) * * warm booted when installation is complete. This is * * * * ignored if the ExtendedInstall response is specified. * ************************************************************** * * * Valid Parms: * DOSSupport=1 * * * 0=Ask user to reboot (DEFAULT) * ************************************************************** * 1=Auto-reboot * * * * * * WIN-OS/2Support * ************************************************************** * * * Specifies whether or not to install WIN-OS/2 * RebootRequired=0 * Environment. If do, select WIN-OS/2 groups or * * other components. This option is valid only * ************************************************************** * when option 1 (DOSSupport) is selected for * * * * the DOSSupport keyvalue. * * REXX * * * * * * Valid Parms: * * Specifies whether or not to install REXX * * * * * * 0=Do NOT install WIN-OS/2 * * Valid Parms: * * ---- Followings INSTALL WIN-OS/2 ---------------------- * * * * 1=All available groups and components (DEFAULT) * * 0=Don't Install REXX * * 2=WIN-OS/2 Readme File * * 1=Install REXX (DEFAULT) * * 3=WIN-OS/2 Accessories Group * * * * 4=WIN-OS/2 Screen Save Utility * ************************************************************** * 5=WIN-OS/2 Sound Utility * * 6=WIN-OS/2 Main and Startup Group ONLY (Minimum support)* REXX=1 * * * Note: * ************************************************************** * * WIN-OS/2 Main Group and StartUp Group will be * * * * installed mandatorily when WIN-OS/2 supported * * SCSI * * ( case 1,2,3,4,5 ). * * * * * Case 6 is minimum WIN-OS/2 support. * * Specifies which, if any, CD ROM adapter support you * * * * wish to install support for. * * Example: * * * * * * Valid Parms: * * WIN-OS/2Support=3,4 * * * * would install WIN-OS/2 Main Group, StartUp Group and * * 0 = None * * WIN-OS/2 Accessories and Screen Save Utility. * * 1 = Autodetect * * * * 2=Adaptec1510, 1520, 1522 * ************************************************************** * 3=Adaptec1540, 1542 * * 4=Adaptec1640 * WIN-OS/2Support=1 * 5=Adaptec1740, 1742, 1744 * * 6=DPTPM2011, PM2012 * ************************************************************** * 7=FutureDomain 845,850,850IBM,860,875,885 * * * * 8=FutureDomain 1650,1660,1670,1680,MCS700 * * WindowedWIN-OS/2 * * 9=FutureDomain 7000EX * * * * 10=IBMPS/2 SCSI Adapter * * Specifies whether Windows** applications should run in * * 11=IBM16-Bit AT Fast SCSI Adapter * * windowed sessions on the Presentation Manager desktop * * * * or in Full Screen sessions. This option is valid only * ************************************************************** * when option 1 (WIN-OS/2 Support) is selected for the * * DOSSupport keyvalue. * SCSI=1 * * * Valid Parms: * ************************************************************** CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 81 * * * * * 0=Windowed WIN-OS/2 sessions * * SerialDeviceSupport * * 1=Full Screen WIN-OS/2 sessions * * * * * * Specifies whether or not to install the serial * ************************************************************** * device driver. * * * *WindowedWIN-OS/2=1 * Valid Parms: * * * ************************************************************** * 0=Don't install * * * * 1=Install (DEFAULT) * * WIN-OS/2Desktop * * * * * ************************************************************** * Specifies what the WIN-OS/2 desktop should look like. * * This option is valid only when option 1 (WIN-OS/2 * SerialDeviceSupport=1 * Support) is selected for the DOSSupport keyvalue. * * Option 1 should be selected only if Windows** currently * ************************************************************** * exists (two related options follow this one). * * * * Option 2 should be selected only if WIN-OS/2 has * * SourcePath * * previously been installed. * * * * * * Specifies a single media (no disk switching) that should* * Valid Parms: * * be used as a source drive and directory from which to * * * * install. * * 0=Install standard WIN-OS/2 desktop (DEFAULT) * * * * 1=Copy existing Windows** desktop and use as the * * Valid Parms: * * WIN-OS/2 desktop (two related options follow) * * * * 2=Preserve WIN-OS/2 desktop currently installed * * KEYVALUE=drive and optional path * * * * DEFAULT=A:\ * ************************************************************** * * ************************************************************** *WIN-OS/2Desktop=0 SourcePath=C:\SHARE_A\IMG\OS2V211 ************************************************************** * * ************************************************************** * ExistingWindowsPath * * * * * * TargetDrive * * Specifies the path to an existing Windows** system. * * * * This option is valid only when option 1 is selected * * Specifies the target drive to which OS/2 should be * * for the WIN-OS/2Desktop keyvalue. * * installed. This drive is assumed to be a valid * * * * partition. If a partition other than C: is specified, * * Valid Parms: * * it is assumed that MOST support is already installed to * * * * enable booting an operating system from any partition. * * A string that specifies the path to the existing * * * * Windows** system * * Valid Parms: * * * * * ************************************************************** * KEYVALUE=d: * * * *ExistingWindowsPath= * where "d " is a valid partition that OS/2 may be * * installed to. * ************************************************************** * DEFAULT=first acceptable partition * * * * * * ShareDesktopConfigFiles * ************************************************************** * * * Specifies that the desktop configuration files should * TargetDrive=C: * be shared between an existing Windows** system and the * CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 82 * WIN-OS/2 system being installed. If this option is * ************************************************************** * selected, the Windows** desktop will be updated when * * * * changes are made to the WIN-OS/2 desktop. This * * WIN-OS/2TargetDrive * * option is valid only when option 1 is selected for the * * * * WIN-OS/2Desktop keyvalue. * * Specifies which valid partition drive to install * * * * WIN-OS/2. * * Valid Parms: * * * * * * Valid Parms: any valid FORMATTED partition. * * 0=Do not share the Windows** desktop configuration * * * * files * * C: (DEFAULT) * * 1=Share the Windows** desktop configuration files * * D: * * * * . * ************************************************************** * . * * * *ShareDesktopConfigFiles=1 * Z: * * * ************************************************************** * Example: * * * * * * DPMI * * WIN-OS/2TargetDrive=D: * * * * would install WIN-OS/2 to partition D located in * * Specifies which DPMI options to install. * * \OS2\MDOS\WINOS2 * * * * * * Valid Parms: * ************************************************************** * * * 0=none * *WIN-OS/2TargetDrive=C: * 1=All (DEFAULT) * * 2=Virtual DOS Protect Mode Interface * ************************************************************** * 3=Virtual Expanded Memory Management * * * * 4=Virtual Extended Memory Support * * ToolsAndGames * * * * * ************************************************************** * Specifies whether or not to install tools and games * * such as editors and jigsaw. * DPMI=1 * * * Valid Parms: * ************************************************************** * * * * * 0=Install none * * ExitOnError * * 1=Install all (DEFAULT) * * * * 2=Enhanced Editor * * Specifies if the install program should exit with an * * 3=Search and Scan Tool * * error code if an error occurs. This also determines * * 4=Terminal Emulator * * whether the installation process will exit with a return* * 5=Chart Maker * * code when it completes rather than the C-A-D panel. * * 6=Personal Productivity * * * * 7=Solitaire - Klondike * * Valid Parms: * * 8=Reversi * * * * 9=Scramble * * 0 = Do not exit when error occurs; display panel * * 10=Cat and Mouse * * (DEFAULT) * * 11=Pulse * * 1 = Exit quietly with a return code * * 12=Jigsaw * * * * 13=Chess * ************************************************************** * * * Example: * ExitOnError=1 * ToolsAndGames=2,8,13 * * would install the Enhanced Editor, Reversi and * ************************************************************** * Chess. * CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 83 * * * * * Fonts * ************************************************************** * * * Specifies which fonts should be installed * ToolsAndGames=1 * * * Valid Parms: * ************************************************************** * * * * * 0 = None * * ConfigSysLine * * 1 = All (DEFAULT) * * * * 2 = Courier (Bitmap) * * Specifies a text line to be appended to CONFIG.SYS. * * 3 = Helvetica (Bitmap) * * There may be multiple occurrences of this keyword. * * 4 = System Mono-spaced (Bitmap) * * No validity checking is done. * * 5 = Times Roman (Bitmap) * * * * 6 = Courier (Outline) * * Valid Parms: * * 7 = Helvetica (Outline) * * * * 8 = Times New Roman (Outline) * * KEYWORD = a valid CONFIG.SYS statement * * * * * ************************************************************** ************************************************************** Fonts=1 * ConfigSysLine=REM This is a CONFIG.SYS remark line. ************************************************************** ************************************************************** * * * * * FormatPartition * * Copy * * * * * * Specifies whether or not to format the install * * Specifies a source file and destination directory * * partition * * of a file to be copied during install. Errors are * * * * ignored, though they will be logged. Packed files * * Valid Parms: * * are acceptable since UNPACK will do the copy. * * * * There may be multiple occurrences of this keyword. * * 0=Do not format (DEFAULT) * * No validity checking is done. * * 1=Format * * * * * * Valid Parms: * ************************************************************** * * * KEYWORD= source file destination * FormatPartition=0 * * * where source file = valid filename * ************************************************************** * and destination = valid directory name * * * * * * Include * * * * * ************************************************************** * For a description of the function of this keyword, * * see IncludeAtEnd which is functionally equivalent * * Copy=vga c:&bls. /n:ini.rc * to this keyword. * * * ************************************************************** * Valid Parms: * * * * * * EarlyUserExit * * KEYWORD = valid filename * * * * * * Specifies the name of a program that Install will * ************************************************************** * DosExec after the target drive is prepared. Install * * waits for the program to return. This keyword may occur* * Include=include.rsp * more than once. Each will be executed in the order that* * they appear at the end of OS/2 Install. The only * ************************************************************** * difference between this keyword and the UserExit keyword* CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 84 * * * is that this one is executed early in the installation * * IncludeAtEnd * * process while the latter is executed at the very end. * * * * * * Specifies another response file to process along * * Valid Parms: * * with the current one. There may be multiple * * * * occurrences of this keyword. The "included" * * KEYVALUE=user exit program name (DEFAULT=none) * * response file is appended to the end of all * * * * response files that have been processed before * ************************************************************** * this one. * * * * EarlyUserExit=T c:\config.sys * eg. * * File1.RSP Processing * ************************************************************** * +------------------------+ ---------- * * * * | IncludeAtEnd=File2.RSP | Mouse=1 * * ExtendedInstall * * | IncludeAtEnd=File4.RSP | Mouse=2 * * * * | Mouse=1 | Mouse=4 * * Specifies program to be run asynchronously while SE * * +------------------------+ Mouse=3 * * Install DosExits * * File2.RSP * * * * +------------------------+ * * Valid Parms: * * | IncludeAtEnd=File3.RSP | * * * * | Mouse=2 | * * KEYVALUE=full pathname of program * * +------------------------+ * * (DEFAULT=none) * * File3.RSP * * * * +------------------------+ * ************************************************************** * | Mouse=3 | * * +------------------------+ * * ExtendedInstall=PROGRAM.EXE * File4.RSP * * +------------------------+ * ************************************************************** * | Mouse=4 | * * * * +------------------------+ * * ID * * * * * * No validity checking is done. * * Specifies some identification string which may be * * * * used by install or UserExit to identify the * * Valid Parms: * * response file(s) used for this installation * * * * * * KEYWORD = valid filename * * Valid Parms: * * * * * ************************************************************** * KEYWORD = ASCII string * * * * IncludeAtEnd=atend.rsp ************************************************************** ************************************************************** *ID=OS2SE20 Sample Response File * * * IncludeInLine * ************************************************************** * * * * * Specifies another response file to process along * * SeedConfigSysLine * * with the current one. There may be multiple * * * * occurrences of this keyword. The "included" * * Specifies a text line to be appended to the CONFIG.SYS * * response file is processed immediately when the * * written to the seed system from which PM Install boots. * * keyword is found. * * This will allow device drivers (that may be required) to* * No validity checking is done. * * become part of that seed system. * * * * There may be multiple occurrences of this keyword. * * eg. * * No validity checking is done. * * File1.RSP Processing * * * CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 85 * +-------------------------+ ---------- * * Valid Parms: * * | IncludeInLine=File2.RSP | Mouse=3 * * * * | IncludeInLine=File4.RSP | Mouse=2 * * KEYWORD = a valid CONFIG.SYS statement * * | Mouse=1 | Mouse=4 * * * * +-------------------------+ Mouse=1 * ************************************************************** * File2.RSP * * +-------------------------+ * * SeedConfigSysLine=REM This is a remark line in the seed CONFIG.SYS. * | IncludeInLine=File3.RSP | * * | Mouse=2 | * ************************************************************** * +-------------------------+ * * * * File3.RSP * * UserExit * * +-------------------------+ * * * * | Mouse=3 | * * Specifies the name of a program that Install will * * +-------------------------+ * * DosExec before exiting memory. Install waits for the * * File4.RSP * * program to return. This keyword may occur more than * * +-------------------------+ * * once. Each will be executed in the order that they * * | Mouse=4 | * * appear at the end of OS/2 Install. * * +-------------------------+ * * * * * * Valid Parms: * * Valid Parms: * * * * * * KEYVALUE=user exit program name (DEFAULT=none) * * KEYWORD = valid filename * * * * * ************************************************************** ************************************************************** * UserExit=T.EXE C:\OS2\INSTALL\INSTALL.LOG * IncludeInLine=inline.rsp ************************************************************** ************************************************************** * * * * * Version * * MigrateConfigFiles * * * * * * Specifies specific version of the operating system for * * Specifies whether or not to migrate configuration files * * which this file is intended. The file can be used for * * from a previous release of the operating system. * * future versions, though some keywords may no longer * * * * be valid. * * Valid Parms: * * * * * * Valid Parms: * * 0=Don't migrate * * * * 1=Migrate files (DEFAULT) * * KEYWORD = some version string (determined later) * * * * * ************************************************************** ************************************************************** MigrateConfigFiles=1 *Version=OS2SE211 ************************************************************** ************************************************************** * * * * * MigrateApplications * * DDInstall * * * * Use OS/2 Device Driver Installation to install external * * Specifies whether or not to migrate existing DOS, * * loadable device drivers. A Device Driver Profile ( a * * Windows** and OS/2 applications. Only those * * text file with a .DDP file name extension) must be * * applications listed in the database specified will * * provided by the device driver author to control the * * be migrated. * * installation of the device driver. * * * * * * Valid Parms: * * Valid Parms: * CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 86 * * * DDISrc = Directory where the .DDP files are. * * Drives to search, database to use for search * * DDIDest = Directory where to copy the device driver * * * * files. * ************************************************************** * DDIDDP = List of .DDP files to install. * * (example: file1.DDP,file2.DDP) * *MigrateApplications= * * * * ************************************************************** ************************************************************** * * * MoreBitmaps * *DDISrc = Z:\DDP * * *DDIDest = C:\ * Specifies whether or not to install more bitmaps. * *DDIDDP = *.DDP * * * Valid Parms: * * * * 0=Don't install More Bitmaps * * 1=Install More Bitmaps (DEFAULT) * * * ************************************************************** ------------------------------------------------------------------------------------------------------------------------------- Step 3. PREPARING THE CHANGE FILE PROFILES A change file profile must be prepared for each product and built into a change file on the CC server. Following are the change file profiles used to set up the maintenance environment and, later, to migrate the operating system: C:\SHARE_A\PRF\OS2V211\OS211MNT.PRF ------------------------------------------------------------------------------- TargetDir = C:\SERVICE Section Catalog Begin ObjectType = SOFTWARE GlobalName = IBM.OS2V211.MAINT.REF.2.1 Description = "Install Procedure for OS/2 V2.11 Seed System" End Section Install Begin Program = SA:\IMG\OS2V211\SEMAINT.EXE Parms = /S:$(SourceDir) /B:C: /L1:$(LogFile1) /T:$(TargetDir) SourceDir = SA:\IMG\OS2V211 LogFile1 = SB:\LOG\OS2V211\MAINT\$(WorkStatName).M11 End ------------------------------------------------------------------------------- CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 87 C:\SHARE_A\PRF\LAPS7045\TLAPSMNT.PRF ------------------------------------------------------------------------------- TargetDir = C:\SERVICE Section Catalog Begin ObjectType = SOFTWARE GlobalName = IBM.LAPS7045.TCPMNT.REF.2.0 Description = "Maintenance System Install Procedure for LAPS 2.20" End Section Install Begin Program = SA:\IMG\LAPS7045\LAPS.EXE Parms = /S:$(SourceDir) /T:$(TargetDir) /R:$(ResponseFile) > /L1:$(LogFile1) /TU:C:\ /E:PREP SourceDir = SA:\IMG\LAPS7045 ResponseFile = SA:\RSP\LAPS7045\$(WorkStatName).RSP LogFile1 = SB:\LOG\LAPS7045\MAINT\$(WorkStatName).LOG End ------------------------------------------------------------------------------- C:\SHARE_A\PRF\TCPIPV20\TCPNBUPD.PRF ------------------------------------------------------------------------------- TargetDir = C:\SERVICE Section Catalog Begin ObjectType = SOFTWARE GlobalName = IBM.TCPIPV20.TCPNBUPD.REF.2.0 Description = "REXX Procedure for XCOPY TCP/IP V2.0 and NetBIOS/TCP files" End Section Install Begin Program = SA:\IMG\TCPIPV20\TCPNBUPD.CMD Parms = $(SA)\RSP\TCPIPV20\$(WorkStatName).RSP C:\TCPIP C:\NETBIOS2 End ------------------------------------------------------------------------------- CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 88 C:\SHARE_A\PRF\NVDM2V21\TCC21MNT.PRF ------------------------------------------------------------------------------- TargetDir = C:\IBMNVDM2 Section Catalog Begin ObjectType = SOFTWARE GlobalName = IBM.NVDM2V21.CLTMNT.REF.2.1 Description = "MAINT SYSTEM Install Procedure for the CC Client Feature > of NetView DM/2 Version 2.1" End Section Install Begin Program = SA:\IMG\NVDM2V21\NVDMCLT.EXE Parms = /M /CO /S:$(SourceDir) /T:$(TargetDir) /R:$(ResponseFile) /L:$(LogFile1) SourceDir = SA:\IMG\NVDM2V21 ResponseFile = SA:\RSP\NVDM2V21\$(WorkStatName).RSP LogFile1 = SB:\LOG\NVDM2V21\MAINT\$(WorkStatName).T1 End ------------------------------------------------------------------------------- C:\SHARE_A\PRF\TCPIPV20\STARTUPD.PRF ------------------------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType = SOFTWARE GlobalName = IBM.TCPIPV20.STARTUPD.REF.2.0 Description = "REXX Procedure for modifying startup for TCP/IP V2.0 > and NetBIOS 2.08 " End Section Install Begin Program = SA:\IMG\TCPIPV20\STARTUPD.CMD Parms = C C:\SERVICE PhaseEnd = Yes End ------------------------------------------------------------------------------- CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 89 C:\SHARE_A\PRF\OS2V211\OS211UPG.PRF ------------------------------------------------------------------------------- TargetDir = C:\OS2 Section Catalog Begin ObjectType = SOFTWARE GlobalName = IBM.OS2V211.UPG.REF.2.1 Description = "Upgrade Install Procedure from OS/2 V2.10 to OS/2 V2.11" End Section Install Begin Program = SA:\IMG\OS2V211\SEINST.EXE Parms = /S:$(SourceDir) /B:C: /R:$(ResponseFile) /L1:$(LogFile1) /T:C:\SERVICE SourceDir = SA:\IMG\OS2V211 ResponseFile = SA:\RSP\OS2V211\OS211UPG.RSP LogFile1 = SB:\LOG\OS2V211\PROD\$(WorkStatName).L11 ------------------------------------------------------------------------------- TCPNBUPD.PRF runs the TCPNBUPD.CMD sample REXX procedure, which you can customize. TCPNBUPD.CMD has the following structure: TCPNBUPD <rspfile> <tcpdir> <nbdir> <tcpdir> and <nbdir> are respectively the directories where TCP/IP V2.0 and NetBIOS/TCP 2.0.8 are installed on the CC client; <rspfile> is a file containing the following parameters that you can customize: o TARGETDIR (mandatory, no default) = maintenance environment directory target o HOST_NAME (mandatory, no default) = host name of the CC client o IP_ADDRESS (mandatory, no default) = ip address of the CC client o BR_ADDRESS (mandatory, no default) = broadcast address of the CC client The procedure checks the response file, executes a XCOPY command from the source directory in the target directory specified in the PARMS section of the change file profile, updates the LIBPATH, PATH and DPATH statements, and adds the TCP/IP + NetBIOS/TCP device drivers to the CONFIG.SYS built after SEMAINT and LAPS have run. Finally, it updates the CONFIG.SYS and STARTUP.CMD system files after saving them in CONFIG.NB and STARTUP.NB. Following is the source code of TCPNBUPD.CMD: CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 90 ------------------------------------------------------------------------------- /******************************************************************************/ /* TCPNBUPD.CMD */ /*----------------------------------------------------------------------------*/ /* REXX procedure to create a Maintenance System in a TCP/IP environment */ /* on a NetView DM/2 CC Client Workstation. */ /*----------------------------------------------------------------------------*/ /* */ /*----------------------------------------------------------------------------*/ /* */ /* Description: */ /* ----------- */ /* This procedure addresses the scenario of the installation of a */ /* Maintenance System on a CC Client running TCP/IP V2.0 for OS/2 + */ /* NetBIOS/TCP 2.0.8. */ /* */ /* */ /* What This Procedure Performs: */ /* ---------------------------- */ /* Basically the procedure TCPNBUPD.CMD is called after SEMAINT.EXE */ /* and LAPS.EXE (invoked with /E:PREP) to do the following activities : */ /* */ /* */ /* 1) CONFIG.SYS changes */ /* _____________________ */ /* */ /* a) XCOPY TCP/IP and NetBIOS modules to C:\SERVICE (instead of C:\ */ /* as for Production System). */ /* */ /* b) Updates the LIBPATH statement of the CONFIG.SYS built by LAPS.EXE */ /* adding <nbtdir> and <tcptdir>\DLL ( note: put <nbtdir> before */ /* \IBMCOM\DLL to avoid a next step to rename ACSNETB.DLL under */ /* \IBMCOM\DLL. */ /* */ /* c) Updates the PATH statement of the CONFIG.SYS built by LAPS.EXE */ /* adding <tcptdir>\BIN. */ /* */ /* d) Updates the DPATH statement of the CONFIG.SYS built by LAPS.EXE */ /* adding <tcptdir> */ /* */ /* e) Adds the following NetBIOS/TCP and TCP/IP statements : */ /* */ /* ------------------------------------------------------------------------ */ /* | DEVICE=<nbtdir>\NBDRIVER.SYS -s* 100 -c 100 -n 100 | */ /* | DEVICE=<tcptdir>\BIN\INET.SYS | */ /* | DEVICE=<tcptdir>\BIN\IFNDIS.SYS | */ /* | SET ETC=<tcptdir>\ETC | */ /* | SET TMP=<tcptdir>\TMP | */ /* | RUN=<tcptdir>\BIN\CNTRL.EXE | */ /* | SET DISPLAY=<ipa>:0 | */ /* | SET TZ=GMT0 | */ /* | SET HOSTNAME=<hname> | */ CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 91 /* | SET READIBM=<tcpdir>\DOC | */ /* ------------------------------------------------------------------------ */ /* */ /* */ /* 2) STARTUP.CMD changes */ /* ______________________ */ /* */ /* a) Removes NetBIOS/TCP start line and adds run detach command to */ /* start NBTCP.EXE as follows: */ /* */ /* ------------------------------------------------------------------------ */ /* DETACH <nbtdir>\NBTCP -b <nbtdir>\<bname> -n <nbtdir>\<nname> <ipa> <bra> */ /* ------------------------------------------------------------------------ */ /* */ /* */ /* NetView DM/2 Change File Profile sample: */ /* ---------------------------------------- */ /* */ /* TCPNBUPD.PRF */ /* ========================================================================== */ /* */ /* TargetDir = C:\SERVICE */ /* */ /* Section Catalog */ /* Begin */ /* ObjectType = SOFTWARE */ /* GlobalName = IBM.TCPIPV20.TCPNBUPD.REF.2.0 */ /* Description = "REXX Proc. for XCOPY TCP/IP V2.0 & NetBIOS/TCP files" */ /* End */ /* */ /* Section Install */ /* Begin */ /* Program = SA:\IMG\TCPIPV20\TCPNBUPD.CMD */ /* Parms = $(SA)\RSP\TCPIPV20\$(WorkStatName).RSP C:\TCPIP C:\NETBIOS2 */ /* End */ /* */ /* ========================================================================== */ /* */ /* Response File sample: */ /* -------------------- */ /* */ /* $(WorkStatName).RSP */ /* ========================================================================== */ /* */ /* TARGETDIR=C:\SERVICE */ /* HOST_NAME=LT0054A0 */ /* IP_ADDRESS=150.5.100.54 */ /* BR_ADDRESS=150.255.255.255 */ /* */ /* ========================================================================== */ /* */ /******************************************************************************/ /* */ /* CCC OOO DDDD EEEEEE */ CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 92 /* C C O O D D E */ /* C O O D D E */ /* C O O D D EEE */ /* C O O D D E */ /* C C O O D D E */ /* CCC OOO DDDD EEEEEE */ /* */ /******************************************************************************/ /*NBTCP Installation */ PARSE ARG rspfile tcpsdir nbsdir if rspfile='' then do say 'no response file' exit 1 end if tcpsdir='' then do say 'no source dir' exit 1 end if nbsdir='' then do say 'no source dir' exit 1 end ipa='' bra='' hname='' tdir='C:\SERVICE' bdrive='C' nname='NETNAME' bname='NETBROAD' ss='100' cc='100' nn='100' /******************************************************************/ /* load on memory of response file */ /******************************************************************/ rc=stream(rspfile,'c','close') size=stream(rspfile,'c','query size') list=charin(rspfile,1,size) rc=stream(rspfile,'c','close') flag='1' do while list><'' parse var list line.flag '0D0A'X list flag=flag+1 CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 93 if C2X(list)='1A' then leave end line.0=flag-1 /********************************************************************* * process to check parameters * *********************************************************************/ do i='1' to line.0 PARSE UPPER VALUE LINE.i WITH keyword '=' keyvalue SELECT WHEN keyword = 'IP_ADDRESS' then ipa=keyvalue WHEN keyword = 'HOST_NAME' then hname=keyvalue WHEN keyword = 'BR_ADDRESS' then bra=keyvalue WHEN keyword = 'TARGETDIR' then tdir=keyvalue WHEN keyword = 'BOOTDRIVE' then bdrive=keyvalue WHEN keyword = 'NETFILE' then nname=keyvalue WHEN keyword = 'BROADFILE' then bname=keyvalue OTHERWISE do msgline=line.i 'is a wrong rsp line' say msgline end END end /******************************************************/ /* preparation of file strings */ /******************************************************/ nbtdir=tdir'\NETBIOS2' tcptdir=tdir'\TCPIP' cfgfile=bdrive':\CONFIG.SYS' cfgtmp=bdrive':\CONFIG.TMP' srtfile=bdrive':\STARTUP.CMD' tcpxcpyline='xcopy /s 'tcpsdir tcptdir'\' nbxcpyline='xcopy /s 'nbsdir nbtdir'\' cfgline='DEVICE='nbtdir'\NBDRIVER.SYS -s' ss' -c' cc' -n' nn srtline='DETACH 'nbtdir'\NBTCP -b 'nbtdir'\'bname' -n' nbtdir'\'nname ipa bra cpyline='copy' cfgfile bdrive':\CONFIG.NB' tcpline.1='DEVICE='tcptdir'\BIN\INET.SYS' tcpline.2='DEVICE='tcptdir'\BIN\IFNDIS.SYS' addline.1='SET ETC='tcptdir'\ETC' addline.2='SET TMP='tcptdir'\TMP' addline.3='RUN='tcptdir'\BIN\CNTRL.EXE' addline.4='SET DISPLAY='ipa':0' addline.5='SET TZ=GMT0' CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 94 addline.6='SET HOSTNAME='hname addline.7='SET READIBM='tcptdir'\DOC' /* XCOPY */ tcpxcpyline nbxcpyline cpyline rc=stream(cfgfile,'c','close') size=stream(cfgfile,'c','query size') list=charin(cfgfile,1,size) rc=stream(cfgfile,'c','close') flag='1' do while list><'' parse var list line.flag '0D0A'X list flag=flag+1 if C2X(list)='1A' then leave end line.0=flag-1 lpos=0 /* CONFIG.SYS changes */ do i='1' to line.0 PARSE UPPER VALUE LINE.i WITH keyword '=' keyvalue SELECT WHEN keyword = 'LIBPATH' then line.i=keyword'='nbtdir';'tcptdir'\DLL;'keyvalue WHEN keyword = 'SET PATH' then line.i=keyword'='keyvalue';'tcptdir'\BIN;' WHEN keyword = 'SET DPATH' then line.i=keyword'='keyvalue';'tcptdir';' WHEN keyword = 'DEVICE' then do parse var keyvalue filespc rest filename=filespec("name",filespc) if filename = 'INET.SYS' then lpos=i end OTHERWISE do end END end if lpos = 0 then do do i='1' to line.0 rc=lineout(cfgtmp,line.i) end rc=lineout(cfgtmp,cfgline) rc=lineout(cfgtmp,tcpline.1) rc=lineout(cfgtmp,tcpline.2) do i='1' to '7' CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 95 rc=lineout(cfgtmp,addline.i) end end else do do i='1' to lpos-1 rc=lineout(cfgtmp,line.i) end rc=lineout(cfgtmp,cfgline) rc=lineout(cfgtmp,line.lpos) lpos=lpos+1 rc=lineout(cfgtmp,line.lpos) do i='1' to '7' rc=lineout(cfgtmp,addline.i) end do i=lpos+2 to line.0 rc=lineout(cfgtmp,line.i) end end rc=lineout(cfgtmp) 'copy 'cfgtmp cfgfile 'del 'cfgtmp /* STARTUP.CMD changes */ 'COPY 'srtfile bdrive':\STARTUP.NB' 'del 'srtfile rc=lineout(srtfile,'') rc=lineout(srtfile,'CALL TCPSTART.CMD') rc=lineout(srtfile,srtline) rc=lineout(srtfile) ------------------------------------------------------------------------------- STARTUPD.PRF runs the STARTUPD.CMD REXX procedure that modifies the SET OS2_SHELL statement (which was altered by NVDMCLT to invoke the maintenance client agent) in the CONFIG.SYS to call the STARTUP.CMD. It comments out the CDM START in the STARTUP.CMD file in order to invoke the maintenance client agent (ANXCMCLC.EXE), adding a line on the bottom of the STARTUP.CMD. Following is the source code of STARTUPD.CMD: ------------------------------------------------------------------------------- /******************************************************************************/ /* STARTUPD.CMD */ /*----------------------------------------------------------------------------*/ /* REXX procedure to create a Maintenance System in a TCP/IP environment */ /* on a NetView DM/2 CC Client Workstation. */ /*----------------------------------------------------------------------------*/ /* */ /*----------------------------------------------------------------------------*/ CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 96 /* */ /* Description: */ /* ----------- */ /* This procedure addresses the scenario of the installation of a */ /* Maintenance System on a CC Client running TCP/IP V2.0 for OS/2 + */ /* NetBIOS/TCP 2.0.8. */ /* */ /* */ /* What This Procedure Performs: */ /* ---------------------------- */ /* Basically the procedure STARTUPD.CMD is called after NVDMCLT.EXE */ /* (invoked with /M /CO) to do the following activities : */ /* */ /* */ /* 1) CONFIG.SYS changes */ /* _____________________ */ /* */ /* a) Changes SET OS2_SHELL statement invoking STARTUP.CMD instead of */ /* ANXCMCLC.EXE as follows : */ /* */ /* ------------------------------------------------------------------------ */ /* | SET OS2_SHELL=<os2path>CMD.EXE /K STARTUP.CMD | */ /* ------------------------------------------------------------------------ */ /* */ /* */ /* 2) STARTUP.CMD changes */ /* ______________________ */ /* */ /* a) Invokes ANXCMCLC.EXE adding a line on the bottom and remarking */ /* out CDM START on the top. */ /* */ /* */ /* NetView DM/2 Change File Profile sample: */ /* ---------------------------------------- */ /* */ /* STARTUPD.PRF */ /* ========================================================================== */ /* */ /* TargetDir = C:\ */ /* */ /* Section Catalog */ /* Begin */ /* ObjectType = SOFTWARE */ /* GlobalName = IBM.TCPIPV20.STARTUPD.REF.2.0 */ /* Description = "REXX Proc. to modify TCP/IP V2.0 + NetBIOS/TCP Startup" */ /* End */ /* */ /* Section Install */ /* Begin */ /* Program = SA:\IMG\TCPIPV20\STARTUPD.CMD */ /* Parms = C C:\SERVICE */ /* PhaseEnd = Yes */ /* End */ /* */ CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 97 /* ========================================================================== */ /* */ /******************************************************************************/ /* */ /* CCC OOO DDDD EEEEEE */ /* C C O O D D E */ /* C O O D D E */ /* C O O D D EEE */ /* C O O D D E */ /* C C O O D D E */ /* CCC OOO DDDD EEEEEE */ /* */ /******************************************************************************/ /* STARTUP.CMD changes */ PARSE ARG drive os2path '@ECHO OFF' if drive='' then do say 'nodrive' exit 1 end if os2path='' then do say 'no service directory' exit 1 end srtfile=drive':\STARTUP.CMD' tmpfile=drive':\STARTUP.TMP' cfgfile=drive':\CONFIG.SYS' cfgtmp=drive':\CONFIG.TMP' rc=stream(srtfile,'c','close') size=stream(srtfile,'c','query size') list=charin(srtfile,1,size) rc=stream(srtfile,'c','close') flag='1' do while list><'' parse var list line.flag '0D0A'X list flag=flag+1 if C2X(list)='1A' then leave end line.0=flag-1 do i='1' to line.0 PARSE UPPER VAR line.i tmp SELECT WHEN tmp='CDM START' then line.i='REM CDM START' WHEN tmp='EXIT' then line.i='REM EXIT' OTHERWISE do CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 98 end END end do i='1' to line.0 rc=lineout(tmpfile,line.i) end rc=lineout(tmpfile,ANXCMCLC.EXE) rc=lineout(tmpfile) 'copy 'tmpfile srtfile 'del 'tmpfile rc=stream(cfgfile,'c','close') size=stream(cfgfile,'c','query size') list=charin(cfgfile,1,size) rc=stream(cfgfile,'c','close') flag='1' do while list><'' parse var list line.flag '0D0A'X list flag=flag+1 if C2X(list)='1A' then leave end line.0=flag-1 /* CONFIG.SYS changes */ do i='1' to line.0 PARSE UPPER VAR line.i key '=' keyvalue other SELECT WHEN key='SET OS2_SHELL' then line.i=key'='os2path'\CMD.EXE /K STARTUP.CMD' OTHERWISE do end END end do i='1' to line.0 rc=lineout(cfgtmp,line.i) end rc=lineout(cfgtmp) 'copy 'cfgtmp cfgfile 'del 'cfgtmp ------------------------------------------------------------------------------- Step 4. BUILDING THE CHANGE FILES FOR THE MAINTENANCE ENVIRONMENT To build the change files using the change file profiles to set up the maintenance environment, enter the following commands: CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 99 CDM BUILD C:\SHARE_A\PRF\OS2V221\OS211MNT.PRF FS:OS211MNT.PKG CDM BUILD C:\SHARE_A\PRF\LAPS7045\TLAPSMNT.PRF FS:TLAPSMNT.PKG CDM BUILD C:\SHARE_A\PRF\TCPIPV20\TCPNBUPD.PRF FS:TCPNBUPD.PKG CDM BUILD C:\SHARE_A\PRF\NVDM2V21\TCC21MNT.PRF FS:TCC21MNT.PKG CDM BUILD C:\SHARE_A\PRF\TCPIPV20\STARTUPD.PRF FS:STARTUPD.PKG After the commands are run, the change files are built and cataloged with the global name specified in the respective change file profiles. Step 5. SUBMITTING THE INSTALLATION REQUEST FOR THE MAINTENANCE ENVIRONMENT Submit an installation request for the workstation LT0054A0 with the command: CDM INSTALL IBM.OS2V211.MAINT.REF.2.1 + IBM.LAPS7045.TCPMNT.REF.2.0 > + IBM.TCPIPV20.TCPNBUPD.REF.2.0 + IBM.NVDM2V21.CLTMNT.REF.2.1 > + IBM.TCPIPV20.STARTUPD.REF.2.0 /WS:LT0054A0 Step 6. CHECKING THE RESULTS OF THE INSTALLATION REQUEST After the restart, at the CC client workstation LT0054A0, the maintenance environment should be correctly installed and the client should be in active status. To verify this status, perform the following activities: o At the CC server issue the following command: CDM LISTWS The output should look like this: ------------------------------------------------------------------------------- Destination id : LT0054A0 Server name : LT0064A0 Workstation type : Client Operating system : OS/2 Status : Active ------------------------------------------------------------------------------- o At the CC server check the log file under C:\IBMNVDM2\CMREQ\LT0054A0\LOG. The MESSAGE.DAT file under this directory should look like this: ------------------------------------------------------------------------------- ** NetView DM/2 logged at 17:26:05 27/07/1994 ** ANX1315: (I) Invoking External Program: 'X:\IMG\OS2V211\SEMAINT.EXE' With Parms: '/S:X:-IMG\OS2V211 /B:C: /L1:W:\LOG\OS2V211\MAINT\LT0054A0.M11 /T:C:\SERVICE' ------------------------------------------------------------------------------- ** NetView DM/2 logged at 17:28:58 27/07/1994 ** CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 100 ANX1315: (I) Invoking External Program: 'X:\IMG\LAPS7045\LAPS.EXE' With Parms: '/S:X:\IMG\LAPS7045 /T:C:\SERVICE /R:X:\RSP\LAPS7045\LT0054A0.RSP /L1:W:\LOG\LAPS7045\MAINT\LT0054A0.LOG /TU:C:\ /E:PREP' ------------------------------------------------------------------------------- ** NetView DM/2 logged at 17:30:31 27/07/1994 ** ANX1315: (I) Invoking External Program: 'X:\IMG\TCPIPV20\TCPNBUPD.CMD' With Parms: 'X:\RSP\TCPIPV20\LT0054A0.RSP C:\TCPIP C:\NETBIOS2' ------------------------------------------------------------------------------- ** NetView DM/2 logged at 17:32:04 27/07/1994 ** ANX1315: (I) Invoking External Program: 'X:\IMG\NVDM2V21\NVDMCLT.EXE' With Parms: '/M /CO /S:X:\IMG\NVDM2V21 /T:C:\IBMNVDM2 /R:X:\RSP\NVDM2V21\LT0054A0.RSP /L:W:\LOG\NVDM2V21\MAINT\LT0054A0.T1' ------------------------------------------------------------------------------- ** NetView DM/2 logged at 17:33:37 27/07/1994 ** ANX1315: (I) Invoking External Program: 'X:\IMG\TCPIPV20\STARTUPD.CMD' With Parms: 'C' ------------------------------------------------------------------------------- ** NetView DM/2 logged at 17:35:52 27/07/1994 ** ANX1398: (I) CM Activity started. ------------------------------------------------------------------------------- ** NetView DM/2 logged at 17:36:18 27/07/1994 ** ANX0221: (I) The processing of the INSTALL request on workstation for an object with Global Name 'IBM.OS2V211.MAINT.REF.2.1' was successfully executed by the CDM Agent. ------------------------------------------------------------------------------- ** NetView DM/2 logged at 17:36:20 27/07/1994 ** ANX1399: (I) CM Activity ended. ------------------------------------------------------------------------------- o At the CC server verify that the following objects: - IBM.OS2V211.MAINT.REF.2.1 - IBM.LAPS7045.TCPMNT.REF.2.0 - IBM.TCPIPV20.TCPNBUPD.REF.2.0 - IBM.NVDM2V21.CLTMNT.REF.2.1 - IBM.TCPIPV20.STARTUPD.REF.2.0 have the INRU (installed non-removably in use) status, issuing the following command: CDM LIST /LT0054A0 The output should look like this: ------------------------------------------------------------------------------- Object Type : SOFTWARE Global Name : IBM.LAPS7045.TCPMNT.REF.2.0 Local Name : C:\IBMNVDM2\FSDATA\TLAPSMNT.CHG FS date and time : 27/07/94 17:25 Description : Maintenance System Install Procedure for LAPS 2.20 CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 101 WS_id Date Time Status LT0054A0 27/07/94 17:36 INRU Object Type : SOFTWARE Global Name : IBM.NVDM2V21.CLTMNT.REF.2.1 Local Name : C:\IBMNVDM2\FSDATA\TCC21MNT.CHG FS date and time : 27/07/94 17:25 Description : MAINT SYSTEM Install Procedure for the CC Client > Feature of NetView DM/2 Version 2.1 WS_id Date Time Status LT0054A0 27/07/94 17:36 INRU Object Type : SOFTWARE Global Name : IBM.OS2V211.MAINT.REF.2.1 Local Name : C:\IBMNVDM2\FSDATA\OS211MNT.CHG FS date and time : 27/07/94 17:24 Description : Install Procedure for OS/2 V2.11 Seed System WS_id Date Time Status LT0054A0 27/07/94 17:36 INRU Object Type : SOFTWARE Global Name : IBM.OS2V211.UPG.REF.2.1 Local Name : C:\IBMNVDM2\FSDATA\OS211UPG.CHG FS date and time : 27/07/94 17:46 Description : Upgrade Install Procedure from OS/2 V2.10 to OS/2 V2.11 WS_id Date Time Status LT0054A0 27/07/94 18:36 INRU Object Type : SOFTWARE Global Name : IBM.TCPIPV20.STARTUPD.REF.2.0 Local Name : C:\IBMNVDM2\FSDATA\STARTUPD.CHG FS date and time : 27/07/94 17:25 Description : REXX Procedure for modifying startup for TCP/IP V2.0 > and NetBIOS 2.08 WS_id Date Time Status LT0054A0 27/07/94 17:36 INRU Object Type : SOFTWARE Global Name : IBM.TCPIPV20.TCPNBUPD.REF.2.0 Local Name : C:\IBMNVDM2\FSDATA\TCPNBUPD.CHG FS date and time : 27/07/94 17:25 Description : REXX Procedure for XCOPY TCP/IP V2.0 & NetBIOS/TCP files WS_id Date Time Status LT0054A0 27/07/94 17:36 INRU ------------------------------------------------------------------------------- Step 7. BUILDING THE CHANGE FILES FOR THE PRODUCTION ENVIRONMENT CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 102 To build the change files using the change file profiles to install OS/2 V2.11 in the production environment, enter the following command: CDM BUILD C:\SHARE_a\PRF\OS2V221\OS211UPG.PRF FS:OS211UPG.PKG After the command is run, the change file is built and cataloged with the global name specified in its change file profile. Step 8. SUBMITTING THE INSTALLATION REQUEST FOR THE PRODUCTION ENVIRONMENT Submit an installation request for the workstation LT0054A0 with the command: CDM INSTALL IBM.OS2V211.UPG.REF.2.1 /WS:LT0054A0 Step 9. CHECKING THE RESULTS OF THE INSTALLATION REQUEST After the restart, at the CC client workstation LT0054A0, OS/2 Version 2.11, TCP/IP Version 2.0 base kit, LAPS and NetBIOS for TCP/IP, and CDM agent should be correctly installed and running. Verify that the CC client status is ACTIVE and that the objects status is INRU. Also check the log file under C:\IBMNVDM2\CMREQ\LT0054A0\LOG. The changes inside the MESSAGE.DAT file under this directory should look like this: ------------------------------------------------------------------------------- ** NetView DM/2 logged at 17:46:59 27/07/1994 ** ANX1398: (I) CM Activity started. ------------------------------------------------------------------------------- ** NetView DM/2 logged at 17:47:05 27/07/1994 ** ANX1315: (I) Invoking External Program: 'X:\IMG\OS2V211\SEINST.EXE' With Parms: '/S:X:\IMG\OS2V211 /B:C: /R:X:\RSP\OS2V211\OS211UPG.RSP /L1:W:\LOG\OS2V211\PROD\LT0054A0.L11 /T:C:\SERVICE' ------------------------------------------------------------------------------- ** NetView DM/2 logged at 18:34:36 27/07/1994 ** ANX1398: (I) CM Activity started. ------------------------------------------------------------------------------- ** NetView DM/2 logged at 18:34:51 27/07/1994 ** ANX1315: (I) Invoking External Program: 'X:\IMG\OS2V211\SEINST.EXE' With Parms: '/S:X:\IMG\OS2V211 /B:C: /R:X:\RSP\OS2V211\OS211UPG.RSP /L1:W:\LOG\OS2V211\PROD\LT0054A0.L11 /T:C:\SERVICE' ------------------------------------------------------------------------------- ** NetView DM/2 logged at 18:36:21 27/07/1994 ** ANX0221: (I) The processing of the INSTALL request on workstation for an object with Global Name 'IBM.OS2V211.UPG.REF.2.1' was successfully executed by the CDM Agent. ------------------------------------------------------------------------------- ** NetView DM/2 logged at 18:36:27 27/07/1994 ** ANX1399: (I) CM Activity ended. ------------------------------------------------------------------------------- CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 103 APPENDIX o MAINTENANCE ENVIRONMENT CONFIG.SYS ------------------------------------------------------------------------------- BUFFERS=32 IOPL=YES MEMMAN=SWAP,PROTECT SWAPPATH=C:\SERVICE 1024 1024 PROTSHELL="C:\SERVICE"\SYSINST1.EXE SET OS2_SHELL=C:\SERVICE\CMD.EXE /K STARTUP.CMD DISKCACHE=64,LW PROTECTONLY=YES LIBPATH=C:\SERVICE\NETBIOS2;C:\SERVICE\TCPIP\DLL;C:\SERVICE\IBMCOM\DLL;> "C:\SERVICE";.;\;C:\IBMNVDM2\DLL; IFS="C:\SERVICE"\HPFS.IFS /C:64 /AUTOCHECK:C PAUSEONERROR=NO CODEPAGE=850 COUNTRY=039,"C:\SERVICE"\COUNTRY.SYS DEVINFO=KBD,US,"C:\SERVICE"\KEYBOARD.DCP DEVINFO=SCR,EGA,"C:\SERVICE"\VTBL850.DCP DEVICE=C:\SERVICE\IBMCOM\PROTOCOL\LANPDD.OS2 DEVICE=C:\SERVICE\IBMCOM\PROTOCOL\LANVDD.OS2 DEVICE=C:\SERVICE\IBMCOM\LANMSGDD.OS2 /I:C:\SERVICE\IBMCOM DEVICE=C:\SERVICE\IBMCOM\PROTMAN.OS2 /I:C:\SERVICE\IBMCOM DEVICE="C:\SERVICE"\DOS.SYS DEVICE="C:\SERVICE"\MOUSE.SYS SET PATH="C:\SERVICE";.;\;C:\SERVICE\TCPIP\BIN;C:\IBMNVDM2\BIN; SET DPATH=C:\SERVICE\IBMCOM;"C:\SERVICE";.;\;C:\SERVICE\TCPIP;C:\IBMNVDM2; SET KEYS=ON BASEDEV=PRINT01.SYS BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD BASEDEV=IBM2FLPY.ADD BASEDEV=IBM2ADSK.ADD BASEDEV=IBM2M57.ADD BASEDEV=IBM2SCSI.ADD BASEDEV=IBMINT13.I13 BASEDEV=OS2DASD.DMD DEVICE="C:\SERVICE"\TESTCFG.SYS DEVICE="C:\SERVICE"\REFPART.SYS RUN=C:\SERVICE\IBMCOM\PROTOCOL\NETBIND.EXE RUN=C:\SERVICE\IBMCOM\LANMSGEX.EXE DEVICE=C:\SERVICE\IBMCOM\PROTOCOL\LANDD.OS2 DEVICE=C:\SERVICE\IBMCOM\PROTOCOL\LANDLLDD.OS2 DEVICE=C:\SERVICE\IBMCOM\MACS\IBMTOK.OS2 RUN=C:\SERVICE\IBMCOM\PROTOCOL\LANDLL.EXE DEVICE=C:\SERVICE\NETBIOS2\NBDRIVER.SYS -s 100 -c 100 -n 100 DEVICE=C:\SERVICE\TCPIP\BIN\INET.SYS CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 104 DEVICE=C:\SERVICE\TCPIP\BIN\IFNDIS.SYS SET ETC=C:\SERVICE\TCPIP\ETC SET TMP=C:\SERVICE\TCPIP\TMP RUN=C:\SERVICE\TCPIP\BIN\CNTRL.EXE SET DISPLAY=150.5.100.54:0 SET TZ=GMT0 SET HOSTNAME=LT0054A0 SET READIBM=C:\SERVICE\TCPIP\DOC DEVICE=C:\IBMNVDM2\BIN\anxifpid.sys DEVICE=C:\IBMNVDM2\BIN\anxifcom.sys IFS=C:\IBMNVDM2\BIN\anxifcom.ifs DEVICE=C:\IBMNVDM2\BIN\ANXACAIP.SYS ------------------------------------------------------------------------------- o MAINTENANCE ENVIRONMENT STARTUP.CMD ------------------------------------------------------------------------------- CALL TCPSTART.CMD DETACH C:\SERVICE\NETBIOS2\NBTCP -b C:\SERVICE\NETBIOS2\NETBROAD > -n C:\SERVICE\NETBIOS2\NETNAME 150.5.100.54 150.255.255.255 ANXCMCLC.EXE ------------------------------------------------------------------------------- NOTE: The scenario has been split in two phases (maintenance and production) in order to underline which profiles, response files, and REXX procedures are strictly needed to set up a maintenance environment, which could be used to install any other CID application that requires a seed system before being installed. In the specific case of the migration from OS/2 V2.1 to OS/2 V2.11, which is attempted in this scenario, you could invoke a single install cycle, installing the OS/2 V2.11 in production as a corequisite of the OS/2 V2.11 in maintenance, by issuing the following command: CDM INSTALL IBM.OS2V211.MAINT.REF.2.1 + IBM.LAPS7045.TCPMNT.REF.2.0 > + IBM.TCPIPV20.TCPNBUPD.REF.2.0 + IBM.NVDM2V21.CLTMNT.REF.2.1 > + IBM.TCPIPV20.STARTUPD.REF.2.0 + IBM.OS2V211.UPG.REF.2.1 > /WS:LT0054A0 Page 327 - Chapter 9 - CDM Utilities The "Receive Timeout" parameter of the NVDMBDSK could be specified from a range of -1 to 2000000000. The value -1 means infinite waiting. CHAPTER 5. CORRECTIONS TO THE CDM USER'S GUIDE 105 LDU USER'S GUIDE PART 4. LDU USER'S GUIDE This part describes changes to make to the LDU User's Guide to reflect changes and corrections made after the documentation for NetView DM/2 Version 2.1 was sent for publication. (C) Copyright IBM Corp. 1991, 1995 106 LDU USER'S GUIDE CHAPTER 6. LDU USER'S GUIDE ENHANCEMENTS ANXADM: A New Tool to Prepare LDU Packages More Easily ANXADM is a utility that makes it easy for you to prepare LDU packages, creating a set of instructions in a file called a profile. This profile can _______ have the following sections: [DEFINE] A collection of definitions of the form: Var=Value|<Var> Whenever "Var" is specified in other sections of the profile, it is substituted with the Value or <Var> specified here. [HERE] A collection of commands to be executed on the server workstation before creating packages. These commands may be used to create, install, or copy files that will be distributed. [TRANSFER] A collection of instructions to transfer files from the server to clients. The syntax of these instructions is as follows: Prefix Locdir TO Clientdir where: "Locdir" is the directory where files are stored on the server. "Clientdir" is the directory where files are stored on clients when the distribution ends. The "Prefix" can be specified in one of the following ways: o TREE, if you want to transfer all the subdirectories also. o DIR, if you want to transfer only this directory. o FILE, if you want to transfer only the specified file. [REMOTE] A collection of commands that are to be executed on clients. [CUSTOM] A collection of statements used to customize certain files according to client name. The syntax is: Filename : Field = Value or (C) Copyright IBM Corp. 1991, 1995 107 LDU USER'S GUIDE Filename : = ModelFile where o "Filename" is only a file name without a path specified. This file name must be specified in the [TRANSFER] section in its fully-qualified form. o "ModelFile" is a fully-qualified file name used as a model. ANXADM creates a customized file following these rules: - If a file with the same name ("Filename") exists, it is used as the model file, even if a different "ModelFile" is specified in a statement. - If no such file exists, a check for a "ModelFile" statement is performed and that file is used as the model file. - If no model file has been identified in the previous steps, the customized file simply contains all related statements specified in the [CUSTOM] section. - If a model file has been identified, ANXADM builds a ___ customized file by copying lines from the model file. For each statement in the model file corresponding to a statement specified in the [CUSTOM] section with a given "Field =" specification, ANXADM substitutes it with the statement specified. Refer to the example profile shown in Figure 1. [DEFINE] LOCDIR = D:\TXT LDRIVE=C: TARGDIR=C:\CLTTXT CLIENT=<CLT> [HERE] COPY <LDRIVE>\*.TXT <LOCDIR> [TRANSFER] DIR <LOCDIR> TO <TARGDIR> FILE <LDRIVE>\<CLT>.INI TO <TARGDIR>\SAVE [REMOTE] COPY <TARGDIR>\README.TXT <TARGDIR>\SAVE [CUSTOM] <CLT>.INI : = C:\MODEL\MDL.INI <CLT>.INI : TXT=README Figure 1. ANXADM Example Profile Using this example profile, ANXADM does the following: CHAPTER 6. LDU USER'S GUIDE ENHANCEMENTS 108 LDU USER'S GUIDE o Executes the copy command requested in the [HERE] section. o Prepares the master package file to transfer any file from directory D:\TXT on the server machine to C:\CLTTXT on the client machine. This package is named <servername>.PKG. o Prepares for each client an individual package file to transfer the client-related files. For instance, in the above example for a client named TARGET, an individual package TARGET.PKG is created to transfer D:\TXT\TARGET.INI to C:\CLTTXT\TARGET.INI o Creates an .INI file related to each client. The distribution is started using the command: LDS <master_package_file> After this distribution ends, a client machine with name TARGET has a copy of all files of the server directory D:\TXT stored in the client directory C:\CLTTXT, a file TARGET.INI in the directory C:\CLTTXT\SAVE, and a copy of C:\CLTTXT\README.TXT in the directory C:\CLTTXT\SAVE. The directory D:\CLTTXT also has a copy of all the extended attributes of the directory D:\TXT. The file C:\CLTTXT\SAVE\TARGET.INI is a copy of the server model file C:\MODEL\MDL.INI, but with the statement TXT=README instead of the original one. Format +---------------------------------------------------------------------------+ | | | >>--ANXADM--clt | cfile--.-----------------------.----------------------> | | '-/PRO--:--profile_name-' | | | | >--.----------------------.--.-------.--.------.-->< | | '-/SRV--:--Server_name-' |-/DEL--| '-/CLT-' | | |-/HERE-| | | '-/PKG--' | | | +---------------------------------------------------------------------------+ Parameters CHAPTER 6. LDU USER'S GUIDE ENHANCEMENTS 109 LDU USER'S GUIDE CLT The name of a client to be installed. CFILE The path and file name where a list of clients is to be installed. /PRO The path and file name of the profile to use to create the package. The default is NVDM2CLT.ADM. /SRV The name of server that will install the clients. If this parameter is not specified, srvname must be specified in the _______ [DEFINE] section of the profile. /DEL Specifies that all files created for specified clients are to be deleted. /HERE Specifies that programs specified in the [HERE] section of the profile are locally executed without creating any package. /PKG Specifies that only package creation, not command execution, is to be performed. /CLT Specifies that only packages related to the specified clients are to be created or deleted. CHAPTER 6. LDU USER'S GUIDE ENHANCEMENTS 110 INSTALLATION GUIDE PART 5. INSTALLATION AND CUSTOMIZATION GUIDE This part describes changes to make to the Installation and Customization Guide to reflect changes and corrections made after the documentation for NetView DM/2 Version 2.1 was sent for publication. (C) Copyright IBM Corp. 1991, 1995 111 INSTALLATION GUIDE CHAPTER 7. NETVIEW DM/2 INSTALLATION CONTROL Additional Configuration Parameters for Installation by Response File NetView DM/2 V.2.1 supports a new set of keywords that start a user program either before the installation of NetView DM/2 begins or as soon as it completes (or after the workstation restarts if installation is unattended). The keywords are: o "PreProcessingProgram" for the name of the user program or procedure that must execute before the installation of NetView DM/2 starts. o "PreProcessingParam" for the parameters that must accompany the program defined with PreProcessingProgram. o "PostProcessingProgram" for the name of the user program or procedure that must execute after the installation of NetView DM/2 has completed. o "PostProcessingParam" for the parameters that must accompany the program defined with PostProcessingProgram. o "IgnoreRC" (YES/NO); if this is set to YES, any return codes originated by the user program defined with PreProcessingProgram will be ignored. The default is NO. Return codes originated by user programs that execute after installation are ignored. These keywords have to be placed in the response file used to install NetView DM/2, when NetView DM/2 is installed using the following commands: o NVDMINST.EXE o NVDMFPIN.EXE o NVDMCLT.EXE User programs defined in PostProcessingProgram execute even when the installation of NetView DM/2 has failed. The following example shows these keywords when added to a response file used with NVDMINST to reinstall NetView DM/2. PreProcessingProgram = PREPACL.EXE PreProcessingParam = /P /D:IBMNVDM2 /B:BACKUP.FIL PostProcessingProgram = PREPACL.EXE PostProcessingParam = /R /B:BACKUP.FIL IgnoreRC = NO In this example a user program, PREPACL.EXE, is run both before and after installation, but using different parameters, to first back-up and then (C) Copyright IBM Corp. 1991, 1995 112 INSTALLATION GUIDE restore a file, BACKUP.FIL, that will be replaced by the installation process. Compatibility with Obsolete Software and Data Deletion Parameters With version 2.1 of NetView DM/2, parameters that delete NetView DM/2 software and data when NetView DM/2 is installed (such as DeleteCM, DeleteFS, DeleteTR, and DeleteWS) are no longer supported, since new run-time commands provide that capability. Including these parameters in a response file invoked by the NetView DM/2 installation command causes an error. With this CSD level, however, the NetView DM/2 installation program runs without an error when the DeleteCM, DeleteFS, DeleteTR, and DeleteWS parameters are specified in response files, although it ignores them. This allows you to use response files written for NetView DM/2 version 2.0 that contain these parameters without having to edit them. New NOSTARTUP Installation Parameter A new installation parameter, /NOSTARTUP, gives you the option to instruct the NetView DM/2 installation program to leave your system's STARTUP.CMD file unchanged. You can invoke this parameter in one of two ways: 1. Adding it directly to the NVDMINST command in the form of /NOSTARTUP 2. Inserting it as a key into a response file invoked by NVDMINST in the form: NOSTARTUP=Yes or NO o Specify NOSTARTUP=NO if you want NVDMINST to modify your STARTUP.CMD. This is the default value. o Specify NOSTARTUP=YES if you want NVDMINST to leave your STARTUP.CMD unchanged. If you do use the NOSTARTUP option (or NOSTARTUP=YES in the response file), __ then NVDMINST will create a STARTUP.ANX file containing the modified STARTUP.CMD file values. CHAPTER 7. NETVIEW DM/2 INSTALLATION CONTROL 113 INSTALLATION GUIDE CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE PAGE 21 - TOPIC 1.1.6 - Prerequisites PAGE 21 - TOPIC 1.1.6.3 - SOFTWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY CLIENT Change the last item in the list of software prerequisites for the LDU receiver to: o DOS J4.01, or J4.01/V, and subsequent versions, and an IBM NetBIOS driver PAGE 22 -TOPIC 1.1.6.5 - SOFTWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED CLIENT Change the last item in the list of software prerequisites to: o DOS J4.01, or J4.01/V, and subsequent versions, and an IBM NetBIOS driver PAGE 22 - FOLLOWING TOPIC 1.1.6.6 After the section of software requirements for the NetView DM/2 Remote administrator, add the following section: Connectivity with NetView DM/MVS If any of the NetView DM/2 V2.1 program packages (Entry, Extended or Remote Administrator) are used in conjunction with NetView DM for MVS acting as a focal point, then the software level of NetView DM for MVS used must be Version 1 Release 5. In addition, if the DASD Space Checking function provided with NetView DM/2 V2.1 is used, then APAR PN58771 must also be installed with NetView DM for MVS Version 1 Release 5. PAGE 22 - TOPIC 1.1.7 - COMPATIBILITY Add to the end of the first paragraph: This is true also with respect to the NetView DM/2 J2.0 Entry and Extended programs. All screens and messages are in English. PAGE 24 - TOPIC 1.1.7.1.3 - SUMMARY OF SOFTWARE REQUIREMENTS In the explanation of the NetBIOS software requirements for NetView DM/2 when OS/2 is installed, replace the list of products that provide NetBIOS with the following one: o OS/2 LAN Enabler 1.0 or higher o OS/2 LAN Server 3.0 or higher o NTS/2 1.0 or higher (C) Copyright IBM Corp. 1991, 1995 114 INSTALLATION GUIDE PAGE 25 - TOPIC 1.1.7.3 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY BASE Change the minimum hard disk storage recommended for the Change Distribution Manager (CDM) to 150MB. This figure includes the storage requirements to run NetView DM/2 and the software prerequisites for this NetView DM/2 component, as described in the Software Requirements section. This number may be increased depending upon the functions used. PAGE 26 - TOPIC 1.1.7.3 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY BASE Add the following items to the list of products providing the NetBIOS driver that support the appropriate communication adapters for the NetView DM/2 LDU Distributor: o OS/2 LAN Server 3.0 or higher o NTS/2 1.0 or higher PAGE 26 - TOPIC 1.1.7.4 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY CLIENT Change the second item in the list of system units for the LDU receiver to: o Any IBM Personal System/55 system unit (supporting Microchannel Architecture) supported by OS/2 Extended Edition J1.3 or by OS/2 Version J2.0 or higher, or by DOS J4.01, or J4.01/V, and subsequent versions. PAGE 26 - TOPIC 1.1.7.4 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY CLIENT Change the last two items showing the minimum storage requirements for the LDU receiver to: o 80MB of hard disk space, when running OS/2 o 20MB of hard disk space, when running DOS This figure includes the storage requirements to run NetView DM/2 and the software prerequisites for this NetView DM/2 component, as described in the Software Requirements section. This number may be increased depending upon the functions used. PAGE 27 - TOPIC 1.1.7.4 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 ENTRY CLIENT Replace the list of products providing the NetBIOS driver that support appropriate communication adapters for the NetView DM/2 LDU receiver with: o OS/2 LAN Enabler 1.0 or higher o OS/2 LAN Server 3.0 or higher o NTS/2 1.0 or higher CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 115 INSTALLATION GUIDE o IBM LAN Support Program or other compatible product (when DOS is installed) PAGE 27 - TOPIC 1.1.7.5 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED BASE Change the minimum storage recommended for the Change distribution manager (CDM) to 200MB of hard disk space. This figure includes the storage requirements to run NetView DM/2 and the software prerequisites for this NetView DM/2 component, as described in the Software Requirements section. This number may be increased depending upon the functions used. PAGE 27 - TOPIC 1.1.7.5 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED BASE Add the following items to the list of products providing the NetBIOS driver that support appropriate communication adapters for the Change distribution manager when LAN-attached: o OS/2 LAN Enabler 1.0 or higher o OS/2 LAN Server 3.0 or higher o NTS/2 1.0 or higher PAGE 28 - TOPIC 1.1.7.6 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED CLIENT Change the second item in the list of system units for a CC client to: o Any IBM Personal System/55 system unit (supporting Microchannel Architecture) supported by OS/2 Extended Edition J1.3 or by OS/2 Version J2.0 or higher, or by DOS J4.01, or J4.01/V, and subsequent versions. PAGE 29 - TOPIC 1.1.7.6 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED CLIENT Change the last two items showing the minimum storage requirements for a CC client to: o 80MB of hard disk space, when running OS/2 o 20MB of hard disk space, when running DOS This figure includes the storage requirements to run NetView DM/2 and the software prerequisites for this NetView DM/2 component, as described in the Software Requirements section. This number may be increased depending upon the functions used. PAGE 29 - TOPIC 1.1.7.6 - HARDWARE REQUIREMENTS FOR THE NETVIEW DM/2 EXTENDED CLIENT Replace the list of products providing the NetBIOS driver that support appropriate communication adapters for the NetView DM/2 Extended client with: o OS/2 LAN Enabler 1.0 or higher CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 116 INSTALLATION GUIDE o OS/2 LAN Server 3.0 or higher o NTS/2 1.0 or higher o IBM LAN Support Program or other compatible product (when DOS is installed) Incorrect Sample List Files for ADD_DEST Command The contents of the ASCII file that accompanies the ADD_DEST command in item a of the Customize NetView DM/2 step throughout the installation scenarios is incorrect and must be replaced. NOTE: No comment lines are allowed in the file. A description of each column for the next files follows: o column 1: RGN o column 2: REN o column 3: ROLE o column 4: For a server, its LU name; for a client, the RGN of its server o column 5: For a server, its LU mode; for a client, the REN of its server o column 6: Operating system o column 7: Description PAGE 56 - TOPIC 1.2.3.3.3 Replace the contents of DEST4A.LST with the following: NETWK1 NDM1 S NDM1 LU62 M Focal point NETWK1 CLIENTB C NETWK1 CDMBASE1 O Client B - Workst. B NETWK1 CLIENTD C NETWK1 CDMBASE1 D Client D - Workst. D PAGE 62 - TOPIC 1.2.4.1.3 No comment lines are allowed in the file. Disregard any comment lines in sample file DEST4A.LST. CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 117 INSTALLATION GUIDE PAGE 65 - TOPIC 1.2.4.1.4 No comment lines are allowed in the file. Disregard any comment lines in sample file DEST4B.LST. PAGE 70 - TOPIC 1.2.4.2.3 Replace the contents of DEST4A.LST with the following: NETWK1 NDM1 S NDM1 LU62 M Focal point NETWK1 DRA1 S DRA1 LU62 O Dept. remote adm.- Workst. D NETWK1 CLIENTB C NETWK1 SERV1 O Client B - Workst. B NETWK1 CLIENTC C NETWK1 SERV1 D Client C - Workst. C PAGE 74 - TOPIC 1.2.4.2.6 Replace the contents of DEST4D.LST with the following: NETWK1 NDM1 S NDM1 LU62 M Focal point NETWK1 DRA1 S SERV1 LU62 O CC server- Workst. A NETWK1 CLIENTB C NETWK1 SERV1 O Client B - Workst. B NETWK1 CLIENTC C NETWK1 SERV1 D Client C - Workst. C PAGE 77 - TOPIC 1.2.5.1.1 Replace the contents of DEST4A.LST with the following: NETWK1 CLIENTB C NETWK1 SERV1RA O Client B of LAN1 - Workst. B NETWK1 CLIENTC C NETWK1 SERV1RA D Client C of LAN1 - Workst. C NETWK1 SERV2 S SERV2 LU62 O CC server of LAN2 - Workst. D NETWK1 CLIENTE C NETWK1 SERV2 O Client E of LAN2 - Workst. E NETWK1 CLIENTF C NETWK1 SERV2 D Client F of LAN2 - Workst. F PAGE 81 - TOPIC 1.2.5.1.4 Replace the contents of DEST4D.LST with the following: NETWK1 SERV1RA S SERV1RA LU62 O CC server/RA of LAN1 - Workst. A NETWK1 CLIENTE C NETWK1 SERV2 O Client E of LAN2 - Workst. E NETWK1 CLIENTF C NETWK1 SERV2 D Client F of LAN2 - Workst. F CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 118 INSTALLATION GUIDE PAGE 85 - TOPIC 1.2.6.1.1 Replace the contents of PS2PWSRA.DES with the following: NETWK1 PS2SRV S PS2SRV LU62 O CC server NETWK1 PS2CL1 C NETWK1 PS2SRV O CC client of PS2SRV NETWK1 PS2CL2 C NETWK1 PS2SRV O CC client of PS2SRV PAGE 94 - TOPIC 1.2.6.3.1 Replace the contents of DESPS2RA.DES with the following: NETWK1 PS21 S PS21 LU62 O CC server of LANB NETWK1 PS22 C NETWK1 PS21 O CC client of LANB NETWK1 PS23 C NETWK1 PS21 O CC client of LANB NETWK1 PS26 S PS26 LU62 O CC server of LANC NETWK1 PS24 C NETWK1 PS26 O CC client of LANC NETWK1 PS25 C NETWK1 PS26 O CC client of LANC PAGE 142 - TOPIC 2.2.4 - Copying Files Prior to Installation At the bottom of the page, where parameters /DOSCLT and /RA of NVDMCOPY are described, replace ONLY with ALSO. This means that if /DOSCLT and/or /RA are specified, then the DOS client and the Remote Administrator feature image files, respectively, are copied in addition to the files contained in the NetView DM/2 package diskettes. PAGE 154 - TOPIC 2.2.9.2.2 - Uploading of ANXCMLDR.COM By NVDMIDOS Add the following item to the list of notes following the syntax diagram of NVDMIDOSat the bottom of page 153/top of page 154: o When installing the DOS CC client, NVDMIDOS adds a statement to AUTOEXEC.BAT that uploads the NetView DM/2 TSR. The statement is as follows: <product dir>\BIN\ANXCMLDR.COM /S:<ServerName> remote administrator /R:<ClientName> /T:<RebootTimeout>, <ResumeTimeout> remote administrator /U:<RebootAction> /A:<AdapterNum> For a description of these parameters refer to Configuration Parameters, page 161 or topic 2.2.11. CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 119 INSTALLATION GUIDE PAGE 345 - TOPIC 2.5.3.3.1 - ANXLUSER.C Replace the listing of sample program ANXLUSER.C with the following: /********************************************************************/ /* */ /* MODULE NAME : ANXLUSER */ /* */ /* DESCRIPTIVE NAME : SAMPLE USER PROCEDURE */ /* */ /* */ /* STATUS : RELEASE 1 MODIFICATION 0 */ /* */ /* FUNCTION : NONE */ /* */ /* NOTES : */ /* */ /* DEPENDENCIES : NONE */ /* */ /* RESTRICTIONS : NONE */ /* */ /* REGISTER USAGE : NO REGISTER RESTRICTION */ /* */ /* MODULE TYPE : PROCEDURE */ /* */ /* PROCESSOR : C */ /* */ /* SIZE : SEE ASSEMBLER LISTING */ /* */ /* ATTRIBUTES : REENTRANT,EXTERNAL,FAR */ /* */ /* ENTRY POINT(S) : ANXLUSER */ /* */ /* PURPOSE : SEE FUNCTION */ /* */ /* LINKAGE : STANDARD */ /* */ /* INPUT : */ /* */ /* PARAMETERS : */ /* TAB POINTER TO THE MESSAGE VARIABLE BUFFER */ /* MSGID POINTER TO THE MESSAGE ID NUMBER */ /* */ /* OUTPUT : */ /* */ /* PARAMETERS : */ /* RC RETURN CODE */ /* */ /* */ /* EXIT NORMAL : */ /* ------------------------------------------------------- */ /* | RC | DESCRIPTION | */ /* ------------------------------------------------------- */ /* | 0 | DEFAULT ACTION | */ CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 120 INSTALLATION GUIDE /* | 1 | MESSAGE LOG WITH POP_UP (FORCED) | */ /* | 2 | MESSAGE LOG WITHOUT POP_UP (FORCED) | */ /* ------------------------------------------------------- */ /* */ /* EXIT ERROR : NONE */ /* */ /* EXTERNAL REFERENCE : */ /* */ /* ROUTINES : NONE */ /* */ /* DATA AREAS : NONE */ /* */ /* CONTROL BLOCKS : NONE */ /* */ /* INTERNAL REFERENCE : */ /* */ /* ROUTINES : NONE */ /* */ /* MACROS : NONE */ /* */ /* MESSAGES : NONE */ /* */ /* PANELS : NONE */ /* */ /* CHANGE ACTIVITY : */ /* */ /* $MOD(ANXLUSER),COMP(CSER),PROD(ANX): MODULE DESCRIPTOR */ /* */ /* FLAG REASON RLSE DATE ORIGIN FLAG DESCRIPTOR FOLLOW */ /* ____ ________ ________ ______ ______ */ /* $A0= ANXVER1 SQ4S 931102 RNSLSA IMPLICIT FLAG, ORIGINAL */ /* */ /********************************************************************/ /********************************************************************/ /* source file */ /********************************************************************/ #define INCL_DOSMISC #define INCL_DOS #define INCL_DOSERRORS #include <os2.h> #include <stdlib.h> #include <stdio.h> #include <string.h> #include <acssvcc.h> void error_log (); extern void xfer_ms_data(PBYTE,unsigned short); char ch; struct uspgm { unsigned short vrnb; CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 121 INSTALLATION GUIDE char far *mvrk[9]; unsigned short mvrs[9]; }; static BYTE alert [] = { 0x0B,0x92,0x00,0x00,0x01,0x31,0x12,0xb5,0x58,0xd3,0x10, 0x04,0x93,0x10,0x23, 0x0e,0x96,0x06,0x01,0x10,0x23,0xf0,0xbe,0x06,0x81,0x30,0x00,0x32,0xA0, 0x02,0x82}; /***********************************/ /* ERROR ROUTINE EXAMPLE */ /***********************************/ void error_log () { DosBeep(500,1000); /* Insert here your own Error Log */ DosBeep(1000,500); /* Routine */ DosBeep(500,1000); } /********************************************************************/ /********************************************************************/ far pascal anxluser(char far *msgid, struct uspgm far *tab) { USHORT MsgNbr; /* Translated Message Number */ MsgNbr = atoi(msgid); ch=0; switch (MsgNbr) { case 901: /* NON retriable error */ if ( (strncmp(tab->mvrk[2],"A1",2)) && (strncmp(tab->mvrk[2],"A3",2)) && (strncmp(tab->mvrk[2],"A2",2)) && (strncmp(tab->mvrk[2],"AC",2)) && (strncmp(tab->mvrk[2],"AA",2)) ) { xfer_ms_data ( alert, sizeof (alert) ); } /* endif SNADS msgs */ return(2); break; case 618: /* retriable error */ { xfer_ms_data ( alert, sizeof (alert) ); } return(2); break; default: return(0); /* Accept Default i.e. PopUp for ANX0211 */ CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 122 INSTALLATION GUIDE break; } /* endswitch */ This listing is in line with the sample ANXLUSER.C in the NetView DM/2 publications sample diskette. APPENDIX F - TOPIC APPENDIX1.6.3 - Locating Some Important Files Replace Table 26, File Location in the Entry Package, with the following: +---------------------------------------------------------------------------+ | Table 5. File Location in the Entry Package | +-------------------------------------+-------------------------------------+ | FILE NAME | DISKETTE NUMBER | +-------------------------------------+-------------------------------------+ | COPYSRV.CMD | 19 | +-------------------------------------+-------------------------------------+ | NVDMCDSK.CMD | 1 | +-------------------------------------+-------------------------------------+ | NVDMCOPY.EXE | 1 | +-------------------------------------+-------------------------------------+ | NVDMDOC.EXE | 11 | +-------------------------------------+-------------------------------------+ | NVDMDTCT.EXE | 2 | +-------------------------------------+-------------------------------------+ | NVDMDTTR.EXE | 2 | +-------------------------------------+-------------------------------------+ | NVDMINST.EXE | 9 | +-------------------------------------+-------------------------------------+ | NVDMENV.EXE | 5 | +-------------------------------------+-------------------------------------+ | NVDMPMS.EXE | 1 | +-------------------------------------+-------------------------------------+ | NVDMREC.EXE | 10 | +-------------------------------------+-------------------------------------+ | NVDMUNIN.EXE | 2 | +-------------------------------------+-------------------------------------+ | *.PAN | 19 | +-------------------------------------+-------------------------------------+ | *.TXT | 19 | +-------------------------------------+-------------------------------------+ Replace Table 27, File Location in the Extended Package, with the following: CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 123 INSTALLATION GUIDE +---------------------------------------------------------------------------+ | Table 6. File Location in the Extended Package | +-------------------------------------+-------------------------------------+ | FILE NAME | DISKETTE NUMBER | +-------------------------------------+-------------------------------------+ | COPYCLI.CMD | 27 | +-------------------------------------+-------------------------------------+ | COPYSRV.CMD | 27 | +-------------------------------------+-------------------------------------+ | NVDMCDSK.CMD | 1 | +-------------------------------------+-------------------------------------+ | NVDMCLT.EXE | 11 | +-------------------------------------+-------------------------------------+ | NVDMCOPY.EXE | 1 | +-------------------------------------+-------------------------------------+ | NVDMDCPY.EXE | 13 | +-------------------------------------+-------------------------------------+ | NVDMDOC.EXE | 19 | +-------------------------------------+-------------------------------------+ | NVDMDTCT.EXE | 2 | +-------------------------------------+-------------------------------------+ | NVDMDTTR.EXE | 2 | +-------------------------------------+-------------------------------------+ | NVDMENV.EXE | 9 | +-------------------------------------+-------------------------------------+ | NVDMIDFO.EXE | 13 | +-------------------------------------+-------------------------------------+ | NVDMIDOS.EXE | 13 | +-------------------------------------+-------------------------------------+ | NVDMINST.EXE | 10 | +-------------------------------------+-------------------------------------+ | NVDMPMC.EXE | 11 | +-------------------------------------+-------------------------------------+ | NVDMPMS.EXE | 1 | +-------------------------------------+-------------------------------------+ | NVDMREC.EXE | 18 | +-------------------------------------+-------------------------------------+ | NVDMUNIN.EXE | 2 | +-------------------------------------+-------------------------------------+ | *.PAN | 27 | +-------------------------------------+-------------------------------------+ | *.TXT | 27 | +-------------------------------------+-------------------------------------+ CHAPTER 8. CORRECTIONS TO THE INSTALLATION AND CUSTOMIZATION GUIDE 124 MESSAGES AND ERROR RECOVERY GUIDE PART 6. MESSAGES AND ERROR RECOVERY GUIDE This part describes changes to make to the Messages and Error Recovery Guide to reflect changes and corrections made after the documentation for NetView DM/2 Version 2.1 was sent for publication. (C) Copyright IBM Corp. 1991, 1995 125 MESSAGES AND CODES CHAPTER 9. MESSAGES AND CODES Changed Messages The following messages have been changed. Message ANXI5587 Throughout the text and the explanation of this message change the words change file to object and filename to name. ___________ ______ ________ ____ Message ANX0203 Throughout the text and the explanation of this message change the words table name to qualifier name. __________ ______________ Message ANX0253 Change the text of this message to read as follows. ANX0253E (E) THE EXTERNAL PROGRAM '***' FAILED WITH EXIT CODE '***'. 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. 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 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. (C) Copyright IBM Corp. 1991, 1995 126 MESSAGES AND CODES Message ANX0179 Change the text of this message to read as follows. ANX0179E (E) CANNOT START PROGRAM '***'. SYSTEM ERROR '***' LOADING '***'. EXPLANATION: An Initiate or External Install has attempted to run a program that needs other files (like DLL files) to run. SYSTEM ACTION: The Request fails and the CDM agent process continues with another request. USER RESPONSE: Check that any files needed by the program are stored in a subdirectory that is available to it. Message ANX0234 Change the text of this message to read as follows. ANX0234 (E) THE PROGRAM '***' SPECIFIED FOR THE GLOBAL NAME '***' TERMINATED BECAUSE OF A HARD ERROR ABORT. EXPLANATION: The system detected a hard error during the execution of an Initiate or External Install program. SYSTEM ACTION: The Install/Initiate request ends in error. Other Change Management requests are processed. USER RESPONSE: Check the hardware by running Diagnostic diskettes. Message ANX0235 Change the text of this message to read as follows. ANX0235 (E) THE PROGRAM '***' SPECIFIED FOR THE GLOBAL NAME '***' TERMINATED BECAUSE A TRAP OPERATION OCCURRED. EXPLANATION: The system detected a Trap error while running an Initiate or External Install program. SYSTEM ACTION: The Install/Initiate request ends in error. Other Change Management requests are processed. USER RESPONSE: Check the Trap number reported as an exit code in message. CHAPTER 9. MESSAGES AND CODES 127 MESSAGES AND CODES Message ANX0236 Change the text of this message to read as follows. ANX0236 (E) THE PROGRAM '***' SPECIFIED FOR THE GLOBAL NAME '***' TERMINATED BECAUSE OF AN UNINTERCEPTED DOSKILLPROCESS. EXPLANATION: The system detected a DosKillProcess for the process of the Initiate or External Install program that was running. The DOSKillProcess was not intercepted by the application. SYSTEM ACTION: The Install/Initiate requests ends in error. Other Change Management requests are processed. USER RESPONSE: Determine what stopped the external process and repeat the request. Message ANX0237 Change the text of this message to read as follows. ANX0237 (E) UNEXPECTED ERROR STARTING PROGRAM '***' SPECIFIED FOR THE GLOBAL NAME '***'. EXPLANATION: An unexpected error occurred while trying to start an Initiate or External Install program. The System Error code is the error number returned by the Operating System when it tries to run the specified program: o In the Install section of a Change File o As a local file of a procedure object to be initiated. SYSTEM ACTION: The Install/Initiate request ends in error. Other Change Management requests are processed. USER RESPONSE: Determine what caused the error and repeat the request. Message ANX2002 Change the text of this message to read as follows. CHAPTER 9. MESSAGES AND CODES 128 MESSAGES AND CODES ANX2002 (E) THE NETWORK ID DEFINED IN THE APPC WAS CHANGED. A MIGRATION OF THE NETVIEW DM/2 DATABASE IS NEEDED. PRESS ACCEPT TO MIGRATE NOW OR EXIT TO AVOID THE PROGRAM TO START. EXPLANATION: The Network ID defined in the APPC was changed and the catalog must be migrated. SYSTEM ACTION: Press ACCEPT to migrate the NetView DM/2 catalog. This will take several minutes depending on the catalog size. When you press EXIT, the product is not started and you can change the NetWork ID again or repeat the operation later. USER RESPONSE: Press ACCEPT or EXIT. Change Informational Messages to Error Messages The following messages were formerly classified as informational, but should now be considered error messages. See the Messages and Error Recovery Guide _________________________________ for additional information on each message. ANX1831 (E) SENSE CODE sense_code HAS BEEN DETECTED BY DESTINATION __________ destination_id FOR AN INSTALL COMMAND ON THE OBJECT WITH GLOBAL ______________ NAME name. ____ ANX1832 (E) SENSE CODE sense_code HAS BEEN DETECTED FROM DESTINATION __________ destination_id FOR A REMOVE COMMAND ON THE OBJECT WITH GLOBAL ______________ NAME name. ____ ANX1833 (E) SENSE CODE sense_code HAS BEEN DETECTED FROM DESTINATION __________ destination_id FOR AN ACCEPT COMMAND ON THE OBJECT WITH GLOBAL ______________ NAME name. ____ ANX1836 (E) SENSE CODE sense_code HAS BEEN DETECTED FROM DESTINATION __________ destination_id FOR AN INITIATE COMMAND ON THE OBJECT WITH ______________ GLOBAL NAME name. THE PROCEDURE ENDED WITH RETURN CODE ____ return_code. ___________ ANX1837 (E) SENSE CODE sense_code HAS BEEN DETECTED FROM DESTINATION __________ destination_id FOR AN ACTIVATE COMMAND. ______________ ANX1840E (E) OBJECT WITH GLOBAL NAME global_name HAS BEEN PUT IN A ___________ BACK-LEVEL STATUS FOR DESTINATION destination_id. ______________ ANX1854E (E) SENSE CODE sense_code HAS BEEN DETECTED BY DESTINATION __________ destination_id FOR THE OPERATION STARTED AT date_time ADDRESSED ______________ _________ TO DESTINATION destination_. ____________ ANX1855E (E) SENSE CODE sense_code HAS BEEN DETECTED BY DESTINATION __________ destination_id FOR THE OPERATION STARTED AT date_time. ______________ _________ ANX1856 (E) SENSE CODE sense_code HAS BEEN DETECTED BY DESTINATION __________ destination_id FOR THE SEND OPERATION STARTED AT date_time OF ______________ _________ THE OBJECT WITH GLOBAL NAME name. ____ ANX1857E (E) SENSE CODE sense_code HAS BEEN DETECTED BY DESTINATION __________ destination_id FOR THE DELETE OPERATION STARTED AT date_time OF ______________ _________ THE OBJECT WITH GLOBAL NAME name. ____ CHAPTER 9. MESSAGES AND CODES 129 MESSAGES AND CODES ANX1858E (E) SENSE CODE sense_code HAS BEEN DETECTED BY DESTINATION __________ destination_id FOR THE RETRIEVE OPERATION STARTED AT date_time ______________ _________ OF THE OBJECT WITH GLOBAL NAME name. ____ New Messages The following messages have been added. Message ANX0088 ANX0088 (E) THE INSTALL REQUEST FOR AN OBJECT WITH GLOBAL NAME name WAS ____ UNSUCCESSFUL BECAUSE THE OBJECT IS ALREADY IN INSTALLED NON REMOVABLY STATUS. EXPLANATION: An INSTALL for an already installed change was requested and CDM rejected this request. SYSTEM ACTION: The request is terminated and processing continues. USER RESPONSE: Ensure that the request is consistent with the object status. Message ANX1488 ANX1488 (E) THE NEW NETWORK ID IS NOT CONSISTENT WITH THE CURRENT NETWORK DEFINITION, BECAUSE THE DESTINATION '%1.%2' IS ALREADY DEFINED. EXPLANATION: The new Network ID defined in the APPC prevents a correct migration of the catalog because with this new definition there are two destinations with the same RGN.REN. SYSTEM ACTION: NetView DM/2 will not start or complete the current command. USER RESPONSE: USER RESPONSE: Change the Network ID and delete all the destinations that will be in conflict with the local destinations updated with the new RGN. Then change the Network ID again. CHAPTER 9. MESSAGES AND CODES 130 MESSAGES AND CODES Message ANX2014 ANX2014 (E) CHANGE_DEST FAILED. THE RGN OF THE CLIENT HAS NOT BEEN SPECIFIED OR IT IS DIFFERENT FROM THE RGN OF THE NEW SERVER. EXPLANATION: CHANGE_DEST may be applied only if the RGN of the old server is the same as the RGN of the new server. SYSTEM ACTION: The client is not moved to the other server. USER RESPONSE: Check if you entered the correct RGN for the client and re-enter the command. Message ANX1322 ANX1322W THE FILE '%1' COULD NOT BE OPENED. 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 ANX1323W THE DIRECTORY '%1' COULD NOT BE REMOVED. RC='%2' 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 ANX1324W EMPTY DIRECTORIES WERE NOT REMOVED. 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. CHAPTER 9. MESSAGES AND CODES 131 MESSAGES AND CODES Message ANX1331 ANX1331W CANNOT EXECUTE THE DOS/WINDOWS EXTERNAL INSTALL PROGRAM '***' SPECIFIED IN INSTALL SECTION OF GLOBAL NAME '***' BECAUSE THE TSR WAS NOT INSTALLED. EXPLANATION: An External Install has attempted to run a DOS or Windows program when the NetView DM/2 DOS TSR for CID support was not installed. SYSTEM ACTION: The Program may have been executed but the Request fails and the CDM agent process continues with another request. USER RESPONSE: Check that the file ANXCCTRS.COM is present under the <product>«BIN directory. Message ANX1332 ANX1332W THE DOS/WINDOWS EXTERNAL INSTALL PROGRAM '***' SPECIFIED IN INSTALL SECTION OF GLOBAL NAME '***' WAS NOT EXECUTED OR DIDN'T RETURN ANY CID EXIT CODE. EXPLANATION: An External Install has attempted to run a DOS or Windows program. The following conditions could occur: o The DOS or Windows environment are not supported/installed at the target Workstation o The DOS or Windows application is not CID-compliant because it didn't return the CID exit codes through the documented interface. SYSTEM ACTION: The Program may have been executed if it not CID-compliant. The Request fails and the CDM agent process continues with another request. USER RESPONSE: Check that the needed environment is supported/installed or that the Application is CID-compliant. Message ANX1333 ANX1333W THE REXX INTERPRETER RETURNED RC '***' WHEN PROCESSING PROGRAM '***'. EXPLANATION: The REXX interpreter returned a negative return code when processing a .CMD program referenced in a change file attempted to INSTALL or when attempting to INITIATE a PROC object. CHAPTER 9. MESSAGES AND CODES 132 MESSAGES AND CODES SYSTEM ACTION: The task INSTALL or INITIATE failed. USER RESPONSE: Check the rc (return code) returned from REXX interpreter and verify the related condition. Message ANX1334 ANX1334W THE INVOCATION OF THE PROGRAM '***' FAILED BECAUSE REXX ENVIRONMENT IS NOT INSTALLED OR CORRUPTED. EXPLANATION: The invocation of a .CMD program, referenced in a change file or part of a PROC object, failed because REXX is not available on the target NetView DM/2 node. SYSTEM ACTION: The task INSTALL or INITIATE failed. USER RESPONSE: Verify if REXX exists on the target node, otherwise install it. Message ANX1325 ANX1325 CDM AGENT STARTING. YOU SHOULD REMOVE THE BOOT DISKETTE AND PRESS ENTER. THEN YOU CAN LEAVE THE WORKSTATION UNATTENDED. EXPLANATION: The CDM Agent is starting and from this moment on it does not need the diskette to be inserted any more. SYSTEM ACTION: The message is issued before trying to attach the CC Server Shared Areas. In this way even if the CC Server has not been started yet, you should remove the diskette. Once the diskette is removed, the CDM Agent will log the messages only remotely. USER RESPONSE: You should remove the diskette and press Enter. Message ANX1449 ANX1449 CREATE DIRECTORY ERROR. EXPLANATION: An error occurred while creating a CC client subdirectory during NetView DM/2 cleanup process. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: An I/O error occurred: your Hard Disk might be corrupted. If problem persists contact the IBM Support Center. CHAPTER 9. MESSAGES AND CODES 133 MESSAGES AND CODES Message ANX1454 ANX1454 UNEXPECTED ERROR. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. Message ANX1459 ANX1459 SERVER SERVER IS MISSING FROM SNA/DS TABLES. EXPLANATION: A remote CC Server defined in NetView DM/2 Catalog is not defined in Transmission Controller Destination Table. SYSTEM ACTION: Processing continues normally. USER RESPONSE: Configure the Remote CC Server in Transmission Controller Destination Table by CDM CONFIG command (with #UPDATE directive) Message ANX1461 ANX1461 ROUTING INFORMATION READ ERROR. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. CHAPTER 9. MESSAGES AND CODES 134 MESSAGES AND CODES Message ANX1462 ANX1462 ROUTING INFORMATION MISMATCH BETWEEN REMOTE CLIENT AND REMOTE SERVER. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. Message ANX1463 ANX1463 DISK FULL ERROR. EXPLANATION: An internal error occurred because no space is available on the hard disk. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Refer to the NetView DM/2 documentation to assess the amount of fixed disk space needed. Message ANX1464 ANX1464 DELETE REPORT FILES ERROR. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. CHAPTER 9. MESSAGES AND CODES 135 MESSAGES AND CODES Message ANX1465 ANX1465 ERROR WHILE CREATING CLIENT CMREQ DIRECTORY FOR LOCAL WORKSTATION . EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. Message ANX1466 ANX1466 SERVER IS MISSING FROM DATABASE - ANXTWS TABLE. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. Message ANX1467 ANX11467 UNLOCK CATALOG ERROR. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. CHAPTER 9. MESSAGES AND CODES 136 MESSAGES AND CODES Message ANX1468 ANX1468 DATABASE ACCESS ERROR - UPDATE ANXTWS TABLE. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. Message ANX1469 ANX1469 DATABASE ACCESS ERROR - READ ANXTWS TABLE. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. Message ANX1470 ANX1470 ERROR IN READING THE CLEAN UP CHECKPOINT FILE. EXPLANATION: None. SYSTEM ACTION: None. USER RESPONSE: Contact your IBM Support Center. Message ANX1471 CHAPTER 9. MESSAGES AND CODES 137 MESSAGES AND CODES ANX1471 REQUEST/REPLY FILE CANNOT BE RENAMED WITH THE VALID EXTENSION. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. Message ANX1472 ANX1472 DIRECTORY FOR REQUEST/REPLY FILE CANNOT BE CLEARED FOR UNUSED FILE. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. Message ANX2031 ANX2031 NVDMRDSK HAS FAILED BECAUSE OF INVALID TARGET DIR EXPLANATION: The target drive specified is not a valid one SYSTEM ACTION: insert a correct diskette USER RESPONSE: procedure terminates Message ANX7241 CHAPTER 9. MESSAGES AND CODES 138 MESSAGES AND CODES ANX7241 THE COMMAND ISSUED IS INVALID. PARAMETER IS NOT A RECOGNIZED PARAMETER EXPLANATION: The keyword parameter indicator was followed by a value that is not a keyword. The invalid parameter is shown in the message. This message is displayed also when the command is longer than 128 chars. In this case the Parameter part of the message cannot be understand. SYSTEM ACTION: Processing terminates normally and control returns to the system. USER RESPONSE: Resubmit the command specifying the correct parameter. Message ANXI5307 ANXI5307 ONLY CHANGE FILES AND REFRESH DATABASE TABLE OBJECTS ARE VALID FOR THIS OPERATION. THE OBJECTS WITH DIFFERENT OBJECT TYPE WILL NOT BE DISPLAYED ON THE FOLLOWING DIALOG. EXPLANATION: Those objects you have selected which are not Change Files or Refresh Database Tables are not allowed for the selected function and are not displayed in the list of selected objects. SYSTEM ACTION: Objects that are not Change Files Refresh Database Tables are not in the list. USER RESPONSE: None Message ANX1313 ANX1313 ACCESS DENIED IN HANDLING FILE OR DIRECTORIES. EXPLANATION: One of the following errors occurred: o The file is marked Read Only. o The file or directory is in use. o You do not have the correct access privilege to modify the file or directory. o The file name or directory name is incorrect or they did not follow the rules of the File System of the target machine. SYSTEM ACTION: The command fails. CHAPTER 9. MESSAGES AND CODES 139 MESSAGES AND CODES USER RESPONSE: None o Use the command ATTRIB to change the Read Only attribute. o Identify the file or program using the file and halt it. o Log on with the correct access privilege. Contact your System Administrator for details. o Correct the file name or directory name. Message ANX1331 ANX1331 CANNOT EXECUTE THE DOS/WINDOWS EXTERNAL INSTALL PROGRAM %1 SPECIFIED IN INSTALL SECTION OF GLOBAL NAME '%2' BECAUSE THE TSR WAS NOT INSTALLED.%0 EXPLANATION: An External Install has attempted to run a DOS or Windows program when the NetView DM/2 DOS TSR for CID support was not installed. SYSTEM ACTION: The Program may have been executed but the Request fails and the CDM agent process continues with another request. USER RESPONSE: Check that the file ANXCCTSR.COM is present under the <product>«BIN directory. sysact.<write here the system actions that follow the message issue> Message ANX1332 ANX1332 THE WINDOWS EXTERNAL INSTALL PROGRAM %1 SPECIFIED IN INSTALL SECTION OF GLOBAL NAME '%2' WAS NOT EXECUTED OR DIDN'T RETURN ANY CID EXIT CODE. EXPLANATION: An External Install has attempted to run a Windows program. The following conditions could occur: o The Windows application run but the agent was not able to detect its return code because the application is not CID compliant and doesn't return the CID exit codes through the documented interface o The Windows environment didn't run the application for environment problems. SYSTEM ACTION: The Program may have been executed if it is not CID-compliant. The Request ends successfully issuing this warning message and the CDM agent process continues with another request. CHAPTER 9. MESSAGES AND CODES 140 MESSAGES AND CODES USER RESPONSE: Check that the needed environment is supported/installed properly or that the Application is CID-compliant. Message ANX1335 ANX1335 CANNOT EXECUTE THE DOS/WINDOWS EXTERNAL INSTALL PROGRAM %1 SPECIFIED IN INSTALL SECTION OF GLOBAL NAME '%2' BECAUSE DOS/WINDOWS ENVIRONMENT IS NOT INSTALLED. EXPLANATION: Before executing the DOS or Windows Application the CDM Agent checks the existence of the DOS (and Windows) shell COMMAND.COM (WIN.COM) This message is issued if the check fails. SYSTEM ACTION: The Request ends in error and the CDM Agent process continues with another request. USER RESPONSE: Check if the DOS/Windows environment is installed properly. Message ANX1449 ANX1449 CREATE DIRECTORY ERROR. EXPLANATION: An error occurred while creating a CC client subdirectory during NetView DM/2 cleanup process. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: An I/O error occurred: your Hard Disk might be corrupted. If problem persists contact the IBM Support Center. Message ANX1454 ANX1454 UNEXPECTED ERROR. EXPLANATION: An internal error occurred. SYSTEM ACTION: Processing ends normally and control is returned to OS/2. USER RESPONSE: Check the message log for other messages that might describe the nature of the problem. If the problem is not an environmental problem (for example, a disk problem), an internal processing error occurred. Report it to the IBM Support Center. CHAPTER 9. MESSAGES AND CODES 141 MESSAGES AND CODES Message ANX1459 ANX1459 (I) SERVER <SERVER_NAME> IS MISSING FROM SNA/DS TABLES. EXPLANATION: A remote CC Server defined in NetView DM/2 Catalog is not defined in Transmission Controller Destination Table. SYSTEM ACTION: Processing continues normally. USER RESPONSE: Configure the Remote CC Server in Transmission Controller Destination Table by CDM CONFIG command (with #UPDATE directive) Message ANX1470 ANX1470 ERROR IN READING THE CLEAN UP CHECKPOINT FILE. EXPLANATION: An error occurred attempting to read the NetView DM/2 clean-up checkpoint file. SYSTEM ACTION: Processing ends abnormally and control is returned to OS/2. USER RESPONSE: Contact your IBM Support Center. Message ANX2053 ANX2053 LOCALE HAS AN INVALID SYNTAX EXPLANATION: LOCALE has been invoked with an invalid syntax SYSTEM ACTION: the program terminates USER RESPONSE: resubmit the command with the correct syntax Message ANX2054 ANX2054 THE LOCALE SPECIFIED IS NOT AVAILABLE EXPLANATION: the language requested is not available or the CDM is active SYSTEM ACTION: the program terminates USER RESPONSE: resubmit the command with the available language or stop the CDM CHAPTER 9. MESSAGES AND CODES 142 MESSAGES AND CODES ANX2055 LOCALE HAS BEEN CHANGED EXPLANATION: the language has been changed SYSTEM ACTION: the program terminates USER RESPONSE: none ANX2056 HELP ON THE COMMANDS NOT AVAILABLE FOR THE LOCALE REQUESTED EXPLANATION: the module is not available for the language requested SYSTEM ACTION: the program terminates USER RESPONSE: none ANX2057 MESSAGES FOR THE DIALOG ARE NOTE AVAILABLE FOR THE LOCALE REQUEST EXPLANATION: the module is not available for the language requested SYSTEM ACTION: the program terminates USER RESPONSE: none ANX2058 HELPS FOR THE DIALOG ARE NOTE AVAILABLE FOR THE LOCALE REQUEST EXPLANATION: the module is not available for the language requested SYSTEM ACTION: the program terminates USER RESPONSE: none Message ADM0103 ADM0103 TOO FEW PARAMETERS. EXPLANATION: ANXADM has been invoked with too few parameters SYSTEM ACTION: Process terminates USER RESPONSE: Resubmit the invocation specifying correct parameters CHAPTER 9. MESSAGES AND CODES 143 MESSAGES AND CODES Message ADM0104 ADM0104 NAME IS NOT A VALID CLIENT NAME. EXPLANATION: ANXADM has been invoked with NAME as clientname but this does not result to be a valid client name. SYSTEM ACTION: Process terminates USER RESPONSE: Resubmit the invocation changing the client name. Message ADM0105 ADM0105 THERE IS NO CLIENT NAME SPECIFIED. EXPLANATION: ANXADM has been invoked with no clientname SYSTEM ACTION: Process terminates USER RESPONSE: Resubmit the invocation with some client names. Message ADM0106 ADM0106 PARAMETER IS A WRONG PARAMETER. EXPLANATION: ANXADM has been invoked with a wrong parameter. SYSTEM ACTION: Process terminates USER RESPONSE: Resubmit the invocation with correct parameters. Message ADM0107 ADM0107 NAME IS A TOO LONG NAME TO BE A SECTION NAME. EXPLANATION: ANXADM has read a profile in which a section name has more than 20 characters SYSTEM ACTION: Process terminates USER RESPONSE: Change section name in order to limit its length to a maximum of 20 characters. Then invoke the utility again. CHAPTER 9. MESSAGES AND CODES 144 MESSAGES AND CODES Message ADM0108 ADM0108 ERROR OPENING FILE FILE . EXPLANATION: ANXADM has not found the specified file or it is locked. SYSTEM ACTION: Process terminates USER RESPONSE: Please check for file presence and be sure that is not locked. Then invoke the utility again. Message ADM0109 ADM0109 ERROR READING FILE FILE . EXPLANATION: ANXADM has found a problem reading the specified file. SYSTEM ACTION: Process terminates USER RESPONSE: Please check if file is still available. Then invoke the utility again. Message ADM0110 ADM0110 NAME IS NOT A VALID SECTION NAME. EXPLANATION: ANXADM has not found a section name different than allowed section names SYSTEM ACTION: Process terminates USER RESPONSE: Please correct section name. Allowed section names are: [DEFINE] [HERE] [TRANSFER] [REMOTE] [CUSTOM] Then invoke the utility again. Message ADM0112 ADM0112 OUT OF MEMORY. EXPLANATION: ANXADM cannot reserve further memory that it needs. SYSTEM ACTION: Process terminates CHAPTER 9. MESSAGES AND CODES 145 MESSAGES AND CODES USER RESPONSE: Please try to invoke the utility passing fewer client names. If the error comes up again wait for the end of other processes and then invoke the utility again. Message ADM0113 ADM0113 LINE IS NOT A VALID DEFINE LINE. EXPLANATION: ANXADM has found a line with wrong syntax in the [DEFINE] section of current profile. Correct syntax is VAR1=VALUE|<VAR2> SYSTEM ACTION: Process terminates USER RESPONSE: Correct the mentioned line. Then invoke the utility again. Message ADM0114 ADM0114 VAR HAS A DUPLICATE VALUE. EXPLANATION: ANXADM has found two or more definitions related to VAR. SYSTEM ACTION: Process terminates USER RESPONSE: Cancel one of the two definitions. Then invoke the utility again. Message ADM0115 ADM0115 A VALUE RELATED TO VAR HAS NOT BEEN FOUND. EXPLANATION: In [DEFINE] section ANXADM has not found a definition related to VAR that is used in one of other sections. SYSTEM ACTION: Process terminates USER RESPONSE: Insert a definition related to VAR in [DEFINE] section. Then invoke the utility again. CHAPTER 9. MESSAGES AND CODES 146 MESSAGES AND CODES Message ADM0116 ADM0116 VAR HAS NOT BEEN FOUND AMONG RECORDED DEFINITIONS. EXPLANATION: In [DEFINE] section ANXADM has not found a definition related to VAR that is used in one of other sections. SYSTEM ACTION: Process terminates USER RESPONSE: Insert a definition related to VAR in [DEFINE] section. Then invoke the utility again. Message ADM0118 ADM0118 LINE IS NOT A VALID TRANSFER LINE. EXPLANATION: In the [TRANSFER] section of current profile ANXADM has found a line with a wrong syntax. Correct syntax is TREE|DIR|FILE Locdir TO Trgdir. Locdir is the name of directory on server machine; Trgdir is the name of directory on target client machine. SYSTEM ACTION: Process terminates USER RESPONSE: Correct the mentioned line. Then invoke the utility again. Message ADM0119 ADM0119 LINE IS NOT A VALID CUSTOM LINE. EXPLANATION: In the [CUSTOM] section of current profile ANXADM has found a line with a wrong syntax. Correct syntax is Filename : Field = Value. Filename is a name of file without path, Field is a variable and Value is the related value. Field may be blank and in this case Value is a fully qualified path and file name. SYSTEM ACTION: Process terminates USER RESPONSE: Correct the mentioned line. Then invoke the utility again. CHAPTER 9. MESSAGES AND CODES 147 MESSAGES AND CODES Message ADM0120 ADM0120 A FILENAME HAS NOT BEEN FOUND IN LINE LINE EXPLANATION: ANXADM has not found a filename in [CUSTOM] line LINE Remind correct syntax is Filename : Field = Value. Filename is a name of file without path, Field is a variable and Value is the related value. Field may be blank and in this case Value is a fully qualified path and file name. SYSTEM ACTION: Process terminates USER RESPONSE: Correct the mentioned line. Then invoke the utility again. Message ADM0121 ADM0121 FILE FILE HAS NOT BEEN FOUND IN TRANSFER SECTION. EXPLANATION: ANXADM has found FILE mentioned in a [CUSTOM] line but has not found a line in a [TRANSFER] section where this file is mentioned. SYSTEM ACTION: Process terminates USER RESPONSE: Correct the name of file in [CUSTOM] section or introduce a line in [TRANSFER] section to state where it should be transferred. Then invoke the utility again. Message ADM0122 ADM0122 MODEL FILE IS NOT SPECIFIED FOR FILE FILE EXPLANATION: ADM has not a line in [CUSTOM] section specifying a file that it can use as model file. SYSTEM ACTION: Process terminates USER RESPONSE: In [CUSTOM] section introduce a line to state which and where is model file. Then invoke the utility again. CHAPTER 9. MESSAGES AND CODES 148 MESSAGES AND CODES Message ADM0123 ADM0123 COMMAND ENDED WITH RETURN CODES EXPLANATION: ANXADM has received a return code different than 0 from last command it issued. SYSTEM ACTION: Process terminates USER RESPONSE: Refer to documentation of program issued. Message ADM0124 ADM0124 EXECUTION OF COMMAND FAILED OS2 RC EXPLANATION: ANXADM has received a message from operating system stating that last command cannot be issued. Operating return code is shown. SYSTEM ACTION: Process terminates USER RESPONSE: Refer to operating system documentation. Message ADM0125 ADM0125 NVDM/2 RESULTS NOT INSTALLED. EXPLANATION: ANXADM has checked that found Nvdm/2 results not installed. SYSTEM ACTION: Process terminates USER RESPONSE: Install Nvdm/2 before invoking the utility again. Message ADM0126 ADM0126 ERROR MAKING DIRECTORY DIR EXPLANATION: ANXADM HAS CHECKED AN ERROR MAKING THE MENTIONED DIRECTORY. SYSTEM ACTION: PROCESS TERMINATES USER RESPONSE: CHECK IF THE A FILE WITH SAME NAME EXIST OR IF DIRECTORY NAME HAS A RIGHT SYNTAX. THEN INVOKE THE UTILITY AGAIN. CHAPTER 9. MESSAGES AND CODES 149 MESSAGES AND CODES Message ADM0127 ADM0127 NOT COMPATIBLE OPTIONS. EXPLANATION: ANXADM HAS BEEN INVOKED WITH OPTIONS NOT COMPATIBLE. SYSTEM ACTION: PROCESS TERMINATES USER RESPONSE: INVOKE THE UTILITY AGAIN FOLLOWING SHOWN SYNTAX. Message ADM0128 ADM0128 LINE LINE IN MODEL FILE FILE CAN NOT BE CUSTOMIZED EXPLANATION: ANXADM HAS CHECKED THAT THE MENTIONED LINE IN THIS FILE HAS A DIFFERENT SYNTAX FROM FIELD = VALUE. SYSTEM ACTION: PROCESS TERMINATES USER RESPONSE: CHANGE OR CORRECT MODEL FILE BEFORE INVOKING THE UTILITY AGAIN. Message ADM0129 ADM0129 ERROR WHILE SUBSTITUTING DEFINITIONS. EXPLANATION: ANXADM HAS CHECKED SOME LINES SPECIFYING VARIABLES WITH WRONG SYNTAX. REMIND THAT VARIABLE VAR MUST BE WRITTEN <VAR> IN LINES OTHER THAN [DEFINE] LINE. SYSTEM ACTION: PROCESS TERMINATES USER RESPONSE: CORRECT PROFILE BEFORE INVOKING THE UTILITY AGAIN. CHAPTER 9. MESSAGES AND CODES 150 INSTALLATION MESSAGES AND CODES CHAPTER 10. INSTALLATION MESSAGES AND CODES New Messages THE FOLLOWING MESSAGES HAVE BEEN ADDED: Message ANX8517 ANX8517 (E) INVALID VALUE value FOR NOSTARTUP KEYWORD. VALID VALUES ARE _____ YES OR NO. EXPLANATION: YOU ENTERED A VALUE OTHER THAN YES OR NO FOR NOSTARTUP. SYSTEM ACTION: PROGRAM TERMINATES. USER RESPONSE: RESUBMIT THE PROGRAM WITH A CORRECT VALUE FOR THE KEYWORD. Message ANX8518 ANX8518 (I) STARTUP.CMD WILL NOT BE UPDATED. VALID VALUES ARE YES OR NO. EXPLANATION: YOU HAVE SPECIFIED NOSTARTUP=YES IN THE RESPONSE FILE, SO STARTUP WILL NOT BE UPDATED, EVEN IF A COPY OF THE UPDATED STARTUP IS IN STARTUP.ANX. SYSTEM ACTION: PROGRAM CONTINUES. USER RESPONSE: NONE Changed Messages THE FOLLOWING MESSAGE HAS BEEN CHANGED: Message ANX8366 CHANGE THE TEXT OF THIS MESSAGE TO READ AS FOLLOWS. (C) Copyright IBM Corp. 1991, 1995 151 INSTALLATION MESSAGES AND CODES ANX8366 (E) NOT ENOUGH DISK SPACE TO INSTALL THE NETVIEW DM/2 DOCUMENTATION. EXPLANATION: NOT ENOUGH SPACE IS AVAILABLE ON THE TARGET DISK TO COPY THE REQUESTED NETVIEW DM/2 DOCUMENTATION. SYSTEM ACTION: PROCESSING TERMINATES NORMALLY AND CONTROL RETURNS TO OS/2. USER RESPONSE: REFER TO THE NETVIEW DM/2 MANUALS TO DETERMINE THE FIXED DISK SPACE REQUIRED TO INSTALL THE SOFTCOPY DOCUMENTATION. CHAPTER 10. INSTALLATION MESSAGES AND CODES 152 CHAPTER 11. CORRECTIONS TO THE MESSAGES AND ERROR RECOVERY GUIDE THIS CHAPTER PROVIDES DETAILS OF CHANGES TO THE MESSAGES AND ERROR RECOVERY GUIDE OTHER THAN CHANGES TO MESSAGES AND CODES, WHICH ARE DESCRIBED IN CHAPTER 9, "MESSAGES AND CODES" ON PAGE 126 AND CHAPTER 10, "INSTALLATION MESSAGES AND CODES" ON PAGE 151. PAGE 304 - Topic 1.3.3.7 - Transmission Controller REMOVE FROM THIS SECTION THE REFERENCES TO THE MAXDISTRETRY AND DISTRETRYINTERVAL KEYWORDS, WHICH CAN NO LONGER BE CUSTOMIZED IN THE IBMNVDM2.INI FILE. REFER TO THE NetView DM/2 Installation and Customization ____________________________________________ Guide (PAGE 343, TOPIC 2.5.3.3) FOR INFORMATION ON THE SETALERT UTILITY, _____ WHICH NOW ALLOWS YOU TO CUSTOMIZE DISTRIBUTION RETRY ATTEMPTS. (C) Copyright IBM Corp. 1991, 1995 153 NVDM/2 GETTING STARTED PART 7. NvDM/2 GETTING STARTED BOOK THIS PART DESCRIBES CHANGES TO MAKE TO THE NVDM/2 GETTING STARTED BOOK TO REFLECT CHANGES AND CORRECTIONS MADE AFTER THE DOCUMENTATION FOR NETVIEW DM/2 VERSION 2.1 WAS SENT FOR PUBLICATION. (C) Copyright IBM Corp. 1991, 1995 154 NVDM/2 GETTING STARTED CHAPTER 12. CORRECTIONS TO THE NvDM/2 GETTING STARTED BOOK PAGE 80 - Using More Functions of NetView DM/2 PAGE 80 - ITEM 4, CLICK ON OPTIONS... IN THE PANEL TO SET THE OBJECT IBM.OS2.MYCHECK.FIX.11.1.US, THE OPTION AUTOMATIC ACCEPTANCE IS SELECTED BUT SHOULD NOT BE. THIS CAUSES THE OBJECT TO BE INSTALLED INRU INSTEAD OF IRU, THUS CAUSING THE SUBSEQUENT REMOVE STEP TO FAIL. (C) Copyright IBM Corp. 1991, 1995 155 INDEX Index +--------------------+ ANX1468 137 | SPECIAL CHARACTERS | ANX1469 137 +--------------------+ ANX1470 137 ANX1471 138 /APPLID 23 ANX1472 138 /CHK 24 ANX1488 130 /SDT 23 ANX2002 128 /SZ 24 ANX2014 131 *.PAN 123, 124 ANX2031 138 *.TXT 123, 124 ANX7241 139 ANX8366 151 ANX8517 151 +---+ ANX8518 151 | A | ANXADM utility 107 +---+ ANXCMLDR.COM 119 ANXI5307 139 ACTIVATE 24 ANXI5587 126 ADD_DEST 25 ANXLUSER.C 120 ADD_DEST command 117 AUTOEXEC.BAT 119 ADDDEST command 66 ANX0088 130 ANX0179 127 +---+ ANX0203 126 | B | ANX0234 127 +---+ ANX0235 127 ANX0236 128 BUILD command 67 ANX0237 128 ANX0253 126 ANX1322 131 +---+ ANX1323 131 | C | ANX1324 131 +---+ ANX1325 133 ANX1331 132 CDM Error Log Window 27 ANX1332 132 CDM Message Log Window 27 ANX1333 132 CDM Request Status Window 28 ANX1334 133 CHANGE_REQ 25 ANX1449 133 Coexistence 22 ANX1454 134 CONFIG command 67 ANX1459 134 COPYCLI.CMD 124 ANX1461 134 COPYSRV.CMD 123, 124 ANX1462 135 corrective service diskettes 2 ANX1463 135 CSD 2, 3 ANX1464 135 what is new 3 ANX1465 136 ANX1466 136 ANX1467 136 (C) Copyright IBM Corp. 1991, 1995 156 INDEX +---+ +---+ | D | | L | +---+ +---+ Database Manager 69 LIST_WS 25 DBMCFG.CMD 69 LISTWS command 67 DBMCFG.PRO 69 DELETE_REQ 25 DeleteCM 113 +---+ DeleteFS 113 | M | DeleteTR 113 +---+ DeleteWS 113 distribution retry attempts, MESSAGE.DAT 27 customization of 153 Minimal CC client 29 DOS CC client, upgrading 12 Modification file 36 Multiserver network 17 +---+ | E | +---+ +---+ | N | +---+ error messages, new 129 NetView DM/2 TSR 119 NOSTARTUP 113 +---+ NVDMBDSK command 105 | F | NVDMCDSK.CMD 123, 124 +---+ NVDMCLT.EXE 124 NVDMCOPY, options 119 File Only, upgrading 12 NVDMCOPY.EXE 123, 124 NVDMDCPY.EXE 124 NVDMDOC.EXE 123, 124 +---+ NVDMDTCT.EXE 123, 124 | H | NVDMDTTR.EXE 123, 124 +---+ NVDMENV.EXE 123, 124 NVDMIDFO.EXE 124 Hardware requirements 18, 114 NVDMIDOS 119 HOLD_REQ 25 NVDMIDOS.EXE 124 NVDMINST.EXE 123, 124 NVDMPMC.EXE 124 +---+ NVDMPMS.EXE 123, 124 | I | NVDMRDSK 29 +---+ NVDMREC.EXE 123, 124 NVDMUFM, enhancements 46 IgnoreRC 112 NVDMUNIN.EXE 123, 124 installation history, deleting 66 NVDMUPO 36 Installation, Quick Help 14 installed objects, listing 66 Installing CID software 70 Interconnections 17 Index 157 INDEX +---+ SQLENSEG 69 | O | Startup diskette 29 +---+ support v System files, modification 36 OS/2 V1.3EE 22 +---+ +---+ | T | | P | +---+ +---+ TCP/IP in pristine environment 70 PostProcessingParam 112 To install the fix on the CC PostProcessingProgram 112 client 155 PreProcessingParam 112 Track History Option 23 PreProcessingProgram 112 +---+ +---+ | U | | Q | +---+ +---+ Unique File Management 46 QUERY_REQ 25 QUERYREP command 68 Quick Help, manuals 14 +---+ | W | +---+ +---+ | R | Workstations 17 +---+ README.TXT introduction v RELEASE_REQ 25 Remote administrator, limitations 17 Remote administrator, support 17 REXX 22 RGN.REN 25 +---+ | S | +---+ Scenarios 68, 70 service support v Software Prerequisites 22 Software requirements 17, 114 Software requirements, Summary 17, 114 Index 158