Guardian Procedure Errors and Messages Manual

Recovery Corrective action is application dependent and depends on whether a read or a write
was involved or a PROCESS_DEBUG_ or DEBUGPROCESS operation was being used.
41 (%51) A checksum error occurred on a file
synchronization block. (device type: 3)
Cause A file synchronization block was in error, probably because a user program modified the
file-system sync buffer area.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Correct the coding error.
43 (%53) Unable to obtain disk space for
file extent. (device type: 3)
Cause The specified volume did not contain enough contiguous free space to permit allocating an
extent of the size needed for the file or for the directory.
Effect The procedure sets the error code and returns without performing the requested operation.
Recovery Purge unneeded files residing on the volume.
Determine the amount of available space and the number and size of fragments on the volume by
using the DSAP FREESPACE command or the LISTFREE command. If there is excessive fragmentation
on the disk, have the operator consolidate the available space by using the Disk Compression
Program (DCOM).
For a temporary workaround, specify a different swapvol in the RUN command.
44 (%54) The disk directory or DCT is full.
(device type: 3)
Cause The disk directory is full. For a named process, the destination control table (DCT) is full.
Effect The procedure sets the error code and returns without adding the entry.
Recovery For disk files, purge some files, then try again, or have the operator relabel the disk to
allow for more directory entries. The directory structure might allow you to add new files whose
names correspond to other areas of the directory structure where there is still space.
For process files, the system might not create any newly named process until at least one existing
named process has stopped.
45 (%55) The file is full; or two entries for
<process-name> were already in the PPD.
(device type: 3)
Cause This error can occur for the following reasons:
• The file system did not add any more records to the given disk file.
• During a call to PROCESS_CREATE_, NEWPROCESSNOWAIT, or NEWPROCESS, two entries
(both the primary and the backup) for process-name were already in the process-pair directory,
so no new entry was added.
Effect For unstructured disk files, as much data as possible is written.
Otherwise, the procedure sets the error code and returns without adding to the file.
Recovery Either create a new file with larger extents and reload it, or increase the current file's
maximum extents by issuing, for example, the FUP ALTER command with the MAXEXTENTS option.
Error Code Descriptions 31