IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page | Contents ]


For the agent

APAR IY45495
A memory leak has been solved on agents running on Windows platforms, which, over a period of time, was causing excessive resource consumption.
APAR IY49454
On certain Windows platforms detailed below, the agent contacts the domain server to determine information about the user of a Windows application too frequently. This is causing performance problems.

The Windows agent platforms to which this problem applies are as follows:

After installing the fix, the agent will store the user information in its cache memory after the initial contact with the domain server.

APAR IY50092
On SUN platforms some scripts are prevented from running by the agent's kernel extension. For example, if you run the following command:
export DISPLAY=`who -m | awk -F"(" {'print $2'} | awk -F")" {'print $1'}`:0
the following error is received:
awk can not be executed

After installing the fix, the kernel extension no longer prevents such scripts from running.

APAR IY50094
On AIX platforms, the agent causes the operating system to loop if more than 15 different processes fail in less than 8 seconds. An operator cannot telnet or log in to the console.

After installing the fix, the agent correctly manages large numbers of failing processes in a short time.

APAR IY50187
On Windows, AIX and SUN platforms, under heavy system stress and in exceptional circumstances, a system kernel panic could occur during the unload of the Tivoli License Manager agent kernel extension. An unload occurs when the agent code is uninstalled, upgraded, or reinstalled, by any method (Web registration, the installagent command, or the agent self-update option on the runtime server).

The agent platforms to which this problem applies are as follows:

Other platforms are not affected by the problem that this fix resolves, and the fix should not be applied to agents running on them.

The fix requires the upgrading of the agent code on the runtime servers that serve agents running the above-listed operating systems. It then requires you to upgrade the agent code at each agent by first applying a utility provided with the fix, and then updating or re-installing the agent code. Full details are provided in Install the interim fix on the servers.

After installing the fix, the agent software can be unloaded without causing a kernel panic.

APAR IY50491
On Windows 9x platforms, after the agent is installed, some in-house programs, for example those developed using Power Builder version 4 or Sybase version 11.0.3, cannot run.

After installing the fix these programs can run.

Inventory scan transmission algorithm
On all platforms, if a large number of agents belong to the same division, the inventory scans cannot be handled by the runtime server because they are occurring in too short a time frame.

After receiving a request for a scan from the runtime server, the agent determines when to send the scan by using an algorithm that generates a random time for the transmission, based in part, on the number of agents, information supplied to it by the runtime server. This algorithm has, a maximum timeframe of 9 hours. Thus, with many agents in the division, the runtime server is experiencing a severe backlog of requests from agents, which affects its capability to respond immediately to license requests.

After installing the fix, the algorithm no longer has this limitation, and correctly schedules the scan transmission so that the runtime server can handle all requests.

Agent self-update on Windows NT(R)
On Windows NT platforms, the self-update of the agent did not work after installing the tlm-1.1.1-0002 interim fix (agent version 1.1.1.10). Agents attempting to self-upgrade terminated abnormally.

After installing this fix, the agent should self-update without problems.

Agent self-update on Windows 98 and ME
Agents on Windows 98 and ME platforms can now use the self-update facility, which did not work prior to the fix.
Deploying agents on unsupported platforms
It is possible to attempt the Web deployment of an agent on the unsupported Windows 2003 platform. The deployment appears to have worked, but as there is no kernel extension available to these agents, no license enforcement is possible..

After installing the fix, a Web deployment request for the Windows 2003 platform will be refused by the runtime server.


[ Top of Page | Previous Page | Next Page | Contents ]