Fcu file transfer options, Cc option – HP XP P9500 Storage User Manual

Page 20

Advertising
background image

CAUTION:

Do not write a signature on Data Exchange volumes having emulation types 3390-3

X, 3390-9X,

3390-L

X, 3380-KX, or 3380-3X (X = A, B, C) in a Windows environment. If a signature-writing

attempt is made by the Disk Administrator with Windows, a Write Error will appear in order to stop
the signature from being written. When the Windows Disk Administrator starts again, a request will
be made again to write the signature. Do not write the signature.

FCU File Transfer Options

For each Data Exchange operation, FCU requires that the transfer direction (mto or otm) and the
source and target files be identified. (An FXoto operation consists of one FXotm operation followed
by one FXmto operation.) In addition to these required parameters, FCU provides the following options
for Data Exchange file transfer operations:

Code conversion (CC)

Padding (PAD)

Delimiters (DEL)

Record description word (RDW)

VSE record (VSE)

Empty file (Emp)

NOTE:

For Data Exchange versions earlier than 01-

XX-50, Multiple Volume Dataset is not supported. When

a dataset is spanned over multiple volumes, only the portion of the dataset within one volume will be
processed. For Data Exchange versions 01-

XX-50 or later, Multiple Volume Dataset is supported only

for FXmto.

NOTE:

Data Exchange supports two kinds of mainframes, MVS and VSE. For Multiple Volume Dataset, Data
Exchange is only supported on MVS.

CC Option

The CC option can be used for FXmto and FXotm operations. The CC option enables you to specify
either the default EBCDIC-ASCII CC table included with FCU (see

Table 1

on page 21) or your own

CC table (see

Table 2

on page 22). When the default table is specified, FCU performs EBCDIC-to-ASCII

CC for FXmto operations and ASCII-to-EBCDIC CC for FXotm operations as specified in

Table

1

on page 21 (see also

Appendix A

on page 173). The user-defined CC table must be a binary data

file created by placing the target code values in the offset positions that correspond to the source
code values.

Always use CC when transferring text files between mainframe and open systems. Do not use CC
when transferring binary data files. CC is available (EcA option), but not recommended for FXoto file
transfers.

About Data Exchange Operations

20

Advertising