Page 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: T1620-96017 First edition: October 2010...
Database Data File Record Format ....................38 Code Conversion Using Fixed-Length Records ................. 39 Code Conversion Using Variable-Length Records ..............39 Converting Variable Length Mainframe Records to Variable Length UNIX/PC Records (mto) .......................... 39 P9000 Data Exchange Code Converter User Guide...
Page 4
Converting Variable-Length UNIX/PC Records to Variable-Length Mainframe Records (otm) .......................... 41 Converting Variable Length UNIX/PC Records to Fixed Length Mainframe Records (otm) ..42 Creating a Field Definition File ..................... 44 Field Definition Statement ....................44 End Statement ......................45 Comments ........................
Page 5
Subscription Service ........................96 HP Websites ..........................96 Documentation Feedback ......................96 A Edit Option File ................97 Edit Option File ........................97 B HOSTBIG5 ..................103 C EBCDIC-ASCII Code Conversion ............317 Glossary ..................321 P9000 Data Exchange Code Converter User Guide...
Page 6
Figures Mainframe to Open (mto) Conversion Diagram ............16 Open to Mainframe (otm) Conversion Diagram ............16 Alphanumeric Character Conversion Flow ..............20 Double-byte Character Conversion Flow ..............21 Non-conversion Process Flow ..................22 Output Suppression Function Flow ................23 Numeric Conversion Function Process Flow ..............
Page 7
Definition Statement for IBM Traditional Chinese to Big5 Code Conversion ..... 75 IBM Traditional Chinese to Big5 Code Conversion: Execution Result ......75 Code Conversion Execution Result ................75 Execution Result ...................... 76 P9000 Data Exchange Code Converter User Guide...
Page 8
Example of Code Conversion Table Contents ............103...
File Conversion Utility. The positioning of the Code Converter and an outline of its operation is shown 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...
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.
Page 17
Code Converter returns the data after conversion to Data Exchange, after ending conversion processing of all the fields for one record. 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...
Page 18
Overview of HP StorageWorks Data Exchange Software Code Converter...
The output field is shortened by The data in the input field is not Output suppression function the length of the non-conversion output. field that is not output. P9000 Data Exchange Code Converter User Guide...
Function Specification Remarks Code conversion is performed to the field data that consists only of numeric characters. Mainframe –> packed decimal, Numeric conversion function None zoned decimal Open system –> numeric character A numeric character code is changed. The functions shown in Table 1 are covered in detail in Alphanumeric Character Conversion...
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...
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.
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...
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.
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...
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.
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...
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.
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...
AIX or later 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...
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 Contents...
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 31. 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...
Move the inputting file for the license key to /usr/bin/: # mv -f ppkeyset /usr/bin 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. Log in to the open systems server (UNIX server) as root.
License Key for Windows Systems 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...
Page 36
Enter <license key> < Installed Directory>. 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” Enter quit.
• Confirm the record formats of the Mainframe file and the open systems file. 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...
• 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. •...
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...
• 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.
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...
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.
• 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...
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.
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...
• 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...
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...
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.
10. Parameters are specified in the order of the line number shown in these tables. Note these line numbers only count lines with effective inform- ation, and do not include lines that only contain comments. P9000 Data Exchange Code Converter User Guide...
• 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.
Page 51
TRAN_SHIFT_DBLCHAR character strings. Specifies double-byte and single-byte mixture. Allows 0-byte length records for datasets with variable length records in mto conversion. TRAN_NOREC Allows 0-byte length records in otm conversion. P9000 Data Exchange Code Converter User Guide...
Conversion Mode Parameter Parameter Value Description Do not fill in field TRAN_NOPAD 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 Parameter value Description Replace code for undefined Replace code for undefined...
Page 53
0 All-space fields outputs a 0. In otm conversion, a field TRAN_ALLSPACE_ZERO 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...
IBM Traditional Chinese IBM Traditional Chinese to Big5 KANJI:OPK1 EBCDIC and IBM Traditional EBCDIC and IBM Traditional Chinese mixture data to ASCII KANJI:OPK2 Chinese and Big5 All code conversion uses the above code conversion tables. P9000 Data Exchange Code Converter User Guide...
Figure 36 Converting IBM Traditional Chinese Code to BIG5 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: •...
Big5 characters, you will need to customize the Code Conversion table. Table 12 Big5 Code Conversion File Name Table Contents HOSTBIG5 Include conversion information of EBCDIC and IBM Traditional Chinese to Big5 P9000 Data Exchange Code Converter User Guide...
Page 58
Mainframe to Open System (MTO) Character Code Conversion...
ASCII and Big5 mixture data to EBCDIC and IBM ASCII and Big5 KANJI:OPK7 Traditional Chinese code conversion All code conversion uses specified code conversion tables. Big5 code is converted to IBM Traditional Chinese. P9000 Data Exchange Code Converter User Guide...
Figure 37 Converting from BIG5 Code to IBM 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'FF'.
For further information on customizing the Code Conversion table, see Chapter on page 69. Table 14 Standard Code Conversion Table File Name Table Contents BIG5HOST Include conversion information of ASCII and Big5 to IBM Traditional Chinese P9000 Data Exchange Code Converter User Guide...
Page 62
Open System to Mainframe (OTM) Character Code Conversion...
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...
• 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).
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...
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 Figure 47 Conversion When Leading sign” is Specified Figure 48 Conversion When Trailing sign”...
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...
• 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...
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 cus- tomization information (definition statements) specified by the user. The standard code conversion table cannot be modified.
Table 18 CODE Statement Options Type of conver- Option Description sion HOSTtoBIG5 T_HOST Customize table for IBM Traditional Chinese code. EBCDIC Customize table for EBCDIC code. BIG5toHOST BIG5 Customize table for Big5 code. P9000 Data Exchange Code Converter User Guide...
Type of conver- Option Description sion ASCII 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.
Execute customizing: Select the [Customize] button after selecting the conversion table file and the definition statement file. Output table information: Select the [Table Information] button; the generated date and history will be displayed. P9000 Data Exchange Code Converter User Guide...
Output table dump: Select the [Table Dump] button, and then open WordPad; a dump of the conversion table will be displayed. 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';...
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 HOSTBIG5.tbl P9000 Data Exchange Code Converter User Guide...
Message text will follow, describing the error condition. System action describes actions taken by the system after the message is output and User Action describes actions to be taken by the user once the P9000 Data Exchange Code Converter User Guide...
message is received. The following table contains the ccnv error messages and recommended actions to take. Table 20 Customizing the Code Conversion Table (ccnv): Error Messages Error Code Error Message and Description Action(s) Utility terminated. Termination code = termination_code. CCNV has terminated. The termination code is shown in decimal number.
Page 79
The code conversion table specified with CCNV10E-I User action: Check that the code -T” or -t” parameter of the utility does not conversion table specified exists, and then exist in the directory where the utility is re-execute. executed. P9000 Data Exchange Code Converter User Guide...
Page 80
Error Code Error Message and Description Action(s) System action: Proceeds to the next CODE statement is wrong value. Operation definition statement (Termination code 08). is executed with CODE=code. CCNV10F-I User action: Check that the value for CODE Wrong value is specified for CODE matches the type of conversion, and then statement.
Page 81
The I/O error of Definition statement file (Termination code 12). occurred. CCNV10D-I User action: Check the condition of the An error occurred during input/output of definition statement file or the system, and the Definition Statement file. then re-execute. P9000 Data Exchange Code Converter User Guide...
Page 82
Error Code Error Message and Description Action(s) Cannot find the code conversion table to System action: Terminates operation customize. (Termination code 12). The code conversion table specified with CCNV10E-I User action: Check that the code -T” or -t” parameter of the utility does not conversion table specified exists, and then exist in the directory where the utility is re-execute.
Page 83
User action: Check the preceding error A critical error was encountered during message to determine the cause of the operation. error, and then re-execute. Code conversion table information output System action: Terminates operation CCNV10W-I succeeded. (Termination code 0). P9000 Data Exchange Code Converter User Guide...
Error Code Error Message and Description Action(s) System action: Terminates operation Cannot make changes to the standard (Termination code 12). code conversion table. The standard code CCNV10Y-I User action: Create a new table when conversion table provided cannot be customizing the standard code conversion changed.
Select Error from the Help menu to view the system ”Edit log buffer : Allocation Cannot allocate memory for -616 error code, and then check error” UOC edit interface logging. the operating system document for error details. P9000 Data Exchange Code Converter User Guide...
Page 86
Error Code Error message Meaning Action Select Error from the Help Cannot allocate memory for menu to view the system ”Output log buffer : -617 UOC output interface/pipe error code, and then check Allocation error” output interface logging. the operating system document for error details.
Page 87
Check the Edit Option file. format error” Edit Option file is wrong. ”Edit option file : Number of the Edit Option -663 Check the Edit Option file. Information count error” file parameter is insufficient. P9000 Data Exchange Code Converter User Guide...
Page 88
Error Code Error message Meaning Action Field Definition file does not ”Field definition file : Non have an end” statement or Check the Field Definition -664 end mark or non fld area statements that start with file. error” fld”. Conversion mode specified ”Edit option file : Edit table in the Field Definition file is Check the Edit Option file...
Page 89
Conversion table I/O error menu to view the system ”Code conversion : occurred in double-byte or -683 error code, and then check Exchange table I/O error” single-byte code the operating system conversion. document for error details. P9000 Data Exchange Code Converter User Guide...
Page 90
Error Code Error message Meaning Action Type of conversion does not ”Code conversion : match the code conversion Check the code conversion -684 Unmatched exchange kind table in double-byte or table. and exchange table error” single-byte code conversion. Conversion table area is Use ccnv to display and Code conversion : Broken broken in double-byte or...
Page 91
Change the Field Definition ”Field definition file : Too Field Definition file is too -706 file so its size is 1,000 lines many data” large. including the comments. P9000 Data Exchange Code Converter User Guide...
Page 92
Error Code Error message Meaning Action Edit Option file is too large ”Edit option file : Too many -707 ( []” not found within the Check the Edit Option file. data” first 1,000 lines). ”Edit option file : 1 line Edit Option file has line(s) A line must be within 127 -708...
S/390 and/or open-system hosts. Collect the following information before you call for technical support: P9000 Data Exchange Code Converter User Guide...
Page 94
• Error codes: FCU error code, FAL error code, SYS error code. Use the FCU GUI to check recent error information (Help-Error command for UNIX, View-Error information command for NT). • FCU parameters: direction (mto or otm), input and output files, and FCU options (code conversion, padding, delimiter, empty file, RDW, VSE record).
HP StorageWorks XP24000/XP20000 Disk Array Owner Guide • HP StorageWorks XP24000/XP20000 Remote Web Console User Guide • HP StorageWorks P9000 Remote Web Console User Guide • Reference Manual Hitachi RapidXchange Code Converter for Solaris, HP-UX, AIX, Windows, Tru64 UNIX, Revision 1.1 •...
HP Technical Support For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: • Product model names and numbers • Technical support registration number (if applicable) • Product serial numbers • Error messages •...
(Chinese character). Conversion mode directions: The definition label [KANJI:OPK2] header of KANJI:OPK2. It changes into OPEN BIG5 code from an M/F HOSTtoBIG5 IBM kanji code. Code conversion table It exists in ./ directory. P9000 Data Exchange Code Converter User Guide...
Page 98
Message/Code Meaning HOSTBIG5 A conversion table called HOSTBIG5.tbl is used. The 1-byte character code in the field concerned is the EBCDIC code. A shift code changes into TRAN_EBCDIC|TRAN_START_SINGLE|TRAN_DBLSPACE 1-byte character from a head. A space character is changed into a 2-byte space code. The 1-byte character un-definition is replaced by X'20'.
Page 99
The 1-byte character un-definition is replaced by X'40'. The 2-byte character un-definition is replaced by 4040 X'4040'. At the time of 1-byte/2-byte mixture, if a conversion place domain remains, it will fill up with X'40'. P9000 Data Exchange Code Converter User Guide...
Page 100
Message/Code Meaning At the time only of 2-byte character, if a 4040 conversion place domain remains, it will fill up with X'4040'. The field concerned is the field of only a 2-byte TRAN_DOUBLE character (Chinese character). Conversion mode directions: The definition label [KANJI:OPK7] header of KANJI:OPK7.
Page 101
0 from a head is set to 0 as it is. TRAN_SIGN_PLUS_C A plus mark is C. TRAN_SIGN_MINUS_D A minus mark is D. The oar 0 of input data is changed into 0 as it TRAN_ALLSPACE_NORMAL End indicator. P9000 Data Exchange Code Converter User Guide...
This appendix provides an example of a Code Conversion table and a table of EBCDIC to ASCII conversion values. Figure 65 Example of Code Conversion Table Contents Table 24 EBCDIC –> ASCII Conversion Table EBCDIC ASCII Char. ASCII Char. ASCII Char. ASCII Char. ASCII Char. < ASCII Char. & P9000 Data Exchange Code Converter User Guide...
The following table lists the EBCDIC-ASCII code conversions performed by the default code conversion table that is provided with FCU (see Table 2 on page 30). Table 211 Default FCU EBCDIC-ASCII Conversions EBCDIC ASCII EBCDIC ASCII EBCDIC ASCII EBCDIC ASCII < > & P9000 Data Exchange Code Converter User Guide...
(such as, OPEN-3, OPEN-8, OPEN-9, OPEN-E), and OPEN-V, which has a variable size and is a CVS based volume. Open-to-Mainframe Open-to-Open Sequential-Access Method, System Administration Manager (HP-UX) TAR, tar Tape archive (file format) User's Own Coding Virtual storage extended. P9000 Data Exchange Code Converter User Guide...