Tivoli
Software Distribution, Version 3.1.5
README
CSD XR22539 for Windows, Version 3.1.5
PTF U481091 for AIX®,
Version 3.1.5
March, 2002
Coexistence
with Other Tivoli Software Distribution Products
2 Tivoli Software
Distribution CSD XR22539 for Windows
Windows
Support and Limitations
Windows 2000 Advanced Server Support
Limitations on Windows NT 4.0 and Windows 95
Dynamic Change Files Preparation not Available on
Windows Administration GUI
Using Message Log via Administration GUI on Windows
Using the Administration GUI on Windows
Using Directory and File Names with Embedded Spaces
on Windows
A NON-ROOT USer CAn ISSUE NVDM START NVDM STOP AND
NVDM RESET
Installation
Scenario for Windows Platforms. 4
Unattended Upgrade of Tivoli Software Distribution Server
or Client to Version 3.1.5
APARs
Fixed in Tivoli Software Distribution, Version 3.1.5 for Windows
3 Tivoli Software
Distribution PTF U481091 for AIX
Installation
Scenarios for AIX
Scenario Two: Upgrade Tivoli Software Distribution
for AIX Server, Version 3.1.5
This file (README.TXT) provides Tivoli Software Distribution, Version 3.1.5 information and limitations for the CSD XR22539 for Windows, and PTF U481091 for AIX.
This release contains various APARs for each supported platform. Full details of the APARs applicable to each platform can be found at the end of each of the platform-specific sections. The CSD and PTF each contain APARs issued in previous CSDs and PTFs released for the various platforms after the GA of version 3.1.5 of the product; there previous APARs were listed in the README files accompanying the previous CSD and PTF, and are not listed again here.
You will notice that both Tivoli® and TME® 10 are used in our sales, marketing, and product information materials. These terms are interchangeable. We will be removing references to TME 10 in future product releases.
Note: Certain characters in this file may not print correctly or at all, depending on your printer configuration, for example, the backslash (\), brackets ([ ]), the tilde (¨) and the at symbol (@).
Currently, Tivoli Software Distribution, Version 3.1.5 cannot coexist on the same workstation with:
· NetFinity Server 4.0, or later
· SystemView for OS/2
· NetView Distribution Management Agent for Windows
· NetView Distribution Management Agent for Windows NT
The following section provides details of the support and limitation criteria for Tivoli Software Distribution, Version 3.1.5 running under Microsoft Windows.
Tivoli Software Distribution, Version 3.1.5 at XR21927 CSD level supports the use of Windows 2000 Advanced Server as a platform both for the server and the client software. Please refer to the README of XR21927 CSD for details.
You should note that Tivoli Software Distribution uses NetFinity® for inventory discovery. However, NetFinity cannot distinguish between the various versions of Windows 2000 (e.g. Professional, Server and Advanced Server).
Windows NT 4.0 is supported only if you have installed Service Pack 2, or later.
Tivoli Software Distribution supports Windows 2000 Professional, Server and Advanced Server.
This CSD was tested on Windows 2000 with service pack 2 on machine with at least 128 Mb memory RAM for the Software Distribution 3.1.5 Server.
Tivoli Software Distribution for Windows 98 has the limitation that the IPX protocol does not work correctly for Windows 98.
On Windows NT and Windows 95, you might experience problems when using the Windows pull-down menu to switch from a main window to another window.
On Windows platforms, the dynamic change files preparation function for the Administration GUI is currently not available. It will be available at a later date.
On Windows platforms, if you use the Message Log via Administration GUI you might experience performance problems.
To use DiskCamera to install a change file, you must have the operating system installed in the same path on both the preparation site and target where you want to install the change file.
If one of the three steps that you perform by using DiskCamera fails, delete the \BIN\DSKCAM.TMP file before using DiskCamera again.
If you run DiskCamera on Windows 3.1x, the DPFPRE.EXE and DPFPOST.EXE files create the DSKCAM.LOG file in different directories. Usually, DPFPRE.EXE creates the DSKCAM.LOG file under <DRIVE>\SOFTDIST\BIN, and DPFPOST.EXE creates the DSKCAM.LOG file under C:\WINDOWS.
On Windows platforms, to improve the performance of the Administration GUI and enable you to use the windows effectively, it is recommended that you use a workstation with a Super VGA display and a Pentium processor.
If you create, refresh, update, or fix a change file by adding new files to it, you might experience problems when using directory or files names with embedded spaces.
On Windows NT 4.0, Windows 2000, Windows 98, or Windows 95, if you select Catalog > Change File > Create New > Refresh or Update or Fix > Change File Type, the Change File window appears.
Select the Files push button. The Files in Change File window appears.
Select Find. The Open window appears. If the name of the directory you use has an embedded space, as in the following example:
aname bname
the name is shown in the list of directories as follows:
anameb¨1
If you have a file name like the following:
afile bname
the name is shown in the list of files as follows:
afileb¨1
When you install the change file in the aname bname directory, either one of the following happens:
· The change file is installed in the aname bname directory, if the directory was created from the command prompt.
· The change file is installed in the anameb¨1 directory, if the directory does not exist.
On Windows NT 3.51, the directory and file names with embedded spaces are not shown in the directory list or file list.
On Windows platforms, to avoid this problem, do not use blanks for directory or file names. As an alternative, you can write the path and file name directly in the Name field of the Change File window.
On Windows NT and Windows 2000 a user that belongs to Administrator group can issue the commands
· nvdm start
The following scenario explains how to upgrade Tivoli Software Distribution, Version 3.1.5 CSD XR22539 on Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, Windows NT, Windows 98, and Windows 95 on single servers and clients.
You can upgrade this CSD using an unattended way: it is the only scenario suppotred for ths CSD.
This scenario is used upgrade Tivoli Software Distribution, Version 3.1.5 Server or Client to this CSD level in an unattended way on a server or client workstation running one of the following operating systems:
· Windows 2000 Server, Professional and Advanced Server
· Windows NT
· Windows 98 (client only)
· Windows 95 (client only)
with Tivoli Software Distribution, Version 3.1.5 Server or Client, already installed.
This scenario assumes the following conditions:
· The server or client workstation is running Tivoli Software Distribution, Version 3.1.5, or Tivoli Software Distribution Version 3.1.3 with CSD XR22091, Server or Client
· The server or client workstation has a version of Windows installed which is compatible with Tivoli Software Distribution, Version 3.1.5 (see the software prerequisites section in Tivoli Software Distribution, Version 3.1.5 Quick Beginnings for Windows NT).
Before commencing the upgrade it is advisable to backup the existing Server or Client installation to be upgraded. This can be achieved by instructing the operator of the server or client workstation to simply copy all files and subdirectories within the program folder to an alternate location on the system.
This scenario uses a batch script called SDUPD.BAT. The script creates a set of change file profiles which can be used to create the change files that will be applied over the existing product installed on the target workstation.
Generic change files are created for the following packages:
· Tivoli Software Distribution, Version 3.1.5 Server for Windows 2000
· Tivoli Software Distribution, Version 3.1.5 Client for Windows 2000
· Tivoli Software Distribution, Version 3.1.5 Server for Windows NT
· Tivoli Software Distribution, Version 3.1.5 Client for Windows NT
· Tivoli Software Distribution, Version 3.1.5 Client for Windows 9x
Download the code for the change files to the code server, in the D:\SD_CSD directory, as described below:
1. Insert the Tivoli Software Distribution CD-ROM for CSD XR22539 in the code server workstation. This scenario assumes that the drive letter corresponding to the CD-ROM is F:
1. Create the D:\SD_CSD directory on the code server workstation.
2. Open a command prompt session.
3. Change the current directory to F:\SD4WNT9x
4. From this directory enter the command:
SDUPD.BAT D:\SD_CSD\SD4WNT9x F:\SD4WNT9x
After completing this step, the following directory structure is created under the D:\SD_CSD directory:
D:\SD_CSD\| |\SD4WNT9x\| |..... |..... |W2KS.PRO |W2KC.PRO |WNTS.PRO |WNTC.PRO |W9XC.PRO |..... |..... |
The WNTS.PRO profile follows as an example.
GLOBAL NAME: IBM.SD4WNT.SERVER.REF.3150.XR22539 DESCRIPTION: SD Server for WNT 3.1.5 - (XR22539 level) CHANGE FILE TYPE: GEN OBJECT: SOURCE NAME: F:\SD4WNT9x\update\wnts\*.exe TARGET NAME: $(FILEPATH)BIN\*.exe TYPE: FILE ACTION: COPY INCLUDE SUBDIRS: NO GENERAL ATTR: -A---- OBJECT: SOURCE NAME: F:\SD4WNT9x\update\wnts\*.dll TARGET NAME: $(FILEPATH)BIN\*.dll TYPE: FILE ACTION: COPY INCLUDE SUBDIRS: NO GENERAL ATTR: -A---- |
To update the Tivoli Software Distribution installed products to this CSD level of Version 3.1.5, use the change file profiles that have been downloaded in the preparation directory D:\SD_CSD\SD4WNT9x.
To build the change files to install the CSD, use the following profiles:
W2KS.PRO |
For a Windows 2000 (Server, Professional or Advanced Server) server |
W2KC.PRO |
For a Windows 2000 (Server or Professional) client |
WNTS.PRO |
For a Windows NT server |
WNTC.PRO |
For a Windows NT client |
W9XC.PRO |
For a Windows 9x client |
To start Tivoli Software Distribution, Version 3.1.5 via the command line interface, enter the following command:
nvdm start
Change the current directory to D:\SD_CSD\SD4WNT9x. Use the Tivoli Software Distribution, Version 3.1.5 command line interface to enter the following command for each change file profile you want to build:
nvdm bld <change_file_profile_name>
Do not remove the CD-ROM during the execution of the nvdm bld command, because the CD-ROM is accessed to get the preparation code.
In Step 2 you created a set of change files that are stored under the repository of the Tivoli Software Distribution, Version 3.1.5 server, with the following names:
IBM.SD4W2K.SERVER.REF.3150.XR22539
IBM.SD4W2K.CLIENT.REF.3150. XR22539
IBM.SD4WNT.SERVER.REF.3150. XR22539
IBM.SD4WNT.CLIENT.REF.3150. XR22539
IBM.SD4W9X.CLIENT.REF.3150. XR22539
To install the change files (which you created in the previous step), use the following commands.
For a Windows 2000 (Server or Professional) server:
nvdm inst IBM.SD4W2K.SERVER.REF.3150. XR22539 -n -vs -w <target_name>
To confirm whether the installation has been completed correctly, verify that the change management status of the IBM.SD4W2K.SERVER.REF.3150.XR22539 change files is as follows:
IBM.SD4W2K.SERVER.REF.3150.XR22539 installed not removable inactive
If the installation performed in the previous step has been executed successfully, perform an activate request on the Windows NT server to make the code changes active, by entering the following command:
nvdm act -w <target_name> -f
During the execution of this step, the server workstation will restart automatically in order to make the code changes active.
For a Windows 2000 (Server or Professional) client:
nvdm inst IBM.SD4W2K.CLIENT.REF.3150.XR22539 -n -vs -w <target_name>
nvdm act -w <target_name> -f
For a Windows NT Server:
nvdm inst IBM.SD4WNT.SERVER.REF.3150.XR22539 -n -vs -w <target_name>
To confirm whether the installation has been completed correctly, verify that the change management status of the IBM.SD4WNT.SERVER.REF.3150.XR22539 change files is as follows:
IBM.SD4WNT.SERVER.REF.3150.XR22539 installed not removable inactive
If the installation performed in the previous step has been executed successfully, perform an activate request on the Windows NT server to make the code changes active, by entering the following command:
nvdm act -w <target_name> -f
During the execution of this step, the server workstation will restart automatically in order to make the code changes active.
For a Windows NT Client:
nvdm inst IBM.SD4WNT.CLIENT.REF.3150.XR22539 -n -vs -w <target_name>
nvdm act -w <target_name> -f
For a Windows 9x Client:
nvdm inst IBM.SD4W9X.CLIENT.REF.3150.XR22539 -n -vs -w <target_name>
nvdm act -w <target_name> -f
The following APARs are fixed in this CSD:
PJ28269 |
Setup.exe in the README |
PJ28292 |
SOFTWARE DISTR. NVDM START/STOP/RESET ISSUED BY NO-ROO USER |
PJ28349 |
SD
AGENT LOST A CONNECTION WITH SERVER AFTER REBOOT on WIN98 |
PJ28075 |
FNDCO006E
WHEN A INIT WITH PARAMETER IS SUBMITTED RECEIVE AN ERR |
PJ28317 |
FNDVL135E
MESSAGE TEXT IN FNDLOG INCORRECTLY IDENTIFIES THE NAME OF
THE CHANGE FILE OR PACKAGE RATHER THAN THE NAME OF THE TARGET |
PJ28316 |
THE
NVDM LSCF OUTPUT FOR A DYNAMIC CHANGE FILE IS INCOMPLETE ON
SD 3.1.5 LEVEL FOR CHANGE FILES BUILT AT 3.1.3 OR 3.1.5 |
This section of the README contains information relevant to systems running AIX.
This section explains how to upgrade existing installations of Tivoli Software Distribution for AIX to this PTF level of Version 3.1.5. It needs to be installed on top of PTF U475024.
The details below provide five scenarios for different types of upgrade/installation:
· Upgrade Tivoli Software Distribution for AIX Server/Client, Version 3.1.5 to this PTF level on a local AIX computer using installp or SMIT
· Upgrade Tivoli Software Distribution for AIX Server, Version 3.1.5 to this PTF level, on an AIX server, using the provided Change File
· Upgrade Tivoli Software Distribution for AIX Server, Version 3.1.5 to this PTF level, on an AIX server, without rebooting, using the provided Change File.
Note: You are recommended to use the same method (installp/SMIT or Change File) for upgrading from Tivoli Software Distribution, Version 3.1.5 to this CSD level, as you used to upgrade from Version 3.1.4 to Version 3.1.5 or to install latter PTFs.
This scenario is used to update Tivoli Software Distribution for AIX, Version 3.1.5 to this PTF level, in an attended way.
This scenario assumes the following conditions:
· Tivoli Software Distribution, Version 3.1.5 with the following components’ level:
·
netviewdm6000.base.obj.3.1.5.0.U475024
or netviewdm6000.base.obj.3.1.4.0.U475024 |
netviewdm6000.remoteadmin.obj.3.1.5.0.U475024
or netviewdm6000.remoteadmin.obj.3.1.4.0.U475024 |
netviewdm6000.tool.obj.3.1.5.0
or netviewdm6000.tool.obj.3.1.4.0.U469697 (updating of 3.1.4 to 3.1.5) |
· The code images are available from the CD-ROM of the PTF
The PTF release of Tivoli Software Distribution, Version 3.1.5 is supplied in the following objects contained in the netviewdm6000.3.1.5.0.U481091 package:
Fileset in
netviewdm6000.3.1.5.0.U481091 |
Contents |
netviewdm6000.base.obj.3.1.5.0.U481091 |
Base |
netviewdm6000.remoteadmin.obj.3.1.5.0.U481091 |
Remote admin |
netviewdm6000.tool.obj.3.1.5.0.U481091 |
Tool |
They are found on the PTF U481091 CD-ROM in the directory /SD4AIX/installp/.
If you wish to upgrade from the command line, move to that directory and type the following:
installp –ac –d<device> <component name>|all
If you wish to upgrade using SMIT, follow the steps below:
5. Run SMIT
6. Select install-update
7. Select Install and Update from ALL Available Software
8. Enter the required information on the displayed screen
9. Select the Update option.
This scenario is used to update an AIX server running Tivoli Software Distribution, Version 3.1.5 for AIX Server, to this PTF level; the upgrade requires the server to be rebooted.
This scenario assumes the following conditions:
· Tivoli Software Distribution, Version 3.1.5 (or 3.1.4 upgraded to 3.1.5) release with the following PTF installed at the AIX server: U475024
· The code images are available from the CD-ROM of the PTF
On an AIX Preparation Site do the following:
10. Create the directory /prep and go there
11. Download the following binary file from the /SD4AIX/update/ directory on the PTF U481091 CD-ROM into the /prep directory:
AIXS3150.TARZBIN
12. Rename the above file to AIXS3150.TARBIN.Z using the command
mv AIXS3150.TARZBIN AIXS3150.TARBIN.Z
13. Uncompress the file AIXS3150.TARBIN.Z using the command
uncompress AIXS3150.TARBIN.Z
14. Unpack the TAR file using the command
tar –xvf AIXS3150.TARBIN
15. If the option: netviewdm6000.remoteadmin.obj is installed prepare the remote admin Change File using the command:
nvdm bld /prep/profile.admin
16. In all cases (servers and focal points), prepare the server Change File using the command:
nvdm bld /prep/profile
17. Exit from that directory.
From any administration site:
18. If the option: netviewdm6000.remoteadmin.obj is installed issue the following command:
nvdm inst –vs IBM.NDM6000.REMOTEADMIN.REF.3150.U481091 >
-w <server> -e
19. In all cases issue the following commands:
nvdm inst –vs IBM.NDM6000.BASE.REF.3150.U481091 >
-w <server> -e
nvdm cat IBM.NDM6000.SCRIPT.REF.3150.U481091 >
/prep/linkrbasy –o Procedure
nvdm act –w<server> >
-m<server>:IBM.NDM6000.SCRIPT.REF.3150.U481091 –f
Should it be necessary to de-install the upgrade:
20. If the option: netviewdm6000.remoteadmin.obj is installed issue the following command:
nvdm rem –vs IBM.NDM6000.REMOTEADMIN.REF.3150.U481091
-w <server>
21. In all cases issue the following commands:
nvdm rem –vs IBM.NDM6000.BASE.REF.3150.U481091 –w <server>
nvdm act –w <server> -f
This scenario is used to update an AIX server running Tivoli Software Distribution, Version 3.1.5 for AIX Server, to this PTF level; the upgrade does not require the server to be rebooted.
This scenario assumes the following conditions:
· Tivoli Software Distribution, Version 3.1.5 (or 3.1.4 upgraded to 3.1.5) release with the following PTF installed at the AIX server: U475024
· The code images are available from the CD-ROM of the PTF
On an AIX Preparation Site do the following:
22. Create the directory /prep and go there
23. Download the following binary file from the /SD4AIX/update/ directory on the PTF U475024 CD-ROM into the /prep directory:
AIXS3150.TARZBIN
24. Rename the above file to AIXS3150.TARBIN.Z using the command:
mv AIXS3150.TARZBIN AIXS3150.TARBIN.Z
25. Uncompress the file AIXS3150.TARBIN.Z using the command:
uncompress AIXS3150.TARBIN.Z
26. Unpack the TAR file using the command:
tar –xvf AIXS3150.TARBIN
If you DO NOT HAVE the option: netviewdm6000.remoteadmin.obj installed, from any administration site follow the steps below.
27. Prepare the server Change File using
nvdm bld /prep/profile.nonreboot
28. Exit from that directory.
29. You can upgrade the server in a REMOVABLE or a NON-REMOVABLE way:
REMOVABLE
a. Enable the REMOVABLE option:
nvdm cat IBM.NDM6000.BASE.REF.3150.U481091.EXECS >
/prep/_fndexecs.sh –o Procedure
nvdm exec IBM.NDM6000.BASE.REF.3150.U481091.EXECS >
-w<server>
b. To upgrade the server:
nvdm inst IBM.NDM6000.BASE.REF.3150.U481091.NR >
-w <server> -e
c. Should it be necessary to de-install the upgrade:
nvdm rem IBM.NDM6000.BASE.REF.3150.U481091.NR >
-w <server>
NON-REMOVABLE
d. To upgrade the server:
nvdm inst IBM.NDM6000.BASE.REF.3150.U481091.NR >
-w <server> -e –n
If you DO HAVE the option: netviewdm6000.remoteadmin.obj installed, from any administration site follow the steps below.
30. Prepare the server Change File using the command:
nvdm bld /prep/profile.admin.nonreboot
31. Exit from that directory.
32. You can upgrade the server in a REMOVABLE or a NON-REMOVABLE way:
REMOVABLE
e. Enable the REMOVABLE option for the remote admin option:
nvdm cat IBM.NDM6000.REMOTEADMIN.REF.3150.U481091.EXECA >
/prep/_fndexeca.sh –o Procedure
nvdm exec IBM.NDM6000.REMOTEADMIN.REF.3150.U481091.EXECA >
-w<server>
f. To upgrade the server:
nvdm inst IBM.NDM6000.REMOTEAMN.REF.3150.U481091.NR >
-w <server> -e
g. Should it be necessary to de-install the upgrade:
nvdm rem IBM.NDM6000.REMOTEADMIN.REF.3150.U481091.NR >
-w <server>
NON-REMOVABLE
h. To upgrade the server:
nvdm inst IBM.NDM6000.REMOTEADMIN.REF.3150.U481091.NR >
-w <server> -e –n
The following APARs are fixed in this PTF:
IY20984 |
Request remain in scheduled status even after installation has been completed |
IY25976 |
Remote Admin Library |
IY30978 |
FNDCL019E error caused by Server libfnddb.a |
IY25977 |
Link GUI |
II12957 |
fnddbcmp wrong permission and ownership |
IY24984 |
Update fndereq.sh level of code |
IY25978 |
Update fndcount level of code |