2-26 About Cross-OS File Exchange Operations
Hitachi USP V Cross-OS File Exchange User’s Guide
With delimiters. The figure below shows an FXotm operation for a fixed-
length source file with delimiters from a previous FXmto transfer. FCU extracts
the data entities from the source file by record length and transfers them to
the target dataset. The delimiters are not transferred. The target dataset must
have fixed-length record format with record length set to the actual length of
each data entity (without delimiter). If the length of any source data entity
does not exactly match the record length defined for the target dataset, FCU
aborts the operation and reports an error. If the delimiter is not found right
after the data entity, FCU aborts the operation reports an error.
Open-System Source File Target Dataset
Record length + 1 or 2 bytes Record length
Data entity 1 D Record 1: Data entity 1
Data entity 2 D
→
Record 2: Data entity 2
Data entity 3 D Record 3: Data entity 3
Figure 2-17 FXotm with Fixed-Length Records: Delimiters
Note: FCU does not add delimiters to FXotm source files. If the FXotm source
file contains delimiters but you specify No for the delimiter option, the
delimiters will be regarded as part of the data entities and will be transferred
to the target dataset.
With padding and delimiters. The figure below shows an FXotm operation
for a fixed-length source file with padding and delimiters from a previous
FXmto transfer. FCU removes the delimiters but not the padding and transfers
the data entities with padding to the target dataset. The original variable-
length dataset cannot be used as the target dataset for this transfer. 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 source data
entity does not 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) − 3 or 2 bytes Record length (max) − 4 bytes
Data entity 1 D Record 1: Data entity 1 with padding
Data entity 2 D
→
Record 2: Data entity 2
Data entity 3 D Record 3: Data entity 3 with padding
