beautypg.com

Fxmto with variable-length records: padding, Fxmto with variable-length records: delimiters, Figure 12 – HP XP P9500 Storage User Manual

Page 29: Figure 13

background image

NOTE:

If you use FXmto with padding, you will not be able to transfer the data back to the original dataset
later using FXotm.

Figure 12 FXmto with Variable-Length Records: Padding

.

With delimiters.

Figure 13

on page 29 shows an FXmto operation with delimiters for a variable-length

source dataset. The FCU extracts and transfers the data entities to the open-system target file and adds
the requested delimiter to the end of each data entity. The RL fields are not transferred. The resulting
length of each data entity in a UNIX target file equals the original data entity length plus 1 byte for
the delimiter. The resulting length of each data entity in a Windows target file equals the original
data entity length plus 2 bytes for the delimiter.

NOTE:

If you use FXmto with delimiters and without padding, you will be able to transfer the variable-length
records back to the original dataset later using FXotm.

Figure 13 FXmto with Variable-Length Records: Delimiters

.

With padding and delimiters.

Figure 14

on page 30 shows an FXmto operation with padding and

delimiters. FXmto with padding and delimiters requires a variable-length source file and produces a
fixed-length target file. FCU adds the appropriate delimiter to each data entity, adds the appropriate
amount of padding so that each record equals the maximum record length, and then extracts and
transfers the data entities with padding and delimiters to the open-system target file. The RL fields are
not transferred.

NOTE:

If you use FXmto with padding and delimiters, you will not to transfer the records back to the original
dataset later (the padding cannot be removed).

HP StorageWorks P9000 Data Exchange User Guide

29