Hi Neil:
According to Tivoli this is an open problem on all levels of TSM (see APAR
IC25335 below). The apar mentions that the performance counters have been
disabled.
Tim Rushforth
City of Winnipeg
[EMAIL PROTECTED]
APAR IC25335
============
NT EVENT VIEW REPORTS "PERFLIB" ERRORS AGAINST DSMCPERF.DLL.
ERROR DESCRIPTION:
The Win32 client at 3.1.0.7 introduced a new performance
monitoring function which includes the files:
dsmperf.dll
perfctr.ini
dsmccnm.h
In some cases, this is not installed properly and can have 2
separate results:
1. The NT Event Viewer - Application Log shows PERFLIB 1011
error against dsmcperf.dll (DWORD0)
This only occurs if the customer tries to open the NT
Performance Monitor
2. Same error in the form of an NT Error Box on boot.
In this case, there are registry entries missing under the
Hkey_Local_Machine > system > currentcontrolset > services >
ADSM Client Performance > performance.
The entries are "First Counter", "First Help", "Last Counter
", "Last Help"
LOCAL FIX:
>From the \adsm\baclient subdir, issue the commands:
1. unlodctr "ADSM Client Performance"
2. lodctr perfctr.ini
This will eliminate the error messages
COMMENTS: Please see the closing remarks for V3.1 IC24370.
In TSM Version 3.7, the performance monitor function is still
inactivated, pending a redesign (if it is possible) so
that other performance monitoring tools such as Netfinity
do not cause TSM to have this problem. The remarks for IC24370
apply in V3.7 as well.
It is a suggestion for a future release to try to redesign
and reimplement the function so that it will work when
outside performance monitors are also in use.
-----Original Message-----
From: Neil Schofield [mailto:[EMAIL PROTECTED]]
Sent: Saturday, December 02, 2000 8:20 AM
To: [EMAIL PROTECTED]
Subject: ADSM Client Performance counters
Has anybody got the ADSM Client Performance counters working for the v4.1
TSM
client software running under NT?
I installed the 4.1.1.16 client on an NT workstation. The install created a
key
in the registry called "TSM Client Performance". However, the versions of
DSMCPERF.DLL and PERFCTR.INI that were installed seemed to reference a key
called "ADSM Client Performance".
I managed to sort this out, along with the extraneous quotation marks and
lack
of a fully qualified path to the DLL in the registry values. I then used
LODCTR
to load the counters into Performance Monitor.
The counters appear, but never register any backup activity. They just stay
at
zero.
I've got an additional problem with the client running on a Compaq server.
On
this system, starting the Compaq NT Management and Patrol for Insight
Manager
services causes an 'ADSM_Client_ThreadList_Mutex' error in the event log.
The
source of the error is "ADSM Client Performance".
Has anybody got this working?
Neil Schofield
The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Yorkshire Water Services Limited
Registered Office 2 The Embankment Sovereign Street Leeds LS1 4BG
Registered in England and Wales No 2366682
