Overview

Code Page Editor

Code pages are used by Windows to determine the character sets being displayed on the screen and used by applications. Much of the computer industry uses Unicode A superset of the ASCII character set that uses two bytes for each character rather than one. Able to handle 65,536 character combinations rather than just 256., while the Barr Enterprise Print Server environment uses EBCDIC coding. The Code Page Editor component of the Barr Enterprise Print Server provides the ability to customize the conversion of data between EBCDIC and Unicode, as well as between ASCII and Unicode. This feature is especially useful for transferring data from computers to the mainframe.

When some file types are imported into the Barr Enterprise Print Server using Print Utility or BARR/PRINT TCP/IP, code page processing occurs in two steps.

  1. The original code page format of the data is translated into Unicode (Code Page In).

  2. The data is then translated into either ASCII or EBCDIC using a second code page (Code Page Out).

If Code Page In is equivalent to Code Page Out, then there is no Unicode translation and the data remains the same except for NJE wrapping. NJE-wrapped Equivalent to the NJE format at the mainframe. The data is typically EBCDIC and is formatted as NJE records, with NJE record headers and NJE file headers. EBCDIC data is the preferred data format for BARR/SPOOL, therefore, you typically will not need to edit the code page translation tables.

If you are printing to a BARR/PRINT390 printer, you might need custom code pages if you are using channel printers configured to print ASCII text, or if you are using custom UCS Acronym for Universal Character Set. Some printers require loading a UCS buffer to match the print train or band installed. trains and translation tables.

With the Code Page Editor, you can perform the following tasks.

What do you want to do?

See also: