CP6100 I/O Process Programming Manual

File System Error Codes
----------------------------------------------------------------
RETRY THESE, BUT FIRST READ NOTES IN TEXT
----------------------------------------------------------------
31 No Buffer for #DEBUG. CP6100 couldn't get a buffer
to service a request for CSSDBUG. This error is a
specific case of error 33, below.
-----------------------------------------------------------------
33 Buffer Space Shortage. CP6100 couldn't get a
buffer for the request. Try the operation again.
If you get this error frequently, any of the
following actions might help:
• Move some lines to other processors, using
SYSGEN or CMI, or add memory to the processor
to increase the amount of I/O segment space.
CP6100 uses system I/O segments for transfers
to and from the line. That space is shared
with all the I/O processes running in the
processor.
• Add memory to the processor to increase available
local pool space. (Local pool space is set at
64K, but a shortage of physical memory may be
preventing a full allocation). CP6100 uses local
pool space for transfers exceeding the size of a
frame, as defined in the line configuration. (A
frame can never exceed 2K, but you might define
it to be smaller.) Local pool space is shared by
all lines this CP6100 process controls.
• If you don't want to add memory to make more
local pool available, use SYSGEN to assign fewer
lines to this CP6100: use the MULTI parameter
less than before. Other ways to conserve local
pool are to send smaller messages, to send fewer
large ones, or to change your frame size so fewer
of your messages exceed it. Remember that only
large messages place demands on local pool.
• Finally, consider the other applications that use
the same lines (or lines in the same processor).
However you work to optimize your program, the
message design of other applications affects the
buffer space available to you.
-----------------------------------------------------------------
A-8