Fxoto Operations; Fxotm With Variable-Length Records: Padding And Delimiters - HP StorageWorks P9000 User Manual

Figure 20 FXotm with Variable-Length Records: Padding and Delimiters
.
If the length of any data entity in a UNIX source file is greater than the specified record length plus
1 byte (CR or LF delimiter), the FCU aborts the operation and reports an error. If the length of any
data entity in a Windows source file is greater than the specified record length plus 2 bytes (CR+LF
delimiter), the FCU aborts the operation and reports an error.

FXoto Operations

FXoto operations transfer data from source files on one open-system platform to target files on another
open-system platform. Each FXoto file transfer consists of two separate Data Exchange operations:
first an FXotm operation transfers the data in the source file to an intermediate dataset, and then an
FXmto operation transfers the data from the intermediate dataset to the target file. For any users with
the all-open storage systems (no attached mainframe host), the intermediate datasets are allocated
on OPEN-x FMT volumes. The FMT utility enables you to format OPEN-x LUs (standard or custom size)
as FXoto volumes. The ALC utility enables you to allocate intermediate datasets on the OPEN-x FMT
volumes. For users with the multiplatform storage systems, the intermediate datasets can be allocated
on OPEN-x FMT volumes or on Data Exchange -A volumes, as desired. When you perform FXoto
operations that access OPEN-x FMT volumes, the FXoto volume definition file must be available for
use by FCU.
The FCU file transfer options (code conversion, padding, delimiters, and so on) 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 that contain the same characters as the delimiter (CR or LF) but are being used for purposes
other than delimiting data entities. If you specify the delimiter option for FXotm, the FCU will interpret
all occurrences of the specified delimiter characters 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 the 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 that access ALC-generated intermediate
datasets on OPEN-x FMT volumes. The only time you would use the VSE option is when transferring
HP StorageWorks P9000 Data Exchange User Guide 35