System i5 / iSeries / AS/400 Printing

Have your AS/400 print jobs automatically sent to your Windows PC for formatting, emailing, converting to PDF, and more! SCS is preserved and AS/400 CPU time is cut in half when printing your AS/400 print files through RPM.

  1. RPM Remote Print Manager® (RPM) installs on a Windows PC.
  2. RPM receives a spool file from the AS/400.
  3. From there, RPM can save the file to disc, apply custom formatting to the AS/400 print job, or simply print the AS/400 spool file to your Windows printer.
  4. Print your AS/400 files to ANY Windows printer, no matter what make or model. As long as your Windows print manager can see the printer, RPM can print to it!

 

iSeries and AS400 printing software printable product overview

IT managers and system administrators have long struggled to make AS/400-based data available in Windows environments.

With RPM Remote Print Manager®, AS/400 host data can be sent to Windows-based printers or accessed on Windows-based systems. The result: lower costs, more flexibility, and more convenience. 


The challenge of freeing host data and making it available on other platforms, namely Windows, is easier and less expensive than you might think. And using host data within Windows environments provides a number of advantages:

  • Increased data availability: When key players have access to host data, they can make better decisions and incorporate the data in key business processes.
  • Connected cross-platform applications: Peripheral applications often reside on Windows PCs or servers, and these applications need access to the data residing on the host.
  • Lower print costs: Because Windows-based printers are common, inexpensive, and relatively easy to maintain, printing AS/400 data to them lowers printing costs.
  • Increased print convenience and flexibility: By placing Windows-based printers in key locations, printouts are easy to pick up, and new printers can be added to the network when needed.
     

Minimum host-side modifications

Putting RPM in place requires little change to the AS/400.
 
In most cases, the host printer simply needs to be redirected to RPM's IP address.

Advanced formatting and finishing capabilities

Host data can be formatted for a specific Windows printer allowing full use of all printer finishing functions, including double-sided printing, stapling, hole punching, n-up, watermarks, etc.
 
Margins, fonts, and text compression are also supported in RPM, including other data massaging options like PCL removal, ASA/Fortran, CR to CR/LF, EBCDIC conversion, and SCS to ASCII.

Simplified print job management

Managing print jobs in the Windows environment reduces host system expenses.

EBCDIC to ASCII

RPM can convert EBCDIC text to ASCII. RPM also supports country-specific extensions to EBCDIC, translating characters not used in the US or United Kingdom to the appropriate ISO 8859-1 codes.
 
RPM allows the user to select the extended EBCDIC codes from a menu of languages. RPM also attempts to match the current locale setting to an EBCDIC extension if one has not already been selected.

AS/400 iSeries SCS to ASCII Conversion

RPM enhances printing time and reduces CPU usage on the AS/400. RPM can interpret SCS codes and translate them to ASCII.
 
For non-text printing (pass-through and filter) RPM creates line oriented output using carriage return for overstrikes as appropriate.
 
For text output RPM preserves the SCS markup and reproduces attributes such as margins, font size, character position, etc.

AS/400 Host Print Transform

The AS/400 Host Print Transform converts the EBCDIC characters to ASCII and converts the SCS formatting instructions to a supported Manufacture Type and Model printer language (PCL or FX80). RPM passes the incoming transformed preformatted data directly to the printer. Very high through put and printer friendly for the supported printers.

RPM's AS/400 Print Queues

RPM's Printing Queues for AS/400 Mainframe to PC Printing: The Text Queue is one of the features that sets RPM apart from all other LPD products. RPM's ability to handle many text formats intelligently, while providing a simple interface, has been a key reason for IT professionals to make the switch from their existing AS/400 printing setup to RPM.

RPM's printing queues give the user extreme flexibility with numerous and hard-to-find formatting options. No more ugly mainframe reports or printing on a network printer, these print queues allow the user to print any host print file on a locally attached or TCP/IP addressable PC printer, raw or formatted!

The types of queues are one of the key features that set RPM apart from others' LPD servers, hardware or software. Each type performs a function and has completely different configuration options than other queue types. Within each queue, you'll find a transform and actions, or multiple occurrences of both. Simply put, the transform is what modifications need to be performed on a print file. The Action is where you want the print file to end up once the transforms are performed. With RPM, you can:

  • Print job is captured to process with an application or saved to a file.
  • RPM checks for duplicate filenames before saving and has many file naming options.
  • The filter queue can be used to integrate third-party software and solutions into RPM.
  • There is no need for any extensive AS/400 printer configurations
  • Easily format Legacy "greenbar" paper reports.
  • Formatting capabilities: modify margins, control fonts, wrap or truncate lines, bold and overstrike, and more.
  • Print from the AS/400 to unsupported PC print devices.
  • RPM passes raw information from the AS/400 to the PC print queue.
  • Receiving files with RPM's Raw Queue bypasses the Windows print driver.
  • RPM processes print data without modification as if the printer were connected directly to the host system through a parallel or serial connection.
  • The Raw Queue supports the advanced queue features such as transforming data, adding and appending bytes or a file, etc.

Read more about RPM's Print Queues

RPM Saves Money and Increases Efficiency in AS/400 Network Printing

  • Replace SNA A large state agency, by replacing green screens with PCs and emulators, and using TCP/IP in place of SNA, has saved millions of dollars directing host print jobs to locally attached parallel cable and USB-attached printers. Printouts are conveniently available and printer costs are significantly lower. (case study)
     
  • Host Label Printing A hospital information system provider creates labels from AS/400 healthcare applications. Host data is sent to RPM, which performs transformations: SCS is converted to ASCII, orientation is changed from portrait to landscape, font is changed to Tahoma 10pt, lines per inch are changed to 8, and page margins are altered. Patient or pharmacy labels are then printed correctly to a Windows-based local or network thermal label printer. (case study)
     
  • Banking Archives At a national bank, RPM receives jobs from an AS/400, converts SCS to ASCII, and saves the transformed jobs to disk. A storage solution then picks up the jobs for processing and archiving.
     
  • Convenient Delivery A wholesale company uses RPM for accounting: an AS/400 holds accounting worksheets which are sent to RPM on the accounting manager's PC. The worksheets are saved in a folder on this local machine and the manager then places the worksheets in other folders or distributes them to others. The AS/400-side process is simple: the OUTQs are pointed to RPM.
     
  • University Printing A registrar's office uses RPM Elite for printing transcripts and other documents. Print jobs go to line printers sent from the host system, but there are PCL escape codes that need to be taken out and others inserted by RPM. Also, depending on the formatting that needs to be done, jobs are directed to different queues, then the jobs go to 1 of the 22 printers in the office.
     
  • Compliance Records An investing firm receives transaction records from a vendor. The jobs arrive on 30 different IP addresses, with each address corresponding to a queue within RPM. RPM saves each record to disk for auditing purposes.