Guardian Procedure Errors and Messages Manual

• Invalid SETMODE operation
• ACTIVATERECEIVETRANSID, READUPDATE, or REPLY attempted on $RECEIVE opened with
a receive-depth of zero.
This error is also returned from REPLYX in any of the three following cases:
• The address of a parameter is extended, but no segment is in use at the time of the call or the
segment in use is invalid.
• The address of a parameter is extended, but is an absolute address.
• The file system cannot use the user's segment when needed.
This error is also returned in any of the following cases:
• A request to perform an invalid operation on a disk file.
• An attempt to create a disk file with invalid or inconsistent parameters.
Effect The operation might return without performing all or part of the requested operation. For
example, FILE_GETINFOLIST[BYNAME]_ can return without all of the requested information.
Recovery Correct the request.
3 (%3) An open or purge of a partition failed.
(device type: 3)
Cause An OPEN or FILE_OPEN_ operation did not open one or more partitions defined for the
file, or a purge or other operation for a partitioned file did not operate on one or more of the
defined partitions.
Effect The open operation succeeds. However, any future attempts to access the nonexistent partition
return an error 72 (attempt to access unmounted partition). The purge operation deletes what it
can.
Recovery Correct the operation or parameters.
4 (%4) An open operation for an alternate key file
failed. (device type: 3)
Cause An open operation for a structured file with alternate keys did not open an alternate-key
file.
Effect The open succeeds. However, any subsequent attempts to access the file by way of an
alternate key stored in the unopened file result in file-system error 46 (invalid key specified). When
an insertion or update is made to a file having an unopened alternate-key file, the insertion (that
is, the write) finishes successfully but does not update the unopened alternate-key file.
Recovery Corrective action is application dependent.
5 (%5) Sequential buffering not used because no
space was available in the PFS for the
sequential block buffer. (device type: 3)
Cause Space was not available in the process file segment (PFS) for the sequential block buffer or
the file is not a structured disk file.
Effect Sequential-block buffering is not used.
Recovery Informative warning message only; no corrective action is needed.
6 (%6) A system message was received from another
process. (device type: 2)
22 File-System Errors