Support for Unicode by the software products

*5 The UTF codes (Unicode Transformation Format) UTF-8, UTF-16 (2

*5 Byte) and UTF-E that follows UTF-EBCDIC from IBM are supported in

*5 BS2000/OSD.

2.17.2 Support for Unicode by the software products

*5 The software environment required for supporting the Unicode

*5 functionality is provided in BS2000/OSD-BC V6.0 and V7.0.

*5 The support encompasses the following functional areas:

*5 - Programming (COBOL2000, ESQL-COBOL, IFG/FHS, AID).

*5 - Data storage (SESAM/SQL, ORACLE).

*5 - Data processing (EDT, SORT, PERCON).

*5 - Data I/O to terminals, printers and file transfer

*5 (VTSU, MT9750,WebTransactions, FHS, RSO, Spool, openFT).

*5 Unicode-specific extensions have been implemented in the above

*5 products.

*5 The different variants of the NATIONAL data type are supported

*5 for the programming environment in COBOL2000 V1.4 and ESQL-COBOL

*5 V3.0 and its use is permitted as a host variable in SQL state-

*5 ments. CRTE V2.6 allows the procedural use of this data.

*5 IFG V8.3 and FHS V8.3 allows separate format fields to be identi-

*5 fied for Unicode.

*5 With appropriate support by COBOL, AID V3.2 offers symbolic de-

*5 bugging of data type UTF-16.

*5 In the database systems SESAM/SQL V5.0 and Oracle 10g, Unicode

*5 characters can be stored and processed with SQL resources using

*5 the new data types NCHAR and NVARCHAR.

*5 XHCS-SYS provides SORT V7.9 with the sorting tables required for

*5 processing data. PERCON V2.9 is correspondingly extended for

*5 standardizing diacritical characters and converting files. Files

*5 with Unicode code sets can be processed as of EDT V17.0.

*5 The EBCDIC variant of UTF-8 (UTF-E) is supported by the terminal

*5 emulation MT9750 V7.0 and VTSU-B V13.2 for input/output. VTSU-B

*5 V13.2 is a component part of openNetServer V3.2.

*5 FHS V8.3 can output messages coded in UTF-E. Inputs in Unicode

*5 fields are converted field-specifically to EBCDIC or UTF-16 be-

*5 fore transfer to the applications.

*5 RSO V3.5 supports network printers with UTF-8 capability and

*5 accepts print files with UTF-8, UTF-16 and UTF-E coding.

*5 In the local spool, files can be printed on OCE high performance

*5 printers in UTF-16 format.

*5 DMS and POSIX files can be transferred in the Unicode formats

*5 UTF-8 and UTF-16 in BS2000 with openFT V10.0.

*5 Note:

*5 The size of all files remains unchanged. Since UTF-16 occupies 2

*5 bytes per character, a SAM record can only contain 16000 charac-

*5 ters and not 32000 characters as previously. The same applies

*5 analogously for the database fields NCHAR and NVCHAR.

*5 You will find detailed information on Unicode support in the Re-

*5 lease Notices of the separate products.

Page 23