Hitachi Cross-OS File Exchange

User’s Guide
Hitachi Virtual Storage Platform
Hitachi Universal Storage Platform V/VM
Hitachi TagmaStore® Universal Storage Platform
Hitachi TagmaStore® Network Storage Controller

FASTFIND LINKS
Document Organization
Product Version
Getting Help
Contents

MK-96RD647-08
 Copyright © 2010 Hitachi, Ltd. All rights reserved.

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

Hitachi and Hitachi Data Systems reserve the right to make changes to this document at any
time without notice and assume no responsibility for its use. This document contains the most
current information available at the time of publication. When new and/or revised information
becomes available, this entire document will be updated and distributed to all registered users.

Some of the features described in this document may not be currently available. Refer to the
most recent product announcement or contact your local Hitachi Data Systems sales office for
information about feature and product availability.

Notice: Hitachi Data Systems products and services can be ordered only under the terms and
conditions of the applicable Hitachi Data Systems agreement(s). The use of Hitachi Data
Systems products is governed by the terms of your agreement(s) with Hitachi Data Systems.

Hitachi is a registered trademark of Hitachi, Ltd. in the United States and other countries.
Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd. in the United
States and other countries.

ShadowImage and TrueCopy are registered trademarks of Hitachi Data Systems.

AIX, ESCON, FICON, FlashCopy, IBM, MVS/ESA, MVS/XA, OS/390, S/390, VM/ESA, VSE/ESA,
z/OS, zSeries, z/VM, and zVSE are registered trademarks or trademarks of International
Business Machines Corporation.

All other trademarks, service marks, and company names are properties of their respective
owners.

Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.

ii

Hitachi Cross-OS File Exchange User’s Guide

 Contents

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

Intended Audience ............................................................................................ viii
Product Version................................................................................................. viii
Document Revision Level ................................................................................... viii
Source Document(s) for this Revision ................................................................. viii
Changes in this Revision ...................................................................................... ix
Document Organization ....................................................................................... ix
Referenced Documents.........................................................................................x
Document Conventions........................................................................................ xi
Convention for Storage Capacity Values .............................................................. xiii
Getting Help ..................................................................................................... xiii
Comments ........................................................................................................ xiv

Overview of Hitachi Cross-OS File Exchange ........................................... 1-1

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

Components .....................................................................................................2-2
FX Volume Types........................................................................................2-3
FCU File Transfer Options ..................................................................................2-8
Code Conversion (CC) Option ......................................................................2-8
PIPE Function...........................................................................................2-10
Padding (PAD) Option ...............................................................................2-13
Delimiter (DEL) Option ..............................................................................2-14
Empty File (Emp) Option ...........................................................................2-15
Record Description Word (RDW) Option .....................................................2-15
VSE Record (VSE) Option...........................................................................2-16
FXmto Operations ...........................................................................................2-16
FXmto with Fixed-Length Record Format ....................................................2-18
FXmto with Variable-Length Record Format ................................................2-19
FXmto with Multiple Volume Datasets.........................................................2-22

Contents iii

Hitachi Cross-OS File Exchange User’s Guide

 FXotm Operations........................................................................................... 2-23
FXotm with Fixed-Length Record Format.................................................... 2-24
FXotm with Variable-Length Record Format................................................ 2-26
FXotm with Multiple Volume Datasets ........................................................ 2-27
FXoto Operations............................................................................................ 2-28
Host Access and I/O Contention ...................................................................... 2-29
Bidirectional Data Transfer .............................................................................. 2-31
AIX Shared Open Function .............................................................................. 2-32
Retry Reserved-Volume Function ..................................................................... 2-33
Supported OS and OS Versions ................................................................. 2-33
AIX Reserve Retry Function ...................................................................... 2-35
Specifying the Environment Variables for the Retry Function ....................... 2-35
Output Retry Log Function........................................................................ 2-37
Errors ..................................................................................................... 2-37
Get Detail Traces Function .............................................................................. 2-38
(1) Check Sending File ............................................................................. 2-40
(2) Set Mode of Making Copy Files ............................................................ 2-40
(3) Set Name of Traces ............................................................................ 2-41
(4) Make Copy Files After Getting Information ............................................ 2-41
(5) Check Information of Sending Files ...................................................... 2-41
(6) Output Traces of Record Size .............................................................. 2-41
(7) Output Traces (FCU Error Occurred)..................................................... 2-42
(8) Output Core Dump ............................................................................. 2-42
Interval Function for OtM Transfer Completion (Linux) ...................................... 2-43
Environment Variable for Interval Time...................................................... 2-44
Display Window for Interval Function ........................................................ 2-44

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

System Requirements ....................................................................................... 3-2
64-bit Version FCU ..................................................................................... 3-6
VSE Requirements and Restrictions ............................................................. 3-6
Compiler Requirements .............................................................................. 3-8
Maximum Data Size ................................................................................... 3-9
Interoperability with HDLM ....................................................................... 3-10
Installing and Configuring the FX Volumes........................................................ 3-11
Installing the FX Software ............................................................................... 3-15
Installing FX on UNIX-Based Platforms....................................................... 3-15
Installing FX on Windows ......................................................................... 3-17
Uninstalling the FX Software on UNIX-Based Platforms................................ 3-18
Uninstalling FX on Windows ...................................................................... 3-19
Updating or uninstalling the FAL version when using File Exchange Code
Converter ......................................................................................... 3-20

iv Contents

Hitachi Cross-OS File Exchange User’s Guide

 Entering the FX License Key Code.....................................................................3-21
Using the ppkeyset Command to Enter the License Key ...............................3-21
Using the autoppkeyset Command to Enter the License Key.........................3-22
Creating FXoto Volumes Using the FMT Utility ...................................................3-24
Creating the FX Volume Definition File(s) ..........................................................3-29
Verifying Mainframe Dataset Requirements .......................................................3-33
Allocating FXoto Intermediate Datasets.............................................................3-34
UNIX .......................................................................................................3-34
Windows Systems.....................................................................................3-35

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
Error Information Screen.............................................................................4-8
FCU for Windows ..............................................................................................4-9
FCU Version and Copyright Dialog ................................................................4-9
File Conversion Utility Window ...................................................................4-10
Volume Information Dialog ........................................................................4-13
Mainframe File Information Dialog .............................................................4-14
Option Dialog ...........................................................................................4-15
Parameter Line Dialog...............................................................................4-16
Execute Dialogs........................................................................................4-17
Error Information Dialog ...........................................................................4-18
Log Files ..................................................................................................4-18
Format Utility for Windows...............................................................................4-20
Allocation Utility for Windows ...........................................................................4-25

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-4
Using the listvol Function (UNIX) .................................................................5-6
Creating FCU Parameter Definition Files (UNIX).............................................5-8
Creating Multiple Volume Definition Files (UNIX) .........................................5-15
Using FCU from the Command Line (UNIX).................................................5-17
Performing File Transfer Operations – Windows.................................................5-20
Starting the FCU GUI ................................................................................5-20
Performing File Transfer Operations (Windows)...........................................5-21
Creating FCU Parameter Definition Files (Windows) .....................................5-25
Creating Multiple Volume Definition Files (Windows)....................................5-26
Using FCU from the Command Line (Windows) ...........................................5-28

Contents v

Hitachi Cross-OS File Exchange User’s Guide

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
Converting DO and RF Information............................................................ 6-11
Using the FAL Functions.................................................................................. 6-13
Multi-Thread Function ..................................................................................... 6-17
Information Storage Area ......................................................................... 6-18
Open Dataset .......................................................................................... 6-19
Read Data ............................................................................................... 6-20
Write Data............................................................................................... 6-21
Close Dataset .......................................................................................... 6-22
Free Information Stored Area.................................................................... 6-22
Initialize Target Record Pointer ................................................................. 6-23
Compiling ...................................................................................................... 6-28
Error Information ........................................................................................... 6-29
FAL Usage Scenario ........................................................................................ 6-30

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

Troubleshooting ............................................................................................... 7-2
Error Codes and Messages ................................................................................ 7-3
FCU Error Codes for UNIX........................................................................... 7-6
FCU Error Codes for Windows Systems ...................................................... 7-16
Calling the Support Center .............................................................................. 7-21

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

Acronyms and Abbreviations

vi Contents

Hitachi Cross-OS File Exchange User’s Guide

 Preface
This document describes and provides instructions for installing and using the
Hitachi Cross-OS File Exchange software (FX) for the following Hitachi RAID
storage systems:
Hitachi Virtual Storage Platform (VSP)
Hitachi Universal Storage Platform V (USP V)
Hitachi Universal Storage Platform VM (USP VM)
Hitachi TagmaStore® Universal Storage Platform (TagmaStore USP)
Hitachi TagmaStore® Network Storage Controller (TagmaStore NSC)

The Cross-OS File Exchange software has two components: File Access Library
(FAL), and File Conversion Utility (FCU). Throughout this document the terms
“FAL”, “FCU”, and “FAL/FCU” refer to the Cross-OS File Exchange software.

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
Source Document(s) for this Revision
Changes in this Revision
Document Organization
Referenced Documents
Document Conventions
Convention for Storage Capacity Values
Getting Help
Comments

Preface vii

Hitachi 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 RAID storage systems.

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 RAID storage systems and has read
the User and Reference Guide for the storage system (e.g., Universal
Storage Platform V/VM User and Reference Guide).
• The user is familiar with the Storage Navigator software for the Hitachi
RAID storage systems and has read the Storage Navigator User’s Guide.

Product Version
This document revision applies to FAL/FCU version 01-XX-66/2x or later.

Document Revision Level

Revision Date Description

MK-96RD647-P February 2007 Preliminary Release

MK-96RD647-00 April 2007 Initial Release, supersedes and replaces MK-96RD647-P

MK-96RD647-01 May 2007 Revision 1, supersedes and replaces MK-96RD647-00

MK-96RD647-02 September 2007 Revision 2, supersedes and replaces MK-96RD647-01

MK-96RD647-03 November 2007 Revision 3, supersedes and replaces MK-96RD647-02

MK-96RD647-04 August 2008 Revision 4, supersedes and replaces MK-96RD647-03

MK-96RD647-05 November 2008 Revision 5, supersedes and replaces MK-96RD647-04

MK-96RD647-06 June 2009 Revision 6, supersedes and replaces MK-96RD647-05

MK-96RD647-07 May 2010 Revision 7, supersedes and replaces MK-96RD647-06

MK-96RD647-08 October 2010 Revision 8, supersedes and replaces MK-96RD647-07

Source Document(s) for this Revision

• Reference Manual, File Access Library & File Conversion Utility, revisions
33.15 – 34.0

viii Preface

Hitachi Cross-OS File Exchange User’s Guide

Changes in this Revision
• Added the Hitachi Virtual Storage Platform storage system.
• Added descriptions for read/write of emulation type -C volumes from
mainframe and open hosts.
• Added initialization information regarding emulation type -C volumes.
• Added description for updating FAL version only.
• Added format note for Solaris, HP-UX, and AIX FX parameters

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

Chapter Description

Overview of Cross-OS File Provides a brief overview Cross-OS File Exchange functions, features,
Exchange and benefits.

About Cross-OS File Describes how Cross-OS File Exchange operates in typical system
Exchange Operations configurations and the operations a user may perform.

Preparing for Cross-OS File Describes the system and volume configuration requirements for
Exchange Operations Cross-OS File Exchange and provides instructions on installing Cross-
OS File Exchange.

Using the Cross-OS File Describes the user interface and commands available to a Cross-OS
Exchange Software File Exchange user.

Performing Cross-OS File Describes how to operate Cross-OS File Exchange.

Exchange Operations

Performing FAL Operations Describes how to perform FAL operations using Cross-OS File
Exchange.

Troubleshooting Provides descriptions of error codes and support desk contact data.

Preface ix

Hitachi Cross-OS File Exchange User’s Guide

Referenced Documents
Hitachi Cross-OS File Exchange:
• Hitachi Cross-OS File Exchange Code Converter User’s Guide, MK-94RD253

Hitachi Virtual Storage Platform:

• Provisioning Guide for Open Systems, MK-90RD7022
• Configuration Guide for Sun Solaris Host Attachment, MK-96RD632
• Storage Navigator User Guide, MK-90RD7027
• Storage Navigator Messages, MK-90RD7028
• User and Reference Guide, MK-90RD7042

Hitachi Universal Storage Platform V/VM:

• LUN Manager User’s Guide, MK-96RD615
• LUN Expansion User’s Guide, MK-96RD616
• Storage Navigator User’s Guide, MK-96RD621
• Virtual LVI/LUN and Volume Shredder User’s Guide, MK-96RD630
• User and Reference Guide, MK-96RD635
• Configuration Guide for Sun Solaris Host Attachment, MK-96RD632
• Hitachi Multiplatform Backup User’s Guide, MK-98RD6713

Hitachi TagmaStore USP/NSC:

• LUN Manager User’s Guide, MK-96RD615
• LUN Expansion, Virtual LVI/LUN, and Volume Shredder User’s Guide,
MK-94RD205
• Sun Solaris Configuration Guide, MK-94RD236
• Universal Storage Platform User and Reference Guide, MK-94RD231
• Network Storage Controller User and Reference Guide, MK-95RD279

Hitachi Dynamic Link Manager (HDLM):

• Hitachi Dynamic Link Manager User's Guide for IBM AIX Systems,
MK-92DLM111
• Hitachi Dynamic Link Manager User's Guide for HP-UX Systems,
MK-92DLM112
• Hitachi Dynamic Link Manager User's Guide for Sun Solaris Systems,
MK-92DLM114
• Hitachi Dynamic Link Manager User's Guide for Windows Systems,
MK-92DLM129

x Preface

Hitachi Cross-OS File Exchange User’s Guide

Document Conventions
The terms “Virtual Storage Platform” and “VSP” refer to all models of the
Hitachi Virtual Storage Platform storage system, unless otherwise noted.

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

The Cross-OS File Exchange software has two components: File Access Library
(FAL), and File Conversion Utility (FCU). Throughout this document the terms
“FAL”, “FCU”, and “FAL/FCU” refer to the Cross-OS File Exchange software.

This document uses the following typographic conventions:

Convention Description

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

Italic 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 variables.
screen/code Indicates text that is displayed on screen or entered by the user.
Example: # pairdisplay -g oradb

< > angled brackets Indicates a variable, which is a placeholder for actual text provided by the
user or system. Example: # pairdisplay -g <group>
Note: Italic font is also used to indicate variables.

[ ] square brackets Indicates optional values. Example: [ a | b ] indicates that you can choose
a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicates that

you must choose either a or b.

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

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

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

Icon Meaning Description

Note Calls attention to important and/or additional information.

Tip Provides helpful information, guidelines, or suggestions for performing

tasks more effectively.

Caution Warns the user of adverse conditions and/or consequences (e.g.,

disruptive operations).

Preface xi

Hitachi Cross-OS File Exchange User’s Guide

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

xii Preface

Hitachi 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:

Physical capacity unit Value

1 KB 1,000 (103) bytes

1 MB 1,000 KB or 1,0002 bytes

1 GB 1,000 MB or 1,0003 bytes

1 TB 1,000 GB or 1,0004 bytes

1 PB 1,000 TB or 1,0005 bytes

1 EB 1,000 PB or 1,0006 bytes

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

Logical capacity unit Value

1 block 512 bytes

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

Accessing Product Documentation

The user documentation for the Hitachi RAID storage systems is available on
the Hitachi Data Systems Portal: https://hdssupport.hds.com. Check this site
for the most current documentation, including important updates that may
have been made after the release of the product.

Getting Help
The Hitachi Data Systems customer support staff is available 24 hours a day,
seven days a week. If you need technical support, log on to the Hitachi Data
Systems Portal for contact information: https://hdssupport.hds.com

Preface xiii

Hitachi Cross-OS File Exchange User’s Guide

Comments
Please send us your comments on this document: doc.comments@hds.com.
Include the document title, number, and revision, and refer to specific
section(s) and paragraph(s) whenever possible.

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

xiv Preface

Hitachi Cross-OS File Exchange User’s Guide

 1
Overview of Hitachi Cross-OS
File Exchange
Hitachi Cross-OS File Exchange (FX) enables data stored on the Hitachi RAID
storage systems to be converted and transferred between mainframe and
open-system platforms and between different open-system platforms.
• The FX mainframe-to-open (FXmto) capability enables you to transfer data
from mainframe datasets to open-system files.
• The FX open-to-mainframe (FXotm) capability enables you to transfer data
from open-system files to mainframe datasets.
• The FX open-to-open (FXoto) capability enables you to transfer data
between open-system platforms without being attached to a mainframe
host.

Cross-OS File Exchange utilizes special FX volumes that are dedicated to data
exchange operations and are accessed as raw devices to provide the greatest
platform flexibility for multiplatform data exchange.

Cross-OS File Exchange provides the following benefits for the user:
• Cross-OS File Exchange provides a centralized data management and
disaster recovery environment for both mainframe and open-systems data.
• Cross-OS File Exchange provides high-speed data transfer over FICON,
ESCON, and fibre channels, freeing up valuable network resources and
communication links for application use.
• Cross-OS File Exchange’s high-speed data exchange enables you to
implement file-level backup of open-systems data to mainframe storage.

Overview of Hitachi Cross-OS File Exchange 1-1

Hitachi Cross-OS File Exchange User’s Guide

1-2 Overview of Hitachi Cross-OS File Exchange

Hitachi 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
Bidirectional Data Transfer
AIX Shared Open Function
Retry Reserved-Volume Function
Get Detail Traces Function
Interval Function for OtM Transfer Completion (Linux)

About Cross-OS File Exchange Operations 2-1

Hitachi Cross-OS File Exchange User’s Guide

Components
Figure 2-1 illustrates the typical system configurations 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).

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.

File Conversion Utility

Application program
(FCU)
Utility program
Application program
File Access Utility program
Library (FAL)

OS (MVS or VSE)
OS (UNIX, PC server)

ExSA (ESCON®) or FICON interface Fibre-channel interface

Database 1 IIntermediate IIntermediate Database 2

(e.g., DB2/XD)M) file 1 (SAM file 2 (UNIX/PC (e.g., ORACLE)
dataset) server)

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

Volume dedicated Volume shared by mainframe Volumes dedicated to open system

to mainframe and open-system

Figure 2-1 FXmto and FXotm System Configuration

2-2 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

 File Conversion File Conversion
Application
Utility (FCU) Utility (FCU) Application
program File Access Formatter/ Formatter/ File Access program
Library Allocater Allocater Library
Utility program (FMT/ALC) (FAL) Utility program
(FAL) (FMT/ALC)

OS (UNIX, PC server) OS (UNIX, PC server)

Fibre-channel interface Fibre-channel interface

Open-System Intermediate File Open-System

Files (SAM dataset) Files

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

Volume dedicated to open system Shared volume (initialized as mainframe Volume dedicated to open system
CKD format by FMT/ALC)

Figure 2-2 FXoto System 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++), which provides
an application-programming interface for data exchange. The FAL functions
can be called by user application programs to read and write data in
mainframe datasets on the Hitachi storage systems. There are two types of
FAL, the 32bitFAL and the 64bitFAL. The latter is provided by the Hitachi RAID
storage systems. The FMT and ALC utilities enable the open-system user to
format OPEN-x logical units (LUs) and create intermediate datasets for FXoto
operations, without having to be attached to any mainframe hosts. OPEN-x is
defined as a standard LU type. The Hitachi RAID storage systems support
OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L, and OPEN-V devices. Contact
your Hitachi Data Systems account team for the latest information on
supported LU types.

FX Volume Types
The FXmto and FXotm volumes are mainframe devices that can only be
accessed by open-system hosts using the FX software. The FXoto volumes are
open-system devices that cannot be accessed by mainframe hosts. FX
operations are performed using the following types of FX volumes on the
Hitachi RAID storage systems:

About Cross-OS File Exchange Operations 2-3

Hitachi Cross-OS File Exchange User’s Guide

 • FXmto, FXotm. The FX -A volumes can be used for FXmto and FXotm
operations. Mainframe hosts have normal read/write access to -A volumes.
Open-system hosts have read/write access to -A volumes but must use FX
to access these volumes as raw devices (no mount operation). Figure 2-3
shows the structure of the FX -A volumes.

MAINFRAME OPEN SYSTEM

Cyl#0
Label area
Cyl# 0
VTOC

Read/Write Datasets Read/Write

Cyl# MAX.
Management area
Cyl# max.

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.
Mainframe hosts have normal read/write access to -B volumes.
Open-system hosts have read-only access to -B volumes and must use FX
to read these volumes as raw devices (no mount operation). The -B
volumes are write-protected from open-system access. The Hitachi RAID
storage systems will reject all open-system write operations to -B volumes
(except disk partitioning and labeling) to protect the mainframe data on
these volumes.
Figure 2-4 shows the structure of the FX -B volumes.

2-4 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

 MAINFRAME OPEN SYSTEM

Cyl# 0
Label area
Read/Write
Cyl# 0
VTOC

Datasets
Read/Write Read only

Cyl# MAX.
Read/Write
Management area
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
FX to access these volumes as raw devices (no mount operation).
Mainframe hosts have read-only access to the -C volumes. The Hitachi
RAID storage systems will reject all Mainframe write operations to -C
volumes (except VTOC) to protect the open-system data on these volumes.
Figure 2-5 shows the structure of the FX -C volumes.
MAINFRAME OPEN SYSTEM

Cyl# 0
Label area
Cyl# 0
Read/Write VTOC

Read/Write

Read only Datasets

Cyl# MAX.
Management area
Cyl# max.

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

About Cross-OS File Exchange Operations 2-5

Hitachi Cross-OS File Exchange User’s Guide

 • 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 FX to access
these volumes as raw devices (no mount operation). Mainframe hosts do
not have any access to the OPEN-x FMT volumes. Figure 2-6 shows the
structure of the FX OPEN-x FMT volumes.
MAINFRAME OPEN SYSTEM

Cyl#0
Label area
Cyl# 0
VTOC

No Access Datasets Read/Write

Cyl# MAX.
Management area
Cyl# max.

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 Cross-OS File Exchange User’s Guide

AIX Installations

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.

Microsoft® Cluster Server Installations

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.
• When configuring MSCS and the server OS is Windows, FXotm and FXmto
cannot be started.

Windows Installations
• 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
environment. If a signature-writing attempt is made by the Disk Administrator
with Windows, a Write Error will appear in order to stop the signature from
being written. When the Windows Disk Administrator starts again, a request
will be made again to write the signature. Do not write the signature.

About Cross-OS File Exchange Operations 2-7

Hitachi Cross-OS File Exchange User’s Guide

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:
• Code conversion (CC)
• Padding (PAD)
• Delimiters (DEL)
• Record description word (RDW)
• VSE record (VSE)
• Empty file (Emp)

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 Table 2-1), or your own code
conversion table (see Table 2-2). When the default table is specified, FCU
performs EBCDIC-to-ASCII code conversion for FXmto operations and
ASCII-to-EBCDIC code conversion for FXotm operations as specified in Table
2-1 (see also Appendix A). 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.

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: The default EBCDIC-ASCII code conversion table is the ACM standard
table (not CACM). Appendix A provides the code conversion information for the
default table shown in Table 2-1. If the default code conversion table does not
yield the desired results, create your own code conversion table. Refer to the
IBM code tables for detailed information on EBCDIC-ASCII code conversion.

2-8 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Table 2-1 Default EBCDIC-ASCII Code Conversion Table for FCU
H
L 0 1 2 3 4 5 6 7 8 9 A B C D E F

0 NUL DLE DS SP & - { } \ 0

(00) (10) (80) (90) (20) (26) (2D) (BA) (C3) (CA) (D1) (D8) (7B) (7D) (5C) (30)

1 SOH DC1 SOS / a j A J 1

(01) (11) (81) (91) (A0) (A9) (2F) (BB) (61) (6A) (E5) (D9) (41) (4A) (9F) (31)

2 STX DC2 FS SYN b k s B K S 2

(02) (12) (82) (16) (A1) (AA) (B2) (BC) (62) (6B) (73) (DA) (42) (4B) (53) (32)

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

4 PF TM BYP PN d m u D M U 4
(9C) (9D) (84) (94) (A3) (AC) (B4) (BE) (64) (6D) (75) (DC) (44) (4D) (55) (34)

5 HT LF RS e n v E N V 5
(09) (85) (0A) (95) (A4) (AD) (B5) (BF) (65) (6E) (76) (DD) (45) (4E) (56) (35)

6 LC BS ETB UC f o w F O W 6
(86) (08) (17) (96) (A5) (AE) (B6) (C0) (66) (6F) (77) (DE) (46) (4F) (57) (36)

7 DEL IL ESC EOT g p x G P X 7

(7F) (87) (1B) (04) (A6) (AF) (B7) (C1) (67) (70) (78) (DF) (47) (50) (58) (37)

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

9 RLF EM ‘ i r z I R Z 9
(8D) (19) (89) (99) (A8) (B1) (B9) (60) (69) (72) (7A) (E1) (49) (52) (5A) (39)

A SMM CC SW ! : ^
(8E) (92) (8A) (9A) (D5) (21) (CB) (3A) (C4) (5E) (D2) (E2) (E8) (EE) (F4) (FA)

B VT CUI CUI CU3 . $ , #

(0B) (8F) (8B) (9B) (2E) (24) (2C) (23) (C5) (CC) (D3) (E3) (E9) (EF) (F5) (FB)

C FF IFS DC4 < * % @

(0C) (1C) (8C) (14) (3C) (2A) (25) (40) (C6) (CD) (D4) (E4) (EA) (F0) (F6) (FC)

D CR IGS ENQ NAK ( ) _ ’ [ ]

(0D) (1D) (05) (15) (28) (29) (5F) (27) (C7) (CE) (5B) (5D) (EB) (F1) (F7) (FD)

E SO IRS ACK + ; > =

(0E) (1E) (06) (9E) (2B) (3B) (3E) (3D) (C8) (CF) (D6) (E6) (EC) (F2) (F8) (FE)

F SI IUS BEL SUB | ~ ? “

(0F) (1F) (07) (1A) (7C) (7E) (3F) (22) (C9) (D0) (D7) (E7) (ED) (F3) (F9) (FF)

Legend for Table 2-1

Bit Positions
Hi Lo

ASCII 8765 4321

EBCDIC (IBM) 0123 4567

About Cross-OS File Exchange Operations 2-9

Hitachi Cross-OS File Exchange User’s Guide

 Table 2-2 User-Defined Code Conversion Table
Item Requirement

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” which 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. Named pipes are strictly unidirectional, even on systems where
anonymous pipes are bidirectional (full-duplex).

2-10 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

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

About Cross-OS File Exchange Operations 2-11

Hitachi 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(‘r’ mode)
| |
open pipe(‘w’ mode) waiting receive data entries
| |
waiting send data entries |
| receive data OK
send data OK |
| read data
write data |
| close pipe
close pipe |
| |
end

Figure 2-7 Pipe Function Process Outline

2-12 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

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 FXotm Operations 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.
Note: If you use FXmto with padding, the data cannot be transferred back to
the original mainframe dataset (the FXotm target dataset will not be
compatible with the original dataset). If you use FXotm with padding, the
delimiter option is required.

About Cross-OS File Exchange Operations 2-13

Hitachi Cross-OS File Exchange User’s Guide

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 FXotm Operations 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 can specify a carriage return (CR), a line
feed (LF), or no delimiter. The length of this delimiter is one byte.
If no delimiter is specified for FXmto, the transferred data is seen as one
long record.
If CR is specified for FXotm, data up to the carriage return is cut off as a
data entity.
If LF is specified for FXotm, data up to the line feed is cut off as a data
entity.
If no delimiter is specified for FXotm, data is cut off according to the
dataset record length.
• For Windows, you can specify a CR + LF or no delimiter. The length of this
delimiter is two bytes.
If CRLF is specified for FXotm, data up to CR+LF is cut off as a data entity.
If no delimiter is specified for FXotm, data is cut off according to the
dataset record length.
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: When you use FXmto with delimiter (no padding) for variable-length
records, the data can be transferred back to the original mainframe dataset
later using FXotm.

2-14 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

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

Record Description Word (RDW) Option

The record description word option can only be used for FXmto operations on
variable-length source datasets. Figure 2-8 shows an FXmto operation with the
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 mainframe dataset (the FXotm target dataset will not be compatible
with the original dataset).

Source Dataset Open-System Target

File
Record length Record length

RL Record 1: Data entity RL Data entity 1

1

RL Record 2: Data entity 2

→ RL Data entity 2

RL Record 3: Data entity 3 RL Data entity 3

Figure 2-8 FXmto with the RDW Option

About Cross-OS File Exchange Operations 2-15

Hitachi Cross-OS File Exchange User’s Guide

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.

FXmto Operations
An FXmto operation transfers the data from a mainframe 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 storage system. 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 supports
both fixed-length and variable-length record formats and provides the
following options for FXmto data transfer (see System Requirements): 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)

2-16 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

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 2-9

FXmto N/A Yes Fixed-length Æ Fixed-length 2-10

FXmto No No Variable-length Æ Variable-length 2-11

FXmto Yes No Variable-length Æ Fixed-length 2-12

FXmto No Yes Variable-length Æ Variable-length 2-13

FXmto Yes Yes Variable-length Æ Fixed-length 2-14

About Cross-OS File Exchange Operations 2-17

Hitachi Cross-OS File Exchange User’s Guide

FXmto with Fixed-Length Record Format
Each fixed-length record in a mainframe 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 length Record length

Record 1: Data entity 1 Data entity 1

Record 2: Data entity 2

→ Data entity 2

Record 3: Data entity 3 Data entity 3

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 data entity length plus one byte for the delimiter. The
resulting length of each data entity in a Windows target file equals the original
data entity length plus two bytes for the delimiter.

Source Dataset Open-System Target File

Record length Record length + 1 or 2 bytes

Record 1: Data entity 1 Data entity 1 D

Record 2: Data entity 2

→ Data entity 2 D

Record 3: Data entity 3 Data entity 3 D

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

2-18 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

FXmto with Variable-Length Record Format
Each variable-length record in a mainframe 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
mainframe 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

Record length Record length – 4 bytes

RL Record 1: Data entity 1 Data entity 1

RL Record 2: Data entity 2

→ Data entity 2

RL Record 3: Data entity 3 Data entity 3

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

Delimiters

About Cross-OS File Exchange Operations 2-19

Hitachi Cross-OS File Exchange User’s Guide

 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.

Source Dataset Open-System Target File

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

RL Record 1: Data entity 1 Data entity 1 padding

RL Record 2: Data entity 2

→ Data entity 2

RL Record 3: Data entity 3 Data entity 3 padding

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

Record length Data entity length + 1 or 2 bytes

RL Record 1: Data entity 1 Data entity 1 D

RL Record 2: Data entity 2

→ Data entity 2 D

RL Record 3: Data entity 3 Data entity 3 D

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

2-20 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

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.

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

Source Dataset Open-System Target File

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

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

RL Record 2: Data entity 2

→ Data entity 2 D

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

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 target file
equals the maximum record length minus two bytes (minus four for the RL,
plus two for the delimiter).

About Cross-OS File Exchange Operations 2-21

Hitachi Cross-OS File Exchange User’s Guide

FXmto with Multiple Volume Datasets
Multiple Volume dataset is supported for FXmto, when the version is
01-XX-50/ YY(XX=01 or 02, 03 or 04) or later.

A multiple volume definition file (multidef.dat) is necessary in current

directory. FAL will check dataset serial number, dataset serial number and last
volume containing data in this dataset in dataset indicators on VTOC DSCB1.

Multiple volume dataset is supported only for MVS.

FAL checks the dataset serial number, dataset serial number, and last volume
containing data in the multiple volume dataset in dataset indicators on VTOC
DSCB1. Table 2-4 shows the specifications for this checking.

Note: For Windows, 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 cannot guarantee that
the volumes will be shared with other OS platforms (AIX, Solaris, HP-UX,
Linux, etc). When you use a shared volume with Windows 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 Multiple Volume Dataset/Serial Numbers

VTOC DSCB1

Dataset Serial Number

1 1 Other than 1 Other than 1

Last Volume Containing Data in this Dataset, in Dataset Indicators

Function ON OFF ON OFF

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

MTO for single volume* OK(OK) NG(OK) NG(OK) NG(OK)

OK = Allowed combination. NG = Not allowed.

* The dataset does not exist in the multiple volume definition file.
The inside of “( )”: The spec of (a) or (b)
(a) Before version 01-XX-50
(b) Version 01-XX-50 and higher, and “FAL_MULTI_CHECK” of the environment variable is “OFF.”

2-22 About Cross-OS File Exchange Operations

Hitachi 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 a mainframe volume. The FXotm source file
must be located on an FX -C or -A volume on the storage system. FCU does
not automatically create the FXotm target dataset. The target dataset must be
created and properly formatted prior to beginning the FXotm operation.

The FCU software performs the FXotm data transfer operations. FCU supports
fixed-length and variable-length record formats for FXotm operations. FCU
provides the following options for FXotm operations (see FCU File Transfer
Options): code conversion, padding, delimiter, empty file, and VSE record. The
record description word option cannot be used with FXotm. FCU automatically
extracts delimiters from FXotm source files, but cannot add delimiters to
FXotm source files. FCU can add padding only to variable-length FXotm source
files. FCU cannot extract padding from FXotm source files. The types of FXotm
operations are:
• FXotm with fixed-length record format
• FXotm with variable-length record format

The table below specifies the record format requirements for each type of
FXotm operation. An open-system source file with fixed-length data entities
can only be transferred to a fixed-length target dataset. An open-system
source file with variable-length data entities must have delimiters and can be
transferred to a variable-length or fixed-length target dataset. If the source
file contains padding from a previous FXmto transfer operation, the padding is
transferred to the target dataset along with the data. If the source file contains
delimiters, the delimiters are not transferred to the target dataset.

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

Table 2-5 FXotm Record Format Requirements

FCU Record Format Requirements

Direction Source File Target Dataset See Figure

FXotm Fixed-length: no padding, no delimiters Æ Fixed-length 2-15

FXotm Fixed-length containing padding Æ Fixed-length 2-16

FXotm Fixed-length containing delimiters Æ Fixed-length 2-17

FXotm Fixed-length containing padding and delimiters Æ Fixed-length 2-18

FXotm Variable-length: with delimiters Æ Variable-length 2-19

FXotm Variable-length: with padding and delimiters Æ Fixed-length 2-20

About Cross-OS File Exchange Operations 2-23

Hitachi Cross-OS File Exchange User’s Guide

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-System Source File Target Dataset

Record length Record length

Data entity 1 Record 1: Data entity 1

Data entity 2
→ Record 2: Data entity 2

Data entity 3 Record 3: Data entity 3

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

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-System 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
→ Record 2: Data entity 2

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

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

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

2-24 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

With delimiters. Figure 2-17 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-System Source File Target Dataset

Record length + 1 or 2 bytes Record length

Data entity 1 D Record 1: Data entity 1

Data entity 2 D
→ Record 2: Data entity 2

Data entity 3 D Record 3: Data entity 3

Figure 2-18 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-System 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

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

About Cross-OS File Exchange Operations 2-25

Hitachi Cross-OS File Exchange User’s Guide

 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.

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-System Source File Target Dataset

Record length – 2 or 1 byte Record length

Data entity 1 D RL Record 1: Data entity 1

Data entity 2 D
→ RL Record 2: Data entity 2

Data entity 3 D RL Record 3: Data entity 3

Data entity + 1 or 2 bytes

Figure 2-20 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
source file is greater than the maximum record length minus two bytes
(CR+LF delimiter), FCU aborts the operation and reports an error.

2-26 About Cross-OS File Exchange Operations

Hitachi 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 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-System Source File Target Dataset

Record length + 1 or 2 bytes Record length

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

Data entity 2 D
→ Record 2: Data entity 2

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

Figure 2-21 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
source file is greater than the specified record length plus two bytes (CR+LF
delimiter), FCU aborts the operation and reports an error.

FXotm with Multiple Volume Datasets

For FXotm with multiple volume datasets, there is no specific method for
allocating the mainframe datasets. When writing open-systems data to the
mainframe for the first time, you need to write dummy data to the target
datasets on the mainframe before you perform the FXotm file transfer
operations.

If you are writing data back to the mainframe after transferring it from the
mainframe to the open-system using FXmto, you can write the data into the
original multiple volume dataset.

About Cross-OS File Exchange Operations 2-27

Hitachi Cross-OS File Exchange User’s Guide

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 Hitachi RAID storage systems (no attached
mainframe 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 Hitachi RAID storage systems, 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.

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

2-28 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

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 mainframe and open-system hosts.
These FX volumes cannot be accessed concurrently by the mainframe and
open-system hosts, and must be varied offline from the mainframe 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.

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

Note: Please note the following restrictions for the listed operating systems:
• For UNIX operating systems, if the FX version is 01-02-48 and later, FXotm
can run several different datasets simultaneously.
• For Windows operating systems, if the FX 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.

The FX volumes can only be accessed by open-system hosts using the FX

software. The mainframe 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 FX to access all FX volumes.

WARNING: Concurrent access to the FX volumes by the mainframe and

open-system hosts is not supported. The user is responsible for managing
access to FX volumes to avoid I/O contention between the mainframe 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 mainframe host can issue a reserve command to reserve a volume for
exclusive use. The mainframe reserve command prevents access by all other
hosts, including all other mainframe 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 mainframe hosts still have normal access to FXmto
and FXotm volumes reserved by open-system hosts. These reserve
commands affect FX operations as follows:

About Cross-OS File Exchange Operations 2-29

Hitachi Cross-OS File Exchange User’s Guide

 • Reserved by mainframe host. When an FX volume is reserved by the
mainframe host, FX operations cannot be performed on that volume,
because the FX 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 a mainframe-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 mainframe application that issued the
reserve, the success of retry operations on reserved volumes cannot be
guaranteed.
• 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 mainframe
access to the FX volume.
• Unreserved. When an FX volume is not reserved by any mainframe or
open-system host, FX operations can be performed from any open-system
host using FX. All mainframe 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 mainframe
hosts.
• Mainframe access. When the mainframe 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, use unaccess. Do not use any
open-system program which accesses unmounted LUs (e.g., AIX SMIT,
HP-UX SAM).

2-30 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Bidirectional Data Transfer
FX supports bidirectional data transfer for both fixed-length and
variable-length mainframe datasets. Bidirectional data transfer involves
transferring data from mainframe datasets to open-system files and then back
to the original mainframe 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.

About Cross-OS File Exchange Operations 2-31

Hitachi Cross-OS File Exchange User’s Guide

AIX Shared Open Function
To share File Exchange volumes on multiple AIX operating systems:
• For FX versions 01-xx-59 and earlier, when one AIX OS opens a File
Exchange volume, the other AIX OS cannot open the File Exchange
volume. This is because the AIX OS reserves the File Exchange volume
when it opens it.
• For FX 01-xx-60 and later, it is possible to share a FileExchange volume
across multiple AIX operating systems by specifying the environment
variable FAL_NO_RESERVE.

Table 2-6 shows the relationship between shared volumes and FX versions. For
AIX 4.3.1 or later (32bit), you cannot transfer over 2GB data (AIX restriction).

Table 2-6 Shared Volume and FX Version

Object Version Description

FAL for AIX 01-xx-59 and earlier Cannot open a shared volume from multiple AIX systems.
(32/64 bit) 01-xx-60 and later Can open a shared volume from multiple AIX systems by
specifying the environment variable.

To define environment variables:

• By specifying the environment variable (FAL_NO_RESERVE), you can select
shared open or exclusive open. Table 2-7 shows the relationship
between 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

2-32 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Retry Reserved-Volume Function
When FileExchange sends data to volume reserved by another system, an OS
system error can occur. The “retry reserved-volume function” can retry to
send data to the reserved volume by specifying wait time and retry count in an
environment variable. FileExchange can resend the data when the reserved
volume is released by the other system.

Supported OS and OS Versions

Table 2-8 shows the supported OS and OS versions. HP-UX does not issue the
reserve function, because HP-UX does not have a system error when it
accesses a reserved-volume, and device driver of HP-UX retries to access the
reserved-volume.

Contact HDS technical support for OS/OS versions not listed below.

About Cross-OS File Exchange Operations 2-33

Hitachi Cross-OS File Exchange User’s Guide

 Table 2-8 OS Version Support for the Retry Reserved-Volume Function
OS OS Version FX Version

AIX 4.3.3ML02(32/64), 5.1ML02(32/64), 01-XX-62 and later (XX=03,04)*1

5.2 ML02(32/64), 6.1TL01(32/64)*3

Tru64 UNIX V5.1a (32) 01-XX-63 and later (XX=03,04)*1

Solaris 8 (32/64), 9 (32/64), 10 (32/64)

Linux Red Hat AS3.0 Update3(32) (x86)(AMD64/Intel64)

AS3.0 Update4(64) (IA64)
AS4.0 Update5(32) (x86)(AMD64/Intel64)*2
AS4.0 Update5(64) (IA64)*2
AS5.1(32) (x86)(AMD64/Intel64)*2
AS5.1(64) (IA64)*2
AS5.2(32) x86, AMD64/Intel64
AS5.2(64) IA64
AS5.3(32) x86,AMD64/Intel64
AS5.3(64) IA64

SuSE SLES9(32) (x86) (IA64) (AMD64/Intel64) 01-04-64/20 and later*1

SLES9(64) IA64
SLES10(32) x86,AMD64/EM64T
SLES10(64) IA64
SLES11(32) x86,AMD64/EM64T
SLES11(64) IA64

HP-UX 11.11 [2002/06](32/64), 01-XX-64/25 and later

11.23 [2004/09][2005/04](64) (XX=03,04)*1

Windows NT 4.0 SP6(x86), 2000 Server SP4(x86), 01-XX-64/23 and later

Server 2003 SP1(x86)(IA64)(AMD64/Intel64) (XX=03,04)*1
Server 2008 (x86)(IA64) (AMD64/Intel64)*4
Server 2008 R2 (64bit) for Itanium
Server 2008 R2 (64bit) for AMD64/Intel64

*1:If your FAL/FCU is version XX=03 or 04 and you are already using Retry reserved-volume function,
you can use XX ≥ 05 compatibly.
*2:AS4.0 U5 and later, AS5.1, AS5.2, AS5.3, SLES10, and SLES11 supported in the case of File
Exchange when the version is 01-XX-66/26 and later (XX ≥ 05).
*3:AIX6.1 supported in the case of File Exchange when the version is 01-XX-65/25(XX ≥ 03) and later
and 01-XX-66/25(XX ≥ 05) and later.
*4:Windows Server 2008 and Windows Server 2008 R2 supported in the case of File Exchange when
the version is 01-XX-66/24 and later (XX ≥ 05).

2-34 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

AIX Reserve Retry Function
Table 2-9 shows the AIX reserve retry function.

Table 2-9 AIX Reserve Retry Function

Environment Variable or Function Description

FAL_RETRY Set the retry function by specifying the environment variable.

FAL_RETRY_COUNT Set the retry count for FX to send data during reserved status
by specifying the environment variable.

FAL_RETRY_WAIT_TIME Set the interval for FX to send data during reserved status by
specifying the environment variable.

FAL_RETRY_TARGET Set the system error codes that trigger a retry by specifying the
environment variable.

Retry function Retry is executed when an AIX system error triggers retry.

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

Specifying the Environment Variables for the Retry Function

FAL_RETRY. You can set the retry function by specifying the environment
variable (FAL_RETRY). Table 2-10 shows the relationship between the
environment variable (FAL_RETRY) and enable/disable.

Table 2-10 FAL_RETRY Environment Variable

FAL_RETRY Retry Counts

No definition of environment variable Disable Retry function

ON Enable Retry function

OFF Disable Retry function

other Disable Retry function

FAL_RETRY_COUNT. You can set the number of times that FileExchange

tries to resend data during reserved status by specifying the environment
variable (FAL_RETRY_COUNT). Table 2-11 shows the relationship between the
environment variable (FAL_RETRY_COUNT) and retry counts.

Table 2-11 FAL_RETRY_COUNT Environment Variable

FAL_RETRY_COUNT Retry Counts

No definition of environment variable 10

1-600 User-specified value.

Others 10

About Cross-OS File Exchange Operations 2-35

Hitachi Cross-OS File Exchange User’s Guide

 FAL_RETRY_WAIT_TIME. You can set the time that FileExchange waits
before resending data during reserved status by specifying the environment
variable (FAL_RETRY_WAIT_TIME). Table 2-12 shows the relationship between
the environment variable (FAL_RETRY_WAIT_TIME) and the interval of retry.

Table 2-12 FAL_RETRY_WAIT_TIME Environment Variable

FAL_RETRY_WAIT_TIME Interval of Retry

No definition of environment variable 1 sec

1-60 User-specified value.

Others 1 sec

FAL_RETRY_TARGET. You can set up to five system error codes to trigger

the retry function by secifying the environment variable(FAL_RETRY_TARGET).
If you set six or more error codes, FX ignores entries after the fifth entry.

Table 2-13 shows the relationship between the environment variable

(FAL_RETRY_TARGET) and system error code.

Caution: OS error codes returned in case of reservation conflict may vary

depending on the host environment such as OS or HBA driver, the timing of
the conflict, etc. You should do adequate testing before determining any non-
default error codes as triggers for the retry function. In case of specifying
system error other than the default value, contact HDS technical support.

Table 2-13 FAL_RETRY_TARGET Environment Variable

FAL_RETRY_TARGET System Error Codes That Trigger Retry Notes

No definition of AIX 16(EBUSY) -

environment variable
Tru64 5(EIO)

Solaris

Linux

HP-UX 22(EINVAL)
13(EACCES)

Windows 170(ERROR_BUSY)

System error, system You can set up to five system error codes 16(EBUSY), 5(EIO),
error, system error, using a comma ‘,’ to separate the error codes. 22(EINVAL), 13(EACCES),
system error… 170(ERROR_BUSY) already
included in each OS.

Other No definition of environment variable -

2-36 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Output Retry Log Function
FileExchange outputs retry log in FAL_Error log file when retry is executed.
Figure 2-22 shows the retry-log format.

Mon Nov 8 16:21:23 2004 : root : err=16 open Retry(1) at 12345 : 01-03-58/21 PID=1234 VSN:DSN
*1 *2 *3 *4 *5 *6 *7 *8 *9

*1 data
*2 user name
*3 system error code
*4 function (open, close, read, write, seek, or flush)
*5 retry counts
*6 number of source code line
*7 version
*8 process ID
*9 target dataset

Figure 2-22 Retry Log

Errors
Table 2-14 shows about error of this function.

Table 2-14 Errors for Retry Function

Error
Code Error Name Error Message Description Note

16 EBUSY Resource busy It will open the reserved volume. Only AIX

5 EIO I/O error Not use the volume -

22 EINVAL Invalid argument Input error Only HP

13 EACCES Permission denied Cannot access the volume

170 ERROR_BUSY The requested The requested resource is being Only Windows
resource is in use. used.

About Cross-OS File Exchange Operations 2-37

Hitachi Cross-OS File Exchange User’s Guide

Get Detail Traces Function
The get detail traces function enables you to get file size and time-date
information while FileExchange sends a file. This function also makes a copy
file before FileExchange sends its file and can get data and information when a
FileExchange otm error occurs (FCU_ERROR –363).
• Table 2-15 shows the FileExchange version support for the get detail traces
function.
• Table 2-16 shows the get detail traces functions.
• Table 2-17 shows the required disk space for getting traces.
• Table 2-18 shows the files to get when a FileExchange error occurs.

Note: This function does not work when FileExchange sends file from
FileExchange volume to open server.

Table 2-15 FX Version Support for the Get Detail Traces Function
Software OS Version FX Version

FAL for AIX (32/64bit) Same OS versions that 01-XX-63 and later (XX ≥ 03)
FileExchange supports.
FAL for Tru64 (32/64bit)

FAL for Solaris (32/64bit)

FAL for Linux (32/64bit)

FAL for HP-UX (32/64bit)

Table 2-16 Get Detail Traces Functions

Function (Environment Variable) Description See
Section:

Check sending file Compare files that FileExchange sends before (1)
(FCU_E363_TRACE_MODE) and after using this environment variable.

Set mode of making copy files before Make copy file before FileExchange sends using (2)
sending (FAL_E363_TRACE_COPY_FILE) this environment variable.

Set name of traces Set file-name of traces using this environment (3)
(FCU_E363_TRACE_LOG) variable.

Make copy file after getting information Make copy file after File Exchange gets file- (4)
information using this environment variable.

Check information of sending file Compare information of file that FileExchange (5)
sends before and after.

Output traces of record size Get traces of record size while FileExchange (6)
sends files.

Output traces (FCU_Error occurred) Get traces of sending file information and make (7)
copy file.

Output core dump Make core dump when FileExchange could not (8)
make traces.

2-38 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Table 2-17 Disk Space for Getting Traces
Content Disk Space of Directory

For copying sending files More than sending files space.

For copying core files About 15 MB.

For copying traces Calculate disk space using the following formula:
100 KB + (number of record sending file × 2 Byte)

Table 2-18 Files to Get in case an Error Occurs

Content Directory

Trace Current directory of FCU: directory set by the environment variable

(FCU_E363_TRACE_LOG).

Sending file Same directory as sending file.

Core dump Current directory of FCU.

FAL_ERROR (current) /tmp, directory set by the environment variable (ERR_LOG_FILE).

FAL_ERROR(back up)

FAL_DUMP(current) /tmp, directory set by the environment variable (ERR_DUMP_FILE).

FAL_DUMP(back up)

Parameter of sending file --

LISTVOL of target volume --

About Cross-OS File Exchange Operations 2-39

Hitachi Cross-OS File Exchange User’s Guide

(1) Check Sending File
You can compare files that FileExchange sends before and after by specifying
the environment variable (FCU_E363_TRACE_MODE). Table 2-19 shows the
relationship between the environment variable (FCU_E363_TRACE_MODE) and
check mode.

Table 2-19 Check Sending File (FCU_E363_TRACE_MODE)

FCU_E363_TRACE_MODE Check Mode

No definition of environment variable Compares files that FileExchange sends before and after. If
each file is different data, FileExchange error FCU_ERROR(-363)
occurs after sending files.

ON Compares sending files and records that FileExchange sends

before and after. If each file is different data, FileExchange
error FCU_ERROR(-363) occurs then.

Other Same as no definition of environment variable.

(2) Set Mode of Making Copy Files

You can make copy files before FileExchange sends by specifying the
environment variable (FCU_E363_TRACE_COPY_FILE). Table 2-20 shows the
relationship between the environment variable
(FCU_E363_TRACE_COPY_FILE) and copy mode.

Table 2-20 Set Mode of Making Copy Files (FCU_E363_TRACE_COPY_FILE)

FCU_E363_TRACE_COPY_FILE Copy Mode

No definition of environment variable Does not make copy files before FileExchange sends files from
open server to FileExchange volume.

ON Makes copy files before FileExchange sends files from open

server to FileExchange volume.

Other Same as no definition of environment variable.

2-40 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

(3) Set Name of Traces
You can set file name of traces by specifying the environment variable
(FCU_E363_TRACE_LOG). Table 2-21 shows the relationship between the
environment variable (FCU_E363_TRACE_LOG) and the trace file name format.

Table 2-21 Set Name of Traces (FCU_E363_TRACE_LOG)

FCU_E363_TRACE_ LOG Trace File Name Format

No definition of environment variable Current directory of FileExchange + “FCU_E363” + traces

getting time-date (yymmddHHMMSS) + process ID of
FileExchange + “.log”

ON Unique file name + “.” + traces getting time-date

(yymmddHHMMSS) + process ID of FileExchange + “.log”

Other Same as no definition of environment variable.

(4) Make Copy Files After Getting Information

When environment variable (FAL_E363_TRACE_LOG) is set to ‘ON’, you can
make copy files after FileExchange gets file-information. If FileExchange error
FCU_ERROR(-363) does not occur, it will delete this file-information. Table
2-22 shows the file name format when FileExchange copies it.

Table 2-22 Make Copy Files After Getting Information

File Name Format

Sending file name + “.” + traces getting time-date (yymmddHHMMSS) + process ID of FileExchange
+ “.cpy”

(5) Check Information of Sending Files

When environment variable (FCU_E363_TRACE_MODE) is not set to ‘ON’, you
can compare information of files (i-node number, file size, file modified) that
FileExchange sends before and after. If FileExchange found a difference of
data, error FCU_ERROR(-363) occurs after sending the file.

When environment variable (FCU_E363_TRACE_MODE) is set to ‘ON’, you can

compare information of files (i-node number, file size, file modified) while
FileExchange sends files. If FileExchange found a difference of data, error
FCU_ERROR(-363) occurs then.

(6) Output Traces of Record Size

You can record size while File Exchange sends files. If FileExchange error
FCU_ERROR(-363) does not occur, it will delete this file-information.

About Cross-OS File Exchange Operations 2-41

Hitachi Cross-OS File Exchange User’s Guide

(7) Output Traces (FCU Error Occurred)
When FileExchange error FCU_ERROR(-363) occurs, you can get traces of
sending file information (start sending file time, error time, file information)
and make copy files. Table 2-23 shows the file name format when
FileExchange copies it.

Table 2-23 Output Traces

File Name Format

Sending file name + “.” + traces getting time-date (yymmddHHMMSS) + process ID of FileExchange
+ “.end.cpy”

(8) Output Core Dump

When FileExchange is not able to make traces and error FCU_ERROR(-363)
occurs, you can make a core dump. You need to set the core dump size to
“ulimit –c unlimited” to use this function.

2-42 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Interval Function for OtM Transfer Completion (Linux)
The interval function for OtM transfer completion provides to wait for the
completion of OtM transfer for specified time (seconds) when OtM transfer by
using File Exchange (Linux version) completes normally. The interval is
specified by the environment variable (FCU_OTM_INTERVAL). If an error
occurs, File Exchange ends abnormally without taking an interval.

In case of accessing a dataset from the mainframe system immediately after

the File Exchange OtM operation to the mainframe dataset completes, you
should take interval with this function between OtM process and mainframe
I/O process. Regarding multiple transfer by parameter file, each OtM transfer
has an interval based on the specified environment variable
(FCU_OTM_INTERVAL). This function does not apply to MtO transfer.

Table 2-24 shows the Linux platform support for the interval function. Table
2-25 lists the interval functions for OtM transfer completion.

Table 2-24 Platform Support for the Interval Function for OtM Transfer
Linux Platform OS File Exchange FAL/FCU Notes

Red Hat 7.2 (32bit) 32bit version ƒ 32bit version supports only x86
cpu architecture (7.2, AS2.1).
AS2.1 (32bit)
AS3.0 ƒ 32bit version supports x86
(32bit) and AMD64/Intel64
AS4.0 (64bit) cpu architecture (AS3.0
AS5.1 and later).

AS5.2 ƒ 64bit version supports only

Itanium cpu architecture.
AS5.3

AS2.1 (64bit) 64bit version (IA64 AS2.1)

AS3.0 (64bit) 64bit version (IA64 AS3.0)

AS4.0 (64bit)
AS5.1 (64bit)
AS5.2 (64bit)
AS5.3 (64bit)

SuSE SLES9 32bit version ƒ 32bit version supports

x86(32bit) and AMD64/Intel64
SLES10
(64bit) cpu architecture.
SLES11
ƒ 64bit version supports only
SLES9 (64bit) 64bit version (IA64 AS3.0) Itanium cpu architecture.
SLES10 (64bit)
SLES11(64bit)

* AS4.0 U5 and later, AS5.1, AS5.2, AS5.3, SLES10, and SLES11 are supported by FX version 01-XX-
66/26 (XX≥05) and later.

About Cross-OS File Exchange Operations 2-43

Hitachi Cross-OS File Exchange User’s Guide

 Table 2-25 Interval Functions for OtM Transfer Completion
Target Function Content

FCU Set interval time Set interval time using environment variable
(FCU_OTM_INTERVAL).

Completion interval Complete OtM transfer after File Exchange wait for an interval
time specified by environment variable (FCU_OTM_INTERVAL).

Display interval condition Display progress of interval time.

Environment Variable for Interval Time

You can specify an interval time after OtM transfer completes by setting
environment variable (FCU_OTM_INTERVAL). Table 2-26 shows the
relationship between the environment variable (FCU_OTM_INTERVAL) and
interval time.

Table 2-26 Relationship between FCU_OTM_INTERVAL and Interval Time

FCU_OTM_INTERVAL Interval time

No definition The interval function is not available. OtM transfer completes

immediately.

Value between 60 and 600 (seconds) OtM transfer completes after a specified interval time passes
on.

Other value The interval function is not available. OtM transfer completes
immediately.

Display Window for Interval Function

The interval function for OtM transfer completion displays interval processing.
Figure 2-23 shows an example of its display window.

# fcunw -nc -P otm a.dat VSN:DSN EA No LF

otm a.dat VSN:DSN EA No LF Emp=No RDW=No VSE=No PIPE=No
Now checking ...
Start
Processing ( 40%)
Processing ( 80%)
OTM Interval ...
Complete
#

Figure 2-23 Display Window for the Interval Function

2-44 About Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

 3
Preparing for Cross-OS File Exchange
Operations
This chapter describes the system and volume configuration requirements to
run and operate FX. It also provides instructions on how to install FX.
System Requirements
Installing and Configuring the FX Volumes
Installing the FX Software
Entering the FX License Key Code
Creating FXoto Volumes Using the FMT Utility
Creating the FX Volume Definition File(s)
Verifying Mainframe Dataset Requirements
Allocating FXoto Intermediate Datasets

Preparing for Cross-OS File Exchange Operations 3-1

Hitachi 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
Hitachi RAID storage systems configuration. This is due to the possible need to
reconfigure and reformat entire array groups, depending on the microcode
level of the storage system.

The system requirements for FX are:

• FX software for the applicable open-system platform(s). This revision of the
Cross-OS File Exchange User’s Guide covers FX software versions 01-XX-6x
and later. For information on earlier versions, please refer to previous
revisions of this document.
– FX supports files larger than 2 GB.
– When installing/uninstalling FX (for 32/64bit), follow the procedure
presented in this Chapter. For 64bit installation, the FX program must
be version 01-XX-59 or later.
• Hitachi RAID storage systems:
– FXmto: the Hitachi RAID storage systems must be configured with -B
and/or -A FX volumes.
– FXotm: the Hitachi RAID storage systems 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.
– Table 3-1 specifies the FX version support for the Hitachi RAID storage
system models.

Table 3-1 FX Version Support for Hitachi RAID Storage Systems

Hitachi RAID Storage System FX (32bit) Version FX (64bit) Version

Virtual Storage Platform 01-06-67 and later 01-06-67 and later

Universal Storage Platform V/VM 01-05-66 and later 01-05-66 and later

TagmaStore USP/NSC 01-04-61 and later 01-04-61 and later

Lightning 9900V 01-03-53 and later 01-03-59 and later

Lightning 9900 01-02-46 and later None.

• Storage Navigator and LUN Manager software. LUN Manager enables the
user to configure FC ports and create custom-size LUs. For information on
LUN Manager, refer to the LUN Manager User’s Guide for the storage
system.
• Mainframe operating systems: z/OS, S/390, MVS, z/VSE
– 2107, 2105, and 3990 control unit (CU) emulations are supported.

3-2 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

• Open-system platforms and operating system (OS) version level(s):
– Table 3-2 specifies the OS version support for FX (32bit).
– Table 3-3 specifies the OS version support for FX (64bit)
– Superuser (root) login access to the open-system server/workstation is
required.

Note: For 64bit FAL, set HBA that supports 64bit into the server. In AIX,
use an IBM product.

Preparing for Cross-OS File Exchange Operations 3-3

Hitachi Cross-OS File Exchange User’s Guide

 Table 3-2 OS Version Support for 32bit FX
Host OS Array CPU OS bit OS Version

HP-UX VSP PA-RISC 32 10.20(*6), 11.0, 11.11

USP V/VM
USP/NSC PA-RISC 64 11.0, 11.11
Lightning 9900V IA64 64 11.23, 11.31

Lightning 9900 PA-RISC 32 10.20, 11.0, 11.11

64 11.0, 11.11

AIX VSP Power PC 32 4.33(*6), 5.1, 5.2, 5.3, 6.1(*3)

USP V/VM
USP/NSC 64 4.33(*6), 5.1, 5.2, 5.3, 6.1(*3)
Lightning 9900V
Lightning 9900(*4)

Solaris VSP UltraSPARC 32 2.6(*6), 7(*6), 8, 9,10

USP V/VM
USP/NSC 64 7(*6), 8, 9,10
Lightning 9900V
Lightning 9900

Red Hat VSP x86 32 7.2(*6), AS2.1, AS3.0(*1),

Linux USP V/VM AS4.0 U5 and later(*2), AS5.1(*2)
USP/NSC AS5.2(*2),AS5.3(*2)
Lightning 9900V
AMD64/Intel64 64 AS3.0(*1), AS4.0 U5 and later(*2)
AS5.1(*2), AS5.2(*2), AS5.3(*2)

SuSE Linux VSP x86 32 SLES9,SLES10(*2), SLES11(*2)

USP V/VM
USP/NSC
Lightning 9900V

Lightning 9900 AMD64/Intel64 64

Tru64 USP V/VM AlphaChip 32 V5.1a

USP/NSC
Lightning 9900V

Lightning 9900 V4.0, V5.0, V5.0a, V5.1a

HI- USP V series PA-RISC 32 07-45, 07-50
UX/WE2(*6) USP series
Lightning
- 9900V series
Lightning 07-35, 07-40
- 9900 series IA64 64 Windows Server 2003
Windows Server 2008 (*5)
AMD64/Intel64 Windows Server 2008 R2 (*5)

Lightning 9900 x86 32 Windows NT 4.0 Server (SP6)

Windows 2000 Server (SP1 and later)

*1: 01-03-60 and later support.

*2: 01-XX-66/26 (XX ≥ 05) and later support.
*3: 01-XX-65/25 (XX ≥ 03) and later and 01-XX-66/25 (XX ≥ 05) and later support.
*4: Lightning 9900 is not supported in AIX 6.1 server.
*5: 01-XX-66/24 and later (XX ≥ 05) support.
*6: VSP is not supported on this server.

3-4 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Table 3-3 OS Version Support for 64bit FX
OS Array CPU OS bit Version

HP-UX VSP PA-RISC 64 11.0, 11.11

USP V/VM
USP/NSC IA64 11.23, 11.31

Solaris Lightning 9900V Ultra SPARC 7(*4), 8, 9, 10

Lightning 9900

AIX Power PC 4.33(*4), 5.1, 5.2 , 5.3, 6.1(*2)

Linux IA64 AS2.1, AS3.0,

AS4.0 U5 and later(*1)
AS5.1(*1)
AS5.2(*1), AS5.3(*1)
AS5.2(IA64)(*1)
AS5.3(IA64)(*1)

SLES9, SLES10(*1), SLES11(*1)

Windows IA64 Server 2003

Server 2008(*3)
Server 2008 R2(*3)

AMD64/Intel64 Server 2003

Server 2008(*3)
Server 2008 R2(*3)

*1:01-XX-66/26 and later (XX ≥ 05) support.

*2:01-XX-65/25 (XX ≥ 03) and later and 01-XX-66/25 (XX ≥ 05) and later support.
*3:01-XX-66/24 and later (XX ≥ 05) support.
*6: VSP is not supported on this server.

Preparing for Cross-OS File Exchange Operations 3-5

Hitachi 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. The 64-bit version FCU does not support a GUI
interface (Windows version supports GUI).

Table 3-4 FX Version Support for OS Platforms

File Exchange Version Supported OS

01-03-59/20 Solaris, HP-UX (PA-RISC), AIX 4.3, AIX 5L

01-04-61/20

01-xx-62/20 (xx ≥ 03) Red Hat Linux AS3.0 (IA64)

01-xx-63/20 (xx ≥ 03) Red Hat Linux AS2.1, HP-UX 11iv2 (IA64)

01-xx-66/21 (xx ≥ 05) Windows Server 2003 (IA64, AMD64/Intel64)

01-xx-65/25 (xx ≥ 03) AIX 6.1

01-xx-66/25 (xx ≥ 05)

01-xx-66/26 (xx ≥ 05) Red Hat Linux AS4.0 (IA64)*1

Red Hat Linux AS5.1 (IA64)
Redhat Linux AS5.2 (IA64)
Redhat Linux AS5.3 (IA64)
SUSE Linux Enterprise Server 10
SUSE Linux Enterprise Server 11

01-xx-66/24 (xx ≥ 05) Windows Server 2008 (IA64, AMD64/Intel64)

Windows Server 2008 R2 (IA64,
AMD64/Intel64)

*1: Red Hat Linux AS4.0 Update5 and later support.

VSE Requirements and Restrictions

FX supports the VSE operating system. The following sections describe the
supported VSE versions that correspond to the Hitachi RAID storage systems
and associated FX version.

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

Table 3-5 Support and OS Conditions

OS Version Hitachi RAID Storage System FX Version

VSE 2.5 and later TagmaStore USP/NSC and later 01-03-59 and later

When you use MTO and OTM for the dataset allocated by VSE 2.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 VSE 2.5, FX can
transfer data without a VSE parameter.

3-6 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Table 3-6 Support Matrix for VSE OS, VSE Parameter and Record Format
OS and FX Version VSE Record Format
Parameter F FB V VB

VSE 2.3 and earlier Yes Available Available Available Available

(FX 01-xx-58 & earlier) No Not available Not available Not available Not available

VSE 2.5 and later Yes Available Available Available *1 Available *2

(FX 01-03-59 & later) No Available Available Available *3 Available *4

Legend:
F: Fixed non block length
FB: Fixed block length
V: Variable non block length
VB: Variable block length

*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
#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

*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

*3 It is possible to transfer data between correct dataset attributes (BL＝RL+4≦32760). The data
transfer is invalid if RL and BL values on VTOC do not match the following condition:
BL＝RL+4≦32760
In case RL and BL values on VTOC are RL > 32756 and BL > 32760, FileExchange manages data
as RL=32756 and BL=32760.
In case RL and BL values on VTOC are RL≦32756, BL≦32760, and RL = BL, FileExchange
manages data as follows:
RL(FileExchange internal value) = RL(value on VTOC) + 4 ≦32756
BL(FileExchange internal value) = BL(value on VTOC) + 8 ≦32760

*4 It is possible to transfer data between correct dataset attributes (BL＝RL+4≦32760). The data
transfer is invalid if RL and BL values on VTOC do not match the following condition:
BL＝RL+4≦32760
In case RL and BL values on VTOC are RL＝BL≦32752, FileExchange manages data as follows:
RL(FileExchange internal value) = RL(value on VTOC) + 4
BL(FileExchange internal value) = BL(value on VTOC) + 8

Preparing for Cross-OS File Exchange Operations 3-7

Hitachi Cross-OS File Exchange User’s Guide

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

Table 3-7 Platforms and Associated Operating Systems

Operating System/Platform Compiler

Red Hat Linux 7.2 (Kernel version 2.4.7-10) gcc (Ver. 2.96 20000731 (Red Hat Linux 7.1 2.96-98))
glibc (Ver. 2.2.4-13)

Red Hat Linux AS2.1 (64bit) (Kernel gcc (Ver. 2.96 20000731 (Red Hat Linux 7.2 2.96-
version 2.4.18-e.31) 118.7.2))
glibc (Ver. 2.2.4-32.3)

Red Hat Linux AS3.0 (64bit) (Kernel gcc (Ver. 3.2.3 20030502 (Red Hat Linux 3.2.3-20))
version 2.4.21-9.0.1.EL)
glibc (Ver. 2.3.2-95.3)

Solaris 2.6 Work Shop Compilers 4.2.1

Solaris 7 Work Shop Compilers 5.0

Windows NT 4.0 service Pack 6a Visual C++ 6.0 SP6

Windows (64bit) for Itanium Microsoft Platform SDK for Windows Server 2003 SP1

Windows (64bit) for x64 Visual C++ 2005

HP-UX 10.20 HP 92453-01 A.10.32.03 HP C Compiler

HP-UX 11.0 (64bit) HP 92453-01 A.11.01.00 HP C Compiler

HP-UX 11iv2 (64bit) HP aC++/ANSI C B3910B A.05.52 [Sep 05 2003]

AIX 4.3 C for AIX 4.4

AIX 5L (64bit) C for AIX, Version 5.0

Tru64 01-XX-59 and earlier:

ƒ Digital UNIX Compiler Driver 3.11
ƒ DEC C V5.6-075 on Digital UNIX V4.0 (Rev. 878)
01-XX-60 and later:
ƒ Digital UNIX Compiler Driver 3.11
ƒ DEC C V5.9-005 on Digital UNIX V4.0 (Rev. 1229)

3-8 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Maximum Data Size
Table 3-8 describes the maximum data sizes for FX version 01-02-48 or later.

Table 3-8 Maximum Data Size

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 OS limits:

HP-UX, Solaris, NT, Tru64: 78 GB
AIX: 64 GB

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

AIX: 64 GB (limit of OS)

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

AIX: 64 GB (limit of OS)

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

Additional Notes:
• 3390-9A: Can be used for both FXmto and FXotm. 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 FXmto. 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 FXotm. 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 FXmto and FXotm. 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 FXmto. 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 FXotm. The same access as for 3390-L is
allowed but read only from Mainframe hosts. Read and write are possible
from Open system hosts.

Preparing for Cross-OS File Exchange Operations 3-9

Hitachi Cross-OS File Exchange User’s Guide

 • Emulation type -C volumes can be read from Mainframe hosts but not
written to. However, read and write operations are possible to –C type
volumes from Open system hosts.
• When initializing -C volumes, use quick initialization which formats only 1
cylinder on the top of the volume.

Interoperability with HDLM

When FX is used with HDLM, the FX version must be 01-03-56 or later. The
appropriate support platform versions are shown in Table 3-9. Please refer to
the Hitachi Dynamic Link Manager (HDLM) User's Guide for the host platform
(see Referenced Documents) for details on each platform.

Table 3-9 HDLM Platforms and HDLM Versions

Platform HDLM Version

Windows 04-01, 05-00-/B

AIX 05-00-/A, 05-01

HP-UX 04-00-/A

Solaris 04-01, 05-00

3-10 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Installing and Configuring the FX Volumes
The FX volumes are installed and configured during Hitachi RAID storage
systems 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 mainframe data to be
transferred to open-system LUs. The FXotm volumes (-C and -A) contain
open-system data to be transferred to mainframe 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
mainframe 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 Hitachi RAID storage systems 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 storage system installation may require reformatting entire array
groups, depending on the microcode level of the system.
2. Complete Hitachi RAID storage system installation and device configuration
as specified in the Configuration Guide for the open-system platform (e.g.,
HP-UX Configuration Guide).
– 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 FX (no mount operation).
– Defining RAW Devices. The OPEN-x volumes that are to be used as
intermediate volumes and shared between open-systems must be
defined as “raw” devices from each host server. From the open
systems, there is no way to distinguish OPEN-x open-system dedicated
volumes from FX volumes. Make sure not to confuse the usage on those
volumes in the host systems.
• The operations below that 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

Preparing for Cross-OS File Exchange Operations 3-11

Hitachi Cross-OS File Exchange User’s Guide

 – IBM AIX: creating a volume group
– Windows: formatting and creating a file system
– Digital UNIX/HP Tru64 UNIX: “newfs” command
– SequeNT DYNIX/ptx®: creating a file system
– NCR® SVR4: creating a volume group
– 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 host Configuration Guide.
– Partition size. Make sure to specify the correct partition size for the FX
volumes as specified in the applicable host 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.

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

3-12 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Table 3-10 Partition Sizes for Hitachi RAID Storage Systems
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

Note 1: For further information on Solaris cylinder partition sizes, refer to the
LUN Expansion User's Guide, Virtual LVI/LUN User's Guide, and Sun Solaris
Configuration Guide for the storage system.

Preparing for Cross-OS File Exchange Operations 3-13

Hitachi Cross-OS File Exchange User’s Guide

 Volume labels. An FX volume with a volume label cannot be shared
between open-system platforms which use volume labels. Table 3-10
shows the allowable configurations for sharing FX volumes between
open-system platforms for the Hitachi RAID storage systems. Table 3-11
shows the allowable configurations for sharing FX volumes between
open-system platforms for the Hitachi RAID storage systems. 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, 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, Tru64, Windows) 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
Access to shared volumes is given only to “root”.
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, Administrator access is required to access the FX volumes.
4. On the mainframe host, make sure to initialize and write the VTOC for each
FXmto and FXotm volume to enable the mainframe host to access the
volumes. The ICKDSF media maintenance utility can be used to perform
these tasks.
5. After FX software installation, make sure to format each FXoto volume
using the FX Formatter (FMT) utility on the UNIX/ Windows host. This
enables the FXoto intermediate datasets to be allocated.

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

IBM AIX HP-UX Sequent Windows Tru64 Solaris NCR Linux
Dynix SVR4

Non-label IBM AIX OK OK OK OK OK OK OK OK

HP-UX OK OK OK OK OK OK OK OK

Sequent Dynix OK OK OK OK OK OK OK OK

Linux OK OK OK OK OK OK OK OK

Label write Windows OK OK OK CHK OK CHK CHK OK

option
Tru64 OK OK OK OK CHK CHK CHK OK

Label Solaris OK OK OK OK OK OK NG OK
auto-write
NCR SVR4 OK OK OK OK OK NG NG OK

CHK = sharing allowed only if volume has no label.

3-14 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Installing the FX Software
The FX software must be installed on the open-system server(s) attached to
the storage system. FX software installation for the UNIX-based platforms is
different from FX installation on Windows hosts. The following sections provide
instructions for installing FX version 01-02-4x and later. For instructions on
installing earlier versions, please refer to previous revisions of this document.

Installing FX on UNIX-Based Platforms

32-Bit FX Software

To install the 32-bit FX software on a UNIX-based platform:

1. If FX version 01-01-36 or later is installed (by the cpio command), you do
not need to uninstall it. A new installation will overwrite the previous
version.
If FX version 01-01-24 or earlier is installed (by the setup program), you
must uninstall this older version as follows before installing version
01-02-4x or later:
a. Log in with the same user ID that was used to install the old FX
software.
b. If FX was installed from FD using the setup program, see Uninstallation
to remove FX.
c. If FX was installed from DAT, or if you can’t find your FX installation FD,
move to the directory fcu/fal.o/dataset.h and remove FX 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 FX 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.
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.

Preparing for Cross-OS File Exchange Operations 3-15

Hitachi Cross-OS File Exchange User’s Guide

 6. For UNIX-based systems, copy the FX 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.
7. For Solaris you must set a path to the resource file for each FX 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:$XFILESEA
RCHPATH
export XFILESEARCHPATH
c. You must log out and log back in to implement these changes.
8. For Tru64 UNIX you must uncompress the FX 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.

64-Bit FX Software

To install the 64-bit FX software on a UNIX-based platform:

1. Log-in as "root".
2. Set CD-ROM, in which the 64-bit FX 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

3-16 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

 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:
Install 64bitFAL after confirming a directory name and a file name by using
the ls command.
– HP-UX 11.0 PA-RISC:
#cpio -iBmuv <(MountPoint)/PROGRAM/FAL64/HP_UX/HP_UX.CPI
– HP-UX 11iV2 PA-RISC:
#cpio -iBmuv <(MountPoint)/PROGRAM/FAL64/HP_UX/PA/HP_UX.CPI
– HP-UX Itanium:
#cpio -iBmuv <(MountPoint)/PROGRAM/FAL64/HP_UX/IA/HP_UX.CPI
– Solaris (Solaris 7, 8, 9, 10):
#cpio -iBmuv (MountPoint)/PROGRAM/FAL64/SOLARIS/SOLARIS.CPI
– AIX 4.3.3:
#cpio -iBmuv <(MountPoint)/PROGRAM/FAL64/AIX/AIX4/AIX.CPI
– AIX 5.x, AIX 6.x
#cpio -iBmuv <(MountPoint)/PROGRAM/FAL64/AIX/AIX5/AIX.CPI
– Red Hat Linux AS2.1:
#cpio -iBmuv <(MountPoint)/PROGRAM/FAL64/LINUX/AS2/LINUX.CPI
– Red Hat Linux AS3.0/IA64, AS4.0, AS5.1, AS5.2, AS5.3, SuSE:
#cpio -iBmuv <(MountPoint)/PROGRAM/FAL64/LINUX/LINUX.CPI
8. Remove the CD-ROM from the drive.
9. Log-out once and log-in again

Installing FX on Windows
To install the FX software on a Windows host:
1. If FX is already installed, uninstall it before installing the new version.
a. To uninstall FX version 01-01-25 or later, use the Windows
Add/Remove Programs utility.
b. To uninstall FX versions 01-01-24 and earlier, delete the folder that
contains the FX software components (fcu.exe, fal.obj, and
dataset.h).
2. Insert the FX installation CD-ROM into the drive, and run setup.exe.

Note: For Windows, 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-17

Hitachi Cross-OS File Exchange User’s Guide

Uninstalling the FX Software on UNIX-Based Platforms
To uninstall FX version 01-01-36 or later:
1. Log in to the system as root.
2. Remove the FX for 32bit files using the rm command as follows, or string
the commands:
# rm /usr/bin/fcu (not applicable to Linux)
# rm /usr/bin/fcunw
# rm /usr/include/dataset.h
# rm /usr/lib/libfal.*
# rm /usr/lib/libfalmt.a (for 01-XX-59/20 and later on AIX)
# rm /usr/lib/libuoc.*
# rm /usr/lib/X11/app-defaults/FcuMf
# rm /usr/bin/mfformat
# rm /usr/bin/allocds
3. Remove the FX 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.* (for AIX and Linux)
# rm /usr/lib/pa20_64/libfal64.sl (for HP-UX PA-RISC)
# rm /usr/lib/hpux64/libfal64.so (for HP-UX IA64)
# rm /usr/lib/sparcv9/libfal64.so.1 (for Solaris)
# rm /usr/lib/libuoc64.*
# rm /usr/bin/mfformat64
# rm /usr/bin/allocds64
When uninstalling FX version 01-01-41 and later, remove the following file:
# rm /usr/bin/listvol (32bit)
# rm /usr/bin/listvol64 (64bit)
When uninstalling FX for Lightning 9900V, TagmaStore USP/NSC, USP
V/VM, or VSP, remove the following files:
# rm /usr/bin/ppkeyset (32bit)
# rm /usr/bin/ppkeyset64 (64bit)
# rm /usr/bin/autoppkeyset (32bit)
# rm /usr/bin/autoppkeyset64 (64bit)

3-18 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Uninstalling FX on Windows
To uninstall the FX software on a Windows host, depending on your version of
FX, do one of the following:
• To uninstall FX version 01-01-25 or later, use the Windows Add/Remove
Programs utility.
• To uninstall FX version 01-01-24 or earlier, delete the folder that contains
the FX software components (fcu.exe, fal.obj, and dataset.h).

Note: For Windows, 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 Cross-OS File Exchange User’s Guide

Updating or uninstalling the FAL version when using File Exchange
Code Converter
Before updating only the FAL version, copy the File Exchange Code Converter
library (UNIX: /usr/lib/libuoc.*, Windows: target directory\uoc.dll) using an
alias. Then, after uninstalling and re-installing FAL, restore this library.

This is done because when FAL is installed, the dummy library is copied which
results in File Exchange Code Converter being unable to operate.

If you missed this operation, install the File Exchange Code Converter again.

For Windows, the option files for File Exchange Code Converter may be used.
Perform the following operations before uninstallation.
1. Save with an alias for each target directory.
2. Copy the libfal.ver and libuoc.ver files in the C:\WINNT directory to the
directory where it is saved.
3. When an updated file exists, copy the file from the backed-up directory
after installation of FAL and File Exchange Code Converter.

3-20 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

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 storage system
(defined by serial number).

Using the ppkeyset Command to Enter the License Key

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 (Version 01-XX-58 and earlier):
ppkeyset <License key> /usr/bin/fcunw /usr/bin/fcu /usr/lib/libfal.a
For 32bit (Version 01-XX-59 and later):
ppkeyset <License key> /usr/bin/fcunw /usr/bin/fcu /usr/lib/libfal.a
/usr/lib/libfalmt.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 Cross-OS File Exchange User’s Guide

Using the autoppkeyset Command to Enter the License Key
The autoppkeyset command reads the “PPID-FILE” and sets the license key.
This command shows the results (Normal End or Error). If no message
appears, the license key has not been set. This is caused by the following
reasons:
• The P.P. is not installed or deleted.
• The license key is not included in PPID FILE.
• The PPID FILE format is different.

Before executing autoppkeyset command, you must install PPID FILE in the
server:
• For UNIX platforms, input the following command from the command line:
32bit: autoppkeyset <License key File>
64bit: autoppkeyset64 <License key File>
Note: This command does not set the License key to libfalmt.*. Use
ppkeyset command to set.
• For Windows systems, open the command prompt (DOS window) and input
the following commands and parameters:
32bit: autoppkeyset <License key File>
64bit: autoppkeyset64 <License key File>
Note: This command does not set the License key to falmt.dll. Use
ppkeyset command to set.

Example:
# autoppkeyset /temp/12345.plk
PPID=xxx
ppkeyset 12345678901234567890 /usr/bin/fcu
[/usr/bin/fcu] set in available for all days.
---------------------
PPID=xxx
ppkeyset 12345678901234567890 /usr/bin/fcunw
[/usr/bin/fcu] set in available for all days.
---------------------
PPID=xxx
ppkeyset 12345678901234567890 /usr/lib/libfal.xx
[/usr/bin/fcu] set in available for all days.
---------------------
#

3-22 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Error messages for the autoppkeyset command:

Error message Meaning

autoppkeyset [PPID FILE] Specify the [PPID FILE]

Too many arguments. The command is specified too arguments

[PPID FILE] does not exist. Install the PPID FILE in server and execute the
command.

[PPID FILE] was not opened. Please re-execute the command.

Defined line in [PPID FILE] is too long. Check the PPID FILE format. The line is too long. The line
must be under 256 bytes.

ppkeyset failed. Please re-execute the command.

ppkeyset64 failed. Please re-execute the command.

Preparing for Cross-OS File Exchange Operations 3-23

Hitachi Cross-OS File Exchange User’s Guide

Creating FXoto Volumes Using the FMT Utility
After the FX 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
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-12.

Table 3-12 FMT Utility Values

Emulation 01-XX-47 01-XX-YY/ZZ 01-XX-YY/ZZ 01-XX-YY/2x 01-XX-YY/2x LUSE
Type or earlier not LUSE LUSE not LUSE (Note 1)
n=number of volumes
(Note 1) (Note 1) (Note 1) (Note 1)
(Note 2)

OPEN-V Not Not Not 65534 (min(Vc*n*128/96-7,65534)

supported supported supported (see Note 3)

OPEN-3 3331 3331 5818 3331 (min 3338*n-7, 65534)

OPEN-8 5818 5818 5818 9959 (min 9996*n-7, 65534)

OPEN-9 5818 5818 5818 10009 (min 10016*n-7, 65534)

OPEN-E Not 5818 5818 19752 (min 19759*n-7, 65534)

supported

OPEN-L Not 5818 5818 49429 (min 49439*n-7, 65534)

supported

Note 1: XX = 1 or 2; YY,x = number; ZZ<2x

Note 2: 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 3: 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-24 Preparing for Cross-OS File Exchange Operations

Hitachi 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-13
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-13 Relation between Block Length and Write Available Capacity
per Track
Block Length Write Block Length Write Block Length Write
by Available by Available by Available
Allocater = (A) Data per Allocater = (A) Data Per Allocater = (A) Data Per
(Bytes) Track (Bytes) Track (Bytes) Track
(Bytes) (Bytes) (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) × 12 917 - 948 (A) × 33 213 - 244 (A) × 55

2933 – 3188 (A) × 13 853 - 916 (A) × 34 181 - 212 (A) × 56

2677 – 2932 (A) × 14 821 - 852 (A) × 35 149 - 180 (A) × 57

2485 – 2676 (A) × 15 789 - 820 (A) × 36 117 - 148 (A) × 58

2325 – 2484 (A) × 16 757 - 788 (A) × 37 85 - 116 (A) × 59

2165 – 2324 (A) × 17 725 - 756 (A) × 38 53 - 84 (A) × 60

2005 – 2164 (A) × 18 693 - 724 (A) × 39 21 - 52 (A) × 61

1877 – 2004 (A) × 19 661 - 692 (A) × 40 1 - 20 (A) × 62

1781 – 1876 (A) × 20 629 - 660 (A) × 41 — —

1685 – 1780 (A) × 21 597 - 628 (A) × 42 — —

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.

Preparing for Cross-OS File Exchange Operations 3-25

Hitachi Cross-OS File Exchange User’s Guide

 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.

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 Table 7-3 for
further information on errors in UNIX).

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

1. Log in to the system as administrator.
2. Double-click on the Format icon to open the Format panel (see Figure
3-1).
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.

3-26 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

 Note: The maximum size for the Allocater is 4369 cylinders.
There is no spin button for Cylinder when version is 01-XX-48 or higher.
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 Figure 3-3). If the specified volser has already
been used, an error message is displayed to notify you (see 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 process 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.

Figure 3-1 FMT Utility for Windows Hosts

Preparing for Cross-OS File Exchange Operations 3-27

Hitachi Cross-OS File Exchange User’s Guide

 Figure 3-2 FMT Format Warning and Confirmation

Figure 3-3 FMT Format Complete Message

Figure 3-4 FMT VOLSER Used Message

Figure 3-5 FMT Error Message

3-28 Preparing for Cross-OS File Exchange Operations

Hitachi 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 Hitachi RAID storage systems. 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. Table 3-14 describes the FX volume association parameters.
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-14 FX Volume Association Parameters

Number Name Function Enter

1 Device file Specifies raw device Character-type device file name (e.g.,
name (partition) name defined for c1t0d2 for HP-UX, c1t0d2s1 for Solaris.
open-system. Note: For Solaris, HP-UX, and AIX, the
format is different if the link is with
JP1/HiCommand Dynamic Link Manager.
Refer to the readme for JP1/HiCommand
Dynamic Link Manager.

2 VOLSER Specifies logical volume Six-character volser (e.g., FX45). A volser

defined for mainframe. can use the following characters: A-Z, 0-9,
@, #, \

3 LVI or LU Specifies LVI or LU type of Correct LVI/LU for FX volume: 3390-3A,

type FX volume. -3B, -3C, 3380-KA, -KB, -KC or
(emulation) OPEN-x-FXoto. Make sure to define all
OPEN-x FMT volumes in a separate file.

4 Carriage Marks end of parameter Make sure to press the Return key (Enter
return set. key for Windows) at the end of each line.

5 End of file Marks end of parameter end

file.

Preparing for Cross-OS File Exchange Operations 3-29

Hitachi Cross-OS File Exchange User’s Guide

 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 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.
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 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 = TID, z = LUN.

In OPEN-x, x = 3, 8, K,E, L, M, 9 or V.

3-30 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

/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 (the first, second, and third drives are 0, 1, 2).

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

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

Preparing for Cross-OS File Exchange Operations 3-31

Hitachi Cross-OS File Exchange User’s Guide

 /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
(7)

Figure 3-13 FX Volume Definition File for Linux

3-32 Preparing for Cross-OS File Exchange Operations

Hitachi 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-15 specifies the requirements for FX datasets. The FCU GUI (see
Performing File Transfer Operations - UNIX and Performing File 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 mainframe dataset attributes
without using the GUI. The FXotm target dataset (which can also be an FXoto
intermediate dataset) must be created and properly configured before the 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-15 Mainframe Dataset Requirements

Item Requirement(s)

Dataset organization SAM (sequential-access method). FX does not support any other DO types (e.g., DAM, VSAM,
(DO) type PAM). If a non-SAM dataset is specified, FX will return an error.
Multiple-volume datasets are not supported. FX can only process the portion within one logical
volume.

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

Record format (RF) Fixed-length or variable-length record format. FX does not support undefined-length or
spanned record formats. If an illegal RF is detected, FX will return an error.
No key. If a record with a key is accessed, FX 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.

Block length (BL) Any length within the extent supported by the OS. If an illegal BL is detected, FX 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.

Record length (RL) Any length within the extent supported by the OS. If an illegal RL is detected, FX will return an
error.
Note: FX 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 option must be used to specify the
RL.

Track format Standard record 0 (R0). FX cannot process tracks with nonstandard R0.

VTOC For MVS: standard or index VTOC. For an index VTOC, FX 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.

Database file Direct access is not supported; must be converted to a SAM file.

Preparing for Cross-OS File Exchange Operations 3-33

Hitachi Cross-OS File Exchange User’s Guide

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 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 systems can only be used
on volumes formatted with the FMT utility for Windows 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.

3-34 Preparing for Cross-OS File Exchange Operations

Hitachi 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 Table 7-3 for
further information on errors in UNIX.

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

Preparing for Cross-OS File Exchange Operations 3-35

Hitachi Cross-OS File Exchange User’s Guide

 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).
– 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 process 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.

3-36 Preparing for Cross-OS File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Figure 3-14 ALC Utility for Windows Systems

Figure 3-15 ALC Disk Not Found Message

Figure 3-16 ALC Allocation Complete Message

Preparing for Cross-OS File Exchange Operations 3-37

Hitachi Cross-OS File Exchange User’s Guide

 Figure 3-17 ALC Error Message

3-38 Preparing for Cross-OS File Exchange Operations

Hitachi 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 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 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.
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, 2002 Hitachi, Ltd.

Figure 4-1 FCU Version and Copyright Screen (UNIX)

Using the Cross-Os File Exchange Software 4-3

Hitachi Cross-OS File Exchange User’s Guide

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.

File Conversion Utility

File Help

Parameter File

Volume File

Direction M to O O to M

Input File OK
Output File Cancel

Code Conversion E<->A EcA No FILE

Padding Yes No
Delimiter CR LF No

Emp Yes No

RDW Yes No
VSE
Status

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.

4-4 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

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

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 mainframe 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 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 Padding (PAD) Option): Yes = padding, No = no padding.
• Delimiter. The Delimiter buttons allow you to select the desired delimiter
option (see 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
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 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
Record Description Word (RDW) Option for further information on the VSE
record option values. Do not select this option for FXoto.

Using the Cross-Os File Exchange Software 4-5

Hitachi Cross-OS File Exchange User’s Guide

 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:
• Now checking = FCU is executing a dataset search or file attribute check.
If you specified the -nc option when you started FCU, this check does not
occur.
• Overwrite ? (OK/Cancel) is displayed if the FXmto target file already
exists. Click OK to overwrite the existing file, or click Cancel to cancel the
requested operation. If you specified the -nc option when you started FCU,
this confirmation does not occur.
• x% = The requested FX operation is x% complete.
• Complete = The requested FX operation completed successfully.
• Error. The Status field also displays error information for FCU and FX
operations. See Troubleshooting for further information on error conditions.

File Menu Commands

The File menu provides access to the following FCU functions:
• Load. This command loads the parameter sets from the specified FCU
parameter definition file onto the FCU main panel. Each time you select
Load, the next set of parameters is loaded. If you enter a file name in the
Parameter File field, the Load command opens the file and loads the first
parameter set (or creates the new file). If the FCU parameter definition file
is empty or was not found, FCU ignores this command.
• Save. This command saves the FCU parameter definition file. If no FCU
parameter set was previously loaded, the current parameter set is added to
the file. If a parameter set was previously loaded and you made changes,
the current parameter set overwrites and replaces the previously loaded
parameter set. If you make changes and do not select Save, FCU will
discard your changes when you select Load or Exit.
• Delete. This command deletes the currently loaded parameter set from the
FCU parameter definition file. If the FCU parameter definition file does not
yet exist or does not contain the parameter set on screen, FCU ignores this
command.
• Exit. This command closes the current FCU parameter definition file
(unsaved changes are discarded), and then closes the FCU program.

4-6 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

Help Menu Commands
The Help menu provides access to the following FCU functions.
Note: When installing FX Code Converter, the Edit_prm menu is displayed,
and the parameters for FX Code Converter can be displayed.
• Volume. This command displays the contents of the FX volume definition
file, so that you can verify that the FX volumes are properly defined.
• MF-File. This command displays the dataset information for each dataset
in the specified mainframe (MF) volume. The VSN must be entered in the
Input File field (for FXmto) or Output File field (for FXotm) on the FCU
main panel.
– Dataset name: An asterisk (*) before the dataset name indicates that
FX can process the dataset. A dash (-) indicates that FX cannot process
the dataset. A question mark (?) indicates that FCU can process the
dataset only if the VSE record option is used to specify the RF, RL, and
BL.
– Dataset organization (DO) type: SAM, DAM, PAM, VSAM, ??? =
unknown.
– Record format (RF): F = fixed length, V = variable length, U =
undefined length, S = spanned record, ? = unknown.
– Block length (BL): in bytes
– Record length (RL): in bytes
– Dataset size (DS): in tracks
• UX-File. This command displays the UNIX (UX) files in the directory
specified in the Input or Output File field on the FCU main panel. If no
directory is specified in the Input File or Output File field, FCU displays
the files in the current directory. If a nonexistent directory is specified, FCU
will return an error.
• Error. This command opens the error information panel, which displays the
FAL, FCU, and system error codes/messages.
• OnVersion. This command displays the FCU version and copyright
information screen.

/dev/rdsk/cxtydz volser 3390-3B

/dev/rdsk/cxtydz volser 3390-3A
/dev/rdsk/cxtydz volser 3390-3C:
/dev/rdsk/cxtydz volser 3380-KB
/dev/rdsk/cxtydz volser 3380-KA
/dev/rdsk/cxtydz volser 3380-KC
:
end

Figure 4-3 Help-Volume Display (HP-UX Shown)

Using the Cross-Os File Exchange Software 4-7

Hitachi Cross-OS File Exchange User’s Guide

 Dataset Information : VSN = xxxxxx Device Emulation Type = 3390-3B

Dataset Name DO RF BL RL DS

*SAMFILE01.FIX SAM F 4096 128 150 ← Can be processed by FCU.

-DAMFILE.F DAM F 4096 128 30 ← Cannot be processed by FCU.
*SAMFILE02.VAR SAM V 4000 80 50 ← Can be processed by FCU.
-PAMFILE PAM F 5000 100 200 ← Cannot be processed by FCU.
-VIRTUALSTORAGEACCESS VSAM V 32768 4096 3000 ← Cannot be processed by FCU.
-UNDEFSAMFILE SAM U 8000 200 80 ← Cannot be processed by FCU.
-SAMFILESPANNED SAM S 8192 8192 300 ← Cannot be processed by FCU.

Figure 4-4 Help MF-File Display

UNIX FILE LIST : DIR = /aaaaa/bbbbb/cccc

ddddd.dd eeeeee ffffff.fffffff

hhhhh.hhhh zzzzzz.z xxxx.x
yyyyyyyyy

Figure 4-5 Help UX-File Display

Error Information Screen

This window opens when the Error command is used. It displays the FAL, FCU,
and system error codes/messages.

Error information

FCU error: ( 0)

FAL error: ( 0)

System error: ( 0)

Close

Figure 4-6 Error Information Display

4-8 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

FCU for Windows
FCU Version and Copyright Dialog
To start the FCU GUI program for Windows systems:
1. Log on with Administrator access privileges.
2. Start the FCU GUI as follows: Click Start-Programs-FCU-FCU, or open
the c:\ folder and double-click on FCU, or create a shortcut for FCU on the
desktop.
Note: Do not start FCU by dragging and dropping an FCU parameter
definition file on the FCU program icon. FCU program operation cannot be
guaranteed.
3. If you want to specify any of the FCU options, start FCU from the command
line (DOS prompt) as follows: Go to the FCU directory (containing fcu.exe
and datasetmount.dat), and enter fcu [-nc] [-cl] [param]
The -nc option is the same as for UNIX: All specified FX operations are
performed without confirmation of FCU parameters or FXmto target file
overwrites.
The -cl option specifies that all FCU log files will be cleared before starting.
The param option is the same as for UNIX:
– If you want to open a new untitled FCU parameter definition file when
you start FCU, leave the param option blank.
– If you want to load an FCU parameter definition file when you start
FCU, enter the file name with complete path if the file is not in the
current directory.
4. The FCU GUI program now starts loading. The FCU version and copyright
screen (see Figure 5-7) is displayed while FCU is loading. When FCU is
finished loading, the FCU main panel is displayed (see Performing File
Transfer Operations (UNIX)).
5. If you started FCU from the DOS prompt and specified the -nc option, FCU
processes all specified operations, overwrites existing FXmto target files,
and then terminates and displays any error information at the DOS prompt.

Using the Cross-Os File Exchange Software 4-9

Hitachi Cross-OS File Exchange User’s Guide

 Figure 4-7 FCU Version and Copyright Screen (Windows Systems)

File Conversion Utility Window

The FCU main panel opens when FCU is finished loading. The FCU main panel
displays the FCU parameter definition file (or Untitled if no file was specified),
allows you to perform FX operations, and provides access to all FCU functions.

View commands:
Volume info.
MF-file info.
Parameter-Load commands: Parameter commands: Options
File commands: Load-Top Save-Insert Error info.
New Load-Previous Save-Replace Parameter line
Open Load-Next Delete Close all dialogs
Save Load-Bottom Wipe Log file Help-About
Title bar

Toolbar

Click this button to select a dataset

Source or (VSN must be specified).
target
dataset

Click to
change
direction

Source or
target file

Starts the specified operation. Not

enabled if parameters are not saved in Click this button to select a file.
the file, or if a parameter is incorrect.
Status bar Current line number/total lines.

Figure 4-8 FCU Main Panel for Windows Systems

4-10 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

The FCU title bar displays the current FCU parameter definition file. The
toolbar provides speed buttons for the commonly used FCU functions. The
status bar displays the current line number and total number of lines in the
current FCU parameter definition file. The Main frame file and Open-system
file fields display the files to be transferred (no spaces allowed). The file
selection buttons ( ) allow you to select the desired mainframe dataset and
Windows file.

The File menu provides access to the following FCU functions:

• The File-New command (Ctrl+N) opens a new FCU parameter def. file
(untitled.prm).
• The File-Open command (Ctrl+O) opens an existing FCU param. def. file
(filename.prm).
• The File-Save command (Ctrl+S) saves the current FCU parameter
definition file. Deleted and replaced lines are discarded, inserted lines are
added, and all lines after end are discarded.
Note: This command does not save the current parameter set.
• The File-Save As… command saves the current FCU parameter definition
file with a different file name and/or location.
• The File-Exit command (Ctrl+X) exits the FCU software.

The Edit menu is reserved for future enhancement and is not yet enabled.

The Parameter menu provides access to the following FCU functions:

• The Parameter-Load command loads the Previous, Next, Top, and
Bottom parameter lines from the current FCU parameter definition file.
The FCU main panel status bar updates the current line number when any
Parameter-Load command is executed.
• The Parameter-Save command allows you to either Insert the parameter
set being displayed into the current FCU parameter definition file, or
Replace the current parameter set (previously loaded) with the parameter
set being displayed. If you do not select this command, your parameter
changes will not be saved.
Note: This command does not save the current FCU parameter definition
file (you must use File-Save/Save As).
• The Parameter-Delete command deletes the current parameter set from
the current FCU parameter definition file. The line is not permanently
deleted until you save the current FCU parameter definition file using the
File-Save command.
• The Parameter-Wipe command clears all FCU initiation parameters
displayed on screen, so that you can input new parameters easily. This
command does not delete the current parameter set.

Using the Cross-Os File Exchange Software 4-11

Hitachi Cross-OS File Exchange User’s Guide

 The View menu provides access to the following FCU functions:
• The View-Toolbar and View-Status bar commands display/hide the FCU
toolbar and status bar.
• The View-Volume information… command opens the FCU Volume
Information panel, which displays the contents of the FX volume definition
file.
• The View-MF-file information… command displays the following
information for the mainframe (MF) files (datasets) in the volume specified
in the Mainframe file field on the FCU main panel.
• The View-Option… command opens the Option panel, which allows you to
view/change the FCU file transfer options.
• The View-Error information… command opens the Error Information
panel.
• The View-Parameter line… command opens the Parameter Line panel.
• The View-Close all dialogs command closes all open panels except the
FCU main panel.
• The View-Log file command opens the log file for the current FCU
parameter definition file.
• The Help-About FCU… menu command opens the FCU version and
copyright screen (refer to Figure 5-7).

4-12 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

Volume Information Dialog
The View-Volume information… command opens the FCU Volume
Information panel, which displays the contents of the FX volume definition file.
A { displayed next to a volume indicates that the volume definition is correct
and FCU can access the volume. An  displayed next to a volume indicates
that the volume definition is not correct and FCU cannot access the volume.

Figure 4-9 Volume Information Panel

Note: This example shows an FX volume definition file which defines only one
FX volume.

Using the Cross-Os File Exchange Software 4-13

Hitachi Cross-OS File Exchange User’s Guide

Mainframe File Information Dialog
The View-MF-file information… command displays the following information
for the mainframe (MF) files (datasets) in the volume specified in the
Mainframe file field on the FCU main panel:
– { = the dataset can be processed by FCU.
 = the dataset cannot be processed by FCU.
? = the dataset can be processed by FCU only if the VSE record option
is used to specify the RF, RL, and BL.
– Dataset = dataset name
– DO = dataset organization type: SAM, DAM, PAM, VSAM, ? (other
than above)
– RF = record format: F (fixed-length), V (variable-length), U
(undefined), S (spanned), ? (other than above)
– BL = block length
– RL = record length
– DS = dataset size (in number of tracks)

Figure 4-10 MF-File Information Panel

Note: This example shows an FX volume (3380-KA, VSN = AAAAAA ) which

contains only two datasets.

Note: When this panel is opened using the Mainframe file selection button
( ), only SAM datasets are displayed.

4-14 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

Option Dialog
The View-Option… command opens the Option panel, which allows you to
view/change the FCU file transfer options (code conversion, padding, delimiter,
empty file, RDW, and VSE), continuous execution option, and clear log file
option.

Figure 4-11 Option Panel

– Select the EBCDIC<-->ASCII button to use the default code

conversion table (EA, EcA). Select No for no code conversion (No).
Select External table file and enter the file name with path if not in
the current directory (e.g., /directory/filename.tbl).
– Check the Padding box to request the padding option (Yes).
– Check the Delimiter box to request the delimiter option (Yes).
– Check the Empty box to request the empty file option (Emp=Yes).
– Check the Record Description Word box to request the RDW option
(RDW=Yes). Note: If the Record description word box is checked,
the EBCDIC<-->ASCII button and the Padding and Delimiter boxes
are ignored.
– Check the VSE box and enter the RF, RL, and BL to request the VSE
record option.

Using the Cross-Os File Exchange Software 4-15

Hitachi Cross-OS File Exchange User’s Guide

 – Check the Continuous execution box to tell FCU to process the rest of
the FCU initiation parameter sets in the specified FCU parameter
definition file without stopping after each completed operation
(equivalent to the -nc option starting at the desired line). FCU will
execute all lines from the current line to the end. If you do not check
the Continuous execution box, FCU will stop after each operation.
– Check the Clear log file before execution box to clear the log file for
the current FCU parameter definition file (e.g., fcudata.prm.log). The
user should clear the FCU log files as needed to decrease the file size
and save space on the current drive.

Parameter Line Dialog

The View-Parameter line… command opens the Parameter Line panel,
which displays the current line (parameter set) in the current FCU parameter
definition file.

The Parameter menu provides access to the following FCU functions:

• The Parameter-Load command loads the Previous, Next, Top, and
Bottom parameter lines from the current FCU parameter definition file.
The FCU main panel status bar updates the current line number when any
Parameter-Load command is executed.
• The Parameter-Save command allows you to either Insert the parameter
set being displayed into the current FCU parameter definition file, or
Replace the current parameter set (previously loaded) with the parameter
set being displayed. If you do not select this command, your parameter
changes will not be saved.
Note: Use File-Save/Save As to save the current FCU parameter
definition file.
• The Parameter-Delete command deletes the current parameter set from
the current FCU parameter definition file. The line is not permanently
deleted until you save the current FCU parameter definition file using the
File-Save command.
• The Parameter-Wipe command clears all FCU initiation parameters
displayed on screen, so that you can input new parameters easily. This
command does not delete the current parameter set.

Figure 4-12 Parameter Line Panel

4-16 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

Execute Dialogs
After selection the desired operation on the FCU Main window, the Execute
button at the bottom of the window is enabled. Click Execute to start the
selected operation. (If the Execute button is not enabled, you have not saved
the current parameter set.)

If you started an FXmto operation and the target file already exists, FCU
requests overwrite confirmation. Click OK to overwrite the target file, or click
Cancel to cancel the operation.

When FCU starts the operation, the Execute panel opens and displays the
progress of the operation. Note: The Execute dialog panel will not appear
when the mainframe OS is VSE.

The Cancel button changes to

Close after the operation is

Figure 4-13 Execute Panel Showing Normal End

When the operation is complete, the Execute panel displays the result. If an
error occurred, the Error information panel opens automatically to display the
error. See Error Codes and Messages for further information on errors.

To cancel the operation in progress, select Cancel.

The Cancel button changes to

Close after the operation ends
abnormally.

Figure 4-14 Execute Panel Showing Canceled Operation

If an error occurred, the Error information panel opens automatically to display

the error). If there is an error during execution the panel below will be
displayed. You should check that your parameters have been entered correctly
and try executing the command again. See Troubleshooting for further
information on errors.

Using the Cross-Os File Exchange Software 4-17

Hitachi Cross-OS File Exchange User’s Guide

 The Cancel button changes to
Close after the operation is
canceled.

Figure 4-15 Execute Panel Showing Error End

Note: FCU does not load the next operation automatically. To perform another
FX operation, select the desired Parameter-Load command, and repeat steps
(8) through (12) as shown in Section File Conversion Utility Window. To exit
FCU, select the File-Exit command.

Error Information Dialog

The View-Error information… command opens the Error Information panel,
which displays the most recent error information (error code and message) for
FCU, FAL, and system errors.

Figure 4-16 Error Information Panel

Log Files
The View-Log file command opens the log file for the current FCU parameter
definition file using the Windows Notepad text editor. The log file contains the
parameter sets executed, the date and time of execution, the result of each
operation, and the error information (FCU, FAL, and Sys error codes) for each
operation.

4-18 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

Figure 4-17 FCU Log File Display in Notepad

Using the Cross-Os File Exchange Software 4-19

Hitachi Cross-OS File Exchange User’s Guide

Format Utility for Windows
After the FX 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
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-12.

Table 4-1 FMT Utility Values

Emulation 01-XX-47 01-XX-YY/ZZ 01-XX-YY/ZZ 01-XX-YY/2x 01-XX-YY/2x
Type or earlier Not LUSE LUSE Not LUSE LUSE (Note 2)
n=number of volumes
(Note 2) (Note 2) (Note 2) (Note 2)
(Note 3)

OPEN-V Not Not Not 65534 (min(Vc*n*128/96-7,65534)

supported supported supported (see Note 4)

OPEN-3 3331 3331 5818 3331 (min 3338*n-7, 65534)

OPEN-8 5818 5818 5818 9959 (min 9996*n-7, 65534)

OPEN-9 5818 5818 5818 10009 (min 10016*n-7, 65534)

OPEN-E Not 5818 5818 19752 (min 19759*n-7, 65534)

supported

OPEN-L Not 5818 5818 49429 (min 49439*n-7, 65534)

supported

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.

4-20 Using the Cross-OS file Exchange Software

Hitachi 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-13
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 4-2 Relation between Block Length and Write Available Capacity
per Track
Block Length Write Block Length Write Block Length Write Available
by Available by Available by Data Per Track
Allocater = (A) Data per Allocater = (A) Data Per Allocater = (A) (Bytes)
(Bytes) Track (Bytes) Track (Bytes)
(Bytes) (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) × 12 917 - 948 (A) × 33 213 - 244 (A) × 55

2933 – 3188 (A) × 13 853 - 916 (A) × 34 181 - 212 (A) × 56

2677 – 2932 (A) × 14 821 - 852 (A) × 35 149 - 180 (A) × 57

2485 – 2676 (A) × 15 789 - 820 (A) × 36 117 - 148 (A) × 58

2325 – 2484 (A) × 16 757 - 788 (A) × 37 85 - 116 (A) × 59

2165 – 2324 (A) × 17 725 - 756 (A) × 38 53 - 84 (A) × 60

2005 – 2164 (A) × 18 693 - 724 (A) × 39 21 - 52 (A) × 61

1877 – 2004 (A) × 19 661 - 692 (A) × 40 1 - 20 (A) × 62

1781 – 1876 (A) × 20 629 - 660 (A) × 41 — —

1685 – 1780 (A) × 21 597 - 628 (A) × 42 — —

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.

Using the Cross-Os File Exchange Software 4-21

Hitachi Cross-OS File Exchange User’s Guide

 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.

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

1. Log in to the system as administrator.
2. Double-click on the Format icon to open the Format panel (see Figure
3-1).

Figure 4-18 FMT Utility for Windows Systems

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

4-22 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

 Figure 4-19 FMT Format Warning and Confirmation

7. When the format operation completes successfully, the Format complete

message is displayed (see Figure 3-3).

Figure 4-20 FMT Format Complete Message

If the specified volser has already been used, an error message is

displayed to notify you (see Figure 3-4).

Figure 4-21 FMT VOLSER Used Message

If the format operation could not be started due to an error condition, the
Format check error message is displayed.

Figure 4-22 FMT Error Message

Using the Cross-Os File Exchange Software 4-23

Hitachi Cross-OS File Exchange User’s Guide

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

4-24 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

Allocation Utility for Windows
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 (see Format Utility for
Windows).

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 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 systems can only be used
on volumes formatted with the FMT utility for Windows systems.

CAUTION: The capacity of the intermediate dataset varies depending on block

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

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).
When record format = V or VB, 5 ≤ record length ≤ (block length − 4).

Using the Cross-Os File Exchange Software 4-25

Hitachi Cross-OS File Exchange User’s Guide

 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 (n = system error code):
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 process 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.

4-26 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

Figure 4-23 ALC Utility for Windows Systems

Figure 4-24 ALC Disk Not Found Message

Figure 4-25 ALC Allocation Complete Message

Using the Cross-Os File Exchange Software 4-27

Hitachi Cross-OS File Exchange User’s Guide

 Figure 4-26 ALC Error Message

4-28 Using the Cross-OS file Exchange Software

Hitachi Cross-OS File Exchange User’s Guide

 5
Performing Cross-OS File Exchange
Operations
This chapter describes how to operate Cross-OS File Exchange.
Performing File Transfer Operations - UNIX
Performing File Transfer Operations – Windows

Performing Cross-OS File Exchange Operations 5-1

Hitachi Cross-OS File Exchange User’s Guide

 FX file transfer operations are performed using the FCU GUI software installed
on the open-system host(s) attached to the Hitachi RAID storage systems.

The FCU GUI enables you to perform file transfer operations interactively,
provides access to detailed information on the FX source datasets and files,
and displays error information for FX operations. The FCU GUI also allows you
to create and modify FCU parameter definition files interactively.

When you perform FX operations that access datasets on -A, -B, or -C FX

volumes, FCU must have access to the FX volume definition file that defines
these volumes. When you perform FX operations that access ALC-generated
datasets on OPEN-x FMT FX volumes, FCU must have access to the separate
FXoto volume definition file that defines the OPEN-x FMT volumes. Since FCU
can only access one FX volume definition file at a time, the FCU parameter
definition files must also keep operations using OPEN-x FMT volumes separate
from operations using -A, -B, or -C FX volumes. Before you start FCU GUI
operations, make sure that the desired FX volume definition file is available
(datasetmount.dat in current directory) and that the desired FCU parameter
definition file contains FX operations which access the volumes defined in the
FX volume definition file. FCU will not be able to perform operations which
access volumes that are not defined in the current FX volume definition file.

The FCU GUI for UNIX -based platforms and the FCU GUI for Windows systems
are significantly different. Section Performing File Transfer Operations - UNIX
describes and provides instructions for using the FCU GUI for UNIX. Section
Performing File Transfer Operations – Windows describes and provides
instructions for using the FCU GUI for Windows systems. For information on
using FCU from the command line (without the GUI), see Using FCU from the
Command Line (UNIX).

For information on using the FAL C functions (Visual C++® for Windows
systems), which enable user programs on the open-system host to access
mainframe datasets on FX volumes, see Allocation Utility for Windows.
4

5-2 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Performing File Transfer Operations - 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.

Starting the FCU GUI for UNIX

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]

Performing Cross-OS File Exchange Operations 5-3

Hitachi 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.
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 5-1 FCU Version and Copyright Screen (UNIX)

Performing File Transfer Operations (UNIX)

To perform file transfer operations using the FCU GUI for UNIX:
1. If you will be performing FXmto operations:
a. Make sure that the source datasets are located on the desired FX
volume(s). If you will not be using an existing FCU parameter definition
file, write down the VSN:dataset of the source dataset and the complete
path and file name of the target file for each FXmto operation.
b. Verify that the FXmto target files do not already exist (or can be
overwritten).
c. Vary the FXmto volume(s) and channel path(s) offline from the
mainframe host.
2. If you will be performing FXotm operations:
a. Make sure that the source files are located on the desired FX volume(s).
If you will not be using an existing FCU parameter definition file, write
down the complete path and file name of the source file and the VSN:
dataset of the target dataset for each FXotm operation.
b. Create and allocate the target datasets. This ensures that the target
dataset is registered in the VTOC. Make sure to allocate enough space
and to use the appropriate record format and record length for the data
to be transferred.

5-4 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

 c. Vary the FXotm volume(s) and channel path(s) offline from the
mainframe host.
3. If you will be performing FXoto operations:
a. If you will not be using an existing FCU parameter def. file, write down
the complete path and file name of the source and target files for each
FXotm/mto operation.
b. Allocate the intermediate datasets on the FXoto volume(s). Use the ALC
utility on OPEN-x FMT volumes. Make sure to allocate enough space and
to use the appropriate record format and record length for the data to
be transferred.
c. Verify that the FXoto target files do not already exist (or can be
overwritten).
4. Make sure that the desired FX volume definition file (FXoto only, or FXmto
and FXotm) is available for use by FCU (datasetmount.dat in current
directory).
5. Start FCU with the desired options (see Starting the FCU GUI for UNIX).
Note: If you specify the -nc option, FCU performs all specified operations
continuously, then self-terminates and displays any error information at
the UNIX prompt.
6. When the FCU main panel opens, make sure that the Volume File field
displays the FX volume definition file (datasetmount.dat). If the FX
volume definition file is not displayed (or if incorrect), FCU will not be able
to perform FX operations.
7. Make sure the Parameter File field displays the desired FCU parameter
definition file. If not, enter the desired FCU parameter definition file name
(with complete path if not in the current directory), and select the
File-Load command to open the file. If you want to create a new file using
the FCU GUI, see Using the listvol Function (UNIX) for instructions.
8. The FCU main panel displays the first/next parameter set in the specified
FCU parameter definition file. If you want to perform this FX operation,
click OK. If not:
a. You can load the next parameter set using the File-Load command.
b. You can delete the current parameter set from the FCU parameter
definition file using the File-Delete command. The next parameter set
loads automatically.
c. You can modify the current parameter set as follows: Change the FCU
parameters as needed, and then use the File-Save command to save
your changes in the FCU parameter definition file (replaces the
previously loaded parameter set).
d. You can add a new parameter set to the end of the file as
follows: Select File-Load until you reach the end of the file, enter the
desired parameters, and then select File-Save to add the new line at
the end. If you want to insert a new line between existing lines, edit the
FCU parameter definition file later using a text editor.

Performing Cross-OS File Exchange Operations 5-5

Hitachi Cross-OS File Exchange User’s Guide

 9. When the desired FX operation is displayed, click OK to start the operation.
(If the OK button is not enabled, you have not saved the current
parameter set.)
10. If you started an FXmto operation and the target file already exists, FCU
requests overwrite confirmation. Click OK to overwrite the target file, or
click Cancel to cancel the operation.
11. When FCU starts the operation, the Status field displays the progress of
the operation. If desired, while the operation is in progress, you can load
another parameter set and click OK to start the next operation right after
the current operation completes.
Note: Be careful when doing this. If you click buttons or menu commands
while an operation is in progress, FCU will save and execute those
commands when the current operation completes.
12. When the FX operation is complete, the Status field displays Complete. If
an error occurred, the error information display opens automatically to
display the error. See Troubleshooting for further information on error
conditions.
13. FCU does not load the next operation automatically. To perform another FX
operation, select File-Load, and repeat steps (8) through (12). To exit
FCU, select the File-Exit command.

Using the listvol Function (UNIX)

The listvol VSN function enables FCU users to access the mainframe dataset
information without having to launch the FCU GUI (and use the Help-MF-File
command). The listvol VSN UNIX command displays the dataset information
for the specified VSN. The listvol VSN function requires the FX volume
definition file.

Note: The listvol VSN function is available in FCU for UNIX versions 01-01-41
and later.

# listvol volser  Specify 6-character VSN.

Dataset Name DO RF RL BL TT R EX (Cyl:Trk)

________________________________________________________________________
*SAMFILE01.FIX SAM F 4096 4096 1 10 100:0
-DAMFILE.F DAM F 128 4096 0 10 100:0
?SAMFILE.VSE SAM ? 0 0 0 0 0:0

0  Return value (normal end).

#

Figure 5-2 Listvol VSN Function

5-6 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

The listvol VSN function displays the following information:
• Dataset name. An asterisk (*) before the dataset name indicates that FX
can process the dataset. A dash (-) indicates that FX cannot process the
dataset. A question mark (?) before the dataset name indicates that FCU
can process the dataset only if the VSE record option is used to specify the
RF, RL, and BL.
• Dataset organization (DO) type: SAM, DAM, PAM, VSAM, ??? = unknown.
FX supports SAM datasets.
• Record format (RF): F = fixed length, V = variable length, U = undefined
length, S = spanned record, ? = unknown. FX supports F and V record
formats.
• Record length (RL): in bytes
• Block length (BL): in bytes
• TT+R: last block address
• EX (Cyl:Trk): data extent size (number of cylinders:number of tracks)
• Return value: 0 indicates normal end; 1 indicates error end. If an error
occurred, the error code and message are displayed and the error is logged
in the error log file.

Performing Cross-OS File Exchange Operations 5-7

Hitachi Cross-OS File Exchange User’s Guide

Creating FCU Parameter Definition Files (UNIX)
The FCU parameter definition files are used to store FCU initiation parameter
sets for pre-defined FX operations. If you plan to perform specific sets of FX
operations more than once, you can create an FCU parameter definition file for
each set of FX operations. The FCU program allows you to specify which FCU
parameter definition file to load and execute, and you can also choose whether
to execute all FX operations defined in the file or confirm each operation
before starting it. You can create and edit the FCU parameter definition files
interactively using the FCU GUI or manually using a text editor.

Table 5-1 lists the requirements for the FCU parameter definition files. Each
set of FCU initiation parameters specifies the direction, source and target files,
and FCU options (e.g., padding, delimiters) for a specific FX operation.

5-8 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Table 5-1 FCU Parameter Definition File Requirements
Item Requirements

Default file name/location For UNIX systems: fcudata.param in the directory containing the
FCU program.
For Windows systems: fcudata.prm in the directory containing the
FCU program.
Note: When upgrading from version 01-01-24 or earlier to version
01-01-36 or later on Windows systems, rename the file to change
.param to .prm.
To access the default FCU parameter definition file, leave the
param option blank when starting FCU.
To access a different parameter definition file, specify the file name
(with complete path if necessary) when starting FCU.
For Windows systems, the FCU parameter definition file must have
the .prm file extension.

Maximum number of For UNIX systems: 999.

parameter sets For Windows systems: determined only by system memory.

FCU initiation parameters Must be separated by at least one space character.

Case sensitive (e.g., use Yes, not YES or yes, for the Emp and
RDW parameters).
Parameters (1)-(6) must be specified in order.
Parameters (7)-(9) (optional) can be specified in any order (not
before 1-6).

Comment lines (start with #) For UNIX systems:

When using the FCU GUI ƒ Cannot be created using GUI.
ƒ Loaded but not displayed by GUI (“Parameter file:Comment line”
displayed).
ƒ Can be changed to a normal parameter line using GUI.
ƒ Included in number of parameter sets (each comment counts as
one set).
For Windows systems:
ƒ Skipped by FCU (not processed).
ƒ Cannot be created, edited, or deleted using GUI (must use text
editor).
ƒ Cannot be displayed by GUI (“Parameter file:Comment line” is
displayed).
ƒ Not included in line count.

Comment lines (start with #) For UNIX only:

When not using the FCU GUI ƒ Skipped by FCU (not processed).
ƒ Not included in number of parameter sets (max = 999).

Space lines Not allowed with FCU GUI (remove space lines if upgrading from 01-
01-24 or earlier to 01-01-36 or later on Windows systems).
Allowed and skipped when using FCU without the GUI (using the -
nw option).

Performing Cross-OS File Exchange Operations 5-9

Hitachi Cross-OS File Exchange User’s Guide

 Figure 5-3 illustrates the structure of an FCU parameter definition file. Table
5-2 lists the requirements for the FCU initiation parameters. To define FXoto
operations, first define the FXotm operations that transfer the data from the
source files to the intermediate datasets, and then define the FXmto
operations, which transfer the data from the intermediate datasets to the
target files. Do not define FXoto operations that access OPEN-x FMT volumes
and FX operations that access -A, -B, or -C FX volumes in the same FCU
parameter definition file. Since FCU can only access one FX volume definition
file at a time, each FCU parameter definition file must contain either FX
operations which access OPEN-x FMT volumes or FX operations which access -
A, -B, or -C volumes, but not both.

mto VSN:dataset name Open-system file name CC PAD DEL Emp=Yes RDW=Yes
VSE=RF,RL,BL
mto VSN:dataset name Open-system file name CC PAD DEL Emp=Yes RDW=Yes
VSE=RF,RL,BL
otm Open-system file name VSN:dataset name CC PAD DEL Emp=Yes
VSE=RF,RL,BL
otm Open-system file name VSN:dataset name CC PAD DEL Emp=Yes
VSE=RF,RL,BL
(1) (2) (3) (4) (5) (6) (7) (8) (9)
(10)
:
end
(11)

Figure 5-3 FCU Parameter Definition File

Table 5-2 FCU Initiation Parameter Requirements

Number Name Function Options

(1) FX direction Required. mto for FX mainframe-to-open.

Specifies the file otm for FX open-to-mainframe.
transfer direction.

(2) Source file Required. VSN:dataset for mainframe source dataset:

Specifies the
ƒ VSN = six-character volume serial number
source file.
ƒ colon = separates VSN and dataset name
ƒ dataset = dataset name (44 chars max, no spaces)
file name for open-system source file:
ƒ Space characters not allowed.
ƒ Specify path (absolute or relative) if not in current
directory:
UNIX path: /directory_name/…/file_name
Windows path: drive:\directory_name\…\file_name

(3) Target file Required. Same as parameter (2): VSN:dataset or file_name.

Specifies the target
file.

5-10 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Number Name Function Options

(4) Code Required. EA to use default EBCDIC-ASCII code conversion table

conversion Specifies code for mto or otm.
conversion.
EcA to use default EBCDIC-ASCII code conversion
table for oto.
No for no code conversion.
File_name to use your own code conversion table
(see section 3.1.1).
(see Note 1)

(5) Padding Required. Yes for FXmto with padding.

Specifies padding No for FXmto without padding and for FXotm.
option.
Note: When FX is used with FX Code Converter,
padding in FCU is not supported. Specify “No.”
Specifying “YES” results in an error.

(6) Delimiter Required. For FXmto operations:

Specifies delimiter UNIX:
option and type.
CR Carriage return (CR) is added as a delimiter.
LF Line feed (LF) is added as a delimiter.
No No delimiter is added.
Windows systems:
CRLF CR + LF is added as a delimiter.
For FXotm operations:
UNIX:
CR Data up to CR is cut off as data entity.
LF Data up to LF is cut off as data entity.
No Data is cut off according to dataset record
length.
Windows systems:
CRLF Data up to CR + LF is cut off as data entity.
No Data is cut off according to dataset record
length.
Note: When using with FX Code Converter, specify
“No” because the delimiter for this parameter is not
supported. Specifying other than “No” ends in an error
in UNIX systems. In Windows systems, however, it is
processed as “No.”

(7) Empty file Optional. This parameter is optional. If not specified, Emp=No
Enables processing is assumed.
of empty source Emp=Yes Execute the data transfer even if the
files.
source file is empty. FXmto target file size = 0. FXotm
target dataset will contain only EOF.
Emp=No Execute the data transfer. If the source file
is empty, the FX operation is rejected with an error.

Performing Cross-OS File Exchange Operations 5-11

Hitachi Cross-OS File Exchange User’s Guide

 Number Name Function Options

(8) Record Optional. This parameter is optional. If not specified, RDW=No

description Specifies if FCU is assumed. Do not specify this parameter for FXotm
word adds the record operations.
description word.
RDW=Yes Add record description word to each
FXmto only.
record. CC, PAD, and DEL must be No (if not, error).
WARNING: Data Direction must be mto (if not, error). Source dataset
transferred to open must be variable length (if not, RDW=Yes is ignored).
using RDW=Yes
RDW=No Do not add record description word to each
and then
record. Outputs only the data entity for each record.
transferred back to
z/OS is not Note: When using with FX Code Converter, do not
compatible with specify “RDW=Yes” because adding record length is
the original not supported. Specifying “RDW=Yes” results in an
dataset. error in UNIX systems, but it is processed as “No” in
Windows systems.

(9) VSE record Optional. This parameter is optional. If not specified, the VTOC
Specifies the RF, must specify the RF, RL, and BL. Do not specify this
RL, and BL for VSE parameter for FXoto using ALC-generated datasets on
datasets. FXmto OPEN-x FMT volumes.
and FXotm only. VSE=RF,RL,BL
RF, RL, and BL must be separated by a comma (,) and
no spaces.
RF F fixed-length and unblocking
FB fixed-length and blocking
V variable-length and unblocking
VB variable-length and blocking
RL record length in bytes (decimal)
When RF = F: RL = BL
When RF = FB: RL = [BL/n] (n is an integer)
When RF = V or VB: 5 ≤ RL ≤ [BL - 4]
BL When RF = F or FB: 1 through 32760
When RF = V or VB: 9 through 32760
(See Note 2)

(10) Carriage Required. Marks Press Return (Enter for Windows systems) at the end
return end of parameter of each line.
set. Note: When using FX with FX Code Converter, specify
‘USER-EDIT field definition file name, edit option file
name’ between (10) and (11). For details, please see
the Code Converter User’s Guide.

(11) End of file Optional. Marks end This parameter is optional.

end of parameter
file.

Note 1: The Code converting function is not supported for FXoto. Specify “No”
in this field when FXoto is used. Even if “EA” is specified or the file name of the
conversion table in this field is specified when FXoto is used, code conversion
is not executed. Since code conversion for FCU is not supported even when
using with FX Code Converter, specify “No.” Specifying anything other than
“No” results in an error in UNIX systems. In Windows systems, however,
specifying anything other than “No” is processed as “No.”

5-12 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Note 2: When you use MTO and OTM for a dataset allocated by VSE2.5, FX
can transfer data without the VSE parameter. This is illustrated below:
• RF=V: It is possible to transfer data between correct dataset attributes
(5≦RL≦BL-4). The data transfer is valid only if the VSE parameter is the
following:
RL≦32756
BL≦32760
BL=RL+4
For the dataset attribute below, the data transfer is valid only if user
specifies the VSE parameter value as shown above.
RL＞32756
BL＞32760
For the following dataset attribute, the data transfer is valid only if user
specifies the VSE parameter value between RL and BL values shown as #1
and #2 below.
RL≦32756
BL≦32760
RL=BL
#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
• RF=VB: It is possible to transfer data using the correct dataset attribute
(5≦RL≦BL-4). The data transfer is valid only if VSE parameter is 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
• RF=V (without VSE parameter): It is possible to transfer data using the
correct dataset attributes (BL＝RL+4≦32760). The data transfer is valid
only if the RL and BL values on VTOC are the following:
BL＝RL+4≦32760
Where RL > 32756 and BL > 32760 on VTOC, FX manages the data as
RL=32756 and BL=32760.
Where RL≦32756, BL≦32760 and RL = BL on VTOC, FX manages the
data as shown:
RL(FX internal value) = RL(value on VTOC) + 4 ≦32756
BL(FX internal value) = BL(value on VTOC) + 8 ≦32760

Performing Cross-OS File Exchange Operations 5-13

Hitachi Cross-OS File Exchange User’s Guide

 • RF=VB (without VSE parameter): It is possible to transfer data between
correct dataset attributes (BL＝RL+4≦32760). The data transfer is valid only
if the RL and BL values on VTOC are the following:
BL＝RL+4≦32760
Where RL＝BL≦32752 on VTOC, FX manages the data as shown:
RL(FX internal value) = RL(value on VTOC) + 4
BL(FX internal value) = BL(value on VTOC) + 8

To create an FCU parameter definition file using the FCU GUI for UNIX:
1. Start the FCU GUI for UNIX by entering fcu (see Starting the FCU GUI for
UNIX). Do not specify the -nw, -nc, or param option.
2. When the FCU main panel opens (see Performing File Transfer Operations
(UNIX)), enter the desired file name in the Parameter File field (with
complete path if you do not want to save the file in the current directory).
3. If you plan to perform FX operations while you are creating the FCU
parameter definition file, make sure that the Volume File field displays the
correct FX volume definition file (datasetmount.dat). If not (or if
incorrect), FCU will not be able to perform FX operations, but you can still
create a new FCU parameter definition file.
4. Select the File-Load command to open the new file.
5. Enter the desired FCU initiation parameters for the first FX operation:
– Select the file transfer direction using the M to O button or O to M
button.
– Enter the source and target files in the Input File and Output File
fields (VSN:dataset, filename with complete path if not in current
directory).
– Select the desired FCU file transfer options: Code Conversion,
Padding, Delimiter, Emp, RDW, and VSE. See Performing File
Transfer Operations (UNIX) for further information on these options.
6. When the FCU initiation parameters are correct, select the File-Save
command to add this parameter set as the first line in the new FCU
parameter definition file. If the FX volume definition file is correct, you can
perform the operation now by clicking OK. If the OK button is not enabled,
the parameter set has not been saved in the file.
7. Select the File-Load command to load the next line. The Status field
should indicate that you are at the end of the file. The FCU GUI for UNIX
only allows you to add new lines when you are at the end of the file (right
after the last line).
8. Repeat steps (5), (6), and (7) to add each parameter set to the new FCU
parameter definition file. Make sure to keep FX operations which use
OPEN-x FMT volumes in a separate FCU parameter definition file from
operations which use -A, -B, -C volumes.

5-14 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

 9. If you need to modify an existing line, go to the line to be modified using
the File-Load command, change the parameters as needed, and then use
the File-Save command to replace the line that was loaded.
10. If you need to insert a new line between existing lines, use a text editor
later to edit the file. You cannot add a new line between existing lines using
the FCU GUI for UNIX.
11. When you are finished adding lines to your new FCU parameter definition
file, make sure that you have selected the File-Save command for the last
parameter set you added or modified, and then select the File-Exit menu
command to close the file and exit FCU.

Creating Multiple Volume Definition Files (UNIX)

Multiple volume dataset is supported for FXmto, when the version is
01-XX-50/YY (XX=01 or 02) or later.

Multiple volume dataset is supported for FXotm when the version is

01-XX-60/YY (XX=02, 03 or 04) or later.

A multiple volume definition file (multidef.dat) is required in the current

directory where the FX is to be executed. If you want to change the name of
the multiple volume definition file, specify the other name in
“FAL_MULTI_DEF_FILE” of the environment variable.

Table 5-3 illustrates the VSN function.

Table 5-3 VSN Function

VSN:DSN[,VOLID1] VSN[,VOLID2] ----- VSN[,VOLIDn]

i) ii) iii) iv)
end
v)

1. This parameter is the information of the head volume:

– VSN: a volume serial number with six digit of alphabet (A-Z, @, #, and
\) or numeral (0-9) characters.
– DSN: dataset name.(Use maximum 44-digit of alphabet or numeral
character )
– VOLID1: a VSN identification ( Omit this parameter if a VSN
identification is omitted in the volume definition file, and specify same
as the volume definition file, if a VSN identification is specified in the
volume definition file.)

Performing Cross-OS File Exchange Operations 5-15

Hitachi Cross-OS File Exchange User’s Guide

 2. This parameter is the information of the second volume:
– VSN: a volume serial number with six digit of alphabet (A-Z, @, #, and
\) or numeral (0-9) characters.
– VOLID2: a VSN identification ( Omit this parameter if a VSN
identification is omitted in the volume definition file, and specify same
as the volume definition file, if a VSN identification is specified in the
volume definition file.)
3. This parameter is the information of the last volume.(The number of
volume is ‘n’):
– VSN: a volume serial number with six digit of alphabet (A-Z, @, #, and
\) or numeral (0-9) characters.
– VOLIDn: a VSN identification ( Omit this parameter if a VSN
identification is omitted in the volume definition file, and specify same
as the volume definition file, if a VSN identification is specified in the
volume definition file.)
4. Each line above must be separated by using “Return” key.
5. The “end” specifies that the volume definition file ends here.

Note: Each parameter must be separated with one or more “space”

character(s).

Note: One dataset information must be specified in one line.

Note: 999 information can be specified in the multiple volume definition file.

5-16 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Using FCU from the Command Line (UNIX)
FCU can be used without the GUI to perform FX operations. To use FCU
without the GUI, you must start FCU using the -nw option. The FCU options
are:
• The -nw option (nw = no Windows) tells FCU to execute the specified FX
operation(s) without displaying the GUI. When you use this option (entered
as fcunw or fcu -nw), FCU uses the FCU initiation parameters specified by
the param option to perform FX operations. To use FCU without the GUI,
the -nw option is required.
Note: FCU versions 01-01-36 and later for Windows systems do not
support the -nw option.
• The -nc option (nc = no checking) tells FCU to execute all specified FX
operations without requesting confirmation for FCU parameters or existing
FXmto target files. If you want to bypass these confirmations, enter -nc.
FCU will perform all specified operations and overwrite existing FXmto
target files. If you want to check the FCU parameters and the FXmto target
file before starting each operation, do not enter -nc.
• The param option (param = FCU parameter definition file) tells FCU
whether to use an 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 located in the current directory) to perform FX
operations, leave the param option blank (do not enter anything).
– file_name. If you want to use a different FCU parameter definition file
to perform FX operations, enter the filename of the file. Make sure to
enter the complete path (absolute or relative path) if the file is 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.

Note: FCU for UNIX cannot be used by a “signal handler.” If this accidentally
happens and memory space is occupied, use kill to cancel the processes, and
use ipcrm to delete the shared memory areas that have KEY=0 (refer to OS
manuals). Do not issue the following signals to an FCU process (UNIX only):
SIGUSR1, SIGUSR2, SIGILL, SIGTRAP, SIGIOT, SIGABRT, SIGEMT, SIGFPE,
SIGKILL, SIGBUS, SIGSEGV, SIGSYS, SIGALRM, SIGPOLL, SIGIO, SIGSTOP,
SIGTSTP, SIGCONT, SIGTTIN, SIGTTOU, SIGVTALRM, SIGPROF, SIGXCPU,
SIGXFSZ, SIGWAITING, SIGLWP, SIGFREEZE, SIGTHAW, SIGCANCEL

Performing Cross-OS File Exchange Operations 5-17

Hitachi Cross-OS File Exchange User’s Guide

 To perform FX operations using FCU without the GUI:
1. If you will be using an FCU parameter definition file to perform FX
operations, make sure that the file contains the correct FCU initiation
parameter sets for the FX operations you want to perform. If you will not
be using the default FCU parameter definition file, note the name and
location of the file.
2. Log in as root on the UNIX server, and enter: fcunw [-nc] [param]
For example (see Figures Figure 5-4, Figure 5-5, and Figure 5-6):
– To perform the FX operations in the default FCU parameter definition
file with confirmations, enter: fcunw
– To perform the FX operations in the default FCU parameter definition
file without confirmations, enter: fcunw -nc
– To perform the FX operations in a different FCU parameter definition file
with confirmations, enter: fcunw /directory/directory/file_name
– To perform the FX operations in a different FCU parameter definition file
without confirmations, enter: fcunw -nc /directory/directory/file_name
– To perform one specific FX operation with confirmations, enter:
fcunw -P mto VSN:dataset targetfile No No No
– To perform one specific FX operation without confirmations, enter:
fcunw -nc -P mto VSN:dataset targetfile No No No
3. If you specified the -nc option, FCU will perform all specified FX operations
without requesting confirmation for the FCU parameters or for existing
FXmto target files.
– If you did not specify the -nc option, FCU will display the FCU initiation
parameters for the operation to be performed and request confirmation.
Enter ok to perform the specified FX operation, or enter cancel to load
the next set of FCU parameters.
– If you did not specify the -nc option and the FXmto target file already
exists, FCU will request confirmation to overwrite the file. Enter ok to
overwrite the existing file, or enter cancel to load the next set of FCU
initiation parameters.
4. When the FX operation starts, FCU displays Start. When the operation
completes successfully, FCU displays Complete. If the operation does not
start or complete successfully, FCU displays an error message and loads
the next parameter set.
5. When the last FCU initiation parameter set is processed (or canceled by the
user), the FCU program terminates and returns an ending status value. The
ending status is included in $status for C-shell and $? for B-shell/K-shell.
0 = successful completion. All FX operations completed successfully.
1 = unsuccessful completion. One or more operations did not complete
successfully.

5-18 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

# fcunw ← Start FCU with checking.
File Conversion Utility Ver.01-01-40/00 ← FCU program version.

mto VSN:dataset file_name EA No LF ← First set of parameters.

ok/cancel ? ok ← Enter ok or cancel.
Now checking... ← Checking for target file.
Complete ← Operation completed.

otm file_name VSN:dataset EA No No ← Next set of parameters.

ok/cancel ? ok ← Enter ok or cancel.
Input file : Open error (-350)  Error info displayed.
(Fal error : xxx
(System error : xxx

mto VSN:dataset file_name EA No LF  Next set of parameters.

ok/cancel ? ok  Enter ok or cancel.
Now checking...  Checking for target file.
OverWrite ? ok/cancel ? ok  Enter ok to overwrite file.
Complete  Operation completed.

mto VSN:dataset file_name EA No LF  Next set of parameters.

ok/cancel ? cancel ← Enter ok or cancel.
:
:
#

Figure 5-4 Using FCU From the UNIX Command Line

# fcunw -nc  Start FCU without checking.

File Conversion Utility Ver.01-01-40/00  FCU program version.

mto VSN:dataset file_name EA No LF  First set of parameters.

Now checking...  Starting FX operation.
Complete  Operation completed.

otm file_name VSN:dataset EA No No  Next set of parameters.

Input file : Open error (-350)  Error info. displayed.
(Fal error : xxx
(System error : xxx

mto VSN:dataset file_name EA No LF  Next set of parameters.

Now checking...  Starting FX operation.
Complete  Operation completed.

mto VSN:dataset file_name EA No LF  Next set of parameters.

:
#

Figure 5-5 Using the -nc Option

# fcunw -nc -P mto VSN:dataset file_name EA No LF  Start FCU without checking.

mto VSN:dataset file_name EA No LF  Specified FCU parameters.

Now checking...  Starting FX operation.
Complete  Operation completed.
#

Figure 5-6 Using the -P param Option

Performing Cross-OS File Exchange Operations 5-19

Hitachi Cross-OS File Exchange User’s Guide

Performing File Transfer Operations – Windows
Starting the FCU GUI
To start the FCU GUI program for Windows systems:
1. Log on with Administrator access privileges.
2. Start the FCU GUI as follows: Click Start-Programs-FCU-FCU, or open
the c:\ folder and double-click on FCU, or create a shortcut for FCU on the
desktop.
Note: Do not start FCU by dragging and dropping an FCU parameter
definition file on the FCU program icon. FCU program operation cannot be
guaranteed.
3. If you want to specify any of the FCU options, start FCU from the command
line (DOS prompt) as follows: Go to the FCU directory (containing fcu.exe
and datasetmount.dat), and enter fcu [-nc] [-cl] [param]
The -nc option is the same as for UNIX: All specified FX operations are
performed without confirmation of FCU parameters or FXmto target file
overwrites.
The -cl option specifies that all FCU log files will be cleared before starting.
The param option is the same as for UNIX:
– If you want to open a new untitled FCU parameter definition file when
you start FCU, leave the param option blank.
– If you want to load an FCU parameter definition file when you start
FCU, enter the file name with complete path if the file is not in the
current directory.
4. The FCU GUI program now starts loading. The FCU version and copyright
screen (see Figure 5-7) is displayed while FCU is loading. When FCU is
finished loading, the FCU main panel is displayed (see Performing File
Transfer Operations (UNIX)).
5. If you started FCU from the DOS prompt and specified the -nc option, FCU
processes all specified operations, overwrites existing FXmto target files,
and then terminates and displays any error information at the DOS prompt.

5-20 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

 Figure 5-7 FCU Version and Copyright Screen (Windows Systems)

Performing File Transfer Operations (Windows)

To perform FX file transfer operations using the FCU GUI for Windows
systems:
1. If you will be performing FXmto operations:
a. Make sure that the source datasets are located on the desired FX
volume(s). If you will not be using an existing FCU parameter definition
file, write down the VSN:dataset of the source dataset and the complete
path and file name of the target file for each FXmto operation.
b. Verify that the FXmto target files do not already exist (or can be
overwritten).
c. Vary the FXmto volume(s) and channel path(s) offline from the
mainframe host.
2. If you will be performing FXotm operations:
a. Make sure that the source files are located on the desired FX volume(s).
If you will not be using an existing FCU parameter definition file, write
down the complete path and file name of the source file and the
VSN:dataset of the target dataset for each FXotm operation.
b. Create and allocate the target datasets. This ensures that the target
dataset is registered in the VTOC. Make sure to allocate enough space
and to use the appropriate record format and record length for the data
to be transferred.
c. Vary the FXotm volume(s) and channel path(s) offline from the
mainframe host.

Performing Cross-OS File Exchange Operations 5-21

Hitachi Cross-OS File Exchange User’s Guide

 3. If you will be performing FXoto operations:
a. If you will not be using an existing FCU parameter def. file, write down
the complete path and file name of the source and target files for each
FXotm/mto operation.
b. Use the ALC utility to allocate the intermediate datasets on the FXoto
volume(s). Make sure to allocate enough space and to use the
appropriate record format and record length for the data to be
transferred.
c. Verify that the FXoto target files do not already exist (or can be
overwritten).
4. Make sure that the desired FX volume definition file (FXoto only, or FXmto
and FXotm) is available for use by FCU (datasetmount.dat in current
directory).
5. Start FCU (see Starting the FCU GUI). If you want to specify any FCU
options, start FCU from the DOS prompt.
Note: If you specify the -nc option, FCU performs all specified operations
continuously, then self-terminates and displays any error information at
the DOS prompt.
6. When the FCU main panel opens, select the View-Volume information…
command ( ) to open the Volume information panel, and verify that the
desired FX volume(s) is/are available. If not, edit the FX volume definition
file as needed.
7. Make sure that the desired FCU parameter definition file is open (displayed
in title bar). If not, open the desired FCU parameter definition file using the
File-Open command ( ). If you want to create a new file using the FCU
GUI, see Creating FCU Parameter Definition Files (Windows) for
instructions.
8. The FCU main panel displays the first/next parameter set in the specified
FCU parameter definition file. If you want to perform this FX operation,
click Execute. If not:
a. You can load the next parameter set using the Parameter-Load-Next
command ( ).
b. You can delete the current parameter set from the FCU parameter
definition file using the Parameter-Delete command ( ). The next
parameter set loads automatically.
c. You can modify the current parameter set as follows: Change the FCU
parameters as needed, and then use the Parameter-Save-Replace
command ( ) to replace the previously loaded parameter set with the
new parameter set.
d. You can add a new parameter set as follows: Change the FCU
parameters as needed, and use the Parameter-Save-Insert command
( ) to insert the new parameter set below the current parameter set.

5-22 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

 e. If the Continuous operation option is selected, you can open the Error
information panel before starting the operations to monitor the FCU
processing. Move the Error information panel so that it does not overlap
the FCU main panel.
9. When the desired FX operation is displayed, click Execute to start the
operation. (If the Execute button is not enabled, you have not saved the
current parameter set.) If the Continuous operation option was selected,
FCU will process all operations from the current line to the end of the file
and then self-terminate. The error information for these operations is
placed in the most recent .log file(s) in the current directory (e.g.,
mto.log).
WARNING: In some early versions of FCU for Windows systems, FCU may
overwrite existing Windows systems target files without requesting
confirmation.
10. If you started an FXmto operation and the target file already exists, FCU
requests overwrite confirmation. Click OK to overwrite the target file, or
click Cancel to cancel the operation.
11. When FCU starts the operation, the Execute panel opens and displays the
progress of the operation. To cancel the operation in progress, select
Cancel.
Note: The Execute dialog panel will not appear when the mainframe OS is
VSE.
12. When the operation is complete, the Execute panel displays the result. If
an error occurred, the Error information panel opens automatically to
display the error. See Error Codes and Messages for further information on
errors.
13. FCU does not load the next operation automatically. To perform another FX
operation, select the desired Parameter-Load command, and repeat steps
(8) through (12). To exit FCU, select the File-Exit command.

Note: After an FXotm file transfer from Windows systems, there will be a
delay before you can access the FX volume. The length of delay varies
according to individual server performance.

Note: After you expand open volumes (LUSE), you will need to reboot
Windows systems.

Note: Do not use the open system host to access an FX volume. Use only FAL
to access FX volumes. This applies to PC server platforms (e.g., NT) and
UNIX-based systems.

Note: The Cancel button changes to Close after the operation ends
abnormally.

Performing Cross-OS File Exchange Operations 5-23

Hitachi Cross-OS File Exchange User’s Guide

 Figure 5-8 Execute Panel Showing Normal End

Figure 5-9 Execute Panel Showing Canceled Operation

Figure 5-10 Execute Panel Showing Error End

5-24 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

Creating FCU Parameter Definition Files (Windows)
See the description in section Creating FCU Parameter Definition Files (UNIX).

To create an FCU parameter definition file using the FCU GUI for Windows
systems:
1. Start the FCU GUI for Windows systems (see Starting the FCU GUI). If you
start FCU from the DOS prompt, enter fcu (do not specify the -nc or
param option).
2. When the FCU main panel opens, the title bar should display Untitled to
indicate that a new parameter definition file is open. If a file name is
displayed instead of Untitled, use the File-New command ( ) to open a
new parameter definition file.
3. If you plan to perform FX operations while you are creating the FCU
parameter definition file, open the Volume information panel (select
View-Volume information…), and make sure that the desired FX
volume(s) is/are available. If not, FCU will not be able to perform FX
operations, but you can still create a new parameter definition file.
4. Enter the desired FCU initiation parameters for the first FX operation.

– Use the buttons to select the transfer direction (M to O or O to

M).
– Enter the source and target datasets/files in the Mainframe File field
(VSN:dataset), and/or Open-system file field (/directory/…/filename).
– Open the Option panel using the View-Option… menu command ( ),
and then select the desired FCU options (code conversion, padding,
delimiters, etc.). Do not select Continuous execution or Clear log
file when creating a new FCU parameter definition file. Close the Option
panel when you are done.
5. When the FCU initiation parameters are correct, select the
Parameter-Save-Insert command ( ) to save the current parameter
set in the new FCU parameter definition file. The status bar now displays
1/1 to indicate that line one of one is now being displayed. If the FX
volume is available, you can perform the operation now by clicking
Execute. If the Execute button is not enabled, the parameter set has not
been saved in the file.
6. Repeat steps (4) and (5) to add each new FCU initiation parameter set to
the new FCU parameter definition file. If desired, you can use the
Parameter-Wipe menu command ( ) to clear the screen before you
enter the next set of parameters, or you can leave the parameters and
make changes where needed to specify the next new line in the file. Make
sure to keep FX operations which use OPEN-x FMT volumes in a separate
FCU parameter definition file from operations which use -A, -B, and -C
volumes.

Performing Cross-OS File Exchange Operations 5-25

Hitachi Cross-OS File Exchange User’s Guide

 7. If you need to insert a new line between two existing lines, go to the line
above/before the line to be inserted using the Parameter-Load
commands ( ), change the parameters as needed, and then use
the Parameter-Save-Insert command ( ) to insert the new line. The
new line is inserted below/after the current line number.
8. If you need to modify an existing line, go to the line to be modified using
the Parameter-Load commands, change the parameters as needed, and
then use the Parameter-Save-Replace command ( ) to modify the line
as specified.
9. When you want to save your new FCU parameter definition file, select the
File-Save menu command ( ). The file extension must be .prm.

Creating Multiple Volume Definition Files (Windows)

Multiple volume dataset is supported for FXmto, when the version is
01-XX-50/YY (XX=01 or 02) or later.

Multiple volume dataset is supported for FXotm, when the version is

01-XX-60/YY (XX=02, 03, or 04) or later.

A multiple volume definition file (multidef.dat) is required in the current

directory where the FX is to be executed. If you want to change the name of
the multiple volume definition file, specify the other name in
“FAL_MULTI_DEF_FILE” of the environment variable.

Table 5-4 illustrates the VSN function.

Table 5-4 VSN Function

VSN:DSN[,VOLID1] VSN[,VOLID2] ----- VSN[,VOLIDn]

i) ii) iii) iv)
end
v)

1. This parameter is the information of the head volume:

– VSN: a volume serial number with six digit of alphabet (A-Z, @, #, and
\) or numeral (0-9) characters.
– DSN: dataset name.(Use maximum 44-digit of alphabet or numeral
character )
– VOLID1: a VSN identification ( Omit this parameter if a VSN
identification is omitted in the volume definition file, and specify same
as the volume definition file, if a VSN identification is specified in the
volume definition file.)

5-26 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

2. This parameter is the information of the second volume:
– VSN: a volume serial number with six digit of alphabet (A-Z, @, #, and
\) or numeral (0-9) characters.
– VOLID2: a VSN identification ( Omit this parameter if a VSN
identification is omitted in the volume definition file, and specify same
as the volume definition file, if a VSN identification is specified in the
volume definition file.)
3. This parameter is the information of the last volume.(The number of
volume is ‘n’):
– VSN: a volume serial number with six digit of alphabet (A-Z, @, #, and
\) or numeral (0-9) characters.
– VOLIDn: a VSN identification ( Omit this parameter if a VSN
identification is omitted in the volume definition file, and specify same
as the volume definition file, if a VSN identification is specified in the
volume definition file.)
4. Each line above must be separated by using “Return” key.
5. The “end” specifies that the volume definition file ends here.

Note: Each parameter must be separated with one or more “space”

character(s).

Note: One dataset information must be specified in one line.

Note: 999 information can be specified in the multiple volume definition file.

Performing Cross-OS File Exchange Operations 5-27

Hitachi Cross-OS File Exchange User’s Guide

Using FCU from the Command Line (Windows)
To perform FX file transfer operations for Windows systems in a non-GUI
environment:
1. Log-in as a user who has administrator privileges.
2. Open the command prompt (DOS Windows) and input the parameters
below:
– fcunw [-cl] [param] ( [-v] )
– -cl : Specifying that all the log file for FCU will be cleared before
stating FCU.
– param :This parameter is used as same as (1) in this section for
UNIX.

Note: When this parameter is not specified, the file name of the “Parameter
definition file” will be assumed to be “fcudata.prm” and it will attempt to read
the detail parameters from the file.
– -v : This displays the version of fcunw.

Note: This parameter cannot be used with any other parameter

simultaneously, as it specifies versions.
– [Return value] 0: Normal end
– [Return value] 1: Error end.

Note: The fcunw command requires the “Parameter definition file” to

function properly. If there is no “Parameter definition file” or if there is an
incorrect parameter in the “Parameter definition file”, the following message
will be displayed:
– [ A parameter definition file doesn’t exist, or it is illegal. ]

5-28 Performing Cross-Os File Exchange Operations

Hitachi Cross-OS File Exchange User’s Guide

 6
Performing File Access Library (FAL)
Operations
This chapter describes how to perform FAL operations using FX.
FAL Requirements
FAL Functions
Using the FAL Functions
Multi-Thread Function
Compiling
Error Information
FAL Usage Scenario

The FAL component of FX consists of the object module file fal.o (fal.obj for
Windows systems) and the header file dataset.h. The FAL provides several
important C functions (Visual C++ for Windows systems) that enable user
applications on the open-system hosts to access mainframe data on the
Hitachi RAID storage system volumes. There are two types of FAL, the 32bit
FAL and the 64bit FAL. The 64bit FAL is provided by the USP V/VM and
TagmaStore USP/NSC storage systems.

Performing File Access Library (FAL) Operations 6-1

Hitachi Cross-OS File Exchange User’s Guide

FAL Requirements
The FAL functions have the same dataset requirements as FCU (e.g., SAM,
standard R0 track format). The FAL also has the following additional
requirements:
• The FAL functions support only standard MVS VTOC. The FAL functions
cannot access MVS datasets managed by an index VTOC and cannot access
VSE datasets when called from user applications.
• The FAL functions are not “thread-safe.” The FAL functions may not
operate properly when used by multiple threads within a single process.
• The FAL functions cannot be used by a “signal handler.” If this accidentally
happens and memory space is occupied, use kill to cancel the processes,
and use ipcrm to delete the shared memory areas that have KEY=0 (refer
to OS manuals). Do not issue the following signals to an FX process (UNIX
only):
SIGUSR1, SIGUSR2, SIGILL, SIGTRAP, SIGIOT, SIGABRT, SIGEMT,
SIGFPE, SIGKILL, SIGBUS, SIGSEGV, SIGSYS, SIGALRM, SIGPOLL, SIGIO,
SIGSTOP, SIGTSTP, SIGCONT, SIGTTIN, SIGTTOU, SIGVTALRM, SIGPROF,
SIGXCPU, SIGXFSZ, SIGWAITING, SIGLWP, SIGFREEZE, SIGTHAW,
SIGCANCEL
• The following terminology is reserved for the FAL functions and cannot be
used in function names, variable names, or constant symbols in the user
application:
– Words that begin with dataset or fast_
– GetVolSers

6-2 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

FAL Functions
The FAL includes the following C functions (Visual C++ for Windows systems):
• Opening a dataset: datasetOpen (see Opening a Dataset)
• Reading one record from a dataset: datasetGet (see Reading Data)
• Writing one record to a dataset: datasetPut (see Writing Data)
• Closing a dataset: datasetClose (see Closing a Dataset)
• Acquiring error information: datasetGetLastError (see Acquiring Error
Information)
• Acquiring dataset attribute information (see Acquiring Dataset Attributes):
datasetGetFileInformation datasetFindNextFile
datasetFindFirstFile datasetFindClose

Converting Dataset Attribute Information

See Converting DO and RF Information):

datasetGetDsorgString datasetGetRecfmString

Performing File Access Library (FAL) Operations 6-3

Hitachi Cross-OS File Exchange User’s Guide

Opening a Dataset
datasetHandle = datasetOpen (pathname, mode)

The datasetOpen function opens the dataset specified by pathname for the
type of access specified by mode. Table 6-1 shows the datasetOpen
arguments and return values.

Table 6-1 DatasetOpen Function

Item Value Type Description

Argument pathname char * VSN:Dataset name

VSN = 6-character volser.
Volume must be listed in FX volume
definition file.
Delimiter = : (colon, no spaces allowed)
mode char * Dataset name: 44 characters max, no
spaces allowed.
r = open dataset for read access
w = open dataset for write access

Return datasetHandle DATASET_HANDLE Handle

value -1 Abnormal end

When the datasetOpen function terminates successfully, it returns a handle

which identifies the dataset opened. The datasetHandle information is used
as the argument of subsequent functions such as datasetGet, datasetPut, or
datasetClose. Do not change the datasetHandle value returned by this
function. If the datasetOpen function terminates unsuccessfully, it returns a
value of -1. To get the error code information, execute the
datasetGetLastError function (see Acquiring Error Information).

The datasetOpen function has the following restrictions:

• Only one dataset at a time can be open within one process. When multiple
datasets need to be opened, the open dataset must be closed before
another dataset can be opened. This restriction does not apply to
open-system files.
• A dataset which is being accessed by the datasetFindFirstFile or
datasetFindNextFile function cannot be opened. The datasetFindClose
function must be executed before the dataset can be opened. This
restriction does not apply to open-system files.

6-4 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Reading Data
reclen = datasetGet (datasetHandle, buf, buflen)

The datasetGet function reads one record from the specified dataset
(datasetHandle) and puts the record into a buffer (buf) of length buflen.
The datasetGet function extracts only the data entity from each record and
does not transfer the BL and RL bytes for variable-length records to the buffer.
Table 6-2 shows the datasetGet arguments and return values.

Table 6-2 DatasetGet Function

Item Value Type Description

Argument datasetHandle DATASET_HANDLE The datasetHandle value returned by the

datasetOpen function.
buf Buffer area for storing the read data.
char *
buflen Size of the buffer area. If the record is larger
long
than buflen or equal to zero, datasetGet
returns an error and does not transfer any
data to the buf.

Return reclen long Data entity size transferred to the buffer

value -1 Abnormal end

Figure 6-1 shows the format requirements for variable-length records accessed
by the datasetGet function. Each variable-length block must start with the
two-byte BL field, and each variable-length record must start with the
two-byte RL field. The datasetGet function automatically extracts the data
entities without the BL and RL fields.

Block length Record length Data entity Record length Data entity
Record length Record length
Block Length

2 bytes 2 bytes
Block length format: Block length 0x0000

2 bytes 2 bytes
Record length format: Record length 0x0000

Figure 6-1 Format Requirements for Reading Variable-Length Records

When the datasetGet function terminates successfully, it returns the length of

the data entity read from the dataset. If the datasetGet function detects the
end of dataset (EOF) or terminates unsuccessfully, it returns a value of -1. To
get the error code information, execute the datasetGetLastError function
(see Acquiring Error Information). For example, when the datasetGet function
detects EOF, datasetGetLastError will return
DATASET_ERROR_END_OF_FILE.

Performing File Access Library (FAL) Operations 6-5

Hitachi Cross-OS File Exchange User’s Guide

Writing Data
reclen = datasetPut (datasetHandle, buf, buflen)

The datasetPut function writes one record from the buf into the dataset
specified by datasetHandle. Table 6-3 shows the datasetPut arguments and
return values.
Table 6-3 DatasetPut Function
Item Value Type Description

Argument datasetHandle DATASET_HANDLE The datasetHandle value returned by the

datasetOpen function.
buf Buffer area for storing the write data.
char *
buflen Size of the buffer area. If any of the following
long
conditions is detected, datasetPut returns an
error and does not transfer any data to the
dataset:
ƒ For fixed-length record:
buflen ≠ RL of the dataset
ƒ For variable-length record:
(buflen + 4) > RL of dataset
ƒ For variable-length record:
buflen = 0 (no data entity)

Return reclen long Data entity size written into the dataset.
value -1 Abnormal end

Figure 6-2 shows the format requirements for variable-length records accessed
by the datasetPut function. When the target dataset is variable-length, the
datasetPut function takes the data entity from the buf, automatically adds
the two-byte RL field, and writes the record into the dataset. When the data is
written into the dataset, multiple records are blocked within the extent defined
by the VTOC of the dataset.

Block length Record length Data entity Record length Data entity
Record length Record length
Block Length (≤block length defined in VTOC)

2 bytes 2 bytes
Block length format: Block length 0x0000

2 bytes 2 bytes
Record length format: Record length 0x0000

Figure 6-2 Format Requirements for Writing Variable-Length Records

When the datasetPut function terminates successfully, it returns the length of

the data entity written to the dataset. If the datasetPut function terminates
unsuccessfully, it returns a value of -1. To get the error code information,
execute the datasetGetLastError function (see Acquiring Error Information).

6-6 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Closing a Dataset
datasetError = datasetClose (datasetHandle)

The datasetClose function closes the dataset specified by datasetHandle,

which is returned by the datasetOpen function. Table 6-4 shows the
datasetClose arguments and return values.

Table 6-4 DatasetClose Function

Item Value Type Description

Argument datasetHandle DATASET_HANDLE The datasetHandle value returned by the

datasetOpen function.

Return 0 Normal end

value
-1 Abnormal end

When the datasetClose function terminates successfully, it returns a value of

0. If it terminates unsuccessfully, it returns a value of -1. To get the error
code information, execute the datasetGetLastError function (see Acquiring
Error Information).

Acquiring Error Information

datasetLastError = datasetGetLastError()

The datasetGetLastError function acquires the error code information for the
most recent error. Errors in FAL functions are defined in dataset.h (see
Troubleshooting). Errors in UNIX are defined by a standard error file
(errno.h). Errors in Windows systems are defined by errno.h attached with
Microsoft Visual C++. Table 6-5 shows the datasetClose arguments and
return values.

Table 6-5 DatasetGetLastError Function

Item Value Type Description

Argument none — —

Return value datasetLastError Long Error code

Performing File Access Library (FAL) Operations 6-7

Hitachi Cross-OS File Exchange User’s Guide

Acquiring Dataset Attributes
FAL provides several functions for acquiring the complete dataset attribute
information for one or more datasets: datasetGetFileInformation,
datasetFindFirstFile, datasetFindNextFile, and datasetFindClose. The
dataset attribute information returned by these functions contains:

typedef struct DATASET_FIND_DATA {

unsigned short blockSize; /* Block length */
unsigned short recordSize; /* Record length */
unsigned char dsorg[2]; /* dataset type */
unsigned char recfm; /* record format */
char name[44]; /* dataset name */
unsigned short lastBlockTt; /* last block address (relative track number) */
unsigned char lastBlockR; /* last block address (relative record number)*/
} DATASET_FIND_DATA;

Acquiring Attribute Information for a Specific Dataset

datasetError = datasetGetFileInformation (pathname, &ffd)

The datasetGetFileInformation function acquires the attribute information

for the dataset specified by pathname and returns the data into ffd.
Table 6-6 shows the datasetGetFileInformation arguments and return
values.

Table 6-6 DatasetGetFileInformation Function

Item Value Type Description

Argument pathname char * Path name (VolumeName:DatasetName (VSN

identification))
ƒ Volume name = 6-character VSN
ƒ Delimiter = : (colon, no spaces)
ƒ Dataset name = 44 characters max, no spaces
ƒ VSN = Same VSN identification in the Volume
Definition File. (It is possible to omit this
parameter.)

Return ffd DATASET_FIND_DATA Attribute information (area where dataset attribute

value information is stored)
0 Normal end
-1 Abnormal end

When the DatasetGetFileInformation function terminates successfully, it

returns a value of 0. If it terminates unsuccessfully, it returns a value of -1. To
get the error code information, execute the datasetGetLastError function
(see Acquiring Error Information).

The DatasetGetFileInformation function has the following restriction:

• The DatasetGetFileInformation function cannot be used on an open
dataset. Use this function before opening or after closing the dataset.

6-8 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Acquiring Attribute Information for Multiple Datasets

A combination of the datasetFindFirstFile, datasetFindNextFile, and

datasetFindClose functions is used to acquire attribute information for more
than one dataset in the specified mainframe volume.
1. datasetHandle = datasetFindFirstFile (pathname, &ffd)
The datasetFindFirstFile function acquires the attribute information for
the first dataset in the volume specified by pathname and returns the
data into ffd. Table 6-7 shows the datasetFindFirstFile arguments and
return values.

Table 6-7 DatasetFindFirstFile Function

Item Value Type Description

Argument pathname char * Path name (VolumeName:DatasetName

(VSN identification))

Return ffd DATASET_FIND_DATA Attribute information (area where the dataset

value attribute information is stored)
datasetHandle DATASET_HANDLE Normal end
-1 Abnormal end

When the datasetFindFirstFile function terminates successfully, it returns

a handle which identifies the dataset for which the attribute information
was acquired. The datasetHandle information is used as the argument of
the subsequent functions datasetFindNextFile and datasetFindClose.
Do not change the datasetHandle value returned by this function. If the
datasetFindFirstFile function terminates unsuccessfully, it returns a value
of -1. To get the error code information, execute the datasetGetLastError
function (see Acquiring Error Information). For example, when the
datasetFindFirstFile function does not find any datasets in the VTOC, the
datasetGetLastError function will return
DATASET_ERROR_END_NO_DATASET.
The datasetFindFirstFile function has the following restrictions:
– The datasetFindFirstFile function cannot be used on an open dataset.
Use this function before opening or after closing the dataset.
– After a dataset has been accessed by the datasetFindFirstFile function,
the dataset cannot be opened until after the datasetFindClose function
is called.
2. datasetError = datasetFindNextFile (datasetHandle, &ffd)
The datasetFindNextFile function acquires the attribute information for
the next dataset in the volume specified by datasetHandle and returns
the data into ffd. This function can be repeated until “no dataset found” is
returned, or until the user application determines that no more information
is needed. Table 6-8 shows the datasetFindNextFile arguments and
return values.

Performing File Access Library (FAL) Operations 6-9

Hitachi Cross-OS File Exchange User’s Guide

 Table 6-8 DatasetFindNextFile Function
Item Value Type Description

Argument datasetHandle DATASET_HANDLE DatasetHandle (value returned by the

preceding datasetFindFirstFile function)

Return ffd DATASET_FIND_DATA Attribute information (area where the dataset

value 0 attribute information is stored)
Normal end
-1
Abnormal, or no dataset found

When the datasetFindNextFile function terminates successfully, it returns

a value of 0. If this function terminates unsuccessfully, it returns a value of
-1. To get the error code information, execute the datasetGetLastError
function (see Acquiring Error Information). For example, when the
datasetFindNextFile function cannot find the next dataset in the VTOC,
the datasetGetLastError function will return
DATASET_ERROR_END_OF_VTOC.
The datasetFindNextFile function has the following restrictions:
– The datasetFindNextFile function cannot be used on an open dataset.
Use this function before opening or after closing the dataset.
– After a dataset has been accessed by the datasetFindNextFile function,
the dataset cannot be opened until after the datasetFindClose function
is called.
– The datasetFindFirstFile function must be called prior to
datasetFindNextFile.
3. datasetError = datasetFindClose (datasetHandle)
The datasetFindClose function terminates the acquisition of attribute
information by the datasetFindFirstFile and datasetFindNextFile
functions and closes the dataset. The datasetFindFirstFile function must
be called prior to datasetFindClose. Table 6-9 shows the
datasetFindClose arguments and return values.

Table 6-9 DatasetFindClose Function

Item Value Type Description

Argument datasetHandle DATASET_HANDLE DatasetHandle (value returned by the preceding

datasetFindFirstFile function)

Return 0 Normal end

value
-1 Abnormal end

When the datasetFindClose function terminates successfully, it returns a

value of 0. If this function terminates unsuccessfully, it returns a value of
-1. To get the error code information, execute the datasetGetLastError
function (see Acquiring Error Information).

6-10 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Converting DO and RF Information
The FAL provides two functions for converting specific attribute information
from a dataset into character strings: datasetGetDsorgString, and
datasetGetRecfmString.

Converting the Dataset Organization (DO) Type Value

datasetError = datasetGetDsorgString (dsorg, text)
The datasetGetDsorgString function converts the dataset organization (DO)
type to a three-byte character string. The DO type is specified by dsorg[2] in
DATASET_FIND_DATA. Table 6-10 lists the datasetGetDsorgString
arguments and return values.

Table 6-10 DatasetGetDsorgString Function

Item Value Type Description

Argument dsorg u_char[ ] Dataset organization type value (2 bytes)

Sets the value of dsorg[], a member of DATASET_FIND_DATA, which
is obtained by datasetGetFileInformation, datasetFindFirstFile,
or datasetFindNextFile to dsorg.

text char [3] Dataset organization type character string (3 bytes):

PS physical sequential organization
VS VSAM organization
DA direct access organization
PO Partial organization
** Other than above
Return 0 Normal end
value
-1 Abnormal end

Performing File Access Library (FAL) Operations 6-11

Hitachi Cross-OS File Exchange User’s Guide

Converting the Record Format (RF) Type Value
datasetError = datasetGetRecfmString (recfm, text)
The datasetGetRecfmString function converts the record format (RF) type to
a five-byte character string. The RF type is specified by recfm in
DATASET_FIND_DATA. Table 6-11 lists the datasetGetRecfmString
arguments and return values.

Table 6-11 DatasetGetRecfmString Function

Item Value Type Description

Argument recfm u_char Record type value (1 byte)

Sets value of recfm, a member of DATASET_FIND_DATA, which is
obtained by datasetGetFileInformation/ datasetFindFirstFile/
datasetFindNextFile, to recfm.

text char [5] Record type character string (5 bytes):

text[0]: “F”: Fixed length record
“V”: Variable length record
“U”: Unknown length record
text[1]: “B”: Blocking record
“sp”: Spanned record
“st”: Standard format record
Return 0 Normal end
value
-1 Abonormal end

6-12 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Using the FAL Functions
The FAL functions can be executed by any C program on the UNIX host. The
FAL does not support C++®. The mainframe datasets accessed by the FAL
functions must be located on FX volumes. The FX volumes must be installed
and configured correctly (see Installing and Configuring the FX Volumes), the
FX software must be installed properly (see Installing the FX Software), and
the FX volume definition file must be available and configured correctly. Since
FAL operations do not involve GUI windows, the X windows environment and
FcuMf resource file are not required.

Figure 6-3 shows an example of reading data using the FAL functions.
Figure 6-4 shows an example of acquiring attribute information using the FAL
functions. To use the FAL functions in a C program (Visual C++ for Windows
systems):
1. Copy the FX volume definition file (datasetmount.dat) to the directory
containing the C program that will call the FAL C function(s).
2. Include the FAL header file (dataset.h) within the C program that will call
the FAL function(s) (e.g., copy dataset.h to /usr/include).
3. Using 32bit FAL, compile the C program as follows:
IBM AIX
# cc -qlanglvl=ansi —D_NO_MT -o Output file name Source file
name /usr/lib/libfal.a
libfal.a = file name of FAL object module
HP-UX
# cc -Ae +DAportable —D_NO_MT -o Output file name Source
file name /usr/lib/libfal.sl
libfal.sl = file name of FAL object module
Solaris
# cc —D_NO_MT -o Output file name Source file name
/usr/lib/libfal.so.1
libfal.so.1 = file name of FAL object module
DIGITAL UNIX/Tru64
# c89 —D_NO_MT -o Output file name Source file name
/usr/lib/libfal.so
libfal.so = file name of FAL object module
Linux
# gcc —D_NO_MT -o Output file name Source file name
/usr/lib/libfal.so.1
libfal.so.1 = file name of FAL object module

Performing File Access Library (FAL) Operations 6-13

Hitachi Cross-OS File Exchange User’s Guide

 4. Using 64bit FAL, compile the C program as follows:
IBM AIX
# cc -qlanglvl=ansi -q64 —D_NO_MT -o Output file name Source
file name /usr/lib/libfal64.a
libfal64.a = file name of FAL object module
HP-UX
# cc -Ae +DAZ.0W —D_NO_MT -o Output file name Source file
name /usr/lib/pa20_64/libfal64.sl
libfal64.sl: = file name of FAL object module.
Solaris
# cc xarch=v9 —D_NO_MT -o Output file name Source file name
/usr/lib/sparcv9/libfal64.so.1
libfal64.so.1: = file name of FAL object module.
Linux
# gcc -o Output file name Source file name /usr/lib/libfal.so.1
libfal.so.1:
This specifies a file name of the object module of the File Access
Library.
Windows systems (Visual C++)
Start Developer Studio and create a new project.
a) Copy the following three FAL files into the project folder:
dataset.h, fal.dll, fal.lib
b) Select Settings in the Projects menu of Developer Studio.
c) On the Project Settings panel, select the Link tab.
d) Enter fal.lib in the object/library module field.
e) Select the C/C++ tab in Project settings dialog.
f) Add _NO_MT to the preprocessor definitions field.
e) Build and execute.

6-14 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

 Acquire attribute information
datasetGetFileInformation
for the dataset.

Error

Confirm the
dataset attributes.

datasetOpen Open the dataset.

Error

datasetGet Read one data record.

Error

EOF

Process the data

that has been read.

datasetGetLastError Acquire error information.

datasetClose Close dataset.

Error processing/termination.

datasetGetLastError Acquire error information.

Error processing/termination.

Figure 6-3 Example of Reading Data from a Mainframe Dataset

Using FAL

Performing File Access Library (FAL) Operations 6-15

Hitachi Cross-OS File Exchange User’s Guide

 Acquire attribute information
datasetFindFirstFile for the first dataset.

Error

To convert the DO or RF type

List the dataset into a character string, use:
attribute information. - datasetGetDsorgString, or
- datasetGetRecfmStrng.
Error

Acquire attribute information

datasetFindNextFile for the next dataset.
Error

To convert the DO or RF type

List the dataset into a character string, use:
attribute information. - datasetGetDsorgString, or
- datasetGetRecfmStrng.
Error

datasetGetLastError Get error information.

datasetFindClose End of the process.

datasetGetLastError Get error information.

Figure 6-4 Example of Acquiring MF Dataset Attributes Using FAL

6-16 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Multi-Thread Function
Specifications: FAL provides the following functions (C programming
language):
• Information storage area: dataset_AllocGlobal
• Open a dataset specified by volume name and dataset name:
dataset_Open
• Read a record specified by dataset: dataset_Get/dataset_Get2
• Write a record specified by dataset: dataset_Put/dataset_Put2
• Close a specified dataset: dataset_Close
• Free storage area: dataset_FreeGlobale
• Return a file pointer to top: dataset_Rewind
• Get a dataset attribute: dataset_GetFileInformation,
dataset_FindFirstFile, dataset_FindNextFile, dataset_FindClose

Programming Restrictions:
• You cannot use FX from the Signal Handler.
• The words listed below are reserved words. When the user creates a
program using FAL, these words cannot be used for function names,
variable names, symbol names, or constant names:
– dataset
– fast_
– GetVolSers
• Do not mix the FX multi-thread function with user API for multi-thread and
user API for non-multi-thread.
• This function is only applicable for AIX and Windows (32bit versions).
• You do not need a volume definition file when user uses API for
multi-thread.
• You can open multiple datasets simultaneously using multi-thread API:
dataset_AllocGlobal… Reserve an area for information of dataset “A”.
dataset_AllocGlobal… Reserve an area for information of dataset “B”.
dataset_Open… Open dataset “A”.
dataset_Open… Open dataset “B”.

Performing File Access Library (FAL) Operations 6-17

Hitachi Cross-OS File Exchange User’s Guide

Information Storage Area
Format: memError= dataset_AllocGlobal(dgpp,derrno,malloc,free)
(Table 6-12)

Table 6-12 Arguments, Types, and Descriptions for Information Storage

Area
Argument Type Description

dgpp void (see Note 2) Global memory area

derrno long (see Note 1) An error information stored area
malloc void (see Note 2) malloc()
free void (see Note 1) free()

Return value: memError int

0 Abnormal end

Note 1: When you issue this function, you must issue dataset_FreeGlobal()
in the end process.

Note 2: You must issue this function before dataset_Open() and

dataset_FindFirstFile().
• Arguments:
– dgpp: Global memory area stored area
– derrno: Return an address stored FAL error code
– malloc: Specify an address of malloc function. Specify as malloc.
– free: Specify an address of free function. Specify as free.
• Return Value:
– When this function ends normally, it returns a 1.
– When this function ends abnormally, it returns a 0. For further
information, see Troubleshooting.
• Example:

void *memptr; /* global memory area */

long err; /* global err information */
int retcode;
:
retcode = dataset_AllocGlobal(&memptr, &err, malloc, free);
:
retcode = dataset_FreeGlobal(&memptr, &err)

6-18 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Open Dataset
Format: datasetError=dataset_Open(global,g_error,devname,dsname,
voltype,mode)

Table 6-13 Arguments, Types and Descriptions for Open Dataset

Argument Type Description

global void (see Note 1) Global memory area

g_error long (see Note 1) An error information stored area
devname char (see Note 1) raw device name
dsname char (see Note 1) dataset name
voltypr char (see Note 1) volume emulation type
mode char (see Note 1) open mod

Return value: datasetError long

-1 Abnormal end

Note 1: When you issue this function, you must issue dataset_ Close() in
the end process.
Note 2: You must issue this function before dataset_Open(), Get(),
dataset_Get2(), dataset_Put(), dataset_Put2(), dataset_Rewind(),
and dataset_GetFileInformation().

This function opens a specified dataset (file) with a specified open mode.
• Argument:
– global: global memory area (specify a Global memory area gotten by
dataset_AllocGlobal)
– g_error: Specify an address to store FAL error code.
– devname: raw device name (special file)
– dsname: dataset name
– voltype: Device emulation type (3390-3A/9A/LA, and 3390-3B/9B/LB,
3380-3A, 3380-3B)
– mode: “r”: Read only, “w”: Write only
– Return Value: When this function ends abnormally, it returns -1.
• Example:

void *memptr; /* global memory area */

long err,datasetError; /* global err information */
int retcode;
retcode = dataset_AllocGlobal(&memptr, &err, malloc, free);
:
datasetError = dataset_Open(memptr, &err,”
HYPERLINK "\\\\.\\PHYSICALDRIVE1"
\\.\PHYSICALDRIVE1
,”DSN001
, ”3390-3A”,”r”);
:
datasetError=dataset_Close(memptr, &err);
retcode = dataset_FreeGlobal(&memptr, &err);

Performing File Access Library (FAL) Operations 6-19

Hitachi Cross-OS File Exchange User’s Guide

Read Data
• Format: reclen = dataset_Get(global, g_error, buf, buflen)

reclen= dataset_Get2(global, g_error, buf, buflen)

Table 6-14 Arguments, Types and Descriptions for Read Data

Argument Type Description

global void* Global memory area

g_error long* An error information stored area
buf char* Read buffer
buflen long Data length transferred to buffer

Return value: reclen long Data length read to buffer

-1 Abnormal end

Note: This function provides the ability to read a record of a previously

opened dataset out to a buffer. Transferred data is real data only. For further
information, see Reading Data.
• Argument:
– global: Global memory area (Specify a Global memory area gotten by
dataset_AllocGlobal.)
– g_error: Specify an address to store FAL error code.
– buf: Specify a buffer to store read data.
– buflen: Specify buffer size.
• Return Value:
– For dataset_Get():
• When this function ends normally, reclen (record length) is returned.
(1 record length≦32760).
• When this function ends abnormally, “- 1” is returned.
• When this function detects EOF, “0” is returned.
– For dataset_Get2():
• When this function ends normally, reclen (record length) is returned.
(0≦record length≦32760).
• When this function ends abnormally, “- 1” is returned.
• When this function detects EOF, “DATASET_ERROR_END_OF_FILE ”
is returned.
Note: When “- 1” is returned, refer to the content of g_error for error
code details. For further information, see Troubleshooting.

6-20 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Write Data
• Format: recren= dataset_ Put(global, g_error, buf, buflen)
• recren= dataset_ Put2(global, g_error, buf, buflen)

Table 6-15 Arguments, Types and Descriptions for Write Data

Argument Type Description

global void (see Note 1) Global memory area

g_error long (see Note 1) An error information stored area
buf char (see Note 1) Read buffer
buflen long (see Note 1) Data length transferred to buffer

Return value: reclen long (see Note 1) Data length read to buffer
-1 Abnormal end

Note 1: When buflen is “0”, the dataset_Put function has ended abnormally,
but the dataset_Put2 function ends normally. (It is possible to handle 0
data.)

Note 2: When a full data error occurs, a return value of dataset_Put2 is “-

1”, but a return value of dataset_Put is “Y”. G_error is “- 50”.

This function writes a record of the previous opened dataset to a buffer. For
variable length record formats, this function writes real data to a buffer with
record length. For more detail, see Reading Data.
• Argument:
– global: Global memory area (Specify a Global memory area gotten by
dataset_AllocGlobal.)
– g_error: Specify an address to store FAL error code.
– buf: Specify a buffer to store write data.
– buflen: Specify buffer size.
• Return Value: When this function ends normally, reclen (record length) is
returned. When this function ends abnormally, “- 1” is returned. When “-
1” is returned, refer to the contents of g_error for error code details. For
further information, see Troubleshooting.

Performing File Access Library (FAL) Operations 6-21

Hitachi Cross-OS File Exchange User’s Guide

Close Dataset
• Format: datasetError=dataset_Close(global,g_error)

Table 6-16 Arguments, Types and Descriptions for Close Dataset

Argument Type Description

global void (see Note 1) Global memory area

g_error long (see Note 1) An error information stored area

Return value: datasetError long (see Note 1)

-1 Abnormal end

This function closes a dataset.

• Return value:
– When this function ends normally, “0” is returned.
– When “- 1” is returned, refer to the content of g_error for error code
detail. For further information, see Troubleshooting.

Free Information Stored Area

• Format: memError= dataset_FreeGlobal(dgpp, derrno)

Table 6-17 Arguments, Types and Descriptions for Free Information

Stored Area
Argument Type Description

dgpp void** Global memory area

derrno long* An error information stored area

Return value: memError int

0 Abnormal end

This function releases information stored area.

• Argument:
– dgpp: Global memory area (Specify a Global memory area gotten by
dataset_AllocGlobal.)
– derrno: Specify an address to store FAL error code.
• Return Value:
– When this function ends normally, “1” is returned.
– When this function ends abnormally, “0” is returned. When “0” is
returned, refer to the content of derrno for error code detail. For
further information, see Troubleshooting.

6-22 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Initialize Target Record Pointer
• Format: datasetError=dataset_Rewind(global,g_error)

Table 6-18 Arguments, Types and Descriptions for Initialize Target Record
Pointer
Argument Type Description

global void (see Note 2) Global memory area

g_error long (see Note 1) An error information stored area

Return value: datasetError long

-1 Abnormal end

Note 1: When this function is issued before dataset_Put, dataset_Put2,

dataset_Get, and dataset_Get2, the pointer is returned to the top record.
And then next dataset_Put, dataset_Put2, dataset_Get, and
dataset_Get2 are performed from the top record.
• Argument:
– global: Global memory area (Specify a Global memory area gotten by
dataset_AllocGlobal.).
– g_error: Specify an address to store FAL error code.
• Return Value:
– When this function ends normally, “0” is returned.
– When this function ends abnormally, “- 1” is returned.
– When “- 1” is returned, refer to the contents of g_error for error code
detail. For further information, see Troubleshooting.

Performing File Access Library (FAL) Operations 6-23

Hitachi Cross-OS File Exchange User’s Guide

Get Specified Dataset Attribute Information
• Format: datasetError= dataset_GetFileInformation(global, g_error,
&ffd)

Table 6-19 Arguments, Types and Descriptions for Get Specified Dataset
Attribute Information
Argument Type Description

global void (see Note 2) Global memory area

g_error long (see Note 1) An error information stored area
ffd DATASET_FIND_DATA A dataset attribute information stored area

Return value: datasetError long

-1 Abnormal end

An attribute of the opened dataset is returned to ffd.

• Argument:

– global: Global memory area (Specify a Global memory area gotten by

dataset_AllocGlobal.).
– g_error: Specify an address to store FAL error code.
– ffd: A first dataset attribute information stored area.
The dataset attribute information format is shown below:

typedef struct DATASET_FIND_DATA {

unsigned short blockSize; /* Block length */
unsigned short recordSize; /* Record length */
unsigned char dsorg[2]; /* Dataset type */
unsigned char recfm; /* Record format */
char name[44]; /* Dataset name */
unsigned short lastBlockTt; /* Last block address(relative track number) */
unsigned char lastBlockR; /* Last block address(relative block number) */
unsigned char mftype; /* Mainframe OS(MVS･ VOS3･ MSP/VSE/VOS1/XSP) */
} DATASET_FIND_DATA;

• Return Value:
– When this function ends normally, “0” is returned.
– When this function ends abnormally, “- 1” is returned.
– When “- 1” is returned, refer to the contents of g_error for details. For
further information, see Troubleshooting.
Note: * You must issue dataset_Open() before this function.

6-24 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Get Multiple Dataset Attribute Information
• Format (1): datasetHandle=dataset_FindFirstFile(global, g_error,
pathname, voltype, and ffd)

Table 6-20 Arguments, Types and Descriptions for Get Multiple Dataset
Attribute Information (1)
Argument Type Description

global void** Global memory area

g_error long* An error information stored area
pathname char* raw device name
voltype char* Device emulation type
ffd DATASET_FIND_DATA A dataset attribute information stored area

Return value: datasetHandle DATASET_HANDLE

-1 Abnormal end

This function returns top dataset attribute information specified by raw device
name to ffd. This function is used with dataset_FindFirstFile,
dataset_FindNextFile and dataset_FindClose.
• Argument (1):
– global: Global memory area (Specify a Global memory area gotten by
dataset_AllocGlobal.).
– g_error: Specify an address to store FAL error code.
– Pathname: Address of partition name/physical drive name.
– Voltype: Device emulation type (3390-3A/9A/LA, and 3390-3B/9B/LB,
3380-3A, 3380-3B).
– ffd: A first dataset attribute information stored area.
• Return Value (1):
– When this function ends normally, “DATASET_HANDLE” is returned.
This handler is used as an argument for next dataset_FindNextFile
and dataset_FindClose functions.
– When this function ends abnormally, “- 1” is returned.
– When “- 1” is returned, refer to the contents of g_error for error code
detail. For further information, see Troubleshooting.
Note: When there is no dataset in the VTOC, the g_error is
“DATASET_ERROR_NO_DATASET”.

Performing File Access Library (FAL) Operations 6-25

Hitachi Cross-OS File Exchange User’s Guide

 • Format (2): datasetError=
dataset_FindNextFile(global,g_error,datasetHandle, &ffd)

Table 6-21 Arguments, Types and Descriptions for Get Multiple Dataset
Attribute Information (2)
Argument Type Description

global void (see Note 1) Global memory area

g_error long (see Note 1) An error information stored area
datasetHandle DATSET_HANDLE Dataset handler
ffd DATASET_FIND_DATA A dataset attribute information stored area

Return value: datasetError long

-1 Abnormal end

This function gets a second dataset and more attribute information. You can
get just the next set of dataset attribute information, or you can use this
function until no further dataset information is available or returned.
• Argument (2):
– global: Global memory area (Specify a Global memory area gotten by
dataset_AllocGlobal.).
– g_error: Specify an address to store FAL error code.
– datasetHandle: Specify dataset handler.
– ffd: Next dataset attribute information stored area.

Refer to dataset_GetFileInformation for dataset attribute information.

• Return Value (2):
– When this function ends normally, “0” is returned.
– When this function ends abnormally, “- 1” is returned.
– When “- 1” is returned, refer to the contents of g_error and for error
code details. For further information, see Troubleshooting.
– When there is no dataset in the VTOC, the return value is “- 1” and
error information is DATASET_ERROR_END_OF_VTOC.
Note*: You must issue dataset_FindFirstFile before this function. When
you finish getting dataset attribute information, you must issue
dataset_FindClose in the end process.

6-26 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

• Format (3): datasetError=
dataset_FindClose(global,g_error,datasetHandle).

Table 6-22 Arguments, Types and Descriptions for Get Multiple Dataset
Attribute Information (3)
Argument Type Description

global void (see Note 1) Global memory area

g_error long (see Note 1) An error information stored area
datasetHandle DATSET_HANDLE Dataset handler

Return value: datasetError long

-1 Abnormal end

This function declares the end of the process, and gets dataset attribute
information using dataset_FindFirstFile and dataset_FindNextFile.
• Argument (3):
– global: Global memory area (Specify a Global memory area gotten by
dataset_AllocGlobal.).
– g_error: Specify an address to store FAL error code.
– datasetHandle: Specify dataset handler.
• Return Value (3):
– When this function ends normally, “0” is returned.
– When this function ends abnormally, “- 1” is returned.
– When “- 1” is returned, refer to the content of g_error and for error
code details. For further information, see Troubleshooting.

Performing File Access Library (FAL) Operations 6-27

Hitachi Cross-OS File Exchange User’s Guide

Compiling
An example of installation including FAL is shown below. For UNIX operating
systems, you need to use a C language compiler based on ANSI. You need to
include a header file in the program which will be using FAL.
• For Windows systems (Windows 2003 and earlier):
a. Launch Developer Studio.
b. Create a new project.
c. Copy the following FAL files to the project folder/directory:
• dataset.h
• falmt.dll
• falmt.lib
d. Select SETTING on the Developer Studio PROJECT menu.
e. Select the LINK tab in the Project setting dialog.
f. Add falmt.lib to the OBJECT/LIBRARY MODULE column.
g. Build/Execute.

Note: For AIX systems:

#cc –qlanglvl=ansi –o output file name source file name /usr/lib/libfalmt.a

• libfalmt.a: object module file name of Multi-thread for FAL.

6-28 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

Error Information
For details on error messages, see Troubleshooting.

The following error codes do not occur for FAL Multi-thread:

-2, -6, -20, -23, -32

The following error codes only occur for FAL Multi-thread:

Table 6-23 FAL Multi-thread Error Codes

Error Code Error Message and Content of Error Codes

-29 DATASET_ERROR_CANNOT_MALLOC
malloc() function is abnormally ended.

-30 DATASET_ERROR_FREE_INVALID_AREA
Invalid area for global area.

-31 DATASET_ERROR_CANNOT_FREE
free() function is abnormally ended.

Performing File Access Library (FAL) Operations 6-29

Hitachi Cross-OS File Exchange User’s Guide

FAL Usage Scenario
• Example 1: read data flowchart

dataset_
AllocGlobal Keep work area for FAL
error

dataset_Open Open dataset

error

dataset_ Get dataset attribute

GetFileInformation information
error

Check dataset attribute

dataset_Get Read one data

error

EOF

Process of reading data

dataset_Close Close dataset

dataset_FreeGlobal
Release work area for FAL

Error process/End
process

dataset_FreeGlobal

Error
process/End

Figure 6-5 Example of Using FAL to Read Data

6-30 Performing File Access Library (FAL) Operations

Hitachi Cross-OS File Exchange User’s Guide

 7
Troubleshooting
This chapter provides descriptions of error codes and support desk contact
data.
Troubleshooting
Error Codes and Messages
Calling the Support Center

Troubleshooting 7-1

Hitachi Cross-OS File Exchange User’s Guide

Troubleshooting
For general troubleshooting information on the Hitachi RAID storage systems,
please refer to the User and Reference Guide for the storage system.

The FX software is not expected to fail in any way. When errors are detected,
error codes and messages are displayed and/or logged. Table 7-2, Table 7-3,
Table 7-4 list the FAL and FCU error codes and provides instructions for
resolving the error conditions.

If you have a problem with the FX software, first make sure that the problem
is not being caused by other open-system software or hardware, and try
rebooting the open-system server.

For FCU operations, make sure that the FX volume definition file and FCU
initiation parameters are correct. Table 7-1 lists potential error conditions in
FX and provides instructions for resolving each condition.

If you are still unable to resolve an error condition, please ask your Hitachi
Data Systems representative for help, or call the Hitachi Data Systems
Support Center for assistance (see Error Codes and Messages).

Table 7-1 Troubleshooting

Error Condition Recommended Action

UNIX files in non-Hitachi storage Make sure that the devices have been mounted. If mounting
systems could not be accessed. is done during an FCU operation, the results cannot be
guaranteed because error information may not be reported to
FCU.

Solaris system reports an error Define a path to the Xmlibrary as follows:

indicating libXm.so.xx is not found. 1. For C shell, add the following line to the .cshrc file in the
home directory:
setenv LD_LIBRARY_PATH
/usr/dt/lib:$LD_LIBRARY_PATH
2. For non-C shell, add the following two lines to the
.dtprofile file in the home directory:

LD_LIBRARY_PATH=/usr/dt/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH

Windows systems only: Remove all space lines from the FCU parameter definition
FCU reports errors when accessing an files. FCU versions 01-01-24 and earlier supported space lines
FCU parameter definition file. when run without the GUI. FCU versions 01-01-36 and later
do not support space lines.

FCU reports code conversion table If you specified your own code conversion table, make sure
errors. that the file name and path are correct. FCU may also report
code conversion table errors when the FX volume definition
file contains both mainframe and OPEN-xFX volumes. Keep
the FXoto volume definition file separate from the FXmto/otm
volume definition file.

7-2 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

Error Codes and Messages
The error information returned by the datasetGetLastError function includes
the FAL error information defined in the dataset.h file. Table 7-2 lists and
describes the FAL error codes and provides instructions for resolving each
error condition. In Table 7-2, the error codes marked by an asterisk (*) may
also be reported when I/O access contention occurs. If the cause of the error
cannot be identified as described in Table 7-2, check for illegal I/O access
contention for the FX volume between the mainframe and open-system hosts.

The FAL error 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
systems are c:\fal_error and c:\fal_error.bak, and c:\fal_dump and
c:\fal_dump.bak.

Note: Error codes with a negative value are FAL errors. Error codes with a
positive value are system errors. UNIX system error codes are defined in the
standard error file errno.h.

Table 7-2 FAL Error Codes

Error
Code Error Message and Description Recommended Action(s)

-7* DATASET_ERROR_INVALID_VOLUME Make sure that the VSN in the FX volume

The actual VSN and the VSN specified in the FX definition file is correct.
volume definition file do not match.

-8 DATASET_ERROR_DATASET_NOT_FOUND Make sure that the actual dataset name

The target dataset was not found. and the specified dataset name are the
same. You can use the MF-File list
command in the FCU HELP menu, or VTOC
dump data on the mainframe host, to
check the dataset name.

-9 DATASET_ERROR_NOT_SUPPORTED Make sure that the dataset was created

correctly on the mainframe host.
The data format is not supported.

-10* DATASET_ERROR_DEVICE_TYPE_NOT_SUPPORTE Make sure that the device emulation type

D (LVI) is correct in the FX volume definition
The device emulation type is not supported. file. The supported LVIs are 3390-3A, -3B
and -3C.

-11 DATASET_ERROR_DSORG_NOT_SUPPORTED Check the DO type using the MF-File list

The dataset organization type is not supported. command in the FCU HELP menu, or VTOC
dump data on the mainframe host.

-12 DATASET_ERROR_RECFM_NOT_SUPPORTED Check the RF type using the MF-File list

command in the FCU HELP menu, or VTOC
The record format is not supported.
dump data on the mainframe host.

-13* DATASET_ERROR_INVALID_DATA Make sure that the VTOC and dataset were
The data in the VTOC or the dataset is invalid. created correctly on the mainframe host.

-14* DATASET_ERROR_VOLUME_DEFINITION_INVALID Make sure that the FX volume definition

The format of volume definition file is invalid. file was created correctly.

Troubleshooting 7-3

Hitachi Cross-OS File Exchange User’s Guide

 Error
Code Error Message and Description Recommended Action(s)

-15 DATASET_ERROR_DATASET_NOT_OPENED Make sure that the datasetOpen function

is called before the datasetGet function.
An attempt was made to read the dataset
without opening it.

-16 DATASET_ERROR_DATASET_NOT_CLOSED Make sure the requirements and

An attempt was made to open the dataset restrictions specified in Chapter 6 are met.
For example:
without closing it first.
Dataset open and close must be used as a
pair.
More than one dataset cannot be open
within one process.
datasetOpen,
datasetGetFileInformation, and
datasetFindFirstFile cannot be used
while the dataset is being accessed by
datasetGetFileInformation or
datasetFindFirstFile.
datasetGetFileInformation and
datasetFindFirstFile cannot be used
while the dataset is being accessed
datasetOpen.

-17 DATASET_ERROR_BUFLEN_SHORT Make sure that the buffer area is larger

The buffer length specified by datasetGet is than the dataset record length.
shorter than the actual record length.

-18* DATASET_ERROR_VOLUME_LABEL_INVALID Make sure that volume initialization is

No standard volume label was found, or the complete and correct on the mainframe
host. This error occurs when a system that
contents of the VTOC are illegal.
does not support large files accesses a
formatted volume from a system that
supports large files. This error also occurs
when a data partition size is incorrect for
Solaris.

-19* DATASET_ERROR_VTOC_INVALID Make sure that the VTOC was created

No VTOC found, or contents of VTOC are invalid. correctly on the mainframe host.

-20* DATASET_ERROR_VOLUME_NOT_DEFINED Make sure that the specified volume has

The specified volume is not defined. been entered correctly in the FX volume
definition file.

-21 DATASET_ERROR_INVALID_ARGUMENT Make sure that the argument for the FAL
function is correct.
An argument of the function is invalid.

-22 DATASET_ERROR_NO_DATASET Make sure that the dataset has been

created correctly on the mainframe host.
No dataset was found.

-23* DATASET_ERROR_NON_STANDARD_R0_EXIST Change the R0 track format to standard

track format. FAL cannot write on tracks
Nonstandard record 0 (R0) exists.
with nonstandard R0.

-24 DATASET_ERROR_INVALID_MODE Make sure that the value of the mode

The mode argument of datasetOpen is not argument for the datasetOpen function is
either r (for read) or w (for write).
valid.

-25* DATASET_ERROR_VOLUME_DEFINED_READ_ONL Make sure that the target dataset for an

Y open-system write operation is on a
The open-system host tried to write to a 3390-3A/C volume.
read-only volume.

7-4 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

Error
Code Error Message and Description Recommended Action(s)

-26 FAL_INTERNAL_ERROR Collect error logs file and error dump file.
And make contact a maintenance staff.
Internal error of FAL
This error occurs when the open system
does not have enough memory.

-27* DATASET_ERROR_END_OF_VOLUME The open-system volume/partition size is

smaller than the mainframe volume size.
The end of volume was detected before the end
Make sure that the partition size is
of dataset was detected.
specified correctly on the open system.
This error occurs when the open system
disk is full or it exceeds a limitation for
FXmto.

-28 DATASET_ERROR_OVERFLOW Check the size of the data to be written,

Data cannot be written because the dataset is and extend the size of the dataset as
needed.
full.

-33 DATASET_ERROR_PARAMETER_MISMATCH Make sure to specify the correct VSE

record option parameters when accessing
User-specified RF, BL, RL does not match the
VSE datasets (see Record Description Word
RF, BL, RL defined in the VTOC; or
(RDW) Option).
RF, BL, RL not specified and not defined in
VTOC.

-35 DATASET_ERROR_NO_LICENSE Ensure that the software license is current

and correct. If problems persist, please
FAL can’t permit execution of software that
contact the Hitachi Data Systems Support
doesn’t have a software license.
Center..

-36 DATASET_ERROR_TIMEOUT_LICENSE Ensure that the trial software license is

FAL can’t permit execution of software with an current and correct. If problems persist,
please contact the Hitachi Data Systems
expired software license trail time.
Support Center

-37 DATASET_ERROR_HOSTNAME_CHANGE Ensure that the current host name has not
been changed.
FAL can’t permit execution if the current host
and the installed host are not identical and/or
the hostname is changed.

-39 DATASET_ERROR_MULTI_VOLUME_DEFINITION_ Parameter sets more than 1000 cannot be

RECORD_OVER processed. Decrease them not to exceed
The number of parameter sets for multiple 1000.
volume definition file exceeded 1000.

-40 DATASET_ERROR_MULTI_VOLUME_NO_DATASET Check volume serial number in the

The dataset isn’t exist in the next volume. multiple volume definition file.

-41 DATASET_ERROR_MULTI_VOLUME_NO_TRANSFE Data cannot be transferred to the dataset

R that is in middle volume of multiple
volume.

-42 DATASET_ERROR_MULTI_VOLUME_DEFINITION_ Specify the record length less than 1400

INVALID_RECORD_LENGTH characters.(not include delimiter).
The record length in the multiple volume
definition file is too long.

-43 DATASET_ERROR_MULTI_VOLUME_DEFINITION_ Specify the number of volume is less than

PARAMETER_ERROR 31 for one line in the multi volume
The number of volume for one dataset in the definition file.
multi volume definition file exceeded 31.

Troubleshooting 7-5

Hitachi Cross-OS File Exchange User’s Guide

 Error
Code Error Message and Description Recommended Action(s)

-44 DATASET_ERROR_MULTI_VOLUME_DEFINITION_ Specify the dataset name in the head

NO_DATASET volume
information of the multiple volume
The Dataset name is not specified in the
definition file.
multiple volume definition file.

-45 DATASET_ERROR_MULTI_VOLUME_DEFINITION_ Check if VSN length in the multiple

VSN_ definition file is less than 7.
LENGTH_ERROR
VSN is incorrect in the multiple volume
definition file.

-46 DATASET_ERROR_MULTI_VOLUME_DEFINITION_ Check if DSN length in the multiple

DSN_ definition file is less than 45.
LENGTH_ERROR
DSN is incorrect in the multiple volume
definition file.

-47 DATASET_ERROR_MULTI_VOLUME_DEFINITION_ Specify the VSN identification length less

VOLID than 36 characters.
_LENGTH_ERROR
The VSN identification length in the multiple
volume definition file is too long.

-48 DATASET_ERROR_MULTI_VOLUME_DEFINITION_ Specified all volumes in the multiple

NO_NEXT_VOLUME volume definition file.
The next VSN is specified in the multiple volume
definition file when the volume isn’t last on VTOC.

-50* DATASET_ERROR_END_OF_FILE None.

End of File (EOF) was detected.

-51* DATASET_ERROR_END_OF_VTOC None.

End of VTOC was detected.

FCU Error Codes for UNIX

If FCU for UNIX reports an error, use the Help-Error command to view the
most recent error. Table 7-3 lists and describes the FCU error codes for UNIX
and provides instructions for resolving each error condition. In Table 7-3, the
error codes marked by an asterisk (*) may also be reported when I/O access
contention for the FX volume occurs between the mainframe and open-system
hosts. If the cause of the error cannot be identified as described in Table 7-3,
check for any illegal I/O contention for the FX volume.

Note: Error codes with a negative value are FCU errors. Error codes with a
positive value are system errors. UNIX system error codes are defined in the
standard error file errno.h.

Note: The error codes with “(C)” in the “Error code” cell in Table 7-3 are
generated only when using with FX Code Converter. For details, please see the
Hitachi Cross-OS File Exchange Code Converter User’s Guide.

7-6 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

Table 7-3 FCU Error Codes for UNIX
Error Error Message and Description Recommended Action(s)
Code

-100 No parameter file If you specified the parameter definition file using the
The FCU parameter definition [param] option, make sure that the specified file
file could not be found. exists and the name is correct.
If you did not specify the [param] option when you
started FCU, make sure that the default parameter
definition file exists (fcudata.param in the current
directory).

-101* Parameter file: Open error Display the system error code using the Help-Error
An error occurred when command. Please refer to the OS user manual for
opening the parameter information on system errors.
definition file.

-102* Parameter file: Read error Display the system error code using the Help-Error
An error occurred when command. Please refer to the OS user manual for
reading the parameter information on system errors.
definition file.

-103* Parameter file: No valid data Make sure that the FCU initiation parameters are
The parameters in the entered correctly in the parameter definition file.
parameter definition file are
not valid.

-107 Parameter file: CODE_CONV Make sure that the code conversion is specified as
error either EA or No.
The code conversion specified
in the parameter definition
file is not valid.

-108 Parameter file: PADDING error Make sure that the padding is specified as either Yes
or No.
The padding option specified
in the parameter definition
file is not valid.

-109 Parameter file: DELIMITER error Make sure that the delimiter is specified as CR, LF,
or No.
The delimiter option specified
in the parameter definition
file is not valid.

-110* Parameter file: Open error Display the system error code using the Help-Error
An error occurred when command. Please refer to the OS user manual for
opening and outputting the information on system errors.
parameter definition file.

-111 Parameter file: Write error Display the system error code using the Help-Error
An error occurred when command. Please refer to the OS user manual for
information on system errors.
writing to the parameter
definition file.

-112 Parameter file: Close error Display the system error code using the Help-Error
command. Please refer to the OS user manual for
An error occurred when
information on system errors.
closing the parameter
definition file.

-114 Parameter: No input file name Make sure to specify the input file name.
The input file name was not
specified.

Troubleshooting 7-7

Hitachi Cross-OS File Exchange User’s Guide

 Error Error Message and Description Recommended Action(s)
Code

-115 Parameter: VSN error Make sure that the specified VSN matches the actual
VSN. Make sure that the VSN is separated from the
The specified VSN is not
dataset name by a colon (:).
correct.

-116 Parameter: Input file name Make sure that the specified file name matches the
error actual file name.
The specified input file name
is not correct.

-117 Parameter: Dataset name error Make sure that the specified dataset name matches
the actual dataset name.
The specified input dataset
name is not correct.

-118 Parameter: Output file name Make sure that the specified output file name
error matches the actual output file name.
The specified output file name
is incorrect.

-119* Input file: Open error Display the error code using the Help-Error
An error occurred when command. If an FAL error code is displayed, refer to
acquiring the dataset Table C.1. If a system error code is displayed, please
attribute information of the refer to the OS user manual. For example, if a
input file. partition name does not match the partition name in
the volume definition file, system error code 6 (No
such device) is displayed.

-120 Overwrite ? (OK/Cancel) The specified open-system target file already exists.
Select OK to overwrite the file, or select Cancel to
This message asks you to
specify a different target file.
confirm whether to overwrite
the existing file.

-121 Output file: File name error Make sure that the correct output file name is
specified.
The output file name is not
specified.

-122* Output file: Open error Display the system error code using the Help-Error
command. Please refer to the OS user manual for
An OPEN error occurred when
checking to see if the output information on system errors.
file exists.

-124 Volume definition: MFtype error. Specified MFN or MFA in MFtype of the volume
Incorrect MFtype is specified in definition file.
the volume definition file.

-125* Volume definition: VSN error Display the contents of the volume definition file
The VSN specified in the using the Help-Volume command. Make sure that
the VSN for the specified volume is correct.
volume definition file is
incorrect.

-126 Volume definition: Partition Display the contents of the volume definition file
name error using the Help-Volume command. Make sure that
the partition name is correct.
The partition name specified
in the volume definition file is
incorrect.

-127* Volume definition: Emulation Display the contents of the volume definition file
type error using the Help-Volume command. Make sure that
The LVI type specified in the the LVI type is correct.
volume definition file is
incorrect.

7-8 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

Error Error Message and Description Recommended Action(s)
Code

-128* Volume definition file: Open Display the system error code using the Help-Error
error command. Please refer to the OS user manual for
information on system errors. For example, if the
An error occurred when
volume definition file does not yet exist, error code 2
opening the volume definition
(No such file or directory) is displayed.
file.

-129* Volume definition file: Read Display the system error code using the Help-Error
error command. Please refer to the OS user manual for
information on system errors.
An error occurred when
reading the volume definition
file.

-130* Volume definition file: No data Display the contents of the volume definition file
using the Help-Volume command. Make sure that
The information found in the
the parameters for each volume are correct.
volume definition file is not
valid.

-131 Volume definition file: Close Display the system error code using the Help-Error
error command. Please refer to the OS user manual for
An error occurred when information on system errors.
closing the volume definition
file.

-135 Parameter error: No input file Specify the VSN of the mainframe source dataset
name before selecting the Help-MF-File command.
The input VSN is not specified.

-136 Parameter error: VSN error Make sure that the VSN has six characters.
The input VSN is incorrect.

-137 Dataset error: No dataset Make sure that the VSN is correct.
The specified volume has no
datasets.

-138* Dataset error: Search error Display the error code using the Help-Error
An error occurred when command. If a FAL error code is displayed, refer to
Table C.1. If a system error code is displayed, please
searching the dataset.
refer to the OS user manual.

-139 Dataset error: Close error Display the error code using the Help-Error
An error occurred when command. If a FAL error code is displayed, refer to
closing the dataset. Table C.1. If a system error code is displayed, please
refer to the OS user manual.

-140 Input file error: Invalid Display the attribute information using the
organization type Help-MF-File command. The DO type must be SAM.
The DO type of the dataset is
not supported.

-141 Input file error: Invalid record Display the attribute information using the
format Help-MF-File command. The RF type must be
fixed-length or variable-length.
The RF type of the dataset is
not supported.

-142 Input file error: Invalid block Display the attribute information using the
length Help-MF-File command. The block length must be
The block length of the nonzero and cannot be greater than 32 kB.
dataset is invalid.

Troubleshooting 7-9

Hitachi Cross-OS File Exchange User’s Guide

 Error Error Message and Description Recommended Action(s)
Code

-143 Input file error: Invalid record Display the attribute information using the
length Help-MF-File command. The record length must be
nonzero and cannot be greater than 32 kB.
The record length of the
dataset is invalid.

-144* Input file error: No data Display the attribute information using the
No data was found in the Help-MF-File command, and check the dataset size.
specified dataset.

-150* Input file: Open error Display the error code using the Help-Error
A file open error occurred in command. If a FAL error code is displayed, refer to
the input dataset. Table C.1. If a system error code is displayed, please
refer to the OS user manual.

-151* Output file: Open error Display the system error code using the Help-Error
A file open error occurred in command. Please refer to the OS user manual for
the output UNIX file. information on system errors.

-152 Output file: Get file data error Collect information such as error log for
A data acquisition error of the troubleshooting.
output file occurred during an
FXotm operation.

-153 Processing data: Length check Make sure that the specified data length matches the
error actual data length. Collect information such as error
A data length to be processed log for troubleshooting.
by FXotm does not match.

-155 Buffer: Memory allocation error Display the system error code using the Help-Error
command. Please refer to the OS user manual for
Memory allocation failed.
information on system errors.

-160* Input file: Read error Display the error code using the Help-Error
A read error occurred in the command. If a FAL error code is displayed, refer to
input dataset. Table C.1. If a system error code is displayed, please
refer to the OS user manual.

-161* Output file: Write error Display the system error code using the Help-Error
command. Please refer to the OS user manual for
A write error occurred in the
information on system errors.
output UNIX file.

-162 Output file: Code conversion Display the error code using the Help-Error
error command. If a FAL error code is displayed, refer to
Table C.1.
An error occurred in the code
conversion to the output
UNIX file.

-163 Get processing data error Display the error code using the Help-Error
The acquisition of processing command. If a FAL error code is displayed, refer to
data failed. Table C.1. If a system error code is displayed, please
refer to the OS user manual.

-165 Dataset error: Invalid data Make sure that the mainframe dataset was generated
An invalid record length was correctly.
found in the dataset.

-170 Input file: Close error Display the error code using the Help-Error
command. If a FAL error code is displayed, refer to
A file close error occurred in
Table C.1. If a system error code is displayed, please
the input dataset.
refer to the OS user manual.

7-10 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

Error Error Message and Description Recommended Action(s)
Code

-171 Output file: Close error Display the system error code using the Help-Error
command. Please refer to the OS user manual for
A file close error occurred in
information on system errors.
the output UNIX file.

-180 UNIX/Open system file: Invalid Check the specified directory name.
directory name
The specified directory name
is not valid.

-181 UNIX file: Not a directory Check the specified directory name.
The specified name is not a
directory name.

-182* UNIX/Open system file: Open Display the system error code using the Help-Error
directory error command. Please refer to the OS user manual for
information on system errors.
A directory open error
occurred.

-183 UNIX/Open system file: Close Display the system error code using the Help-Error
directory error command. Please refer to the OS user manual for
A directory close error information on system errors.
occurred.

-190 Input file name: No data The input file name must be specified when you
The input file name is not select File-Save.
specified.

-191 Output file name: No data The output file name must be specified when you
The output file name is not select File-Save.
specified.

-192 Parameter file name: No data The FCU parameter definition file name must be
The parameter definition file specified when you select File-Save.
name is not specified.

-200 Parameter file: End line The next time you select File-Load, the first set of
The last parameter set was parameters will be loaded.
loaded from the parameter
definition file.

-201 Parameter file: Direction error Make sure that the direction (mto or otm) is correct.
The data transfer direction
specified in the parameter
file is incorrect.

-202 Parameter file: Too many data The FCU parameter definition file can only store a
maximum of 100 parameter sets. If necessary,
The number of parameter sets
for parameter definition file delete one or more parameter sets to make room for
exceeded 100. a new parameter set.

-203 Parameter: Empty select error Make sure that the Emp=Yes/No parameter is
The Emp parameter is correct.
incorrect.

-204 Parameter: RDW select error Make sure that the RDW=Yes/No parameter is
The RDW parameter is correct.
incorrect.

Troubleshooting 7-11

Hitachi Cross-OS File Exchange User’s Guide

 Error Error Message and Description Recommended Action(s)
Code

-205 RDW error: CODE_CONV not Code conversion cannot be performed when
supported RDW=Yes. Change the code conversion parameter
to No.
Code conversion is not
specified as No when
RDW=Yes.

-206 RDW error: PADDING not Padding cannot be processed when RDW=Yes.
supported Change the padding parameter to No.
Padding is not specified as No
when RDW=Yes.

-207 RDW error: DELIMITER not Delimiters cannot be processed when RDW=Yes.
supported Change the delimiter parameter to No.
Delimiter is not specified as
No when RDW=Yes.

-210 Parameter file: Comment line If you specify Load, FCU will move to the next line.
You can also replace the comment line with a valid
This is a comment line in the
parameter file. parameter.

-220 Parameter: VSE select error Make sure that the number of VSE parameters is
The VSE parameter format is correct and that a comma is used correctly to
not correct. separate the VSE parameters.

-221 Parameter: VSE record format Make sure that the record format is set to either one
error of F/FB/V/VB.
Record format in the VSE
parameter is not correct.

-222 Parameter: VSE record length Make sure that the record length is set to the correct
error value within the extent allowed.
Record length in the VSE
parameter is not correct.

-223 Parameter: VSE block length Make sure that the block length is set to the correct
error value within the extent allowed.
Block length in the VSE
parameter is not correct.

-230 No code conv. table file: No Make sure that the code conversion table file name is
code conv. table correct and that the file exists. This error may also
be reported if you mix mainframe and OPEN-x
The code conversion table was
devices in the same FX volume definition file.
not found.

-231 Code conv. table: Open error Refer to the OS user manuals for assistance.
The code conversion table
could not be opened.

-233 Code conv. table: Close error Refer to the OS user manuals for assistance.
The code conversion table
could not be closed.

-234 Code conv. table: Get file data Check the contents of the file. Refer to the OS user
error manuals for assistance.
The size of the code
conversion table could not be
obtained.

7-12 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

Error Error Message and Description Recommended Action(s)
Code

-235 Code conv. table: File size error Make sure that the size of the code conversion table
is 256 bytes.
The size of the code conv
table is not correct.

-236 Code conv. table Check the contents of the input file, especially the
function: Invalid argument delimiters.
No source data to be
converted was found.

-238 Code conv. table name: No data If you do not specify EA or No for the code
conversion option, make sure to specify the correct
The file name of the code
file name of your code conversion table.
conversion table is not
specified.

-300 Data error: Invalid record length Check the source data length and the target record
length, and make sure that the record length is
The data length is not correct
correct for the source data entities.
for the FXotm padding
function.

-301 Dataset error: Invalid record For FXotm with padding, make sure that the target
format dataset has fixed-length record format.
The record format is not
correct for the FXotm
padding function.

-302 Parameter error: Delimiter error If padding=Yes for an FXotm operation, the delimiter
The delimiter setting is not option must be CR, LF or CRLF.
correct for the FXotm
padding function.

-319* Dataset: Open error Display the error code using the Help-Error
An error occurred when command. If a FAL error code is displayed, refer to
Table C.1. If a system error code is displayed, please
opening the dataset.
refer to the OS user manual. For example, if the
partition name does not match the partition name in
the volume definition file, system error code 6 (No
such device) is displayed.

-324 O to M error: RDW is not Do not specify the RDW option for FXotm operations.
supported

-340 Dataset error: Invalid Display the attribute information using the
organization type Help-MF-File command. The DO type must be SAM.
The DO type of the dataset is
not supported.

-341 Dataset error: Invalid record Display the attribute information using the
format Help-MF-File command. The RF type must be
fixed-length or variable-length.
The RF of the dataset is not
supported.

-342 Dataset error: Invalid block Display the attribute information using the
length Help-MF-File command. The block length must be
nonzero and cannot be greater than 32 kB.
The block length of the
dataset is invalid.

-343 Input file error: Invalid record Display the attribute information using the
length Help-MF-File command. The record length must be
The record length of the nonzero and cannot be greater than 32 kB.
dataset is invalid.

Troubleshooting 7-13

Hitachi Cross-OS File Exchange User’s Guide

 Error Error Message and Description Recommended Action(s)
Code

-350* Input file: Open error Display the system error code using the Help-Error
command. Please refer to the OS user manual for
An open error occurred in the
information on system errors.
input UNIX file.

-351* Output file: Open error Display the error code using the Help-Error
A file open error occurred in command. If a FAL error code is displayed, refer to
Table C.1. If a system error code is displayed, please
the output dataset.
refer to the OS user manual.

-352 Input file: Get file data error Collect information such as error log for trouble
A data acquisition error for shooting.
input file occurred during an
FXotm operation.

-353 Processing data: Length check Collect information such as error log for trouble
error shooting.
A data length to be processed
in FXotm operation does not
match.

-355 Buffer: Memory allocation error Display the system error code using the Help-Error
Memory allocation failed. command. Please refer to the OS user manual for
information on system errors.

-360* Input file: Read error Display the error code using the Help-Error
command. If a FAL error code is displayed, refer to
A read error occurred in the
Table C.1. If a system error code is displayed, please
input UNIX file.
refer to the OS user manual.

-361* Output file: Write error Display the system error code using the Help-Error
A write error occurred in the command. Please refer to the OS user manual for
information on system errors.
output dataset.

-362 Output file: Code conversion Display the error code using the Help-Error
error command. If a FAL error code is displayed, refer to
An error occurred in the code Table C.1.
conversion to the output
dataset.

-363 Get processing data error Display the error code using the Help-Error
command. If a FAL error code is displayed, refer to
The acquisition of processing
Table C.1. If a system error code is displayed, please
data failed.
refer to the OS user manual.

-370 Input file: Close error Display the system error code using the Help-Error
A file close error occurred in command. Please refer to the OS user manual for
information on system errors.
the input UNIX file.

-371 Output file: Close error Display the error code using the Help-Error
A file close error occurred in command. If a FAL error code is displayed, refer to
Table C.1. If a system error code is displayed, please
the output dataset.
refer to the OS user manual.

-379* UNIX file: No data Make sure to specify an input file which contains
data.
No data was found in the
input UNIX file.

-380 No UNIX file Make sure that the specified UNIX file exists.
The specified UNIX file was
not found.

7-14 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

Error Error Message and Description Recommended Action(s)
Code

-381* UNIX file: Open error Display the system error code using the Help-Error
command. Please refer to the OS user manual for
An open error occurred in the
information on system errors.
UNIX file.

-382 Output file: Unsupported record Display the attribute information using the
format Help-MF-File command. The RF type must be
The record format of the fixed-length or variable-length.
output file is not supported.

-383* Input file: Invalid format Display the system error code using the Help-Error
command. Please refer to the OS user manual for
The format of the input file is
information on system errors.
incorrect.

-384* Input file: Invalid delimiter Display the attribute information using the
position Help-MF-File command. Make sure that the record
length of the target dataset is correct.
The delimiter position in the
input file is incorrect. Data
record length of input file
exceeds that of target
dataset, or a record with no
data entity is included.

-385 Input file: File seeking error Display the system error code using the Help-Error
An error occurred when command. Please refer to the OS user manual for
seeking for the input file. information on system errors.

-399 Volume definition : VSN Specify the VSN identification length than 35
identification length error. characters.
The VSN identification length
in the volume
definition file is too long.

-400 Parameter: Invalid input file Specify only one file name as the input file.
name
More than one input file name
was specified.

Troubleshooting 7-15

Hitachi Cross-OS File Exchange User’s Guide

FCU Error Codes for Windows Systems
If FCU for Windows systems reports an error, use the View-Error
information… command to view the most recent error. FCU for Windows
systems also logs errors in the FCU log file (e.g., fcudata.prm.log). Table 7-4
lists and describes the FCU error codes for Windows 2000/Windows NT
systems and provides instructions for resolving each error condition.

Note: Error codes with a plus value are system errors. Windows systems
system error codes are defined in the errno.h file attached with Microsoft
Visual C++®.

Table 7-4 FCU Error Codes for Windows Systems

Error Error Message and Description Recommended Action(s)
Code

-100 Parameter definition file: Open error Make sure that the parameter definition file was
An error occurred when opening the created correctly. If the parameter definition file
parameter definition file. was created correctly, check the system error.

-101 Parameter: Count error Make sure that the parameter count is correct.
An error is detected in the parameter
count.

-102 Parameter: Direction error Make sure that the direction is specified correctly
The data transfer direction is not as mto or otm.
correct.

-103 Parameter: Mainframe file name error Make sure that the mainframe file name is set
Mainframe file name is not correct. correctly.

-104 Parameter: Open system file name error Make sure that the open system file name is set
Open system file name is not correct. correctly.

-105 Parameter: Code conversion error Make sure that the code conversion option is
Code conversion setting is not correct. specified as EA, EcA, No, or File_name (of your
code conversion table). This error may also be
reported if you mix 3390/3380 and OPEN-x
devices in the same FX volume definition file.

-106 Parameter: Padding error Make sure that the padding option is specified as
Yes or No.
Padding setting is not correct.

-107 Parameter: Delimiter error Make sure that the delimiter option is specified as
Delimiter setting is not correct. CRLF or No.

-108 Parameter: Add parameter error If you are adding delimiters for Windows systems,
Delimiter setting is not correct. make sure that the delimiter option is specified as
CRLF (not just CR or LF).

-109 Parameter: Empty duplication error Specify only one empty setting.
More than one empty setting is
specified.

-110 Parameter: RDW duplication error Specify only one RDW setting.
More than one RDW setting is specified.

7-16 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

Error Error Message and Description Recommended Action(s)
Code

-120 Volume definition file: Open error Make sure that the volume definition file was
created correctly. If the volume definition file is
An error is detected when opening the
correct, check the system error.
volume definition file.

-121 Volume definition file : Length error Specify the record length less than 2080
The record length in the volume characters (not including delimiter).
definition file is too long.

-124 Volume definition: Emulation type Length Specify an emulation type parameter less than 11
error characters.
An emulation type parameter in the
volume definition file is too long.

-125 Volume definition: MFtype Length error. Specified MFN or MFA in MFtype of the volume
Incorrect definition file.
Ftype is specified in the volume
definition file.

-126 Volume definition: VSN identification Specify the VSN identification length than 35
length error. characters.
The VSN identification length in the
volume
definition file is too long.

-130 Dataset: No dataset error Make sure that the mainframe name is specified
No dataset is found. correctly, or that the dataset is allocated correctly
on the specified volume.

-131 Dataset: Search error Make sure that the volume definition file name is
specified correctly, or that the mainframe file name
An error is detected in searching the
is specified correctly.
dataset.

-132 Dataset: Information get error Make sure that the volume definition file name is
specified correctly, or that the mainframe file name
An error is detected in acquiring dataset
is specified correctly.
information.

-133 Dataset: Organization error Make sure that the dataset organization type is
specified correctly.
The specified dataset org. type is not
correct.

-134 Dataset: Record format error Make sure that the record format is specified
The specified record format is not correctly.
correct.

-135 Dataset: Block length error Make sure that the block length is specified
The specified block length is not correct. correctly.

-136 Dataset: Record length error Make sure that the record length is specified
The specified record length is not correctly.
correct.

-137 Dataset: Dataset size error Make sure that the dataset size is specified
The specified dataset size is not correct. correctly.

-138 Dataset: Close error Check the FAL error code and system error code.
An error is detected during close
operation.

Troubleshooting 7-17

Hitachi Cross-OS File Exchange User’s Guide

 Error Error Message and Description Recommended Action(s)
Code

-150 Mainframe file: Open error Check the FAL error code and system error code.
An error is detected when opening the
mainframe file.

-151 Mainframe file: Read error Check the FAL error code and system error code.
An error is detected during reading data
from the mainframe file.

-152 Mainframe file: Write error Check the FAL error code and system error code.
An error is detected when writing data
into the mainframe file.

-153 Mainframe file: Close error Check the FAL error code and system error code.
An error is detected when closing the
mainframe file.

-154 Mainframe file: Record format error For FXotm with the padding function, make sure
that the target dataset has fixed-length record
An error is detected in the record
format (or change padding to No).
format of the mainframe file.

-170 Open system file: Open error Make sure that the open-system file name is
An error is detected when opening the specified correctly.
open system file. Check if any system error is reported.

-171 Open system file: Read error Check the system error.
An error is detected when reading data
from the open system file.

-172 Open system file: Write error Check the system error.
An error is detected when writing data
into the open system file.

-173 Open system file: Close error Check the system error.
An error is detected when closing the
open system file.

-174 Open system file: No data error Make sure that the open-system file has data. If
No dataset is found. not, create the appropriate data in the
open-system file.

-175 Open system file: Delimiter (CR) position Make sure that the open-system file name is
error correct. Make sure that the mainframe dataset
Delimiter (CR) position error is name is correct. Make sure that the record length
detected. The source data record of the open-system file is correct.
length exceeds the target record
length, or a record with no data entity
is included.

-176 Open system file: Delimiter (LF) position Make sure that the open-system file name is
error correct. Make sure that the mainframe dataset
Delimiter (LF) position error is detected. name is correct. Make sure that the record length
of the open-system file is correct.

-177 Open system file: Record format error Make sure that the open-system file name is
correct. Make sure that the mainframe dataset
An illegal record format is found.
name is correct. Make sure the record format
(fixed- or variable-length) of the open-system file
data is correct.

7-18 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

Error Error Message and Description Recommended Action(s)
Code

-178 Open system file: Record length error Check the data length of the open-system file, and
make sure the dataset has the correct record
An illegal record length was found. Data
length.
length of open-system file is too large.

-190 Code conversion error Make sure that the dataset size is specified
An error was found during code correctly.
conversion.

-200 Process data get error Check the FAL error code and system error code.
An error is detected during close
operation.

-220 External table file: Open error Check the file name of code conversion table.
Check the system error.
The code conversion table could not be
opened.

-221 External table file: Size error Make sure that the size is 256 bytes and that the
table was created correctly.
The code conversion table size is not
correct.

-222 External table file: Read error Check the system error.
A read error was found when reading
the code conversion table.

-223 External table file: Close error Check the system error.
The code conv. table could not be
closed.

-240 Parameter: Direction, PAD, and DEL not For FXotm with the padding function, make sure
matched that the delimiter option is specified as Yes (or set
The combination of otm direction, padding=No).
PAD=Yes, and DEL=No is not
allowed.

-241 Parameter: Direction and RDW not When the FX data transfer direction is otm, make
matched sure that the RDW option is specified as No.
The combination of otm data transfer
direction and RDW=Yes is not
allowed.

-242 Parameter: Code conv. and RDW not When the code conversion option is EA or
matched File_name, make sure that the RDW option is
specified as No. When RDW=Yes, the code
The combination of RDW=Yes and
conversion option must be specified as No.
code conversion other than No is not
allowed.

-243 Parameter: Padding and RDW not When the padding option is specified as Yes, make
matched sure that the RDW option is specified as No.
The combination of RDW=Yes and When the RDW option is specified as Yes, make
padding=Yes is not allowed. sure that the padding option is specified as No.

-244 Parameter: Delimiter and RDW not When the delimiter option is specified as Yes,
matched make sure that the RDW option is specified as No.
The combination of RDW=Yes and When the RDW option is specified as Yes, make
delimiter=Yes is not allowed. sure that the delimiter option is specified as No.

-245 Parameter : Specified VOLSER isn’t Check whether specified VOLSER is defined in the
defined Volume Definition file. volume definition file.
Specified VOLSER isn’t defined the
volume definition file.

Troubleshooting 7-19

Hitachi Cross-OS File Exchange User’s Guide

 Error Error Message and Description Recommended Action(s)
Code

-300 Parameter definition file : Length error Specify the record length less than 3200
characters (do not include delimiter).
The record length in the parameter
definition file is too long.

-301 Mainframe file name : Length error Specify an input/output dataset name less than
An input dataset name(in case of 1025 characters.
FXmto) or an output dataset name(in
case of FXotm) in the parameter
definition file is too long.

-302 Opensystem file name : Length error Specify an input/output file name less than 1025
characters.
An input filet name(in case of FXotm) or
an output file name(in case of FXmto)
in the parameter definition file is too
long.

-303 Code conversion Length error Specify a code conversion file name less than 1025
characters.
A code conversion file name in the
parameter definition file is too long.

-304 VSE: Length error Specify a VSE parameter less than 21 characters.
A VSE parameter in the parameter
definition file is not corrected.

-305 VSE record-format: Length error Specify the record format for VSE less than 3
The record format for VSE in the characters.
parameter definition file is not
corrected.

-306 VSE record-length: Length error Specify the record length for VSE less than 6
The record length for VSE in the characters.
parameter definition file is not
corrected.

-307 VSE block-length: Length error Specify the block length for VSE less than 6
The block length for VSE in the characters.
parameter definition file is not
corrected.

7-20 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

Calling the Support Center
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.
• The exact content of any error messages displayed on the host system(s).
• The exact content of any error messages displayed by Storage Navigator.
• The Storage Navigator configuration information (use the FD Dump Tool).
• The service information messages (SIMs), including reference codes and
severity levels, displayed by Storage Navigator.
• 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 systems are c:\fal_error and c:\fal_error.bak, and
c:\fal_dump and c:\fal_dump.bak.
• Windows 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

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: (800) 446-0744
• Outside the United States: (858) 547-4526

Troubleshooting 7-21

Hitachi Cross-OS File Exchange User’s Guide

7-22 Troubleshooting

Hitachi Cross-OS File Exchange User’s Guide

 A
EBCDIC-ASCII Code Conversion
This appendix provides a list of EBCDIC to ASCII conversion values.

Table A-1 lists the EBCDIC-ASCII code conversions performed by the default
code conversion table which is provided with FCU).

EBCDIC-ASCII Code Conversion A-1

Hitachi Cross-OS File Exchange User’s Guide

 Table A-1 Default FCU EBCDIC-ASCII Conversions

Hex EBCDIC ASCII Hex EBCDIC ASCII Hex EBCDIC ASCII Hex EBCDIC ASCII

00 NUL NUL 20 DS 40 SP DS 60 - ENQ

01 SOH SOH 21 SOS a 41 61 / BEL
02 STX STX 22 FS b 42 62

03 ETX ETX 23 c 43 s 63

04 PF 24 BYP d 44 t 64

05 HT RLF 25 LF SMM 45 u 65

06 LC f 26 ETB IL 46 v 66

07 DEL “ 27 ESC CUI 47 w 67

08 GE p 28 h 48 x 68

09 RLF 29 i 49 y 69

0A SMM 2A SW 4A N 6A

0B VT VT 2B CUI 4B . ACK 6B ,

0C FF FF 2C 4C < DC4 6C % LF

0D CR CR 2D ENQ HT 4D ( 6D _ ~

0E SO SO 2E ACK LC 4E + CUI 6E >

0F SI SI 2F BEL DEL 4F | @ 6F ? SUB

10 DLE DLE 30 50 & ETB 70

11 DC1 DC1 31 j 51 z 71

12 DC2 DC2 32 SYN BS 52 72

13 DC3 DC3 33 l 53 73 ]

14 TM 34 PN m 54 74

15 e 35 RS n 55 [ 75

16 BS GE 36 UC o 56 76 {

17 IL g 37 EOT PF 57 77 A

18 CAN CAN 38 q 58 78 B

19 EM EM 39 r 59 79 ‘ -

1A CC k 3A ^ 5A ! SOS 7A :

1B CUI 3B CU3 5B $ BYP 7B #

1C IFS IFS 3C DC4 TM 5C * SW 7C @ SP

1D IGS IGS 3D NAK 5D ) 7D ‘ ESC

1E IRS IRS 3E 5E : CU3 7E = NAK

1F IUS IUS 3F SUB CC 5F ~ = 7F “ FS

80 C A0 J C0 { # E0 \ *

A-2 EBCDIC-ASCII Code Conversion

Hitachi Cross-OS File Exchange User’s Guide

Hex EBCDIC ASCII Hex EBCDIC ASCII Hex EBCDIC ASCII Hex EBCDIC ASCII

81 A / A1 V C1 A E1

82 B A2 s C2 B E2 S

83 C A3 t C3 C E3 T

84 D A4 u C4 D E4 U

85 E A5 v C5 E E5 V

86 F A6 w C6 F E6 W

87 G A7 x C7 G E7 X

88 H A8 y ‘ C8 H E8 Y

89 I A9 z : C9 I E9 Z !

8A D AA K CA Y EA 4

8B E AB L CB Z EB 5

8C F AC M CC EC 6

8D G AD [ $ CD ED 7

8E H AE O CE EE 8

8F I AF P CF EF 9

90 B0 Q D0 } ‘ F0 0

91 J B1 R D1 J F1 1

92 K , B2 D2 K . F2 2 SYN

93 L % B3 D3 L < F3 3

94 M _ B4 D4 M ( F4 4 PN

95 N > B5 D5 N + F5 5 RS

96 O ? B6 D6 O | F6 6 UC

97 P B7 D7 P & F7 7 EOT

98 Q B8 \ D8 Q F8 8

99 R B9 D9 R F9 9

9A ^ ; BA S DA FA

9B BB T DB FB

9C BC U DC 0 FC

9D BD ] ) DD 1 FD

9E BE W DE 2 FE

9F } BF X DF 3 FF

EBCDIC-ASCII Code Conversion A-3

Hitachi Cross-OS File Exchange User’s Guide

A-4 EBCDIC-ASCII Code Conversion

Hitachi Cross-OS File Exchange User’s Guide

 Acronyms and Abbreviations
ASCII American National Standard Code for Information Interchange

BL block length

CKD count key data

CR carriage return
CVS custom volume size

D delimiter
DAM direct-access method (not supported by FX)
DAT digital audio tape
DO dataset organization
DS dataset size

EA EBCDIC/ASCII (includes EBCDIC-to-ASCII and ASCII-to-EBCDIC)

EBCDIC extended binary-coded decimal interchange code
Emp empty file option
EOF end of file

F fixed-length and de-blocking (mainframe record format)

FAL File Access Library
FB fixed-length and blocking (mainframe record format)
FC fibre channel
FCU File Conversion Utility
FD floppy disk
FWD fast-wide differential
FX Hitachi Cross-OS File Exchange
FXmto Hitachi Cross-OS File Exchange – mainframe to open
FXotm Hitachi Cross-OS File Exchange – open to mainframe
FXoto Hitachi Cross-OS File Exchange – open to open

GUI graphical user interface

HMBR Hitachi Multiplatform Backup/Restore

HRX Hitachi RapidXchange (name for FX on Lightning 9900V/9900)

KB kilobyte

LDEV logical device

LF line feed

Acronyms and Abbreviations Acronyms-1

Hitachi Cross-OS File Exchange User’s Guide

 LSM Logical Storage Manager
LU logical unit
LUN logical unit number
LVI Logical volume image

MF mainframe
mto mainframe-to-open
MVS Multiple Virtual Storage

OPEN-x standard LU type (e.g., OPEN-3, OPEN-9)

OS operating system
otm open-to-mainframe
oto open-to-open

PAM partitioned access method (not supported by FX)

R0 record 0
RDW record description word
RF record format
RL record length

SAM sequential-access method, System Administration Manager (HP-UX)

SCSI small computer system interface
SLES SuSE Linux Enterprise Server
SMIT System Management Information Tool (IBM AIX)

V variable-length and de-blocking (mainframe record format)

VB variable-length and blocking (mainframe record format)
VIR Virtual LVI/LUN
volser volume serial number
VOS3 Virtual-Storage Operating System 3 (a Hitachi OS)
VSAM Virtual Storage Access Method (not supported by FX)
VSE Virtual Storage Extended
VSN volume serial number
VSP Hitachi Virtual Storage Platform
VTOC volume table of contents

Acronyms-2 Acronyms and Abbreviations

Hitachi Cross-OS File Exchange User’s Guide

Hitachi Cross-OS File Exchange User’s Guide
Hitachi Data Systems

Corporate Headquarters
750 Central Expressway
Santa Clara, California 95050-2627
U.S.A.
Phone: 1 408 970 1000
www.hds.com
info@hds.com

Asia Pacific and Americas

750 Central Expressway
Santa Clara, California 95050-2627
U.S.A.
Phone: 1 408 970 1000
info@hds.com

Europe Headquarters
Sefton Park
Stoke Poges
Buckinghamshire SL2 4HD
United Kingdom
Phone: + 44 (0)1753 618000
info.eu@hds.com

MK-96RD647-08