HP StorageWorks P9000 User Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Storage
  5. P9000
  6. User manual
HP StorageWorks P9000 User Manual

HP StorageWorks P9000 User Manual

Data exchange user guide
Hide thumbs Also See for StorageWorks P9000:
Table of Contents

Quick Links

See also: Administrator's Manual, User Manual
HP StorageWorks P9000 Data Exchange User
Guide
Part Number: T1620-96016
First edition: October 2010
Table of Contents
loading

Related Manuals for HP StorageWorks P9000

Summary of Contents for HP StorageWorks P9000

  • Page 1 HP StorageWorks P9000 Data Exchange User Guide Part Number: T1620-96016 First edition: October 2010...
  • Page 2 Legal and notice information © Copyright 2007, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.

  • Page 3: Table Of Contents

    (4) Make Copy Files After Getting Information ................ 45 (5) Check Information for Sending Files ................. 46 (6) Output Traces of Record Size ..................46 (7) Output Traces (FCU Error Occurred) ................. 46 (8) Output Core Dump ......................46 HP StorageWorks P9000 Data Exchange User Guide...
  • Page 4 Interval Function for OtM Transfer Completion (Linux) ..............46 Environment Variable for Interval Time ................... 48 Display Window for Interval Function ..................48 3 Preparing for Data Exchange Operations ..........49 System Requirements ......................... 49 64-bit Version FCU ......................50 VSE Requirements and Restrictions ..................
  • Page 5 FCU Error Codes for UNIX ....................154 FCU Error Codes for Windows Systems ................163 Calling HP Technical Support ....................169 8 Support and Other Resources ............171 Related Documentation ......................171 Conventions for Storage Capacity Values ................... 171 HP StorageWorks P9000 Data Exchange User Guide...
  • Page 6 HP Technical Support ......................172 Subscription Service ........................ 172 HP Websites .......................... 172 Documentation Feedback ......................172 A EBCDIC-ASCII Code Conversion ............173 Glossary ..................177 Index ....................181...
  • Page 7 Data Exchange Volume Definition File for IBM AIX (mto/otm Shown) ......73 Data Exchange Volume Definition File for DIGITAL Tru64 UNIX (oto Shown) ....74 Data Exchange Volume Definition File for Windows (mto/otm Shown) ......74 HP StorageWorks P9000 Data Exchange User Guide...
  • Page 8 Data Exchange Volume Definition File for NCR UNIX ........... 74 Data Exchange Volume Definition File for DYNIX/ptx ........... 74 Data Exchange Volume Definition File for Linux ............75 ALC Utility for Windows Systems ................79 ALC Disk Not Found Message .................. 79 ALC Allocation Complete Message ................
  • Page 9 Format Requirements for Writing Variable-Length Records ........... 127 Example of Reading Data from a Mainframe Dataset Using FAL ........135 Example of Acquiring MF Dataset Attributes Using FAL ..........136 Example of Using FAL to Read Data ................ 147 HP StorageWorks P9000 Data Exchange User Guide...
  • Page 10 Tables Default EBCDIC-ASCII CC Table for FCU ..............21 User-Defined CC Table .................... 22 FXmto Record Format Requirements ................27 Multiple Volume Dataset/Serial Numbers ..............31 FXotm Record Format Requirements ................32 Shared Volume and Data Exchange Version ............... 38 Environment Variable (FAL_NO_RESERVE) and Open Mode .........
  • Page 11 FAL Multi-thread Error Codes .................. 146 Troubleshooting ....................149 FAL Error Codes ....................150 FCU Error Codes for UNIX ..................154 FCU Error Codes for Windows Systems ..............164 Default FCU EBCDIC-ASCII Conversions ..............173 HP StorageWorks P9000 Data Exchange User Guide...

  • Page 13: Overview Of Hp Storageworks Data Exchange Software

    The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer browser. Actual windows may differ depending on the operating system and browser used. GUI contents also vary with licensed program products, storage system models, and firmware versions. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 14 Overview of HP StorageWorks Data Exchange Software...

  • Page 15: About Data Exchange Operations

    FXmto/otm operations are performed using the FCU and FAL, which are installed on the open-system hosts. Figure 2 on page 16 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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 16: Fxmto And Fxotm System Configuration

    Figure 1 FXmto and FXotm System Configuration Figure 2 FXoto System Configuration About Data Exchange Operations...

  • Page 17: Data Exchange Volume Types

    -B volumes (except disk partitioning and labeling) to protect the mainframe data on these volumes. Figure 4 on page 18 shows the structure of the Data Exchange -B volumes. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 18: B/9B/Lb Volume Structure (Fxmto)

    Figure 4 3390-3B/9B/LB Volume Structure (FXmto) NOTE: The open-system host accesses only the VTOC area on -B volumes. Catalog or security control functions cannot be used to provide access control for these volumes. • FXotm. The Data Exchange -C volumes can only be used for FXotm operations. Open-system hosts have read/write access to the -C volumes, but must use Data Exchange to access these volumes as raw devices (no mount operation).

  • Page 19: Aix Installations

    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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 20: Fcu File Transfer Options

    CAUTION: Do not write a signature on Data Exchange volumes having emulation types 3390-3 X , 3390-9 X , 3390-L X , 3380-K X , or 3380-3 X ( 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.

  • Page 21: Default Ebcdic-Ascii Cc Table For Fcu

    (39) (8E) (92) (8A) (9A) (D5) (21) (CB) (3A) (C4) (5E) (D2) (E2) (E8) (EE) (F4) (FA) (0B) (8F) (8B) (9B) (2E) (24) (2C) (23) (C5) (CC) (D3) (E3) (E9) (EF) (F5) (FB) HP StorageWorks P9000 Data Exchange User Guide...

  • Page 22: Pipe Function

    < (0C) (1C) (8C) (14) (3C) (2A) (25) (40) (C6) (CD) (D4) (E4) (EA) (F0) (F6) (FC) ’ (0D) (1D) (05) (15) (28) (29) (5F) (27) (C7) (CE) (5B) (5D) (EB) (F1) (F7) (FD) > (0E) (1E) (06) (9E) (2B) (3B) (3E) (3D)

  • Page 23: Using The Pipe Function In Unix Systems

    • • 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: HP StorageWorks P9000 Data Exchange User Guide...

  • Page 24: Pad Option

    • 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. Figure 7 on page 24 illustrates the Pipe function process. Figure 7 Pipe Function Process Outline PAD Option The PAD option can be used for FXmto with variable-length source datasets and for FXotm with...

  • Page 25: Del Option

    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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 26: Vse 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). Figure 8 FXmto with the RDW Option 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 RF), RL, or BL of the dataset.

  • Page 27: Fxmto With Fixed-Length Record Format

    UNIX target file equals the original record length plus 1 byte for the delimiter. The resulting length of each data entity in a Windows target file equals the original record length plus 2 bytes for the delimiter. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 28: Fxmto With Variable-Length Record Format

    Figure 10 FXmto with Fixed-Length Records: Delimiters 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.

  • Page 29: Fxmto With Variable-Length Records: Padding

    The RL fields are not transferred. NOTE: If you use FXmto with padding and delimiters, you will not to transfer the records back to the original dataset later (the padding cannot be removed). HP StorageWorks P9000 Data Exchange User Guide...

  • Page 30: Fxmto With Multiple Volume Datasets

    Figure 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 3 bytes (minus 4 for the RL, plus 1 for the delimiter). The resulting length of each data entity in a Windows target file equals the maximum record length minus 2 bytes (minus 4 for the RL, plus 2 for the delimiter).

  • Page 31: Fxotm Operations

    FXmto transfer operation, the padding is transferred to the target dataset along with the data. If the source file contains delimiters, the delimiters are not transferred to the target dataset. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 32: Fxotm With Fixed-Length Record Format

    NOTE: Do not update the volume that is transferred directly by the FXotm. Table 5 FXotm Record Format Requirements FCU Direc- Record Format Requirements See Figure tion Source File Target Dataset FXotm Fixed-length: no padding, no delimiters Fixed-length Figure 15, page 32 FXotm Fixed-length containing padding Fixed-length...

  • Page 33: Fxotm With Fixed-Length Records: Padding

    4 bytes. If the length of any source data entity does not match the record length defined for the target dataset, The FCU aborts the operation and reports an error. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 34: Fxotm With Variable-Length Record Format

    Figure 18 FXotm with Fixed-Length Records: Padding and Delimiters NOTE: The 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.

  • Page 35: Fxoto Operations

    • The VSE record option does not apply to FXoto operations that access ALC-generated intermediate datasets on OPEN-x FMT volumes. The only time you would use the VSE option is when transferring HP StorageWorks P9000 Data Exchange User Guide...

  • Page 36: Host Access And I/O Contention

    a file between open-system platforms via a VSE dataset on an -A Data Exchange volume. In this case, you must use the VSE record option for both transfers (FXotm/mto). Host Access and I/O Contention The user must manage access to the FXmto and FXotm volumes to prevent illegal I/O access contention between the mainframe and open-system hosts.

  • Page 37: Bidirectional Data Transfer

    If you specify the delimiter option for FXotm, FCU will interpret all occurrences of the specified delimiter characters as delimiters, which can create a dataset with corrupt records or generate an error condition. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 38: Aix Shared Open Function

    AIX Shared Open Function To share Data Exchange volumes on multiple AIX operating systems: • For Data Exchange versions 01-xx-59 and earlier, when one AIX OS opens a Data Exchange volume, the other AIX OS cannot open the Data Exchange volume. This is because the AIX OS reserves the Data Exchange volume when it opens it.

  • Page 39: Aix Reserve Retry Function

    Description or Function FAL_RETRY Set the retry function by specifying the environment variable. Set the retry count for Data Exchange to send data during reserved status by spe- FAL_RETRY_COUNT cifying the environment variable. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 40: Specifying The Environment Variables For The Retry Function

    Environment Variable Description or Function Set the interval for Data Exchange to send data during reserved status by specifying FAL_RETRY_WAIT_TIME the environment variable. Set the system error codes that trigger a retry by specifying the environment vari- FAL_RETRY_TARGET able. Retry function Retry is executed when an AIX system error triggers retry.

  • Page 41: Output Retry Log Function

    No definition of environment variable – Output Retry Log Function Data Exchange outputs a retry log in the FAL_Error log file when retry is executed. Figure 21 on page 42 shows the retry log format. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 42: Errors

    Mon Nov 8 16:21:23 2004 : root : err=16 open Retry(1) at 12345 : 01-03-58/21 PID=1234 VSN:DSN data user name system error code function (open, close, read, write, seek, or flush) retry counts number of source code line version process ID target dataset Figure 21 Retry Log Errors...

  • Page 43: Data Exchange Version Support For The Get Detail Traces Function

    Output traces (FCU_Error occurred) tion and make copy of file. curred), page 46 Make core dump when Data Ex- Output core dump (8) Output Core Dump, page 46 change could not make traces. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 44: Check Sending File

    Table 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. Calculate disk space using the following formula: For copying traces 100 KB + (number of record sending file × 2 bytes) Table 18 Files to Get in case an Error Occurs Content Directory...

  • Page 45: Set Mode Of Making Copy Files

    45 shows the file name format when Data Exchange copies it. Table 22 Make Copy Files After Getting Information File Name Format Sending file name + . + traces getting time-date (yymmddHHMMSS) + process ID of Data Exchange + .cpy HP StorageWorks P9000 Data Exchange User Guide...

  • Page 46: Check Information For Sending Files

    (5) Check Information for Sending Files When environment variable (FCU_E363_TRACE_MODE) is not set to ON, you can compare information for files (i-node number, file size, file modified) that Data Exchange sends before and after. If Data Exchange found a difference in the 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 for files (i-node number, file size, file modified) while Data Exchange sends files.

  • Page 47: Platform Support For The Interval Function For Otm Transfer

    Set interval time using environment variable Set interval time (FCU_OTM_INTERVAL). Complete OtM transfer after Data Exchange waits for Completion interval an interval time specified by environment variable (FCU_OTM_INTERVAL). Display interval condition Display progress of interval time. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 48: Environment Variable For Interval Time

    Environment Variable for Interval Time You can specify an interval time after the OtM transfer completes by setting environment variable (FCU_OTM_INTERVAL). Table 26 on page 48 shows the relationship between the environment variable (FCU_OTM_INTERVAL) and interval time. Table 26 Relationship between FCU_OTM_INTERVAL and Interval Time FCU_OTM_INTERVAL Interval time No definition...

  • Page 49: Preparing For Data Exchange Operations

    Table 27 Data Exchange Version Support for Storage Systems Storage System Data Exchange (32-bit) Ver- Data Exchange (64-bit) Ver- sion sion P9500 Disk Array 01-06-67 and later 01-06-67 and later XP24000/XP20000 disk array 01-05-66 and later 01-05-66 and later HP StorageWorks P9000 Data Exchange User Guide...

  • Page 50: 64-Bit Version Fcu

    Storage System Data Exchange (32-bit) Ver- Data Exchange (64-bit) Ver- sion sion XP12000/XP10000 disk array 01-04-61 and later 01-04-61 and later XP1024/XP128 disk array 01-03-53 and later 01-03-59 and later XP512/XP48 disk array 01-02-46 and later None. • HP StorageWorks Remote Web Console and LUN Manager software. LUN Manager enables the user to configure FC ports and create custom-size LUs.

  • Page 51: Support And Os Conditions

    VSE parameters are as shown: 32756 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 HP StorageWorks P9000 Data Exchange User Guide...
  • Page 52 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. 32756 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...

  • Page 53: Compiler Requirements

    Digital UNIX Compiler Driver 3.11 • DEC C V5.6-075 on Digital UNIX V4.0 (Rev. 878) HP Tru64 01-XX-60 and later: • Digital UNIX Compiler Driver 3.11 • DEC C V5.9-005 on Digital UNIX V4.0 (Rev. 1229) HP StorageWorks P9000 Data Exchange User Guide...

  • Page 54: Maximum Data Size

    Maximum Data Size Table 31 on page 54 describes the maximum data sizes for Data Exchange version 01-02-48 or later. Table 31 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...

  • Page 55: Interoperability With Hdlm

    The FXoto volumes contain the intermediate datasets for file transfers between open-system platforms. Data Exchange does not support concurrent access to Data Exchange volumes by the mainframe and open-system hosts. To install and configure the Data Exchange volumes: HP StorageWorks P9000 Data Exchange User Guide...
  • Page 56 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.
  • Page 57 For Solaris, use the following partition sizes for the Data Exchange volumes, and use 2 (two) for the number of alternate cylinders (Table 33 on page 58): HP StorageWorks P9000 Data Exchange User Guide...

  • Page 58: Partition Sizes For Storage Systems

    Table 33 Partition Sizes for Storage Systems 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...

  • Page 59: Sharing Data Exchange Volumes Between Open-System Platforms

    Table 34 Sharing Data Exchange Volumes between Open-System Platforms HP-UX Sequent Win- True64 Solaris Linux Dynix dows SVR4 IBM AIX HP-UX Non-la- Sequent Dynix Linux Win- Label dows write op- tion Tru64 Label Solaris auto- write HP StorageWorks P9000 Data Exchange User Guide...

  • Page 60: Installing The Data Exchange Software

    HP-UX Sequent Win- True64 Solaris Linux Dynix dows SVR4 SVR4 CHK = sharing allowed only if volume has no label. Installing the Data Exchange Software The Data Exchange software must be installed on the open-system servers attached to the storage system.
  • Page 61 When the Data Exchange Code Converter is installed, the libuoc.* file is replaced with the Data Exchange Code Converter library (the extension varies according to OS). Before installing Data Exchange Code Converter, save libuoc.* with an alias. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 62: 64-Bit Data Exchange Software

    64-Bit Data Exchange Software To install the 64-bit Data Exchange software on a UNIX-based platform: Log in as root. Set the CD-ROM on which the 64-bit Data Exchange is stored to the drive. Mount it. Check to see if the following directories currently exist. If they do not, create them as follows: All Platforms: /usr, /usr/lib Solaris: /usr/lib/sparcv9 HP-UX: /usr/lib/pa20_64...

  • Page 63: Uninstalling The Data Exchange Software On Unix-Based Platforms

    When the 64-bit Data Exchange version 01-01-41/00 or later is used, or P9500 Disk Array, remove the following files: #rm /usr/bin/ppkeyset64 #rm /usr/bin/autoppkeyset64 When uninstalling 32-bit Data Exchange version 01-01-45 and later, or P9500 Disk Array, remove the following files: # rm /usr/lib/libfal.ver #rm /usr/bin/ppkeyset #rm /usr/bin/autoppkeyset HP StorageWorks P9000 Data Exchange User Guide...

  • Page 64: Uninstalling Data Exchange On Windows

    Uninstalling Data Exchange on Windows To uninstall the Data Exchange software on a Windows host, depending on your version of Data Exchange, do one of the following: • To uninstall Data Exchange version 01-01-25 or later, use the Windows Add/Remove Programs utility.

  • Page 65: Using The Autoppkeyset Command To Enter The License Key

    This command does not set the License key to libfalmt.*. Use the ppkeyset command to set it. • For Windows systems, open the command prompt (DOS window) and input the following commands and parameters: 32-bit: autoppkeyset 64-bit: autoppkeyset64 HP StorageWorks P9000 Data Exchange User Guide...

  • Page 66: Creating Fxoto Volumes Using The Fmt Utility

    NOTE: This command does not set the License key to falmt.dll. Use the 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...

  • Page 67: Fmt Utility Values

    (A) × 3 1397 - 1492 (A) × 24 501 - 532 (A) × 46 9077 - 11476 (A) × 4 1333 - 1396 (A) × 25 469 - 500 (A) × 47 HP StorageWorks P9000 Data Exchange User Guide...
  • Page 68 Block Length Write Avail- Block Length Write Avail- Block Length Write Avail- by Allocater = able Data per by Allocater = able Data Per by Allocater = able Data Per (A) (Bytes) Track (Bytes) (A) (Bytes) Track (Bytes) (A) (Bytes) Track (Bytes) 7477 - 9076 (A) ×...
  • Page 69 When the VSN, physical drive number, and cylinder size are correct, click Start. When the Format confirmation appears (see Figure 24 on page 71), click OK to perform the requested FMT format operation, or click Cancel to cancel your request. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 70: Fmt Utility For Windows Hosts

    When the format operation completes successfully, the Format complete message is displayed (see Figure 25 on page 71). If the specified volser has already been used, an error message is displayed to notify you (see Figure 26 on page 71). If the format operation could not be started due to an error condition, the Format check error message is displayed.

  • Page 71: Creating The Data Exchange Volume Definition Files

    72 describes the Data Exchange volume association parameters. Figure 28 on page 73 through Figure 35 on page 75 show the structure and contents of the Data Exchange volume definition file for each supported platform. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 72: Data Exchange Volume Association Parameters

    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 alphabetic (A-Z, @, #, and \) or numeric (0-9) characters.

  • Page 73: Data Exchange Volume Definition File For Solaris (Mto/Otm Shown)

    3380-KA Figure 30 Data Exchange Volume Definition File for IBM AIX (mto/otm Shown) NOTE: n = disk ID number (note that the first, second, and third drives are 0, 1, and 2). HP StorageWorks P9000 Data Exchange User Guide...

  • Page 74: Data Exchange Volume Definition File For Digital Tru64 Unix (Oto Shown)

    /dev/rrzX1Y1Z1 AAAAAA 3390-3A /dev/rrzX3Y3Z3 cccccc 3380-KB VOS3 /dev/rrzX4Y4Z4 dddddd 3380-KA Figure 31 Data Exchange 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;...

  • Page 75: Verifying Mainframe Dataset Requirements

    For FXotm, the block length of the target dataset must be preconfigured to match Block length (BL) 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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 76: Allocating Fxoto Intermediate Datasets

    Item Requirements Any length within the extent supported by the OS. If an illegal RL is detected, Data Exchange will return an error. NOTE: Data Exchange cannot process a variable-length dataset that includes a record with no data entity (RL = 4). Record length (RL) 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.

  • Page 77: Unix

    Windows Systems To allocate an intermediate FXoto dataset using the ALC utility: Log in to the system as administrator. Double-click the Allocate icon to start the ALC utility and open the Allocation panel. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 78 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 list of volsers. If ALC could not find any OPEN-x FMT volumes, ALC displays the Data Exchange format disk not found message.

  • Page 79: Alc Utility For Windows Systems

    Figure 36 ALC Utility for Windows Systems Figure 37 ALC Disk Not Found Message Figure 38 ALC Allocation Complete Message HP StorageWorks P9000 Data Exchange User Guide...

  • Page 80: Alc Error Message

    Figure 39 ALC Error Message Preparing for Data Exchange Operations...

  • Page 81: Using The Data Exchange Software

    FCU parameters and perform Data Exchange operations manually. The FCU GUI also displays the error information for Data Exchange operations. FCU Version and Copyright Screen To start the FCU GUI program for UNIX-based platforms: HP StorageWorks P9000 Data Exchange User Guide...

  • Page 82: Fcu Version And Copyright Screen (Unix)

    At the UNIX command line prompt, enter: fcu [-nc] [param] The -nc option (nc = no checking) tells FCU to execute all specified Data Exchange operations without requesting confirmation for FCU parameters or checking for existing FXmto target files. 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 Data Exchange operations.

  • Page 83: File Conversion Utility Screen

    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: HP StorageWorks P9000 Data Exchange User Guide...

  • Page 84: File Menu Commands

    • Direction. The Direction buttons allow you to select the desired direction for the Data Exchange operation: M to O = FXmto, O to M = FXotm. • Input File. The Input File field allows you to enter the name of the Data Exchange source file. For FXmto, enter the mainframe volser and dataset name (VSN:dataset).

  • Page 85: Help Menu Commands

    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 Figure 42 Help-Volume Display (HP-UX Shown) HP StorageWorks P9000 Data Exchange User Guide...

  • Page 86: Error Information Screen

    Dataset Information : VSN = xxxxxx Device Emulation Type = 3390-3B Dataset Name Can be processed by FCU. *SAMFILE01.FIX 4096 Cannot be processed by FCU. -DAMFILE.F 4096 Can be processed by FCU. *SAMFILE02.VAR 4000 Cannot be processed by FCU. -PAMFILE 5000 Cannot be processed by FCU.

  • Page 87: File Conversion Utility Window

    The FCU main panel opens when the 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 Data Exchange operations, and provides access to all FCU functions. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 88: Fcu Main Panel For Windows Systems

    Figure 47 FCU Main Panel for Windows Systems 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.

  • Page 89: Volume Information Dialog

    FCU can access the volume. A displayed next to a volume indicates that the volume definition is not correct and FCU cannot access the volume. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 90: Mainframe File Information Dialog

    Figure 48 Volume Information Panel NOTE: This example shows a Data Exchange volume definition file that defines only one Data Exchange volume. 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: •...

  • Page 91: 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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 92: Parameter Line Dialog

    Figure 50 Option Panel • Select the EBCDIC<-->ASCII option 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 the path if not in the current directory (for example, /directory/filename.tbl). •...

  • Page 93: Execute Dialogs

    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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 94: Error Information Dialog

    Figure 52 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” on page 150 for further information on errors. To cancel the operation in progress, click Cancel.

  • Page 95: Log Files

    FXoto volumes using the 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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 96: Fmt Utility Values

    NOTE: FCU version 01-01-42 or later is required for the FMT utility. The FMT utility defines the size of the OPEN-x volume in cylinders. The maximum number of cylinders allowed by FMT is shown in Table 39 on page 96. Table 39 FMT Utility Values Emulation 01-XX-47...
  • Page 97 The Data Exchange 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 Data Exchange FMT utility for Windows: HP StorageWorks P9000 Data Exchange User Guide...

  • Page 98: Fmt Utility For Windows Systems

    Log in to the system as administrator. Double-click the Format icon to open the Format panel (see Figure 57 on page 98). Figure 57 FMT Utility for Windows Systems On the Format panel, enter the 6-character volume serial number for the OPEN-x volume being formatted in the VOLSER field.

  • Page 99: Fmt Format Complete Message

    Close error! (n): Close process error on specified volume. When you are finished formatting OPEN-x volumes for use as FXoto volumes, click Close to close the Format panel and exit the FMT utility. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 100: Alc Utility For Windows

    IMPORTANT: 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.
  • Page 101 Write error! (n): Write process error on the FXoto volume. Close error! (n): Close process error on the FXoto volume. When you are finished allocating datasets on FXoto volumes, click Close to close the Allocation panel and exit the ALC utility. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 102: Alc Utility For Windows Systems

    Figure 62 ALC Utility for Windows Systems Figure 63 ALC Disk Not Found Message Figure 64 ALC Allocation Complete Message Using the Data Exchange Software...

  • Page 103: Alc Error Message

    Figure 65 ALC Error Message HP StorageWorks P9000 Data Exchange User Guide...
  • Page 104 Using the Data Exchange Software...

  • Page 105: Performing Data Exchange Operations

    (if specified), allows you to modify the FCU parameter definition file interactively, and also allows you to enter FCU parameters and perform Data Exchange operations manually. The FCU GUI also displays the error information for Data Exchange operations. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 106: Starting The Fcu Gui For Unix

    Starting the FCU GUI for UNIX To start the FCU GUI program for UNIX-based platforms: At the UNIX command line prompt, enter: fcu [-nc] [param] The -nc option (nc = no checking) tells FCU to execute all specified Data Exchange operations without requesting confirmation for FCU parameters or checking for existing FXmto target files.

  • Page 107: Performing File Transfer Operations (Unix)

    Verify that the FXoto target files do not already exist (or can be overwritten). Make sure that the desired Data Exchange volume definition file (FXoto only, or FXmto and FXotm) is available for use by FCU (datasetmount.dat in current directory). HP StorageWorks P9000 Data Exchange User Guide...
  • Page 108 Start FCU with the desired options (see “Starting the FCU GUI for UNIX” on page 106). 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. When the FCU main panel opens, make sure that the Volume File field displays the Data Exchange volume definition file (datasetmount.dat).

  • Page 109: Using The Listvol Function (Unix)

    “Performing File Transfer Operations (UNIX)” on page 107), enter the desired file name in the Parameter File field (with the complete path if you do not want to save the file in the current directory). HP StorageWorks P9000 Data Exchange User Guide...

  • Page 110: Creating Multiple Volume Definition Files (Unix)

    If you plan to perform Data Exchange operations while you are creating the FCU parameter definition file, make sure that the Volume File field displays the correct Data Exchange volume definition file (datasetmount.dat). If not (or if incorrect), FCU will not be able to perform Data Exchange operations, but you can still create a new FCU parameter definition file.

  • Page 111: Using Fcu From The Command Line (Unix)

    Using FCU from the Command Line (UNIX) FCU can be used without the GUI to perform Data Exchange operations. To use FCU without the GUI, you must start FCU using the -nw option. The FCU options are: HP StorageWorks P9000 Data Exchange User Guide...
  • Page 112 • The -nw option (nw = no Windows) tells FCU to execute the specified Data Exchange operations 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 Data Exchange op- erations.
  • Page 113 The ending status is included in $status for C-shell and $? for B-shell/K-shell. 0 = Successful completion. All Data Exchange operations completed successfully. 1 = Unsuccessful completion. One or more operations did not complete successfully. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 114: Using Fcu From The Unix Command Line

    Start FCU with checking. # fcunw FCU program version. File Conversion Utility Ver.01-01-40/00 First set of parameters. mto VSN:dataset file_name EA No LF Enter ok or cancel. ok/cancel ? ok Checking for target file. Now checking... Operation completed. Complete Next set of parameters. otm file_name VSN:dataset EA No No ok/cancel ? ok Enter ok or cancel.

  • Page 115: Performing File Transfer Operations Windows

    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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 116: Performing File Transfer Operations (Windows)

    Figure 72 FCU Version and Copyright Screen (Windows Systems) Performing File Transfer Operations (Windows) To perform Data Exchange file transfer operations using the FCU GUI for Windows systems: If you will be performing FXmto operations: Make sure that the source datasets are located on the desired Data Exchange volumes. 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.
  • Page 117 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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 118: Execute Panel Showing Normal End

    When FCU starts the operation, the Execute panel opens and displays the progress of the operation. To cancel the operation in progress, click Cancel. NOTE: The Execute panel will not appear when the mainframe OS is VSE. 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.

  • Page 119: Creating Fcu Parameter Definition Files (Windows)

    1/1 to indicate that line one of one is now being displayed. If the Data Exchange 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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 120: Creating Multiple Volume Definition Files (Windows)

    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.

  • Page 121: Using Fcu From The Command Line (Windows)

    999 information can be specified in the multiple volume definition file. Using FCU from the Command Line (Windows) To perform Data Exchange file transfer operations for Windows systems in a non-GUI environment: Log in as a user who has administrator privileges. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 122 Open the command prompt (DOS Windows) and input the parameters below: • fcunw [-cl] [param] ( [-v] ) • -cl: Specifies that all the log files for FCU will be cleared before stating FCU. • param: This parameter is used the 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.

  • Page 123: Performing Fal Operations

    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 HP StorageWorks P9000 Data Exchange User Guide...

  • Page 124: Fal Functions

    FAL Functions The FAL includes the following C functions (Visual C++ for Windows systems): • Opening a dataset: datasetOpen (see “Opening a Dataset” on page 124) • Reading one record from a dataset: datasetGet (see “Reading Data” on page 125) •...

  • Page 125: Reading Data

    Each variable-length block must start with the 2-byte BL field, and each variable-length record must start with the 2-byte RL field. The datasetGet function automatically extracts the data entities without the BL and RL fields. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 126: Writing Data

    Figure 77 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”...

  • Page 127: Closing A Dataset

    Errors in FAL functions are defined in dataset.h (see Chapter 7 on page 149). Errors in UNIX are defined by a standard error file (errno.h). Errors in Windows systems are defined by errno.h HP StorageWorks P9000 Data Exchange User Guide...

  • Page 128: Acquiring Dataset Attributes

    attached with Microsoft Visual C++. Table 45 on page 128 shows the datasetClose arguments and return values. Table 45 DatasetGetLastError Function Item Value Type Description Argument none Return value datasetLastError Long Error code Acquiring Dataset Attributes FAL provides several functions for acquiring the complete dataset attribute information for one or more datasets: datasetGetFileInformation, datasetFindFirstFile, datasetFindNextFile, and datasetFindClose.

  • Page 129: Acquiring Attribute Information For Multiple Datasets

    • 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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 130: Datasetfindnextfile Function

    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.

  • Page 131: Converting Do And Rf Information

    VS: VSAM organization text char [3] DA: direct access organization PO: Partial organization **: Other than above Normal end Return value Abnormal end Converting the RF Type Value datasetError = datasetGetRecfmString (recfm, text) HP StorageWorks P9000 Data Exchange User Guide...

  • Page 132: Using The Fal Functions

    The datasetGetRecfmString function converts the RF type to a 5-byte character string. The RF type is specified by recfm in DATASET_FIND_DATA. Table 51 on page 132 lists the datasetGetRecfmString arguments and return values. Table 51 DatasetGetRecfmString Function Item Value Type Description Record type value (1 byte) Sets value of recfm, a member of...
  • Page 133 # c89 —D_NO_MT -o Output file name Source file name /usr/lib/lib- fal.so libfal.so = file name of FAL object module • Linux # gcc —D_NO_MT -o Output file name Source file name /usr/lib/lib- fal.so.1 libfal.so.1 = file name of FAL object module HP StorageWorks P9000 Data Exchange User Guide...
  • Page 134 Using 64-bit 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.

  • Page 135: Example Of Reading Data From A Mainframe Dataset Using Fal

    Figure 79 Example of Reading Data from a Mainframe Dataset Using FAL HP StorageWorks P9000 Data Exchange User Guide...

  • Page 136: Multi-Thread Function

    Figure 80 Example of Acquiring MF Dataset Attributes Using FAL 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 •...

  • Page 137: Information Storage Area

    • 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. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 138: Open Dataset

    • When this function ends abnormally, it returns a 0. For further information, see Chapter on page 149. 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) Open Dataset Format: datasetError=dataset_Open(global,g_error,devname,dsname,voltype,mode)

  • Page 139: Read Data

    • 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 the EOF, “0” is returned. • For dataset_Get2(): HP StorageWorks P9000 Data Exchange User Guide...

  • Page 140: Write Data

    • 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, see the content of g_error for error code details. For further information, see Chapter 7 on page 149.

  • Page 141: Close Dataset

    • When this function ends normally, “1” is returned. • When this function ends abnormally, “0” is returned. When “0” is returned, see the content of derrno for error code detail. For further information, see Chapter 7 on page 149. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 142: Initialize Target Record Pointer

    Initialize Target Record Pointer • Format: datasetError=dataset_Rewind(global,g_error) Table 58 Arguments, Types, and Descriptions for Initialize Target Record Pointer Argument Type Description global void Global memory area g_error An error information stored area long datasetError Return value: long Abnormal end When this function is issued before dataset_Put, dataset_Put2, dataset_Get, and dataset_Get2, the pointer is returned to the top record.

  • Page 143: Get Multiple Dataset Attribute Information

    Return value: DATASET_HANDLE Abnormal end This function returns the top dataset attribute information specified by the raw device name to ffd. This function is used with dataset_FindFirstFile, dataset_FindNextFile, and data- set_FindClose. • Argument (1): HP StorageWorks P9000 Data Exchange User Guide...

  • Page 144: Arguments, Types, And Descriptions For Get Multiple Dataset Attribute Information (2)

    • global: Global memory area (specify a global memory area gotten by dataset_Alloc- Global). • g_error: Specify an address to store the FAL error code. • Pathname: Address of the partition name/physical drive name. • Voltype: Device emulation type (3390-3A/9A/LA, 3390-3B/9B/LB, 3380-3A, and 3380-3B).

  • Page 145: Compiling

    C language compiler based on ANSI. You need to include a header file in the program that will be using FAL. • For Windows systems: Launch Developer Studio. Create a new project. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 146: Error Information

    Copy the following FAL files to the project folder/directory: • dataset.h • falmt.dll • falmt.lib Select SETTING on the Developer Studio PROJECT menu. Select the LINK tab in the Project setting dialog. Add falmt.lib to the OBJECT/LIBRARY MODULE column. Build/Execute. NOTE: For AIX systems: #cc −qlanglvl=ansi −o output file name source file name /usr/lib/libfalmt.a...

  • Page 147: Example Of Using Fal To Read Data

    Figure 81 Example of Using FAL to Read Data HP StorageWorks P9000 Data Exchange User Guide...
  • Page 148 Performing FAL Operations...

  • Page 149: Troubleshooting

    Remove all space lines from the FCU parameter definition files. FCU versions FCU reports errors when 01-01-24 and earlier supported space lines when run without the GUI. FCU accessing an FCU parameter versions 01-01-36 and later do not support space lines. definition file. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 150: Error Codes And Messages

    Error Condition Recommended Action If you specified your own code conversion table, make sure that the file name and path are correct. FCU may also report code conversion table errors when FCU reports code conversion the Data Exchange volume definition file contains both mainframe and OPEN-x table errors.
  • Page 151 No VTOC found or the contents of the VTOC are invalid. rectly on the mainframe host. DATASET_ERROR_VOLUME_NOT_DEFINED Make sure that the specified volume has -20* been entered correctly in the Data Ex- The specified volume is not defined. change volume definition file. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 152 Error Code Error Message and Description Recommended Actions DATASET_ERROR_INVALID_ARGUMENT Make sure that the argument for the FAL An argument of the function is invalid. function is correct. DATASET_ERROR_NO_DATASET Make sure that the dataset has been cre- No dataset was found. ated correctly on the mainframe host.
  • Page 153 The next VSN is specified in the multiple volume definition file definition file. when the volume is not last on the VTOC. DATASET_ERROR_END_OF_FILE -50* None. End of File (EOF) was detected. DATASET_ERROR_END_OF_VTOC -51* None. End of VTOC was detected. HP StorageWorks P9000 Data Exchange User Guide...

  • Page 154: Fcu Error Codes For Unix

    FCU Error Codes for UNIX If the FCU for UNIX reports an error, use the Help-Error command to view the most recent error. Table on page 154 lists and describes the FCU error codes for UNIX and provides instructions for resolving each error condition.
  • Page 155 6 (No such device) is displayed. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 156 Error Error Message and Description Recommended Actions Code Overwrite ? (OK/Cancel) The specified open-system target file already -120 This message asks you to confirm exists. Click OK to overwrite the file, or click whether to overwrite the existing file. Cancel to specify a different target file. Output file: File name error Make sure that the correct output file name is -121...
  • Page 157 Output file: Open error Display the system error code using the Help- -151* A file open error occurred in the output Error command. See the OS user manual for UNIX file. information on system errors. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 158 Error Error Message and Description Recommended Actions Code Output file: Get file data error Collect information such as the error log for -152 A data acquisition error of the output troubleshooting. file occurred during an FXotm operation. Processing data: Length check error Make sure that the specified data length -153 A data length to be processed by FXotm...
  • Page 159 The RDW parameter is incorrect. correct. RDW error: CODE_CONV not supported Code conversion cannot be performed when -205 Code conversion is not specified as No RDW=Yes. Change the code conversion para- when RDW=Yes. meter to No. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 160 Error Error Message and Description Recommended Actions Code RDW error: PADDING not supported Padding cannot be processed when RDW=Yes. -206 Padding is not specified as No when Change the padding parameter to No. RDW=Yes. RDW error: DELIMITER not supported Delimiters cannot be processed when RDW=Yes. -207 Delimiter is not specified as No when Change the delimiter parameter to No.
  • Page 161 Dataset error: Invalid block length Display the attribute information using the Help- -342 The block length of the dataset is MF-File command. The block length must be invalid. nonzero and cannot be greater than 32 kB. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 162 Error Error Message and Description Recommended Actions Code Input file error: Invalid record length Display the attribute information using the Help- -343 The record length of the dataset is MF-File command. The record length must be invalid. nonzero and cannot be greater than 32 kB. Input file: Open error Display the system error code using the Help- -350*...

  • Page 163: 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 (for example, HP StorageWorks P9000 Data Exchange User Guide...

  • Page 164: Fcu Error Codes For Windows Systems

    Table 67 on page 164 lists and describes the FCU error codes for Windows fcudata.prm.log). 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++.
  • Page 165 Make sure that the record format is specified -134 The specified record format is not correctly. correct. Dataset: Block length error Make sure that the block length is specified -135 correctly. The specified block length is not correct. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 166 Error Error Message and Description Recommended Actions Code Dataset: Record length error Make sure that the record length is specified -136 The specified record length is not correctly. correct. Dataset: Dataset size error Make sure that the dataset size is specified -137 The specified dataset size is not correct.
  • Page 167 The code conversion table size is not the table was created correctly. correct. External table file: Read error -222 Check the system error. A read error was found when reading the code conversion table. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 168 Error Error Message and Description Recommended Actions Code External table file: Close error -223 The code conversion table could not be Check the system error. closed. Parameter: Direction, PAD, and DEL not matched For FXotm with the padding function, make sure -240 The combination of otm direction, that the delimiter option is specified as Yes (or...

  • Page 169: Calling Hp Technical Support

    RDW, and VSE record). • The Data Exchange volume definition file: contents • The FCU parameter definition file (if used): contents • The command line log (if possible). HP StorageWorks P9000 Data Exchange User Guide...
  • Page 170 • The 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: The FCU log file (for example, fcudata.prm.log) and Dr. Watson’s log file (for example, c:\WINNT\DRWTSN32.LOG).

  • Page 171: Support And Other Resources

    1 MB (megabyte) = 1,024 bytes • 1 GB (gigabyte) = 1,024 bytes • 1 TB (terabyte) = 1,024 bytes • 1 PB (petabyte) = 1,024 bytes • 1 block = 512 bytes HP StorageWorks P9000 Data Exchange User Guide...

  • Page 172: Hp Technical Support

    HP Technical Support For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: • Product model names and numbers • Technical support registration number (if applicable) • Product serial numbers • Error messages •...

  • Page 173: A Ebcdic-Ascii Code Conversion

    173 lists the EBCDIC-ASCII code conversions performed by the default code conversion table that is provided with FCU). Table 68 Default FCU EBCDIC-ASCII Conversions EBCDIC ASCII EBCDIC ASCII EBCDIC ASCII EBCDIC ASCII “ < > & HP StorageWorks P9000 Data Exchange User Guide...
  • Page 174 EBCDIC ASCII EBCDIC ASCII EBCDIC ASCII EBCDIC ASCII ‘ ‘ “ ‘ ‘ < EBCDIC-ASCII Code Conversion...
  • Page 175 EBCDIC ASCII EBCDIC ASCII EBCDIC ASCII EBCDIC ASCII > & HP StorageWorks P9000 Data Exchange User Guide...
  • Page 176 EBCDIC-ASCII Code Conversion...

  • Page 177: Glossary

    Fixed-length and de-blocking (mainframe record format). File Access Library. Fixed-length and blocking (mainframe record format). Fibre Channel. A network technology primarily used for storage networks. File Conversion Utility. Floppy disk. Data Exchange Formatter. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 178 FMT/ALC Formatter Allocater. Fast-wide differential. Data Exchange. FXmto Data Exchange-mainframe to open. FXotm Data Exchange-open to mainframe. FXoto Data Exchange-open to open. HDLM Hitachi Dynamic Link Manager. HMBR HP Multiplatform Backup/Restore. ICKDSFA Device Support Facilities (DSF) command used to perform media maintenance. LD, LDEV Logical device.
  • Page 179 Variable-length and blocking (mainframe record format). Virtual LVI/LUN. volser Volume serial number. VSAM Virtual Storage Access Method (not supported by Data Exchange). Virtual storage extended. Volume serial number. VTOC Volume table of contents. HP StorageWorks P9000 Data Exchange User Guide...
  • Page 180 Glossary...

  • Page 181: Index

    HP, 169, device recognition, Time_Out_Value, document related documentation, documentation volume types HP website, in general, providing feedback, mto, otm, 17, EBCDIC ASCII code conversion, websites help HP Subscriber's Choice for Business, obtaining, product manuals, HP StorageWorks P9000 Data Exchange User Guide...

Table of Contents