>Leo,
>we have the same problem with the V3 NT ADSM client software (all PTFs).
>I opened a problem record (#13137).
>Here's my description and the response from IBM tech. support.
>
>Regards,
>Michael
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>DESCRIPTION: Memory leak in ADSM NT BA-Client V3 PTF 3-6
>
>Dependent of the number of objects inspected during a scheduled
>incremental session, the ADSM NT BA-Client allocates a certain
>amount of RAM and only frees a part of it after completion of the
>session.
>On a client containing 1 million+ files the amount of allocated RAM
>for ADSM gets increased each day and leads to a reboot being
>necessary after a few weeks.
>
>When upgrading from one PTF to another, one DLL cannot be replaced
>making a reboot necessary. This behaviour could be a part of the same
>problem (DLL does not release all allocated RAM and therefor cannot
>get removed from memory?).
>
>Regards, Michael Bartl
> -HOFRATH, HEINZ MVS-564802001 - 99/02/17-14:50-
> -HOFRATH, HEINZ MVS-565511901 - 99/02/17-15:05-
>Hello Mr Bartl
>it looks like your problemis described in ic22119
>************************************************************************
>APAR=3D IC22119 SER=3D UR UR
>THE CLIENT SCHEDULER IS NOT FREEING ALL THE MEMORY THAT IT
>USES, OR NEVER LOWERS THE REQUIRED MEMORY USEAGE.
>STAT=3D CLOSED PER FESN0902370- CTID=3D SJ0291 ISEV=3D 2
>************************************************************************
>this apar is closed and should get fixed in 3.1.0.7 level which is not
>available yet
>regards Heinz Hofrath
>
>-----Urspr=FCngliche Nachricht-----
>Von: Leo Humar [ mailto:lhumar AT VIC.BIGPOND.NET DOT AU
><mailto:lhumar AT VIC.BIGPOND.NET DOT AU> ]
>Gesendet am: Montag, 22. Februar 1999 14:15
>An: ADSM-L AT VM.MARIST DOT EDU
>Betreff: NT 3.1.0.6 memory problem
>
>Hi dear ADSMr's,
>
>Has anybody encountered any memory problems with the 3.1.0.6 baclient ?
>Does the fixtest IC22800J4.EXE addresse this memory problems?
>Hardware:
>Digital prioris 6000 with two pentium Pro 200's and 128MB memory.
>This machine is a one of two sharing a 70 GB redundant RAID.
>These servers are clients of our ADSM Server 3.1.2.13
>We are using ADSM since late October 1998.
>Both servers where running NT 3.51 and required frequent rebooting due t=
o
>the filemanager not responding.
>We where not sure what caused this problem.We upgraded one of the server=
s
to
>NT4 and 3.1.0.6 baclient.
>After the overnight backup we couldn't access this server and this was d=
ue
>to the lack of available memory.
>The test this afternoon showed that the baclient used the available memo=
ry
>(70MB) and didn't release it after we stopped the backup.
>We also compared the 3.1.0.5 client and noticed that it didn't release s=
ome
>of the memory on the NT3.51 with the 3.1.0.5 client but over time this i=
s
>most likely to cause us problems.
>I've noticed that solaris and digital alpha's have this problem but I
didn't
>read about any Intel based servers having memory leakage problems.
>The backup overnight finished without any problems but we had to reboot =
the
>server in the morning as it was unusable. The actlog showed about 257000
>objects for one server and 255000 objects for the other server. The serv=
ice
>requires about 500 bytes per object to process. So I require about 100MB
for
>this process.
>The process should still run reasonably well with this amount of memory.
>I'm sure there will be much larger windows NT4 clients out there with an
NT4
>ADSM server version 3.1.2.13
>Can you please tell me if you have any similar problems?
>Have you fixed it and what are the fixes?
>
>I.m looking forward to your responses and I thank you all for your help =
!
>
>Have a G'day !
>
>
>Leo Humar
>LCS Pty Ltd
>lhumar AT vic.bigpond.net DOT au <mailto:lhumar AT vic.bigpond.net DOT au>