Softpanorama

May the source be with you, but remember the KISS principle ;-)
Contents Bulletin Scripting in shell and Perl Network troubleshooting History Humor

Installation of Fixpack 11 on TWS 8.2

8.2.0-TIV-TWS-FP0011

2.0 Installation

This section describes how to install Tivoli Workload Scheduler and Tivoli Workload Scheduler Connector Fix Pack 10. It is divided into the following sections:
*  2.1.1, "Windows"
*  2.1.2, "UNIX (IRIX, OSF, DYNIX, LINUX_PPC)"
*  2.1.3, "UNIX (AIX, HP-UX, Solaris Operating Environment, LINUX I386,
   LINUX S390) - Graphical Installation"
*  2.1.4, "UNIX (AIX, HP-UX, Solaris Operating Environment) - Alternate
   Installation"
*  2.2, "Additional Installation Instructions"
*  2.2.2, "Installation Log Files"
*  2.2.3, "Product Uninstall on Tier 1"
*  2.2.4, "Tivoli Workload Scheduler Connector"
*  2.3, "Tivoli Workload Scheduler Plus Module"

2.1 Applying the Fix Pack

Note: If the product was originally installed using the ISMP method, the
      fix pack should also be installed by this method. If another
      method is used to patch, you may experience various errors and a
      bad state of registry. Read 2.2, "Additional Installation
      Instructions" before installing the fix pack.

2.1.2 UNIX (IRIX, OSF, DYNIX, LINUX_PPC)

Follow these steps to apply the fix pack:

1. Download the operating system-specific MAESTRO.TAR file to the Tivoli
   Workload Scheduler home directory and untar it with the following
   command:
   tar xvf MAESTRO.TAR

   This creates the following two files:
   *  maestro.tar.Z
   *  customize

2. You may have to set the execute bit on the customize script. Use this
   command:
   chmod 755 customize

3. Unlink the host on which you are installing the patch from the IBM Tivoli Workload Scheduler network and shut down IBM Tivoli Workload Scheduler. Use the following commands:
   conman "unlink @!@; noask"
   conman "stop @!@; wait"
   conman "shut; wait"

4. Run the customize script with the -update option. Use the following command:
   customize -update -uname <tws_user>

2.1.3 UNIX (AIX, HP-UX, Solaris Operating Environment, LINUX I386, LINUX
      S390) - Graphical Installation

Follow these steps to apply the fix pack:

1. Download the operating system-specific directory, SETUP.jar and
   media.inf files on your system.
2. Unlink the host on which you are installing the patch from the IBM
   Tivoli Workload Scheduler network and shut down IBM Tivoli Workload
   Scheduler. Use the following commands:
   conman "unlink @!@; noask"
   conman "stop @!@; wait"
   conman "shut; wait"

3. Run SETUP.bin to install the fix pack and follow the instructions on
   the screen. When required, select the instance of the Tivoli Workload
   Scheduler on which you are installing the fix pack.

2.1.4 UNIX (AIX, HP-UX, Solaris Operating Environment) - Alternate Installation

1. On the patch CD, go to the directory named according to your  operating system.

2. Unlink the host you are installing the patch on from the IBM Tivoli
   Workload Scheduler network and shut down IBM Tivoli Workload
   Scheduler. Use the following commands:
   conman "unlink @!@; noask"
   conman "stop @!@; wait"
   conman "shut; wait"

3. Run the twspatch script, use the following option:
   ./twspatch -install -uname <tws_user>.

2.2 Additional Installation Instructions

2.2.1 New Installation Methods on Tier 1 Platforms

When you use the graphical installation or the command line installation you can perform the following actions:
*  Apply the fix pack in "undoable" mode (this means that it is possible to roll back the modified files).
*  Roll back an undoable fix pack.
*  Commit an undoable fix pack (this means that it will not be possible to roll back the fix pack).
*  Repair an already committed fix pack. This action allows you to restore an existing Tivoli Workload Scheduler instance to the current  committed level when a problem arises with a binary.

Depending on the fix pack installation state, you can perform the action as shown below:

+-----------------------+----------------------+----------------------+
| Initial state         | Action               | Final State          |
+-----------------------+----------------------+----------------------+
| -                     | apply                | IU                   |
+-----------------------+----------------------+----------------------+
| IU                    | commit               | IC                   |
+-----------------------+----------------------+----------------------+
| IU                    | roll back            | -                    |
+-----------------------+----------------------+----------------------+
| IC                    | repair               | IC                   |
+-----------------------+----------------------+----------------------+


where:
*  IU = installed undoable
*  IC = installed and committed

If you have a Tivoli Workload Scheduler fix pack installed in "undoable
mode" (IU state) on your machine and you are applying a more recent
Tivoli Workload Scheduler fix pack on it, all the changes that you have
made when installing the previous Tivoli Workload Scheduler fix pack
will be committed before applying the newer ones. Therefore, if you undo
the fix pack you last installed, you will restore the previous fix pack
changes. These changes are permanent. The setup program discovers all
the Tivoli Workload Scheduler 8.2 instances existing on the machine.
After selecting one of these, it is possible to specify the required
action.

The table below shows the actions that are performed on your installed
fix packs when patching a Tivoli Workload Scheduler 8.2 instance:

+-----------------------+----------------------+----------------------+
| Initial state         | Action               | Final State          |
+-----------------------+----------------------+----------------------+
| FP01=IU               | apply FP02           | FP01=IC+FP02=IU      |
| FP01=IC               |                      |                      |
+-----------------------+----------------------+----------------------+
| FP01=IC+FP02=IU       | commit FP02          | FP02=IC              |
|    FP02=IU            |                      |                      |
+-----------------------+----------------------+----------------------+
| FP01=IC+FP02=IU       | roll back FP02       | FP01=IC              |
|    FP02=IU            |                      |                      |
+-----------------------+----------------------+----------------------+


An alternative way to use the graphical installation is the silent
installation. The silent installation requires the response file
customization. A template of the response file is available on both CDs,
in the RESPONSE_FILE directory.

You can use the silent installation by launching the SETUP.bin
(SETUP.exe on Windows Systems) program as follows:

./SETUP.bin -options /opt/tws/FP02/patchInstall.txt -silent

where patchInstall.txt is a customized response file.

On AIX, HP-UX ,Solaris Operating Environment, Linux_IX86, and Linux_S390
platforms you can install the fix pack using the twspatch script file.
The synopsis of twspatch is:
*  ./twspatch -{install | undo | commit | repair} -uname <TWS user>

The fix pack installation is recorded in the TWSRegistry.dat file adding
the following lines:

product_dir=/home/root/.swdis/work
working_dir=/home/root/.swdis/backup
trace_level=0
trace_size=1000000
sen_timeout=300
autopack_dir=/home/root/.swdis/autopack
staging_dir=/home/root/.swdis/service
user_file_variables=/home/root/.swdis/swdis.var
import_libraries=spd,libecimp

where:
*  $(SWD-OS-NAME) depends on the platform where you are installing.
*  $(tws_user) is the Tivoli Workload Scheduler instance owner.
*  $(patch_id) is the fix pack number.

On Tier 2 Platforms, the existing customize script is available for
installation. For more details about the new installation technologies
refer to the "Planning and Installation Guide".

2.2.2 Installation Log Files

To check the installation status look in the following log files:

/tmp/FP_TWS_<platform>_<TWS user>^8.2.0.01.log (%TEMP% on windows)
/tmp/TWSIsmp.log (%TEMP% on windows)
/tmp/TWSinstall.log (%TEMP% on windows)

2.2.2.1 Space needed for backup copy creation

On AIX, HP-UX, Solaris Operating Environment, LINUX-I386, LINUX-S390 and
Windows platforms the fix pack installation is SPB Technology based (as
for Tivoli Workload Scheduler 8.2 GA installation). Every time you
install a Tivoli Workload Scheduler 8.2 fix pack it is installed in
"undoable mode".

"Undoable" means that a backup copy of the existing binaries is created
automatically before replacing them with the newer ones. This
installation mode allows the modifications introduced by the installed
fix pack to be rolled back until you commit them.

You should commit the fix pack after checking the installation. By
default, on UNIX Systems the CM/SPB working directory is set to the home
directory of the installing user and for Tivoli Workload Scheduler
installation the installing user is root. This is a CM4.2 configuration
based on the /etc/Tivoli/swdis.ini file on UNIX Systems
(%WINDIR%/swdis.ini on Windows systems). It stores the following
information (needed by CM4.2 to run): product_dir=/home/root/.swdis/work
working_dir=/home/root/.swdis/backup trace_level=0 trace_size=1000000
sen_timeout=300 autopack_dir=/home/root/.swdis/autopack
staging_dir=/home/root/.swdis/service
user_file_variables=/home/root/.swdis/swdis.var
import_libraries=spd,libecimpwhere the root home directory is:

 /home/root.

 So, for every Tivoli Workload Scheduler 8.2 installation that you
patch, you will find:
*  A backup copy under the /home/root/.swdis/backup directory. Every
   backup copy will be removed when committing the fix pack for a
   specific Tivoli Workload Scheduler 8.2 installation.
*  An entry in the CM 4.2 catalog. The CM wdlssp command displays a list
   of all the products installed with the help of Configuration Manager.

The space requirements for creating the backup copy are shown in the
following table:

+---------------------------------+-----------------------------------+
| Platform                        | Space (Mb)                        |
+---------------------------------+-----------------------------------+
| Windows                         | 10                                |
+---------------------------------+-----------------------------------+
| Unix                            | 25                                |
+---------------------------------+-----------------------------------+


Before installing a fix pack check the /home/root capability. If there
is not enough space you need to change the CM 4.2 configuration by
performing the following steps:
1. Open the swdis.ini file and replace the path /home/rootby setting a
   path with the required capability for all path variables defined in
   the swdis.ini file.
2. Move the already existing .swdis directory from /home/root to
   /<new_path> to save the existing information.

2.2.3 Product Uninstall on Tier 1

Using the ISMP setup program (AIX, Solaris Operating Environment, HP-UX,
LINUX, Windows): Run the Tivoli Workload Scheduler 8.2 GA ISMP
uninstaller program to uninstall the Tivoli Workload Scheduler 8.2
instance and the related installed fix pack. See Tivoli Workload
Scheduler 8.2 Installation and Planning Guide for more details about the
ISMP uninstaller program.

Using alternate installation (AIX, Solaris Operating Environment, HP-UX,
LINUX_I386 and LINUX_S390): Run the following two steps to uninstall the
Tivoli Workload Scheduler:

1. Uninstall the current fix pack as follows:
   <TWS home>/twspatch -remove -uname <TWS user>

2. Uninstall Tivoli Workload Scheduler as follows:
   <TWS home/twsinst -uninst -uname <TWS user>

Note: The twspatch -remove command can only be used to uninstall the fix
      pack.

Both uninstall methods need a Tivoli Configuration Manager update before
you run them. Starting from this fix pack a new tool is available for
copying the needed software from the TWS 8.2 FPx images to the TWSHome
path. You will find the script named "copyCMcli" under all Tier 1
directories. The following is the copyCMcli script synopsis:

copyCMcli <source path> <target path>

Where:

<source path> -- path in which is contained the IBM Configuration
Manager CLI directory (AIX, Solaris Operating Environment, HP-UX,
LINUX_I386 and LINUX_S390).

<target path> -- IBM Tivoli Workload Scheduler installation path

2.2.4 Tivoli Workload Scheduler Connector

It is required that both the Tivoli Workload Scheduler master
workstation and the connector be at the same level. Therefore, when you
install this fix pack on the connector, make sure that you also install
the fix pack for the Tivoli Workload Scheduler engine on the master
workstation.

To install this fix pack, you must have the General Availability version
of the connector for IBM Tivoli Workload Scheduler 8.2, with or without
the previous fix pack.

To install the fix pack, follow these steps on the workstation that runs
the connector:

1. Insert the CD of the fix pack.
2. Open the Tivoli desktop and click on Desktop -> Install->Install
   Patch....
3. Select the installation path in the file browser of Select Media.
4. Follow the instructions listed in the Tivoli Job Scheduling Console
   User's Guide to complete installation.

2.3 Tivoli Workload Scheduler Plus Module

To apply the fix pack successfully on the Plus Module, you must have the
install_product and super authorization roles. Carry out the following
steps:
1. Using the Tivoli desktop, select the Install -> Install Patch...
   option from the Desktop menu to display the Install Patch dialog.
2. Press the Select Media... button to display the File Browser dialog.
3. Enter the path to the directory containing the patch in the Path
   Name: field.
4. Press the Set Media & Close button to return to the Install Patch
   dialog. The patch install list now contains the name of the patch.
   Select the patch by clicking on it.
5. Select the clients where you want to install this patch.
6. Press the Install button to install the patch."

The TWSPlus installation has been written to be supported only in C/en
LANG. Before installing TWSPlus perform the following steps to set the
framework locale to C:

1. LANG=C
2. export LANG
3. LC_ALL=C
4. export LC_ALL
5. locale=C
6. export locale
7. wsetlang -o
8. Restart the oserv
9. Start the TWSPlus installation

3.0 Contacting IBM Software Support

Before contacting IBM(R) Software Support with a problem, refer to the IBM Software Support site by accessing the following Web address:

http://www.ibm.com/software/support

To access Tivoli(R) support, click the Tivoli support link at the bottom
right of the page.

If you want to contact IBM Software Support, see the IBM Software
Support Guide at the following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software
Support, depending on the severity of your problem, and the following
information:
*  Registration and eligibility.
*  Telephone numbers, depending on the country in which you are located.
*  Information you must have before contacting IBM Software Support.



Etc

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes.   If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. 

ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.  

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least


Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.

The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Last modified: October 11, 2015