× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Jim,

The typical data stream format expected by a copier/printer when activating
a finishing function prior to printing a PCL formatted spool file would be
as follows:

1. Universal Exit Language Command to delimit spool file boundary
<esc>%-12345X

2. Multiple PJL Commands (@PJL...) to define the default print environment
for the spool file. Included in these commands will be the activation of the
stapling option, the choice of where staples should be placed, and the
output bin where the pages should be directed so that stapling can occur.
Quite often PJL commands to activate features such as stapling will use a
syntax that is unique to the print controller being used by the
copier/printer in question.

3. PCL commands to format the pages to be printed.

4. Universal Exit Language Command to delimit spool file boundary - the job
is complete. <esc>%-12345X

In the case of PCL compatible printers, the OS/400 based Host Print
Transform function was created by IBM to handle the creation of properly
formatted ASCII spool files that included the necessary PCL commands
required to format the pages of a report correctly for printing by a PCL
compatible printer.

It was assumed that PJL commands would be handled by a different lower level
driver functionality that could be developed by printer manufacturers who
read the OS/400 print API's. Unfortunately, there has been little interest
shown by printer manufacturers to date in performing the driver construction
task for OS/400 so that the only PJL driver that exists today is the one
authored by IBM known as *HPPJLDRV. This driver will insert the necessary
UEL commands at the beginning and at the end of each spool file to show the
target printer the spool file boundaries but it offers no capability to be
customized to send other PJL commands that might be required by a particular
printer to activate a certain feature.

This typically leaves an iSeries or AS/400 end user with the following
options:

1. The *HPPJLDRV driver expects the target printer to support bi-directional
PJL command - response conversational capabilities. Many of the digital
copier/printer products currently being sold in the marketplace do not yet
offer this facility. If the copier/printer in question does support this
function, you can try to activate the required finishing option through a
front panel setup of the copier/printer along with a *LAN configuration
(using the *HPPJLDRV driver) on the IBM host. This option is limited and
often doesn't work well when the printer is being shared across multiple
hosts.

2. You can investigate using Client Access or a third party printing
emulation package. In this scenario, you do not always activate the OS/400
based host print transform feature. Client Access and a number of third
party packages support the TN5250E transport protocol. They appear to the
IBM host as typical 3812 model 1 system printers capable of receiving an
EBCDIC data stream directly. In an operating system environment (frequently
Windows) that offers a pre-built print driver for the target copier/printer,
it is possible to bring the EBCDIC data into the host sponsoring the TN5250E
printer client software and then convert the incoming data from EBCDIC to
ASCII and pass the result to a print driver for final formatting and
delivery to the target printer. Under this scenario, all of the
pre-requisite PJL commands will be sent to the target printer at the
appropriate time by the driver selected.

2a. It is also possible to direct OS/400 host print transform created output
to an intermediate server where a software package will add the necessary
PJL command header to the incoming file before passing it to the actual
printer for final rendering.

3. You can also investigate the use of one of the OS/400 print API's (Begin
Open Time Commands) to add the necessary PJL commands onto the front of a
spool file as it is released towards the target printer.

HTH

Best Regards,

/Paul
--
Paul Tykodi
National Product Manager
Intermate US Inc.

p: 603-431-0606 x115
f: 603-436-6432
E-mail: paul@intermate-us.com
www.intermate.com

>From: "Jim Franz" <franz400@triad.rr.com>
>To: <MIDRANGE-L@midrange.com>
>Subject: using printer stapler in pcl6
>Date: Tue, 11 Jun 2002 11:07:02 -0400
>Reply-To: midrange-l@midrange.com
>
>is it possible for me to trigger the printer to staple a report,
>either printing 200 copies & stapling each copy or
>stapling each customer break? is there a specific string in a
>workstation customization? Currently using a variation of HP5SI
>customization & pcl6.
>jim franz
>--



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.