ADSM-L

a problem with adsm client and mem usage

1994-08-30 12:25:29
Subject: a problem with adsm client and mem usage
From: Leonard Boyle <SNOLEN AT VM.SAS DOT COM>
Date: Tue, 30 Aug 1994 12:25:29 EDT
I noticed this on IBMLINK today. It explains some other problems we have
seen. I hope that this one is fixed soon.


Item IC08046




  APAR Identifier ...... IC08046      Last Changed ........ 94/08/15
  THE SCHEDULER CAUSES A MEMORY LEAK THAT CAN CAUSE THE SCHEDULE
  PROCESS TO ABEND.

  Symptom ...... AB ABEND             Status ........... OPEN
  Severity ................... 3      Date Closed .........
  Component .......... 564802013      Duplicate of .........
  Reported Release ......... 1B0      Fixed Release ............
  Component Name ADSM HP CLIENT       Special Types ....
  Current Target Date ..              Type of Relief ..Not Available
  SCP ................... PCHPT       Platform ............ HP

  Status Detail: Not Available

  PE PTF List:

  PTF List:


  Parent APAR:
  Child APAR list:


  ERROR DESCRIPTION:
  ANS4505E Error starting the trusted communication agent process.
  .
  After completing an incremental backup the scheduler fails
  subsequent incrementals with the above message. The scheduler
  may subsequently abend. This is due to a memory leak caused by
  the scheduler. The memory leaks causes the workstation to run
  out of swap space.
  .
  This problem is prevalent when the filesystems being backed up
  contain several thousands of files.


  LOCAL FIX:

-------------------------------------------------------------------------
Leonard Boyle, Mainframe support            snolen AT vm.sas DOT com
Leonard Boyle, Mainframe support            snolen AT vm.sas DOT com
SAS Institute Inc.                          ussas4hs@ibmmail
Room E206                                   (919) 677-8000 ext 6241
203 SAS Campus Drive
Cary NC 27513
<Prev in Thread] Current Thread [Next in Thread>
  • a problem with adsm client and mem usage, Leonard Boyle <=