Image Data Record
The image data basic record length is 244 bytes.
| Field Number | Format | Bytes | Constant Value | Description |
|---|---|---|---|---|
| 1 | binary | 2 | Logical record length | |
| 2 | binary | 2 | X'00's | Reserved |
| 3 | binary | 1 | X'40' | Record type (image data record) |
| 4 | binary | 1 | X'00' | Reserved |
| 5 | binary | 1 | X'01' | Record format version |
| 6 | binary | 1 | X'00' | Reserved |
| 7 | character | 28 | C' ‘s | Reserved |
| 8 | character | 8 | C' ‘s | Reserved |
| 9 | binary | 4 | Data length (present segment length plus X'D0') | |
| 10 | binary | 1 | X'02' | Record format version |
| 11 | binary | 3 | X'00's | Reserved |
| 12 | binary | 10 | X'00's | Reserved |
| 13 | 2 | User area (default is X'20's) | ||
| 14 | character | 6 | C'ELRC.C' | Image date key - First eye catcher |
| 15 | character | 2 | Image data key - Business category | |
| 16 | character | 2 | C'.Y' | Image data key - Second eye catcher |
| 17 | character | 4 | Image data key - Business date's year (YYYY) | |
| 18 | character | 3 | C'.MD' | Image data key - Third eye catcher |
| 19 | character | 2 | Image data key - Business date's month (MM) | |
| 20 | character | 2 | Image data key - Business date's day (DD) | |
| 21 | character | 2 | C'.S' | Image data key - Fourth Eye Catch |
| 22 | character | 2 | Image data key - Document processor number | |
| 23 | character | 3 | Image data key - ISN's 3 high order digits | |
| 24 | character | 2 | C'.S' | Image data key - Fifth eye catcher |
| 25 | character | 5 | Image data key - ISN's 5 low order digits | |
| 26 | character | 9 | C' ‘s | Image data key - Padding |
| 27 | binary | 6 | X'00's | Reserved |
| 28 | binary | 2 | Present segment count | |
| 29 | binary | 4 | 0 | Segment 0 offset from start of field 6 |
| 30 | binary | 4 | 0 | Segment 0 length |
| 31 | binary | 4 | Segment 1 offset from start of field 6 | |
| 32 | binary | 4 | Segment 1 length | |
| 33 | binary | 4 | Segment 2 offset from start of field 6 | |
| 34 | binary | 4 | Segment 2 length | |
| 35 | binary | 4 | Segment 3 offset from start of field 6 | |
| 36 | binary | 4 | Segment 3 length | |
| 37 | binary | 4 | Segment 4 offset from start of field 6 | |
| 38 | binary | 4 | Segment 4 length | |
| 39 | binary | 4 | 0 | Segment 5 offset from start of field 6 |
| 40 | binary | 4 | 0 | Segment 5 length |
| ........... | .................. | .................. | .................. | .................. |
| ........... | .................. | .................. | .................. | .................. |
| 59 | binary | 4 | 0 | Segment 15 offset from start of field 6 |
| 60 | binary | 4 | 0 | Segment 15 length |
| 61 | binary | variable | The extracted segments (0 - 4) |
When present in the image data record, segment zero always has
a size of 1500 bytes and contains the data in Table 2:
| Offset | Bytes | Constant Value | Description |
|---|---|---|---|
| 0 | 1 | X'84' | Record version number |
| 858 | 149 | Basic codeline definition table containing only the field definitions (16 nine-byte fields starting at codeline definition table offset 6), in ascending order. Each field definition contains only the field's process buffer offset from the end of the process buffer in byte 3 and the field's length in byte 5. | |
| 1008 | 256 | Reconstructed process buffer area containing the right justified packed unsigned codeline fields | |
| 1265 | 1 | Item tracking number |
When codeline data extraction is active, the codeline fields have variable length including their significative characters, by default. If the fixed length codeline fields option is also active, the codeline fields have a fixed length based on their respective lengths in the FTM database item table. In both cases, the codeline definition table preceding the process buffer area contains the precise codeline field offsets and lengths
When segment 0 is present, the process buffer area's field
0 (header record field) has the contents shown in Table 3.
| Bytes | Bit | Constant Value | Description |
|---|---|---|---|
| 0 | Not set | ||
| 1 | Not set | ||
| 2 | Item type and field validity bits | ||
| 0 | Control document (divider document if bits 1, 2, and 3 are off) | ||
| 1 |
|
||
| 2 | Tracer, if bit 0 is on and bit 1 is off | ||
| 3 | Field 1 validity | ||
| 4 | Field 2 validity | ||
| 5 | Field 3 validity | ||
| 6 | Field 5 validity | ||
| 7 | Field 7validity | ||
| 3 | Not set | ||
| 4 | Module or pocket number | ||
| 5 | Not set | ||
| 6 | Not set | ||
| 7 | Not set | ||
| 8 | 0 | Auto-select indicator | |
| 9 | Additional field validity bits | ||
| 0 | Field 4 validity | ||
| 1 | Field 6 validity | ||
| 3 | Image assist document, if byte 2 bit 0 is on | ||
| 10 | Tracking number | ||
| 11 | X'80' | Data document type |
Field 0 (header record field) contains only the:
- Control document and control document type indicators
- On us and auto-select indicators
- Codeline field validity bits
- Module pocket number
- Tracking number
- Record header type
When user segments 13, 14 or 15 are generated, their contents are set by the user exit routine. The user exit routine determines whether the segments are generated by calling their respective setters.