4.1.1-TMF-0104 is a patch for TMR servers, managed nodes, and gateways. No other patches or fixpacks need to be installed prior to the installation of 4.1.1-TMF-0104.
Download Description
Please see the download package for the full Readme.
Internal CMVC defect 216237
Symptoms: Some Framework applications use TLL to install a library
of tasks. If that installation fails, then when the wtll command is
run later, it may also fail. For instance, wtll may fail because the
system has run out of resources. Also, tmstat may show a large
number of transactions and the $DBDIR/odb.log file can be very large.
Internal CMVC defect 220450
Symptoms: If the select_gateway_policy is incorrectly specified, an
error similar to the following can appear in the endpoint manager
log file:
Internal CMVC defect 222879
Symptoms: If there are errors in user-written TLL (Task Library
Language) input to the wtll command, then executing wtll can cause
the task library and task repository to be out of sync.
Internal CMVC defect 223107
Symptoms: Extend an endpoint manager method so Software Distribution
can retrieve lists of endpoints faster.
APAR IZ14274
Symptoms: The wruntask command may terminate abnormally if an invalid
target, either a managed node or endpoint, is specified with the -h
option. For example,
@Endpoint:problem (ManagedNode): The task failed to execute.
@Endpoint:problem (ManagedNode): FRWTT0003E An instance named
"@Endpoint:problem" of resource "ManagedNode" was not found.
Segmentation Fault(coredump)
APAR IZ14739
Symptoms: Forwarding a notice group message on AIX causes commas to
be inserted throughout the message. This problem can also be seen in
applications (for instance, APM and SWD) that use the Framework's
send_support method to mail messages and the smtp_client.exe that is
used to mail a message on a Windows machine.
APAR IZ17892
Symptoms: When the Tivoli desktop is invoked from an Exceed session
on Windows, it can randomly crash on an AIX managed node.
Additional Information: This is also fixed in 4.1.1-TMF-0097LA.
APAR IZ22845
Symptoms: In some situations, the Endpoint Manager can terminate
abnormally. The last lines in epmgrlog before the failure show the
get_endpoints method has been called: "2008/05/02 12:10:06 4
528e68: get_endpoints: Requesting search for
123456789.13827.522+#TMF_Endpoint::Endpoint#".
APAR IZ23770
Symptoms: The backup script, objsnapshot, does not have the correct
PATH on Linux platforms to find the compress utility (if the
customer has not installed the compress utility).
APAR IZ23876
Symptoms: In non-English locales, the data in the last three lines
of "wep <ep>" output does not match the labels describing that data.
APAR IZ24316
Symptoms: If the "wtll" command passes invalid task implementation
pathnames to the installation code, there can be problems with the
task library and task repository because the installation code does
not correctly check the pathnames.
Additional Information: This is also fixed in 4.1.1-TMF-0096LA.
APAR IZ24819
Symptoms: Modify the Tivoli Scheduler so that it is possible to
drag-and-drop a job into the scheduler and pop up a dialog that
enables configuring parameters to the job, if the task to be
executed by the job was installed via TLL.
To enable this fix for the first time, execute the following shell
commands:
Each time a job is dragged-and-dropped into the scheduler, this
attribute is checked. Thus, it can be turned on and off as needed.
APAR IZ24823
Symptoms: In a situation where an application makes many method
calls (to endpoints), and Port Range is set for the gateway to limit
the number of available source ports, then many of these method
calls can fail with this error: "ipc_create_new_remote_client
failed: unable to connect to 9.48.130.27+4184: (31) FRWOG0011E
resource still in use", and this message can appear in the gatelog:
"2008/06/23 11:04:21 2 3036de48: create_session: failed on
9.48.130.27+4184".
The fix for this APAR extends the gateway retry mechanism to
downcalls. (See APARs IY83177 and IZ13656 for details on the gateway
retry mechanism.) The ep_conn_retry_mode parameter now allows values
for downcalls. Valid values are 0 - 7, which are bit combinations of
the following:
0 - Gateway will not retry any connection attempts
1 - Gateway will retry failed connections in EP login thread
2 - Gateway will retry failed connections in upcall threads
4 - Gateway will retry failed connections in downcall threads
APAR IZ26786
Symptoms: In some circumstances, scheduling a job on the 28th (or
later) day of the month with a monthly interval can result in the
next date for the job being on the 27th (i.e., one day earlier than
the expected date).
Prerequisites
None.
Installation Instructions
Applying the Patch:
1) Extract the patch:
On a Unix system:
Extract the contents into a scratch directory. For the purpose
of this release note, assume that the symbol $PATCH points to
this directory.
# cd $PATCH
# tar xvf 4.1.1-TMF-0104.tar
On a Windows 2000 system:
Extract the contents into a scratch directory. For the purpose
of this release note, assume that the symbol %PATCH% points to
this directory.
> %SystemRoot%\system32\drivers\etc\Tivoli\setup_env
> X:
^-- 'X' is drive letter where %PATCH% is found
> cd %PATCH%
> tar xvf 4.1.1-TMF-0104.tar
NOTE: If you are extracting the tar image on a Windows 2000
system, you will find an executable for tar in the TME
installation on Windows 2000 under bin/w32-ix86/tools/tar.exe.
2) If this patch is to be installed on a release level of 3.6 or
greater, follow these instructions for using Software
Installation Service (SIS). If not, skip to step 3 below.
NOTE: SIS can install Tivoli products on any hardware
platform supported by Tivoli, but there are some
hardware platforms on which SIS cannot be run. Please
check your SIS User's Manual for the list of platforms
on which SIS can be run.
NOTE: You must have the install_product and super authorization
roles to successfully install this patch.
a) From the Tivoli Desktop, pull down
Desktop --> Install --> Software Installation Service.
b) SIS will initialize, and bring up the Get Installation
Password Dialog. Enter your Installation Password.
c) Click the Install Button on the dialog which contains
the Tivoli image.
d) Click the Select Product Button on the Install Spreadsheet
Dialog.
e) Click the Import Product Button on the Select Product
Dialog.
f) Locate the media to 4.1.1-TMF-0104 using the file browser,
and select the PATCHES.LST file by double-clicking it.
g) Select 4.1.1-TMF-0104 in the Import Product Dialog, and
click the Import Button.
h) When the import is complete, click the OK Button on the
Global Progress Dialog.
i) Select 4.1.1-TMF-0104 in the Select Product Dialog, if it
is not already selected, and click the OK Button.
j) Now click the Select Machine Button on the Install
Spreadsheet Dialog.
k) Select the machine(s) you would like to install
4.1.1-TMF-0104 on and click the OK Button.
l) Click the appropriate cell(s) in the Install Spreadsheet
Dialog. (NOTE: This should yield an "X" in the cell(s)
for the machines you want to install 4.1.1-TMF-0104 to).
m) Click the Install Button.
n) Select the install algorithm you want to use on the
Installation Algorithm Dialog, and click OK.
o) SIS will perform the installation(s) you designated
in the Install Spreadsheet Dialog.
p) Installation is complete. Check the Additional
Installation Instructions section below.
3) Use the following steps to install the patch using the Tivoli
GUI install mechanism.
NOTE: You must have the install_product and super authorization
roles to successfully install this patch.
a) Select the "Install -> Install Patch..." option from the
"Desktop" menu to display the "Install Patch" dialog.
b) Press the "Select Media..." button to display the "File
Browser" dialog.
c) Enter the path to the directory containing the patch,
$PATCH, in the "Path Name:" field.
d) Press the "Set Media & Close" button to return to the
"Install Patch" dialog.
e) The patch install list now contains the name of the patch.
Select the patch by clicking on it.
f) Select the clients to install this patch on. This patch
needs to be installed on the TME server and on each
managed node client.
g) Press the "Install" button to install the patch.
Additional Installation Instructions:
After applying this patch, perform the following numbered steps to
restart the oservs on the TMR server and managed nodes / gateways.
1) From the TMR server, run the following command to shut down all
managed nodes / gateways:
odadmin shutdown clients
2) When the client oservs have all terminated, run the following
command to restart the TMR server:
odadmin reexec 1
3) Once the oserv on the TMR server has fully restarted, then run
the following command to restart the managed nodes / gateways:
This patch contains the Windows library TivoliAP.dll. Since
TivoliAP.dll may already be in use by Windows, the Windows system
must be rebooted after an upgrade (or a new installation where an
older version of TivoliAP.dll was in use) so that this new version
of TivoliAP.dll will be loaded into memory. If you do not reboot,
then Windows will continue to use the older TivoliAP.dll that was
previously loaded.
(The TivoliAP.dll being replaced is used by the Windows security
service. Due to this library being locked, we must follow the
Microsoft solution for handling locked libraries. This solution
dictates that we must reboot the Windows system to allow the locked
library to be replaced at boot time.)
Note: The version of TivoliAP.dll supplied in this patch is the same
as the version (28) supplied 4.1.1-TMF-0076 except for timestamp
information, but is different from all earlier versions. Thus, if
you are upgrading from 4.1.1-TMF-0076 (or later) to this patch, then
it is not necessary for the Windows box to be rebooted. For earlier
versions, however, there is no problem in continuing to run with an
older version of TivoliAP.dll except that certain fixes will not be
available. Thus, the reboot of a machine where this patch has been
applied can be deferred until a later time.
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
