HP XP20000XP24000 Disk Array - Manual (Page 43)

About Cross-OS File Exchange Operations 2-25
Hitachi USP V Cross-OS File Exchange User’s Guide
FXotm with Fixed-Length Record Format
No padding, no delimiters. The figure below shows an FXotm operation for
a fixed-length source file without padding or delimiters. The target dataset
must have fixed-length record format with record length set to the actual
length of each data entity. If the data entity length does not exactly match the
record length defined for the target dataset, FCU aborts the operation and
reports an error.
Open-System Source File Target Dataset
Record length Record length
Data entity 1 Record 1: Data entity 1
Data entity 2 → Record 2: Data entity 2
Data entity 3 Record 3: Data entity 3
Figure 2-15 FXotm with Fixed-Length Records: No Padding, No
Delimiters
With padding. The figure below shows an FXotm operation for a fixed-length
source file with padding from a previous FXmto transfer. The original FXmto
dataset cannot be used as the FXotm target dataset. FCU transfers the data
entities including padding to the target dataset. The length of each data entity
in the source file equals the maximum record length minus four bytes (for the
RL field). The target dataset must have fixed-length record format with record
length set to the maximum record length minus four bytes. If the length of
any record (data entity plus padding) in the source file does not exactly match
the record length defined for the target dataset, FCU aborts the operation and
reports an error.
Open-System Source File Target Dataset
Record length (max) − 4 bytes Record length (max) − 4 bytes
Data entity 1 padding Record 1: Data entity 1 (with padding)
Data entity 2 → Record 2: Data entity 2
Data entity 3 padding Record 3: Data entity 3 (with padding)
Figure 2-16 FXotm with Fixed-Length Records: Padding
Note: FCU does not extract padding from FXotm source files.