6100 ADCCP Programming Manual

File-System Error Codes
File-System Error Codes
A–6 069225 Tandem Computers Incorporated
Table A-2 lists error codes that your application can respond to by retrying the
operation.
Table A-2. File-System Error Codes– Retry
Error
Code Description/Solution
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 could not 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 do not want to add memory to make more local pool available, use SYSGEN to
assign fewer lines to this CP6100 and 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.
200 Device owned by other CPU. This message indicates that a path switch has occurred or is
occurring. See “Path Switches” in this appendix.
210 Path switch occurred. Device owned by other CPU. This message indicates that a path
switch has occurred or is occurring. See “Path Switches” in this appendix.
211 CPU failure. Device Owned by Other CPU. This message indicates that a path switch has
occurred or is occurring. See “Path Switches” in this appendix.
230 CPU power on. Device Owned by Other CPU. This message indicates that a path switch
has occurred or is occurring. See “Path Switches” in this appendix.
231 Controller power on, channel reset, or loss of contact with the 6100 subsystem cabinet. See
“Total Subsystem and LIU Failures” in this Appendix.