HP StorageWorks P9000 Data Exchange Code Converter User Guide

Transcription

1 HP StorageWorks P9000 Data Exchange Code Converter User Guide Abstract This guide describes and provides instructions for installing and using the Data Exchange feature of the HP XP P9000 storage systems. Part Number: T First edition: October 2010

2 Legal and notice information Copyright 2008, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Microsoft, Windows, and Windows XP are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. Export Requirements You may not export or re-export this document or any copy or adaptation in violation of export laws or regulations. Without limiting the foregoing, this document may not be exported, re-exported, transferred or downloaded to or within (or to a national resident of) countries under U.S. economic embargo, including Cuba, Iran, North Korea, Sudan, and Syria. This list is subject to change. This document may not be exported, re-exported, transferred, or downloaded to persons or entities listed on the U.S. Department of Commerce Denied Persons List, Entity List of proliferation concern or on any U.S. Treasury Department Designated Nationals exclusion list, or to parties directly or indirectly involved in the development or production of nuclear, chemical, biological weapons, or in missile technology programs as specified in the U.S. Export Administration Regulations (15 CFR 744). Revision History Edition First Date October 2010 Description This document revision applies to HP storage system microcode version /00 or later.

3 Contents 1 Overview of HP StorageWorks Data Exchange Software Code Converter Overview of Code Converter Data Exchange Code Converter Process Code Converter Functions Alphanumeric Character Conversion Function Double-byte Character Conversion Function Non-conversion Function (Simple Transmission) Output Suppression Function Numeric Conversion Function Code Conversion Functions Undefined Character Code Processing (Single-byte) Undefined Character Code Processing (Double-byte) Shift Code Deletion Processing (Double-byte and Single-byte Combination) Shift Code Insertion Processing (Double-byte and Single-byte Combination) Shift Code Insertion Suppression Processing (Double-byte and Single-byte Combination) Short Output Field Processing System Requirements and Installation System Requirements Overview of the Data Exchange Code Converter Installation Installation Media for UNIX-based Systems Installation Media for Windows-based Systems Installing and Uninstalling for UNIX Systems Installing for UNIX Systems Uninstalling for UNIX Systems Upgrading or Downgrading Installing and Uninstalling for Windows Systems Installing for Windows Systems Uninstalling for Windows Systems Upgrading or Downgrading License Key Input License Key for UNIX Systems License Key for Windows Systems Using Data Exchange Code Converter Data Exchange Code Converter User Process Flow Database Data File Record Format Code Conversion Using Fixed-Length Records Code Conversion Using Variable-Length Records Converting Variable Length Mainframe Records to Variable Length UNIX/PC Records (mto) P9000 Data Exchange Code Converter User Guide 3

4 Converting Variable-Length UNIX/PC Records to Variable-Length Mainframe Records (otm) Converting Variable Length UNIX/PC Records to Fixed Length Mainframe Records (otm) Creating a Field Definition File Field Definition Statement End Statement Comments Conversion Modes For Open Systems Using Indication Parameter Of Conversion Mode When Field Is Value Using the Parameter Definition File to Associate Field Definition Files with Database Data Files Adding Parameters to the Parameter Definition File Edit Option File Conversion Mode Format Details Mainframe to Open System (MTO) Character Code Conversion Overview of Character Code Conversion Alphanumeric Field Conversion (CHAR:OPK4) Double-byte Character Field Conversion (KANJI:OPK1) Double-byte Character Field Conversion (KANJI:OPK2) Customizing the Code Conversion Table Open System to Mainframe (OTM) Character Code Conversion Overview Alphanumeric Field Conversion (CHAR:OPK9) Double-byte Character Field Conversion (KANJI:OPK6) Double-byte Character Field Conversion (KANJI:OPK7) Customizing the Code Conversion Table Numeric Conversion MTO (Mainframe To Open System) Numeric Value Conversion Overview Packed Decimal Conversion (NUM:OPA1) Sign Zero Suppression Decimal Point All-space Fields Zoned Decimal Conversion (NUM:OPA2) Sign Zero Suppression Decimal Point All-space Fields only Fields Customizing the Code Conversion Table Operation Overview Utility Features Definition Statement Syntax Definition Statement Syntax Rules Definition Statement Details Command Syntax for UNIX Systems Command Syntax for Windows Systems Examples of the ccnv Utility Customizing Character Conversion Converting Private Characters

5 Outputting Code Conversion Table Information Outputting to a File Troubleshooting Troubleshooting Error Codes ccnv Messages Data Exchange Code Converter Error Codes and Basic Troubleshooting Guidelines Calling HP Technical Support Support and Other Resources Related Documentation Conventions for Storage Capacity Values HP Technical Support Subscription Service HP Websites Documentation Feedback A Edit Option File Edit Option File B HOST C EBCDIC-ASCII Code Conversion Glossary P9000 Data Exchange Code Converter User Guide 5

6 Figures Mainframe to Open (mto) Conversion Diagram Open to Mainframe (otm) Conversion Diagram Alphanumeric Character Conversion Flow Double-byte Character Conversion Flow Non-conversion Process Flow Output Suppression Function Flow Numeric Conversion Function Process Flow Undefined Character Code Processing (Single-byte) Undefined Character Code Processing (Double-byte) Shift Code Deletion Processing Shift Code Insertion Process Shift Code Insertion Suppression Process Short Output Field Processing Installation Overview Data Exchange Code Converter User Process Flow Field Position and Field Length Example Field Position and Field Length Example Code Converter Record Formats and Conversion Modes Code Conversion Outline for Fixed-length Records Code Conversion in Variable Length Records ( end not specified for field length) Code Conversion in Variable Length Records (with end specified for field length) Overview of Code Conversion in Variable Length Records ( end not specified for field length) Overview of Code Conversion in Variable Length Records (with end specified for field length) Overview of Code Conversion in Variable Length Records ( end not specified for field length) Overview of Code Conversion in Variable Length Records (with end specified for field length) Field Definition Statement Last Field In The Record End Statement Including Comments in a Field Definition File

7 30 List of Field Attribute Options of the Traditional Chinese Code System List of Field Attribute Options for Numeric-based Coding Scheme Example of a Field Definition File Using the Parameter Definition File to Associate the Field Definition File Specifying the Conversion Mode in the Edit Option File Including Comments in the Edit Option File Converting Traditional Chinese Code to Code Converting from Code to Traditional Chinese Code Conversion When Leading sign is Specified Conversion When Trailing Sign is Specified Conversion When Insert Sign Before Effective Digits Is Specified Conversion When Unsigned is Specified Conversion When No zero suppression, Leading sign is Specified Conversion When Zero suppression, Trailing sign is Specified Conversion for Decimal Point = 3, Zero suppression and Trailing sign Specified Conversion for Decimal Point = 0, No zero suppression and Unsigned Specified Conversion of 0 in a 0-only Field to Spaces Conversion When Leading sign is Specified Conversion When Trailing sign is Specified Conversion When Insert sign before effective digits is Specified Conversion When Unsigned is Specified Conversion When No zero suppression, Leading sign is Specified Conversion When Zero suppression, Trailing sign is Specified Conversion for Decimal Point = 3, Zero suppression and Insert before effective digits Specified Conversion for Decimal Point = 0, No zero suppression and Unsigned Specified Conversion of 0 in a 0-only Field to Spaces Overview of the ccnv Utility Order of Definition Statements Using the ccnv Utility with Windows Systems Definition Statement for EBCDIC to ASCII and Traditional Chinese to Code Conversion EBCDIC to ASCII and Traditional Chinese to Code Conversion: Execution Result Definition Statement for Traditional Chinese to Code Conversion Traditional Chinese to Code Conversion: Execution Result Code Conversion Execution Result Execution Result P9000 Data Exchange Code Converter User Guide 7

8 65 Example of Code Conversion Table Contents

9 Tables Code Converter Functions Code Converter Utility Files for UNIX Systems File Extensions by UNIX-based Operating System Code Converter Utility Files for Windows Systems CD Device File Names Conversion Mode Parameters by Type of Conversion and Field Attribute List of Conversion Mode Parameters for Alphanumeric Character Conversion [CHAR:OPnn] (no. of parameters: 6) List of Conversion Mode Parameters for Double-Byte Code Conversion [KANJI:OPnn] (no. of parameters: 9) List of Conversion Mode Parameters for Double-Byte Code Conversion [KANJI:OPnn] (no. of parameters: 9) (continued) List of Conversion Mode Parameters for Numeric Conversion [NUM:OPnn] (no. of parameters: 7) Code Conversion Data Types and Field Types Code Conversion otm Code Conversion Standard Code Conversion Table Types of Numeric Value Conversion Definition Statements Syntax Options CODE Statement Options Range of Values Customizing the Code Conversion Table (ccnv): Error Messages Data Exchange Code Converter Error Codes MTO OTM EBCDIC > ASCII Conversion Table EBCDIC > ASCII Conversion Table (continued) ASCII > EBCDIC Conversion Table (continued) ASCII > EBCDIC Conversion Table (continued) > Conversion Table > Conversion Table (continued) P9000 Data Exchange Code Converter User Guide 9

10 30 > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued)

11 67 > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) P9000 Data Exchange Code Converter User Guide 11

12 104 > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued)

13 141 > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) P9000 Data Exchange Code Converter User Guide 13

14 178 > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) > Conversion Table (continued) Default FCU EBCDIC-ASCII Conversions

15 1 Overview of HP StorageWorks Data Exchange Software Code Converter This chapter provides an overview of how Data Exchange Code Converter operates and the interactions it has with other HP software. Overview of Code Converter, page 15 Data Exchange Code Converter Process, page 15 Unless otherwise specified, the term storage system in this guide refers to the following disk arrays: HP StorageWorks XP24000 Disk Array HP StorageWorks XP20000 Disk Array HP StorageWorks XP12000 Disk Array HP StorageWorks XP10000 Disk Array HP StorageWorks P9500 Disk Array 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. Overview of Code Converter The Data Exchange Code Converter, running on the HP storage system using HP File Exchange (FX), moves data from Mainframe systems to UNIX-based or PC-based servers. It enables the modification of data, including code conversion of various double-bytes characters. It incorporates functions such as standard double-byte code conversion. It is supported by the Data Exchange File Conversion Utility (FCU). The purpose of implementing the Data Exchange Code Converter is to build a Mainframe/Server data exchange system, without the user having to develop such a converter, as with 's double-byte code conversion. Data Exchange Code Converter Process The Data Exchange Code Converter is a UOC (user's own coding) function, which is called from the File Conversion Utility. The positioning of the Code Converter and an outline of its operation is shown in Figure 1 for the mto (Mainframe to open) conversion, and in Figure 2 for the otm (open to Mainframe) conversion. P9000 Data Exchange Code Converter User Guide 15

16 .. Figure 1 Mainframe to Open (mto) Conversion Diagram Figure 2 Open to Mainframe (otm) Conversion Diagram Note 1: JP1 and OJE (open job entry) are HP-provided package products. They are required for communication between the Mainframe and the open systems servers to handle data transfer. Note 2: A field represents a part of a record or can be the whole record, and is the basic processing unit of the Data Exchange Code Converter. The following procedure represents the basic flow of the Code Converter program: 1. The File Conversion Utility reads the data of a Mainframe FXmto volume. 16 Overview of HP StorageWorks Data Exchange Software Code Converter

17 2. If the use of the mto edit interface is declared with reference to the Parameter Definition file (which the user creates in advance), the File Conversion Utility will extract the data for one record, and will pass record data to Code Converter. The following steps represent the processing range of Code Converter: 1. Code Converter extracts data for one field, and then determines the type of conversion specified referring to the Field Definition file (which a user creates in advance). Convert double-byte or other characters referring to the Field Definition file and the Edit Option file (standard file provided). 2. Repeat the extraction processing and conversion processing of steps 3 and 4 for all the fields in the record. 3. Code Converter returns the data after conversion to Data Exchange, after ending conversion processing of all the fields for one record. 4. The File Conversion Utility outputs the data for the record to a server file (UNIX, etc.). (The process repeats iteratively.) P9000 Data Exchange Code Converter User Guide 17

18 18 Overview of HP StorageWorks Data Exchange Software Code Converter

19 2 Code Converter Functions This chapter describes Code Converter's available functions, their concept of operations, and when they are used by an operator. Alphanumeric Character Conversion Function, page 20 Double-byte Character Conversion Function, page 21 Non-conversion Function (Simple Transmission), page 22 Output Suppression Function, page 22 Numeric Conversion Function, page 23 Code Conversion Functions, page 24 The following table shows the Code Converter function specifications. Table 1 Code Converter Functions Function Specification Remarks Alphanumeric character conversion function Code conversion is performed only on single-byte field data characters. Mainframe > EBCDIC Open system > ASCII NOTE: Single-byte character codes are changed. None Double-byte character conversion function Code conversion is performed on field data characters that are only double-byte characters, or that are double-byte characters and single-byte characters, intermingled. Mainframe > Traditional Chinese Open system > NOTE: Double-byte character codes are changed. None Non-conversion function (= simple transmission) The data in the input field is not changed and is output. Input data is not limited to characters. Output suppression function The data in the input field is not output. The output field is shortened by the length of the non-conversion field that is not output. P9000 Data Exchange Code Converter User Guide 19

20 . Function Specification Remarks Numeric conversion function Code conversion is performed to the field data that consists only of numeric characters. Mainframe > packed decimal, zoned decimal Open system > numeric character A numeric character code is changed. None The functions shown in Table 1 are covered in detail in Alphanumeric Character Conversion Function on page 20 through Code Conversion Functions on page 24. The edit functions performed in connection with the alphanumeric and double-byte code conversions are covered in detail in Code Conversion Functions on page 24. Alphanumeric Character Conversion Function Code conversion is performed on a single-byte character data field. The following figure illustrates the process flow. The target coding system is as follows: Mainframe code set > EBCDIC Open system code set > ASCII Figure 3 Alphanumeric Character Conversion Flow Data is read from an input file per 1 record, the portion of the single-byte character field to convert is extracted, and the specified alphanumeric character conversion is performed. Conversion is performed for every field, and the result is edited per 1 record and written to an output file. 20 Code Converter Functions

21 . The position from which single-byte character fields in a record are extracted and the output field length are determined by referring to the value specified in the Field Definition file created by the user (see Creating a Field Definition File on page 44 for more information). Detail specification (the type of conversion table to use and so on) of the alphanumeric character conversion method is controlled by the default specification parameter in the standard Edit Option file provided (see Edit Option File on page 48 for more information). Double-byte Character Conversion Function Code conversion is performed on a data field that consists of only double-byte characters, or double-byte and single-byte characters that are intermingled. The following figure illustrates the process flow. The target coding system is as follows: Mainframe > Traditional Chinese: In this case, EBCDIC single-byte-characters are intermingled with double-byte characters Open system > : In this case, ASCII single-byte characters are intermingled with double-byte characters. Figure 4 Double-byte Character Conversion Flow Data is read from an input file per 1 record, the portion of the double-byte character field (single-byte character can be included in the field) to convert is extracted, and the double-byte character conversion is performed. The conversion process is the same as the alphanumeric character conversion explained in Alphanumeric Character Conversion Function on page 20. P9000 Data Exchange Code Converter User Guide 21

22 . Non-conversion Function (Simple Transmission) Data in the input field is output without any processing. Input data is not limited to character codes. The following figure illustrates the process flow. Figure 5 Non-conversion Process Flow Data is read from an input file per 1 record, the portion of the non-conversion field (unprocessed) is extracted, and simple transmission is performed. The position from which the non-conversion field in a record is extracted is determined by referring to the specified value in the Field Definition file created by the user. For details, see Creating a Field Definition File on page 44. Note 1: For non-conversion fields, make sure that the output field length is the same as the input field length. If the description of the output field length is omitted in the Field Definition file, the default will be the same length as the input field. Note 2: Because this processing method carries out only simple transmissions for non-conversion fields, the standard Edit Option file that is usually provided is not referred to here. Output Suppression Function Input field data is not output. The output record length is shortened and is not output. The following figure illustrates the process flow. 22 Code Converter Functions

23 . Figure 6 Output Suppression Function Flow Data is read from an input file per 1 record; the portion of the output suppression field is extracted, and after being read, the data is discarded. The output field length of an output suppression field is always 0. The position from which the output suppression field in a record is extracted is recognized by referring to the value specified in the Field Definition file created by the user. For details, see Creating a Field Definition File on page 44. NOTE: Do not specify an output field length for the output suppression function. Because an output is suppressed, the standard Edit Option file provided is not referred to here. Numeric Conversion Function Code conversion is performed only on the numeric character data fields. The following figure illustrates the process flow. The target coding system is as follows: Mainframe > packed decimal or zoned decimal Open system > Numeric character P9000 Data Exchange Code Converter User Guide 23

24 . Figure 7 Numeric Conversion Function Process Flow Data is read from an input file per 1 record, the portion of the numeric character field to convert is extracted, and the numeric character conversion is performed. Conversion is performed for every field, and the result is edited per 1 record and written to an output file. The position from which the numeric character field in a record is extracted and the output field length is determined by referring to the value specified in the Field Definition file created by the user. For details, see Creating a Field Definition File on page 44. Specification of the details (sign position, the number of decimal digits, and so on) of the numeric character conversion method is controlled by the default specification parameter in the standard Edit Option file provided. For details, see Edit Option File on page 48. Code Conversion Functions Undefined Character Code Processing (Single-byte) The following figure illustrates the single-byte undefined character code process. 24 Code Converter Functions

25 .. Figure 8 Undefined Character Code Processing (Single-byte) In this situation, an undefined character (a valid character that is not defined in the conversion table) in an alphanumeric character conversion is replaced by a replacement code for undefined characters (single-byte space). Undefined Character Code Processing (Double-byte) The following figure illustrates the undefined character code process. Figure 9 Undefined Character Code Processing (Double-byte) In this situation, an undefined character (a valid character that is not defined in the conversion table) in a double-byte character conversion is replaced by a replacement code for undefined characters (double-byte space). When single-byte characters are intermingled with double-byte characters, either a single-byte space or a double-byte space is used as the replacement code according to the position in the field. Shift Code Deletion Processing (Double-byte and Single-byte Combination) The following figure illustrates the shift code deletion process. P9000 Data Exchange Code Converter User Guide 25

26 .. Figure 10 Shift Code Deletion Processing When carrying out double-byte code conversion (double-byte and single-byte in the same field) from a coding system with a shift code to a coding system without a shift code, the shift codes are deleted. A shift code is a special code that shows the boundary of double-byte/single-byte characters. Data is left-aligned in the output field. Extra space in the output field is padded with the field padding code (double-byte or single-byte space). Shift Code Insertion Processing (Double-byte and Single-byte Combination) The following figure illustrates the shift code insertion process. Figure 11 Shift Code Insertion Process When carrying out double-byte code conversion (double-byte and single-byte in the same field) from a coding system without a shift code to a coding system with a shift code, a shift code can be inserted where necessary. A shift code is a special code that shows the boundary of double-byte/single-byte characters. If extra space still remains in the output field, it is filled up with a field padding code (double-byte/single-byte space). The end of input data is discarded when an output field area runs short as a result of inserting shift codes. Shift Code Insertion Suppression Processing (Double-byte and Single-byte Combination) The following figure illustrates the shift code insertion suppression process. 26 Code Converter Functions

27 .. Figure 12 Shift Code Insertion Suppression Process When double-byte code conversion (double-byte and single-byte in the same field) is carried out from a coding system without a shift code to a coding system with a shift code, the user can choose not to insert a shift code in the output field. A shift code is a special code that shows the boundary of double-byte/single-byte characters. NOTE: It is necessary to additionally specify TRAN_SHIFT_NO for code conversion mode in the Edit Option file. Normally, a shift code is inserted. Short Output Field Processing The following figure illustrates the short output field process. Figure 13 Short Output Field Processing NOTE: The end of input data is discarded when the output field length specified in the Field Definition file is too short, or when the output field becomes short as a result of inserting shift codes. P9000 Data Exchange Code Converter User Guide 27

28 28 Code Converter Functions

29 3 System Requirements and Installation This chapter describes the system and installation requirements for Code Converter. It also details how to install Code Converter on your system. System Requirements, page 29 Overview of the Data Exchange Code Converter Installation, page 30 Installation Media for UNIX-based Systems, page 30 Installation Media for Windows-based Systems, page 32 Installing and Uninstalling for UNIX Systems, page 33 Installing and Uninstalling for Windows Systems, page 34 License Key Input, page 35 System Requirements The system requirements for the Data Exchange Code Converter are: FAL/FCU CD for the applicable open-system platform(s). See the HP StorageWorks P9000 Data Exchange Software (32-bit) v67.06 Release Notes or HP StorageWorks P9000 Data Exchange Software (64-bit) v67.06 Release Notes for details regarding the FAL/FCU software. NOTE: FAL/FCU currently supports files larger than 2 GB. Multiplatform or all-open P9500 Disk Array storage systems: Data Exchange Code Converter mto: the P9500 Disk Array must be configured with -B and/or -A Data Exchange volumes. Data Exchange Code Converter otm: the P9500 Disk Array must be configured with -C and/or -A Data Exchange volumes. NOTE: A license key is required for Data Exchange Code Converter operation. If you execute mto before inputting the license key code, a 0 byte file will be created. If this occurs, execute mto again after you have input the license key code. The Remote Console HP StorageWorks P9000 Remote Web Console is used to enter the license key. For information on the Remote Console Remote Web Console, see the HP StorageWorks P9000 Remote Web Console User's Guide. See the release notes for supported operating systems. Data Exchange Code Converter works with Data Exchange software version or later. P9000 Data Exchange Code Converter User Guide 29

30 . Overview of the Data Exchange Code Converter Installation The following figure shows an overview of the Data Exchange Code Converter installation process. In order to use the Data Exchange Code Converter, you must first install the File Conversion Utility (FCU) and then install Code Converter. For details on installing the File Conversion Utility, see the HP StorageWorks P9000 Data Exchange User Guide. Figure 14 Installation Overview Installation Media for UNIX-based Systems The Data Exchange Code Converter Installation Utility files for UNIX systems are listed in the following table. Data Exchange Code Converter provides the following files in tar (tape archive) format. These files are contained in an accompanying compact disk. Table 2 Code Converter Utility Files for UNIX Systems File Name (Note 1) libuoc.* codetran.ini Contents UOC double-byte conversion function's object. Replace with a dummy object provided by FAL/FCU. ini file used by the double-byte code conversion routine Installation Location /usr/lib HOST.tbl HOST.tbl Traditional Chinese > conversion table > Traditional Chinese conversion table standard table for mto conversion standard table for otm conversion FAL/FCU boot directory EditOpFile Edit Option file 30 System Requirements and Installation

31 File Name (Note 2) ccnv ppkeyset Contents Executable file for the ccnv command used to customize code conversion tables for all files contained in this table. Executable file for inputting a license key code. Installation Location /usr/bin libuoc.ver (Note 5) Version information file /usr/lib (Note 3) uoc.c Standard source provided uocerror.h (Note 3) libuoc.mak (Note 3) Standard header file provided Makefile Files for creating user-defined UOC function that is used when not using Code Converter FAL/FCU boot directory (Note 3, 4) uoc.exp Module definition file Note 1: This file extension is used in place of.* depending on the platform as shown in Table 3. Note 2: Use ccnv listed here when customizing code conversion tables, such as when adding user-defined characters or characters not in the conversion table. Note 3: These files are not necessary when you use Code Converter. Note 4: uoc.exp is provided only in the AIX version. Note 5: Place libuoc.ver in /usr/lib/. Table 3 File Extensions by UNIX-based Operating System Type Manufacturer Operating System File Extension UNIX Server HP HP-UX or later AIX or later.sl.so.a SUN Solaris or later.so.1 REd Hat Linux AS2.1 or later.so.1 SuSE Linux ES9 or later.so.1 For further information on a supported operating system, contact your HP service representative. P9000 Data Exchange Code Converter User Guide 31

32 Installation Media for Windows-based Systems The Data Exchange Code Converter Installation Utility files for Windows systems are shown in the following table. Data Exchange Code Converter provides the following files in Windows installation format (InstallShield). These files are contained in an accompanying compact disk. Table 4 Code Converter Utility Files for Windows Systems File Name uoc.dll codetran.ini Contents UOC double-byte conversion function's object. Replace with a dummy object provided by FAL/FCU. ini file used by the double-byte code conversion routine Installation Location HOST.tbl HOST.tbl Traditional Chinese > conversion table > Traditional conversion table standard table for mto conversion standard table for otm conversion FAL/FCU boot folder (C:\FCU) EditOpFile Edit Option file (Note 1) ccnv.exe ppkeyset.exe Executable file for the ccnv command used to customize code conversion tables for all files contained in this table. Executable file for inputting a license key code. libuoc.ver (Note 3) Version information file. Stored in the Windows system directory. C:\WINNT (Note 2) uoc.c Standard source provided uocerror.h (Note 2) (Note 2) uoc.mak Standard header file provided Makefile File for creating user-defined UOC function that is used when not using Code Converter FAL/FCU folder \UOC (C:\FCU\UOC) (Note 2) uoc.dsp Project file (Note 2) uoc.def def file Note 1: Use ccnv files listed here when customizing code conversion tables, such as when adding user-defined characters or characters not in the conversion table. Note 2: These files are not necessary when you use Code Converter. These files are stored in the subdirectory Uoc that is created under the working directory of the installation directory. Note 3: This file is stored in a Windows system directory (for example, c:\winnt). 32 System Requirements and Installation

33 Installing and Uninstalling for UNIX Systems This section discusses installing, uninstalling, upgrading, and downgrading of the Data Exchange Code Converter program using UNIX systems. Installing for UNIX Systems 1. Log in to the open systems server (UNIX server) as root. 2. To mount Code Converter, insert CD into the drive. 3. Go to the working directory of the installation server, and then use the following tar command to copy all files in the installation media to the working directory. The Code Converter files listed in Table 2 on page 30 will be stored in the working directory of open systems. Enter the following, specifying the CD device file name as shown in the following table: #tar xvf xxxxxx/libuoc.tar Table 5 CD Device File Names OS HP-UX or later CD Installation Media Device File Name (Mount point)/program/convert/main/hp_ux/ Tru64 UNIX V5.1 or later CD (Mount point)/program/convert/main/digital/ AIX or later Solaris 2.6 or later CD CD (Mount point)/program/convert/main/aix/ (Mount point)/program/convert/main/solaris/ For further information regarding supported operating systems, contact your HP technical representative. NOTE: When you mount the CD, file names/directory names may not be displayed in all caps as shown in Table 5. You may also find a semicolon (;) plus one character, for example, ';l', at the end of the file name. In these cases, you have to place single quotes around the file name. Check on the file name using the ls command. 4. Remove the CD for Code Converter from the drive. 5. Save libuoc.* in /user/lib under another file name. Specify the file extension for your operating system according to Table 3 on page Move the shared library to /usr/lib/: # mv -f libuoc.* /usr/lib. Specify the file extension for your operating system according to Table 3 on page Move the version information file to /usr/lib/: # mv -f libuoc.ver /usr/lib IMPORTANT: The FCU cannot operate unless this is done. P9000 Data Exchange Code Converter User Guide 33

34 8. Move the inputting file for the license key to /usr/bin/: # mv -f ppkeyset /usr/bin 9. Log out, and then log in again. Code Converter is now installed. Uninstalling for UNIX Systems Before uninstalling the FAL/FCU products, you have to uninstall the Code Converter products. 1. Log in to the open systems server (UNIX server) as root. 2. Delete all files described in Table 2 on page 30 by using the rm command. 3. Delete the libuoc executable files and the version information files that have been installed on the /usr/lib directory. Specify the file extension for your operating system according to Table 3 on page 31. # cd /usr/lib # rm libouc.* libuoc. ver 4. Rename the file that was saved under another file name during the installation procedure described in Installing for UNIX Systems on page 33 (step 5) to libuoc.*. The FCU cannot operate unless this is done. Specify the file extension for your operating system according to Table 3 on page 31. Upgrading or Downgrading 1. Log in to the open systems server (UNIX server) as root. 2. Copy the files within the related files that are provided by Code Converter, if a user has changed, into a working directory. 3. Edit the option file (EditOpFile). 4. Install Code Converter from CD. 5. Restore the files from step Log out, and then log in again. Code Converter is now upgraded/downgraded. Installing and Uninstalling for Windows Systems This section discusses installing, uninstalling, upgrading, and downgrading of the Data Exchange Code Converter program using Windows systems. Installing for Windows Systems 1. Start the computer. 2. Log in as administrator. 3. Insert the CD for Code Converter into the drive. 4. Double-click setup.exe in Explorer to run the Code Converter setup file: setup.exe is in the following directory: (CD drive)\program\convert\main\win\disk1. 5. Follow the instructions displayed and enter /select user information, installation folder, program folder, and so on. Specify the same FCU directory as the destination directory. 34 System Requirements and Installation

35 6. When the InstallShield Wizard Complete window appears, click the [Finish] button to complete the Code Converter installation. Uninstalling for Windows Systems Before uninstalling the FAL/FCU products, you have to uninstall the Code Converter products. 1. Start the computer. 2. Log in as administrator. 3. Select [Start]-[Settings]-[Control Panel]. 4. Double-click [Add/Remove Programs]. 5. Select [Code Converter] from the list under [Removes the Change or Remove Programs], and click the [Change/Remove] button to start uninstallation. Follow the instructions displayed. 6. When the Maintenance Complete window appears, click the [Finish] button to complete the uninstallation process. Upgrading or Downgrading 1. Start the computer. 2. Log in as administrator. 3. Copy files within the related files that are provided by Code Converter, if a user has changed, in a working directory. 4. Edit the option file (EditOpFile). 5. Install Code Converter from CD. 6. Restore files from step 3above. Code Converter is now upgraded/downgraded. License Key Input A license key is required for using the Data Exchange Code Converter. License Key for UNIX Systems Input the license key using the ppkeyset command. When you use the AIX operating system, and you run the Code Converter program before inputting a license key, an error may occur during the ppkeyset command execution. Enter the slibclean command, and input the license key using the ppkeyset command. Input the following commands from the command line, according to operating system and platform: HP-UX: ppkeyset <License key> /usr/lib/libuoc.sl Solaris: ppkeyset <License key> /usr/lib/libuoc.so.1 AIX: ppkeyset <License key> /usr/lib/libuoc.a Tru64 UNIX: ppkeyset <License key> /usr/lib/libuoc.so License Key for Windows Systems 1. Double-click ppkeyset.exe in the install directory. The following message will appear in the MS- DOS window: Please enter <License key> [Installed Directory or File]... or <quit> for exit P9000 Data Exchange Code Converter User Guide 35

36 2. Enter <license key> < Installed Directory>. 3. Enter the following, if < Installed Directory> is a directory name with space : <license key> fal.dll falmt.dll The following message will appear: Please enter <License key> [Installed Directory or File]... or <quit> for exit 4. Enter quit. 36 System Requirements and Installation

37 . 4 Using Data Exchange Code Converter This chapter describes the operational sequence, how users perform operations, and use the functions of Code Converter. Data Exchange Code Converter User Process Flow, page 37 Database Data File Record Format, page 38 Data Exchange Code Converter User Process Flow The following figure illustrates the user process flow for the Data Exchange Code Converter. Figure 15 Data Exchange Code Converter User Process Flow The following steps are represented in Figure Confirm the record formats of the database data file to be converted. NOTE: When using Code Converter to perform double-byte-conversions, the database data file must be a sequential access method file (SAM) with fixed-length or variable-length records. Additionally, the field positions within the records must be fixed and consistent. Confirm the record formats of the Mainframe file and the open systems file. 2. Create a Field Definition file. Specify the field configuration details of the input/output record and the details of the conversion: P9000 Data Exchange Code Converter User Guide 37

38 .. The position of the fields to be converted, the type of conversion to be performed on those fields, how the result should be edited and output to the output record, and the length of the output field will be specified. A Field Definition file will be created for each record format (field configuration) found in the database data file to be converted. For each field in the input record, position, length, type of code conversion to be performed, and output length are specified in the prescribed format. 3. Use the Parameter Definition file to associate the Field Definition file with the database data file. Parameter Definition files are used to associate Field Definition files with the database data file to be converted. The Parameter Definition file is used by the File Conversion Utility to specify the database data files for mto conversion or otm conversion (a pair of files: Mainframe SAM file and an open systems UNIX/PC file). Describe the Parameter Definition file in text file form. 4. Execute/run the File Conversion Utility. Database Data File Record Format When using Code Converter to perform conversions such as double-byte conversions, the database data file must be a sequential access method file (SAM) with fixed-length or variable-length records. In addition, the field positions within the records must be fixed and consistent. You must confirm the record formats of the Mainframe file and the open systems file. Code Converter retrieves input data from a fixed position within each record. The field position within the record and the field length must be the same for all records, as shown in Figure 16 and Figure 17 (for example, SAM file output by the DB2 REORG utility). Figure 16 Field Position and Field Length Example 1 Figure 17 Field Position and Field Length Example 2 The following figure illustrates the record formats supported and conversion modes provided by the Data Exchange Code Converter. 38 Using Data Exchange Code Converter

39 .. Figure 18 Code Converter Record Formats and Conversion Modes Code Conversion Using Fixed-Length Records The following figure shows the mto (Mainframe-to-open systems) and otm (open systems-to-mainframe) code conversion when Mainframe records and open systems records both have fixed-length formats. Figure 19 Code Conversion Outline for Fixed-length Records Code Conversion Using Variable-Length Records The following actions must be performed when converting variable-length records: 1. Specify all delimiters. 2. Ensure that the total of field lengths specified in the Field Definition file equals the maximum record length of the Mainframe record length 4 (minus 4). 3. Ensure that the fields specified in the Field Definition file end within the Mainframe record. NOTE: When the last field has a variable length ( end is specified for input field length), numeric conversion cannot be performed on the field. Numeric codes (packed decimal/zoned decimal) are treated as being in fixed-length fields. Converting Variable Length Mainframe Records to Variable Length UNIX/PC Records (mto) Code conversion is performed on each field in the variable length Mainframe record, and the result is output as a variable length UNIX/PC record. Make sure to specify a delimiter in the end statement of the Field Definition file. P9000 Data Exchange Code Converter User Guide 39

40 Fixed field length: The following figure shows how mto code conversion is performed when the fields specified in the field definition statement have a fixed length (when end is not specified for the input field length). The record length of variable length Mainframe records have to be short as the maximum record length 4. Figure 20 Code Conversion in Variable Length Records ( end not specified for field length). Record 1: Code conversion is performed on Field 1 only. Fields 2 and 3 are not processed. Record 2: Code conversion is performed on Fields 1 through 3. Record 3: Code conversion is performed on Fields 1 and 2. Field 3 is not processed. Last field = variable length: The following figure shows how otm (open systems-to-mainframe) code conversion is performed when the last field specified in the field definition statement has a variable length (when end is specified for the input field length). The record length of variable length Mainframe records have to be short as the maximum record length 4. Figure 21 Code Conversion in Variable Length Records (with end specified for field length). You can specify end in the field definition statement only when the field is the last field of the record. When end is specified, code conversion for the last field starts at the beginning of the field and ends at the end of the record. In Figure 21, end is specified for Field 2, indicated by the grey areas. 40 Using Data Exchange Code Converter

41 Converting Variable-Length UNIX/PC Records to Variable-Length Mainframe Records (otm) After removing the delimiters in the variable length UNIX/PC records, code conversion is performed on each field, and the result is output to the Mainframe in variable length record format. The output record length after conversion must equal to (the maximum record length defined for the Mainframe record 4). Fixed field length: The following figure shows how otm code conversion is performed when the fields specified in the Field Definition file have a fixed length (when end is not specified for the input field length). Delimiters are not output to the Mainframe records. The record length of variable length Mainframe records have to be short as the maximum record length 4. Figure 22 Overview of Code Conversion in Variable Length Records ( end not specified for field length). Record 1: Code conversion is performed on Field 1 only. Fields 2 and 3 are not processed. Record 2: Code conversion is performed on Fields 1 through 3. Record 3: Code conversion is performed on Fields 1 and 2. Field 3 is not processed. Last field = variable length: The following figure shows how otm (open systems-to-mainframe) code conversion is performed when the last field specified in the Field Definition file has a variable length (when end is specified for the input field length). P9000 Data Exchange Code Converter User Guide 41

42 Figure 23 Overview of Code Conversion in Variable Length Records (with end specified for field length). You can specify end in the Field Definition file only when the field is the last field of the record. When end is specified, code conversion for the last field starts at the beginning of the field and ends at the end of the record. In Figure 23, end is specified for Field 2, indicated by the grey areas. Converting Variable Length UNIX/PC Records to Fixed Length Mainframe Records (otm) After removing the delimiters in the variable length UNIX/PC records, code conversion is performed on each field, and the result is output to the Mainframe in fixed length record format. Padding and delimiter must be specified in the end statement of the Field Definition file. After code conversion, the extra space in the Mainframe record is padded with the padding code specified. The extra space in each field is filled with the field padding code specified in the Edit Option file. The total length of the output fields defined in the field definition must be less than the fixed length of the Mainframe record. NOTE: Mainframe records with padding cannot be reconverted to UNIX/PC records using mto conversion. Fixed field length: The following figure shows how otm code conversion is performed when the fields specified in the field definition statement have a fixed length (when end is not specified for the input field length). Delimiters are not output to the Mainframe records. 42 Using Data Exchange Code Converter

43 Figure 24 Overview of Code Conversion in Variable Length Records ( end not specified for field length). Record 1: Code conversion is performed on Field 1 only. The rest of the Mainframe record is padded with a padding code. Fields 2 and 3 are not processed. Record 2: Code conversion is performed on Fields 1 through 3. Record 3: Code conversion is performed on Fields 1 and 2. The rest of the Mainframe record is padded with a padding code. Field 3 is not processed. Last field = variable length: The following figure shows how otm (open systems-to-mainframe) code conversion is performed when the last field specified in the Field Definition file has a variable length (when end is specified for the input field length). Figure 25 Overview of Code Conversion in Variable Length Records (with end specified for field length). Record 1: Code conversion is performed on Field 1 only. The rest of the Mainframe record is padded with a padding code. Field 2 is not processed. Record 2: Code conversion is performed on Fields 1 and 2. Record 3: Code conversion is performed on Fields 1 and 2. The rest of the Mainframe record is padded with a padding code. P9000 Data Exchange Code Converter User Guide 43

44 . Creating a Field Definition File Create a Field Definition file to specify the position of the fields to be converted, the type of conversion to be performed on those fields, how the result should be edited and output to the output record, and the length of the output field. A Field Definition file is created for each record format (field configuration) found in the database data file to be converted. For each field in the input record, specify its position, length, type of code conversion to be performed, and output length, in the format described below. Use editors such as vi to create the Field Definition file as a text file. The maximum file size is 1,000 lines, including comments. To use the file, store it in the current directory of the open systems (UNIX/PC server). The Field Definition file consists of field definition statements, an end statement, and comments. Field Definition Statement Specify a line for a field definition statement for each field in the input record in the order they appear, starting from the first field of the record (Figure 26). Figure 26 Field Definition Statement. fld: Keyword (reserved word) to indicate a field definition statement. relative_byte_position: Specify a relative byte position within the record to indicate where the field begins, using a decimal value starting from 0. input_field_length: Specify the byte length of the input (source) field using a decimal value. field_attribute: Specify the type of code conversion to be performed on the field as follows: Suppress output : SKIP No code conversion: NOP Alphanumeric character conversion: CHAR:OPnn ffor OPnn, see Table 7 on page 50) Double-byte character conversion: KANJI:OPnn (for OPnn, see Table 7 on page 50) Numeric conversion: NUM:OPnn (for OPnn, see Table 8 on page 50) output_field_length: Specify the byte length of the field's output (target) area, using a decimal value. This parameter can be omitted if the length is the same as the byte length of the input field. This parameter must be omitted for fields with no code conversion and fields that suppress output. If the field is the last field in the record and if the rest of the record is included in this last input field, the byte length of the input field can be simply specified with end as shown below (because you do not need to specify a specific value, this allows you to create a field definition statement/field Definition file for multiple data sets/records that is the same except for the length of the last field) (Figure 27): Figure 27 Last Field In The Record 44 Using Data Exchange Code Converter

45 end: the rest of the record starting from the beginning of this field is defined as an input field. The field length depends on the record format, as follows: Fixed length record: (byte length of input field) = (input record length) (relative byte position within the record) Variable length record: (byte length of input field) = (the length after code conversion) NOTE: You cannot perform numeric conversion on a variable length record field with end specified. Numeric conversion can only be performed on fixed length records. End Statement A line for an end statement is written at the end, after field definition statements are specified for all fields in the input record (Figure 28). Figure 28 End Statement. end: Keyword (reserved word) to indicate that all field definition statements have been written. Delimiter = delimiter_code: Specify a delimiter code as follows, if a delimiter is added to the end of the open systems records: To add CR = (0D) - Delimiter = CR To add LF = (0A) - Delimiter = LF To add CRLF = (0D0A) - Delimiter = CRLF (Only for Windows) Padding = padding_code: When converting variable length open systems records to fixed length Mainframe records, specify a padding code with a 2-digit hexadecimal character, to fill the space between the last field to convert and the end of the Mainframe record. NOTE: When adding a delimiter, the output record length increases/decreases accordingly. Take this into consideration when specifying the output length. When the input record contains binary data in addition to single-byte and/or double-byte characters, the binary data may include data that matches the delimiter specified. This may prevent correct recognition of delimiters to isolate records. Comments Comments can be included as necessary, within a field definition statement (at the end of the statement), or separately as a comment statement (Figure 29). When including a comment within a field definition statement, add the comment after the required items of the statement (5 parameters). When the byte length of the output field is omitted, # can be specified in its place to indicate that subsequent data is a comment. When # is specified at the beginning of a line, the entire line is becomes a comment. P9000 Data Exchange Code Converter User Guide 45

46 .. Blank lines are also treated as comments. Figure 29 Including Comments in a Field Definition File The following table shows the conversion mode parameters for each field attribute. Table 6 Conversion Mode Parameters by Type of Conversion and Field Attribute Type of conversion Field attribute Suppress output No code conversion Alphanumeric character conversion Double-byte character conversion Numeric conversion Suppress output SKIP NOP CHAR:OPnn KANJI:OPnn NUM:OPnn SKIP Conversion Modes For Open Systems Using The following figure contains the attribute options to use with the Traditional Chinese Code System. Figure 30 List of Field Attribute Options of the Traditional Chinese Code System Indication Parameter Of Conversion Mode When Field Is Value The following figure contains the list of field attribute options for a numeric-based coding scheme. 46 Using Data Exchange Code Converter

47 .. Figure 31 List of Field Attribute Options for Numeric-based Coding Scheme Figure 32 Example of a Field Definition File In the example in Figure 32, the input record length is = 1,236 bytes and the output record length is , = 2,456 plus 1 byte for the delimiter, thus 2,457 bytes. The first field contains the first 294 bytes of data. Single-byte alphanumeric character conversion is performed before output. Conversion is performed according to the conversion mode information for [CHAR:OP45] specified in the Edit Option file. The output field length is 588 bytes. The second field is the 16 bytes of data that follow the first field. No code conversion is performed, and data is output without any change. The output field length is 16 bytes. The third field is the 756 bytes of data that follow the second field. Single-byte alphanumeric character conversion is performed before output. Conversion is performed according to the conversion mode information for [CHAR:OP45] specified in the Edit Option file. The output field length is 1512 bytes. The fourth field is the 40 bytes of data that follow the third field. Only double-byte code conversion is performed before output. Conversion is performed according to the conversion mode information for [KANJI:OP41] specified in the Edit Option file. The output field length is 80 bytes. The fifth field is the 130 bytes of data that follow the fourth field. Single-byte alphanumeric character conversion is performed before output. Conversion is performed according to the conversion mode information for [CHAR:OP45] specified in the Edit Option file. The output field length is 260 bytes. Using the Parameter Definition File to Associate Field Definition Files with Database Data Files Parameter Definition files are used to associate Field Definition files with the database data file to be converted. The Parameter Definition file is used by the File Conversion Utility to specify the database P9000 Data Exchange Code Converter User Guide 47

48 . data files for mto conversion or otm conversion (a pair of Mainframe SAM file and open systems UNIX/PC file). Add a declaration to perform user editing operations (Code Converter operations), as well as Code Converter parameters such as the Field Definition file name, to the Parameter Definition file. The Parameter Definition file is also created by the user as a text file, following a prescribed format. Adding Parameters to the Parameter Definition File Add two parameters as follows: USER-EDIT: This is a reserved keyword declaring that user editing operations (Code Converter operations) are to be performed. At the end of the existing Parameter Definition file, enter one or more single-byte spaces, and then specify this keyword exactly as shown. Field Definition file name and Edit Option file name: These are the Code Converter parameters. Add./ to the name of the Field Definition file created as described in Code Conversion Using Variable-Length Records on page 39 and to the name of the Edit Option file (EditOpFile), join the two names with a, (comma), and then add this after USER-EDIT in ü following one or more single-byte spaces. Do not enter any spaces between the Field Definition file name and the Edit Option file name. The following figure shows the Parameter Definition file being used to associate the Field Definition file. Figure 33 Using the Parameter Definition File to Associate the Field Definition File Edit Option File The Edit Option file defines the details for all the code conversion modes supported by Code Converter. It is located in the current directory of the open systems environment (UNIX/PC server). Users may want to customize this file, such as using a special space code to replace the undefined character code. For clarification, a brief explanation of what is defined in the Edit Option file is presented in the following figure. 48 Using Data Exchange Code Converter

49 .. Figure 34 Specifying the Conversion Mode in the Edit Option File For each line in the Edit Option file, the part of the line after the necessary item (1 parameter), as well as any data following #, are treated as comments. Blank lines are also treated as comments. Figure 35 Including Comments in the Edit Option File Conversion Mode Format Details The Edit Option file includes conversion mode information such as that for alphanumeric character conversions and double-byte code conversions. Information appears in no particular order for every conversion mode (OPnn) used in the Field Definition file. Information for each conversion mode starts with a definition label header specified in the format [CHAR:OPnn], [KANJI:OPnn], or [NUM:OPnn], and continues until the next definition label header [xxxx:opnn] appears. The end of information is indicated with the end indicator (two characters [] ). Conversion mode parameters are specified one parameter per line, for the prescribed number of parameters as shown in Table 7 through Table 10. Parameters are specified in the order of the line number shown in these tables. Note these line numbers only count lines with effective information, and do not include lines that only contain comments. P9000 Data Exchange Code Converter User Guide 49

50 The last line contains the end indicator ( [] ), which indicates the end of the Edit Option file. Table 7 through Table 10 show the conversion mode parameters used by the Data Exchange Code Converter. Table 7 List of Conversion Mode Parameters for Alphanumeric Character Conversion [CHAR:OPnn] (no. of parameters: 6) Conversion Mode Parameter Parameter value Description Type of code conversion mto otm EBCto toebc Convert EBCDIC to ASCII. Convert ASCII to EBCDIC. Tables directory Alphanumeric string Specifies where the code conversion tables are located. Conversion table name Alphanumeric string Specifies the code conversion table to use for this field. Replace code for undefined characters Field padding code Code conversion option 2-digit hexadecimal character 2-digit hexadecimal character Code conversion option Specifies the code to replace undefined characters. Specifies the code to fill the extra space in the output field. Allows 0-byte length records for datasets with variable length records in mto conversion. Allows 0-byte length records in otm conversion. This line can be omitted when not specifying TRAN_NOREC. Table 8 List of Conversion Mode Parameters for Double-Byte Code Conversion [KANJI:OPnn] (no. of parameters: 9) Conversion Mode Parameter Parameter Value Description Type of code conversion mto otm HOSTto tohost Convert double-byte characters from Traditional Chinese characters to. Convert double-byte characters from to Traditional Chinese characters. 50 Using Data Exchange Code Converter

51 Tables directory Conversion Mode Parameter Parameter Value Alphanumeric string Description Specifies where the code conversion tables are located. Conversion table name Alphanumeric string Specifies the code conversion table to use for this field. Code conversion option TRAN_EBCDIC TRAN_SGLSPACE TRAN_DBLSPACE TRAN_START_SINGLE TRAN_START_DOUBLE TRAN_SHIFT_NO TRAN_SHIFT_SPACE Single-byte code in the record. Convert spaces to single-byte space code. Convert spaces to double-byte space code. This record starts with a single-byte character*. This record starts with a double-byte character*. Do not insert shift code. In otm conversion, add shift code to single-byte spaces within double-byte character strings. TRAN_SHIFT_DBLCHAR In otm conversion, add shift code to double-byte character strings. Specifies double-byte and single-byte mixture. TRAN_NOREC Allows 0-byte length records for datasets with variable length records in mto conversion. Allows 0-byte length records in otm conversion. P9000 Data Exchange Code Converter User Guide 51

52 Conversion Mode Parameter Parameter Value TRAN_NOPAD Description Do not fill in field padding code for deleted SO/SI codes. Table 9 List of Conversion Mode Parameters for Double-Byte Code Conversion [KANJI:OPnn] (no. of parameters: 9) (continued) Conversion Mode Parameter Replace code for undefined single-byte characters Replace code for undefined single-byte characters Specifies the code to replace undefined double-byte characters. Double-byte field padding code Single-byte/double-byte Parameter value Replace code for undefined single-byte characters 4-digit hexadecimal character 2-digit hexadecimal character 4-digit hexadecimal character TRAN_DOUBLE TRAN_MIX Description Replace code for undefined single-byte characters. Specifies the code to replace undefined double-byte characters. Specifies the code to fill the extra space in the output field when both single-byte and double-byte codes exist. Specifies the code to fill the extra space in the output field when only double-byte codes exist. This field contains double-byte codes only. This field contains both single and double-byte codes. Table 10 List of Conversion Mode Parameters for Numeric Conversion [NUM:OPnn] (no. of parameters: 7) Conversion Mode Parameter Parameter value Description Type of code conversion mto otm PACKtoCHAR ZONEtoCHAR CHARtoPACK CHARtoZONE Convert packed decimals to characters. Convert zoned decimals to characters. Convert characters to packed decimals. Convert characters to zoned decimals. Sign position TRAN_SIGN_F TRAN_SIGN_E Leading sign. Trailing sign. 52 Using Data Exchange Code Converter

53 Conversion Mode Parameter Decimal digits Zero suppression Type of plus sign* Type of minus sign* All-space fields Parameter value TRAN_SIGN_V TRAN_SIGN_NON 1-digit decimal character TRAN_NON_SUPPRESS TRAN_ZERO_SUPPRESS TRAN_SIGN_PLUS_C TRAN_SIGN_PLUS_A TRAN_SIGN_PLUS_E TRAN_SIGN_PLUS_F TRAN_SIGN_MINUS_D TRAN_SIGN_MINUS_B TRAN_ALLSPACE_NORMAL Description Insert sign before effective digits (only applicable to zero suppressed fields). Unsigned. Specifies the number of decimal digits between 0 and 9. Does not perform zero suppression. Performs zero suppression. Indicated with C (otm conversion only). Indicated with A (otm conversion only). Indicated with E (otm conversion only). Indicated with F (otm conversion only). Indicated with D (otm conversion only). Indicated with B (otm conversion only). In otm conversion, a field that only contains spaces generates an error. In mto conversion, a field that only contains 0 outputs a 0. TRAN_ALLSPACE_ZERO In otm conversion, a field that only contains spaces outputs a 0. * Parameter applicable to otm conversion. In mto conversion, signs are determined automatically. P9000 Data Exchange Code Converter User Guide 53

54 54 Using Data Exchange Code Converter

55 5 Mainframe to Open System (MTO) Character Code Conversion This chapter describes the mto character code conversion process. Overview of Character Code Conversion, page 55 Alphanumeric Field Conversion (CHAR:OPK4), page 56 Double-byte Character Field Conversion (KANJI:OPK1), page 56 Double-byte Character Field Conversion (KANJI:OPK2), page 57 Customizing the Code Conversion Table, page 57 Overview of Character Code Conversion The single-byte code conversion process changes code from EBCDIC to ASCII. The double-byte code conversion process is from Traditional Chinese to. Code Converter provides the following types of character code conversion for each field data type, as shown in the following table. Table 11 Code Conversion Data Types and Field Types EBCDIC Input field data type Traditional Chinese EBCDIC and Traditional Chinese Character code conversion EBCDIC to ASCII Traditional Chinese to EBCDIC and Traditional Chinese mixture data to ASCII and Field type and conversion mode CHAR:OPK4 KANJI:OPK1 KANJI:OPK2 All code conversion uses the above code conversion tables. P9000 Data Exchange Code Converter User Guide 55

56 . Figure 36 Converting Traditional Chinese Code to Code Alphanumeric Field Conversion (CHAR:OPK4) All specified field data conversion assume single-byte code. Code conversion follows the code conversion table shown in Appendix C on page 317. The following are exceptions: Undefined character: An undefined character (a valid character that is not defined in the conversion table) will be replaced by X''. Undefined characters can be replaced by a single-byte character if they are specified in the Edit Option file. Shift code: Shift code (X'0E': double-byte code start; X'0F': single-byte start) is treated the same way as an undefined character. Double-byte Character Field Conversion (KANJI:OPK1) All data conversion operations assume double-byte code. The following are exceptions: Undefined character: An undefined character (a valid character that is not defined in the conversion table) will be replaced by X''. Undefined characters can be replaced by a double-byte character if they are specified in the Edit Option file. Unjustified character: An unjustified character (first byte: X'41' through X'49', X'4C' through X'91', X'C2' through X'E2'; second byte: X'40' through X'FD') is treated the same way as an undefined character. The space character (X'40') is excluded. Shift code: The shift character (X'0E': double-byte code start; X'0F': single-byte code start) is treated as a double-byte code. When performing code conversion with double-byte data following a shift code and another shift code, the data is treated as an unjustified character code. 56 Mainframe to Open System (MTO) Character Code Conversion

57 Space character: An even-numbered character (X'40') is converted to a double-byte space character (X'A140'). A one-byte space character (X'40') is changed to an ASCII single-byte space character (X'20'). When specifying TRAN_SGLSPACE in the Edit Option file, all X'40' characters are changed to single-byte space characters (X'20'). Double-byte Character Field Conversion (KANJI:OPK2) Shift code is used for converting single-byte code double-byte code n. Single-byte code conversion is the same as alphanumeric field conversion (OPK4). Double-byte conversion is the same as double-byte character field conversion (OPK1). The following are exceptions. Shift code: The code set does not have a shift character. The shift code character is used for converting single-byte code and double-byte code. The shift code itself is not converted. When the shift code character is input, the output data length becomes shorter than the original input data length, and X'' is added for the shift code characters in the output data. When specifying field padding code in the Edit Option file, padding code can be replaced with specified singlebyte code. Assumption of shift code: When the first byte of a field is not a shift code, data conversion is in single-byte format. When the first character of the field is double-byte, double-byte conversion will be assumed by specifying TRAN_START_DOUBLE in the Edit Option file. Customizing the Code Conversion Table When converting from Traditional Chinese to, the Data Exchange Code Converter uses the standard code conversion table shown in the following table. When using user-defined characters or using anything other than standard characters, you will need to customize the Code Conversion table. Table 12 Code Conversion File Name HOST Table Contents Include conversion information of EBCDIC and Traditional Chinese to P9000 Data Exchange Code Converter User Guide 57

58 58 Mainframe to Open System (MTO) Character Code Conversion

59 6 Open System to Mainframe (OTM) Character Code Conversion Overview This chapter describes open system to Mainframe (otm) character code conversion. Overview, page 59 Alphanumeric Field Conversion (CHAR:OPK9), page 60 Double-byte Character Field Conversion (KANJI:OPK6), page 60 Double-byte Character Field Conversion (KANJI:OPK7), page 60 Customizing the Code Conversion Table, page 61 Single-byte code conversion involves changing code from ASCII to EBCDIC. Double-byte code conversion is from to Traditional Chinese. The Data Exchange Code Converter provides the following types of character code conversion for each field data type, as shown in the following table. Table 13 otm Code Conversion Input Field Data Type ASCII ASCII and ASCII to EBCDIC Character Code Conversion to Traditional Chinese ASCII and mixture data to EBCDIC and Traditional Chinese code conversion Field Type and Conversion Mode CHAR:OPK9 KANJI:OPK6 KANJI:OPK7 All code conversion uses specified code conversion tables. code is converted to Traditional Chinese. P9000 Data Exchange Code Converter User Guide 59

60 . Figure 37 Converting from Code to Traditional Chinese Code Alphanumeric Field Conversion (CHAR:OPK9) All specified field data conversion assumes single-byte code. Code conversion follows the code conversion table shown in Table 14 on page 61. Undefined characters are exceptions. An undefined character (a valid character is not defined in the conversion table) is a conversion is replaced by X''. An undefined character can replace single-byte code by specifying single-byte in the Edit Option file. Double-byte Character Field Conversion (KANJI:OPK6) All data conversion assumes double-byte code. The following are exceptions. Undefined character: Undefined characters (valid characters not defined in the conversion table) are replaced by X''. Undefined characters can replace double-byte code by specifying doublebyte in the Edit Option file. Unjustified character: An unjustified character (first byte: X'81' through X'FE', second byte:x'40' through X'7E', X'A1' through X'FE') is same as an undefined character. The space character (X'20') is excluded. Double-byte Character Field Conversion (KANJI:OPK7) Single-byte conversion is the same as alphanumeric field conversion (OPK9). Double-byte conversion is same as double-byte character field conversion (OPK6). The following is an exception. 60 Open System to Mainframe (OTM) Character Code Conversion

61 Shift code: Traditional Chinese code uses Shift code (X'0E': double-byte code start, X'0F': single-byte code start) to convert single-byte code and double-byte code. The converted code will be no longer than the previous unconverted code because shift code is padded. When converted code is longer than the allowable record length, an error is generated. When you specify TRAN_NOSHIFT in the Edit Option file, shift code is not padded. Customizing the Code Conversion Table When converting code from to Traditional Chinese, the Data Exchange Code Converter uses the standard code conversion table shown in the following table. When using user-defined characters or using anything other than the standard characters, you will need to customize the code conversion table. For further information on customizing the Code Conversion table, see Chapter 8 on page 69. Table 14 Standard Code Conversion Table HOST File Name Table Contents Include conversion information of ASCII and to Traditional Chinese P9000 Data Exchange Code Converter User Guide 61

62 62 Open System to Mainframe (OTM) Character Code Conversion

63 7 Numeric Conversion This chapter describes the considerations involved in performing numeric value conversions. MTO (Mainframe To Open System) Numeric Value Conversion Overview, page 63 Packed Decimal Conversion (NUM:OPA1), page 63 Zoned Decimal Conversion (NUM:OPA2), page 65 MTO (Mainframe To Open System) Numeric Value Conversion Overview Numeric values are stored in Mainframe systems as packed decimal or zoned decimal. The Data Exchange Code Converter provides the following types of numeric value conversion for each field data type, as shown in the following table. Table 15 Types of Numeric Value Conversion Input Field Data Type Packed decimal Zoned decimal Numeric Value Conversion Packed decimal data converted to character data Zoned decimal data converted to character data Field Type and Conversion Mode NUM:OPA1 NUM:OPA2 Numeric value conversion output is right-aligned. If an output field is not large enough for the converted value (the effective length of the converted field is longer than the output field length), an error is generated (error code: 757). Conversely, if there is extra space in the output field (the effective length of the converted value is shorter than the output field length), the extra space preceding the effective field data is padded with 0 or a blank space(s). Packed Decimal Conversion (NUM:OPA1) Packed decimal conversion divides 1 byte of numeric (packed decimal) data in the specified field into the top 4 bits and the bottom 4 bits, and then converts each group into 1 byte of character data, resulting in a total of 2 bytes of character data. If the 1 byte of packed decimal data is out of range (top/bottom 4 bits: X'A' to X'F'), an incorrect data error is generated (error code: 760). Packed decimal conversion is performed according to the options specified in the Edit Option file. Sign The bottom 4 bits in the last byte of packed decimal data contain the sign bits. Sign bits are recognized as follows: P9000 Data Exchange Code Converter User Guide 63

64 Sign bits indicating A, C, E, or F: plus Sign bits indicating B or D: minus Sign bits indicating a value other than the above (0 through 9): wrong data (error code: 760) The sign is inserted into the sign position specified in the Edit Option file. NOTE: When the sign position is specified as unsigned, no minus sign is inserted for negative values (indicated by sign bits B or D). Figure 38 Conversion When Leading sign is Specified Figure 39 Conversion When Trailing Sign is Specified Figure 40 Conversion When Insert Sign Before Effective Digits Is Specified Figure 41 Conversion When Unsigned is Specified Zero Suppression Zero suppression replaces leading zeroes preceding the effective digits in the output field with spaces. Zero suppression is performed according to the option specified in the Edit Option file. Zeroes are suppressed in relation to sign position, as shown in the following examples. Figure 42 Conversion When No zero suppression, Leading sign is Specified Figure 43 Conversion When Zero suppression, Trailing sign is Specified 64 Numeric Conversion

65 ... Decimal Point A decimal point is inserted according to the number of decimal places specified in the Edit Option file. When 0 is specified, no decimal point is inserted. Figure 44 Conversion for Decimal Point = 3, Zero suppression and Trailing sign Specified Figure 45 Conversion for Decimal Point = 0, No zero suppression and Unsigned Specified All-space Fields All-space fields that contain only spaces (all data is X'40') unconditionally generate a data error (error code: 760). 0-only fields: Fields that contain only 0 are converted according to the All-space field option in the Edit Option file. When the option to convert 0 in 0-only fields to 0 (TRAN_ALLSPACE_NORMAL) is specified, 0 is converted to 0 as in normal numeric value conversions. When the option to convert 0 in 0-only fields to spaces (TRAN_ALLSPACE_ZERO) is specified, all 0's are converted to spaces (X'20'), as shown in the following figure. The sign position, zero suppression, and the number of decimal places specified in the Edit Option file, as well as the sign of the input data, are ignored. Figure 46 Conversion of 0 in a 0-only Field to Spaces Zoned Decimal Conversion (NUM:OPA2) Zoned decimal conversion takes 1 byte of numeric (zoned decimal) data in the specified field and converts the bottom 4 bits into 1 byte of character data. If the 1 byte of zoned decimal data is out of range (bottom 4 bits: X'A to X'F), a data error is generated (error code: 760). Zoned decimal conversion is performed according to the options specified in the Edit Option file. Sign The bottom 4 bits in the last byte of zoned decimal data contain the sign bits. Sign bits are recognized as follows: Sign bits indicating A, C, E, or F: plus Sign bits indicating B or D: minus Sign bits indicating a value other than above (0 through 9): wrong data (error code: 760) P9000 Data Exchange Code Converter User Guide 65

66 The sign is inserted into the sign position as specified in the Edit Option file. When the sign position is specified as unsigned, no minus sign is inserted for negative values (indicated by sign bits B or D). Figure 47 Conversion When Leading sign is Specified Figure 48 Conversion When Trailing sign is Specified Figure 49 Conversion When Insert sign before effective digits is Specified Figure 50 Conversion When Unsigned is Specified Zero Suppression Zero suppression replaces leading zeroes preceding the effective digits in the output field to spaces. Zero suppression is performed according to the option specified in the Edit Option file. Zeroes are suppressed in relation to sign position, as shown in the examples that follow. Figure 51 Conversion When No zero suppression, Leading sign is Specified Figure 52 Conversion When Zero suppression, Trailing sign is Specified Decimal Point A decimal point is inserted according to the number of decimal places specified in the Edit Option file. When 0 is specified, there will be no decimal point, and no decimal point is inserted. 66 Numeric Conversion

67 ... Figure 53 Conversion for Decimal Point = 3, Zero suppression and Insert before effective digits Specified Figure 54 Conversion for Decimal Point = 0, No zero suppression and Unsigned Specified All-space Fields 0-only Fields Fields that only contain spaces (all data is X'40') unconditionally generate a data error (error code: 760). Fields that contain only 0 are converted according to the All-space field option in the Edit Option file. When the option to convert 0 in 0-only fields to 0 (TRAN_ALLSPACE_NORMAL) is specified, 0 is converted to 0 as in normal numeric value conversions. When the option to convert 0 in 0-only fields to spaces (TRAN_ALLSPACE_ZERO) is specified, all 0's are converted to spaces (X'20'), as shown in the following figure. The sign position, zero suppression, and the number of decimal digits specified in the Edit Option file, as well as the sign of the input data, is ignored. Figure 55 Conversion of 0 in a 0-only Field to Spaces P9000 Data Exchange Code Converter User Guide 67

68 68 Numeric Conversion

69 . 8 Customizing the Code Conversion Table This chapter describes the procedures for customizing the code conversion table for use with your specific conversion requirements. Operation Overview, page 69 Utility Features, page 70 Definition Statement Syntax, page 70 Definition Statement Details, page 71 Command Syntax for UNIX Systems, page 72 Command Syntax for Windows Systems, page 73 Examples of the ccnv Utility, page 74 Operation Overview The following figure illustrates the code conversion table customization process. Figure 56 Overview of the ccnv Utility P9000 Data Exchange Code Converter User Guide 69

70 Utility Features The ccnv utility provides features necessary to customize code conversion tables. These are described below: Table customization: Customizes the specified code conversion table according to the user's customization information (definition statements) specified by the user. The standard code conversion table cannot be modified. This feature is also used for conversion of user-defined characters. Table information output: Outputs information on the code conversion table such as the type of conversion, creation date, and date last modified. Table dump output: Outputs code conversion table dump results to a file. The contents of this dump output only concerns the codes, and does not include internal information such as header information contained in the code conversion table. The resulting file name is the code conversion table name with.dmp appended to the end as the file extension. Standard table generation: Re-generates the standard code conversion table provided. Use this feature when the standard code conversion table is modified or deleted unintentionally or by hard disk failures. Definition Statement Syntax This section describes the syntax of the definition statement used by the ccnv utility command to customize the code conversion table. Definition Statement Syntax Rules Use single-byte alphanumeric characters to specify the definition statement (except comments). Types of definition statements (Table 16): Table 16 Definition Statements Definition statement NAME statement TYPE statement CODE statement Code customization statement Comments Description Specifies name of the code conversion table to customize. Specifies the type of conversion to customize. Specifies the character code to customize. Specifies how the character code is converted. Enter comments. Start position of the definition statement: Although there are no rules regarding the start position, it is recommended to keep the statement in one line, within 120 columns. Order of definition statements: The definition statements must be specified in the order shown in the following figure: 70 Customizing the Code Conversion Table

71 . Figure 57 Order of Definition Statements Definition Statement Details NAME statement Syntax: NAME=code_conversion_table_name_to_generate Parameters: Specify the code conversion table name to generate in alphanumeric characters. The maximum length is 255 characters, and the name must begin with an alphabetic character. When modifying an existing code conversion table and not creating a new one, specify '*'. TYPE statement Syntax: TYPE=type_of_conversion Parameters: Specify the type of code conversion to customize. The following table shows the options that can be specified. Table 17 Syntax Options Option HOSTto tohost Description Customize the code conversion table to convert Traditional Chinese to. Customize the code conversion table to convert to Traditional Chinese. CODE statement Syntax: CODE=type_of_code Parameters: Specify the type of code to customize. When none is specified, it is assumed from the type of conversion in the code conversion table passed by the -t option of the ccnv utility command. The following table shows the options that can be specified in the CODE statement. Table 18 CODE Statement Options Type of conversion HOSTto tohost Option T_HOST EBCDIC Description Customize table for Traditional Chinese code. Customize table for EBCDIC code. Customize table for code. P9000 Data Exchange Code Converter User Guide 71

72 Type of conversion Option ASCII Description Customize table for ASCII code. Code customization statement Syntax: Code_to_convert:Converted_code When specifying more than one code, separate them with a comma (,). There are no rules regarding the columns to define the parameters, but each pair must be separated with a comma (,) or a line break. Parameters: Specify code_to_convert from the code conversion table with hexadecimal. Specify the desired code after conversion in converted_code, also using hexadecimal. The following table shows the range of values that can be specified. Note that specifying any value outside this range generates an error. Table 19 Range of Values Code Valid values EBCDIC 0x00 0x ASCII 0x00 0x T_HOST First byte: 0x41 0x49, 0x4C 0x91, 0xC2 0xE2 Second byte: 0x41 0x7F, 0x81 0xFD0x4180 First byte: 0x81 0xFE Second byte: 0x40 0x7E, 0xA1 0xFE Remarks Shift code results in an error. Value outside the valid range results in an error. Value outside the valid range results in an error. Comments: Enter comments. Syntax: #Comments Parameters: Anything entered between '#' and line break is treated as a comment. Command Syntax for UNIX Systems Use the ccnv command to customize code conversion tables. The syntax rules for the ccnv command are described below. ccnv command: Syntax: ccnv [option] definition_statement_file_name ( indicates a single-byte space) Parameters: Specify the name of the definition statement file that defines the customization of the code conversion table. The file name must include the file extension.txt. When there is no file extension, an error message indicating that definition statements cannot be found is displayed. Command options: D -d dir: Specify the output directory for the code conversion table in dir. This option can be used with other options for file output. 72 Customizing the Code Conversion Table

73 L -l: Definition statements specified are additionally output to the result list. When this option is specified, lines with errors are output directly above the error message, and making corrections becomes easier. P -p: The generated code conversion table is dumped as a character based file. The table is output to the current directory from which the command is executed, with a file name that includes the Code Conversion name and the file extension changed to.dmp. Use this file to review the customized table. T -t: Specifies the code conversion table name to customize. This option can be omitted when executing customization. It defaults to the standard table for the type of conversion specified in the definition statement. -I -I: Outputs code conversion table information such as the creation date and date last modified to standard output. Command Syntax for Windows Systems Use the ccnv.exe utility to customize code conversion tables. This section describes the use of this utility (Figure 58). Figure 58 Using the ccnv Utility with Windows Systems. 1. Execute customizing: Select the [Customize] button after selecting the conversion table file and the definition statement file. 2. Output table information: Select the [Table Information] button; the generated date and history will be displayed. P9000 Data Exchange Code Converter User Guide 73

74 .. 3. Output table dump: Select the [Table Dump] button, and then open WordPad; a dump of the conversion table will be displayed. 4. Create a Standard Table: Select the [Create Standard Table] button, and then select Create standard conversion table. Examples of the ccnv Utility Customizing Character Conversion In the following example, EBCDIC code X'00' is converted to ASCII code X'31'; Traditional Chinese code X'5965' and X'5B99' are converted to code X'F8A6' and X'A4AA' respectively. Figure 59 Definition Statement for EBCDIC to ASCII and Traditional Chinese to Code Conversion Figure 60 EBCDIC to ASCII and Traditional Chinese to Code Conversion: Execution Result Converting Private Characters User-defined characters are converted in Traditional Chinese to code conversion. User-defined characters X'47B0', X'47B1', X'47B2' created on the Mainframe computer are respectively converted to user-defined characters X'FA40', X'FA41', X'FA42' created on the workstation. 74 Customizing the Code Conversion Table

75 ... Figure 61 Definition Statement for Traditional Chinese to Code Conversion Figure 62 Traditional Chinese to Code Conversion: Execution Result Outputting Code Conversion Table Information Code conversion table information is output to standard output. Enter the following command at the command line: ccnv r -p r -t r HOST.tbl Figure 63 Code Conversion Execution Result Outputting to a File Code conversion table dump information is output to a file. Enter the following command at the command line: ccnv r -p r -t r HOST.tbl P9000 Data Exchange Code Converter User Guide 75

76 . Figure 64 Execution Result 76 Customizing the Code Conversion Table