Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Global Conversion Routine for Multiple Emulators, Utilities and Applications in a Single Product

IP.com Disclosure Number: IPCOM000037194D
Original Publication Date: 1989-Nov-01
Included in the Prior Art Database: 2005-Jan-29
Document File: 3 page(s) / 54K

Publishing Venue

IBM

Related People

Nguyen, HH: AUTHOR [+5]

Abstract

The PC DOS internal data is in an 8-bit IBM PC Code. The internal data stream of a product can be in many forms. The product's data needs to be converted to and from the system supported codes. The OS/2* Extended Edition product accomplishes this with its General Convert Routine. It has the following features to satisfy the unique data conversion needs of all pieces of the product.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

Global Conversion Routine for Multiple Emulators, Utilities and Applications in a Single Product

The PC DOS internal data is in an 8-bit IBM PC Code. The internal data stream of a product can be in many forms. The product's data needs to be converted to and from the system supported codes. The OS/2* Extended Edition product accomplishes this with its General Convert Routine. It has the following features to satisfy the unique data conversion needs of all pieces of the product.

1) All code pages in the product must be supported. The operating system has five 8-bit IBM PC code pages. The 3270 emulator supports nine EBCDIC code pages. The Async emulator supports six 7-bit ASCII code pages.

2) The conversion works for any supported code page to any other supported code page. For example, the conversion can be an 8 bit PC code page to an 8- bit PC code page or to an EBCDIC code page or to a 7-bit ASCII code page.

3) The conversion routine builds a table for the conversion. The user specifies a source code page and a target code page. The conversion routine builds the translation table in the user specified location. The table that is built, provides uniqueness of code points. This allows applications, like file transfer, to have round trippable data conversion.

4) The conversion routine also has the option of building a table that does not have uniqueness of code points. An application may require a substitution character (i.e., underscore) when the source and target code pages have different character representations. The conversion routine allows the user to specify the substitution code point that will be used in the table when conversion is not possible for a particular character.

5) Control codes are also converted when going from any suppor...