*** Original Author: ADSM-L @ UGA - ** Remote User **; 10/20/94 19:40
>Received: from uga.cc.uga.edu by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V2R2.1)
> with TCP; Thu, 20 Oct 94 19:40:28 CDT
>Received: from UGA.CC.UGA.EDU by uga.cc.uga.edu (IBM VM SMTP V2R2)
> with BSMTP id 6076; Thu, 20 Oct 94 20:31:47 EDT
>Received: from UGA.CC.UGA.EDU (NJE origin LISTSERV@UGA) by UGA.CC.UGA.EDU (LMai
> V1.2a/1.8a) with BSMTP id 4378; Thu, 20 Oct 1994 20:31:47 -0400
>Date: Thu, 20 Oct 1994 17:07:58 EDT
>Reply-To: "Dist. Stor. Manager(ADSM) List"
> <ADSM-L%MARIST.BITNET AT uga.cc.uga DOT edu>
>Sender: "Dist. Stor. Manager(ADSM) List"
> <ADSM-L%MARIST.BITNET AT uga.cc.uga DOT edu>
>From: Melinda Varian <MAINT%PUCC.BITNET AT uga.cc.uga DOT edu>
>Subject: Failure of restore with DOS Client, ANS1772E
>To: Multiple recipients of list ADSM-L
> <ADSM-L%MARIST.BITNET AT uga.cc.uga DOT edu>
>
We are testing the ADSM DOS client. The system we are testing
with is an IBM PS/2 Model 80 with 8M of memory.
Our test case is the backup and restore of one hard disk, which
occupies 40M on the ADSM server and contains 4,141 files.
The backup appears to have succeeded, but the restore fails with
"ANS1772E No memory available while trying to get server file
information", which is followed by "ANS1730E restore file selection
failed, return code = 1001".
A "mem" command indicates that we have 7,685K total free memory
(when not running a restore), including 573K under the 1MB line.
Given that this is a relatively large DOS system and a relatively
small disk, such a failure is disheartening. Are there any options
we should be trying to get around this problem?
Melinda Varian
Princeton University
*** Comments from STEWAJM - Stewart, Mike; 10/21/94 07:08am:
We've had what sounds like the same problem for a year, in several
of the clients. Of the clients we use, all except the DOS
client seem to have been fixed.
IBM has opened the following APAR, which may describe your problem:
APAR Identifier ...... IC08453 Last Changed ........ 94/10/11
DOS RUNS OUT OF MEMORY WHEN A LARGE NUMBER OF FILES IN DIRECTORY
BEING BACKED UP
Symptom ...... IN INCORROUT Status ........... CLOSED SUG
Severity ................... 4 Date Closed ......... 94/10/11
Component .......... 564802009 Duplicate of .........
Reported Release ......... 110 Fixed Release ............
Component Name ADSM WIND CLIEN Special Types ....
Current Target Date .. Type of Relief ..Not Available
SCP ................... PC/DOS Platform ............ DOS
COMMENTS: When backing up a directory, the filenames are put
into an array and sorted so that when displayed, they will be
in alphabetic order. When there are a large number of filenames,
this array can fill up available memory. To solve this problem
and still provide for a list that the user can easily find the
filename they are looking for, requires implementing an enhanced
memory management for DOS that will allow sections of the array
to be swapped in and out of DOS-addressable memory. We hope to
do this in the future, but the amount of change involved makes
this fix a design change that does not fall within normal apar
and ptf proceedures.
|
