======================================================================== IBM ADSM for Windows NT PTF5 (Y2K) Read1st File ======================================================================== (c) Copyright IBM Corporation, 1997 The information in this document and the online help system is more up-to-date than in the hardcopy manuals. -------- Contents -------- 1.0 INTRODUCTION 1.1 What's New 2.0 INSTALLATION INSTRUCTIONS FOR ADSM FOR WINDOWS NT PTF5 2.2 Downloading the Package 2.3 Extracting and Installing the Package 3.0 INSTALLATION FEATURES 4.0 INSTALLATION CUSTOMIZATION 5.0 UNINSTALL 1.0 INTRODUCTION ----------------- 1.1 What's New --------------- o ADSM for Windows NT V2 Y2K Correction o New server security option o For the latest ADSM information please refer to ADSM for Windows NT V2 Y2K Correction ADSM has been updated to handle leap-year processing beyond the year 2000. New server security option ADSM has been updated to provide additional control related to the administrative authority required to issue selected commands that cause the ADSM server to write information to an external file. A new server option REQSYSAUTHOUTFILE has been added to control this processing. REQSYSAUTHOUTFILE YES: Specifies that system authority is required for administrative commands that cause the server to write to an external file. The commands and associated parameters that are controlled by this option are: - BACKUP VOLHISTORY when the FILENAMES parameter has been specified - BACKUP DEVCONFIG when the FILENAMES parameter has been specified - TRACE BEGIN when a file name has been specified REQSYSAUTHOUTFILE NO: Specifies that system authority is not required for administrative commands that cause the server to write to an external file (i.e. there is no change to the privilege class required to execute the command). The default is REQSYSAUTHOUTFILE YES. The explanation for ANR2035E has been updated to indicate that this message can be issued as a result of the server option REQSYSAUTHOUTFILE YES. Note, it is assumed that proper access controls are in place for the server options file dsmserv.opt. For the latest ADSM information please refer to http://www.storage.ibm.com/storage/software/adsm In this PTF you can review the readmes.hlp file for information on the individual components. You can review the readmes file from the ADSM for Windows NT program folder by clicking on the entry -- PTF5 (Y2K) README Files. A list of APARS fixed in this PTF is available in the file(s) ntptf4.fix and ntptf5.fix located in the server directory after installation. 2.0 INSTALLATION INSTRUCTIONS FOR ADSM FOR WINDOWS NT PTF5 ---------------------------------------------------------------------- 2.1 Downloading the Package ------------------------------------------ This package is available via anonymous ftp from machine: index.storsys.ibm.com login: anonymous password: yourname@your.company.com location: /adsm/fixes/v2r1/ntsrv/ptf5 The package contains 4 files ntptf5.txt -- this file ntptf5.fix -- fixinfo file that lists APARS fixed in this ptf unpack.bat -- bat file that will expand pkg using -d option ntptf5.exe -- the ptf5 distribution package 2.2 Extracting and Installing Package ------------------------------------- The following examples demonstrate how to download and extract this PTF. Summary: 1) create a temporary directory on your computer and cd into it 2) ftp to index.storsys.ibm.com, login, cd to the ntsrv ptf5 dir 3) In ASCII, ftp ntptf5.txt, ntptf5.fix and unpack.bat to your computer 4) In binary, ftp ntptf5.exe to your computer 5) From the new directory on your computer issue: unpack 6) view the readmes help file 7) stop any ADSM programs 8) stop any ADSM services 9) run setup 10) follow the directions displayed during setup Detailed example: 1) - c: - cd \ - mkdir ntdist - cd ntdist 2) - ftp index.storsys.ibm.com - Name (index.storsys.ibm.com:yourname): anonymous - Password: yourname@your.company.com - cd /adsm/fixes/v2r1/ntsrv/ptf5 3) - ascii - get ntptf5.txt - get ntptf5.fix - get unpack.bat 4) - binary - get ntptf5.exe 5) - unpack 6) - cd config - winhlp32 readmes - cd c:\ntdist 7) - If any ADSM programs are running stop them 8) - If any ADSM services are running stop them for example at a DOS prompt issue: net start | more - if you see ADSM Server issue: net stop "adsm server" 9) - setup 10) - follow the instructions 3.0 INSTALLATION FEATURES ---------------------------------------------------------------------- * If a previous version is detected the path to that version becomes the default installation directory. * A warning is displayed if you install an additional copy of ADSM into a location other than the previous copy. * If a component has never been installed but there is another existing component it will be the default installation directory. * If the installation program detects existing ADSM environment variables which may conflict with the installation, a warning dialog is issued. * During installation you now have the choice to uninstall previous versions of the 32-Bit Windows client including files and program folders * Existing options files are preserved and the new options file is saved in the appropriate directory with a name of dsm.new. * You should ensure that any previous ADSM components are not running before you do an install of this package. If the ADSM scheduler is running as a service for example and you try to go through the install you will see a message stating that a read-only file was encountered and it will ask if you want to replace anyway. If you say yes, the install will fail as the files cannot be overwritten while they are in use. If you say no, you run the risk of not having current versions. The best thing to do is to shut down any ADSM applications that are running before doing an ADSM install. * A manual cleanup of files that were generated by ADSM components is required after uninstall. These default files are located in the baclient and/or saclient directories. 4.0 INSTALLATION CUSTOMIZATION ---------------------------------------------------------------------- * You may supply customized options files by replacing ba_dsm.opt (for the backup-archive client), sa_dsm.opt (for the administrator client) and srv_dsm.opt (for the server) in the config directory of disk 1 with your own version. * You may replace the default readme.hlp file in the config directory of disk 1 with your own or you can choose not to have ADSM install a readme.hlp file by removing readme.hlp from the config directory. * You may generate an automatic response file for custom silent installs. 1) To automatically create a tailored setup.iss file use: setup -r Then go through the install of your choice. The dialogs you see and the answers you give will be recorded in a file called setup.iss. Installshield puts setup.iss in your windows system directory. To use this file response file, copy it into the same directory as setup.exe. This will be disk1 for floppy based installs. 2) To start ADSM setup in silent mode use: setup -s Setup will look for the response file setup.iss resident in the same directory as setup.exe. * You may now provide your own custom installation instructions to accompany ADSM. The customization initialization file customc.ini must reside in the config directory of disk 1. The parameters you must specify are: InstallReadme -- Yes - Install the specified file. No - Don't install the file. ReadmeFilename -- User supplied custom readme file placed in the config directory on install disk 1. ReadmeFileViewer -- Application to use to view the custom readme file. ReadmeCaption -- Program Group/Start menu item caption to use for custom readme file icon. ViewAfterInstall -- Yes - Force the file to be viewed after the the installation has completed. No - Do not view the file after installation has completed. 5.0 UNINSTALL ---------------------------------------------------------------------- The ADSM Uninstall program has been significantly enhanced in this PTF. You can now select multiple ADSM components to uninstall and you can also disable installshield prompting so that you can watch the entire process run automatically. Uninstall also supports a new silent uninstall mode. Should you prefer to perform a completely automated removal of all installed ADSM components, except personal data files, you may specify the /SILENTALL flag with your call to uninstal.exe. This mode of uninstal will not provide any further verification prompts, will stop any running ADSM services, and will silently remove all registry entries and components automatically. You will find the uninstal.exe program in the ADSM\SHARED directory of your installation; by default this is 'C:\WIN32APP\IBM\ADSM\SHARED'. You may run the silent uninstal by typing the following from a command prompt while in the ADSM\SHARED directory: uninstal /silentall