HP XP P9500 Storage - Manual (Page 75)

/dev/rsda AAAAAA 3390-3A MFN MVS1
/dev/asdb AAAAAA 3390-3A MFN VOS3
/dev/rsd ccccccc 3380-KB
/dev/rsd ddddddd 3380-KA
(1) (2) (3) (4) (5) (6)
end
(7)
Figure 35 Data Exchange Volume Definition File for Linux
.
Verifying Mainframe Dataset Requirements
FAL and FCU have specific requirements for the Data Exchange source and target datasets. Table
38 on page 75 specifies the requirements for Data Exchange datasets. The FCU GUI (see “ Performing
File Transfer Operations—UNIX ” on page 105 and“ Performing File Transfer
Operations—Windows ” on page 115) allows the user to display the dataset attributes and verify the
dataset requirements. The FCU for UNIX (version 01-01-41 and later) also provides the listvol
function to display mainframe dataset attributes without using the GUI. The FXotm target dataset (which
can also be an FXoto intermediate dataset) must be created and properly configured before the Data
Exchange operation is performed. The FCU does not support automatic expansion of the extent during
FXotm operations. The Data Exchange ALC utility allocates intermediate datasets in accordance with
the requirements specified below.
Table 38 Mainframe Dataset Requirements
Requirements Item
SAM (sequential-access method). Data Exchange does not support any other DO
types (for example, DAM, VSAM, PAM). If a non-SAM dataset is specified, Data
Exchange will return an error.
Multiple-volume datasets are not supported. Data Exchange can only process the
portion within one logical volume.
Dataset organization
(DO) type
No spaces. If Data Exchange encounters a space, it will accept the characters
before the space as the dataset name and continue processing.
Dataset name
Fixed-length or variable-length record format. Data Exchange does not support
undefined-length or spanned record formats. If an illegal RF is detected, Data
Exchange will return an error.
No key. If a record with a key is accessed, Data Exchange will return an error.
For FXotm, the record format of the target dataset must be preconfigured to match
the record format of the data entities in the source file.
For VSE source and target datasets, the VSE record option must be used to specify
the RF.
Record format (RF)
Any length within the extent supported by the OS. If an illegal BL is detected, Data
Exchange will return an error.
For FXotm, the block length of the target dataset must be preconfigured to match
the block length of the data entities in the source file.
For VSE source and target datasets, the VSE record option must be used to specify
the BL.
Block length (BL)
HP StorageWorks P9000 Data Exchange User Guide 75