t-verify.messages Article/Article

t-verify.messages

Command t-verify.messages Article/Article
Applicable release versions: AP
Category Article (24)
Description T-verify error message explanations.

Originally ran in PickWorld Magazine under the title: "WHAT IS T-VERIFY TELLING ME?".

[1502] Illegal file level for 'D' pointer
A d-pointer was read from the tape, but the file level number was not valid. It could have been garbage. Do not rely on this tape.

[1503] Illegal file ID for 'D' pointer
A d-pointer was read from the tape, but the file id (file number) was not valid. It could have been garbage. The file ID is taken from the file-of-files file. Do not rely on this tape.

[1504] Illegal character count for 'D' pointer
A d-pointer was read from the tape, but the count field was not a valid 4 byte hex number (ASCII hex). It could have been garbage. Do not rely on this tape.

[1505 Character count too small for 'D' pointer
A d-pointer was read that had a count field that was too small for the number of characters actually read. The d-pointer body has been corrupted or the count field is wrong. Do not rely on this tape.

[1506] Item-ID too large for count field in 'D' pointer
A d-pointer was read from the tape, but the whole d-pointer is just an Item- ID. Maybe it got truncated or overwritten. Do not rely on this tape.

[1507] Item-ID too small for count field in 'D' pointer
A d-pointer was read from the tape, but the whole d-pointer is just an Item-ID and ended prematurely (too small). Maybe it got truncated. Do not rely on this tape.

[1512] Non decimal modulo for 'D' pointer
A d-pointer was read from the tape, but attribute 3 does not have a decimal number in it. Maybe garbage was read. This invalidates this item as a d-point er. Do not rely on this tape.

[1513] MDS 'D' pointer expected
A T-VERIFY on a full save tape was begun, but the mds d-pointer was not found at the beginning of the 1st reel. Maybe an account-save tape was insert ed or the 1st reel was not rewound to the beginning. The file-system has not been checked at all yet.

[1515] Illegal file level for MDS 'D' pointer
The mds d-pointer has a file level of zero. Zero is the highest level. This is the only file that is at this level. This is not a valid full save tape. No statement can be made about the file-system (disk).

[1516] Mismatching MDS 'D' pointer
The mds d-pointer read from the tape does not match the one on disk (in the file-system). The tape is intact and restorable, but does not reflect the current state of the system.

[1520] Non hexadecimal file ID
Every item on the tape has a file number with it that tells which file it came from. This field is supposed to be ASCII hex! For some reason, it is corrupt and not ASCII hex. The restore processor might have trouble restoring it. Do not rely on this tape.

[1523] Count field too small for item
The item read from the tape has more characters than its count field indicates. The data might still restore properly, but do not rely on it.

[1524] Item-ID too large for count field
The whole item was just an Item-ID and it was too small for its count field. Maybe it got truncated. The count field (character count) was wrong. This one item was bad and maybe garbage. No Item-ID is displayed because T- VERIFY could not guarantee it found one.

[1525] Non hexadecimal binary code block count
Every binary item (basic object code) on the tape has a block count associated with it. Binary item data is placed on the save tape 1000 bytes per block. This hexadecimal field is corrupt. If this message occurs on only one item, than just recompile the item from the source program. If many messages occur, then do not rely on this tape.

[1526] Attribute mark missing after Item-ID
The item read from the tape was only an Item-ID and was terminated by a segment mark. This is not normal but the item will restore properly. Check the item on disk. The tape is intact. No statement can be made abut the file- system (disk).

[1527 Count field missing
The item read from tape has no 4 byte count field and it is not a pointer item or a binary item (those types do not have count fields). The item might restore or it might be garbage. Do not rely on this tape. No statement can be made about the file-system.

[1549] File on tape not on disk
A d-pointer item was read from the tape. It is fine, but there is not a file on disk with the same name. The tape is intact, but does not reflect the current state of the file-system.

[1552] Binary code missing inter-block delimiter
Advanced Pick dumps binary code as a binary frame dump. Each frame has a 1 byte separator on the tape. This byte is missing, or a block was lost or garbage was read. Something is wrong with the tape. Do not rely on it.

[1553] Binary code missing final segment mark
On the tape, after the last block of object code of a binary item, there is a segment mark. This one is missing. It will probably restore correctly, but you might lose the next item on the tape. Maybe a block was lost from the tape. Do not rely on this tape.

[1565] Data level is in the process of being deleted
You cannot verify a file against the disk if it is being deleted. the tape is still intact, but does not reflect the current state of the file-system.

[1566] Dictionary is in the process of being deleted
You cannot verify a file against the disk if it is being deleted. The tape is still intact, but does not reflect the current state of the file-system.

[1567] Account is in the process of being deleted
You cannot verify an account if it is in the process of being deleted. The tape is intact and can be restored from, but does not reflect the current state of the file-system.

[1588] Label missing
A label is expected prior to each account. The tape is corrupt or was not posi tioned at the beginning prior to running T-VERIFY.

[1591] Illegal file ID of zero
Every file has a number associated with it. For some reason, a file has been read from the tape that has a file number of zero. Check the file-of-files file for a zero Item-ID. If this is the only tape error, then the tape is probably restorable, but don't rely on it.

[1593] Illegal file number for index b-tree
An index b-tree was read from the tape, but T-VERIFY cannot determine what file it belongs to. The tape is corrupt. Do not rely on it.

[1594] Index will not restore, different frame size
The save was made on a machine with a different frame size. The tape is intact and restorable, but all index b-trees will be skipped and will be generat ed new at the end of the restore. This is because, like binary items, the b-trees are dumped to tape in binary images, frame by frame.

[1596] Index b-trees mismatch
The index b-tree read from the tape is intact and restorable, but does not match the one in the file-system. Maybe the index on disk was updated. The tape is fine.

[1598] GFE(s) encountered
While comparing the tape against the disk, a GFE was encountered and skipped. The tape is intact, but the file-system has data corruption.
Syntax
Options
Example
Purpose
Related tcl.t-verify
pointer.item