Distribute Host / Mainframe Print:

Distribute Host / Mainframe Print:  Overview

Production printers are not the sole destinations for mainframe print jobs any more.  They have been joined by a varied assortment of destinations such as multi-function devices, data warehouses, web users, email, etc. 

Distribute Host / Mainframe Print:  Challenges  

The main challenge related to widely distributing mainframe output is how to achieve this without making changes on the host. 

Distribute Host / Mainframe Print:  Barr Systems' Solutions

Our solutions for distributing mainframe print are based on two main components.  One is the input side, where we have four main ways in which we can seamlessly extract data from the host.  More details on this follows below. 

Once we receive the data, it is our powerful network based output manager that takes over and ensures the delivery to the destination.  The delivery is dynamic, based on the contents of the job.  This functionality is covered in our Document Distribution and Delivery Application guide.

Each of the four different methods of receiving data from the mainframe has its advantages:

• NJE (Network Job Entry) - The mainframe treats us as a peer, and therefore provides us with all of the job's header fields, which can be used for routing.  Perfect for mainframe consolidation projects.  Usable over SNA or IP.
• RJE (Remote Job Entry) - The mainframe communicates with us via the 3770 protocol.  Usable over SNA or IP.
• TCP/IP - The mainframe sends us data over IP using LPR.  We also support input from LRS' VPS product.
• Mainframe Channel - Our Bus & Tag and ESCON boards enable direct connection to the mainframe.  We emulate printers or tape drives.  Most secure solution thanks to the physical connection.  Perfect for situations where an actual channel-attached device is being replaced or moved.

If you would like to understand in greater detail how these connections work, please see the following:

Using Peer-to-Peer Connections to Receive Host Print

The first solution involves using the BARR/NJE module to provide the most sophisticated, versatile and feature-rich connection to the mainframe for your organization’s remote destinations. In this solution, the central mainframe operates as if the BEPS is a peer host. Using the standard NJE protocols, the BARR/NJE module accepts mainframe print and job sets and feeds them to the Barr Server, which then routes the jobs to the appropriate local printer.  Because of the mainframe thinks of us as another mainframe, it provides us with a full complement of job headers, all of which can be used to set up dynamic routing.

Using Remote Job Entry (RJE) to Receive Host Print

The second solution is very similar to the solution mentioned above.  The BARR/RJE module provides control of the job flow between your mainframe and BEPS. You can use BARR/RJE to receive job output and setup messages (PDIR) from the mainframe and send commands and data files to the mainframe.

You can connect BARR/RJE to your mainframe in a variety of ways. First, BARR/RJE can connect to an IBM mainframe over an IP network using the EE Link, without the need for special routers or SNA gateways. Second, BARR/RJE can connect via an 802.2 network (Token Ring or Ethernet) using IBM 3174, 3725, and 3745 communications controllers. Third, BARR/RJE can connect via a modem (dial-up or dedicated line) using BARR/SYNC. Finally, BARR/RJE can connect via a MS/LUA connection through an SNA gateway (Microsoft SNA Server, SNA Workstation, or HIS).

Using Your Mainframe’s TCP/IP Stack

Barr offers a third solution for organizations that have implemented TCP/IP on the mainframe, providing remote printing capability without changes to the host. In this case, the Barr Server receives data remotely from the host over your existing network connections via BARR/PRINT TCP/IP.  If you have channel-attached printers, they can be driven at rated speed via BARR/PRINT390. BARR/PRINT TCP/IP implements Line Printer Daemon (LPD) to service Line Print Requests (LPRs) from anywhere on the Local Area Network (LAN) or Wide Area Network (WAN).  We also support direct input from LRS' VPS product.

Connecting to the host via Bus & Tag or ESCON

This easy-to-configure solution involves channel-attaching a Barr Server to the host using either Bus & Tag or ESCON and configuring it to emulate 3211 printers, IPDS printers, or 3490 tape drives.  The modules providing this functionality are BARR/PRINT CHANNEL, BARR/PRINT CHANNEL for IPDS, or BARR/CHANNEl Offload.  

As in all the other cases, once the jobs reach the Barr server, you have full control over where their routing.