Difference between revisions of "Record Format"
From AC Wiki
(→Record Format Table) |
|||
| Line 16: | Line 16: | ||
| MU || '''c''' ''or'' '''d''' ''or'' '''i''' ''or'' '''j''' || | | MU || '''c''' ''or'' '''d''' ''or'' '''i''' ''or'' '''j''' || | ||
|-align="center" | |-align="center" | ||
| − | | CR || '''a''' || '''b''' ''or'' '''i''' ''or'' ''' | + | | CR || '''a''' || '''b''' ''or'' '''i''' ''or'' '''s''' |
|-align="center" | |-align="center" | ||
| VM || '''g''' ''or'' '''k''' ''or'' '''o''' ''or'' '''r''' || | | VM || '''g''' ''or'' '''k''' ''or'' '''o''' ''or'' '''r''' || | ||
Latest revision as of 16:22, 10 February 2014
MARS 2.0 Record Format Criteria
MARS 2.0 processing determines the format of the record based entirely off of the values of leader bytes 06 & 07. The value for LDR 06 must be met before the value for LDR 07 is even considered. So, if LDR 06 byte value is e, yet LDR 07 byte value is i, the record will still be considered a map (MP), even though LDR 07 says it could be a continuing resource (CR).
Record Format Table
| Type | LDR 06 Value | LDR 07 Value |
|---|---|---|
| BK | t or a | a or c or d or m |
| CF | m | |
| MP | e or f | |
| MU | c or d or i or j | |
| CR | a | b or i or s |
| VM | g or k or o or r | |
| MX | p |
