Data formats and conversions

Barr Enterprise Print Server

The native data format used by the Barr Enterprise Print Server is EBCDIC Line Data wrapped in mainframe NJE format. Line Data is simple text with ANSI (ASA) or 3211 machine carriage control. This is essentially the same format used by the JES2 spooling system on IBM mainframes, which is logical because the Barr Enterprise Print Server is, in many ways, emulating a JES2 spooling system.

Most of the conversions performed by the Barr Enterprise Print Server can be logically deduced once you understand this starting point. For example, if you receive a job from a mainframe through BARR/NJE and then print that job to a channel-attached printer through BARR/PRINT390, clearly no conversions will occur because all three devices, the mainframe, the Barr spooler, and the channel printer use EBCDIC Line Data by default. You can also deduce that translations will occur by default when the source or destination is something that does not use EBCDIC Line Data.

The Record-Oriented Inputs and Record-Oriented Outputs in the following diagram are related to emulation of various IBM Mainframe devices, which use EBCDIC Line Data natively. The File-Oriented Inputs and File-Oriented Outputs in the diagram, on the other hand, are all more native to the computer or UNIX An operating system for workstations developed by AT&T Bell Laboratories that features multiprogramming in a multiuser environment. world, and they typically use ASCII data.

This table summarizes the main features of record-oriented and file-oriented interfaces.

Record-Oriented Interfaces

File-Oriented Interfaces

Usually associated with IBM Mainframe interfaces like RJE and 3211 emulation.

Common in the computer or Inter-networking arenas.

EBCDIC text is assumed.

ASCII text is assumed.

EBCDIC Line Data format with ASA or 3211 machine carriage control is used.

ASCII text with ASCII carriage control is generally assumed, but any format is possible.

Files are transmitted as a series of records with some agreed upon-record structure (that is, delimiters and carriage control).

Files are transmitted as a sequence of bytes with no inherent record structure.

True binary pass-through IS NOT possible.

True binary pass-through IS possible.

Four basic data conversion possibilities can be used with the Barr Enterprise Print Server.

See also:


Receive from a record-oriented input and send to record-oriented output

Typical situation

Receiving jobs from an IBM mainframe through NJE and printing the jobs on channel-attached printers, such as Xerox laser and IBM line printers.

General notes

Special

Some data conversion can be forced using code pages when desired. Here are two examples of when you might want to translate the data.

Receive from a record-oriented input and send to file-oriented output

Typical situation

Receiving jobs from an IBM Mainframe through NJE or RJE and printing them on computer or network printers. Also, receiving jobs from an IBM mainframe and writing them to a computer or network drive or long-term storage device.

General notes

Special

The Barr File port can be used on the output side to generate special formats. For example, if you want to leave the data in EBCDIC, you can use the Barr File Port to write the file to disk in an EBCDIC fixed-length format.

Receive from a file-oriented input and send to record-oriented output

Typical situation

Receiving jobs from any TCP/IP-based host (UNIX systems, HP 9000s, AS/400s, PCs, and so on.) and printing them on channel-attached printers, such as Xerox Lasers and IBM line printers. Also, printing to the channel-attached printers from the computer or LAN environment.

This case also includes sending print jobs generated in the computer and LAN environment to an IBM mainframe through NJE or RJE.

General notes

Special

One other possibility in this case is the Barr archive format. Data originally spooled to one Barr Enterprise Print Server can be sent out in the Barr archive format, and then received on a second Barr Print Server through LPD, socket, or Print Utility. This method of exchanging jobs preserves both the data and all the header information, and no conversion or translation will occur in the exchange.

Receive from a file-oriented input and send to file-oriented output

Typical situation

Using the Barr Enterprise Print Server to manage your computer and Network printing.

General notes