Silent installation using an automatically generated response |file
|During the initial installation of the current version of Tivoli Workload Scheduler for z/OS, |you can create a response file based on the parameters of the initial |installation. You use this response file to run subsequent installations |with the same parameters. Creating an automatically generated response |file is recommended because all input is automatically validated by |the program.
|To perform a silent installation using an automatically generated |response file, perform the following steps:
|-
|
- Perform the initial installation using the following command:
|
-
|
- UNIX and Linux operating systems: |
-
|
./SETUP.bin -options-record local_dir/response_file.txt
|where response_file.txt is the name of the response |file to be created. The SETUP.bin file is located in the |root directory of the relevant installation DVD.
|
| - Windows operating |systems: |
-
|
SETUP.exe -options-record local_dir\response_file.txt
|where response_file.txt is the name of the response |file to be created. The SETUP.exe file is located int TWS\WINDOWS on |32-bit operating systems, and in TWS\WINDOWS_X86_64 on |64-bit operating systems.
|
|
The installation wizard is launched. Follow the prompts and |complete the installation (for details, see Installing with the installation wizard). |A response file is created in the directory that you specified in |the setup command.
|Although the response file contains the parameters |that you entered in the installation wizard, be aware that you might |need to edit the file for each subsequent installation. This depends |on the configuration of each workstation.
| ||Note:|The |response file that is created will contain unencrypted password information.
| - For all subsequent installations, enter the following command:
||||||||||||
UNIX and Linux | ./SETUP.bin -options local_dir/response_file.txt -silent
Windows | SETUP.exe -options local_dir\response_file.txt -silent
| - After each silent installation, review the installation messages |in the summary.log file to check that installation was |successful.