FXotm Operations

An FXotm operation transfers the data from an open-system file on an FX volume to a target dataset on an z/OS volume. The FXotm source file must be located on an FX -C or -A volume on the subsystem. 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 version 01-01-40 or later is required for VSE target datasets. FCU supports fixed- length and variable-length record formats for FXotm operations. FCU provides the following options for FXotm operations (see section FCU File Transfer Options): code conversion, padding (01-01-41 and later), 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

The table below 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.

Note: Do not update the volume that is transferred directly by the FXotm.

Table 2-5

FXotm Record Format Requirements

 

 

 

 

 

 

 

Record Format Requirements

 

 

 

 

 

 

 

FCU Direction

Source File

 

Target Dataset

See

 

 

 

 

Figure:

 

 

 

 

 

FXotm

Fixed-length: no padding, no delimiters

Fixed-length

3.8

 

 

 

 

FXotm

Fixed-length containing padding

Fixed-length

3.9

 

 

 

 

FXotm

Fixed-length containing delimiters

Fixed-length

3.10

 

 

 

 

FXotm

Fixed-length containing padding and delimiters

Fixed-length

3.11

 

 

 

 

FXotm

Variable-length: with delimiters

Variable-length

3.12

 

 

 

 

FXotm

Variable-length: with padding and delimiters

Fixed-length

3.13

 

 

 

 

 

2-24

About Cross-OS File Exchange Operations

Hitachi USP V Cross-OS File Exchange User’s Guide

Page 42
Image 42
Hitachi MK-96RD647-01 manual FXotm Operations, FXotm Record Format Requirements, Source File Target Dataset See