HP StorageWorks P9000 Data Exchange User Guide (T1620-96016, September 2010)

NOTE:
Do not update the volume that is transferred directly by the FXotm.
Table 5 FXotm Record Format Requirements
See FigureRecord Format RequirementsFCU Direc-
tion
Target DatasetSource File
Figure 15, page 32Fixed-lengthFixed-length: no padding, no delimitersFXotm
Figure 16, page 33Fixed-lengthFixed-length containing paddingFXotm
Figure 17, page 33Fixed-lengthFixed-length containing delimitersFXotm
Figure 18, page 34Fixed-length
Fixed-length containing padding and delim-
iters
FXotm
Figure 19, page 34Variable-lengthVariable-length: with delimitersFXotm
Figure 20, page 35Fixed-length
Variable-length: with padding and delim-
iters
FXotm
FXotm with Fixed-Length Record Format
No padding, no delimiters. Figure 15 on page 32 shows an FXotm operation for a fixed-length source
file without padding or delimiters. The target dataset must have a fixed-length record format with the
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, the FCU aborts the operation and reports an
error.
Figure 15 FXotm with Fixed-Length Records: No Padding, No Delimiters
.
With padding. Figure 16 on page 33 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.The 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 4 bytes (for the RL field).
The target dataset must have a fixed-length record format with the record length set to the maximum
record length minus 4 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, the FCU aborts the operation
and reports an error.
About Data Exchange Operations32