HP XP20000XP24000 Disk Array - Manual (Page 48)

2-30 About Cross-OS File Exchange Operations
Hitachi USP V Cross-OS File Exchange User’s Guide
Note: FCU version 01-01-41 or later is required for FXoto operations using
ALC-generated datasets on OPEN-x FMT volumes.
The FCU file transfer options (code conversion, padding, delimiters, etc.) can
be used on the FXotm and FXmto sub-operations as needed.
• Code conversion is not available for FXoto transfers.
• Padding can be used but will render the target file incompatible with the
source file due to the change in record format from variable-length to fixed-
length. If you use padding for the FXotm operation, the target file can be
transferred back to the same intermediate dataset but not back to the same
source file. If you use padding for the FXmto operation, the target file cannot
be transferred back to the same intermediate dataset or back to the same
source file.
• Delimiters can be used to enable bidirectional data transfers. When using
delimiters, watch out for files which contain the same character(s) as the
delimiter (CR and/or LF) but used for purposes other than delimiting data
entities. If you specify the delimiter option for FXotm, FCU will interpret all
occurrences of the specified delimiter character(s) as delimiters, which can
create a dataset with corrupt records or generate an error condition.
• The empty file option can be used to enable empty files to be processed. For
example, if a source file specified in your FXoto FCU parameter definition file
becomes empty, you can add the empty file option to the FXotm/mto
operations on that file to enable FCU to process the FCU parameter definition
file without errors.
• The RDW option is not normally used for FXoto operations. If you use the
RDW option (FXmto operation only), you will not be able to transfer the data
back to the same intermediate dataset.
• The VSE record option does not apply to FXoto operations which access ALC-
generated intermediate datasets on OPEN-x FMT volumes. The only time you
would use the VSE option is when transferring a file between open-system
platforms via a VSE dataset on a -A FX volume. In this case, you must use
the VSE record option for both transfers (FXotm/mto).
Host Access and I/O Contention
The user must manage access to the FXmto and FXotm volumes to prevent
illegal I/O access contention between the z/OS and open-system hosts. These
FX volumes cannot be accessed concurrently by the z/OS and open-system
hosts, and must be varied offline from the z/OS host during FX operations. The
FX volumes should not contain any regularly accessed data and should be
dedicated to data exchange operations to avoid accidental overwriting of data.