noft Manual (G06.27+, H06.03+, J06.03+)

ar Diagnostic Messages
noft Manual—528273-003
6-2
Cause. When building an archive in the Guardian environment, ar encountered a file
system error identified by the number errnum when processing the specified member.
The archive should be intact except for the member that caused the error.
Recovery. Correct the error condition and add the member to the archive using the -r
option, and also specifying a or b if the position of the member is relevant.
Cause. When building an archive in the Guardian environment, the maximum size for
a single member is approximately 128,073,728 bytes.
Recovery. Rebuild the archive, excluding the file that is too large.
Cause. When building an archive in the Guardian environment, each member file
must be an odd, unstructured disk file. In particular, Edit-format (code 101) files are not
allowed in archives.
Recovery. Rebuild the archive, excluding files that are of invalid types.
Cause. An I/O error occurred when the specified archive was being closed prior to
constructing the archive symbol table.
Recovery. Correct the condition that caused the I/O error, and then build the symbol
table by using ar with the -ts options.
Cause. An error occurred when ar attempted to open the specified archive.
Recovery. Identify the error and remedy the situation, and then rebuild the archive.
Cause. An I/O error occurred in the Guardian environment when ar attempted to
open the specified archive to set the file permissions.
Recovery. Use the FUP utility to look at the permissions on the archive and make any
corrections needed.
ar: member: file too large.
ar: member: invalid file type.
archive, cannot close to reposition for symbol table.
archive, cannot open.
archive, cannot open archive to set permissions.