Hitachi MK-96RD647-01 User Manual

S

Hit achi Universal Storage Platform V

Cross-OS File Exchange User’s Guide

F

ASTFIND

L

INK

Document Organization
Product Version
Getting Help
Contents

MK-96RD647-01

r

Copyright © 2007 Hitachi Data Systems Corporation,
ALL RIGHTS RESERVED

Notice: No part of this public ation may be reproduced
or transmitted in any form or by a ny means, electronic
or mechanical, including photocopying and recording, o
stored in a database or retrieval system for any
purpose without the express written permission of
Hitachi Data Systems Corporation (hereinafter referred
to as “Hitachi Data Systems”).

Hitachi Data Systems reserves the right to make
changes to this document at any time without notice
and assumes no responsibility for its use. Hitachi Data
Systems products and services can only be ordered
under the terms and conditions of Hitachi Data
Systems’ applicable agreements. All of the features
described in this document may not be currently
available. Refer to the most recent p roduct
announcement or contact your local H itachi Data
Systems sales office for information on feature and
product availability.

This document contains the most curren t information
available at the time of publication. When new and/or
revised inform ation bec omes ava ilable, th is entire
document will be updated and distributed to all
registered users.

Hitachi Data Systems is a registered trademark and
service mark of Hitachi, Ltd., and the Hitachi Data
Systems design mark is a trademark and service mark
of Hitachi, Ltd.

All other brand or product names are or ma y be
trademarks or service marks of and are used to identify
products or services of their respective owners.

ii

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

Contents

Preface..................................................................................................vii

Overview of Hitachi Cross-OS File Exchange (FX).................................... 1-1

About Cross-OS File Exchange Operations.............................................. 2-1

Components.....................................................................................................2-2

FX Volume Types........................................................................................2-4

FCU File Transfer Options ..................................................................................2-7

Code Conversion (CC) Option ......................................................................2-8

PIPE Function...........................................................................................2-11

Using the PIPE function in UNIX Systems.............................................2-11

FAL/FCU Pipe Function Details.............................................................2-12

Pipe Function Time-Out Value.............................................................2-12

Padding (PAD) Option...............................................................................2-13

Delimiter (DEL) Option..............................................................................2-14

Empty File (Emp) Option...........................................................................2-14

Record Description Word (RDW) Option .....................................................2-16

VSE Record (VSE) Option...........................................................................2-16

FXmto Operations ...........................................................................................2-17

FXmto with Fixed-Length Record Format.................................................... 2-18

FXmto with Variable-Length Record Format ................................................2-19

FXmto with Multiple Volume Datasets.........................................................2-23

FXotm Operations ...........................................................................................2-24

FXotm with Fixed-Length Record Format ....................................................2-25

FXotm with Variable-Length Record Format ................................................2-28

FXoto Operations ............................................................................................2-29

Host Access and I/O Contention.......................................................................2-30

AIX Shared Open Function...............................................................................2-32

AIX Reserve Function ......................................................................................2-34

AIX Reserved Retry Function.....................................................................2-34

Contents iii

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

Environment Variables and Functions ........................................................ 2-34

Bidirectional Data Transfer.............................................................................. 2-36

Preparing for Cross-OS File Exchange Operations.................................... 3-1

System Requirements....................................................................................... 3-2

VSE Requirements and Restrictions ............................................................. 3-4

Compiler Requirements .............................................................................. 3-6

Maximum Data Size ...................................................................................3-7

Interoperability with HDLM......................................................................... 3-9

Installing and Configuring the FX Volumes........................................................ 3-10

Installing the FAL/FCU Software ...................................................................... 3-15

Installing FAL/FCU on UNIX-Based Platforms .............................................. 3-15

32-Bit FAL/FCU Software.................................................................... 3-15

64-Bit FAL/FCU Software.................................................................... 3-18

Installing FAL/FCU on Windows................................................................. 3-19

Uninstalling the FAL/FCU Software on UNIX-Based Plaforms........................ 3-20

Uninstalling FAL/FCU on Windows............................................................. 3-20

Entering the FX License Key Code.................................................................... 3-21

Creating FXoto Volumes Using the FMT Utility................................................... 3-22

Creating the FX Volume Definition File(s).......................................................... 3-28

Verifying Mainframe Dataset Requirements....................................................... 3-32

Allocating FXoto Intermediate Datasets............................................................ 3-33

Using the Cross-OS File Exchange Software............................................ 4-1

FCU for UNIX...................................................................................................4-2

FCU Version and Copyright Screen .............................................................. 4-2

File Conversion Utility Screen...................................................................... 4-4

File Menu Commands ..........................................................................4-8

Help Menu Commands......................................................................... 4-8

Error Information Screen.......................................................................... 4-10

FCU for Windows............................................................................................ 4-10

FCU Version and Copyright Dialog............................................................. 4-10

File Conversion Utility Window.................................................................. 4-12

Volume Information Dialog....................................................................... 4-14

Mainframe File Information Dialog............................................................. 4-14

Option Dialog .......................................................................................... 4-16

Parameter Line Dialog.............................................................................. 4-18

Execute Dialogs....................................................................................... 4-18

Error Information Dialog........................................................................... 4-20

Log Files ................................................................................................. 4-21

Format Utility for Windows.............................................................................. 4-22

Allocation Utility for Windows .......................................................................... 4-27

iv Contents

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

Performing Cross-OS File Exchange Operations....................................... 5-1

Performing File Transfer Operations - UNIX.........................................................5-3

Starting the FCU GUI for UNIX.....................................................................5-3

Performing File Transfer Operations (UNIX)..................................................5-6

Using the listvol Function (UNIX)............................................................5-8

Creating FCU Parameter Definition Files (UNIX).............................................5-9

Creating Multiple Volume Definition Files (UNIX) .........................................5-10

Using FCU from the Command Line (UNIX).................................................5-12

Performing File Transfer Operations – Windows.................................................5-17

Starting the FCU GUI ................................................................................5-17

Performing File Transfer Operations (Windows)...........................................5-19

Creating FCU Parameter Definition Files (Windows).....................................5-23

Creating Multiple Volume Definition Files (Windows)....................................5-25

Using FCU from the Command Line (Windows)...........................................5-27

Performing File Access Library (FAL) Operations ..................................... 6-1

FAL Requirements.............................................................................................6-2

FAL Functions...................................................................................................6-3

Converting Dataset Attribute Information .....................................................6-3

Opening a Dataset......................................................................................6-4

Reading Data .............................................................................................6-5

Writing Data...............................................................................................6-6

Closing a Dataset........................................................................................6-7

Acquiring Error Information.........................................................................6-7

Acquiring Dataset Attributes........................................................................6-8

Acquiring Attribute Information for a Specific Dataset .............................6-8

Acquiring Attribute Information for Multiple Datasets..............................6-9

Converting DO and RF Information ............................................................6-12

Converting the Dataset Organization (DO) Type Value ..........................6-12

Converting the Record Format (RF) Type Value....................................6-12

Using the FAL Functions ..................................................................................6-14

Multi-Thread Function......................................................................................6-18

Information Storage Area..........................................................................6-19

Open Dataset...........................................................................................6-20

Read Data................................................................................................6-22

Write Data ...............................................................................................6-23

Close Dataset........................................................................................... 6-24

Free Information Stored Area ....................................................................6-25

Initialize Target Record Pointer..................................................................6-26

Get Dataset Attribute Information..............................................................6-27

Get Specified Dataset Attribute Information.......................................... 6-27

Get Multiple Dataset Attribute Information...........................................6-28

Compiling.......................................................................................................6-31

Error Information............................................................................................6-32

FAL Usage Scenario........................................................................................ 6-33

Troubleshooting................................................................................... 7-1

Troubleshooting...............................................................................................7-2

Error Codes and Messages ................................................................................ 7-3

FCU Error Codes for UNIX........................................................................... 7-7

FCU Error Codes for Windows Systems...................................................... 7-16

Calling the Support Center .............................................................................. 7-21

EBCDIC-ASCII Code Conversion ............................................................ A-1

Acronyms and Abbreviations ..................................................... Acronyms-1

Index............................................................................................Index-1

vi Contents

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

Preface

This Hitachi TagmaStore® USP and NSC Cross-OS File Exchange (FX) User’s
Guide describes and provides instructions for installing and using the FX

feature of the Hitachi TagmaStore Universal Storage Platform V (USP V) and
Network Storage Controller (NSC) disk array subsystems.

Please read this document carefully to understand how to use this product,
and maintain a copy for reference purposes.

This preface includes the following information:

 Intended Audience
 Product Version
 Document Revision Level
 Changes in this Revision
 Document Organization
 Referenced Documents
 Document Conventions
 Convention for Storage Capacity Values
 Getting Help
 Comments

Notice: The use of Cross-OS File Exchange and all other Hitachi Data Systems
products is governed by the terms of your agreement(s) with Hitachi Data
Systems.

Preface vii

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

Intended Audience

This document is intended for system administrators, Hitachi Data Systems
representatives, and Authorized Service Providers who are involved in
installing, configuring, and operating the Hitachi Universal Storage Platform V
storage system.

This document assumes the following:

• The user has a background in data processing and understands RAID

storage systems and their basic functions.

• The user is familiar with the Hitachi Universal Storage Platform V storage

system and has read the Universal Storage Platform V User and Reference
Guide.

• The user is familiar with the Storage Navigator software for the Universal

Storage Platform V and has read the Storage Navigator User’s Guide.

• The user is familiar with the operating system and web browser software

on the system hosting the Storage Navigator software.

Product Version

This document revision applies to Universal Storage Platform V microcode
60-03-x and higher.

Document Revision Level

Revision Date Description

MK-96RD647-P February 2007 Preliminary Release
MK-96RD647-00 April 2007 Initial Release, supersedes and repl aces MK-96RD647-P
MK-96RD647-01 May 2007 Revision 1, supersedes and repl aces MK-96RD647-00

Changes in this Revision

Not applicable to this release.

viii Preface

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

Document Organization

The following table provides an overview of the contents and organization of
this document. Click the chapter title
The first page of each chapter provides links to the sections in that chapter.

Chapter Description

in the left column to go to that chapter.

Overview of Cross-OS File
Exchange

About FX Operations

Preparing for FX Operations

Using FX Software

Performing FX Operations This chapter describes how to operate FX.
Performing FAL Operations This chapter describes how to perform FAL operations using FX.
Troubleshooting This chapter provides descriptions of error codes and supp ort desk contact data.
Acronyms and Abbreviations Defines the acronyms and abbreviations used in this document.
Index Lists the topics in this document in alphabetical order.

Referenced Documents

Hitachi Universal Storage Platform V:

• Command Control Interface (CCI) User and Reference Guide, MK-90RD011

This chapter provides a brief overview FX functions, features, and benefits.

This chapter describes how FX operates in typical system configurations and
describes the operations a user may perform using FX.

This chapter describes the system requirements and volume configuration
necessary to run and operate FX. It also provides instructions on how to install
FX.

This chapter describes the user interface and the commands available to an FX
user.

• LUN Manager User’s Guide, MK-96RD615

• User and Reference Guide, MK-96RD635

• Storage Navigator User’s Guide, MK-96RD621

<Other Hitachi product (e.g., TagmaStore USP/NSC, HiCommand)>:

• HiCommand

Preface ix

®

Device Manager Web Client User’s Guide, MK-91HC001

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

Document Conventions

The terms “Universal Storage Platform V” and “USP V” refer to all models of
the Hitachi Universal Storage Platform V, unless otherwise noted.

This document uses the following typographic conventions:

Typographic Convention Description

Bold

Italic

screen/code

< > angled brackets

[ ] square brackets

{ } braces

| vertical bar

underline Indicates the default value. Example: [ a | b ]

Indicates text on a window, other than the window title, including menus, menu
options, buttons, fields, and labels. Example: Click OK.

Indicates a variable, which is a placeholder for actual text provided by the user or
system. Example: copy source-file target-file

Note: Angled brackets (< >) are also used to indicate varia bles.
Indicates text that is displayed on screen or entered by the user. Example: #

pairdisplay -g oradb

Indicates a variable, which is a placeholder for actual text provided by the user or
system. Example:

Note: Italic font is also used to indicate variables.
Indicates optional values. Example: [ a | b ] indicates that you can choose a, b, or

nothing.
Indicates required or expected values. Example: { a | b } indicates that you must

choose either a or b.
Indicates that you have a choice between two or more options or arguments.

Examples:

[ a | b ] indicates that you can choose a, b, or nothing.
{ a | b } indicates that you must choose either a or b.

# pairdisplay -g <group>

This document uses the following icons to draw attention to information:

Icon Meaning Description

Note Calls attention to important and/or additional information.

Tip

Caution

WARNING

DANGER

ELECTRIC SHOCK
HAZARD!

ESD Sensitive

Provides helpful information, guidelines, or suggestions for performing tasks more
effectively.

Warns the user of adverse conditions and/or consequences (e.g., disruptive
operations).

Warns the user of severe conditions and/or consequences (e.g., destructive
operations).

Dangers provide information about how to avoid physical injury to yourself and
others.

Warns the user of electric shock hazard. Failure to take appropriate precautions
(e.g., do not touch) could result in serious injury.

Warns the user that the hardware is sensitive to electrostatic discharge (ESD).
Failure to take appropriate precautions (e.g., grounded wriststrap) could result in
damage to the hardware.

x Preface

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

Convention for Storage Capacity Values

Physical storage capacity values (e.g., disk drive capacity) are calculated
based on the following values:

1 KB = 1,000 bytes
1 MB = 1,000
1 GB = 1,000
1 TB = 1,000
1 PB = 1,000

Logical storage capacity values (e.g., logical device capacity) are calculated
based on the following values:

1 KB = 1,024 bytes
1 MB = 1,024
1 GB = 1,024
1 TB = 1,024
1 PB = 1,024
1 block = 512 bytes

Getting Help

If you need to call the Hitachi Data Systems Support Center, make sure to
provide as much information about the problem as possible, including the
circumstances surrounding the error or failure and the exact content of any
messages displayed on the z/OS and/or open-system hosts. Please collect the
following information before you call for technical support:

2

bytes

3

bytes

4

bytes

5

bytes

2

bytes

3

bytes

4

bytes

5

bytes

• Error codes: FCU error code, FAL error code, SYS error code. Use the FCU

GUI to check recent error information (Help-Error command for UNIX,
View-Error information command for NT).

• FCU parameters: direction (mto or otm), input and output files, and FCU

options (code conversion, padding, delimiter, empty file, RDW, VSE
record).

• FX volume definition file: contents

• FCU parameter definition file (if used): contents

• Command line log (if possible).

• FAL error logs. The FAL logs for UNIX are /tmp/fal_error and

/tmp/fal_error.bak, and /tmp/fal_dump and /tmp/fal_dump.bak. The FAL
logs for Windows 2000/2003/Windows NT systems are c:\fal_error and
c:\fal_error.bak, and c:\fal_dump and c:\fal_dump.bak.

• Windows 2000/2003/Windows NT systems only: FCU log file (e.g.,

fcudata.prm.log), and Dr. Watson’s log file (e.g.,
c:\WINNT\DRWTSN32.LOG).

• Syslog: error information and other applicable contents

Preface xi

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

The Hitachi Data Systems customer support staff is available 24 hours/day,
seven days a week. If you need technical support, please call:

• United States: [phone]

• Outside the United States: [phone]

xii Preface

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

Comments

Please send us your comments on this document. Make sure to include the
document title, number, and revision. Please refer to specific section(s) and
paragraph(s) whenever possible.

• E-mail: [e-mail]

• Fax: [phone]

• Mail:

Technical Writing, M/S 35-10
Hitachi Data Systems
10277 Scripps Ranch Blvd.
San Diego, CA 92131

Thank you! (All comments become the property of Hitachi Data Systems
Corporation.)

Preface xiii

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

1

Overview of Hitachi Cross-OS File

Exchange (FX)

This chapter provides a brief overview FX functions, features, and benefits.
The Hitachi Cross-OS File Exchange (FX) feature enables data stored on the

TagmaStore
and open-system platforms and between different open-system platforms. The
FX mainframe-to-open (FXmto) capability enables you to transfer data from
z/OS (mainframe) datasets to open-system files. The FX open-to-mainframe
(FXotm) capability enables you to transfer data from open-system files to z/OS
datasets. The FX open-to-open (FXoto) capability enables you to transfer data
between open-system platforms without being attached to a z/OS host. FX
utilizes special FX volumes which are dedicated to data exchange operations
and are accessed as raw devices to provide the greatest platform flexibility for
multiplatform data exchange.

The Hitachi TagmaStore USP and NSC subsystems support concurrent
attachment to z/OS hosts and multiple open-system platforms, including

®

UNIX
platforms (e.g., Windows NT, Novell
NSC subsystems provide high-speed response, continuous data availability,
scalable connectivity, and expandable capacity for both z/OS and open-system
storage. The TagmaStore USP and NSC subsystem can operate with multihost
applications and host clusters, and is designed to handle very large databases
as well as data warehousing and data mining applications that store and
retrieve terabytes of data.

®

USP subsystems to be converted and transferred between z/OS®

based platforms (e.g., Solaris, HP-UX, IBM® AIX®) and PC server

®

NetWare®). The TagmaStore USP and

The Hitachi TagmaStore USP and NSC subsystems provide the following host
connectivity options:

• Multiplatform: Both fibre-channel (FC) ports and ExSA™ (ESCON) ports.

• All open: All fibre-channel (FC) ports (no ExSA). This type of subsystem is

called an all-open subsystem. FX can be used on the all-open TagmaStore
subsystems for FXoto file transfers.

Overview of Hitachi Cross-OS File Exchange (FX) 1-1

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

• All mainframe. The TagmaStore subsystems can be configured with all

ExSA (no FC ports). This type of subsystem is called an all-mainframe
subsystem. FX is not used on the all-mainframe TagmaStore subsystem.

Note: The Hitachi Multiplatform Backup (MBU) feature of the TagmaStore USP
and NSC subsystem enables you to implement z/OS-based backup/restore
operations (device-level only) for the open-system data stored on the
multiplatform TagmaStore USP and NSC. For further information on HMBR,
please refer to the Hitachi Multiplatform Backup (MBU) (MK-94RD209) or
contact your Hitachi Data Systems account team.

Note: For FAL/FCU 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 FAL/FCU
versions 01-XX-50 or later, Multiple Volume Dataset is supported only for
FXmto.

Note: FAL/FCU supports two kinds of mainframes, MVS

TM

and VSE®. For

Multiple Volume Dataset, FAL/FCU is only supported on MVS.
Note: When the mainframe OS is VSE, the supported version is 2.3 or earlier.
FX provides the following benefits for the user:

• FX provides a centralized data management and disaster recovery

environment for both z/OS and open-system data.

• FX provides high-speed data transfer over ExSA™ (ESCON ®) and fibre

channels, freeing up valuable network resources and communication links
for application use.

• FX’s high-speed data exchange enables you to implement file-level backup

of open-system data to z/OS storage (e.g., using Harbor).

1-2 Overview of Hitachi Cross-OS File Exchange (FX)

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

Overview of Hitachi Cross-OS File Exchange (FX) 1-3

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

2

About Cross-OS File Exchange

Operations

This chapter describes how FX operates in typical system configurations and
describes the operations a user may perform using FX.

 Components
 FCU File Transfer Options
 FXmto Operations
 FXotm Operations
 FXoto Operations
 Host Access and I/O Contention
 AIX Shared Open Function
 AIX Reserve Function
 Bidirectional Data Transfer

About Cross-OS File Exchange Operations 2-1

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

Components

Figure 2-1 illustrates the typical system configurations required for FXmto and
FXotm operations. FXmto/otm operations are performed using the File
Conversion Utility (FCU) and File Access Library (FAL), which are installed on
the open-system host(s).

Application program

Utility program

OS (MVS or VSE)

ExSA (ESCON®) interface

Database 1

(e.g., DB2/XD)M)

(CKD format) (FBA format) (FBA format)(CKD format)

Volume dedicated

to S/390®

by S/390 and UNIX/PC server

Intermediate

file 1 (SAM

dataset)

Volume shared

File Conversion Utility

(FCU)

File Access

Library (FAL)

OS (UNIX, PC server)

Fibre-channel interface

Intermediate

file 2 (UNIX/PC

server)

Volumes dedicated to open system

Application program

Utility program

Database 2

(e.g., ORACLE)

Figure 2-1 FXmto and FXotm System Configuration

Figure 2-2 illustrates the typical system configurations required for FXoto
operations, which are performed using the Formatter (FMT) and Allocater
(ALC) utilities in addition to FCU and FAL.

2-2 About Cross-OS File Exchange Operations

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

Application

program

Utility program

File Conversion

Utility (FCU)

File Access

Library

(FAL)

Formatter/

Allocater

(FMT/ALC)

File Conversion

Utility (FCU)

Formatter/

Allocater

(FMT/ALC)

File Access

Library

(FAL)

Application

program

Utility program

OS (UNIX, PC server)

Fibre-channel interface

Open-System

Files

(FBA format)

Volume dedicated to open system

Intermediate File

(SAM dataset)

Shared volume (initialized as mainframe

CKD format by FMT/ALC)

OS (UNIX, PC server)

Fibre-channel interface

Open-System

Files

(FBA format)(CKD format)

Volume dedicated to open system

Figure 2-2 FXoto Syst em Configuration

The FCU program provides the commands and graphical user interface (GUI)
for FX file transfer operations as well as several important options for data
exchange, including EBCDIC-ASCII code conversion and data record padding
and delimiters. The FAL is a library of C functions (Visual C++

®

NT

), which provides an application-programming interface for data exchange.

®

for Windows

The FAL functions can be called by user application programs to read and write
data in z/OS datasets on the TagmaStore USP and NSC. There are two types
of FAL, the 32bitFAL and the 64bitFAL. The latter is provided by the
TagmaStore USP and NSC. The FMT and ALC utilities enable the all-open
TagmaStore USP and NSC user to format OPEN-x logical units (LUs) and
create intermediate datasets for FXoto operations, without having to be
attached to any z/OS hosts. OPEN-x is defined as a standard LU type. The
TagmaStore USP and NSC subsystem currently supports OPEN-3, OPEN-8,
OPEN-9, OPEN-E, OPEN-L and OPEN-V devices. Please contact your Hitachi
Data Systems account team for the latest information on supported LU types.

About Cross-OS File Exchange Operations 2-3

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

FX Volume Types

The FXmto and FXotm volumes are z/OS devices that can only be accessed by
open-system hosts using the FAL/FCU software. The FXoto volumes are open­system devices that cannot be accessed by z/OS hosts. FX operations are
performed using the following types of FX volumes on the TagmaStore USP
and NSC subsystems:

• FXmto, FXotm. The FX -A volumes can be used for FXmto and FXotm

operations. z/OS hosts have normal read/write access to -A volumes. Open­system hosts have read/write access to -A volumes but must use FAL/FCU to
access these volumes as raw devices (no mount operation).
the structure of the FX -A volumes.

MAINFRAME OPEN SYSTEM

Figure 2-3 shows

Cyl#0

Read/Write

Cyl# max.

Cyl# 0

Read/Write

Cyl# MAX.

Label area

VTOC

Datasets

Management area

Figure 2-3 3390-3A/9A/LA Volume Structure (FXmto, FXotm,

FXoto)

Note: The -A volumes are not write-protected. Do not execute any open­system write operations to -A volumes (except disk partitioning and
labeling). Do not create a file system on an -A volume; this will overwrite
the data exchange files on the volume.

• FXmto. The FX -B volumes can only be used for FXmto operations. z/OS

hosts have normal read/write access to -B volumes. Open-system hosts have
read-only access to -B volumes and must use FAL/FCU to read these volumes
as raw devices (no mount operation). The -B volumes are write-protected
from open-system access. The TagmaStore subsystem will reject all open­system write operations to -B volumes (except disk partitioning and labeling)
to protect the z/OS data on these volumes.
the FX -B volumes.

Figure 2-4 shows the structure of

2-4 About Cross-OS File Exchange Operations

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

MAINFRAME

y

y

C

l# 0

Label area

VTOC

OPEN SYSTEM

Cyl# 0
Read/Write

Read/Write

Cyl# MAX.

Datasets

Management area

Read only

Read/Write
Cyl# max.

Figure 2-4 3390-3B/9B/LB Volume Structure (FXmto)

Note: The open-system host accesses only the volume table of contents
(VTOC) area on -B volumes. Catalog or security control functions cannot be
used to provide access control for these volumes.

• FXotm. The FX -C volumes can only be used for FXotm operations. Open-

system hosts have read/write access to the -C volumes but must use
FAL/FCU to access these volumes as raw devices (no mount operation). z/OS
hosts have read-only access to the -C volumes. The TagmaStore subsystem
will reject all z/OS write operations to -C volumes (except VTOC) to protect
the open-system data on these volumes.
the FX -C volumes.

MAINFRAME

l# 0

C

Read/Write

Label area

VTOC

OPEN SYSTEM

Cyl# 0

Figure 2-5 shows the structure of

Read/Write

Read only

Cyl# MAX.

Datasets

Management area

Cyl# max.

Figure 2-5 3390-3C/9C/LC, 3380-KC/3C Volume Structure (FXotm)

• FXoto. OPEN-x volumes that are formatted with the FX Formatter (FMT)

utility can only be used for FXoto operations. Open-system hosts have
read/write access to the OPEN-x FMT volumes but must use FAL/FCU to
access these volumes as raw devices (no mount operation). z/OS hosts do
not have any access to the OPEN-x FMT volumes.
structure of the FX OPEN-x FMT volumes.

About Cross-OS File Exchange Operations 2-5

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

Figure 2-6 shows the

MAINFRAME OPEN SYSTEM

Cyl#0

Read/Write

Cyl# max.

Cyl# 0

No Access

Cyl# MAX.

Label area

VTOC

Datasets

Management area

Figure 2-6 OPEN-x FMT Volume Structure (FXoto)

Note: When the mainframe OS is VSE, DFSORT cannot be used after an FX
volume is copied to another volume. Use the DITTO function for this
purpose.

2-6 About Cross-OS File Exchange Operations

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

Note for AIX: When installing FX devices in an AIX environment, the following
notes apply:

• When the UserID is not the root, a patch is required.

• AIX V5.1 can be used with 64bitFAL.

Please contact your IBM technical representative for assistance.
Note for Microsoft Cluster Server: When installing FX devices in a Microsoft

Cluster Server (MSCS) environment, you must write signatures on the FX
volumes before configuring MSCS.

• The MSCS server cannot connect volumes that do not have signatures.

• The volume on which a signature is written cannot be accessed from another

server.

• The volume on which a signature is written cannot be shared.

• Only the mainframe and the server that wrote the signature can access the

volume that has the signature.

• Signatures cannot be written to FX volumes for which the emulation type is

3390-3X, 3390-9X 3390-LX , or 3380-KX, 3380-3X (X = A, B, C), when the
OS server is Windows 2000/2003/Windows NT.

• When configuring MSCSand the server OS is Windows 2000/2003/Windows

NT, FXotm and FXmto cannot be started.

Notes for Windows 2000/2003/Windows NT:

• Service Pack 1 must be installed when MSCS is configured

• A signature is not necessary for the MSCS configuration. A Write Error will

occur if a signature is attempted.

Warning: Do not write a signature on FX Volumes having emulation types
3390-3X, or 3390-9X, 3390-LX, or 3380-KX, 3380-3X (X=A,B,C) in a Windows
2000/2003/Windows NT environment. If a signature-writing attempt is made
by the Disk Administrator with Windows 2000/2003/Windows NT, a Write Error
will appear in order to stop the signature from being written. When the
Windows 2000/2003/Windows NT 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 FX 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 FX file transfer
operations:

About Cross-OS File Exchange Operations 2-7

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

• Code conversion (CC)

• Padding (PAD)

• Delimiters (DEL)

• Record description word (RDW)

• VSE record (VSE)

• Empty file (Emp)

Note: For FAL/FCU 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 FAL/FCU
versions 01-XX-50 or later, Multiple Volume Dataset is supported only for
FXmto.

Note: FAL/FCU supports two kinds of mainframes, MVS and VSE. For Multiple
Volume Dataset, FAL/FCU is only supported on MVS.

Code Conversion (CC) Option

The code conversion option can be used for FXmto and FXotm operations. The
code conversion option enables you to specify either the default EBCDIC-ASCII
code conversion table included with FCU (see
conversion table (see
performs EBCDIC-to-ASCII code conversion for FXmto operations and ASCII­to-EBCDIC code conversion for FXotm operations as specified in
also Appendix C). The user-defined code conversion 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.

Table 2-2). When the default table is specified, FCU

Table 2-1), or your own code

Table 2-1 (see

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

Note: FCU versions 01-01-40 and later support the user-defined code
conversion table.

Note: The default EBCDIC-ASCII code conversion table is the ACM standard
table (not CACM). Appendix C provides the code conversion information for the
default table which is shown in
does not yield the desired results, create your own code conversion table.
Please refer to the IBM code tables for detailed information on EBCDIC-ASCII
code conversion.

2-8 About Cross-OS File Exchange Operations

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

Table 2-1. If the default code conversion table

Table 2-1 Default EBCDIC-ASCII Code Conversion Table for FCU

H L

0 1 2

NUL

0

(00)

SO

1

H

(01)

STX

2

(02)

ETX

3

(03)

PF

4

(9C)

HT

5

(09) (85)

LC

6

(86)

DEL

7

(7F)

GE

8

(97)

RLF

9

(8D)

SM

A

M

(8E)

VT

B

(0B

)

FF

C

(0C

)

CR

D

(0D

)

SO

E

(0E)

SI

F

(0F)

DLE

(10)

DC1

(11)

3 4 5

DS

(80) (90)

SO

S

SP

(20) & (26) - (2D) (BA) (C3) (CA) (D1) (D8) { (7B) } (7D) \ (5C) 0 (30)

(91) (A0) (A9) / (2F) (BB) a (61) j (6A) (E5) (D9) A (41) J (4A) (9F) 1 (31)

6 7

8 9 A B C D E

(81)

DC2

FS

SYN

(12)

(82)

(16) (A1) (AA) (B2) (BC) b (62) k (6B) s (73) (DA) B (42) K (4B) S (53) 2 (32)

DC3

(13) (83) (93) (A2) (AB) (B3) (BD) c (63) l (6C) t (74) (DB) C (43) L (4C) T (54) 3 (33)

TM

BYP

PN

(9D)

(84)

(94) (A3) (AC) (B4) (BE) d (64) m (6D) u (75) (DC) D (44) M (4D) U (55) 4 (34)

LF

RS

(0A)

(95) (A4) (AD) (B5) (BF) e (65) n (6E) v (76) (DD) E (45) N (4E) V (56) 5 (35)

BS

ETB

UC

(08)

(17)

(96) (A5) (AE) (B6) (C0) f (66) o (6F) w (77) (DE) F (46) O (4F) W (57) 6 (36)

IL

ESC

EOT

(87)

(1B)

(04) (A6) (AF) (B7) (C1) g (67) p (70) x (78) (DF) G (47) P (50) X (58) 7 (37)

CAN

(18) (88) (98) (A7) (B0) (B8) (C2) h (68) q (71) y (79) (E0) H (48) Q (51) Y (59) 8 (38)

EM

(19)

CC

(92)

CUI

(8F)

IFS
(1C

IGS
(1D

IRS

(1E)

IUS

(1F)

)

)

(89) (99)

SW
(8A

(9A

)

CUI

CU3

(8B

(9B

)

DC4
(14)

(8C

)

EN

NAK

Q

(15) ( (28) ) (29) _ (5F) ’ (27)

(05)
ACK

(06) (9E)

BEL

SUB

(07)

(1A

)

)

)

(A8

(B1

)

)
!

(21)

(D5

)

.

(2E) $ (24)

<

*

(3C

(2A

)

)

;

+

(3B

(2B

(7C

)

)
|

~

(7E) ? (3F) “ (22)

)

‘

(60) i (69) r (72)

(B9

)

:

(CB

(3A

)

)

,

#

(23)

(2C

)

%

(25) @ (40)

>

=

(3E)

(3D

)

(C4

)

(C5

)

(C6

)

(C7

)

(C8

)

(C9

)

z

(E1) I (49) R (52)

(7A

)

^

(5E)

(CC

)

(CD

)

(CE

)

(CF)

(D0

)

(E2) (E8) (EE) (F4) (FA)

(D2

)

(E3) (E9) (EF) (F5) (FB)

(D3

)

(D4

(5B

(D6

(D7

(E4)

)
[

]

(5D

)

)

(E6)

)

(E7)

)

(F0) (F6) (FC)

(EA

)

(F1) (F7)

(EB

)

(F2) (F8) (FE)

(EC

)

(F3) (F9) (FF)

(ED

)

Z

(39)

(5A

)

(FD

F

9

)

Note: Appendix C shows the EBCDIC-ASCII code conversion information for
this binary table.

Legend for Table 3-1

ASCII

About Cross-OS File Exchange Operations 2-9

Bit
Positions

Hi Lo

8765 4321

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

EBCDIC (IBM)

0123 4567

2-10 About Cross-OS File Exchange Operations

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

Table 2-2 User-Defined Code Conversion Table

Item Requirement(s)

Size 256 bytes
Format Binary data
Code length One byte (two-byte codes cannot be converted)
File name

The following sequences of characters cannot be used in the file
name:
EA EcA EkJ No
If the file name for the code conversion table contains any of these
sequences, FCU will ignore the file and use the default table instead.

PIPE Function

This function transfers data entries from the mainframe to the application
program or the utility program for UNIX systems using a “named pipe”. When
this function is used, a mainframe dataset can be transferred to an open
system. This is a much faster way to transfer data than the Code Conversion
method.

A "named pipe" is a special file that is used to transfer data between unrelated
processes. One (or more) processes writes to it, while another process reads
from it. Named pipes are visible in the file system and may be viewed with ‘ls’
like any other file. (Named pipes are also called "fifo"s; this term stands for
`First In, First Out'.) Named pipes may be used to pass data between
unrelated processes, while normal (unnamed) pipes can only connect
parent/child processes (with some exceptions). Named pipes are strictly
unidirectional, even on systems where anonymous pipes are bidirectional (full­duplex).

Using the PIPE function in UNIX Systems

A "named pipe" is a special file that is used to transfer data between unrelated
processes. One (or more) processes write to it, while another process reads
from it. Named pipes are visible in the file system and may be viewed with `ls'
like any other file. (Named pipes are also called "fifo"s; this term stands for
`First In, First Out'.) Named pipes may be used to pass data between
unrelated processes, while normal (unnamed) pipes can only connect
parent/child processes (unless you try *very* hard). Named pipes are strictly
unidirectional, even on systems where anonymous pipes are bidirectional (full­duplex).

About Cross-OS File Exchange Operations 2-11

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

FAL/FCU Pipe Function Details

FCU can carry out data transmission to a pipe file. A user application opens
and reads this pipe file, and a direct data transmission is attained between the
application and FCU. There is no need for it to be output as a file on an HDD.

A named-pipe name is specified in a parameter definition file as the output file
name. “PIPE=Yes” needs to be specified as an option. Under these
conditions, FCU will open a pipe file with the specified output file name, and
will transmit data to it.

If the specified file exists as a standard UNIX file, FCU re-creates a pipe file
using the same name (the UNIX file is deleted.) Since FCU only inputs in data
to a pipe, the FCU function needs to obtain the data via a user application. If
data remains in the pipe, FCU will stop and processing does not progress to
the next step. The FCU function has an inbuilt timer. If the application does
not continue receiving data, FCU will send an error message after a certain set
time, and it will progress to the next logical process.

Note: This function is only supported for UNIX systems. It is not supported for
Windows 2000/2003/Windows NT. It is supported for mainframe to open
systems data transfer only. This function requires an application program or a
utility program to receive data entries using a named pipe.

Pipe Function Time-Out Value

• FCU waits for a “Read Data Entries” status message. A time-out error will be

reported if the TIME OUT VALUE is not set appropriately. The TIME OUT
VALUE should be set in the WAIT_TIME_VALUE environment variable. The
limits are 0~1440 seconds (0 = unlimited). The default value is 10 when the
timeout value is undefined.

• The following examples illustrate the use of the WAIT_TIME_VALUE

environment variable.

Note: After setting the variable, log out and log in again to establish the
variable’s value.

• Example 1: For C shell:

– Add “setenv WAIT_TIME_VALUE 300” to the file“.cshrc” in the home

directory.

– If “.cshrc” does not exist, create it and add the “setenv” line.

• Example 2: For non-C shell:

– Add “WAIT_TIME_VALUE=300"
– Add "export WAIT_TIME_VALUE"

These two commands must be added to the file “.dtprofile” in the home
directory. If “.dtprofile” does not exist, create it and add the lines.

2-12 About Cross-OS File Exchange Operations

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

Figure 2-7 illustrates the Pipe function process.

FCU Application/Utility Program

.

start

|

create a named pipe

|

open pipe(‘w’ mode)

|

waiting send data entries

|

send data OK

|

write data

|

close pipe

|

open pipe(‘r’ mode)

waiting receive data entries

receive data OK

|
|

|
|

|
|

read data

|

close pipe

|
|

end

Figure 2-7 Pipe Function Process Outline

Padding (PAD) Option

The padding option can be used for FXmto with variable-length source
datasets and for FXotm with fixed-length target datasets. When the padding
option is specified for FXmto, FCU adds padding to each source data record, so
that the length of the each record equals the maximum record length. When
padding is specified for FXotm, FCU adds padding to each source data entity,
so that the length of the each target record equals the record length defined
for the target dataset. FCU transfers the data entities with padding to the
target file/dataset. FCU cannot extract padding from files or datasets. Sections
FXmto Operations and FXmto with Multiple Volume Datasets describe FXmto
and FXotm operations with padding.

The type of padding added by FCU depends on whether code conversion was
also requested:

• Padding with code conversion (text files). When padding and code

conversion are both specified, FCU adds spaces to the short data entities as
needed.

• Padding without code conversion (binary data files). When padding is

specified but code conversion is not, FCU adds 0x00 to the short data
entities as needed.

About Cross-OS File Exchange Operations 2-13

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

Note: If you use FXmto with padding, the data cannot be transferred back to
the original z/OS dataset (the FXotm target dataset will not be compatible with
the original dataset). If you use FXotm with padding, the delimiter option is
required.

Delimiter (DEL) Option

The delimiter option can be used for both FXmto and FXotm operations and
enables variable-length records to be transferred between platforms without
losing compatibility with the original dataset. When the delimiter option is
specified for FXmto, FCU adds the specified delimiter to the end of each data
entity in the source file, and then extracts and transfers the data entity with
delimiter to the open-system target file. When the delimiter option is specified
for FXotm, FCU extracts each data entity preceding the specified delimiter and
transfers the data entities without delimiters to the target dataset. Sections
FXmto Operations and FXmto with Multiple Volume Datasets describe FX
operations with delimiters.

The type and length of the delimiter added (or recognized and extracted) by
FCU depends on the open-system platform:

• For UNIX-based platforms, you must specify either a carriage return (CR) or

a line feed (LF). The length of this delimiter is one byte.

• For Windows 2000/2003/Windows NT, you must specify a CR + LF. The

length of this delimiter is two bytes.

Note: Do not use the delimiter option for FXotm if the source file contains
the same character(s) as the delimiter but used for a purpose other than
delimiting data entities. If you do, FCU will interpret the specified delimiter
character(s) as delimiters, which can create a target dataset with corrupt
records or generate an error condition.

Note: If you use FXmto with delimiter (no padding) for variable-length
records, you will be able to transfer the data back to the original z/OS dataset
later using FXotm.

Empty File (Emp) Option

The empty file (Emp) option can be used for both FXmto and FXotm
operations. When the empty file option is specified, FCU processes an empty
source file instead of returning an error. An empty z/OS dataset is a dataset
which has no records or only EOF records. An empty open-system file is a file
which has a file size of 0 bytes. When an empty z/OS dataset is processed, the
open-system target file size = 0. When an empty open-system file is
processed, the target dataset will contain only EOF records.

2-14 About Cross-OS File Exchange Operations

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

Note: FCU version 01-01-38 or later for UNIX and FCU version 01-01-36 or
later for Windows 2000/2003/Windows NT are required for the empty file
option.

About Cross-OS File Exchange Operations 2-15

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

Record Description Word (RDW) Option

The record description word option can only be used for FXmto operations on
variable-length source datasets.
RDW option specified. When the RDW option is specified, FCU adds the record
description word in binary code to the head of each record in the source
dataset, and then transfers the data entity with record length bytes to the
open-system target file. The CC, PAD, and DEL parameters must be No; if not,
FCU returns an error. If the RDW option is specified for a fixed-length source
dataset, FCU ignores the RDW option.

Note: If you use FXmto with RDW, the data cannot be transferred back to the
original z/OS dataset (the FXotm target dataset will not be compatible with the
original dataset).

Note: FCU version 01-01-38 or later for UNIX and FCU version 01-01-36 or
later for Windows 2000/2003/Windows NT are required for the RDW option.

Source Dataset Open-System Target File

RL Record 1: Data entity 1 RL Data entity 1
RL Record 2: Data entity 2

Record length Record length

Figure 2-8 shows an FXmto operation with the

→

RL Data entity 2

RL Record 3: Data entity 3 RL Data entity 3

Figure 2-8 FXmto with the RDW Option

VSE Record (VSE) Option

The VSE record option must be used for FXmto and FXotm operations
involving VSE datasets. The VTOC of a VSE dataset does not specify the record
format (RF), record length (RL), or block length (BL) of the dataset. The VSE
record option enables the user to specify these values so that FCU can process
source/target VSE datasets. If you do not specify the VSE record option for a
VSE dataset, FCU will return an error. If you specify the VSE record option and
the RF, RL, and BL are also specified in the VTOC, FCU will process the dataset
if the RF, RL, and BL values are the same, or return an error if the RF, RL, and
BL values are not the same. The VSE record option does not apply to ALC­generated intermediate datasets.

Note: FCU version 01-01-40 or later is required for the VSE record option.

2-16 About Cross-OS File Exchange Operations

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

FXmto Operations

An FXmto operation transfers the data from a z/OS dataset on an FX volume
to an open-system file on an open-system LU. The object data entities are
those contained in all records between the beginning of the file and the end of
the file. The end of a dataset is the EOF record or the end of the final extent.
The end of an open-system file is the EOF. The FXmto source file must be
located on an FX -B or -A volume on the subsystem. If the specified FXmto
target file does not exist, FCU automatically creates the target file during the
FXmto operation. If the specified FXmto target file already exists, FCU
requests confirmation to overwrite the target file (unless the -nc option is
specified).

The FCU software performs the FXmto data transfer operations. FCU version
01-01-40 or later is required for VSE source datasets. FCU supports both
fixed-length and variable-length record formats and provides the following
options for FXmto data transfer (see section entitled “
code conversion, padding, delimiter, empty file, record description word, and
VSE record. The types of FXmto operations are:

• FXmto with fixed-length record format

• FXmto with variable-length record format)

System Requirements”):

Table 2-3 specifies the record format requirements for each type of FXmto
operation. A fixed-length source dataset can only be transferred to a fixed­length target file, with or without delimiters. Padding cannot be added to a
fixed-length source file. A variable-length source dataset can be transferred to
a variable-length or fixed-length target file, depending on the padding option,
and delimiters can also be added if desired.

Table 2-3 FXmto Record Format Requirements

Record Format Requirements

FCU Direction Padding Delimiters Source Dataset Target File See Figure:

FXmto N/A No Fixed-length Fixed-length 3.2
FXmto N/A Yes Fixed-length Fixed-length 3.3
FXmto No No Variable-length Variable-length 3.4
FXmto Yes No Variable-length Fixed-length 3.5
FXmto No Yes Variable-length Variable-length 3.6
FXmto Yes Yes Variable-length Fixed-length 3.7

About Cross-OS File Exchange Operations 2-17

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

FXmto with Fixed-Length Record Format

Each fixed-length record in a z/OS dataset includes only the fixed-length data
entity. The record length defined for a fixed-length dataset equals the actual
length of each data entity. The padding option cannot be used for FXmto with
fixed-length records.

No padding, no delimiters.

Figure 2-9 shows an FXmto operation for a
fixed-length source dataset. Padding cannot be added to fixed-length records.
FCU extracts and transfers the data entities to the open-system target file. The
length of each data entity in the target file equals the record length defined for
the source dataset.

Source Dataset Open-System Target File

Record 1: Data entity 1 Data entity 1
Record 2: Data entity 2

Record 3: Data entity 3 Data entity 3

Record length Record length

→

Data entity 2

Figure 2-9 FXmto with Fixed-Length Records: No Padding, No

Delimiters

With delimiters. Figure 2-10 shows an FXmto operation with delimiters (D)
for a fixed-length source dataset. 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 resulting length of each data entity in a UNIX target file
equals the original record length plus one byte for the delimiter. The resulting
length of each data entity in a Windows 2000/2003/Windows NT target file
equals the original record length plus two bytes for the delimiter.

Source Dataset Open-System Target File

Record 1: Data entity 1 Data entity 1 D
Record 2: Data entity 2

Record 3: Data entity 3 Data entity 3 D

Record length Record length + 1 or 2 bytes

→

Data entity 2 D

Figure 2-10 FXmto with Fixed-Length Records: Delimiters

2-18 About Cross-OS File Exchange Operations

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

FXmto with Variable-Length Record Format

Each variable-length record in a z/OS dataset includes a four-byte RL field and
the variable-length data entity. The record length defined for a variable-length
dataset equals the maximum allowable record length.

Note: If you want to be able to transfer the data back to the original z/OS
dataset later, you must use FXmto without padding and with delimiters.

No padding, no delimiters.

Figure 2-11 shows an FXmto operation without
padding or delimiters for a variable-length source dataset. FCU extracts and
transfers only the data entities to the target file. The RL fields are not
transferred. The resulting length of each data entity in the target file is equal
to or less than the maximum record length minus four bytes (for the RL field).

Note: If you plan to transfer the data back to the original dataset later using
FXotm, use FXmto with delimiters.

Source Dataset Open-System Target File

RL Record 1: Data entity 1 Data entity 1
RL Record 2: Data entity 2

RL Record 3: Data entity 3 Data entity 3

Record length Record length – 4 bytes

→

Data entity 2

Figure 2-11 FXmto with Variable-Length Records: No Padding, No

Delimiters

With padding. Figure 2-12 shows an FXmto operation with padding. FXmto
with padding requires a variable-length source file and produces a fixed-length
target file. FCU adds padding to the source records as needed so that the
length of each record equals the maximum record length. FCU then extracts
and transfers the data entities with padding to the open-system target file.
The RL fields are not transferred. The resulting length of each data entity in
the target file equals the maximum record length minus four bytes (for the RL
field).

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

About Cross-OS File Exchange Operations 2-19

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

Source Dataset Open-System Target File

RL Record 1: Data entity 1 Data entity 1 padding

Record length (max) Record length (max) – 4 bytes

RL Record 2: Data entity 2

RL Record 3: Data entity 3 Data entity 3 padding

→

Data entity 2

Figure 2-12 FXmto with Variable-Length Records: Padding

With delimiters. Figure 2-13 shows an FXmto operation with delimiters (D)
for a variable-length source dataset. 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 one byte for the delimiter. The resulting length of each data entity in a
Windows 2000/2003/ Windows NT target file equals the original data entity
length plus two bytes for the delimiter.

Note: If 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.

Source Dataset Open-System Target File

RL Record 1: Data entity 1 Data entity 1 D
RL Record 2: Data entity 2

Record length Data entity length + 1 or 2 bytes

→

Data entity 2 D

RL Record 3: Data entity 3 Data entity 3 D

Figure 2-13 FXmto with Variable-Length Records: Delimiters

With padding and delimiters. Figure 2-14 shows an FXmto operation with
padding and delimiters (D). 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.

2-20 About Cross-OS File Exchange Operations

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

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

About Cross-OS File Exchange Operations 2-21

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

Source Dataset Open-System Target File

RL Record 1: Data entity 1 Data entity 1 D padding

Record length Record length (max) − 3 or 2 bytes

RL Record 2: Data entity 2

RL Record 3: Data entity 3 Data entity 3 D padding

→

Data entity 2 D

Figure 2-14 FXmto with Variable-Length Records: Padding and

Delimiters

The resulting length of each data entity in a UNIX target file equals the
maximum record length minus three bytes (minus four for the RL, plus one for
the delimiter). The resulting length of each data entity in a Windows
2000/2003/Windows NT target file equals the maximum record length minus
two bytes (minus four for the RL, plus two for the delimiter).

2-22 About Cross-OS File Exchange Operations

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

FXmto with Multiple Volume Datasets

Multiple Volume Dataset is supported only for FXmto, when the version is 01­XX-50/ YY(XX=01 or 02, 03 or 04) or higher.

Note: Multiple Volume Dataset is not supported for FXotm. A multiple volume
definition file (multidef.dat) is necessary in current directory. FAL will check
Dataset Serial number, Data set serial number and Last volume containing
data in this data set in Data set indicators on VTOC DSCB1.

Note: Multiple volume Dataset is supported for FileExchangeotm when the
version is 01-XX-60/YY (XX=02 or 03 or 04) or higher.

Note: For Windows 2000/2003, you should not write a signature on shared
volumes, which are 3390-3X, 3390-9X, 3390-LX, or 3380-KX, 3380-3X
(X=A,B,C). If you try to write a signature on the shared volumes, FX can not
guarantee that the volumes will be shared with other OS’s (AIX, Solaris, HP­UX, Tru64, Linux, etc). When you use a shared volume with Windows
2000/2003 only, FX will perform correctly if you write a signature on the
shared volumes. (A “write error” message will appear in the System log, but
this will not have a negative influence on FX operation.)

Table 2-4 Illustrates this.

Note: FAL/FCU supports two kinds of mainframes, MVS
Multiple Volume Dataset, FAL/FCU is only supported on MVS

TM

and VSE. For

TM

.

Table 2-4 Multiple Volume Dataset/Serial Numbers

VTOC DSCB1/

Action

OTM OK(OK) NG(OK) NG(OK) NG(OK)
MTO for single

volume(*1)

1 1 Except 1 Except 1

Last Volume Containing Data in this Data Set, in Data Set Indicators

On Off On Off

OK(OK) NG(OK) NG(OK) NG(OK)

Data Set Serial Number

About Cross-OS File Exchange Operations 2-23

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

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
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.

FCU File Transfer

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

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

Figure:

FXotm with Fixed-Length Record Format

No padding, no delimiters. The figure below shows an FXotm operation for
a fixed-length source file without padding or delimiters. The target dataset
must have fixed-length record format with record length set to the actual
length of each data entity. If the data entity length does not exactly match the
record length defined for the target dataset, FCU aborts the operation and
reports an error.

Open-S ystem Source File Target Dataset

Data entity 1 Record 1: Data entity 1
Data entity 2

Data entity 3 Record 3: Data entity 3

Figure 2-15 FXotm with Fixed-Length Records: No Padding, No

Record length Record length

→

Record 2: Data entity 2

Delimiters

With padding. The figure below shows an FXotm operation for a fixed-length
source file with padding from a previous FXmto transfer. The original FXmto
dataset cannot be used as the FXotm target dataset. FCU transfers the data
entities including padding to the target dataset. The length of each data entity
in the source file equals the maximum record length minus four bytes (for the
RL field). The target dataset must have fixed-length record format with record
length set to the maximum record length minus four bytes. If the length of
any record (data entity plus padding) in the source file does not exactly match
the record length defined for the target dataset, FCU aborts the operation and
reports an error.

Open-Sys tem Source File Target Dataset

Record length (max) − 4 bytes Record length (max) − 4 bytes

Data entity 1 padding Record 1: Data entity 1 (with padding)
Data entity 2

Data entity 3 padding Record 3: Data entity 3 (with padding)

→

Record 2: Data entity 2

Figure 2-16 FXotm with Fixed-Length Records: Padding

Note: FCU does not extract padding from FXotm source files.

About Cross-OS File Exchange Operations 2-25

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

With delimiters. The figure below shows an FXotm operation for a fixed­length source file with delimiters from a previous FXmto transfer. FCU extracts
the data entities from the source file by record length and transfers them to
the target dataset. The delimiters are not transferred. The target dataset must
have fixed-length record format with record length set to the actual length of
each data entity (without delimiter). If the length of any source data entity
does not exactly match the record length defined for the target dataset, FCU
aborts the operation and reports an error. If the delimiter is not found right
after the data entity, FCU aborts the operation reports an error.

Open-Sys tem Source File Target Dataset

Data entity 1 D Record 1: Data entity 1
Data entity 2 D

Data entity 3 D Record 3: Data entity 3

Record length + 1 or 2 bytes Record length

→

Record 2: Data entity 2

Figure 2-17 FXotm with Fixed-Length Records: Delimiters

Note: FCU does not add delimiters to FXotm source files. If the FXotm source
file contains delimiters but you specify No for the delimiter option, the
delimiters will be regarded as part of the data entities and will be transferred
to the target dataset.

With padding and delimiters. The figure below shows an FXotm operation
for a fixed-length source file with padding and delimiters from a previous
FXmto transfer. FCU removes the delimiters but not the padding and transfers
the data entities with padding to the target dataset. The original variable­length dataset cannot be used as the target dataset for this transfer. The
target dataset must have fixed-length record format with record length set to
the maximum record length minus four bytes. If the length of any source data
entity does not match the record length defined for the target dataset, FCU
aborts the operation and reports an error.

Open-Sys tem Source File Target Dataset

Record length (max) − 3 or 2 bytes Record length (max) − 4 bytes

Data entity 1 D Record 1: Data entity 1 with padding
Data entity 2 D

→

Record 2: Data entity 2

Data entity 3 D Record 3: Data entity 3 with padding

2-26 About Cross-OS File Exchange Operations

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

Figure 2-18 FXotm with Fixed-Length Records: Padding and Delimiters

Note: FCU does not extract padding from FXotm source files. If the FXotm
source file contains delimiters but you specify No for the delimiter option, the
delimiters will be regarded as part of the data entities and will be transferred
to the target dataset.

About Cross-OS File Exchange Operations 2-27

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

FXotm with Variable-Length Record Format

FXotm operations can be performed on variable-length source files only if
delimiters have already been added to the source file (e.g., from a previous
FXmto operation). If a variable-length source file without delimiters is
processed, FCU will use the maximum record length to construct the target
data entities, thereby corrupting the data and rendering the dataset unusable.
FCU extracts but does not add delimiters to FXotm source files.

With delimiters. The figure below shows an FXotm operation for a variable­length source file with delimiters. FCU extracts and transfers the data entities
to the target dataset, and automatically adds the four-byte RL field. The
delimiters are not transferred. The target dataset must have variable-length
record format.

Open-Sys tem Source File Target Dataset

Data entity 1 D RL Record 1: Data entity 1
Data entity 2 D

Record length – 2 or 1 byte Record length

→

RL Record 2: Data entity 2

Data entity 3 D RL Record 3: Data entity 3

Data entity + 1 or 2 bytes

Figure 2-19 FXotm with Variable-Length Records: Delimiters

If the length of any data entity in a UNIX source file is greater than the
maximum record length minus one byte (CR or LF delimiter), FCU aborts the
operation and reports an error. If the length of any data entity in a Windows
2000/2003/Windows NT source file is greater than the maximum record length
minus two bytes (CR+LF delimiter), FCU aborts the operation and reports an
error.

2-28 About Cross-OS File Exchange Operations

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

With padding and delimiters. The figure below shows an FXotm operation
with padding for a variable-length source file with delimiters. FCU version 01­01-41 or later is required for FXotm with padding added to variable-length
source files. FCU adds padding, extracts and transfers the data entities with
padding to the target dataset, and automatically adds the four-byte RL field.
The delimiters are not transferred. The target dataset must have fixed-length
record format with record length defined as needed.

Open-Sys tem Source File Target Dataset

Data entity 1 D Record 1: Data entity 1 + padding
Data entity 2 D

Data entity 3 D Record 3: Data entity 3 + padding

Record length + 1 or 2 bytes Record length

→

Record 2: Data entity 2

Figure 2-20 FXotm with Variable-Length Records: Padding and

Delimiters

If the length of any data entity in a UNIX source file is greater than the
specified record length plus one byte (CR or LF delimiter), FCU aborts the
operation and reports an error. If the length of any data entity in a Windows
2000/2003/Windows NT source file is greater than the specified record length
plus two bytes (CR+LF delimiter), FCU aborts the operation and reports an
error.

FXoto Operations

FXoto operations transfer data from source files on one open-system platform
to target files on another open-system platform. Each FXoto file transfer
consists of two separate FX operations: first an FXotm operation transfers the
data in the source file to an intermediate dataset, and then an FXmto
operation transfers the data from the intermediate dataset to the target file.
For any users with the all-open TagmaStore USP or NSC subsystem (no
attached z/OS host), the intermediate datasets are allocated on OPEN-x FMT
volumes. The FMT utility enables you to format OPEN-x LUs (standard or
custom size) as FXoto volumes. The ALC utility enables you to allocate
intermediate datasets on the OPEN-x FMT volumes. For users with the
multiplatform TagmaStore USP or NSC subsystem, the intermediate datasets
can be allocated on OPEN-x FMT volumes or on FX -A volumes, as desired.
When you perform FXoto operations which access OPEN-x FMT volumes, the
FXoto volume definition file must be available for use by FCU.

About Cross-OS File Exchange Operations 2-29

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

Note: FCU version 01-01-41 or later is required for FXoto operations using
ALC-generated datasets on OPEN-x FMT volumes.

The FCU file transfer options (code conversion, padding, delimiters, etc.) can
be used on the FXotm and FXmto sub-operations as needed.

• Code conversion is not available for FXoto transfers.

• Padding can be used but will render the target file incompatible with the

source file due to the change in record format from variable-length to fixed­length. If you use padding for the FXotm operation, the target file can be
transferred back to the same intermediate dataset but not back to the same
source file. If you use padding for the FXmto operation, the target file cannot
be transferred back to the same intermediate dataset or back to the same
source file.

• Delimiters can be used to enable bidirectional data transfers. When using

delimiters, watch out for files which contain the same character(s) as the
delimiter (CR and/or LF) but used for purposes other than delimiting data
entities. If you specify the delimiter option for FXotm, FCU will interpret all
occurrences of the specified delimiter character(s) as delimiters, which can
create a dataset with corrupt records or generate an error condition.

• The empty file option can be used to enable empty files to be processed. For

example, if a source file specified in your FXoto FCU parameter definition file
becomes empty, you can add the empty file option to the FXotm/mto
operations on that file to enable FCU to process the FCU parameter definition
file without errors.

• The RDW option is not normally used for FXoto operations. If you use the

RDW option (FXmto operation only), you will not be able to transfer the data
back to the same intermediate dataset.

• The VSE record option does not apply to FXoto operations which access ALC-

generated intermediate datasets on OPEN-x FMT volumes. The only time you
would use the VSE option is when transferring a file between open-system
platforms via a VSE dataset on a -A FX volume. In this case, you must use
the VSE record option for both transfers (FXotm/mto).

Host Access and I/O Contention

The user must manage access to the FXmto and FXotm volumes to prevent
illegal I/O access contention between the z/OS and open-system hosts. These
FX volumes cannot be accessed concurrently by the z/OS and open-system
hosts, and must be varied offline from the z/OS host during FX operations. The
FX volumes should not contain any regularly accessed data and should be
dedicated to data exchange operations to avoid accidental overwriting of data.

2-30 About Cross-OS File Exchange Operations

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

Note: For 01-02-48 and earlier, do not access the FX volume from FAL/FCU
when AIX is accessing it. For 01-02-50 and earlier, do not access the FX
volume from FAL/FCU when Windows 2000/2003/Windows NT is accessing it.

Note: Please note the following restrictions for the listed operating systems:

• For UNIX operating systems, if the version is 01-02-48 and later, FXotm can

run several different datasets simultaneously.

• For Windows 2000/2003/Windows NT operating systems, if the version is 01-

02-50 and later, FXotm can run several different datasets simultaneously.

• For AIX operating systems, since volumes are reserved during accessing,

FXotm cannot run several different datasets simultaneously.

Please refer to the Reference Manual for RAID 200/300/400/450 FAL & FCU,
revision 20.0, for more detail.

The FX volumes can only be accessed by open-system hosts using the
FAL/FCU software. The z/OS hosts have normal read/write access to the -B
and -A volumes, read-only access to the -C volumes, and no access at all to
the OPEN-x FMT volumes. The open-system hosts have read/write access to
the -C, -A, and OPEN-x FMT volumes and read-only access to the -B volumes.
The open-system hosts must use FAL/FCU to access all FX volumes.

WARNING: Concurrent access to the FX volumes by the z/OS and open­system hosts is not supported. The user is responsible for managing access to
FX volumes to avoid I/O contention between the z/OS and open-system hosts.
Since FCU accesses only the VTOC area of the FX -B volumes, catalog or
security control functions cannot be used to provide access control for the
3390-3B volumes.

The z/OS host can issue a reserve command to reserve a volume for
exclusive use. The z/OS reserve command prevents access by all other hosts,
including all other z/OS hosts and all open-system hosts. The open-system
host can also reserve a volume to exclude I/Os issued by other systems. The
open-system reserve command prevents access by all other open-system
hosts, but z/OS hosts still have normal access to FXmto and FXotm volumes
reserved by open-system hosts. These reserve commands affect FX
operations as follows:

• Reserved by z/OS host. When an FX volume is reserved by the z/OS host,

FX operations cannot be performed on that volume, because the FAL/FCU
access from the open-system host will terminate unsuccessfully. Open­system access other than read or write I/Os can be executed successfully.

Note: Open-system access to an z/OS-reserved volume may complete
successfully if the open-system retries the operation after the reserve is
released. However, since the time interval before a retry varies depending
on the open-system platform and the z/OS application that issued the
reserve, the success of retry operations on reserved volumes cannot be
guaranteed.

About Cross-OS File Exchange Operations 2-31

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

• Reserved by open-system host. When an FX volume is reserved by the

open-system host, FX operations can be performed only from the host that
reserved the volume. FX operations from any other open-system host will
terminate unsuccessfully. Open-system reserve does not affect z/OS access
to the FX volume.

• Unreserved. When an FX volume is not reserved by any z/OS or open-

system host, FX operations can be performed from any open-system host
using FAL/FCU. All z/OS hosts and all open-system hosts have access to
unreserved volumes.

The user should implement exclusive access control and job coordination at
the system level for the FX volumes. The user should also take the following
steps to avoid I/O contention problems for the FX volumes:

• Open-system access. When the open-system host needs to access an FX

volume, vary the volume and its channel path offline from all z/OS hosts.

• z/OS access. When the z/OS host needs to access an FX volume, stop all

open-system access to the corresponding LU. For AIX, vary off the volume
group(s). For Windows 2000/2003/Windows NT, use unaccess. Do not use
any open-system program which accesses unmounted LUs (e.g., AIX SMIT,
HP-UX SAM, and NT Disk Administrator).

AIX Shared Open Function

To share FileExchange volumes on multiple AIX operating systems:

• For FX versions 01-xx-59 and earlier, when one AIX OS opens a FileExchange

volume, the other AIX OS cannot open the FileExchange volume. This is
because the AIX OS reserves the FileExchange volume when it opens the it.

• For FX 01-xx-60 and later, it is possible to share an FileExchange volume

across multiple AIX operating systems by specifying the environment
variable:

FAL_NO_RESERVE.

The following table (Table 2-6) shows the relationship between shared
volumes and FX versions.

Table 2-6 Shared Volume and FX Version

Object Version Description

01-xx-59 and earlier Cannot open a shared volume from multiple AIX OSs. FAL for AIX

(32/64 bit)

01-xx-60 and later

Can open a shared volume from multiple AIX OSs by specifying the
environment variable.

To define environment variables:

2-32 About Cross-OS File Exchange Operations

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

• By specifying the environment variable (FAL_NO_RESERVE), you can select

shared open or exclusive open.
the environment variable (FAL_NO_RESERVE) and open mode.

Table 2-7 Environment Variable (FAL_NO_RESERVE) and Open Mode

FAL_NO_RESERVE Open Mode

No definition of environment variable Exclusive Open (Original mode)
ON Shared Open
OFF Exclusive Open
Other Exclusive Open

Table 2-7 shows the relationship between

About Cross-OS File Exchange Operations 2-33

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

AIX Reserve Function

AIX Reserved Retry Function

For FX versions 01-XX-61 and earlier, an AIXsystem error will occur when you
use FX to send data to a reserved volume on another system. For FX versions
01-XX-62 and later, you can retry sending data to the reserved volume by
specifying the wait time and retry count for the environment variable of the
other system. FX can send data again when the reserved volume is released
by the other system. The following table shows the AIX reserve functions.

Table 2-8 AIX Reserve Retry Function

Environment Variable or Function Description

FAL_RETRY To set retry function: specify the environment variable.
FAL_RETRY_COUNT

FAL_RETRY_WAIT_TIME

FAL_RETRY_TARGET

Retry function

Out put retry log function

To set retry count: specify the environment variable. (FX
attempts top send data while in reserve status.)

To set the interval: specify the environment variable. (FX
attempts to send data while in reserved status.)

To set system error codes: Specify the environment
variable. (System error codes asreretry triggers.)

The retry function in invoked when AIX commands
trigger a system error (open,close,read,write,seek,flush).

FX outputs a retry log (FAL_Error log) when it executes
retry.

Environment Variables and Functions

• Retry Function: You can set the retry function by specifying the

environment variable (FAL_RETRY).

– If there is no definition of environment variable, the Retry function

is disabled.

– If the environment variable is defined as ON, the Retry function is

enabled.

– If the environment variable is defined as OFF, the Retry function is

disabled.

– If the environment variable is defined as other, the Retry function is

disabled.

• Retry Counts Function: You can set the number of retry function instances

by specifying the environment variable (FAL_RETRY_COUNT). FX attempts to
send data during reserved status.

– The default count number is 10, where no definition of the environment

variable is given.

– The range of the FAL_RETRY_COUNT variable is 1-600.

2-34 About Cross-OS File Exchange Operations

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

– If other values outside the range are given, the default value applies.

• Retry Wait Time Function:You can set the wait time interval by specifying

the environment variable(FAL_RETRY_WAIT_TIME). FX attempts to send data
during reserved status.

– The default is 1 second, where no definition of the environment variable

is given.

– The range of the FAL_RETRY_WAIT_TIME variable is 1-60 seconds.
– If other values outside the range are given, the default value applies.

• Retry target function: You can set system error codes, which are retry

triggers, by specifying the environment variable (FAL_RETRY_TARGET).

– You can set up to 5 system error codes separated by commas. If you set

six or more system error codes, FX will ignore all after the fifth.

– If no environment variable definition is given, an error code 16(EBUSY)

will appear.

– You can set up to 5 system error codes, separated by commas.
– If other values outside the range are given, the 16(EBUSY) error code

applies.

– For setting error codes outside default values, please contact your Hitachi

Data Systems technical representative.

About Cross-OS File Exchange Operations 2-35

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

Bidirectional Data Transfer

FX supports bidirectional data transfer for both fixed-length and variable­length z/OS datasets. Bidirectional data transfer involves transferring data
from z/OS datasets to open-system files and then back to the original z/OS
datasets again. The requirements for bidirectional data transfer are:

• For all FXmto operations, do not specify the record description word (RDW)

option. If the RDW option is specified for an FXmto data transfer, the
subsequent FXotm target dataset will not be compatible with the original
dataset.

• For FXmto with fixed-length datasets, do not specify the delimiter option,

since the data entities are extracted by length. If you add delimiters for the
FXmto transfer, the subsequent FXotm target dataset will not be compatible
with the original dataset.

• For FXmto with variable-length datasets, you must add delimiters but not

padding. If delimiters are not added or if padding is added for the FXmto
transfer, the subsequent FXotm target dataset will not be compatible with the
original dataset.

• For FXotm operations do not specify the delimiter option if the source file

contains the same character(s) as the delimiter (CR and/or LF) but used for
purposes other than delimiting data entities. If you specify the delimiter
option for FXotm, FCU will interpret all occurrences of the specified delimiter
character(s) as delimiters, which can create a dataset with corrupt records or
generate an error condition.

2-36 About Cross-OS File Exchange Operations

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

About Cross-OS File Exchange Operations 2-37

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

3

Preparing for Cross-OS File Exchange

Operations

This chapter describes the system requirements and volume configuration
necessary to run and operate FX. It also provides instructions on how to install
FX.

 System Requirements
 Installing and Configuring the FX Volumes
 Installing the FAL/FCU Software

Preparing for Cross-OS File Exchange Operations 3-1

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

System Requirements

The user should examine existing data exchange needs carefully, especially
the desired number of FX volumes to be installed and configured, prior to
TagmaStore USP or NSC system configuration. This is due to the possible need
to reconfigure and reformat entire array groups, depending on the microcode
level of the subsystem.

The system requirements for FX are:

• FAL/FCU CD for the applicable open-system platform(s). This revision of the

FX User’s Guide covers versions 01-02-4x through 01-03-59. For earlier
versions, please refer to the previous revision of this document.

– FAL/FCU currently supports files larger than 2 GB.

• Multiplatform or all-open TagmaStore USP or NSC subsystem:

– FXmto: the TagmaStore USP or NSC must be configured with -B and/or -A

FX volumes.

– FXotm: the TagmaStore USP or NSC must be configured with -C and/or -A

FX volumes.

– FXoto: the user can format OPEN-x LUs as FXoto volumes or use -C FX

volumes. Version 01-01-41 or later of FCU is required to format FXoto
volumes.

• Remote Console PC and LUN Manager Software. LUN Manager enables the

user to configure FC ports and create custom-size LUs. If remote LUN
Manager is not installed, please contact the Hitachi Data Systems
representative about LUN Manager configuration services. For information on
LUN Manager, refer to the Hitachi TagmaStore USP and NSC LUN Manager
User’s Guide (MK-94RD203).

• z/OS operating systems: MVS, VSE (supported by FCU 01-01-40 and later),

VOS3

– Both 3990 and 2105 control unit (CU) emulations are supported.

3-2 Preparing for Cross-OS File Exchange Operations

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

• Open-system platforms and operating system (OS) version level(s):

– 32bitFAL:

HP-UX 10.2 and 11.0, 11i, 11iV2
Solaris 2.5, 2.6, 7, 8, 9 (version 2.5 = Ver. 01-XX-47 or earlier)

®

IBM

AIX® 5.3, 5.2ML02, 5.1ML02, 4.1.x, 4.2.x, 4.3.xML02, 5 (version

4.1 = Ver. 01-XX-47 or earlier)
Windows® 2000 SP4(x86)/2003 SP1(x86)/NT® 4.0 SP6(x86)(IA64)(x64)
(Workstation or Server

®

HP

Tru64 UNIX V5.1a

Red Hat Linux 7.2: AS2.1, AS3.0/IA64

– 64bitFAL:

HP-UX 11.0, 11i, 11iV2
Solaris 8, 9
IBM AIX 5.3, 5.2, 5.1, 4.3.3
Red Hat Linux AS3.0/Update3(x86) or Update4/IA64
Red Hat SuSE SLES9(x86)(IA64)(AMD64/EM64T)

Note: When installing/uninstalling Rapid Xchange (for 32/64bit), follow the
procedure presented in this Chapter. For 64bit installation, the FX program
must be version 01-03-59 or later.

TM

)

– 64bitFCU:

HP-UX11.0,11i,11iV2
Solaris 7,8,9
IBM AIX

4.3, 5L

Red Hat Linux AS3.0/IA64

Note: The Motif 1.2 (or later) Windows system software is required for
the FCU GUI for UNIX. If Motif is not installed, see Appendix B (Using
FCU without the GUI).

– Superuser (root) login access to the open-system server/workstation is

required.

Note: For FAL/FCU versions earlier than 01-02-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 FAL/FCU
versions 01-02-50 or later, Multiple Volume Dataset is supported only for
FXmto.

Note: For 64bitFAL, set the HBA which supports 64bit to the server. IBM AIX
systems support 64bitFAL. For further information on IBM AIX systems, please
contact the IBM Support Center.

Preparing for Cross-OS File Exchange Operations 3-3

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

64-bit Version FCU

FX supports the 64-bit version FCU. The application method is the same as for
the 32-bit version FCU.

Note: The 64-bit version FCU does not support a GUI interface.
FX version 01-04-61/20 supports Solaris, HP-UX, AIX 4.3, and AIX 5L

operating systems.
FX version 01-04-62/20 supports Red Hat Linux AS3.0/IA64 operating system.

VSE Requirements and Restrictions

FX supports the VSE operating system. The following sections describe the
supported VSE versions that correspond to the TagmaStore subsystem and
associated FX version.

Note: There is no guarantee that FX will correctly access your data without
meeting these requirements.

Table 3-1 Support and OS Conditions

OS version RAID subsystem FX

VSE2.5 and upper TagmaStore USP or NSC After 01-03-59

3-4 Preparing for Cross-OS File Exchange Operations

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

When you use MTO and OTM for the dataset allocated by VSE2.3, you must
specify RF (Record Format), RL(Record Length) and BL(Block Length) by using
the correct VSE parameters.

When you use MTO and OTM for the dataset allocated by VSE2.5, FX can
transfer data without a VSE parameter.

Table 3-2 Support Matrix for VSE OS, VSE Parameter and Record Format

Record Format OS andFX Version

VSE2.3 and previous
(FX: 01-xx-58 and

previous)

(FX: 01-03-59)

VSE Parameter

Yes
No

Yes
No

F FB V VB

   
× × × ×

 
 

Note 1



Note 3



Note 2



Note 4



VSE2.5 and higher

Key:
o: Transfer is available

×: Transfer is not available
F: Fixed non-block length
FB: Fixed block length
V: Variable non-block length
VB: Variable block length

Note 1: It is possible to transfer data between correct dataset
attribute(5≦RL≦BL-4). The data transfer is valid only if the VSE parameters
are as shown:

RL≦32756
BL≦32760
BL=RL+4

For the following dataset attributes, the data transfer is invalid if user does

not specify the VSE parameter value as shown above.

RL＞32756
BL＞32760

For the following dataset attributes, the data transfer is invalid if user does
not specify the VSE parameter value between RL and BL values shown in #1
and #2.

RL≦32756
BL≦32760
RL=BL

Preparing for Cross-OS File Exchange Operations 3-5

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

s#1: RL(Input value for VSE parameter) = RL(value on VTOC) + 4 ≦32756
#2: BL(Input value for VSE parameter) = BL(value on VTOC) + 8 ≦32760
Note 2: It is possible to transfer data between the correct dataset attributes

(5≦RL≦BL-4). The data transfer is invalid if the VSE parameter is not the
following value:

RL(Input value for VSE parameter) = RL(value on VTOC) + 4 ≦32756
BL(Input value for VSE parameter) = BL(value on VTOC) + 8 ≦32760

Note 3: It is possible to transfer data between the correct dataset attributes
(BL＝RL+4≦32760). The data transfer is invalid if the RL and BL values on VTOC

do not match to the following condition:

BL＝RL+4≦32760

When the RL and BL values on VTOC are such that RL > 32756 and BL >
32760, FX manages the data as RL=32756 and BL=32760.

When the RL and BL values on VTOC are such that RL≦32756, BL≦32760 and
RL = BL, FX manage the data as shown below:

RL(FX internal value) = RL(value on VTOC) + 4 ≦32756
BL(FX internal value) = BL(value on VTOC) + 8 ≦32760

Note 4: It is possible to transfer data between the correct dataset attributes
(BL＝RL+4≦32760). The data transfer is invalid if RL and BL values on VTOC
do not match to the following condition:

BL＝RL+4≦32760

When the RL and BL values on VTOC are such that RL＝BL≦32752, FX
manages the data as shown below:

RL(FX internal value) = RL(value on VTOC) + 4
BL(FX internal value) = BL(value on VTOC) + 8

Note: If you Create a user program by using the dataset attribute exchange
rule, you need to use the following functions:

datasetGetFileInformation()
datasetGetFileInformationEx()

Compiler Requirements

The compiler requirements are shown below for each OS. This information is
the result of test and evaluation by Hitachi LTD and is guaranteed for the
specified development environment for use with FX. If the development
environment differs from that specified here, your results may differ.

3-6 Preparing for Cross-OS File Exchange Operations

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

Table 3-3 Platforms and Associated Operating Systems

Operating System/Platform Compiler

Red Hat Linux 7.2 (Kernel version 2.4.7-10)
and Red Hat Linux

Solaris

Windows NT 4.0 service Pack 6a Visual C++® 6.0 SP4
HP-UX 10.20

AIX4.3 C® for AIX 4.4
AIX5L C® for AIX, Version 5.0
HP® Tru64 Digital UNIX Compiler Driver 3.11

AS2.1 and AS3.0

Maximum Data Size

Table 3-4 describes the maximum possible data sizes for FAL/FCU version 01-02­48 or later.

Table 3-4 Maximum Data Size

gcc(Ver.2.96-98)
glibc(Ver.2.2.4-13)

Work Shop Compilers 4.2.1

HP® 92453-01 A.10.32.03 HP® C Compiler

DEC C V5.6-075 on Digital UNIX V4.0 (Rev. 878)

Emulation Type No LUSE LUSE Multiple Volume Dataset

OPEN-3 About 21 GB About 42.8 GB
OPEN-8 About 6.5 GB About 42.8 GB
OPEN-9 About 6.5 GB About 42.8 GB
OPEN-E About 12.9 GB About 42.8 GB
OPEN-L About 32.3 GB About 42.8 GB
OPEN-V About 42.8 GB About 42.8 GB
3390-3X About 2.6 GB

3390-9X About 8.3 GB HP-UX(*1)/Solaris /NT Tru64 :249GB

3390-LX About 27.1 GB HP-UX(*1)/Solaris /NT/ Tru64 :813GB

OS limits:
HP-UX, Solaris, NT, Tru64
AIX: 64GB

AIX: 64GB(The limit of OS)

AIX: 64GB(The limit of OS)

®

: 78GB

Note: The data capacity that can be stored within the intermediate file is
smaller than its physical capacity, and varies depending upon the block length
to be used.

Additional Notes:

Preparing for Cross-OS File Exchange Operations 3-7

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

• 3390-9A: Can be used for both FileExchangemto and FileExchangeotm. The

same access as for 3390-9 is allowed from Mainframe hosts. Read and write
are possible from Open system hosts.

• 3390-9B: Can be used only for FileExchangemto. The same access as for

3390-9 is allowed from Mainframe hosts. Read only is allowed from Open
system hosts.

• 3390-9C: Can be used only for FileExchangeotm. The same access as for

3390-9 is allowed but read only from Mainframe hosts. Read and write are
possible from Open system hosts.

• 3390-LA: Can be used for both FileExchangemto and FileExchangeotm. The

same access as for 3390-L is allowed from Mainframe hosts. Read and write
are possible from Open system hosts.

• 3390-LB: Can be used only for FileExchangemto. The same access as for

3390-L is allowed from Mainframe hosts. Read only is allowed from Open
system hosts.

• 3390-LC: Can be used only for FileExchangeotm. The same access as for

3390-L is allowed but read only from Mainframe hosts. Read and write are
possible from Open system hosts.

3-8 Preparing for Cross-OS File Exchange Operations

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

Interoperability with HDLM

When FX is used with HDLM, the FAL/FCU version must be 01-03-56 or later.
The appropriate support platform versions are shown in
to the Hitachi Freedom Storage Hitachi Dynamic Link Manager (HDLM) User's
Guide for IBM AIX Systems
(MP-92DLM111), the Hitachi Freedom Storage Hitachi Dynamic Link Manager

(HDLM) User's Guide for HP-UX
Storage Hitachi Dynamic Link Manager (HDLM) User's Guide for Sun Solaris
Systems (MP-92DLM114), and the Hitachi Freedom Storage Hitachi Dynamic
Link Manager (HDLM) User's Guide for Windows NT and Windows 2000 (MP-

92DLM129) for further details on each platform.

Table 3-5 HDLM Platforms and HDLM Versions

Platform HDLM Version

Windows 2000/NT/2003 04-01, 05-00-/B
AIX 05-00-/A, 05-01
HP-UX 04-00-/A
Solaris 04-01, 05-00

Table 3-5. Please refer

Systems (MP-92DLM112), the Hitachi Freedom

Preparing for Cross-OS File Exchange Operations 3-9

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

Installing and Configuring the FX Volumes

The FX volumes are installed and configured during TagmaStore USP and NSC
installation and configuration. The FX volumes should be dedicated to data
exchange operations to avoid accidental overwriting or deletion of important
data. The FXmto volumes (-B and -A) contain z/OS data to be transferred to
open-system LUs. The FXotm volumes (-C and -A) contain open-system data
to be transferred to z/OS volumes. The FXoto volumes contain the
intermediate datasets for file transfers between open-system platforms. FX
does not support concurrent access to FX volumes by the z/OS and open­system hosts.

To install and configure the FX volumes:

1. Determine exactly how many FXmto, FXotm, and FXoto volumes you will
need for your multiplatform data exchange operations. The -A volumes can
be used for FXmto, FXotm, and FXoto. The -B volumes are restricted to
FXmto. The -C volumes are restricted to FXotm. The OPEN-x FMT volumes
are restricted to FXoto. Make sure that the Hitachi Data Systems
representative installs the desired number of each type of FX volume during
TagmaStore USP and NSC subsystem installation and configuration.

Note: If you need to change the number of FX volumes, please contact
your Hitachi Data Systems account team. Reconfiguring the FX volumes
after TagmaStore USP and NSC subsystem installation may require
reformatting entire array groups, depending on the microcode level of the
subsystem.

2. Complete TagmaStore USP and NSC installation and device configuration as
specified in the TagmaStore USP and NSC configuration guide for the
applicable open-system platform (e.g., the TagmaStore USP and NSC HP-UX
Configuration Guide, MK-94RD235).

– Device recognition and device files. For all open-system platforms,

you must verify device recognition and device file creation for all FX
volumes.

– File system/volume group. Do not create a file system or volume

group on any FX volume, including the OPEN-x devices which will be
formatted for FXoto operations. FX volumes can only be accessed as raw
devices by the open-system host using FAL/FCU (no mount operation).

3-10 Preparing for Cross-OS File Exchange Operations

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

– Defining RAW Devices. Those volumes which are to be used as

intermediate volumes and to be shared between open systems must be
defined as OPEN-3/8/9/K/E/L/M/V emulation type for RAID200/300,
and must be defined as “raw” devices from each host server. From the
open systems, there are no means to distinguish OPEN-3/8/9/K/E/L/M/V
for open system dedicated volumes from these FX volumes. Please make
sure not to confuse the usage on those volumes in the host systems.

• The operations below which create file systems on the intermediate
volumes must not be executed. Otherwise, information on the volume
may be destroyed and the volumes will become unusable as FX
volumes.

– Solaris: “newfs” command
– HP-UX: “pvcreate” command
– IBM AIX: creating a volume group
– Windows: formatting and creating a file system
– Digital UNIX/HP
– SequeNT DYNIX/ptx
– NCR

®

SVR4: creating a volume group

®

Tru64 UNIX: “newfs” command

®

: creating a file system

– Linux: “raw” command

Note for Microsoft

®

: Cluster Server: When installing FX devices in a
Microsoft Cluster Server (MSCS) environment, you must write
signatures on the FX volumes before configuring MSCS.

– The MSCS server cannot connect volumes which do not have

signatures.

– The volume on which a signature is written cannot be accessed from

another server.

– The volume on which a signature is written cannot be shared.
– Only the mainframe and the server which wrote the signature can

access the volume which has the signature.

– I/O time-out and I/O queue depth. Make sure to set the I/O time-out

and I/O queue depth values for the FX volumes as specified in the
applicable TagmaStore USP and NSC configuration guide.

– Partition size. Make sure to specify the correct partition size for the FX

volumes as specified in the applicable TagmaStore USP and NSC
configuration guide. If the partition size for -A or -B volumes is smaller
than the mainframe volume size, the open-system host may not be able
to access data to the end of the extent of these volumes.

Preparing for Cross-OS File Exchange Operations 3-11

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

For Solaris, use the following partition sizes for the FX volumes, and use 2
(two) for the number of alternate cylinders (

Table 3-6):

Table 3-6 Partition Sizes for TagmaStore USP and NSC Subsystems

LVI Cylinder # for Data Cylinder Extent

3390-3A 0 - 3345
3390-3B 0 - 3339
3390-3C 0 - 3345
3390-9A 0 - 10035
3390-9B 0 - 10017
3390-9C 0 - 10035
3390-LA 0 - 32763
3390-LB 0 - 32760
3390-LC 0 - 32763
OPEN-3 0 - 3335
OPEN-8 0 - 9963
OPEN-9 0 - 10013
OPEN-E 0 - 19756
OPEN-L 0 - 49433
3390-3A 0 - 3345
3390-3B 0 - 3339
3390-3C 0 - 3345
OPEN-3 0 - 3335
OPEN-8 0 - 9963
OPEN-9 0 - 10013
OPEN-E 0 - 19756
OPEN-L 0 - 19012
OPEN-V See Note 1.
3390-3A 0 - 3345

3-12 Preparing for Cross-OS File Exchange Operations

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

Note 1: For further information on Solaris cylinder partition sizes, please refer
to the Hitachi TagmaStore USP and NSC LUN Expansion and Virtual LVI/LUN

User's Guide (MK-94RD205), and the Hitachi TagmaStore USP and NSC Sun
Solaris Configuration Guide(MK-94RD236)

• Volume labels. An FX volume with a volume label cannot be shared between

open-system platforms which use volume labels.
allowable configurations for sharing FX volumes between open-system
platforms for the TagmaStore USP and NSC subsystems.
allowable configurations for sharing FX volumes between open-system
platforms for the TagmaStore USP and NSC subsystems. HP-UX and IBM AIX
do not use volume labels, so FX volumes can always be shared with these
platforms. Labels are optional for DIGITAL UNIX/Tru64 and Windows
2000/2003/Windows NT, so FX volumes can be shared with these platforms
only if they have no label. Solaris always writes volume labels, so FX volumes
can never be shared between these two platforms, but can be shared with
the other platforms (HP, IBM, DIGITAL UNIX/Tru64, NT) as long as they do
not have labels.

Note: Solaris may display the following warning messages when formatting
and labeling an FX volume. This is normal, and the user can ignore these
messages.

Warning: error writing VTOC
Warning: no backup labels
Write label failed

Table 3-6 shows the

Table 3-7 shows the

3. For UNIX hosts, make sure to set up the desired access privileges for each FX
volume (e.g., using groups and/or chmod command). Please refer to the OS
user documentation for information on access permission rights. For Windows
2000/2003/Windows NT, Administrator access is required to access the FX
volumes.

4. On the z/OS host, make sure to initialize and write the VTOC for each FXmto
and FXotm volume to enable the z/OS host to access the volumes. The
ICKDSF media maintenance utility can be used to perform these tasks.

5. After FAL/FCU software installation, make sure to format each FXoto volume
using the FX Formatter (FMT) utility on the UNIX/ Windows NT host. This
enables the FXoto intermediate datasets to be allocated.

Preparing for Cross-OS File Exchange Operations 3-13

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

Table 3-7 Sharing FX Volumes between Open-System Platforms

No label

Label
write
option

Label
auto­write

IBM AIX HP-UX

SequeNT

®

DYNIX

Windows

2000/200

3/

Windows

NT

®

HP

®

UNIX ®

True64

Solaris NCR

®

Linux

SVR4

IBM AIX OK OK OK OK OK OK OK OK
HP-UX OK OK OK OK OK OK OK OK
SequeNT

OK OK OK OK OK OK OK OK

DYNIX
Linux OK OK OK OK OK OK OK OK
HPTrue64

OK OK OK CHK CHK

/ UNIX

Windows

OK OK OK OK CHK CHK CHK OK
2000/200
3/
Windows
NT

Solaris OK OK OK OK OK OK

NCR

OK OK OK OK OK NO NO OK
SVR4

CHK = sharing allowed only if volume has no label.

3-14 Preparing for Cross-OS File Exchange Operations

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

Installing the FAL/FCU Software

The FAL/FCU software must be installed on the UNIX/NT server(s) attached to
the subsystem. FAL/FCU software installation for the UNIX-based platforms is
different from FAL/FCU installation on Windows 2000/2003/Windows NT. The
following sections provide instructions for installing FAL/FCU version 01-01­36/38 or later. For instructions on installing versions 01-01-24 and earlier,
please refer to previous revisions of this document.

Installing FAL/FCU on UNIX-Based Platforms

32-Bit FAL/FCU Software

To install the 32-bit FAL/FCU software on a UNIX-based platform:

1. If FAL/FCU version 01-01-36 or later is already installed (by cpio command),
you do not need to uninstall it. A new installation will overwrite the previous
version.
If FAL/FCU version 01-01-24 or earlier is already installed (by setup
program), you must uninstall this older version as follows before installing
version 01-01-36 or later:

a) Log in with the same user ID that was used to install the old FAL/FCU

software.

b) If FAL/FCU was installed from FD using the setup program, see

Uninstallation to remove FAL/FCU.

c) If FAL/FCU was installed from DAT, or if you can’t find your FAL/FCU

installation FD, move to the directory fcu/fal.o/dataset.h and remove
FAL/FCU by entering:
# rm fcu fal.o dataset.h $HOME/FcuMf

If you cannot find the directory, you can use the following procedure:

# find / -name “fcu” -print
# find / -name “fal.o” -print
# find / -name “dataset.h” -print
# find / -name “FcuMf” -print

2. Log in to the system as root.

3. Insert the FAL/FCU installation media (e.g., CD-ROM) into the drive.

Note: Verify that the device file for the CD-ROM drive exists. For Solaris,
do not use volcheck if the CD-ROM device file is not available for auto-

mount.

Preparing for Cross-OS File Exchange Operations 3-15

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

4. Make sure the following six directories exist on the open-system host. If not,
create the directories using the mkdir command (e.g., # mkdir
/usr/lib/X11/app-defaults).
/usr /usr/lib
/usr/bin /usr/lib/X11
/usr/include /usr/lib/X11/app-defaults

5. Move to the root directory.

6. For UNIX-based systems, copy the FAL/FCU software from the installation
CD-ROM as follows:

# cpio -iBmuv < CD_device_file_name/d

Note: Use the full device file name: wildcards will not work.

3-16 Preparing for Cross-OS File Exchange Operations

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

7. For Solaris you must set a path to the resource file for each FAL/FCU user:
a) For C shell, add the following line to the end of the .cshrc file in the home

directory. If .cshrc does not exist, create it and enter the following line:

setenv XFILESEARCHPATH /usr/lib/X11/app­defaults/%N:$XFILESEARCHPATH

export XFILESEARCHPATH

Note: Add these two lines to the file “.profile” in your home directory,
when it is not in the common desktop environment. If “.profile” does
not exist, create it.

b) For non-C shell, add the following two lines to the end of the .dtprofile

file in the home directory. If .dtprofile does not exist, create it and enter
the following lines:

XFILESEARCHPATH=/usr/lib/X11/app­defaults/%N:$XFILESEARCHPATH
export XFILESEARCHPATH

c) You must log out and log back in to implement these changes.

8. For Tru64

UNIX you must uncompress the FAL/FCU program:

# uncompress /usr/bin/fcu.Z

9. Remove the CD-ROM from the drive.

10. Log out, and then log in again.

Note: When the FX Code Converter is installed, the libuoc.* file is replaced
with the FX Code Converter library (the extension varies according to OS).
Before installing FX Code Converter, save libuoc.* with an alias.

Preparing for Cross-OS File Exchange Operations 3-17

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

64-Bit FAL/FCU Software

To install the 64bitFAL/FCU software on a UNIX-based platform:

1. Log-in as "root".

2. Set CD-ROM, in which the 64bitFAL/FCU is stored, to the drive.

3. Mount it.

4. Check to see if the following directories currently exist. If they do not, create
them as follows:

a. All Platforms: /usr, /usr/lib
b. Solaris: /usr/lib/sparcv9
c. HP-UX: /usr/lib/pa20_64

5. Move to the root directory

6. Copy 64bitFAL from CD-ROM

7. A file or directory can be viewed using the correct file name given at
mounting. To view a directory, use one of the following procedures according
to platform:

d. Install 64bitFAL after confirming a directory name and a file name by

using the ls command.

– HP-UX (11.0):

#cpio -iBmuv <(MountPoint)/PROGRAM/FAL64/HP_UX/HP_UX.CPI

– Solaris (Solaris 7,8, 9):

#cpio -iBmuv (MountPoint)/PROGRAM/FAL64/SOLARIS/SOLARIS.CPI

– AIX (AIX 4.3.3 ):

#cpio -iBmuv <(MountPoint)/PROGRAM/FAL64/AIX/AIX4/AIX.CPI

– Red Hat Linux AS3.0/IA64:

#cpio -iBmuv <(MountPoint)/PROGRAM/FAL64/LINUX/LINUX.CPI

8. Remove the CD-ROM from the drive.

9. Log-out once and log-in again

3-18 Preparing for Cross-OS File Exchange Operations

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

Installing FAL/FCU on Windows

To install the FAL/FCU software on a Windows 2000/2003/Windows NT-based
platform:

1. If FAL/FCU is already installed, uninstall it before installing the new version.
a) To uninstall FAL/FCU version 01-01-25 or later, use the Windows

Add/Remove Programs utility.

b) To uninstall FAL/FCU versions 01-01-24 and earlier, delete the folder that

contains the FAL/FCU software components (fcu.exe, fal.obj, and
dataset.h).

2. Insert the FAL/FCU installation CD-ROM into the drive, and run setup.exe.

Note: For Windows 2000/2003/Windows NT, if the Installed Directory has a
directory name using a “space” character, enter the following: <license key>
fal.dll falmt.dll

Preparing for Cross-OS File Exchange Operations 3-19

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

Uninstalling the FAL/FCU Software on UNIX-Based Platforms

If you need to uninstall FAL/FCU version 01-01-36 or later:

1. Log in to the system as root.
Remove the FAL/FCU for 32bit files using the rm command as follows, or

string the commands:

# rm /usr/bin/fcu
# rm /usr/bin/fcunw
# rm /usr/include/dataset.h
# rm /usr/lib/libfal.
# rm /usr/lib/libuoc.
# rm /usr/lib/X11/app-defaults/FcuMf
# rm /usr/bin/mfformat
# rm /usr/bin/allocds

2. Remove the FAL/FCU for 64bit files using the rm command as follows, or

string the commands:

# rm /usr/bin/fcunw
# rm /usr/include/dataset.h
# rm /usr/lib/libfal64.*
# rm /usr/lib/libuoc64.*
# rm /usr/bin/mfformat64
# rm /usr/bin/allocds64

When uninstalling 32bit FAL/FCU version 01-01-41 and later, remove the
following file:

# rm /usr/bin/listvol

When the 64bit FAL/FCU Ver.01-01-41/00 or later is used, remove the
following files:

#rm /usr/bin/ppkeyset64
#rm /usr/bin/autoppkeyset64

When uninstalling 32bit FAL/FCU version 01-01-45 and later, remove the
following files:

# rm /usr/lib/libfal.ver

#rm /usr/bin/ppkeyset
#rm /usr/bin/autoppkeyset

Uninstalling FAL/FCU on Windows

To uninstall the FAL/FCU software on a Windows 2000/2003/Windows NT­based platform:

3. Depending on your version of FAL/FCU, do one of the following:

3-20 Preparing for Cross-OS File Exchange Operations

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

• To uninstall FAL/FCU version 01-01-25 or later, use the Windows
Add/Remove Programs utility.

• To uninstall FAL/FCU versions 01-01-24 and earlier, delete the folder that
contains the FAL/FCU software components (fcu.exe, fal.obj, and
dataset.h).

Note: For Windows 2000/2003/Windows NT, if the Installed Directory has a
directory name using a “space” character, enter the following: <license key>
fal.dll falmt.dll

Entering the FX License Key Code

The license key for FX is entered by command on the server system after FX
has been installed. A license key is required for each server and for each
different server type. Each key is associated with a specific TagmaStore USP or
NSC subsystem (defined by serial number). The procedures for entering
license keys follow.

For UNIX platforms, input the following command from the command line:

• HP-UX:

– 32bit: ppkeyset <License key> /usr/bin/fcunw /usr/bin/fcu

/usr/lib/libfal.sl

– 64bit: ppkeyset64 <License key> /usr/bin/fcunw64

/usr/lib/pa20_64/libfal64.sl

• Solaris:

– 32bit: ppkeyset <License key> /usr/bin/fcunw /usr/bin/fcu

/usr/lib/libfal.so.1

– 64bit: ppkeyset64 <License key> /usr/bin/fcunw64

/usr/lib/sparcv9//libfal64.so.1

• AIX:

– 32bit: ppkeyset <License key> /usr/bin/fcunw /usr/bin/fcu /usr/lib/libfal.a
– 64bit: ppkeyset64 <License key> /usr/bin/fcunw64 /usr/lib/libfal64.a

• Digital UNIX/HP Tru64 UNIX /DYNIX/ptx:

– 32bit: ppkeyset <License key> /usr/bin/fcunw /usr/bin/fcu

/usr/lib/libfal.so

• Linux:

– 32bit: ppkeyset <License key> /usr/bin/fcunw /usr/lib/libfal.so.1
– 64bit: ppkeyset64 <License key> /usr/bin/fcunw64 /usr/lib/libfal64.so.1

Preparing for Cross-OS File Exchange Operations 3-21

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

Creating FXoto Volumes Using the FMT Utility

After the FAL/FCU software has been installed on the open-system host(s),
you can format the FXoto volumes using the FX Formatter (FMT) utility. This
enables you to allocate FXoto intermediate datasets. The FMT utility for UNIX
is a UNIX command executed from the UNIX command line. The FMT utility for
Windows 2000/2003/Windows NT is a GUI.

Note: FCU version 01-01-42 or later is required for the FMT utility.
The FX FMT utility defines the size of the OPEN-x volume in cylinders. The

maximum number of cylinders allowed by FMT is shown in

Table 3-8 FMT Utility Values

Table 3-8.

Emulation Type 01-XX-47 or

OPEN-3 3331 3331 5818 3331

OPEN-8 5818 5818 5818 9959

OPEN-9 5818 5818 5818 10009

OPEN-E

OPEN-L

OPEN-V

earlier

(

Note 2

not
supported

not
supported

not
supported

01-XX-YY/ZZ not

LUSE

)

(

Note 2

)

5818 5818 19752

5818 5818 49429

not supported not supported 65534

01-XX-YY/ZZ

LUSE

(

Note 2

)

01-XX-YY/2x

not LUSE

(

Note 2

)

(min 3338*n-7,

65534)
(min 9996*n-7,

65534)
(min 10016*n-7,

65534)
(min 19759*n-7,

65534)
(min 49439*n-7,

65534)
(min(Vc*n*128/

96-7,65534)
(see Note 4)

01-XX-YY/2x

Note 2

LUSE (

n=number of

volumes
(

Note 3

)

)

Note 2: XX = 1 or 2; YY,x = number; ZZ<2x
Note 3: For Solaris, the data cylinder must be less than or equal to 32767.

When using a LUSE volume, the geometry parameter is different, so the
number of cylinders should be calculated as follows:

Cylinder (specified to FAL formatting) <= (A*B*C) / (15*96) – 5

A: Head (Geometry parameter)
B: Block/Track (Geometry parameter)

C: cylinder (Geometry parameter)
Note 4: Vc = OPEN-V cylinder value (MAX.:49160 cylinders using FAL)
The FMT utility can be used on standard-size OPEN-x volumes and on Virtual

LVI/LUN (VIR) volumes.

3-22 Preparing for Cross-OS File Exchange Operations

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

Note: The VIR OPEN-x devices can also be called custom volume size (CVS)
devices (e.g., OPEN-3-CVS). When formatting a VIR OPEN-x LU, use the
number of cylinders defined for VIR minus seven (e.g., use 993 cylinders for a
VIR device defined with 1000 cylinders). The cylinder size is: one cylinder =
15 tracks, one track = 96 sub-blocks, one sub-block = 512 bytes.

Table 3-9
shows the relation between block length and write available capacity per track.
The actual data capacity per cylinder = (write available capacity per track) ×
(15 tracks).

Table 3-9 Relation between Block Length and Write Available Capacity

per Track

Block Length by

Allocater = (A)

(Bytes)

23477 - 32760 (A) × 1 1589 - 1684 (A) × 22 565 - 596 (A) × 44
15477 - 23476 (A) × 2 1493 - 1588 (A) × 23 533 - 564 (A) × 45
11477 - 15476 (A) × 3 1397 - 1492 (A) × 24 501 - 532 (A) × 46
9077 - 11476 (A) × 4 1333 - 1396 (A) × 25 469 - 500 (A) × 47
7477 - 9076 (A) × 5 1269 - 1332 (A) × 26 437 - 468 (A) × 48
6357 - 7476 (A) × 6 1205 - 1268 (A) × 27 405 - 436 (A) × 49
5493 - 6356 (A) × 7 1141 - 1204 (A) × 28 373 - 404 (A) × 50
4821 - 5492 (A) × 8 1077 - 1140 (A) × 29 341 - 372 (A) × 51
4277 - 4820 (A) × 9 1045 - 1076 (A) × 30 309 -340 (A) × 52
3861 – 4276 (A) × 10 981 - 1044 (A) × 31 277 - 308 (A) × 53
3477 –3860 (A) × 11 949 - 980 (A) × 32 245 - 276 (A) × 54
3189 – 3476 (A) × 1 2 917 - 948 (A) × 33 213 - 244 (A) × 55
2933 – 3188 (A) × 1 3 853 - 916 (A) × 34 181 - 212 (A) × 56
2677 – 2932 (A) × 1 4 821 - 852 (A) × 35 149 - 180 (A) × 57
2485 – 2676 (A) × 1 5 789 - 820 (A) × 36 117 - 148 (A) × 58
2325 – 2484 (A) × 1 6 757 - 788 (A) × 37 85 - 116 (A) × 59
2165 – 2324 (A) × 1 7 725 - 756 (A) × 38 53 - 84 (A) × 60
2005 – 2164 (A) × 1 8 693 - 724 (A) × 39 21 - 52 (A) × 61
1877 – 2004 (A) × 1 9 661 - 692 (A) × 40 1 - 20 (A) × 62
1781 – 1876 (A) × 2 0 629 - 660 (A) × 41 — —
1685 – 1780 (A) × 2 1 597 - 628 (A) × 42 — —

Write Available
Data per Track

(Bytes)

Block Length by

Allocater = (A)

(Bytes)

Write Available

Data Per Track

(Bytes)

Block Length by

Allocater = (A)

(Bytes)

Write Available
Data Per Track

(Bytes)

Note: The write available data per track includes the four-byte RL information
and four-byte BL information for each record. When transferring variable­length records, make sure to take this extra required space into account.

WARNING: The FX FMT utility erases all data on the OPEN-x LU being
formatted. If necessary, back up the data on the OPEN-x LUs prior to FMT
formatting.

Preparing for Cross-OS File Exchange Operations 3-23

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

To format an OPEN-x volume using the FX FMT utility for UNIX:

1. Log in to the system as root.

2. Enter the following command at the UNIX command line prompt:
# mfformat -d devname -v VOLSER [-p primary_cylinders]

-d devname: Specify the raw device name (e.g., /dev/rdsk/c0t1d2 for HP­UX) of the OPEN-x volume being formatted. This parameter is required.
Make sure to use the same raw device name for this volume in the FXoto
volume definition file.

-v VOLSER: Specify the VSN of the volume being formatted (A-Z, 0-9, @,
#, \). Use only uppercase letters, and do not use any spaces or symbols
other than @, #, and \. This parameter is required. Make sure to use the
same volser for this volume in the FXoto volume definition file.

-p primary_cylinders: Specify the number of primary cylinders (from
decimal 2 through 5818). This parameter is required for custom-size
volumes but is optional for standard-size volumes. If this parameter is
omitted, the default value of max cylinders is used, specifically: OPEN-3 =
0-3331, OPEN-8 = 0-9959, OPEN-9 = 0-10009, OPEN-E = 0-19752, OPEN­L = 0-49429. When LUSE is set, the default value is the maximum value in
a single volume.

3. If the FMT format operation could not be started due to an error condition,
the Format check error message is displayed. If the FMT format operation
did not complete successfully, an error message is displayed. Remove the
error condition, and retry the operation (see section C.2 in Appendix C for
further information on errors in UNIX).

To format an OPEN-x volume using the FX FMT utility for Windows
2000/2003/
Windows NT:

1. Log in to the system as administrator.

2. Double-click on the Format icon to open the Format panel (see

3. On the Format panel, enter the six-character volume serial number for the
OPEN-x volume being formatted in the VOLSER field. Make sure to use the
same volser for this volume in the FXoto volume definition file.

4. Specify the physical drive number (device number) for the OPEN-x volume
being formatted in the Physical drive No field. Make sure to use the same
physical drive number for this volume in the FXoto volume definition file.

5. Specify the number of cylinders for the OPEN-x volume in the Cylinder Size
field. The Min. button enters 2 (two) cylinders, and the Max. button enters
5818 cylinders. If the OPEN-x volume is standard size (e.g., OPEN-3), use the
maximum size of 5818 cylinders. If the OPEN-x volume is custom size (e.g.,
OPEN-3*n VIR device), use the following value: (# of cylinders defined for
VIR) − 7. For example, if the VIR OPEN-x volume is defined with 1000
cylinders, enter 993 in the Cylinder Size field.

Note: The maximum size for the Allocater is 4369 cylinders.

3-24 Preparing for Cross-OS File Exchange Operations

Figure 3-1).

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

6. When the VSN, physical drive number, and cylinder size are correct, select
the Start button. When the Format confirmation appears (see

Figure 3-2),
select OK to perform the requested FMT format operation, or select Cancel
to cancel your request.

7. When the format operation completes successfully, the Format complete
message is displayed (see
been used, an error message is displayed to notify you (see

Figure 3-3). If the specified volser has already

Figure 3-4). If
the format operation could not be started due to an error condition, the
Format check error message is displayed. If the format operation did not
complete successfully, one of the following error messages is displayed (see
Figure 3-5) (n = system error code):

Open error! (n) Open process error on specified volume.
Seek error! (n) Seek process error on specified volume.
Read error! (n) Read process error on specified volume.
Write error! (n) Write process error on specified volume.
Close error! (n) Close proce ss error on specified volume.

8. When you are finished formatting OPEN-x volumes for use as FXoto volumes,
select Close to close the Format panel and exit the FMT utility.

Important Note:

When the message “Format check error” is indicated, the formatting
operation has not started and the original condition has been kept. When
another message is indicated, the formatting process has already started. The
data on the volume has already been initialized. Remove the error condition
and format the volume again.

If you execute over the maximum number of cylinders on Windows 2003, the
message “Format failed … Format check error” appears after about a minute.
It should be clear when formatting has completed.

Preparing for Cross-OS File Exchange Operations 3-25

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

Figure 3-1 FMT Utility for Windows 2000/2003/Windows NT

Figure 3-2 FMT Format Warning and Confirmation

Figure 3-3 FMT Format Complete Message

3-26 Preparing for Cross-OS File Exchange Operations

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

Figure 3-4 FMT VOLS ER Used Message

Figure 3-5 FMT Erro r Message

Preparing for Cross-OS File Exchange Operations 3-27

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

Creating the FX Volume Definition File(s)

The FX volume definition file contains the volume association parameters for
the FX volumes on the TagmaStore USP and NSC. This file must be created
before you can use FCU or FAL to access data on these volumes. The volume
association parameters define the FX volume by associating the volume serial
number (VSN or volser) with the open-system device file for the same logical
volume.
Figure 3-6 through Figure 3-13 show the structure and contents of the FX
volume definition file for each supported platform.

Note: Regarding the specification of the same VSN in volume definition file for
01-XX-48 or later: The same VSN can be defined in the Volume definition file
using VSN identification, and both volumes can be used by FXotm and FXmto.
The definitions should be defined with 35 digits, using the alphabet (A-Z, @,
#, and \) or numeral (0-9) characters.

The -A, -B, and -C FX volumes and the OPEN-x-FXoto volumes can be defined
in the same FX volume definition file. For example:

XXX/XXXXXX MVS01 3390-3A
YYY/YYYYYY VSN01 OPEN-3
end

Table 3-10 describes the FX volume association parameters.

Table 3-10 FX Volume Association Parameters

Number Name Function Enter

1

2

3

4

5

Device file name Specifies raw device (partition)

VOLSER Specifies logical volume defined

LVI or LU type
(emulation)

Carriage return Marks end of parameter set. Make sure to press the Return key (Enter key

End of file Marks end of par ameter file. end

name defined for open-system.

for z/OS.
Specifies LVI or LU type of FX

volume.

Character-type device file name (e.g., c1t0d2 for
HP-UX, c1t0d2s1 for Solaris.

Six-character volser (e.g., FX45). A volser can
use the following characters: A-Z, 0-9, @, #, \

Correct LVI/LU for FX volume: 3390-3A, -3B, ­3C, 3380-KA, -KB, -KC or OPEN-x-FXoto. Make
sure to define all OPEN-x FMT volumes in a
separate file.

for Windows 2000/2003/Window s NT) at the end
of each line.

To create the FX volume definition file:

1. Open a new empty text file. For UNIX-based systems, use the UNIX vi editor
(e.g., vi datasetmount.dat). For Windows 2000/2003/Windows NT

systems,
use any text editor, and make sure to use plain text. The file name must be
datasetmount.dat (all lowercase), and the file must be located in the
current working directory when you start FCU. If you are creating two FX
volume definition files, use datasetmount1.dat and datasetmount2.dat,
and remove the “1” or “2” from the desired file before starting FCU.

3-28 Preparing for Cross-OS File Exchange Operations

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

2. Add the volume association parameters for the FX volumes to the file.

– Put at least one space between each parameter, and press the Return

key at the end of each line to separate the parameter sets. All three
parameters (device name, volser, LVI type) are case-sensitive. If you add
comments to the file, make sure that each comment line starts with #.
Make sure to enter end on the last line of the file.

3. When you are done adding the volume association parameters for each FX
volume to the volume definition file, save your changes and exit the text
editor.

/dev/rdsk/cx1tx2dx3sx4 AAAAAA 3390-3A MFN MVS1
/dev/rdsk/cy1ty2dy3sy4 AAAAAA 3390-3A MFN VOS3
/dev/rdsk/cz1tz2dz3sz4 cccccc 3380-KB
/dev/rdsk/cw1tw2dw3sw4 dddddd 3380-KA
(1) (2) (3) (4) (5) (6)
end
(7)

Figure 3-6 FX Volume Definition File for Solaris (mto/otm Shown)

Note: x = controller number, y = SCSI target ID (TID), z = LUN, w = partition
(or slice)

/dev/rdsk/cx1tx2dx3 AAAAAA 3390-3A MFN MVS
/dev/rdsk/cy1ty2dy3 AAAAAA 3390-3A MFN VOS3
/dev/rdsk/cz1tz2dz3 cccccc 3380-KB
/dev/rdsk/cw1tw2dw3 dddddd 3380-KA
(1) (2) (3) (4) (5) (6)
end
(7)

Figure 3-7 FX Volume Definition File for HP-UX (oto Shown)

Note: In cxtydz, x = controller number, y = SCSI TID, z = LUN. In OPEN-x, x
= 3, 8, K,E, L, M, 9 or V.

/dev/rhdiskn1 AAAAAA 3390-3A MFN MVS
/dev/rhdiskn2 AAAAAA 3390-3A MFN VOS3
/dev/rhdiskn3 cccccc 3380-KB
/dev/rhdiskn4 dddddd 3380-KA
(1) (2) (3) (4) (5) (6)
end
(7)

Figure 3-8 FX Volume Definition File for IBM AIX (mto/otm Shown)

Note: n = disk ID number (note that the first, second, and third drives are 0,
1, 2).

Preparing for Cross-OS File Exchange Operations 3-29

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

/dev/rrzX1Y1Z1 AAAAAA 3390-3A MFN MVS
/dev/rrzX3Y3Z3 cccccc 3380-KB MFN VOS3
/dev/rrzX4Y4Z4 dddddd 3380-KA
(1) (2) (3) (4) (5) (6)
end
(5)

Figure 3-9 FX Volume Definition File for DIGITAL Tru64 UNIX (oto

Shown)

Note: X = b through h = LUN1 through LUN7 (no letter is used for LUN0); Y =
fibre bus number × 8 + SCSI TID; Z = partition = a through h. For example,
rrzc18a = SCSI TID 2, LUN2 (partition a) on fibre bus 2.

Note: OPEN-x = 3, 8, K, E, L, M , 9 or V

\\.\PHYSICALDRIVE0 AAAAAA 3390-3A MFN MVS
\\.\PHYSICALDRIVE1 AAAAAA 3390-3A MFN VOS3
\\.\PHYSICALDRIVE2 cccccc 3380-KB
\\.\PHYSICALDRIVE3 dddddd 3380-KA
(1) (2) (3) (4) (5) (6)
end
(7)

Figure 3-10 FX Volume Definition File for Windows NT /2000/2003

Systems (mto/otm Shown)

Note: n = disk ID number.

/dev/rdsk/cx1tx2dx3s0 AAAAAA 3390-3B MFN MVS
/dev/rdsk/cy1ty2dy3s0 AAAAAA 3390-3A MFN VOS3
/dev/rdsk/cz1tz2dz3s0 cccccc 3380-KB
/dev/rdsk/cw1tw2dw3s0 dddddd 3380-KA
(1) (2) (3) (4) (5) (6)
end
(7)

Figure 3-11 FX Volume Definition File for NCR® UNIX

/dev/rdsk/sdx1 AAAAAA 3390-3A MFN MVS
/dev/rdsk/sdx2 AAAAAA 3390-3A MFN VOS3
/dev/rdsk/sdx3 cccccc 3380-KB
/dev/rdsk/sdx4 dddddd 3380-KA
(1) (2) (3) (4) (5) (6)
end
(7)

Figure 3-12 FX Volume Definition File for DYNIX/ptx

/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

3-30 Preparing for Cross-OS File Exchange Operations

®

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

(7)

Figure 3-13 FX Volume Definition File for Linux

Preparing for Cross-OS File Exchange Operations 3-31

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

Verifying Mainframe Dataset Requirements

FAL and FCU have specific requirements for the FX source and target datasets.
Table 3-11 specifies the requirements for FX datasets. The FCU GUI (see
sections
Transfer Operations – Windows) allows the user to display the dataset
attributes and verify the dataset requirements. FCU for UNIX (version 01-01­41 and later) also provides the listvol function to display z/OS 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 FX operation is performed. FCU does not support automatic
expansion of the extent during FXotm operations. The FX ALC utility allocates
intermediate datasets in accordance with the requirements specified below.

Table 3-11 z/OS Dataset Requirements

Performing File Transfer Operations - UNIX and Performing File

Item Requirement(s)

Dataset organization
(DO) type

Dataset name

Record format (RF)

Block length (BL)

Record length (RL)

SAM (sequential-access method). FAL/FCU does not support any other DO types (e.g.,
DAM, VSAM, PAM). If a non-SAM dataset is specified, FAL/FCU will return an error.

Multiple-volume datasets are not supported. FAL/FCU can only process the portion within one logical volume.

No spaces. If FAL/FCU encounters a space, it will accept the characters before the space
as the dataset name and continue processing.

Fixed-length or variable-length record format. FAL/FCU does not su pport undefined­length or spanned record formats. If an illegal RF is detected, FAL/FCU will return an error.

No key. If a record with a key is accessed, FAL/FCU 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.

Any length within the extent supported by the OS. If an illegal BL is detected, FAL/FCU 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.

Any length within the extent supported by the OS. If an illegal RL is detected, FAL/FCU will
return an error.

Note: FAL/FCU cannot process a variable-length dataset which includes a record with no
data entity (RL = 4).

For FXotm, the record length of the target dataset must be preconfigured to match the record length of the data
entities in the source file.

For VSE source and target datasets, the FCU VSE record optio n must be used to specify the RL.

Track format Standard record 0 (R0). FAL/FCU cannot proces s tracks with nonstandard R0.
VTOC

Database file Direct access is not supported; must be conve rted to a SAM file.

3-32 Preparing for Cross-OS File Exchange Operations

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

For MVS: standard or index VTOC. For an index VTOC, F AL/FCU ignores the index and
accesses the entire VTOC sequentially.

For VSE: The user must specify the RF, BL, and RL using the FCU VSE record option.
Note: The FAL functions cannot be used on VSE datasets.

Allocating FXoto Intermediate Datasets

When you perform FXoto operations using OPEN-x FMT volumes, you must
allocate the intermediate datasets before starting the file transfer operations.
The FX Allocater (ALC) utility can only be used on OPEN-x volumes which have
already been formatted using the FX FMT utility.

Note: FCU version 01-01-41 or later is required for the ALC utility.
Note: For versions 01-01-41: The ALC utility for UNIX is a UNIX command

executed from the UNIX command line. The ALC utility for Windows
2000/2003/Windows NT systems is a GUI. The ALC utility for UNIX can only be
used on volumes formatted with the FMT utility for UNIX. The ALC utility for
Windows 2000/2003/Windows NT systems can only be used on volumes
formatted with the FMT utility for Windows 2000/2003/Windows NT systems.

CAUTION: The capacity of the intermediate dataset varies depending on block
length so remember to calculate the required size for the intermediate dataset.
When you transfer variable-length records, make sure to take the four-byte RL
information and four-byte BL information for each record into account.

UNIX - To allocate an FXoto intermediate dataset using the ALC utility:

1. Log in to the system as root.

2. Enter the following command at the UNIX command line prompt:
# allocds -d devname [-n datasetname] [-f recform] [-r reclen] [-b blocklen]
[-c cylinders]

Note: Enter only one value for each parameter. You can only allocate one
dataset at a time.

-d devname: Specify the raw device name of the OPEN-x volume on which
the dataset is being allocated. This parameter is required and must be
specified.

-n datasetname: Specify the name of the dataset being allocated
(maximum forty-four characters: A-Z, 0-9, @, #, ., \). Use uppercase
letters only, and do not use any spaces or symbols other than @, #, ., and
\. This parameter is required. If not specified, ALC will return the residual
capacity (free space) on the specified volume in number of cylinders.

-r recform: Specify the record format of the dataset being allocated: F
(fixed-length and de-blocking), FB (fixed and blocking), V (variable and
de-blocking), or VB (variable and blocking). This parameter is required. If
not specified, the default value of F is used.

-r reclen: Specify the record length (decimal) of the dataset being
allocated: 1 to 32760. This parameter is required. If not specified, the
default value of 4096 is used.

Preparing for Cross-OS File Exchange Operations 3-33

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

-b blocklen: Specify the block length (decimal) of the dataset being
allocated.
When record format = F, block length = record length.
When record format = FB, block length = record length × N (N =
integer).
When record format = V/VB, block length = record length + 4 or
more.

This parameter is required. If not specified, the following default values are
used:
When record format = F/FB, default block length = record length.
When record format = V/VB, default block length = record length + 4.

-c cylinders: Specify the size of the dataset being allocated in number of
cylinders (decimal). This parameter is required. If not specified, the default
value of 100 is used.

3. If the ALC allocate operation could not be started due to an error condition,
the Allocate check error message is displayed. If the ALC allocate operation
did not complete successfully, an error message is displayed. Remove the
error condition, and retry the operation. See section C.2 in Appendix C for
further information on errors in UNIX.

Windows 2000/2003/Windows NT systems: To allocate an intermediate FXoto
dataset using the ALC utility:

1. Log in to the system as administrator.

2. Double-click on the Allocate icon to start the ALC utility and open the
Allocation panel.

3. The ALC utility automatically displays the first OPEN-x FMT volume (in
alphanumeric order) in the VOLSER field. If this is not the desired volume,
select the desired volume from the drop-down list of volsers. If ALC could not
find any OPEN-x FMT volumes, ALC displays the FX format disk not found
message.

4. Enter the name of the dataset being allocated in the Dataset field (maximum
forty-four characters: A-Z, 0-9, @, #, ., \). Do not use any spaces or symbols
other than @, #, ., and \.

5. Enter or select the size of the new dataset (number of cylinders, number of
tracks) in the Cylinder and Track fields. The file size will be (# of cyl) + (#
of tracks). The Max. button enters the maximum size for the new dataset in
the Cylinder and Track fields based on the available capacity. The
Available Capacity box displays the free space on the specified volume, so
that you can select the appropriate size for the new dataset.

6. Enter or select the record format in the Record format field: F, FB, V, or VB.

7. Enter or select the record length in the Record length field:

– When record format = F, record length = block length.
– When record format = FB, record length = block length ÷ N (N = integer).

3-34 Preparing for Cross-OS File Exchange Operations

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

– When record format = V or VB, 5 ≤ record length ≤ (block length − 4).

8. Enter or select the block length in the Block length field. If block length =
record length, select the Copy button to copy the record length into the
Block length field.

– When record format = F or FB, 1 ≤ block length ≤ 32760.
– When record format = V or VB, 9 ≤ block length ≤ 32760.

9. When all parameters for the new dataset are correct, select the Start button.

10. When the allocate operation completes successfully, the Allocation
complete message is displayed. If the allocate operation could not be started
due to an error condition, the Allocate check error message is displayed. If
the allocate operation did not complete successfully, one of the following
error messages is displayed:

Open error! (n) Open process error on the FXoto volume.
Seek error! (n) Seek process error on the FXoto volume.
Read error! (n) Read process error on the FXoto volume.
Write error! (n) Write process error on the FXoto volume.
Close error! (n) Close proce ss error on the FXoto volume.

11. When you are finished allocating datasets on FXoto volumes, select Close to
close the Allocation panel and exit the ALC utility.

Preparing for Cross-OS File Exchange Operations 3-35

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

Figure 3-14 ALC Utility for Windows 2000/2003/Windows NT systems

Figure 3-15 ALC Disk Not Found Message

Figure 3-16 ALC Allocation Complete Message

3-36 Preparing for Cross-OS File Exchange Operations

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

Figure 3-17 ALC Error Message

Preparing for Cross-OS File Exchange Operations 3-37

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

3-38 Preparing for Cross-OS File Exchange Operations

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

4

Using the Cross-OS File Exchange

Software

This chapter describes the user interface and the commands available to an FX
user.

 FCU for UNIX
 FCU for Windows
 Format Utility for Windows
 Allocation Utility for Windows

Using the Cross-OS File Exchange Software 4-1

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

FCU for UNIX

The FCU GUI enables you to perform FX file transfer operations interactively
and provides access to detailed information on the datasets/files in the
specified FX source volume/directory. The FCU GUI displays the FX operations
in the FCU parameter definition file (if specified), allows you to modify the FCU
parameter definition file interactively, and also allows you to enter FCU
parameters and perform FX operations manually. The FCU GUI also displays
the error information for FX operations.

FCU Version and Copyright Screen

To start the FCU GUI program for UNIX -based platforms:

1. At the UNIX command line prompt, enter: fcu [-nc] [param]
The -nc option (nc = no checking) tells FCU to execute all specified FX

operations without requesting confirmation for FCU parameters or checking
for existing FXmto target files. If you want to bypass these confirmations,
enter -nc.

The param option tells FCU whether to use the FCU parameter definition
file or a specific FCU initiation parameter set to perform FX operations. The
param option must have one of the following three values:

– [blank]. If you want to use the default FCU parameter definition file

(fcudata.param in the current directory), leave the param option blank
(do not enter anything).

– file_name. If you want to use a different FCU parameter definition file,

enter the file name with complete path (absolute or relative) if not in the
current directory.

– -P + parameters. If you want to perform one specific FX operation, enter

-P followed by the FCU initiation parameter set (e.g., mto VSN:dataset
targetfile No No No) for the desired FX operation. The -P option
requires the -nc option.

For example:

– If you want to use the default FCU parameter definition file and check the

parameters and FXmto target files, enter: fcu

– If you want to use the default FCU parameter definition file and perform

all operations without checking parameters or FXmto target files,
enter: fcu -nc

– If you want to use a different FCU parameter definition file and perform all

operations without checking parameters or FXmto target files, enter: fcu -
nc filename

– If you want to perform one specific FX operation, enter: fcu -nc -P

[parameters]

4-2 Using the Cross-OS file Exchange Software

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

Note: The following warnings may appear during FCU startup. These
warnings do not affect FCU and can be ignored.

WARNING: Missing characters in String to FontSet conversion.
WARNING: Cannot convert string “-dt-interface system-medium-r-

normal -m*-*-*-*-*-*-*-*-*” to type FontSet.

Using the Cross-Os File Exchange Software 4-3

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

2. The FCU GUI program now starts loading. The FCU version and copyright

screen (see

Figure 5-1) is displayed while FCU is loading. When FCU is

finished loading, the FCU main panel is displayed.

3. If you specified the -nc option, FCU processes all specified operations,

overwrites existing mto target files, terminates, and displays any error
information at the UNIX prompt.

FAL for xxxxxx (OS name)

File Conversion Utility

Ver. xx-xx-xx/xx

All right reserved, Copyright (C) 1997, 1998 Hitachi, Ltd.

Figure 4-1 FCU Version and Copyright Screen (UNIX)

File Conversion Utility Screen

The FCU main panel opens when the FCU GUI program is finished loading. The
FCU main panel displays the FCU initiation parameter sets in the specified FCU
parameter definition file (if available), allows you to perform FX operations,
and provides access to all FCU functions.

4-4 Using the Cross-OS file Exchange Software

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

File Conversion Utility

N

N

N

N

N

File

Parameter File

Volume File

Direction

Input File

Output File

Code Conversion

Padding

Delimiter

Emp
RDW
VSE
Status

M to O

E<->A

Yes

CR

Yes

Yes

O to M

EcA

LF

Help

OK

Cancel

o
o

o

o
o

FILE

Figure 4-2 FCU Main Panel for UNIX Platforms

The File and Help buttons display the File menu commands and Help menu
commands. These commands are described later in this section.

The Parameter File field displays the FCU parameter definition file that you
specified by the param option when you started FCU. If this field is blank, FCU
could not find the default or specified FCU parameter definition file. If you
want to use an FCU parameter definition file, you can enter the desired file
name in this field (complete path if not in the current directory). If you do not
want to use an FCU parameter definition file, you can leave the Parameter
File field blank and enter the FCU initiation parameters manually.

The Volume File field displays the FX volume definition file. This file must
have the default name and location (datasetmount.dat in current directory).
If this field is blank, FCU could not find the file and will not be able to perform
FX operations. In this case, exit FCU, and create the FX volume definition file
as described in section “

Creating the FX Volume Definition File(s)”.

Using the Cross-Os File Exchange Software 4-5

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

When FCU starts up, the first set of FCU initiation parameters is automatically
loaded from the specified FCU parameter definition file (unless the file is not
found). If desired, you can change any of the parameters, or you can use the
File-Load command to load the next parameter set. The FCU initiation
parameters are:

• Direction. The Direction buttons allow you to select the desired direction

for the FX operation: M to O = FXmto, O to M = FXotm.

• Input File. The Input File field allows you to enter the name of the FX

source file. For FXmto, enter the z/OS volser and dataset name
(VSN:dataset). For FXotm, enter the UNIX file name (with complete path if
not in the current directory).

• Output File. The Output File field allows you to enter the name of the FX

target file. For FXmto, enter the UNIX file name (with complete path if not in
the current directory). For FXotm, enter the VSN and dataset name
(volser:dataset).

• Code Conversion. The Code Conversion buttons allow you to select the

desired code conversion option (see section Code Conversion (CC)
Option): E<->A = default code conversion table, EcA = default code
conversion table (for FXoto only), No = no code conversion, File = enter the
file name of your conversion table (with complete path if not in current
directory).

• Padding. The Padding buttons allow you to select the desired padding

option (see section Padding (PAD) Option): Yes = padding, No = no padding.

• Delimiter. The Delimiter buttons allow you to select the desired delimiter

option (see section Delimiter (DEL) Option): CR = carriage return, LF = line
feed, No = no delimiters.

• Emp. The Emp buttons allow you to select the empty file option (see section

Empty File (Emp) Option):
Yes = source file is empty, No = source file is not empty.

• RDW. The RDW buttons allow you to select the record description word

option (mto only) (see section Empty File (Emp) Option): Yes = add RDW to
each record (Code Conversion, Padding, and Delimiter must be No), No
= do not add RDW to each record.

• VSE. The VSE field allows you to enter the VSE record information: RF,RL,BL

Use a comma (no spaces) between each value. See section
Description Word (RDW) Option for further information on the VSE record
option values.

The OK button starts the specified FX operation. The Cancel button removes
the values entered by the user and returns the FCU main panel to the initial
settings. (The Cancel button does not cancel the FX operation in progress.) Be
careful not to click OK or Cancel more than once. The Status field displays
the status of the requested FX operation:

Record

4-6 Using the Cross-OS file Exchange Software

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