Fxmto with variable-length record format, Fxmto with fixed-length records: delimiters, Figure 10 – HP XP P9500 Storage User Manual
Page 28: Figure 11

Figure 10 FXmto with Fixed-Length Records: Delimiters
.
FXmto with Variable-Length Record Format
Each variable-length record in a mainframe dataset includes a four-byte RL field and the variable-length
data entity. The record length defined for a variable-length dataset equals the maximum allowable
record length.
NOTE:
To transfer the data back to the original mainframe dataset later, you must use FXmto without padding
and with delimiters.
No padding, no delimiters.
on page 28 shows an FXmto operation without padding or
delimiters for a variable-length source dataset. FCU extracts and transfers only the data entities to the
target file. The RL fields are not transferred. The resulting length of each data entity in the target file
is equal to or less than the maximum record length minus 4 bytes (for the RL field).
NOTE:
If you plan to transfer the data back to the original dataset later using FXotm, use FXmto with delimiters.
Figure 11 FXmto with Variable-Length Records: No Padding, No Delimiters
.
With padding.
on page 29 shows an FXmto operation with padding. FXmto with padding
requires a variable-length source file and produces a fixed-length target file. The FCU adds padding
to the source records as needed so that the length of each record equals the maximum record length.
The FCU then extracts and transfers the data entities with padding to the open-system target file. The
RL fields are not transferred. The resulting length of each data entity in the target file equals the
maximum record length minus 4 bytes (for the RL field).
About Data Exchange Operations
28