<![CDATA[
Copyright (c) IBM Corporation 1991 - 1997
All rights reserved
NetView Distribution Manager/2
Version 2.1
Documentation Update
FixPak
XREFP03
March 26, 1997
CONTENTS
CONTENTS
ABOUT THIS FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . IV
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
IBM Service Support . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Additional Support . . . . . . . . . . . . . . . . . . . . . . . . . . iv
-----------------------------------------------------------------------------
PART 1. FIXPAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
CHAPTER 1. THE NETVIEW DM/2 FIXPAK . . . . . . . . . . . . . . . . . . . 2
What is New in this FixPak . . . . . . . . . . . . . . . . . . . . . . . 3
Maintenance Level Serviced by This FixPak . . . . . . . . . . . . . . . 12
Preparing NetView DM/2 for the FixPak . . . . . . . . . . . . . . . . . 12
Methods to install the NetView DM/2 V2.1 FixPak . . . . . . . . . . . 13
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring The CC Server . . . . . . . . . . . . . . . . . . . . . . . 18
-----------------------------------------------------------------------------
PART 2. CDM USER'S GUIDE . . . . . . . . . . . . . . . . . . . . . . . 20
CHAPTER 2. CDM USER'S GUIDE AMENDMENTS TO SH19-5048-02 . . . . . . . . 21
NVDMUPO and NVDMUPFS syntax command . . . . . . . . . . . . . . . . . . 21
NVDMUPO and NVDMUPFS syntax command . . . . . . . . . . . . . . . . . . 21
INITIATE syntax command . . . . . . . . . . . . . . . . . . . . . . . . 21
INSTALL syntax command . . . . . . . . . . . . . . . . . . . . . . . . 22
ADD_DEST syntax command . . . . . . . . . . . . . . . . . . . . . . . . 22
Using CDM Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
NVDMBDSK and NVDMRDSK . . . . . . . . . . . . . . . . . . . . . . . . . 22
CDM BUILD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
-----------------------------------------------------------------------------
PART 3. LDU USER'S GUIDE . . . . . . . . . . . . . . . . . . . . . . . 24
CHAPTER 3. LDU USER'S GUIDE, AMENDMENTS TO SH19-5049-02 . . . . . . . 25
Using Mapping File . . . . . . . . . . . . . . . . . . . . . . . . . . 25
-----------------------------------------------------------------------------
PART 4. INSTALLATION AND CUSTOMIZATION GUIDE . . . . . . . . . . . . . 26
CHAPTER 4. INSTALLATION & CUSTOMIZATION GUIDE, AMENDMENTS TO
SH19-6915-05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
NVDMIDOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . 27
Customizing for the Disposition Parameter . . . . . . . . . . . . . . . 27
Message Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Error Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Customizing a Workstation for NetView DM/2 . . . . . . . . . . . . . . 29
-----------------------------------------------------------------------------
PART 5. MESSAGES AND ERROR RECOVERY GUIDE . . . . . . . . . . . . . . 31
CHAPTER 5. MESSAGES AND CODES, AMENDMENTS TO SH19-6924-05 . . . . . . 32
(C) Copyright IBM Corp. 1991, 1997 ii
CONTENTS
Changed Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
New Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
CONTENTS iii
ABOUT THIS FILE
ABOUT THIS FILE
Introduction
This file (README.TXT) tells you how to install the FixPak and informs which
fixes, see section "What is new in this FixPak" of this text, are made
available with this FixPak along with service TIPS.
Moreover, this README.TXT informs some changes to the NetView DM/2 V2.1
product manuals.
IBM Service Support
Please contact the local IBM Service Support Center before installing this
FixPak 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 596
Extension 62824
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, 1997 iv
FIXPAK
PART 1. FixPak
This FixPak set improves the NetView DM/2 V2.1 reliability and functionality
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, 1997 1
FIXPAK
CHAPTER 1. THE NETVIEW DM/2 FixPak
The NetView Distribution Manager/2 Version 2.1 FixPak follows the rules that
applies to those OS/2 related. In fact, the FixPak for NetView DM/2 Version
2.1 are built using the same Corrective Service Facility (also called
FIXTOOL) that OS/2 uses to build its own FixPak. Thus, each NetView
Distribution Manager/2 Version 2.1 FixPak is composed by a set of the
diskettes that contain just the product fixes; to implement a FixPak a couple
of diskettes, called Kickers, are needed; these come along with FixPak and
are different from others related to products different from NetView
Distribution Manager/2 Version 2.1 (i.e. OS/2 Kicker diskettes are not valis
for NetView DM/2).
The NetView Distribution Manager/2 Version 2.1 FixPak allows to apply related
product maintenance either to product images or fully configured product
installation.
However, we recommend as, faster method, to apply FixPak on top existing
product images and from these refresh both CC Server and CC Client
installations.
This method combines and takes advantage from both CID methodology and
Software Distribution capability of your NetView DM/2 V2.1 .
In fact, you can apply the FixPak on NetView DM/2 product images stored at
your Preparation Site and from here, to distribute and to install these to
the remote CC Servers of your network.
Once distributed the upgraded product images to all CC Servers, you could
reinstall, by unattending the targets, CC Servers (first) and CC Clients from
these via an External Install of Execution of respectively NVDMINST and
NVDMCLT.
The NetView Distribution Manager/2 Version 2.1 FixPak implementation will
results as:
o upgrading of the product files
o upgrading of the related SYSLEVELs
(C) Copyright IBM Corp. 1991, 1997 2
FIXPAK
What is New in this FixPak
This FixPak, XREFP03, distributes some product fixes as referenced in the
FIXES.TXT file located in the first FixPak diskette, labelled CC Server, RA &
OS/2 CC Client APAR FIXES; it cumulates fixes distributed with previous
FixPaks (XREFP01 and XREFP02).
+--- LIMITATIONS -----------------------------------------------------------+
| |
| This FixPak applies to NetView DM/2 Version 2.1 product images and fully |
| configured installation on OS/2 platform. So, DOS CC Client and LDU |
| Receiver MUST be upgraded reinstalling the product from upgraded product |
| images. |
| |
+---------------------------------------------------------------------------+
+--- CURRENT CONTENT -------------------------------------------------------+
| |
| The following RETAIN APAR fixes are distributed starting with FixPak |
| XREFP03 |
| |
+---------------------------------------------------------------------------+
PJ21326
CDM SEND FAILS BECAUSE NETVIEW DM/2 DOES NOT SUPPORT LATIN II
CODEPAGE
PJ22107
MESSAGE ANX0310, ENTRY ALREADY EXISTS IN CATALOG
PJ22187
NVDMUPO.EXE - ADDING DUPLICATE ENTRIES IN CONFIG.SYS
PJ22197
INITIATE PROCEDURE ENDED WITH RC=8 SENSE084B0000
PJ22267
RETURN CODE 37 ON CDM DELETIT
PJ22290
ANXSAQ4S.EXE NOT FREEING ALLOCATED MEMORY
PJ22306
NVDM/2 WILL NOW RECOGNIZE 0X0400 WINDOWS PROTECTED MODE PROGRAM
PROCESSED IN CF FOR WINDOWS APPS CID-ENABLED W/ SFT. INSTALLER/
CHAPTER 1. THE NETVIEW DM/2 FixPak 3
FIXPAK
PJ22361
SCHEDULED ACTIVATE REQUEST FOR A GROUP OF CC CLIENTS IS BEING
INCORRECTLY PROCESSED. SOME ACTIVATES OCCUR IMMEDIATELY
PJ22425
REQUIREMENT FOR DOUBLE QUOTES AROUND PARAMETERS IN NVDM2 PROFIL
PJ22606
IMPROVING MESSAGING WHILE EXECUTING TRANSMISSION CONTROLLER QUEUE
RECOVERY
PJ22687
WHEN TRYING TO INSTALL PACKAGES FROM CDM DIALOGS ON THE RA WORK
STATION, REMOTE TARGETS DOES NOT APPEAR AS AVAILABLE TARGETS.
PJ22774
NVDM/2 AGENT TRAPS IN CASE OF CORRUPTED PACKAGES
PJ22942
IMPROVEMENT MESSAGING WHEN CDM ACCEPT FAILS BECAUSE *.REM FIL HAS
BEEN DELETED EVEN IF ACCIDENTALLY
PJ23115
SYS3175 IN ANVCMSRV.EXE WHEN SENDING AN EMPTY FILE
PJ23142
RETRIEVE VIA REMOTE ADMIN OF NVDM/2 XR0004 IN ORDER TO RETRIEVE
MICROCODE TO A 3174 GETS ANXE5211.
PJ23144
INTERMITTANT SYS3175 TRAP IN ANXCMCLC.EXE WHEN INSTALL REXX
INSTALLATION TO CLIENTS. ANX0189 'SYSTEM ABEND 2' IN LOG
PJ23181
TRANSMISSION CONTROLLER HANG DURING STRESS CONDITION HANDLING MANY
INSTALL REQUESTS
PJ23224
APAR TO TRACK NVDM2 WORKAROUND OF NETBIOS FIND_NAME BUG
PJ23423
PRISTINE INSTALLATION ABORTS
CHAPTER 1. THE NETVIEW DM/2 FixPak 4
FIXPAK
PJ23603
NETVIEW DM/2 V2.1 CC SERVER INSTALLATION HANGS (BY USING NVDMINST
AFTER HAS ACCESSED THE STARTUP.CMD FILE
PJ23639
INCORRECT OUTPUT OF COMMAND CDM LIST /WS
PJ23664
NVDMBDSK/NVDMRDSK ENHANCEMENT'S TO SUPPORT 2+ BOOT DISKETTES
INTRODUCED WITH LATEST OS/2 WARP V4 CODED MERLIN
PJ23710
ANX0030 IN CC CLIENT DURING A NVDM/2 DISTRIBUTION.
PJ23714
LDR0017 NO NETBIOS SESSIONS AVAILABLE WHEN LDU CLIENT TRIES TO
CONNECT TO THEIR SERVER
PJ23722
ANX0166 AT CDM SEND IF CHG FILE BUILT FROM A: DRIVE
PJ23723
AFTER AN ACTIVATE FUNCTION INVALID ATTRIB CONFIG.NDM
PJ23878
GET MESSAGE ANX1247 INVOKING CDM BUILD USING CDROM
PJ23934
TRANSMISSION CONTROLLER HANG DURING STRESS CONDITION HANDLING MANY
INSTALL REQUESTS
PJ23936
REMOTE SEND TO NVDM/2 CC SVR WITH GREATER THAN > 4GIG FREE SPAC
RESULTS IN SENSE CODE 084C0002 DUE TO BAD CALCULATION
PJ24019
FILE GETS CORRUPTED WHEN SEND FROM NDM/MVS TO NVDM/2
PJ24049
NVDM/2 DELETES STATEMENTS WHICH BEGIN WITH START FROM THE STAR
UP.CMD
CHAPTER 1. THE NETVIEW DM/2 FixPak 5
FIXPAK
PJ24188
MSGANX0082 IN NDM/2 AND NDM0856E IN NDM DURING HAVY LOAD
PJ24229
MESSAGE AND ERROR LOGS VIEWED THROUGH THE DIALOG DO NOT HAVE A
TIMESTAMP - ONLY DISPLAY (AM) OR (PM) AND DATE OF ENTRY
PJ24272
NVDM/6K DETECTS A FORMAT ERROT FOR DATETIME INSTALL
PJ24371
TRAP MAY OCCUR DURING AN ACTIVATE AT IPL TIME
PJ24373
DISK CAMERA, ABNORMAL END MONITORING *.INI WITH LINE > 255
PJ24374
DISK CAMERA SHOULD INCREASE MAXIMUM INI FILE SIZE TO MONITOR
PJ24375
AGENT DOS FAILS ACTIVATE IF THERE IS NO FLOPPY DRIVE
PJ24376
NVDMUNIN FAILS TO UNINSTALL OS/2 CC CLIENT BECAUSE OF DB RELATED
DLLS NOT FOUND
PJ24377
NVDMDTCT UTILITY DOESN'T RUN IF DB WAS NOT STARTED
PJ24378
INCORRECT CHARACTERS ACCEPTED WHEN ADDING CLIENTS
PJ24379
STORED NAME MISSING IN THE REPORT SENT TO AS/400
PJ24380
ANXIFCOM.IFS IS NOT INSTALLED ON LAN MANAGER 2.0
PJ24381
ANXSNADS TRAPS DURING STARTUP IF LMU2 IS STARTING TOO
CHAPTER 1. THE NETVIEW DM/2 FixPak 6
FIXPAK
PJ24382
TRANSMISSION CONTROLLER (TC) ERROR INIT MESSAGES EVEN IF THE TC IS
NORMALLY STARTED
PJ24410
TRAP ISSUING A REMOTE INITIATE WITH PARMS WHEN RUNNING
COMMUNICATIONS SERVER V4.X AND NETVIEW DM/2 V2.1
+--- CUMULATED FIXES -------------------------------------------------------+
| |
| This FixPak cumulates the following RETAIN APARs from |
| previous released FixPaks |
| |
+---------------------------------------------------------------------------+
II08812
NETVIEW DM/2 V2.1 DOES NOT INSTALL ON TOP DB2&SLR.2
PJ19581
NETVIEW DM/2 V2.1 LDU MISCELLANEOUS FIXES 1 OF 1
PJ19582
NETVIEW DM/2 V2.1 CDM MISCELLANEOUS FIXES 1 OF 2
PJ19583
NETVIEW DM/2 V2.1 CDM MISCELLANEOUS FIXES 2 OF 2
PJ19934
CDM LIST_REQ EXECUTION DATE FIELD IS EMPTY
PJ19981
REMOTE DELETE REQUEST CAUSES A TRAP ON A NVDM2 2.1 CC SERVER
PJ20451
UNATTENDED NVDM/2 INSTALLATION LEAVE \ANX SUBDIR. WITH 3 DLLS:
ANXDBCS.DLL NDMNLS.DLL AND ANXACTVF.DLL FOLLOWING INSTALLATION
PJ20512
OS/2 2.11 XR_A091 AND NVDM/2 XR00003 GENEERATES A SYS1811, THE
SOFTWARE DIAGNOSTIC CODE (TRAP NO) IS 0000
PJ20560
CDM DIALOG: ANXE5141 ON THE SECOND INSTALL OF AN OBJECT
CHAPTER 1. THE NETVIEW DM/2 FixPak 7
FIXPAK
PJ20562
CDMD ERROR: "UNABLE TO ALLOCATE VIRTUAL ADDRESS SPACE"
PJ20590
CDM DIALOGS FAILS TO RETRIEVE MESSAGE/ERROR DAT FILES
PJ20658
ANXIDISP VARIABLE FOR NVDM2 2.1 Q3 ENVIRONMENT DOES NOT WORK
PJ20741
NVDM/2 SYNCHRONZIATION PROBLEM BETWEEN 2 DM/2 PROCESSES: DELETE_WS
AND CM_REQUEST WHEN LARGE AMOUNT OF DEFINED CLIENTS
PJ20751
PERFORMANCE PROBLEM IN INSTALL DIALOG FOR "SERVER" ENVIRONMENT
PJ20793
NVDM/2 IS PROVIDING INCORRECT LENGTH ON FILE WITH VARIABLE LENGTH.
PROBLEM IS APPARENT ON A RETRIEVE OPERATION FROM DM/MVS
PJ20829
WHEN USING AN INVALID PARAMETER WITH THE CDM SEND COMMAND, THE RC=0
WHEN IT SHOULD HAVE BEEN 5.
PJ20900
CDM DIALOG DOES NOT REGISTER ERROR/MESSAGE WINDOWS OPENING
PJ20980
ANX1007 MESSAGE IS INCORRECTLY ISSUED DURING THE CDM BUILD COMMAND
PJ21119
ANX0081 WITH ACTIVATE AFTER REM/DEL
PJ21258
ANX0211 ERROR MESSAGE LOGGED AND CC SERVER TERMINATES WHEN INSTALL
IS EXECUTED AT 00:00:00 TIMESTAMP
PJ21269
DEFER POPUP NOT DISPLAYED BY ACTIVATE WITH FORCE=NO
CHAPTER 1. THE NETVIEW DM/2 FixPak 8
FIXPAK
PJ21270
NVDM/2 V2.1 ENHANCEMENT TO SUPPORT GREEK CODEPAGES/COUNTRY CODE
PJ21271
MSG ANX1470: "CANNOT OPEN ANXCLCK FILE" AT CDM START
PJ21272
TRAP IN ANXBASE.DLL ISSUING CDM START OPERATION
PJ21275
NVDM/2 V2.1 ENHANCEMENT TO INCREASE SIZE OF THE MAP FILE USED BY
LDU DISTRIBUTOR COMPONENT.
PJ21305
ANXCMLDR STATEMENT CANNOT BE MODIFIED FOR ANY REASON.
PJ21350
BOOT DISKETTE CREATED WITH MS DOS ARE NOT RECOGNIZED BY NVDMBDSK
PJ21471
ANX0081 ERROR WITH ACTIVATE AFTER REMOVE OF OBJECT
PJ21476
NVDMLZW / LZW DECOMPRESSION FAILURE CAUSED BY A CORRUPTED FILE FROM
A RESOURCE LOADED INTO DM/MVS WITH A SPECIFIC LENGTH
PJ21577
DOS CC CLIENT AGENT ENDS DUE TO MEMORY LACK WITHOUT POINTING OUT
THIS LACKNESS.
PJ21642
WRONG OPTION REFERENCES FOR SEND SWITCH IN INITIATE/INSTALL
PJ21711
THE AIX OPERATING SYSTEM IS NOT MENTIONED IN DOCUMENTATION REFE
ENCING THE CDM ADD_DEST COMMAND
PJ21719
DECOMPRESSION FAILURE FOR A ZIPPED FILE
CHAPTER 1. THE NETVIEW DM/2 FixPak 9
FIXPAK
PJ21812
CDM DIALOGS: RUNTIME ERROR IN "OPEN WORKSTATION" DIALOG,
"OBJECTS..." FUNCTION
PJ21860
NVDM/2 V2.1 ENHANCEMENT, TO MONITOR WIN.INI, PROGRAM.INI AND
SYSTEM.INI LOCATED OUT OF WINOS2 SUBDIRECTORY.
PJ21861
DISKCAMERA FOR OS/2 FAILS TO MONITOR WIN.INI BECAUSE CUSTOMER USED
A CUSTOMIZED NAME FOR WINOS2 SUBDIRECTORY AS OS/2 ALLOWS
PJ21862
SWAPPER.DAT FILE GROWS USING CDM RELEASE
PJ21864
ALIGNMENT WITH NEW CID ARCHITECTURE ENABLEMENT SPECIFICATION
PJ21865
CLIENT IN 'RUNNING' STATUS FOREVER WHEN EXECUTING AN INSTALL
PJ21866
ERROR LOG NOT MEANINGFUL FOR PACK/UNPACK FAILURE
PJ21867
WRONG MESSAGE, ANX0250, ISSUED WHEN A FILE IS DETECTED LOCKED
DURING AN INSTALL
PJ21868
NVDMUPO DOES NOT MANAGE CORRECTLY COMMA IN AFTER ATTRIBUTE
PJ21869
TRAP IN ANXCMSRV AFTER INSTALLING A CHANGE FILE
PJ21870
A TOO MANY SENDING REQUEST PENDING MESSAGE REPEATED INDEFINETLY IN
THE MESSAGE.DAT
PJ21871
DOS CC CLIENT FAILS TO EXECUTE BATCH FILES IN PRISTINE SCENARIO
CHAPTER 1. THE NETVIEW DM/2 FixPak 10
FIXPAK
PJ21872
ACTIVATE FAILS IF INSTALL IN SERVICE AREA IS WITH /C PARAMETER
PJ21873
DOS CC CLIENT SHOULD BE ENHANCED TO SUPPORT DRIVELETTERS KEYWORD
INTO THE IBMNVDM.INI FILE
PJ21874
NVDMINST /CO FAILS DUE TO MISSING *.BND AFTER HAVING REINSTALLED
THE PRODUCT FROM PRODUCT IMAGES
PJ21875
AN FST FILE BELONGING TO NO ACTIVE TRANSMISSION IS FOUND IN THE
FSDATA SUBDIRECTORY
PJ21876
SENSE CODE 100B 000C DETECTED FROM NVDM/6000 WHEN RETRIEVING A
RESOURCE.
PJ21877
DOS CC CLIENT FAILS TO BUILD MINIMAL CONFIGURATION FILES IF ANY
STATEMENT OF THE ACTIVE ONES IS GREATER THAN 128 CHARACTERS.
PJ21878
REQUIREMENT TO UPDATE RULE FILE .BKC TO REFER IBM DOS V7
PJ21879
NVDMUPO DOES NOT REPLACE ALL OCCURRENCES OF TARGETDIR MACRO
PJ21881
EXCESSIVE ERROR.DAT GROWS DUE TO REPEATED ANXACCDO MESSAGES
PJ21882
REQUIREMENT TO CUSTOMIZE MAXIMUM LOG FILE SIZES
CHAPTER 1. THE NETVIEW DM/2 FixPak 11
FIXPAK
Maintenance Level Serviced by This FixPak
The FixPak requires, as minimum, NetView DM/2 at maintenance level XR00002_
(CSD XR20466 or June '95 product refresh); it applies on top any previous
released FixPaks (XREFP01 or XREFP02).
Once implemented, any product full configuration or images, selected at
FixPak installation time, will be upgraded at the XR00005_ level.
Preparing NetView DM/2 for the FixPak
If planning to implement FixPak on a fully configured installation by running
CSF GUI (i.e. SERVICE.EXE from an OS/2 prompt), please make sure that CDM has
been stopped and no CDM Dialogs are active before to apply the service.
CHAPTER 1. THE NETVIEW DM/2 FixPak 12
FIXPAK
Methods to install the NetView DM/2 V2.1 FixPak
+--- WARNING -----------------------------------------------------+
| |
| When servicing a NetView DM/2 workstation configured as |
| Remote Administrator, PLEASE BE SURE to apply any |
| related maintenance simultaneously to either CC Server |
| (SYSLEVEL.NDM) and Remote Administrator |
| (SYSLEVEL.FPF). |
| |
| Service reference: RETAIN INFO APAR II08220 |
| |
+-----------------------------------------------------------------+
+--- 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 previous maintenance level and "new" means |
| this FixPak. |
| |
+-----------------------------------------------------------------+
ATTENDED INSTALLATION OF THE NETVIEW DM/2 FIXPAK
The attended methods for installing the NetView DM/2 FixPak uses
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.
The FixPak 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 FIXPAK INSTALLATION VIA REBOOT
This method applies the FixPak to the installed version of
NetView DM/2 Version 2.1 and product images as well.
CHAPTER 1. THE NETVIEW DM/2 FixPak 13
FIXPAK
If you want to install the FixPak using the standard defaults,
thus the default response file, proceed as follows:
1. Insert the NetView DM/2 kicker diskette #1 in the A: drive.
2. Restart the workstation.
NOTE: The FixPak is implemented according to response file
directives; if no changes to the default response file,
FixPak is applied to all NetView DM/2 product
installations and images that are detected to be
serviced. A log file, called SERVICE.LOG, is created or
appended according to the :LOGFILE tag specified into
RESPONSE.FIL file located on the second NetView DM/2
Version 2.1 kicker diskette: the default log path is
C:\OS2\INSTALL . If the default path is unavailable or
the User wishes to log differently, edit the above
mentioned RESPONSE.FIL file and override the default
path/filename with your favorite one.
NOTE: Refer to REDBOOK GG24-3780 (Remote Installation and
Maintenance) for more information on how to create your own
response file.
NETVIEW DM/2 IMAGE ON FIXED DISK - DEFAULT FIXPAK INSTALLATION BY
USING RESPONSE FILE (FSERVICE).
This method applies the FixPak to the installed version and also
to a diskette image of NetView DM/2 V2.1 by invoking FSERVICE
along with response file.
A standard response file (called RESPONSE.FIL) is provided, on
the diskette #2 of the NetView DM/2 kicker ones, that the User
may customize.
NOTE: Refer to REDBOOK GG24-3780 (Remote Installation and
Maintenance) for more information on how to create your own
response file.
To apply FixPak using standard response file, proceed as
follows:
1. Insert the NetView DM/2 kicker diskette #2 in the A: drive.
2. Enter A:\FSERVICE.
NOTE: The FixPak is implemented according to response file
directives; if no changes to the default response file,
FixPak is applied to all NetView DM/2 product
installations and images that are detected to be
CHAPTER 1. THE NETVIEW DM/2 FixPak 14
FIXPAK
serviced. A log file, called SERVICE.LOG, is created or
appended according to the :LOGFILE tag specified into
RESPONSE.FIL file located on the second NetView DM/2
Version 2.1 kicker diskette: the default log path is
C:\OS2\INSTALL . If the default path is unavailable or
the User wishes to log differently, edit the above
mentioned RESPONSE.FIL file and override the default
path/filename with your favorite one.
NOTE: Refer to REDBOOK GG24-3780 (Remote Installation and
Maintenance) for more information on how to create your own
response file.
NETVIEW DM/2 IMAGE ON FIXED DISK - FIXPAK INSTALLATION DRIVEN BY A
DIALOG (GUI) INTERFACE (SERVICE)
This method applies the FixPak to the installed version and also
to a diskette image of NetView DM/2 V2.1 from the command line
by using a dialog.
1. Insert the NetView DM/2 kicker diskette #1 in the A: drive.
2. Enter A:\SERVICE. This displays a window (called
"Serviceable Products") 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 and press SERVICE button.
NOTE: All eligible products are initially selected.
4. Pressing SERVICE button will open a window called
"Corrective Service Facility : Service" : press OK button to
start service.
NOTE: You WILL NOT be able to terminate the service process
after it has been started.
5. At the end of a successful implementation of the FixPak, a
small window will inform of the success of the task : press
OK button to continue.
6. At this time, a small window will ask if you to re-display
the products eligible to service: press YES button if you
want to service some product previously skipped or NO button
to end.
7. To exit from Corrective Service Facility press CANCEL button
from the window called "Serviceable Products".
A service log is provided for installation verification:
<bootdrive>:\OS2\INSTALL\SERVICE.LOG,
where <bootdrive> is the partition from which you IPLed.
CHAPTER 1. THE NETVIEW DM/2 FixPak 15
FIXPAK
Subsequent installs will be appended to the service log.
UNATTENDED INSTALLATION OF THE NETVIEW DM/2 FIXPAK
The unattended method of installing the NetView DM/2 FixPak
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
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 FixPak.
The recommended process for the unattended installation of a
NetView DM/2 FixPak 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 FixPak 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 FSERVICE or SERVICE).
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."
CHAPTER 1. THE NETVIEW DM/2 FixPak 16
FIXPAK
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 FixPak 17
FIXPAK
Limitations
1. OS/2 Versions 1.2 and 1.3 are not supported
2. PC based on 286 processor are not supported
3. OS/2 Version 2.x or later are serviceable either from the command line
(SERVICE, dialog, or FSERVICE, response file driven) or by restarting
with the first NetView DM/2 Version 2.1 kicker diskette,
4. If a machine has installed the 386 HPFS file system with LOCAL SECURITY
feature installed, the service is allowed only by command line.
Moreover, before starting the FixPak implementation with the A:\SERVICE
command, it is necessary to log on to the server with an administrator's
privilege level.
Configuring The CC Server
If you have installed this FixPak 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 FixPak 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 ....
NOTE:
CHAPTER 1. THE NETVIEW DM/2 FixPak 18
FIXPAK
TO RECOVER FROM THIS FAILING EVENT RUN NVDMINST /CO FROM THE
<PRODUCT_ROOT_DIR>\BIN PATH.
CHAPTER 1. THE NETVIEW DM/2 FixPak 19
CDM USER'S GUIDE
PART 2. 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, 1997 20
CDM USER'S GUIDE
CHAPTER 2. CDM USER'S GUIDE AMENDMENTS TO SH19-5048-02
NVDMUPO and NVDMUPFS syntax command
The OS/2 Camera has been enhanced in order to manage value1, of the AFTER:
attribute, that contain a comma. This enhancement has been reached
introducing a new grammatical for value1 of the AFTER: attribute in order to
manage comma; the syntax remain unchanged as follows:
verb(attribute:value1,value2) The new grammatical to have correctly handled
comma in value1 is to substitute comma with '&comma' (without quotes) key.
For instance, assuming to have a statement such as:
AddStatement(AFTER:[A,B],<SOFTFONT1=$(TargetDir)PSFONTS>)
the above statement should be changed as follows:
AddStatement(AFTER:<[A&commaB]>,<SOFTFONT1=$(TargetDir)PSFONTS>)
NVDMUPO and NVDMUPFS syntax command
The DeleteFile statement, to work properly, MUST be placed after a statement
[FS].
Example:
[FS]
DeleteFile(FS,C:\TMP\STARTUP.CMD)
NOTE:
any Modification File Statement works only under the specified statement
referred in the section "Attributes and Statements Relationships"
INITIATE syntax command
The INITIATE syntax command incorrectly informs that the parameter /SEND may
be followed by options while in reality it does not.
(C) Copyright IBM Corp. 1991, 1997 21
CDM USER'S GUIDE
INSTALL syntax command
The INSTALL syntax command incorrectly informs that the parameter /SEND may
be followed by options while in reality it does not.
ADD_DEST syntax command
The default value (OS/2) for /OS applies both to OS/2 and AIX
Using CDM Dialogs
The radio button OS/2, on the Figure 99 "The New Node Window", for Operating
System applies both to OS/2 and AIX
NVDMBDSK and NVDMRDSK
Starting from OS/2 Warp Version 4, the boot diskettes to IPL change from 2 to
3 therefore NVDMBDSK/NVDMRDSK fails to produce Pristine diskettes set because
designed to handle 2 boot diskettes. In particular, the NVDMBDSK/NVDMRDSK
fail because of CONFIG.SYS is not present on the last diskette of the new OS
boot set, that to which are made the changes to support NetView DM/2
Pristine. The CONFIG.SYS is present on the diskette 1. The NVDMBDSK utility
has been changed to prompt a pop-up message to request User to insert boot
diskette with CONFIG.SYS before to continue the process. Also, the NVDMRDSK
has been changed to pop up a message to ask for diskette with CONFIG.SYS
inserted into the drive when needed to update CONFIG.SYS file. The new
sequence to create OS/2 Pristine boot diskettes is:
1. create a new OS/2 V4 (Merlin) boot diskettes set by using SEDISK and OS/2
V4 Merlin CD-ROM
2. leave the diskette 2 into driver and then run THINLAPS to add network
drivers on the diskette
3. remove diskette 2 and insert diskette 1 when requested by THINLAPS
program to configure CONFIG.SYS
4. insert diskette 2 into driver and then run the new NVDMBDSK utility to
add minimal NetView DM/2 V2.1 CC Client.
5. remove diskette 2 and insert diskette 1 when requested by NVDMBDSK
program to configure CONFIG.SYS
CHAPTER 2. CDM USER'S GUIDE AMENDMENTS TO SH19-5048-02 22
CDM USER'S GUIDE
+--- NOTE ------------------------------------------------------------------+
| |
| The message asking for diskette with CONFIG.SYS file has been introduced |
| for DOS Pristine boot diskettes too in order to be ready for future |
| enhancements. |
| |
+---------------------------------------------------------------------------+
CDM BUILD
When product installation programs require parameters with quotation marks,
NetView Distribution Manager/2 requires a second set of quotation marks
around the entire parameters.
TargetDir = C:½
Section Catalog
Begin
ObjectType = SOFTWARE
GlobalName = DB2V211.INSTSU.WRG8085.ALL.REF.0
Description = "IBM DB2 f r OS/2 Einzelplatz-System "
End
Section Install
Begin
Program = $(SourceDir)½INSTALL.EXE
Parms = /R:$(ResponseFile) /X /A:i "/P:"IBM DB2 for OS/2 (Einzelplatz-System)"" /S:$(SourceDir)
/L1:$(LogFile1) /L2:$(LogFile2)
SourceDir = SA:½CID½IMG½DB2V211
ResponseFile = SA:½CID½RSP½IMG½DB2V211½$(WorkStatName).SU
LogFile1 = SA:½CID½LOG½IMG½DB2V211½$(WorkStatName).SU1
LogFile2 = SA:½CID½LOG½IMG½DB2V211½$(WorkStatName).SU2
End
CHAPTER 2. CDM USER'S GUIDE AMENDMENTS TO SH19-5048-02 23
LDU USER'S GUIDE
PART 3. 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, 1997 24
LDU USER'S GUIDE
CHAPTER 3. LDU USER'S GUIDE, AMENDMENTS TO SH19-5049-02
Using Mapping File
The maximum size, 20KB, for LDU Distributor mapping file has been increased
up to 40KB.
(C) Copyright IBM Corp. 1991, 1997 25
INSTALLATION GUIDE
PART 4. 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, 1997 26
INSTALLATION GUIDE
CHAPTER 4. INSTALLATION & CUSTOMIZATION GUIDE, AMENDMENTS TO SH19-6915-05
NVDMIDOS
The "DriveLetters" keyword is now supported by NVDMIDOS even if the table 17
referring to Response File for NVDMIDOS has not been updated. The new
supported keyword is not mandatory. The possible values range from C to Z.
Configuration Parameters
A new environment variable, SMALLTALKVIRTUALALLOC, has been introduced to
allow User customization of the virtual memory allocated by CDM Dialogs
(SmallTalk based) when started. The new variable is not mandatory. In case
of problems to start CDM Dialog due to not enough virtual memory, add the
following statement in the CONFIG.SYS and reboot the system before to start
CDM Dialogs:
SET SMALLTALKVIRTUALALLOC=<memory size>
WHERE
<memory size> is the amount of memory expressed in MB.
Customizing for the Disposition Parameter
The default disposition, even if the NetView DM/2 V2.1 is connected to a
Focal Point or is APPC connected with other NetView DM/2 V2.1 nodes, is
always KEEP. To change this default, add the following statement in your
CONFIG.SYS file:
SET ANXIDISP=DELETE
NOTE:
The ANXDISP setting is valid only for APPC connected workstation not defined
as CC server.
(C) Copyright IBM Corp. 1991, 1997 27
INSTALLATION GUIDE
Message Log File
The maximum MESSAGE.DAT log size can be defined by adding the following
statement in the CONFIG.SYS:
SET ANXMSGSZ=<number>
WHERE
<number> is the desired size for MESSAGE.DAT expressed in Kbytes.
When the maximum size is reached, the log file is saved in a back up copy and
a new file is created
NOTE:
RECOMMENDED INITIAL VALUE
We recommend to set this variable to 1024 (1Mbyte).
APPLY TO ...
This setting conditions local managing for MESSAGE.DAT file at both
CC Server and CC Client sides.
IT DOES NOT APPLY TO ...
This setting does not condition remote logging for CC Client
MESSAGE.DAT (i.e. MESSAGE.DAT file under CMREQ\<client_name>\LOG
path)
Error Log File
The maximum ERROR.DAT log size can be defined by adding the following
statement in the CONFIG.SYS:
SET ANXERRSZ=<number>
WHERE
<number> is the desired size for ERROR.DAT expressed in Kbytes.
When the maximum size is reached, the log file is saved in a back up copy and
a new file is created
NOTE:
RECOMMENDED INITIAL VALUE
We recommend to set this variable to 1024 (1Mbyte).
CHAPTER 4. INSTALLATION 28 CUSTOMIZATION GUIDSH19-6915-05S 28
INSTALLATION GUIDE
APPLY TO ...
This setting conditions local managing for ERROR.DAT file at both
CC Server and CC Client sides.
IT DOES NOT APPLY TO ...
This setting does not condition remote logging for CC Client
ERROR.DAT (i.e. ERROR.DAT file under CMREQ\<client_name>\LOG path)
Customizing a Workstation for NetView DM/2
FREE UNUSED_SESSION KEY IN .NDF FOR NETVIEW DM/2
When NetView DM/2 establishes a comunication with its remote partners, it
exchanges APPC LU62 Conversation verbs. For what concerning the management
of the sessions all works in the following way. If a NvDM MvS starts a
communication and if it finds that a session with its remote NetView DM/2
partner is not active, it opens the session, then allocate a conversation and
at the end both deallocates the conversation and closes the session. If
NetView DM/2 starts a communication, it only manages APPC conversation verbs
and NOT directly the sessions. So, NetView DM/2 calls APPC ALLOCATE verb to
allocate a conversation, then APPC checks if a session is active, if so, over
this session it allocates the requested conversation, on the contrary firstly
opens the session and then allocate the conversation. At the end of
communication, NetView DM/2 issues APPC DEALLOCATE verb, this APPC verb has
the effect to only deallocate a conversation without closing the session that
has been previously opened via the ALLOCATE verb. This session is idle and
can be used by NetView DM/2 in case it needs to allocate othe conversation.
If customer wishes to close anyway this session, starting from CM2 fixpack
CM2AP111 there is the possibility to set a new key in .NDF file:
FREE_UNUSED_SESSION in DEFINE_LOCAL_CP verb. Hereafter an abstract from
CM2AP111.DOC file:
JR08314: LU62 Sessions remain active even when not needed.
Previous to this APAR, Communications Manager/2 did not free LU62 sessions
even after they were no longer needed. This APAR fix allows one to modify
the Communications Mgr/2 configuration file with a new parameter known as
FREE_UNUSED_SESSIONS. You may invoke this new function as follows:
Determine the name of your communications Manager/2 configuration file. If
you do not know the name, execute the command CMQUERY at OS/2 command prompt
while Communications Manager/2 is running. CMQUERY will return the name of
the active configuration. For this example, assume the name is CMBASE.
From an OS/2 window edit the file CMBASE.NDF, found in the CMLIB directory
(where CMBASE is the name of YOUR Communications Manager/2 configuration
file).
CHAPTER 4. INSTALLATION 29 CUSTOMIZATION GUIDSH19-6915-05S 29
INSTALLATION GUIDE
The CMBASE.NDF file is an ASCII file that is readable. The first section in
this file shows the DEFINE_LOCAL_CP verb and the associated parameters. See
example below:
DEFINE_LOCAL_CP FQ_CP_NAME(USIBMNR.MYCPNAME )
DESCRIPTION(Created on 01-15-93 at 02:31p)
CP_ALIAS(MYCPNAME )
NAU_ADDRESS(INDEPENDENT_LU)
NODE_TYPE(EN)
NODE_ID(X'05D512A0')
NW_FP_SUPPORT(NONE)
HOST_FP_SUPPORT(YES)
HOST_FP_LINK_NAME(HOST0001)
add--------->FREE_UNUSED_SESSIONS(YES)
MAX_COMP_LEVEL(NONE)
MAX_COMP_TOKENS(0)
Notice the 'add------------>' indicator. This shows the new line
that must be added to invoke this new function. Only enter the
FREE_UNUSED_SESSIONS(YES) parameter (add------------> is just to
show you where the parameter is inserted).
After adding the new line parameter, SAVE the change and then perform a
C:\CMVERIFY CMBASE /e This will verify the configuration file change. Upon
successful verification, STOP and RESTART communications Manager/2 to invoke
the new function.
CHAPTER 4. INSTALLATION 30 CUSTOMIZATION GUIDSH19-6915-05S 30
MESSAGES AND ERROR RECOVERY GUIDE
PART 5. 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, 1997 31
MESSAGES AND ERROR RECOVERY GUIDE
CHAPTER 5. MESSAGES AND CODES, AMENDMENTS TO SH19-6924-05
Changed Messages
The following messages have been changed.
Message ANX1773
ANX1773 (E) CANNOT RETRIEVE CLIENT PARAMETERS.
EXPLANATION: The program cannot retrieve the client parameters
from the ANXCMLDR configuration line, in the autoexec.bat
system file. The following is an example of ANXCMLDR
configuration line:
ANXCMLDR.COM /S=LUCAS /R=LUCAC /T=300,10 /U=ACCEPT /A=0
SYSTEM ACTION: The program is terminated and the product is
not installed.
USER RESPONSE: Check if the ANXCMLDR line in the autoexec.bat
is not existing or is not correct.
Message ANX0649
ANX0649 (E) THE TRANSMISSION CONTROLLER RECEIVE TRANSACTION PROGRAM IS NOT
DEFINED IN THE COMMUNICATIONS MANAGER.
EXPLANATION: The transaction program that the Transmission
Controller uses to receive transmissions from adjacent nodes is
not defined in the configuration of Communications Manager.
This transaction program must be defined before NetView DM/2
can successfully communicate with partner nodes.
SYSTEM ACTION: The Transmission Controller terminates.
USER RESPONSE: Define the receive transaction program (TP name
= X'21',008) in Communications Manager. Check the NetView DM/2
Installation and Customization Guide for information on
configuring Communications Manager for NetView DM/2.
(C) Copyright IBM Corp. 1991, 1997 32
MESSAGES AND ERROR RECOVERY GUIDE
New Messages
The following messages have been added.
Message ANX0312
ANX0312 (W) BUILD FAILED. TOO MANY FILES TO BE PACKED.
EXPLANATION: The User exceeded the maximum number (10000) of
names of files and directories that can be managed by the Build
function.
SYSTEM ACTION: The BUILD task is aborted and processing
continues.
USER RESPONSE: Split the Change File in more ones to be within
the maximum number.
CHAPTER 5. MESSAGES AND CODES, AMENDMENTS TO SH19-6924-05 33
INDEX
Index
+---+ +---+
| A | | I |
+---+ +---+
ANX0312 33 INITIATE syntax command 21
ANX0649 32 INSTALL syntax command 22
ANX1773 32
+---+
+---+ | M |
| C | +---+
+---+
Message Log File 28
Change File Profile Structure 23 Modification File Statements 21
Configuration Paramaters 27
Configuring Communications
Manager/2 29 +---+
refid=CM/2 FIX CM2AP111 29 | N |
Creating Startup Diskettes for OS/2 +---+
.... 22
Customizing for the Disposition NVDMIDOS 27
Parameter 27
+---+
+---+ | P |
| D | +---+
+---+
Parameters 22
Defining a New Remote
Destination 22
+---+
| R |
+---+ +---+
| E |
+---+ README.TXT
introduction iv
Error Log File 28
+---+
+---+ | S |
| F | +---+
+---+
service support iv
FixPak 2, 3 support iv
what is new 3
(C) Copyright IBM Corp. 1991, 1997 34
INDEX
+---+
| U |
+---+
Using Mapping File 25
Index 35
]]>