Fxotm operations, Multiple volume dataset/serial numbers – HP XP P9500 Storage User Manual

Page 31

Advertising
background image

NOTE:

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

Table 4 Multiple Volume Dataset/Serial Numbers

Dataset Serial Number

VTOC DSCB1

Except 1

Except 1

1

1

Last Volume Containing Data in this Dataset, in Dataset Indicators

Off

On

Off

On

Action

No(Yes)

No(Yes)

No(Yes)

Yes(Yes)

OTM

No(Yes)

No(Yes)

No(Yes)

Yes(Yes)

MTO for single volume

1

1

The dataset does not exist in the multiple volume definition file.

The inside of ( ): The spec of (a) or (b)

(a) Before version 01-XX-50

(b) Version 01-XX-50 and higher, and FAL_MULTI_CHECK of the environment variable is OFF.

FXotm Operations

An FXotm operation transfers the data from an open-system file on a Data Exchange volume to a
target dataset on a mainframe volume. The FXotm source file must be located on a Data Exchange
-C or -A volume on the storage system. The FCU does not automatically create the FXotm target dataset.
The target dataset must be created and properly formatted prior to beginning the FXotm operation.

The FCU software performs the FXotm data transfer operations. FCU supports fixed-length and
variable-length record formats for FXotm operations. FCU provides the following options for FXotm
operations (see

FCU File Transfer Options

” on page 20): code conversion, padding, delimiter, empty

file, and VSE record. The record description word option cannot be used with FXotm. FCU automatically
extracts delimiters from FXotm source files, but cannot add delimiters to FXotm source files. FCU can
add padding only to variable-length FXotm source files. FCU cannot extract padding from FXotm
source files. The types of FXotm operations are:

FXotm with fixed-length record format

FXotm with variable-length record format

Table 5

on page 32 specifies the record format requirements for each type of FXotm operation. An

open-system source file with fixed-length data entities can only be transferred to a fixed-length target
dataset. An open-system source file with variable-length data entities must have delimiters and can
be transferred to a variable-length or fixed-length target dataset. If the source file contains padding
from a previous FXmto transfer operation, the padding is transferred to the target dataset along with
the data. If the source file contains delimiters, the delimiters are not transferred to the target dataset.

HP StorageWorks P9000 Data Exchange User Guide

31

Advertising