Ref: 13390004
Title: 3+Open "Out of Scratch Memory" Message
Date: 8/30/89

Copyright 3Com Corporation, 1991.  All rights reserved.

A message like "logNoResourc1:out of scratchmem" can be generated
during startup of the server software or during server operation
if there is not enough scratch memory for the following needs:

1.  When an open SMB calls for the generation of a handle type open
(though not FCB type open), the full pathname of the file being opened
is generated.  Scratch memory is allocated for the building of this full
pathname.

2.  When an open SMB is in user security mode, the full pathname of the
file is generated locally to determine the user's right to access.  Scratch
memory is allocated for the building of this full pathname.

3.  During the audit process, the attempted audit log entry plus space
for the queue header is allocated from scratch memory.

The server allocates a single segment for all of its tables, work areas,
queues, view buffers, etc.  The remaining space in the segment is allocated
to scratch memory.  The scratch area is enlarged as the needs of the server
demand it; however, the segment cannot grow beyond its 64 KB limit.  If
the need for scratch memory exceeds the segment boundary, an error message
is generated.

Usually, when scratch memory is no longer needed, it is logically freed
by its user.  However, in 3+Open 1.0, the spooler does not free
the memory it uses to build a full path name for the print queue file if
the queue is rejected on the basis of the "maxqueue" parameter.  This
generates a GP fault in the spooler rather than a "scratch memory" error.
(This problem will be addressed in the next version of the LAN Manager.)

