Tivoli
Software Distribution, Version 3.1.5
README
CSD XR22091 for Windows®, OS/2® and NetWare, Version
3.1.5
PTF U475024 for AIX®,
Version 3.1.5
June, 2001
Coexistence with Other Tivoli Software
Distribution Products
2 Tivoli Software
Distribution CSD XR22091 for OS/2
Software Preparation GUI for OS/2 Available
on OS/2 Warp 3.0, or Later
DiskCamera for OS/2 Available on OS/2 Warp
3.0, or Later
Installation Scenarios for OS/2
Preparing the Code Images of Tivoli Software
Distribution, Version 3.1.5 on the Preparation Site
Scenario 1: Attended Upgrade of Tivoli
Software Distribution Server or Client
APARS Fixed in Tivoli Software Distribution,
Version 3.1.5 for OS/2
3 Tivoli Software
Distribution CSD XR22091 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
Installation Scenarios for Windows Platforms
Preparing the Code Images of Tivoli Software
Distribution on the Preparation Site
Scenario 2: Unattended Upgrade of Tivoli
Software Distribution Server or Client to Version 3.1.5
Updating Version 3.1.5 to this CSD level
Migration Issues
APARs Fixed in Tivoli Software Distribution,
Version 3.1.5 for Windows
4 Tivoli Software
Distribution CSD XR22091 for Netware
Netware Support and Limitations
STS APPC Support Not Available
Software Distribution User Names
Server Configuration Parameters for TCP/IP
Networks
Installation Scenarios for Netware
Preparing the Code Images of the CSD on the
Preparation Site
APARs fixed in Tivoli Software Distribution,
Version 3.1.5 for Netware
5 Tivoli Software
Distribution PTF U475024 for AIX
Installation Scenarios for AIX
Scenario Two: Upgrade Tivoli Software
Distribution for AIX Server, Version 3.1.5
Scenario Four: Upgrade Tivoli Software
Distribution for AIX Client, Version 3.1.5, to This PTF Level
This file (README.TXT) provides Tivoli Software Distribution, Version 3.1.5 information and limitations for the CSD XR22091 for OS/2, Windows and NetWare, and PTF U475024 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
This chapter of the README contains information relevant to systems running OS/2, Versions 3.x, 4.0 and 4.5.
On OS/2, you cannot use the ls and lscf commands via a TELNET remote session with TCP/IP 4.0, because the server stops.
If you use the Tivoli Software Distribution, Version 3.1.5 for OS/2 Client via NetBIOS on a less powerful workstation, you might experience connection problems. To avoid these problems, set the following variable in the CONFIG.SYS file:
set FNDNBOS2 = YES
Then restart the workstation.
You can use the graphical user interface to software preparation for OS/2 only on OS/2 Warp 3.0, or later.
You can use DiskCamera for OS/2 only on OS/2 Warp 3.0, or later.
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.
This section explains how to use the CSD XR22091 to upgrade existing installations of Tivoli Software Distribution to this CSD level of Version 3.1.5, and to make scratch installations of Tivoli Software Distribution, Version 3.1.5 at this CSD level. It requires that you have the licensed code images of Tivoli Software Distribution, Version 3.1.5, either the GA version or the upgrade installed with XR21925. If you have already installed CSD XR21927 on either of these two levels, you can now install CSD XR22091 on top. It is assumed that you will be using one OS/2 server as a Preparation Site and carrying out attended or unattended installations of servers and/or clients and/or mobile clients. If you have not already set up a server as a Preparation Site, you are strongly recommended to do so.
The details below describe how to prepare the Tivoli Software Distribution, Version 3.1.5 CSD XR22091 code images on the Preparation Site, and then provide three scenarios for different types of upgrade/installation:
· Attended upgrade of Tivoli Software Distribution, Version 3.1.5 Server or Client to this CSD level
· Attended installation of Tivoli Software Distribution, Version 3.1.5 Server or Client at this CSD level
· Unattended upgrade of Tivoli Software Distribution, Version 3.1.5 Server or Client to this CSD level
The following are assumed:
· The code images for Tivoli Software Distribution, Version 3.1.5 are stored on an OS/2 server, under the directory D:\CID\IMG\SD4OS2 (if this is not currently the case, the instructions for preparing the Tivoli Software Distribution, Version 3.1.5 code images show you how to set up the Version 3.1.5 images first).
· The OS/2 server is also used as the Preparation Site
Before carrying out any of the upgrade/installation scenarios it is necessary to upgrade the Tivoli Software Distribution Code Images at the preparation site to this CSD level of Version 3.1.5, creating them from scratch if necessary. This preparation site can then be used as the base for executing the upgrade and installation scenarios described below.
If your Preparation Site is running a Windows, NetWare or AIX operating system, see the other chapters of this Readme.
For this preparation activity you require the code images for Tivoli Software Distribution, Version 3.1.5 on a preparation site workstation, or the Tivoli Software Distribution, Version 3.1.5 CD-ROM (LK3T-5087-00).
If the Preparation Site does not already contain the Tivoli Software Distribution, Version 3.1.5 code images, you should add them, following the instructions in the README.TXT file of either the Tivoli Software Distribution, Version 3.1.5 GA release or the Tivoli Software Distribution Version 3.1.3 with CSD XR21925 or Tivoli Software Distribution 3.1.5 with XR21927.
To upload the Tivoli Software Distribution, Version 3.1.5 CSD XR22091 code images to the preparation site:
1. Place the Tivoli Software Distribution, Version 3.1.5 CSD XR22091 CD-ROM in the CD-ROM drive
2. Move to the D:\CID\IMG\SD4OS2 directory on the Preparation Site workstation
3. From this directory enter the following command:
XCOPY <XR22091-CD-ROMdrive>\SD4OS2\*.* /s
After completing this step, the following structure is created under the D:\CID\IMG directory:
D:\CID\IMG\| |\<DIR>SD4OS2\| |. |..|\<DIR> PRISTINE |\<DIR> SAMPLES |\<DIR> TOOLS |\<DIR> IMAGES\| |. |..|\<DIR> CLT |\<DIR> DSKCAM |EPFISINC.PKG |INSTALL.EXE |INSTALL.IN_|\<DIR> NETFIN |\<DIR> MOB |NVDMCAT.ICF |NVDMDSC.DSC |NVDMPKG.PKG |\<DIR> PREPCLT |\<DIR> PREPSRV |SDISTCLT.RSP |SRV|tme10ipf.cmd |tme10sd.adf |tme10sd.mrf |tme10sd.ndi |tme10sd.var|tme10vl.cmd |
Note that this preparation stage has only upgraded the code images; you should now upgrade your servers and clients using one of the following scenarios.
This scenario is used if you wish to upgrade Tivoli Software Distribution, Version 3.1.5 to this CSD level, in an attended way on an OS/2 Server or Client workstation.
If your Server or Client workstation is running a Windows, NetWare or AIX operating system, see the other chapters of this Readme.
This scenario assumes the following conditions:
· The code images of the CSD XR22091 have already been uploaded onto an OS/2 Preparation Site in the D:\CID\IMG\SD4OS2 directory.
· The Server or Client workstations have installed Tivoli Software Distribution, Version 3.1.5, or Tivoli Software Distribution Version 3.1.3 with CSD XR21925 or Tivoli Software Distribution 3.1.5 with XR21927
· The Server or Client workstations have a version of OS/2 installed which is compatible with this CSD level of Tivoli Software Distribution, Version 3.1.5 (see the software prerequisites section in Tivoli Software Distribution, Version 3.1.5 Quick Beginnings for OS/2).
During the installation you will be asked if you want to backup the existing Tivoli Software Distribution server or client product, in which case a copy of the installation files will be stored in the installation directory in an appropriately named sub-directory. However, if you wish to backup the installation to a different location you can simply copy all files and subdirectories within the program folder to an alternative location on the system.
To install Tivoli Software Distribution, use the D:\CID\IMG\SD4OS2\IMAGES directory as the source directory.
The server and client installation scenarios are described in the Tivoli Software Distribution, Version 3.1.5 documentation, as follows:
|
Server Upgrade |
Tivoli Software Distribution, Version 3.1.5 Quick Beginnings for OS/2 |
|
Client Upgrade |
Tivoli Software Distribution, Version 3.1.5 Clients Installation and Configuration |
This scenario is used if you wish to install Tivoli Software Distribution, Version 3.1.5 Server or Client at this CSD level, in an attended way on a scratch server or client workstation running OS/2, i.e. an OS/2 server or client workstation without any previous version of Tivoli Software Distribution installed.
If your server or client workstation is running a Windows, NetWare or AIX operating system, see the other chapters of this Readme.
This scenario assumes the following conditions:
· The code images of the CSD XR22091 have already been uploaded onto an OS/2 Preparation Site in the D:\CID\IMG\SD4OS2 directory.
· The Server or Client workstations have a version of OS/2 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 OS/2).
To upgrade/install Tivoli Software Distribution, Version 3.1.5, use the D:\CID\IMG\SD4OS2\IMAGES directory as the source directory.
The server and client installation scenarios are described in the Tivoli Software Distribution, Version 3.1.5 documentation, as follows:
|
Server Installation |
Tivoli Software Distribution, Version 3.1.5 Quick Beginnings for OS/2 |
|
Client Installation |
Tivoli Software Distribution, Version 3.1.5 Clients Installation and Configuration |
This scenario is used if you wish to install this CSD level of Tivoli Software Distribution, Version 3.1.5 in an unattended way on a server or client workstation with Tivoli Software Distribution, Version 3.1.5 Server or Client already installed.
If your server or client workstation is running a Windows, NetWare or AIX operating system, see the other chapters of this Readme.
This scenario assumes the following conditions:
· The code images of the CSD XR22091 have already been uploaded onto an OS/2 Preparation Site in the D:\CID\IMG\SD4OS2 directory.
· The server or client workstation has installed Tivoli Software Distribution, Version 3.1.5, or Tivoli Software Distribution Version 3.1.3 with CSD XR21925 or Tivoli Software Distribution 3.1.5 with XR21927, Server or Client as appropriate,
· The server or client workstation has a version of OS/2 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 OS/2).
During the installation you will be asked if you want to backup the existing Tivoli Software Distribution server or client product, in which case a copy of the installation files will be stored in the installation directory in an appropriately named sub-directory. However, if you wish to backup the installation to a different location you can simply copy all files and subdirectories within the program folder to an alternative location on the system.
To update the Tivoli Software Distribution for OS/2 Server, Clients, and Mobile Clients to this CSD level of Version 3.1.5, use the CID change file profile and response files examples stored in the following directories:
D:\CID\IMG\SD4OS2\SAMPLES
Customize the client and server change file profiles examples by modifying the paths and the file names to match your environment.
Use the following CLIENT.PRO change file profile example stored on the D:\CID\IMG\SD4OS2\SAMPLES directory to build and install the Tivoli Software Distribution client:
GLOBAL NAME: TME10.SD4OS2.OS2CLIENT.REF.315.XR22091.US_ENDESCRIPTION: TME 10 SD Client for OS/2 CSD XR22091LOCAL NAME: $(REPOSITORY)\clt927.csdCHANGE FILE TYPE: OS2CID PREREQ COMMAND: cidmount SRVIFS $(FREEDRIVE2) $(FREEDRIVE3) > bichi distimg distlogPOSTREQ COMMAND: cidunmnt SRVIFS $(FREEDRIVE2) $(FREEDRIVE3) INSTALL PROGRAM: PROGRAM NAME: $(FREEDRIVE2)\SD4OS2\IMAGES\INSTALL.EXE PARAMETERS: /S:$(FREEDRIVE2)\SD4OS2\IMAGES /R:$(RSPFILE) > /TU:$(BOOTDRIVE)\ /L1:$(FREEDRIVE3)\LOG\CLT\$(TARGET).L1 /L2:$(FREEDRIVE3)\LOG\CLT\$(TARGET).L2 /A:U /X RESPONSE FILE: D:\CID\IMG\SD4OS2\SAMPLES\CLIENT.RSP |
Use the following SERVER.PRO change file example stored on the D:\CID\IMG\SD4OS2\SAMPLES directory, to install the Tivoli Software Distribution server:
|
GLOBAL NAME: TME10.SD4OS2.OS2SERVER.REF.315.XR22091.US_ENDESCRIPTION: TME 10 SD Server for OS/2 CSD XR22091LOCAL NAME: $(REPOSITORY)\srv927.csdCHANGE FILE TYPE: OS2CID INSTALL PROGRAM: PROGRAM NAME: D:\CID\IMG\SD4OS2\IMAGES\INSTALL.EXE PARAMETERS: /S:D:\CID\IMG\SD4OS2\IMAGES /R:$(RSPFILE) > /TU:$(BOOTDRIVE)\ /L1:D:\CID\IMG\LOG\SRV\$(TARGET).L1 /L2:D:\CID\IMG\LOG\SRV\$(TARGET).L2 /A:U /X RESPONSE FILE: D:\CID\IMG\SD4OS2\SAMPLES\SERVER.RSP |
On the Tivoli Software Distribution, Version 3.1.5 server, enter the start command to start the Tivoli Software Distribution command line interface if the product has not yet started, as follows:
nvdm start
Check whether the server and the client response files contain the components you want to update, and modify them if needed.
Use the Tivoli Software Distribution for OS/2 command line interface to enter the following command for each change file profile you want to build:
nvdm bld D:\CID\IMG\SD4OS2\SAMPLES\SERVER.PRO
nvdm bld D:\CID\IMG\SD4OS2\SAMPLES\CLIENT.PRO
To install the server change file as not removable in the active area on the Tivoli Software Distribution, Version 3.1.5 server workstation, enter the following command:
nvdm inst TME10.SD4OS2.OS2SERVER.REF.315.XR22091.US_EN -n
During the execution of this command, the server workstation will reboot to make the code changes active.
After the installation process, the Tivoli Software Distribution panel displays a reboot warning message for 60 seconds. Do not select the Activate Now button, because if selected, the Tivoli Software Distribution folder icons will not be saved in the Tivoli Software Distribution folder after the reboot process.
If you select the Activate Now button in error, you can recover by running the fndicons.cmd tool that is stored in the <XR22091-CD-ROM drive>\SD4OS2\TOOLS directory.
Perform this step only if Step 1: Installing the Cataloged Change File for the Server on page 6 has been successfully executed.
Before you install the mobile client, connect it to the server by entering the following command from the server workstation:
nvdm connect <client_name>
To install the change files as not removable in the active area on each Tivoli Software Distribution client and mobile workstation, enter the following command:
nvdm inst TME10.SD4OS2.OS2CLIENT.REF.315.XR22091.US_EN -n -w <client_name>
During the execution of this step the client workstations will reboot automatically in order to make the code changes active.
After the installation process, the Tivoli Software Distribution panel displays a reboot warning message for 60 seconds. Do not select the Activate Now button, because if selected, the Tivoli Software Distribution folder icons will not be saved in the Tivoli Software Distribution folder after the reboot process.
If you select the Activate Now button in error, you can recover by running the fndicons.cmd tool that is stored in the <CD-ROM CSD XR22091 drive>\SD4OS2\TOOLS directory.
The following APARs are fixed in this CSD (the CSD also contains all APARs fixed in CSD XR21927, as listed in the README file accompanying that CSD):
|
PJ27936 |
Error FNDCL146E occurs adding installation parameters to a renamed target |
|
PJ27883 |
Error in held relc commands |
|
PJ26170 |
CMD connection changes from held to released after nvdm rld or nvdm start |
|
PJ27725 |
FNDCM024E first token is overwritten |
|
PJ27745 |
FNDFS047E: Received in fndlog at SD/AIX when sending a 0 byte file to replace An existing file with DESTRUCTION=A and DISP=OLD |
|
PJ27754 |
FNDCM024E first token is overwritten |
|
DE12772 |
THE UPDAK COMMAND DOESN’T RUN CORRECTLY |
This section of the README contains information relevant to systems running Microsoft Windows 95, 98, NT and 2000 (Professional, Server and Advanced Server versions).
It includes the following:
· Support and limitations - see Windows Support and Limitations on page 8
· Installation scenarios - see page Installation Scenarios for Windows Platforms on page 10
· Installing and configuring Tivoli Software Distribution on multiple servers to provide server redundancy – see Installing and Configuring Tivoli Software Distribution, Version 3.1.5 on Windows 2000 Advanced Server using Microsoft Cluster on page 18
· APARS fixed - see APARs Fixed in Tivoli Software Distribution, Version 3.1.5 for Windows on page 20.
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).
Full details of the installation and configuration of Advanced Server are given in Installing and Configuring Tivoli Software Distribution, Version 3.1.5 on Windows 2000 Advanced Server using Microsoft Cluster on page 19.
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.
The following scenarios explain how to upgrade and install Tivoli Software Distribution, Version 3.1.5 CSD XR22091 on Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, Windows NT, Windows 98, and Windows 95 on single servers and clients. Installation scenarios for Windows 2000 Advanced Server on multiple servers to provide server redundancy are described in Installing and Configuring Tivoli Software Distribution, Version 3.1.5 on Windows 2000 Advanced Server using Microsoft Cluster on page 18.
This section explains how to use the Tivoli Software Distribution, Version 3.1.5 CSD XR22091 to upgrade existing installations of Tivoli Software Distribution, Version 3.1.5 to this CSD level and to make scratch installations of this CSD level. It requires that you have the licensed code images of Tivoli Software Distribution, Version 3.1.5, either the GA version or the upgrade installed with XR21925. If you have already installed CSD XR21927 on either of these two levels, you can now install CSD XR22091 on top. It is assumed that you will be using one Windows server as a Preparation Site and carrying out attended or unattended installations of servers and/or clients and/or mobile clients. If you have not already set up a server as a Preparation Site, you are strongly recommended to do so.
The details below describe how to prepare the Tivoli Software Distribution CSD XR22091 code images on the Preparation Site, and then provide two scenarios for different types of upgrade/installation:
· Attended upgrade or scratch installation of Tivoli Software Distribution, Version 3.1.5 Server or Client to this CSD level
· Unattended upgrade of Tivoli Software Distribution, Version 3.1.5 at this CSD level
The following are assumed:
· The code images for Tivoli Software Distribution, Version 3.1.5 are stored on a Windows NT server, under the directory D:\SD_IMG (if this is not currently the case, the instructions for preparing the Tivoli Software Distribution code images show you how to set up the Version 3.1.5 images first).
· The Windows server is also used as the Preparation Site
Before carrying out any of the software upgrade/installation scenarios it is necessary to upgrade the Tivoli Software Distribution Code Images at the Preparation Site to this CSD level, creating them from scratch if necessary. This site can then be used as the base for carrying out the installation and upgrade scenarios.
If your Preparation Site is running an OS/2, NetWare or AIX operating system, see the other chapters of this Readme.
For this preparation activity you require the code images for Tivoli Software Distribution, Version 3.1.5 on a preparation site workstation.
If the Preparation Site does not already contain the Tivoli Software Distribution, Version 3.1.5, code images, you should add them, following the instructions in the README.TXT file for Tivoli Software Distribution, Version 3.1.5, either from the GA version (CD-ROM LK3T-5087-00) or the CSD XR21925.
Note that this preparation stage has only upgraded the code images; you should now upgrade your servers and clients using one of the following scenarios.
This scenario is used if you wish to upgrade Tivoli Software Distribution, Version 3.1.5 Server or Client to this CSD level in an attended way, or make an attended installation of Tivoli Software Distribution, Version 3.1.5 Server or Client at this CSD level, on a server or client workstation running one of the following operating systems:
· Windows 2000 Advanced Server
· Windows 2000
· Windows NT
· Windows 98 (client only)
· Windows 95 (client only)
If your Server or Client workstation is running an OS/2, NetWare or AIX operating system, see the other chapters of this Readme.
This scenario assumes the following conditions:
· The code images of the CSD XR22091 have already been uploaded onto a Windows Preparation Site in the D:\SD_IMG directory
· If you wish to upgrade an existing installation of Tivoli Software Distribution, the workstation must be running Tivoli Software Distribution, Version 3.1.5, or Tivoli Software Distribution Version 3.1.3 with CSD XR21925, Server or Client
· The Server or Client workstations have 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 starting the installation, backup the existing installation of Tivoli Software Distribution on the server or client (you can do this simply by copying all files and subdirectories within the program folder to an alternate location on the system).
To install Tivoli Software Distribution, Version 3.1.5 Server or Client, use the D:\SD_IMG source directory.
The server and client installation scenarios are described in the following manuals:
|
Server Upgrade |
Tivoli Software Distribution, Version 3.1.5 Quick Beginnings for Windows NT |
|
Client Upgrade |
Tivoli Software Distribution, Version 3.1.5 Clients Installation and Configuration |
This scenario is used if you wish to 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.
If your server or client workstation is running an OS/2, NetWare or AIX operating system, see the other chapters of this Readme.
This scenario assumes the following conditions:
· The code images of the CSD XR22091 have already been uploaded onto a Windows Preparation Site in the D:\SD_IMG directory.
· The server or client workstation is running Tivoli Software Distribution, Version 3.1.5, or Tivoli Software Distribution Version 3.1.3 with CSD XR21925, 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
· Tivoli Software Distribution, Version 3.1.5 Mobile Client for Windows NT
· Tivoli Software Distribution, Version 3.1.5 Mobile 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 XR22091 in the code server workstation. This scenario assumes that the drive letter corresponding to the CD-ROM is F:
2. Create the D:\SD_CSD directory on the code server workstation.
3. Open a command prompt session.
4. Change the current directory to F:\SD4WNT9x
5. 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 |WNTM.PRO |W9XC.PRO |W9XM.PRO|..... |..... |
The WNTS.PRO profile follows as an example.
GLOBAL NAME: IBM.SD4WNT.SERVER.REF.3150.XR22091 DESCRIPTION: SD Server for WNT 3.1.5 - (XR22091 level) CHANGE FILE TYPE: GENOBJECT: 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---- OBJECT: SOURCE NAME: F:\SD4WNT9x\update\wnts\*.cat TARGET NAME: $(FILEPATH)*.cat TYPE: FILE ACTION: COPY INCLUDE SUBDIRS: NO GENERAL ATTR: -A---- OBJECT: SOURCE NAME: F:\SD4WNT9x\update\dkamnt\*.* TARGET NAME: $(FILEPATH)BIN\*.* TYPE: FILE ACTION: COPY INCLUDE SUBDIRS: NO GENERAL ATTR: -A---- # ----------- GUI code - uncomment if needed #OBJECT: # SOURCE NAME: F:\SD4WNT9x\update\guints\*.* # TARGET NAME: $(FILEPATH)BIN\*.* # TYPE: FILE # ACTION: COPY # INCLUDE SUBDIRS: NO # GENERAL ATTR: -A---- # ----------- NetFinity 5.0 code - uncomment if needed #OBJECT: # SOURCE NAME: F:\SD4WNT9x\update\netfwnt\*.* # TARGET NAME: $(FILEPATH)BIN\*.* # TYPE: FILE # ACTION: COPY # INCLUDE SUBDIRS: NO # GENERAL ATTR: -A---- # ----------- Documentation files - uncomment if needed #OBJECT: # SOURCE NAME: F:\SD4WNT9x\update\doc\*.* # TARGET NAME: $(FILEPATH)BIN\*.* # TYPE: FILE # ACTION: COPY # INCLUDE SUBDIRS: NO # GENERAL ATTR: -A---- |
·
· The GUI component (guints) is commented out in the profiles. Remove the number sign (#) to update the GUI component.
· The NetFinity component (netfwnt) is commented out in the profiles. Remove the number sign (#) to update the NetFinity files to the 5.0 version. Use NetFinity version 5.0 if there is a problem with the inventory phase of the product; if necessary, a change file can be built later to update the NetFinity files.
· The documentation component (doc) is commented out in the profiles. Remove the number sign (#) to update the documentation component.
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 |
|
WNTM.PRO |
For a Windows NT mobile |
|
W9XC.PRO |
For a Windows 9x client |
|
W9XM.PRO |
For a Windows 9x mobile 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.XR22091
IBM.SD4W2K.CLIENT.REF.3150.XR22091
IBM.SD4W2K.MOBILE.REF.3150.XR22091
IBM.SD4WNT.SERVER.REF.3150.XR22091
IBM.SD4WNT.CLIENT.REF.3150.XR22091
IBM.SD4WNT.MOBILE.REF.3150.XR22091
IBM.SD4W9X.CLIENT.REF.3150.XR22091
IBM.SD4W9X.MOBILE.REF.3150.XR22091
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.XR22091 -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.XR22091 change files is as follows:
IBM.SD4W2K.SERVER.REF.3150.XR22091 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.XR22091 -n -vs -w <target_name>
nvdm act -w <target_name> -f
For a Windows 2000 (Server or Professional) mobile client:
nvdm inst IBM.SD4W2K.MOBILE.REF.3150.XR22091 -n -vs -w <target_name>
nvdm act -w <target_name> -f
For a Windows NT Server:
nvdm inst IBM.SD4WNT.SERVER.REF.3150.XR22091 -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.XR22091 change files is as follows:
IBM.SD4WNT.SERVER.REF.3150.XR22091 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.XR22091 -n -vs -w <target_name>
nvdm act -w <target_name> -f
For a Windows NT Mobile Client:
nvdm inst IBM.SD4WNT.MOBILE.REF.3150.XR22091 -n -vs -w <target_name>
nvdm act -w <target_name> -f
For a Windows 9x Client:
nvdm inst IBM.SD4W9X.CLIENT.REF.3150.XR22091 -n -vs -w <target_name>
nvdm act -w <target_name> -f
For a Windows 9x Mobile Client:
nvdm inst IBM.SD4W9X.MOBILE.REF.3150.XR22091 -n -vs -w <target_name>
nvdm act -w <target_name> -f
Tivoli Software Distribution, Version 3.1.5 without this CSD applied will not operate under the Windows 2000 Advanced Server environment. Before migrating your operating system from Windows NT or Windows 2000 Professional or Server to Windows 2000 Advanced Server you must follow this procedure:
1. Update Tivoli Software Distribution, Version 3.1.5 to this CSD level, using one of the procedures described above
2. Migrate the operating system from Windows NT or Windows 2000 Professional or Server to Windows 2000 Advanced Server
3. Modify the configuration of Tivoli Software Distribution to recognize the new operating system, as follows:
a. Stop the product by entering the command:
nvdm stop -x -k
b. Open nvdm.cfg in a text editor and change the MACHINE TYPE keyword so that it reads:
MACHINE TYPE: WIN2K_ADV
c. Restart the product with the command:
nvdm start
d. Update the database entry for the computer by issuing the command:
nvdm updtg <target_name> -y WIN2K_ADV
Tivoli Software Distribution, Version 3.1.5 can be installed and configured for servers running Windows 2000 Advanced Server.
This scenario allows you to set up two servers that, by use of the Microsoft Cluster Service (MSCS), allows a single installation of Tivoli Software Distribution on an external storage unit to be run by either server, the transfer of control between the servers being carried out without needing to switch off either of the servers or detaching and reattaching the external storage unit.
The configuration consists of two servers, with different hostnames/IP addresses, both of which are concurrently connected to each other and the same external storage unit in a cluster configuration. The use of the MSCS feature of Windows 2000 Advanced Server ensures that whichever server is running Tivoli Software Distribution, the hostname and IP address used by other Tivoli Software Distribution servers and clients does not change.
The operational scenario allows both servers to be up and running at any one time, but only one is running Tivoli Software Distribution. It is possible to transfer control to the other server at any time, without switching off either server or touching the external storage unit.
The procedure steps are summarized as follows:
1. Install Windows 2000 Advanced Server on the Primary Cluster Node
2. Install Windows 2000 Advanced Server on the Secondary Cluster Node
3. Configure the MSCS to define a cluster including both servers, the quorum device and the shared device on the external storage unit, and to assign a network identity to the cluster service
4. Test the network
5. Install Tivoli Software Distribution, Version 3.1.5 at CSD XR22091 level on the shared device on the external storage unit
6. Configure the cluster service. There are two possibilities:
a) Manual configuration
1. Configure the cluster service to include Tivoli Software Distribution as a resource
2. Start up the Tivoli Software Distribution resource from the cluster service
3. Clone the installation of Tivoli Software Distribution by copying the registry, environment variables and services details relating to Tivoli Software Distribution from the Primary Cluster Node to the Secondary Cluster Node
5. Switch from the Primary Cluster Node to the Secondary Cluster Node
6. Switch from the Secondary Cluster Node to the Primary Cluster Node
b) Automatic configuration
o From the First Cluster Node, run the following provided on the CSD XR22091 CD-ROM:
§ AddNetViewDM.cmd script with the primary node parameter = 1, which identifies the Primary Cluster Node
o From the Secondary Cluster Node, run the following provided on the CSD XR22091 CD-ROM:
§ CloneReg.exe tool. After you run the tool, log off and log on the workstation.
§ AddNetviewDM.cmd script with the secondary node parameter = 2, which identifies the Secondary Cluster Node
This scenario assumes the following conditions:
· Two servers with diskette drives.
· One external storage unit compatible with the MSCS (i.e. it must be in the HCL for MSCS). The external storage unit would normally use a RAID5 SCSI configuration, in which the quorum device is a pair of mirrored disk drives, while the shared device is an array of three or more disk drives, with an extra drive available to hot swap in the event of problems with any of the other drives in the array.
The shared device must be of sufficient capacity and speed to hold the Tivoli Software Distribution, Version 3.1.5 server software and the files used by the software. Information on the disk requirements of Tivoli Software Distribution can be found in the Planning chapter of Tivoli Software Distribution for Windows NT Quick Beginnings, Version 3.1.5; the disk requirements for the Tivoli Software Distribution files (database, catalog, etc.) will depend largely on how you want to use the software, and which software products you will be distributing.
· SCSI cards and cables to interconnect the disks and servers using a SCSI bus, compatible with the MSCS (i.e. they must be in the HCL for MSCS).
· Three static IP addresses and associated hostnames, all of which are valid for the domain in which the servers will be connected.
· Login access as Domain Administrator
The normal scenario in which you will want to operate the cluster service is with both servers online. In this way, the cluster service will normally pass requests to Tivoli Software Distribution running on the Primary Cluster Node, but if it detects any problem with the Primary Cluster Node it will immediately pass requests to the Secondary Cluster Node which will take over control. To activate this scenario, right click on the Tivoli Software Distribution service on the Secondary Cluster Node in the Cluster Administrator, and select Bring online; now both servers are capable of running Tivoli Software Distribution when the cluster service asks them to.
If you want to switch off the Primary Cluster Node, for example to carry out maintenance, you can switch to the Secondary Cluster Node as follows. From the Cluster Administrator, right click on the Primary Cluster Node name and select Stop cluster service; the cluster service will now route all traffic for Tivoli Software Distribution to the Secondary Cluster Node.
If you want to switch back to the Primary Cluster Node, for example, after the maintenance activity is completed, right click on the Primary Cluster Node name from the Cluster Administrator and select Start cluster service. Now both servers are running, but unless the cluster service encounters a problem with the Secondary Cluster Node, it will continue to direct Tivoli Software Distribution traffic to the Secondary Cluster Node. To return to the original situation of both nodes running, but the Primary Cluster Node taking precedence, you should stop and then start the Secondary Cluster Node.
In the event that the Primary Cluster Node fails while Tivoli Software Distribution is running, when you start Tivoli Software Distribution on the Secondary Cluster Node (see sub-step 4 on page on page 18) you will be able to carry out the normal error recovery procedures described in the Distribution Scenarios chapter of Tivoli Software Distribution for Windows NT Quick Beginnings, Version 3.1.5, as if you were carrying them out from the Primary Cluster Node.
The following APARs are fixed in this CSD (the CSD also contains all APARs fixed in CSD XR21927, as listed in the README file accompanying that CSD):
|
PJ27933 |
Error FNDCL146E occurs adding installation parameters to a renamed target. |
|
PJ27913 |
DOS popup box generated on Tivoli Software Distribution Windows NT server for each fndtr and fndts during an SNA connection |
|
PJ27912 |
SNA over tcp/ip transport between NetView DM, Release 7 and Tivoli Software Distribution, Version 3.1.5 |
|
PJ27884 |
Error in heldc relc commands |
|
PJ26239 |
Cmd connection changes from held to released after nvdm rld or nvdm start |
|
PJ27721 |
Generating change file via CLI update of GUI catalog takes long time. |
|
PJ27744 |
FNDFS047E: received in fndlog at sd/aix when sending a 0 byte file to replace an existing file with destruction=a and disp=old |
|
PJ27755 |
FNDCM024E first token is overwritten |
|
PJ27756 |
FNDCM024E first token is overwritten |
|
II12871 |
Host integration server 5.0 is now supported on Tivoli Software Distribution, Version 3.1.5 on Windows 2000 platform. |
|
DE12772 |
The updak command doesn’t run correctly |
This section of the README contains information relevant to systems running Novell Netware.
If you are a Windows user, and you want to read the online information stored in the SD4NW\BOOKS directory, use the XVIEW tool. At the Windows workstation insert the Tivoli Software Distribution, Version 3.1.5 CSD XR22091 CD-ROM in the CD drive and enter the following command:
XVIEW CD_DRIVE\SD4NW\BOOKS filename.inf /SHOW
where filename is the name of the file that contains the information that you want to read. For example, if you want to read the Tivoli Software Distribution, Version 3.1.5 Quick Beginnings for NetWare manual, enter:
XVIEW CD_DRIVE\SD4NW\BOOKS FNDNWMST.inf /SHOW
The XVIEW tool is stored in the SD4W31\DOC directory.
The following section provides details of the support and limitation criteria for Tivoli Software Distribution, Version 3.1.5 running under Novell Netware
STS APPC support is not available at this time for:
· Server to server connections
· Server to client connections
TCP/IP 3.00H (or later) must be loaded to use the Software Distribution for NetWare product.
Asynchronous support is not available at this time.
Do not use a Software Distribution user name that contains more than 8 characters.
In the Configuration Parameter dialog of the server installation procedure, configure the server name and workstation address as follows:
· The server name should be equal to the workstation address. It represents the name of the software distribution server.
· The workstation address is the host name of the workstation where the software distribution server is installed. The installation procedure configures them with the same name by default.
· If you want the server name and configuration name to be different, edit the nvdm.cfg configuration file of each CLIENT to change the SERVER section as follows:
SERVER: <ServerName> <Protocol> <ServerWorkstationAddress>
where the ServerName and ServerWorkstationAddress must match the server name and workstation address specified for the server; and the protocol field is TCP/IP.
If you do not modify the server section of the nvdm.cfg file the client cannot connect to the server.
This section explains how to use the CSD XR22091 to upgrade existing installations of Tivoli Software Distribution to this CSD level of Version 3.1.5, and to make scratch installations of Tivoli Software Distribution, Version 3.1.5 at this CSD level. It requires that you have the licensed code images of Tivoli Software Distribution, Version 3.1.5, either the GA version or the upgrade installed with XR21925. If you have already installed CSD XR22074 on either of these two levels, you can now install CSD XR22091 on top. It is assumed that you will be using one NetWare Server as a Preparation Site and carrying out attended or unattended installations of the Tivoli Software Distribution, Version 3.1.5 Server and/or Client software on this and other NetWare Servers. If you have not already set up a server as a Preparation Site, you are strongly recommended to do so.
The details below describe how to prepare the Tivoli Software Distribution, Version 3.1.5 CSD XR22091 code images on the Preparation Site, and then provide four scenarios for different types of upgrade/installation:
· Attended upgrade of Tivoli Software Distribution, Version 3.1.5 Server to this CSD level or scratch installation of Tivoli Software Distribution, Version 3.1.5 Server at this CSD level
· Unattended upgrade of Tivoli Software Distribution, Version 3.1.5 Server to this CSD level
· Attended upgrade of Tivoli Software Distribution, Version 3.1.5 Client to this CSD level or scratch installation of Tivoli Software Distribution, Version 3.1.5 Client at this CSD level
· Unattended upgrade of Tivoli Software Distribution, Version 3.1.5 Client to this CSD level
The following are assumed:
· The code images for Tivoli Software Distribution, Version 3.1.5 are stored on a NetWare server, under the directory SD4NW (if this is not currently the case, the README.TXT for Tivoli Software Distribution, Version 3.1.5 shows you how to set up the code images).
· The NetWare server is also used as the Preparation Site
Before carrying out any of the upgrade/installation scenarios it is necessary to upgrade the Tivoli Software Distribution Code Images at the Preparation Site to this CSD level of Version 3.1.5, creating them from scratch if necessary. This site can then be used as the base for executing the upgrade and installation scenarios described below.
For this preparation activity you require the code images for Tivoli Software Distribution, Version 3.1.5 on a preparation site workstation, or the Tivoli Software Distribution, Version 3.1.5 CD-ROM (LK3T-5087-00).
If the Preparation Site does not already contain the Tivoli Software Distribution, Version 3.1.5 code images, you should add them, following the instructions in the README.TXT file of either the Tivoli Software Distribution, Version 3.1.5 GA release or the Tivoli Software Distribution, Version 3.1.3 with CSD XR21925 applied.
To upload the Tivoli Software Distribution, Version 3.1.5 CSD XR22091 code images to the preparation site:
1. Place the Tivoli Software Distribution, Version 3.1.5 CSD XR22091 CD-ROM in the CD-ROM drive; for these scenarios it is assumed to be the E: drive
2. At the NetWare requester, map the NetWare volume where you want to store the code images; for these scenarios it is assumed to be K:
3. Create the SD4NW directory on the K: drive of the Preparation Site
4. From this directory entering the following command:
XCOPY E:\SD4NW\*.* /s /e K:\SD4NW
After completing this step, the following structure is created under the K:\SD4NW directory:
K:\ SD4NW\ | |\ <DIR> BOOKS |\ <DIR> CLIENT\ | |LIST |PINSTALL.NLM |PRODUCTS.TME |CLIENT.PRF |CRTPRF.CMD |FNDSDCLT.SIG |FNDSWINV |\ <DIR> BIN |\ <DIR> SERVER\ | |LIST |NVDM.CFG |PRODUCTS.TME |SERVER.PRF |CRTPRF.CMD |FNDSDSRV.SIG |FNDSWINV |PINSTALL.NLM |TABLEG.DAT |\ <DIR> DB|\ <DIR> BIN |
Note that this preparation stage has only upgraded the code images; you should now upgrade your servers and clients using one of the following scenarios.
This scenario is used if you wish to upgrade Tivoli Software Distribution, Version 3.1.5 Server to Version 3.1.5 or install Tivoli Software Distribution, Version 3.1.5 Server from scratch in an attended way on a NetWare Server.
This scenario assumes the following conditions:
· The code images of the CSD XR22091 have already been uploaded onto a NetWare Preparation Site in the K:\SD4NW directory.
· The NetWare Server has Tivoli Software Distribution, Version 3.1.5 Server, or Tivoli Software Distribution, Version 3.1.3, with CSD XR21925 installed.
· The NetWare Server has a version of NetWare installed which is compatible with this CSD level of Tivoli Software Distribution, Version 3.1.5 (see the software prerequisites section in Tivoli Software Distribution for NetWare Quick Beginnings, Version 3.1.5).
Before starting the installation, backup the existing installation of Tivoli Software Distribution on the Server (you can do this simply by copying all files and subdirectories within the program folder to an alternate location on the system).
The upgrade/installation steps are as follows:
1. At the Server console, enter the following command:
Load <NW_VOLUME>:SD4NW\SERVER\pinstall
The Tivoli Software Distribution, Version 3.1.5 for NetWare Main Menu window appears.
2. On the Main Menu, specify whether you are installing on this NetWare Server or another NetWare Server, and press Enter. The Destination Directory window appears.
3. In the Destination Directory field, enter the name of the destination directory, and press Enter. The default value is SYS:SOFTDIST. The CSD Installation Options window appears.
4. If Tivoli Software Distribution, Version 3.1.5 Server or Tivoli Software Distribution Server, Version 3.1.3 with CSD XR21925 is already installed in the target installation directory, the following message appears:
The Target directory contains the same release.
In this event, choose one of the following options:
· If you want to remove Tivoli Software Distribution, Server for NetWare, and install Tivoli Software Distribution, Server for NetWare, Version 3.1.5 at this CSD level select Remove the directory contents and install from scratch and press Enter.
Tivoli Software Distribution, Server for NetWare, is removed and a new installation starts, as described in “Installing a Tivoli Software Distribution, Version 3.1.5 for NetWare Server”, in the Tivoli Software Distribution for NetWare Quick Beginnings, Version 3.1.5. If you select this option the existing network configuration will be deleted.
· If you want to copy the NLMs files only, select Refresh the NLMs and press Enter.
If you select this option the existing network configuration will be saved.
· If you want to keep Tivoli Software Distribution Server for NetWare and install Tivoli Software Distribution, Version 3.1.5 CSD XR22091 for NetWare in another directory, select Choose a different target directory and press Enter.
A new installation starts as described in “Installing a Tivoli Software Distribution, Version 3.1.5 for NetWare Server,” in the Tivoli Software Distribution for NetWare Quick Beginnings, Version 3.1.5.
If Tivoli Software Distribution is not installed in the target directory, a new installation starts as described in “Installing a Tivoli Software Distribution, Version 3.1.5 for NetWare Server,” in the Tivoli Software Distribution for NetWare Quick Beginnings, Version 3.1.5.
This scenario is used if you wish to upgrade Tivoli Software Distribution, Version 3.1.5 Server to this CSD level, in an unattended way, on a NetWare Server.
You run the scenario from a Preparation Site where you have already downloaded the code images (see Preparing the Code Images of the CSD on the Preparation Site on page 22).
This scenario assumes the following conditions:
· The Tivoli Software Distribution, Version 3.1.5 CSD XR22091 code images have already been uploaded onto a NetWare Preparation Site in the K:\SD4NW directory.
· The target Server has Tivoli Software Distribution, Version 3.1.5 for NetWare Server, or Tivoli Software Distribution Version 3.1.3 for NetWare Server with CSD XR21925 installed.
· The target Server has a version of NetWare installed which is compatible with Tivoli Software Distribution, Version 3.1.5 (see the software prerequisites section in Tivoli Software Distribution for NetWare Quick Beginnings, Version 3.1.5).
To upgrade the Tivoli Software Distribution, Version 3.1.5 for NetWare to this CSD level on a NetWare Server in unattended mode, perform the following steps at the Preparation Site server:
1. Customize the SOURCE NAME in the SERVER.PRF profile in the directory K:SD4NW\SERVER\ to refer to the specific volume where the product images are stored. A sample response file is as follows:
GLOBAL NAME: SD4NW.XR22091.SERVER.REF.315CHANGE FILE TYPE: NWGENOBJECT: SOURCE NAME: XR22091:SD4NW\SERVER\FNDSDSRV.SIG TARGET NAME: $(FILEPATH)FNDSDSRV.SIG TYPE: FILE ACTION: COPY OBJECT:SOURCE NAME: XR22091:SD4NW\SERVER\BIN\*.* TARGET NAME: $(FILEPATH)bin\*.* TYPE: FILE ACTION: COPY |
You should change the volume XR22091 where it occurs in both source name keys, to the volume where the SD4NW directory containing the code files is located, for example: SYS.
2. At the server console use the following command to build your profile:
load nvdm bld K:SD4NW\SERVER\SERVER.PRF
This command creates the SD4NW.XR22091.SERVER.REF.315 change file in your catalog.
3. Use the following command to install the change file on the server:
load nvdm inst SD4NW.XR22091.SERVER.REF.315 –w <swd_server>
4. Use the following commands to stop and start the Tivoli Software Distribution, Version 3.1.5 for NetWare server:
load fnddown load fndload
When you start the server all the code changes will be applied.
This scenario is used if you wish to upgrade Tivoli Software Distribution, Version 3.1.5 Client to this CSD level or install Tivoli Software Distribution, Version 3.1.5 Client from scratch at this CSD level in an attended way on a NetWare Client.
This scenario assumes the following conditions:
· The code images of the CSD XR22091 have already been uploaded onto a NetWare Preparation Site in the K:\SD4NW directory.
· The NetWare Server has at least Tivoli Software Distribution, Version 3.1.5 Client, or Tivoli Software Distribution, Version 3.1.3 Client, with CSD XR21925 installed.
· The NetWare Server has a version of NetWare installed which is compatible with Tivoli Software Distribution, Version 3.1.5 (see the software prerequisites section in Tivoli Software Distribution for NetWare Quick Beginnings, Version 3.1.5).
Before starting the installation, backup the existing installation of Tivoli Software Distribution on the Client (you can do this simply by copying all files and subdirectories within the program folder to an alternate location on the system).
The upgrade/installation steps are as follows:
1. At the Server console (Preparation Site), enter the following command:
Load <NW_VOLUME>:SD4NW\CLIENT\pinstall
The Tivoli Software Distribution, Version 3.1.5 for NetWare Main Menu window appears.
2. On the Main Menu, specify whether you are installing the Client software on this NetWare Server or another NetWare Server, and press Enter.
The Destination Directory window appears.
3. In the Destination Directory field, enter the name of the destination directory, and press Enter. The default value is SYS:SOFTDIST. The CSD Installation Options window appears.
4. If Tivoli Software Distribution, Version 3.1.5 Client is already installed in the target installation directory, the following message appears:
The Target directory contains the same release.
In this event, choose one of the following options:
· If you want to remove Tivoli Software Distribution, Client for NetWare and install Tivoli Software Distribution, Version 3.1.5, Client for NetWare, at this CSD level, select Remove the directory contents and install from scratch and press Enter.
Tivoli Software Distribution, Version 3.1.5, Client for NetWare, is removed and a new installation starts, as described in “Installing a Tivoli Software Distribution, Version 3.1.5 for NetWare Client”, in the Tivoli Software Distribution for NetWare Quick Beginnings, Version 3.1.5. If you select this option the existing network configuration will be deleted.
· If you want to copy the NLMs files only, select Refresh the NLMs and press Enter.
If you select this option the existing network configuration will be saved.
· If you want to keep the existing version of Tivoli Software Distribution, Version 3.1.5, Client for NetWare, and install Tivoli Software Distribution, Version 3.1.5, Client for NetWare, at this CSD level in another directory. Select Choose a different target directory and press Enter.
A new installation starts as described in “Installing a Tivoli Software Distribution, Version 3.1.5 for NetWare Client,” in the Tivoli Software Distribution for NetWare Quick Beginnings, Version 3.1.5.
If Tivoli Software Distribution is not installed in the target directory, a new installation starts as described in “Installing a Tivoli Software Distribution, Version 3.1.5 for NetWare Client,” in the Tivoli Software Distribution for NetWare Quick Beginnings, Version 3.1.5.
This scenario is used if you wish to upgrade Tivoli Software Distribution, Version 3.1.5 Client to this CSD level, in an unattended way, on a NetWare Client.
You run the scenario from a Preparation Site where you have already downloaded the code images (see Preparing the Code Images of the CSD on the Preparation Site on page 22).
This scenario assumes the following conditions:
· The Tivoli Software Distribution, Version 3.1.5 CSD XR22091 code images have already been uploaded onto a NetWare Preparation Site in the K:\SD4NW directory.
· The target Client has Tivoli Software Distribution, Version 3.1.5 for NetWare Client, or Tivoli Software Distribution Version 3.1.3 for NetWare Client with CSD XR21925 installed.
· The target Client has a version of NetWare installed which is compatible with Tivoli Software Distribution, Version 3.1.5 (see the software prerequisites section in Tivoli Software Distribution for NetWare Quick Beginnings, Version 3.1.5).
To upgrade the Tivoli Software Distribution, Version 3.1.5 for NetWare to this CSD level on a NetWare Client in unattended mode, perform the following steps at the Preparation Site server:
1. Customize the SOURCE NAME in the CLIENT.PRF profile in the directory K:SD4NW\CLIENT\ to refer to the specific volume where the product images are stored. A sample response file is as follows:
GLOBAL NAME: SD4NW.XR22091.CLIENT.REF.315CHANGE FILE TYPE: NWGEN OBJECT:SOURCE NAME: XR22091:SD4NW\CLIENT\FNDSDCLT.SIG TARGET NAME: $(FILEPATH)FNDSDCLT.SIG TYPE: FILE ACTION: COPY OBJECT:T: SOURCE NAME: XR22091:SD4NW\CLIENT\BIN\*.NLM TARGET NAME: $(FILEPATH)bin\*.NLM TYPE: FILE ACTION: COPY OBJECT:SOURCE NAME: XR22091:SD4NW\CLIENT\BIN\*.NCF TARGET NAME: $(FILEPATH)bin\*.NCF TYPE: FILE ACTION: COPY OBJECT:SOURCE NAME: XR22091:SD4NW\CLIENT\BIN\FNDCOMSG.CAT TARGET NAME: $(FILEPATH)bin\FNDCOMSG.NEW TYPE: FILE ACTION: COPY |
You should change the volume XR22091 where it occurs in the source name keys, to the volume where the SD4NW directory containing the code files is located, for example: SYS.
2. At the preparation site server console use the following command to build your profile:
load nvdm bld K:SD4NW\CLIENT\CLIENT.PRF
This command creates the SD4NW.XR22091.CLIENT.REF.315 change file in your catalog.
3. Use the following command to install the change file on the server:
load nvdm inst SD4NW.XR22091.CLIENT.REF.315 –w <swd_client>
4. Use the following commands to stop and start the Tivoli Software Distribution, Version 3.1.5 for NetWare client:
load fnddown load fndload
When you start the client all the code changes will be applied.
Use the FNDDBCMP.NLM tool to compress the files of the Tivoli Software Distribution, Version 3.1.5 for NetWare database. It physically deletes all the records that are logically flagged to be deleted in the database files. In some cases, it can recover corrupted database files.
Use the FNDCFG.NLM tool to directly configure, start, stop, and monitor the Tivoli Software Distribution, Version 3.1.5 for NetWare from the console. It is a menu-driven tool.
The following APARs are fixed in this CSD (the CSD also contains all APARs fixed in CSD XR22074, as listed in the README file accompanying that CSD):
|
PJ27885 |
Error in heldc relc commands |
|
PJ27940 |
Error FNDCL146E occurs adding installation parameters to a renamed target. |
|
PJ26618 |
Tivoli Software Distribution for AIX remote communications queues remain in hold status after the product is restarted. |
|
PJ26635 |
Cmd connection changes from held to released after nvdm rld or nvdm start |
|
DE12772 |
The updak command doesn’t run correctly |
|
DE12776 |
nvdm uninst doesn’t work on Netware |
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, and to make scratch installations of Tivoli Software Distribution, Version 3.1.5 at this PTF level, using PTF U475024. It requires that you have the licensed code images of Tivoli Software Distribution, Version 3.1.5, either the GA version or the upgrade installed with PTF U469697. If you have already installed PTF U474354 on either of these two levels, you can now install PTF U475024 on top.
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.
· Upgrade Tivoli Software Distribution for AIX Client, Version 3.1.5 to this PTF level, on an AIX server, using the provided Change File
· Upgrade Tivoli Software Distribution for AIX Client, 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.
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:
· Either Tivoli Software Distribution, Version 3.1.5 GA release or Tivoli Software Distribution Version 3.1.4 plus one of the following minimum combinations of PTFs is installed at the local computer, depending on whether it is a server, client or mobile client:
|
Server |
U475024, U478257, U478286 |
|
Client |
U478259, U478257, U478286 |
|
Mobile Client |
U478260, U478257, U478286 |
· 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 packages:
|
Package name |
Contents |
|
netviewdm6000.3.1.5.0.U475024 |
Base and Server components |
|
netviewdm6000.3.1.5.0.U478259 |
Client components |
|
netviewdm6000.3.1.5.0.U478257 |
En_US Documentation |
|
netviewdm6000.3.1.5.0.U478286 |
en_US Documentation |
|
netviewdm6000.3.1.5.0.U478260 |
Mobile Client Components |
They are found on the PTF U475024 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:
1. Run SMIT
2. Select install-update
3. Select Install and Update from ALL Available Software
4. Enter the required information on the displayed screen
5. 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:
· Either Tivoli Software Distribution, Version 3.1.5 GA release or Tivoli Software Distribution Version 3.1.4 plus the following minimum combination of PTFs is installed at the AIX server: U469697, U474028 and U474029
· The code images are available from the CD-ROM of the PTF
On an AIX Preparation Site do the following:
1. Create the directory /prep and go there
2. Download the following binary file from the /SD4AIX/update/ directory on the PTF U475024 CD-ROM into the /prep directory:
AIXS3150.TARZBIN
3. Rename the above file to AIXS3150.TARBIN.Z using the command
mv AIXS3150.TARZBIN AIXS3150.TARBIN.Z
4. Uncompress the file AIXS3150.TARBIN.Z using the command
uncompress AIXS3150.TARBIN.Z
5. Unpack the TAR file using the command
tar –xvf AIXS3150.TARBIN
6. If the option: netviewdm6000.remoteadmin.obj is installed prepare the remote admin Change File using the command:
nvdm bld /prep/profile.admin
7. In all cases (servers and focal points), prepare the server Change File using the command:
nvdm bld /prep/profile
8. Exit from that directory.
From any administration site:
1. If the option: netviewdm6000.remoteadmin.obj is installed issue the following command:
nvdm inst –vs IBM.NDM6000.REMOTEADMIN.REF.3150.U475024 > -w <server> -e
2. In all cases issue the following commands:
nvdm inst –vs IBM.NDM6000.BASE.REF.3150.U475024 > -w <server> -e nvdm cat IBM.NDM6000.SCRIPT.REF.3150.U475024 > /prep/linkrbasy –o Procedure nvdm act –w<server> > -m<server>:IBM.NDM6000.SCRIPT.REF.3150.U475024 –f
Should it be necessary to de-install the upgrade:
1. If the option: netviewdm6000.remoteadmin.obj is installed issue the following command:
nvdm rem –vs IBM.NDM6000.REMOTEADMIN.REF.3150.U475024 -w <server>
2. In all cases issue the following commands:
nvdm rem –vs IBM.NDM6000.BASE.REF.3150.U475024 –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:
· Either Tivoli Software Distribution, Version 3.1.5 GA release or Tivoli Software Distribution Version 3.1.4 plus the following minimum combination of PTFs is installed at the AIX server: U469697, U474028 and U474029
· The code images are available from the CD-ROM of the PTF
On an AIX Preparation Site do the following:
1. Create the directory /prep and go there
2. Download the following binary file from the /SD4AIX/update/ directory on the PTF U475024 CD-ROM into the /prep directory:
AIXS3150.TARZBIN
3. Rename the above file to AIXS3150.TARBIN.Z using the command:
mv AIXS3150.TARZBIN AIXS3150.TARBIN.Z
4. Uncompress the file AIXS3150.TARBIN.Z using the command:
uncompress AIXS3150.TARBIN.Z
5. 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.
1. Prepare the server Change File using
nvdm bld /prep/profile.nonreboot
2. Exit from that directory.
3. 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.U475024.EXECS >/prep/_fndexecs.sh –o Procedure
nvdm exec IBM.NDM6000.BASE.REF.3150.U475024.EXECS >-w<server>
b. To upgrade the server:
nvdm inst IBM.NDM6000.BASE.REF.3150.U475024.NR >-w <server> -e
c. Should it be necessary to de-install the upgrade:
nvdm rem IBM.NDM6000.BASE.REF.3150.U475024.NR > -w <server>
NON-REMOVABLE
a. To upgrade the server:
nvdm inst IBM.NDM6000.BASE.REF.3150.U475024.NR >-w <server> -e –n
If you DO HAVE the option: netviewdm6000.remoteadmin.obj installed, from any administration site follow the steps below.
1. Prepare the server Change File using the command:
nvdm bld /prep/profile.admin.nonreboot
2. Exit from that directory.
3. You can upgrade the server in a REMOVABLE or a NON-REMOVABLE way:
REMOVABLE
a. Enable the REMOVABLE option for the remote admin option:
nvdm cat IBM.NDM6000.REMOTEADMIN.REF.3150.U475024.EXECA > /prep/_fndexeca.sh –o Procedure nvdm exec IBM.NDM6000.REMOTEADMIN.REF.3150.U475024.EXECA > -w<server>
b. To upgrade the server:
nvdm inst IBM.NDM6000.REMOTEAMN.REF.3150.U475024.NR > -w <server> -e
c. Should it be necessary to de-install the upgrade:
nvdm rem IBM.NDM6000.REMOTEADMIN.REF.3150.U475024.NR > -w <server>
NON-REMOVABLE
a. To upgrade the server:
nvdm inst IBM.NDM6000.REMOTEADMIN.REF.3150.U475024.NR >-w <server> -e –n
This scenario is used to update an AIX Client running Tivoli Software Distribution, Version 3.1.5 for AIX Client, to this PTF level; the upgrade requires the client to be rebooted.
This scenario assumes the following conditions:
· Either Tivoli Software Distribution, Version 3.1.5 GA release or Tivoli Software Distribution Version 3.1.4 plus the following minimum combination of PTFs is installed at the AIX client: U474027, U474028 and U474029.
· The code images are available from the CD-ROM of the PTF
On an AIX Preparation Site do the following:
1. Create the directory /prep and go there
2. Download the following binary file from the /SD4AIX/update/ directory on the PTF U475024 CD-ROM into the /prep directory:
AIXC3150.TARZBIN
3. Rename the above file to AIXC3150.TARBIN.Z using the command
mv AIXC3150.TARZBIN AIXC3150.TARBIN.Z
4. Uncompress the file AIXC3150.TARBIN.Z using the command
uncompress AIXC3150.TARBIN.Z
5. Unpack the TAR file using the command
tar –xvf AIXC3150.TARBIN
6. Prepare the client Change File using
nvdm bld /prep/profile
7. Exit from that directory.
From any administration site use the following commands:
nvdm inst –vs IBM.NDM6000.CLIENT.REF.3150.U478259 –w <target> -e
nvdm cat IBM.NDM6000.SCRIPT.REF.3150.U478259 >
/prep/linkrbasy –o Procedurenvdm act –w<target> -f
Should it be necessary to de-install the upgrade use the following commands:
nvdm rem –vs IBM.NDM6000.CLIENT.REF.3150.U478259 –w <target>
nvdm act –w <target> -f
This scenario is used to update an AIX client running Tivoli Software Distribution, Version 3.1.5 for AIX Client, to this PTF level; the upgrade does not require the client to be rebooted.
This scenario assumes the following conditions:
· Either Tivoli Software Distribution, Version 3.1.5 GA release or Tivoli Software Distribution Version 3.1.4 plus the following minimum combination of PTFs is installed at the AIX client: U474027, U474028 and U474029
· The code images are available from the CD-ROM of the PTF
On an AIX Preparation Site do the following:
1. Create the directory /prep and go there
2. Download the following binary file from the /SD4AIX/update/ directory on the PTF U475024 CD-ROM into the /prep directory:
AIXC3150.TARZBIN
3. Rename the above file to AIXC3150.TARBIN.Z using the command
mv AIXC3150.TARZBIN AIXC3150.TARBIN.Z
4. Uncompress the file AIXC3150.TARBIN.Z using the command
uncompress AIXC3150.TARBIN.Z
5. Unpack the TAR file using the command
tar –xvf AIXC3150.TARBIN
From any Administration Site:
1. Prepare the client Change File using
nvdm bld /prep/profile.nonreboot
2. Exit from that directory.
3. You can upgrade the client in a REMOVABLE or a NON-REMOVABLE way:
REMOVABLE
a. Enable the REMOVABLE option:
nvdm cat IBM.NDM6000.CLIENT.REF.3150.U478259.EXECC >/prep/_fndexecc.sh –o Procedure
nvdm exec IBM.NDM6000.CLIENT.REF.3150.U478259.EXECC –w<target>
b. To upgrade the client:
nvdm inst IBM.NDM6000.CLIENT.REF.3150.U478259.NR –w <target> -e
c. Should it be necessary to de-install the upgrade:
nvdm rem IBM.NDM6000.CLIENT.REF.3150.U478259.NR –w <target>
NON-REMOVABLE
a. To upgrade the client:
nvdm inst IBM.NDM6000.CLIENT.REF.3150.U478259.NR > -w <target> -e –n
The following APARs are fixed in this PTF (the PTF also contains all APARs fixed in PTF U474354, as listed in the README file accompanying that PTF):
|
IY19107 |
Error FNDCL146E occurs adding installation parameters to a renamed target. |
|
IY18306 |
Error in heldc relc commands |
|
II12729 |
Wrong global file name in _fndipsts.sh released with Tivoli Software Distribution for AIX, Version 3.1.5 (LK3T-5088-00) |
|
IY15760 |
FNDFS047E: received in fndlog for Tivoli Software Distribution for AIX when sending a 0 byte file to replace an existing file with destruction=a and disp=old |
|
IY19001 |
Customer has scheduler problem. Customer receives error messages ’FNDFS025E’ and ’FNDRS012E’. |
|
IX86905 |
nvdm updcm is not correctly transmitted to the focal point |
|
IY06222 |
Use of $serverlist and $targetlist transmission plan variables specification of targets or target groups on execpln command |
|
IY16576 |
FNDCM024E first token is overwritten |
|
IY16579 |
FNDCM024E first token is overwritten |
|
DE12772 |
The updak command doesn’t run correctly |