Hitachi Universal Storage Platform V Cross-OS File Exchange User’s Guide FASTFIND LINKS Document Organization Product Version Getting Help Contents MK-96RD647-01
Copyright © 2007 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED Notice: 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 Data Systems Corporation (hereinafter referred to as “Hitachi Data Systems”).
Contents Preface .................................................................................................. vii Overview of Hitachi Cross-OS File Exchange (FX) .................................... 1-1 About Cross-OS File Exchange Operations .............................................. 2-1 Components .....................................................................................................2-2 FX Volume Types.................................................................................
Environment Variables and Functions ........................................................ 2-34 Bidirectional Data Transfer .............................................................................. 2-36 Preparing for Cross-OS File Exchange Operations.................................... 3-1 System Requirements ....................................................................................... 3-2 VSE Requirements and Restrictions .............................................................
Performing Cross-OS File Exchange Operations....................................... 5-1 Performing File Transfer Operations - UNIX .........................................................5-3 Starting the FCU GUI for UNIX.....................................................................5-3 Performing File Transfer Operations (UNIX) ..................................................5-6 Using the listvol Function (UNIX) ............................................................
FAL Usage Scenario ........................................................................................ 6-33 Troubleshooting ................................................................................... 7-1 Troubleshooting ............................................................................................... 7-2 Error Codes and Messages ................................................................................ 7-3 FCU Error Codes for UNIX............................................
Preface This Hitachi TagmaStore® USP and NSC Cross-OS File Exchange (FX) User’s Guide describes and provides instructions for installing and using the FX feature of the Hitachi TagmaStore Universal Storage Platform V (USP V) and Network Storage Controller (NSC) disk array subsystems. Please read this document carefully to understand how to use this product, and maintain a copy for reference purposes.
Intended Audience This document is intended for system administrators, Hitachi Data Systems representatives, and Authorized Service Providers who are involved in installing, configuring, and operating the Hitachi Universal Storage Platform V storage system. This document assumes the following: • The user has a background in data processing and understands RAID storage systems and their basic functions.
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 Exchange This chapter provides a brief overview FX functions, features, and benefits.
Document Conventions The terms “Universal Storage Platform V” and “USP V” refer to all models of the Hitachi Universal Storage Platform V, unless otherwise noted. This document uses the following typographic conventions: Typographic Convention Description Bold 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.
Convention for Storage Capacity Values Physical storage capacity values (e.g., disk drive capacity) are calculated based on the following values: 1 1 1 1 1 KB = 1,000 bytes MB = 1,0002 bytes GB = 1,0003 bytes TB = 1,0004 bytes PB = 1,0005 bytes Logical storage capacity values (e.g.
The Hitachi Data Systems customer support staff is available 24 hours/day, seven days a week.
Comments Please send us your comments on this document. Make sure to include the document title, number, and revision. Please refer to specific section(s) and paragraph(s) whenever possible. • E-mail: doc.comments@hds.com • Fax: 858-695-1186 • Mail: Technical Writing, M/S 35-10 Hitachi Data Systems 10277 Scripps Ranch Blvd. San Diego, CA 92131 Thank you! (All comments become the property of Hitachi Data Systems Corporation.
1 Overview of Hitachi Cross-OS File Exchange (FX) This chapter provides a brief overview FX functions, features, and benefits. The Hitachi Cross-OS File Exchange (FX) feature enables data stored on the TagmaStore® USP subsystems to be converted and transferred between z/OS® and open-system platforms and between different open-system platforms. The FX mainframe-to-open (FXmto) capability enables you to transfer data from z/OS (mainframe) datasets to open-system files.
• All mainframe. The TagmaStore subsystems can be configured with all ExSA (no FC ports). This type of subsystem is called an all-mainframe subsystem. FX is not used on the all-mainframe TagmaStore subsystem. Note: The Hitachi Multiplatform Backup (MBU) feature of the TagmaStore USP and NSC subsystem enables you to implement z/OS-based backup/restore operations (device-level only) for the open-system data stored on the multiplatform TagmaStore USP and NSC.
Overview of Hitachi Cross-OS File Exchange (FX) Hitachi USP V Cross-OS File Exchange User’s Guide 1-3
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 Figure 2-1 illustrates the typical system configurations required for FXmto and FXotm operations. FXmto/otm operations are performed using the File Conversion Utility (FCU) and File Access Library (FAL), which are installed on the open-system host(s). File Conversion Utility (FCU) Application program Utility program Application program Utility program File Access Library (FAL) OS (MVS or VSE) OS (UNIX, PC server) ExSA (ESCON®) interface Fibre-channel interface Database 1 (e.g.
File Conversion Utility (FCU) Application program File Access Library (FAL) Utility program File Conversion Utility (FCU) Formatter/ Allocater (FMT/ALC) Formatter/ Allocater (FMT/ALC) Application program File Access Library (FAL) Utility program OS (UNIX, PC server) OS (UNIX, PC server) Fibre-channel interface Fibre-channel interface Open-System Files Intermediate File (SAM dataset) Open-System Files (FBA format) (CKD format) (FBA format) Volume dedicated to open system Figure 2-2 Share
FX Volume Types The FXmto and FXotm volumes are z/OS devices that can only be accessed by open-system hosts using the FAL/FCU software. The FXoto volumes are opensystem devices that cannot be accessed by z/OS hosts. FX operations are performed using the following types of FX volumes on the TagmaStore USP and NSC subsystems: • FXmto, FXotm. The FX -A volumes can be used for FXmto and FXotm operations. z/OS hosts have normal read/write access to -A volumes.
MAINFRAME OPEN SYSTEM Cyl# 0 Label area Cyl# 0 Read/Write VTOC Datasets Read/Write Read only Cyl# MAX. Management area Read/Write Cyl# max. Figure 2-4 3390-3B/9B/LB Volume Structure (FXmto) Note: The open-system host accesses only the volume table of contents (VTOC) area on -B volumes. Catalog or security control functions cannot be used to provide access control for these volumes. • FXotm. The FX -C volumes can only be used for FXotm operations.
MAINFRAME OPEN SYSTEM Label area Cyl# 0 No Access Cyl#0 VTOC 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.
Note for AIX: When installing FX devices in an AIX environment, the following notes apply: • When the UserID is not the root, a patch is required. • AIX V5.1 can be used with 64bitFAL. Please contact your IBM technical representative for assistance. Note for Microsoft Cluster Server: When installing FX devices in a Microsoft Cluster Server (MSCS) environment, you must write signatures on the FX volumes before configuring MSCS. • The MSCS server cannot connect volumes that do not have signatures.
• Code conversion (CC) • Padding (PAD) • Delimiters (DEL) • Record description word (RDW) • VSE record (VSE) • Empty file (Emp) Note: For FAL/FCU versions earlier than 01-XX-50, Multiple Volume Dataset is not supported. When a dataset is spanned over multiple volumes, only the portion of the dataset within one volume will be processed. For FAL/FCU versions 01-XX-50 or later, Multiple Volume Dataset is supported only for FXmto. Note: FAL/FCU supports two kinds of mainframes, MVS and VSE.
Table 2-1 Default EBCDIC-ASCII Code Conversion Table for FCU H L 0 1 0 NUL DLE DS (00) (10) 1 SO H DC1 2 STX DC2 FS SYN (02) (12) (82) 3 ETX DC3 (03) (13) (83) PF TM BYP PN (9C) (9D) (84) (94) LF RS (85) (0A) (95) LC BS ETB UC (86) (08) (17) (96) DEL IL ESC EOT (7F) (87) (1B) GE CAN (97) (18) (01) 4 5 6 7 8 (11) HT (09) 2 3 4 5 6 7 8 9 A B C SP & - (80) (90) (20) (26) (2D) SO S (91) (A0) (A9) { } \ 0 (BA) (C3) (CA)
EBCDIC (IBM) 2-10 0123 4567 About Cross-OS File Exchange Operations Hitachi USP V Cross-OS File Exchange User’s Guide
Table 2-2 User-Defined Code Conversion Table Item Requirement(s) Size 256 bytes Format Binary data Code length One byte (two-byte codes cannot be converted) File name The following sequences of characters cannot be used in the file name: EA EcA EkJ No If the file name for the code conversion table contains any of these sequences, FCU will ignore the file and use the default table instead.
FAL/FCU Pipe Function Details FCU can carry out data transmission to a pipe file. A user application opens and reads this pipe file, and a direct data transmission is attained between the application and FCU. There is no need for it to be output as a file on an HDD. A named-pipe name is specified in a parameter definition file as the output file name. “PIPE=Yes” needs to be specified as an option.
Figure 2-7 illustrates the Pipe function process. FCU . start | create a named pipe | open pipe(‘w’ mode) | waiting send data entries | send data OK | write data | close pipe | end Figure 2-7 Application/Utility Program | | open pipe(‘r’ mode) | waiting receive data entries | | receive data OK | read data | close pipe | | Pipe Function Process Outline Padding (PAD) Option The padding option can be used for FXmto with variable-length source datasets and for FXotm with fixed-length target datasets.
Note: If you use FXmto with padding, the data cannot be transferred back to the original z/OS dataset (the FXotm target dataset will not be compatible with the original dataset). If you use FXotm with padding, the delimiter option is required. Delimiter (DEL) Option The delimiter option can be used for both FXmto and FXotm operations and enables variable-length records to be transferred between platforms without losing compatibility with the original dataset.
Note: FCU version 01-01-38 or later for UNIX and FCU version 01-01-36 or later for Windows 2000/2003/Windows NT are required for the empty file option.
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.
FXmto Operations An FXmto operation transfers the data from a z/OS dataset on an FX volume to an open-system file on an open-system LU. The object data entities are those contained in all records between the beginning of the file and the end of the file. The end of a dataset is the EOF record or the end of the final extent. The end of an open-system file is the EOF. The FXmto source file must be located on an FX -B or -A volume on the subsystem.
FXmto with Fixed-Length Record Format Each fixed-length record in a z/OS dataset includes only the fixed-length data entity. The record length defined for a fixed-length dataset equals the actual length of each data entity. The padding option cannot be used for FXmto with fixed-length records. No padding, no delimiters. Figure 2-9 shows an FXmto operation for a fixed-length source dataset. Padding cannot be added to fixed-length records.
FXmto with Variable-Length Record Format Each variable-length record in a z/OS dataset includes a four-byte RL field and the variable-length data entity. The record length defined for a variable-length dataset equals the maximum allowable record length. Note: If you want to be able to transfer the data back to the original z/OS dataset later, you must use FXmto without padding and with delimiters. No padding, no delimiters.
Source Dataset Open-System Target File Record length (max) RL Record 1: Data entity 1 RL Record 2: Data entity 2 RL Record 3: Data entity 3 Figure 2-12 Record length (max) – 4 bytes Data entity 1 → padding Data entity 2 Data entity 3 padding FXmto with Variable-Length Records: Padding With delimiters. Figure 2-13 shows an FXmto operation with delimiters (D) for a variable-length source dataset.
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 RL Record 1: Data entity 1 RL Record 2: Data entity 2 RL Record 3: Data entity 3 Figure 2-14 Record length (max) − 3 or 2 bytes Data entity 1 → D padding Data entity 2 Data entity 3 D D padding 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).
FXmto with Multiple Volume Datasets Multiple Volume Dataset is supported only for FXmto, when the version is 01XX-50/ YY(XX=01 or 02, 03 or 04) or higher. Table 2-4 Illustrates this. Note: Multiple Volume Dataset is not supported for FXotm. A multiple volume definition file (multidef.dat) is necessary in current directory. FAL will check Dataset Serial number, Data set serial number and Last volume containing data in this data set in Data set indicators on VTOC DSCB1.
FXotm Operations An FXotm operation transfers the data from an open-system file on an FX volume to a target dataset on an z/OS volume. The FXotm source file must be located on an FX -C or -A volume on the subsystem. FCU does not automatically create the FXotm target dataset. The target dataset must be created and properly formatted prior to beginning the FXotm operation. The FCU software performs the FXotm data transfer operations. FCU version 01-01-40 or later is required for VSE target datasets.
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.
With delimiters. The figure below shows an FXotm operation for a fixedlength 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).
Figure 2-18 FXotm with Fixed-Length Records: Padding and Delimiters Note: FCU does not extract padding from FXotm source files. If the FXotm source file contains delimiters but you specify No for the delimiter option, the delimiters will be regarded as part of the data entities and will be transferred to the target dataset.
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.
With padding and delimiters. The figure below shows an FXotm operation with padding for a variable-length source file with delimiters. FCU version 0101-41 or later is required for FXotm with padding added to variable-length source files. FCU adds padding, extracts and transfers the data entities with padding to the target dataset, and automatically adds the four-byte RL field. The delimiters are not transferred. The target dataset must have fixed-length record format with record length defined as needed.
Note: FCU version 01-01-41 or later is required for FXoto operations using ALC-generated datasets on OPEN-x FMT volumes. The FCU file transfer options (code conversion, padding, delimiters, etc.) can be used on the FXotm and FXmto sub-operations as needed. • Code conversion is not available for FXoto transfers. • Padding can be used but will render the target file incompatible with the source file due to the change in record format from variable-length to fixedlength.
Note: For 01-02-48 and earlier, do not access the FX volume from FAL/FCU when AIX is accessing it. For 01-02-50 and earlier, do not access the FX volume from FAL/FCU when Windows 2000/2003/Windows NT is accessing it. Note: Please note the following restrictions for the listed operating systems: • For UNIX operating systems, if the version is 01-02-48 and later, FXotm can run several different datasets simultaneously.
• Reserved by open-system host. When an FX volume is reserved by the open-system host, FX operations can be performed only from the host that reserved the volume. FX operations from any other open-system host will terminate unsuccessfully. Open-system reserve does not affect z/OS access to the FX volume. • Unreserved. When an FX volume is not reserved by any z/OS or opensystem host, FX operations can be performed from any open-system host using FAL/FCU.
• 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.
AIX Reserve Function AIX Reserved Retry Function For FX versions 01-XX-61 and earlier, an AIXsystem error will occur when you use FX to send data to a reserved volume on another system. For FX versions 01-XX-62 and later, you can retry sending data to the reserved volume by specifying the wait time and retry count for the environment variable of the other system. FX can send data again when the reserved volume is released by the other system. The following table shows the AIX reserve functions.
– • • If other values outside the range are given, the default value applies. Retry Wait Time Function:You can set the wait time interval by specifying the environment variable(FAL_RETRY_WAIT_TIME). FX attempts to send data during reserved status. – The default is 1 second, where no definition of the environment variable is given. – The range of the FAL_RETRY_WAIT_TIME variable is 1-60 seconds. – If other values outside the range are given, the default value applies.
Bidirectional Data Transfer FX supports bidirectional data transfer for both fixed-length and variablelength z/OS datasets. Bidirectional data transfer involves transferring data from z/OS datasets to open-system files and then back to the original z/OS datasets again. The requirements for bidirectional data transfer are: 2-36 • For all FXmto operations, do not specify the record description word (RDW) option.
About Cross-OS File Exchange Operations Hitachi USP V Cross-OS File Exchange User’s Guide 2-37
3 Preparing for Cross-OS File Exchange Operations This chapter describes the system requirements and volume configuration necessary to run and operate FX. It also provides instructions on how to install FX.
System Requirements The user should examine existing data exchange needs carefully, especially the desired number of FX volumes to be installed and configured, prior to TagmaStore USP or NSC system configuration. This is due to the possible need to reconfigure and reformat entire array groups, depending on the microcode level of the subsystem. The system requirements for FX are: • FAL/FCU CD for the applicable open-system platform(s).
• Open-system platforms and operating system (OS) version level(s): – 32bitFAL: HP-UX 10.2 and 11.0, 11i, 11iV2 Solaris 2.5, 2.6, 7, 8, 9 (version 2.5 = Ver. 01-XX-47 or earlier) IBM® AIX® 5.3, 5.2ML02, 5.1ML02, 4.1.x, 4.2.x, 4.3.xML02, 5 (version 4.1 = Ver. 01-XX-47 or earlier) Windows® 2000 SP4(x86)/2003 SP1(x86)/NT® 4.0 SP6(x86)(IA64)(x64) (Workstation or ServerTM) HP® Tru64 UNIX V5.1a Red Hat Linux 7.2: AS2.1, AS3.0/IA64 – 64bitFAL: HP-UX 11.0, 11i, 11iV2 Solaris 8, 9 IBM AIX 5.3, 5.2, 5.1, 4.3.
64-bit Version FCU FX supports the 64-bit version FCU. The application method is the same as for the 32-bit version FCU. Note: The 64-bit version FCU does not support a GUI interface. FX version 01-04-61/20 supports Solaris, HP-UX, AIX 4.3, and AIX 5L operating systems. FX version 01-04-62/20 supports Red Hat Linux AS3.0/IA64 operating system. VSE Requirements and Restrictions FX supports the VSE operating system.
When you use MTO and OTM for the dataset allocated by VSE2.3, you must specify RF (Record Format), RL(Record Length) and BL(Block Length) by using the correct VSE parameters. When you use MTO and OTM for the dataset allocated by VSE2.5, FX can transfer data without a VSE parameter. Table 3-2 Support Matrix for VSE OS, VSE Parameter and Record Format OS andFX Version Record Format VSE Parameter F FB V VB VSE2.3 and previous Yes (FX: 01-xx-58 and previous) No VSE2.
s#1: RL(Input value for VSE parameter) = RL(value on VTOC) + 4 ≦32756 #2: BL(Input value for VSE parameter) = BL(value on VTOC) + 8 ≦32760 Note 2: It is possible to transfer data between the correct dataset attributes (5≦RL≦BL-4).
Table 3-3 Platforms and Associated Operating Systems Operating System/Platform Compiler Red Hat Linux 7.2 (Kernel version 2.4.7-10) and Red Hat Linux AS2.1 and AS3.0 gcc(Ver.2.96-98) glibc(Ver.2.2.4-13) Solaris Work Shop Compilers 4.2.1 Windows NT 4.0 service Pack 6a Visual C++® 6.0 SP4 HP-UX 10.20 HP® 92453-01 A.10.32.03 HP® C Compiler AIX4.3 C® for AIX 4.4 AIX5L C® for AIX, Version 5.0 HP® Tru64 Digital UNIX Compiler Driver 3.11 DEC C V5.6-075 on Digital UNIX V4.0 (Rev.
3-8 • 3390-9A: Can be used for both FileExchangemto and FileExchangeotm. The same access as for 3390-9 is allowed from Mainframe hosts. Read and write are possible from Open system hosts. • 3390-9B: Can be used only for FileExchangemto. The same access as for 3390-9 is allowed from Mainframe hosts. Read only is allowed from Open system hosts. • 3390-9C: Can be used only for FileExchangeotm. The same access as for 3390-9 is allowed but read only from Mainframe hosts.
Interoperability with HDLM When FX is used with HDLM, the FAL/FCU version must be 01-03-56 or later. The appropriate support platform versions are shown in Table 3-5.
Installing and Configuring the FX Volumes The FX volumes are installed and configured during TagmaStore USP and NSC installation and configuration. The FX volumes should be dedicated to data exchange operations to avoid accidental overwriting or deletion of important data. The FXmto volumes (-B and -A) contain z/OS data to be transferred to open-system LUs. The FXotm volumes (-C and -A) contain open-system data to be transferred to z/OS volumes.
– Defining RAW Devices. Those volumes which are to be used as intermediate volumes and to be shared between open systems must be defined as OPEN-3/8/9/K/E/L/M/V emulation type for RAID200/300, and must be defined as “raw” devices from each host server. From the open systems, there are no means to distinguish OPEN-3/8/9/K/E/L/M/V for open system dedicated volumes from these FX volumes. Please make sure not to confuse the usage on those volumes in the host systems.
For Solaris, use the following partition sizes for the FX volumes, and use 2 (two) for the number of alternate cylinders (Table 3-6): Table 3-6 LVI 3-12 Partition Sizes for TagmaStore USP and NSC Subsystems 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 - 49
Note 1: For further information on Solaris cylinder partition sizes, please refer to the Hitachi TagmaStore USP and NSC LUN Expansion and Virtual LVI/LUN User's Guide (MK-94RD205), and the Hitachi TagmaStore USP and NSC Sun Solaris Configuration Guide(MK-94RD236) • Volume labels. An FX volume with a volume label cannot be shared between open-system platforms which use volume labels.
Table 3-7 Sharing FX Volumes between Open-System Platforms IBM AIX No label Label write option Label autowrite HP-UX SequeNT DYNIX® Windows 2000/200 3/ Windows NT HP®True64 ® UNIX ® Solaris Linux 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 HPTrue64 / UNIX OK OK OK CHK CHK Windows 2000/200 3/ Windows NT OK OK OK OK CHK CHK CHK OK Solaris OK OK OK OK OK OK
Installing the FAL/FCU Software The FAL/FCU software must be installed on the UNIX/NT server(s) attached to the subsystem. FAL/FCU software installation for the UNIX-based platforms is different from FAL/FCU installation on Windows 2000/2003/Windows NT. The following sections provide instructions for installing FAL/FCU version 01-0136/38 or later. For instructions on installing versions 01-01-24 and earlier, please refer to previous revisions of this document.
4. Make sure the following six directories exist on the open-system host. If not, create the directories using the mkdir command (e.g., # mkdir /usr/lib/X11/app-defaults). /usr /usr/lib /usr/bin /usr/lib/X11 /usr/include /usr/lib/X11/app-defaults 5. Move to the root directory. 6. For UNIX-based systems, copy the FAL/FCU software from the installation CD-ROM as follows: # cpio -iBmuv < CD_device_file_name/d Note: Use the full device file name: wildcards will not work.
7. For Solaris you must set a path to the resource file for each FAL/FCU user: a) For C shell, add the following line to the end of the .cshrc file in the home directory. If .cshrc does not exist, create it and enter the following line: setenv XFILESEARCHPATH /usr/lib/X11/appdefaults/%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.
64-Bit FAL/FCU Software To install the 64bitFAL/FCU software on a UNIX-based platform: 1. Log-in as "root". 2. Set CD-ROM, in which the 64bitFAL/FCU is stored, to the drive. 3. Mount it. 4. Check to see if the following directories currently exist. If they do not, create them as follows: a. All Platforms: /usr, /usr/lib b. Solaris: /usr/lib/sparcv9 c. HP-UX: /usr/lib/pa20_64 5. Move to the root directory 6. Copy 64bitFAL from CD-ROM 7.
Installing FAL/FCU on Windows To install the FAL/FCU software on a Windows 2000/2003/Windows NT-based platform: 1. If FAL/FCU is already installed, uninstall it before installing the new version. a) To uninstall FAL/FCU version 01-01-25 or later, use the Windows Add/Remove Programs utility. b) To uninstall FAL/FCU versions 01-01-24 and earlier, delete the folder that contains the FAL/FCU software components (fcu.exe, fal.obj, and dataset.h). 2.
Uninstalling the FAL/FCU Software on UNIX-Based Platforms If you need to uninstall FAL/FCU version 01-01-36 or later: 1. Log in to the system as root. Remove the FAL/FCU for 32bit files using the rm command as follows, or string the commands: # # # # # # # # rm rm rm rm rm rm rm rm /usr/bin/fcu /usr/bin/fcunw /usr/include/dataset.h /usr/lib/libfal. /usr/lib/libuoc. /usr/lib/X11/app-defaults/FcuMf /usr/bin/mfformat /usr/bin/allocds 2.
• To uninstall FAL/FCU version 01-01-25 or later, use the Windows Add/Remove Programs utility. • To uninstall FAL/FCU versions 01-01-24 and earlier, delete the folder that contains the FAL/FCU software components (fcu.exe, fal.obj, and dataset.h). Note: For Windows 2000/2003/Windows NT, if the Installed Directory has a directory name using a “space” character, enter the following: fal.dll falmt.
Creating FXoto Volumes Using the FMT Utility After the FAL/FCU software has been installed on the open-system host(s), you can format the FXoto volumes using the FX Formatter (FMT) utility. This enables you to allocate FXoto intermediate datasets. The FMT utility for UNIX is a UNIX command executed from the UNIX command line. The FMT utility for Windows 2000/2003/Windows NT is a GUI. Note: FCU version 01-01-42 or later is required for the FMT utility.
Note: The VIR OPEN-x devices can also be called custom volume size (CVS) devices (e.g., OPEN-3-CVS). When formatting a VIR OPEN-x LU, use the number of cylinders defined for VIR minus seven (e.g., use 993 cylinders for a VIR device defined with 1000 cylinders). The cylinder size is: one cylinder = 15 tracks, one track = 96 sub-blocks, one sub-block = 512 bytes. Table 3-9 shows the relation between block length and write available capacity per track.
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 HPUX) 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.
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).
3-26 Figure 3-1 FMT Utility for Windows 2000/2003/Windows NT Figure 3-2 FMT Format Warning and Confirmation Figure 3-3 FMT Format Complete Message Preparing for Cross-OS File Exchange Operations Hitachi USP V Cross-OS File Exchange User’s Guide
Figure 3-4 FMT VOLSER Used Message Figure 3-5 FMT Error Message Preparing for Cross-OS File Exchange Operations Hitachi USP V Cross-OS File Exchange User’s Guide 3-27
Creating the FX Volume Definition File(s) The FX volume definition file contains the volume association parameters for the FX volumes on the TagmaStore USP and NSC. This file must be created before you can use FCU or FAL to access data on these volumes. The volume association parameters define the FX volume by associating the volume serial number (VSN or volser) with the open-system device file for the same logical volume. Table 3-10 describes the FX volume association parameters.
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.
/dev/rrzX1Y1Z1 /dev/rrzX3Y3Z3 /dev/rrzX4Y4Z4 (1) end (5) AAAAAA 3390-3A cccccc 3380-KB dddddd 3380-KA (2) (3) MFN MFN MVS VOS3 (4) (5) Figure 3-9 FX Volume Definition File for DIGITAL Tru64 UNIX (oto Shown) (6) Note: X = b through h = LUN1 through LUN7 (no letter is used for LUN0); Y = fibre bus number × 8 + SCSI TID; Z = partition = a through h. For example, rrzc18a = SCSI TID 2, LUN2 (partition a) on fibre bus 2. Note: OPEN-x = 3, 8, K, E, L, M , 9 or V \\.\PHYSICALDRIVE0 AAAAAA 3390-3A \\.
(7) Figure 3-13 FX Volume Definition File for Linux Preparing for Cross-OS File Exchange Operations Hitachi USP V Cross-OS File Exchange User’s Guide 3-31
Verifying Mainframe Dataset Requirements FAL and FCU have specific requirements for the FX source and target datasets. Table 3-11 specifies the requirements for FX datasets. The FCU GUI (see sections Performing File Transfer Operations - UNIX and Performing File Transfer Operations – Windows) allows the user to display the dataset attributes and verify the dataset requirements.
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.
-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.
– 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.
3-36 Figure 3-14 ALC Utility for Windows 2000/2003/Windows NT systems Figure 3-15 ALC Disk Not Found Message Figure 3-16 ALC Allocation Complete Message Preparing for Cross-OS File Exchange Operations Hitachi USP V Cross-OS File Exchange User’s Guide
Figure 3-17 ALC Error Message Preparing for Cross-OS File Exchange Operations Hitachi USP V Cross-OS File Exchange User’s Guide 3-37
3-38 Preparing for Cross-OS File Exchange Operations Hitachi USP V Cross-OS File Exchange User’s Guide
4 Using the Cross-OS File Exchange Software This chapter describes the user interface and the commands available to an FX user.
FCU for UNIX 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.
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-rnormal -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.
File Conversion Utility Help File Parameter File Volume File M to O Direction O to M OK Input File Output File Cancel Code Conversion E<->A EcA No Padding Yes Delimiter CR Emp Yes No RDW Yes No FILE No LF 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.
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.
• 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.
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.
– 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.
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 FCU for Windows FCU Version and Copyright Dialog To start the FCU GUI program for Windows 2000/2003/Windows NT systems: 1. Log on with Administrator access privileges. 2.
4. The FCU GUI program now starts loading. The FCU version and copyright screen (see Figure 5-6) is displayed while FCU is loading. When FCU is finished loading, the FCU main panel is displayed (see section 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.
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. File commands: New Open Save Parameter-Load commands: Load-Top Load-Previous Load-Next Load-Bottom Parameter commands: Save-Insert Save-Replace Delete Wipe View commands: Volume info. MF-file info. Options Error info.
• 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 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-6).
– { = the dataset can be processed by FCU. 8 = 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.
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 4-16 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.
– 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.
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.
WARNING: In some early versions of FCU for Windows 2000/2003/Windows NT systems, FCU may overwrite existing Windows 2000/2003/Windows NT systems target files without requesting confirmation. 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.
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 hae been entered correctly and try executing the command again. See Appendix C for further information on errors. 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.
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.
Figure 4-17 FCU Log File Display in Notepad Format Utility for Windows After the FAL/FCU software has been installed on the open-system host(s), you can format the FXoto volumes using the FX Formatter (FMT) utility. This enables you to allocate FXoto intermediate datasets. The FMT utility for UNIX is a UNIX command executed from the UNIX command line. The FMT utility for Windows 2000/2003/Windows NT is a GUI. Note: FCU version 01-01-42 or later is required for the FMT utility.
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 supported 5818 5818 19752 (min 19759*n-7, 65534) OPEN-L not supported 5818 5818 49429 (min 49439*n-7, 65534) OPEN-V not supported not supported not supported 65534 (min(Vc*n*128/ 96-7,65534) (see Note 4) 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.
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
Figure 4-18 FMT Utility for Windows 2000/2003/Windows NT 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.
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.
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.
Figure 4-23 ALC Utility for Windows 2000/2003/Windows NT systems 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. Figure 4-24 ALC Disk Not Found Message 4.
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.
If the allocate operation did not complete successfully, one of the following error messages is displayed (n = system error code): Open error! (n) Seek error! (n) Read error! (n) Write error! (n) Close error! (n) Open process error on the FXoto volume. Seek process error on the FXoto volume. Read process error on the FXoto volume. Write process error on the FXoto volume. Close process error on the FXoto volume. 11.
Using the Cross-Os File Exchange Software Hitachi USP V Cross-OS File Exchange User’s Guide 4-31
5 Performing Cross-OS File Exchange Operations This chapter describes how to operate FX. • Performing File Transfer Operations - UNIX • Performing File Transfer Operations – Windows FX file transfer operations are performed using the FCU GUI software installed on the opensystem host(s) attached to the TagmaStore USP and NSC subsystem.
The FCU GUI for UNIX -based platforms and the FCU GUI for Windows 2000/2003/Windows NT 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 2000/2003/Windows NT systems. For information on using FCU from the UNIX command line (without the GUI), see Appendix B.
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.
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-rnormal -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.
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.
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 that 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.
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 z/OS 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.
• 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. Creating FCU Parameter Definition Files (UNIX) To create an FCU parameter definition file using the FCU GUI for UNIX: 1. Start the FCU GUI for UNIX by entering fcu (see section Starting the FCU GUI for UNIX). Do not specify the -nw, -nc, or param option. 2.
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.
• 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.) g. iii) 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.
Note: Each parameter must be separated with one or more “space” character(s). Note: One data set information must be specified in one line. Note: 999 information can be specified in the multiple volume definition file. 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.
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 Hitachi USP V Cross-OS File Exchange User’s Guide 5-13
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.
# fcunw File Conversion Utility Ver.01-01-40/00 ← Start FCU with checking. ← FCU program version. mto VSN:dataset file_name EA No LF ok/cancel ? ok Now checking... Complete ← ← ← ← otm file_name VSN:dataset EA No No ok/cancel ? ok Input file : Open error (-350) (Fal error : xxx (System error : xxx ← Next set of parameters. ← Enter ok or cancel. Error info displayed. mto VSN:dataset file_name EA No LF ok/cancel ? ok Now checking...
Figure 5-5 5-16 Using the -P param Option Performing Cross-Os File Exchange Operations Hitachi USP V Cross-OS File Exchange User’s Guide
Performing File Transfer Operations – Windows Starting the FCU GUI To start the FCU GUI program for Windows 2000/2003/Windows NT 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.
Figure 5-6 5-18 FCU Version and Copyright Screen (Windows 2000/2003/Windows NT Systems) Performing Cross-Os File Exchange Operations Hitachi USP V Cross-OS File Exchange User’s Guide
Performing File Transfer Operations (Windows) To perform FX file transfer operations using the FCU GUI for Windows 2000/2003/Windows NT 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.
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 ( ).
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.
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 2000/2003/Windows NT systems, there will be a delay before you can access the FX volume. The length of delay varies according to individual server performance.
Creating FCU Parameter Definition Files (Windows) To create an FCU parameter definition file using the FCU GUI for Windows 2000/2003/Windows NT systems: 1. Start the FCU GUI for Windows 2000/2003/Windows NT systems (see section 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.
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.).
Creating Multiple Volume Definition Files (Windows) Multiple volume Dataset is supported for FXmto, when the version is 01-XX50/YY (XX=01 or 02) or later. Multiple volume Dataset is also supported for FXotm when the version is 01-XX-60/YY (XX=02, 03 or 04) or later. The name of the multiple volume definition file is “multidef.dat”. It must be placed under the current directory where the FAL/FCU is to be executed.
• 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.) m. iv) Each line above must be separated by using “Return” key. n. v) 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 data set information must be specified in one line.
Using FCU from the Command Line (Windows) To perform FX file transfer operations for Windows 2000/2003/Windows NT 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] – -cl : Specifying that all the log file for FCU will be cleared before stating FCU. – param UNIX.
5-28 Performing Cross-Os File Exchange Operations Hitachi USP V 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 2000/2003/Windows NT systems) and the header file dataset.h.
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: 6-2 • 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.
FAL Functions The FAL includes the following C functions (Visual C++ for Windows 2000/2003/Windows NT systems): • • • • • • Opening a dataset: datasetOpen (see section Opening a Dataset) Reading one record from a dataset: datasetGet (see section Reading Data) Writing one record to a dataset: datasetPut (see section Writing Data) Closing a dataset: datasetClose (see section Closing a Dataset) Acquiring error information: datasetGetLastError (see section Acquiring Error Information) Acquiring dataset attrib
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 Argument Return value Value Type Description pathname char * VSN:Dataset name VSN = 6-character volser. Volume must be listed in FX volume definition file.
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.
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 Argument Value Type datasetHandl e DATASET_HAND LE The datasetHandle value returned by the datasetOpen function. char * long Size of the buffer area.
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 Argument Return value Value Type Description datasetHandl e DATASET_HANDLE The datasetHandle value returned by the datasetOpen function.
Acquiring Dataset Attributes FAL provides several functions for acquiring the complete dataset attribute information for one or more datasets: datasetGetFileInformation, datasetFindFirstFile, datasetFindNextFile, and datasetFindClose.
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 z/OS 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.
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.
-1 Error 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 section Acquiring Error Information).
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.
Argument Return value recfm u_char text char [5] Value of recfm (one byte) obtained by attribute acquisition function datasetGetFileInformation, datasetFindFirstFile, or datasetFindNextFile.
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 z/OS datasets accessed by the FAL functions must be located on TagmaStore USP or NSC FX volumes. The FX volumes must be installed and configured correctly (see section Installing and Configuring the FX Volumes), the FAL/FCU software must be installed properly (see section Installing the FAL/FCU Software), and the FX volume definition file must be available and configured correctly.
# 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.
datasetGetFileInformation Acquire attribute information for the dataset. Error Confirm the dataset attributes. Open the dataset. datasetOpen Error Read one data record. datasetGet Error EOF Process the data that has been read. datasetGetLastError datasetClose Acquire error information. Close dataset. Error processing/termination. datasetGetLastError Acquire error information. Error processing/termination.
datasetFindFirstFile Acquire attribute information for the first dataset. List the dataset attribute information. To convert the DO or RF type into a character string, use: - datasetGetDsorgString, or - datasetGetRecfmStrng. Error Error Acquire attribute information for the next dataset. datasetFindNextFile Error To convert the DO or RF type into a character string, use: - datasetGetDsorgString, or - datasetGetRecfmStrng. List the dataset attribute information.
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
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 Abnormal end 0 Note 1: When you issue this function, you must issue dataset_FreeGlobal() in the en
Open Dataset Format: datasetError=dataset_Open(global,g_error,devname,dsname,voltype, mode) Table 6-13 Arguments, Types and Descriptions for Open Data Set 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 Abnormal end lo
int retcode; retcode = dataset_AllocGlobal(&memptr, &err, malloc, free); : datasetError = dataset_Open(memptr, &err,” HYPERLINK "\\\\.\\PHYSICALDRIVE1" \\.
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
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 global Description 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 Abnormal end -1 N
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 long (see Note 1) Abnormal end Return value: datasetError -1 This function closes a dataset. • 6-24 Return value: – When this function ends normally, “0” is returned.
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 Abnormal end 0 This function releases information stored area. • • Argument: – dgpp: Global memory area (Specify a Global memory area gotten by dataset_AllocGlobal.
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 Abnormal end -1 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.
Get Dataset Attribute Information 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 Abnormal end -1 An a
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 Specified Dataset Attribute Information Argument Type Description global void** Global memory area g_error long* An error information stored area ffd DATASET_FIND_DATA A dataset attribute information stored area long Abnormal end Return value: datasetError -1 This function returns top dataset attribut
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 ffd DATSET_HANDLE DATASET_FIND_DATA Dataset handler Return value: datasetError long -1 A dataset attribute information stored area Abnormal end This function gets a second dataset and more attribute information.
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 Abnormal end -1 This function declares the end of the process, and gets dataset attribute information using dataset_FindFirstFile and dataset_FindNextFile. • • 6-30 Argument (3): – global: Global memory area (Specify a Global memory area gotten by dataset_AllocGlobal.).
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 NT/Windows 2000/2003 systems: o. 1. Launch Developer Studio. p. 2. Create a new project. q. 3. Copy the following FAL files to the project folder/directory: • dataset.h • falmt.dll • falmt.lib r. 4. Select SETTING on the Developer Studio PROJECT menu. s. 5.
Error Information For details on error messages, see Appendix B. 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 6-32 FAL Multi-thread 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.
FAL Usage Scenario • Example 1: read data flowchart dataset_ AllocGlobal Keep work area for FAL error Open dataset dataset_Open error dataset_ GetFileInformation Get dataset attribute information error Check dataset attribute dataset_Get Read one data error EOF Process of reading data dataset_Close dataset_FreeGlobal Close dataset Release work area for FAL Error process/End process dataset_FreeGlobal Error process/End Performing File Access Library (FAL) Operations Hitachi USP V Cross-OS
6-34 Performing File Access Library (FAL) Operations Hitachi USP V Cross-OS File Exchange User’s Guide
11 Troubleshooting This chapter provides descriptions of error codes and support desk contact data.
Troubleshooting For general troubleshooting information on the TagmaStore USP and NSC subsystems, please refer to the Hitachi TagmaStore Universal Storage Platform User and Reference Guide (MK-94RD231) or Hitachi TagmaStore Network Storage Controller User and Reference Guide (MK-95RD279). The FAL/FCU software is not expected to fail in any way. When errors are detected, error codes and messages are displayed and/or logged.
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.
Error Code -16 Error Message and Description DATASET_ERROR_DATASET_NOT_CLOSED An attempt was made to open the dataset without closing it first. -17 DATASET_ERROR_BUFLEN_SHORT The buffer length specified by datasetGet is shorter than the actual record length. -18* DATASET_ERROR_VOLUME_LABEL_INVALID No standard volume label was found, or the contents of the VTOC are illegal. -19* DATASET_ERROR_VTOC_INVALID No VTOC found, or contents of VTOC are invalid.
Error Code -33 Error Message and Description DATASET_ERROR_PARAMETER_MISMATCH User-specified RF, BL, RL does not match the RF, BL, RL defined in the VTOC; or RF, BL, RL not specified and not defined in VTOC. -35 DATASET_ERROR_NO_LICENSE FAL can’t permit execution of software that doesn’t have a software license. -36 DATASET_ERROR_TIMEOUT_LICENSE FAL can’t permit execution of software with an expired software license trail time.
Error Code -50* Error Message and Description DATASET_ERROR_END_OF_FILE Recommended Action(s) 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 z/OS and open-system hosts.
Error Code -109 Error Message and Description Parameter file: DELIMITER error The delimiter option specified in the parameter definition file is not valid. Recommended Action(s) Make sure that the delimiter is specified as either CR, LF, or No. -110* Parameter file: Open error An error occurred when opening and outputting the parameter definition file. Display the system error code using the Help-Error command. Please refer to the OS user manual for information on system errors.
Error Code Error Message and Description Recommended Action(s) -124 Volume definition: MFtype error. Incorrect MFtype is specified in the volume definition file. Specified MFN or MFA in MFtype of the volume definition file. -125* Volume definition: VSN error Display the contents of the volume definition file using the Help-Volume command. Make sure that the VSN for the specified volume is correct. The VSN specified in the volume definition file is incorrect.
Error Code -141 Error Message and Description Input file error: Invalid record format The RF type of the dataset is not supported. -142 Input file error: Invalid block length The block length of the dataset is invalid. -143 Input file error: Invalid record length The record length of the dataset is invalid. -144* Recommended Action(s) Display the attribute information using the Help-MF-File command. The RF type must be fixed-length or variablelength.
Error Code -171 Error Message and Description Output file: Close error A file close error occurred in the output UNIX file. -180 UNIX/Open system file: Invalid directory name Recommended Action(s) Display the system error code using the Help-Error command. Please refer to the OS user manual for information on system errors. Check the specified directory name. The specified directory name is not valid. -181 UNIX file: Not a directory Check the specified directory name.
Error Code -206 Error Message and Description Recommended Action(s) RDW error: PADDING not supported Padding cannot be processed when RDW=Yes. Change the padding parameter to No. Padding is not specified as No when RDW=Yes. -207 RDW error: DELIMITER not supported Delimiters cannot be processed when RDW=Yes. Change the delimiter parameter to No. Delimiter is not specified as No when RDW=Yes. -210 Parameter file: Comment line This is a comment line in the parameter file.
Error Code -300 Error Message and Description Data error: Invalid record length The data length is not correct for the FXotm padding function. -301 Dataset error: Invalid record format The record format is not correct for the FXotm padding function. -302 Parameter error: Delimiter error The delimiter setting is not correct for the FXotm padding function. -319* Dataset: Open error An error occurred when opening the dataset.
Error Code -360* Error Message and Description Input file: Read error A read error occurred in the input UNIX file. -361* Output file: Write error A write error occurred in the output dataset. -362 Output file: Code conversion error An error occurred in the code conversion to the output dataset. -363 Get processing data error The acquisition of processing data failed. -370 Input file: Close error A file close error occurred in the input UNIX file.
Error Code -399 Error Message and Description Volume definition : VSN identification length error. Recommended Action(s) Specify the VSN identification length than 35 characters. The VSN identification length in the volume definition file is too long. -400 Parameter: Invalid input file name Specify only one file name as the input file. More than one input file name was specified.
FCU Error Codes for Windows Systems If FCU for Windows 2000/2003/Windows NT systems reports an error, use the View-Error information… command to view the most recent error. FCU for Windows 2000/2003/Windows NT 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.
-121 Volume definition file : Length error The record length in the volume definition file is too long. -124 Volume definition: Emulation type Length error An emulation type parameter in the volume definition file is too long. -125 Volume definition: MFtype Length error. Incorrect Specify the record length less than 2080 characters (not including delimiter). Specify an emulation type parameter less than 11 characters. Specified MFN or MFA in MFtype of the volume definition file.
-154 Mainframe file: Record format error An error is detected in the record format of the mainframe file. -170 Open system file: Open error An error is detected when opening the open system file. -171 Open system file: Read error For FXotm with the padding function, make sure that the target dataset has fixed-length record format (or change padding to No). Make sure that the open-system file name is specified correctly. Check if any system error is reported. Check the system error.
-240 Parameter: Direction, PAD, and DEL not matched For FXotm with the padding function, make sure that the delimiter option is specified as Yes (or set padding=No). The combination of otm direction, PAD=Yes, and DEL=No is not allowed. -241 Parameter: Direction and RDW not matched The combination of otm data transfer direction and RDW=Yes is not allowed. -242 Parameter: Code conv. and RDW not matched The combination of RDW=Yes and code conversion other than No is not allowed.
-307 VSE block-length: Length error Specify the block length for VSE less than 6 characters. The block length for VSE in the parameter definition file is not corrected.
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).
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).
He x EBCDIC ASCII Hex EBCDIC IL g 37 EOT CAN CAN 38 17 18 19 EM EM 39 r 59 1A CC k 3A ^ 5A ! SOS 5B $ BYP 7B # 5C * SW 7C @ 1B CUI 1C IFS 1D IGS 1E IRS 1F IUS IUS 3F C / 80 3B CU3 3C DC4 IGS 3D NAK IRS 3E IFS Hex EBCDIC ASCII Hex EBCDIC ASCII PF 57 77 A q 58 78 B TM 79 ‘ 7A : - SP 5D ) 7D ‘ ESC 5E : CU3 7E = NAK CC 5F ~ = 7F “ FS A0 J C0 { # E0 \ * A1 V C1 A E1 SUB 81 a 82 b A2 s C2 B E2
He x Hex EBCDIC ASCII Hex 9D BD ] ) 9E BE BF 9F EBCDIC ASCII } EBCDIC ASCII Hex DD 1 FD W DE 2 FE X DF 3 FF EBCDIC-ASCII Code Conversion Hitachi USP V Cross-OS File Exchange User’s Guide EBCDIC ASCII A-3
A-4 EBCDIC-ASCII Code Conversion Hitachi USP V Cross-OS File Exchange User’s Guide
EBCDIC-ASCII Code Conversion Hitachi USP V Cross-OS File Exchange User’s Guide A-5
Acronyms and Abbreviations ASCII American National Standard Code for Information Interchange BL block length CKD CR CVS count key data carriage return custom volume size D DAM DAT DO DS delimiter direct-access method (not supported by FX) digital audio tape dataset organization dataset size EA EBCDIC Emp EOF ESCON EBCDIC/ASCII (includes EBCDIC-to-ASCII and ASCII-to-EBCDIC) extended binary-coded decimal interchange code empty file option end of file Enterprise System Connection (IBM trademark for op
MF mto MVSTM mainframe mainframe-to-open Multiple Virtual Storage OPEN-x OS otm oto standard LU type, e.g.
Acronyms and Abbreviations Hitachi USP V Cross-OS File Exchange User’s Guide Acronyms-3
Acronyms-4 Acronyms and Abbreviations Hitachi USP V Cross-OS File Exchange User’s Guide
Index partition, 3-11 Support Center, Hitachi Data Systems, 7-22 system requirements, 3-2 A accessing FCU, 7-2 raw devices, 1-1 VSE® datasets, 7-5 T target code values, 2-8 Time_Out_Value, 2-12 C V commands deinstallation, 3-20 file menu, 4-5 help menu, 4-5 HRX file transfer operations, 2-3 Parameter Delete, 4-13, 4-18 Parameter Load, 4-13, 4-18 Parameter Save, 4-13, 4-18 Parameter-Save-Insert, 5-24 reserve, 2-31 TIME_OUT_VALUE, 2-12 View Status bar, 4-13 View Toolbar, 4-13 concurrent access support,
Hitachi USP V Cross-OS File Exchange User’s Guide
Hitachi USP V Cross-OS File Exchange User’s Guide
Hitachi USP V Cross-OS File Exchange User’s Guide
Hitachi USP V 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.
