On Sep 17, 2015, at 6:41 PM, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> wrote:
I haven't tried embedded the PJL sequence in WSCST as you are doing, but it seems logical that it'd work.
For USRDTATFM, I used a modified version of IBM's TSPRWPR tool. I think this tool was originally part of QUSRTOOL and was to enable page range support with remote writers...
But, I got a copy that they had modified further to also support the stapling and hole-punching capability of a newer copier/printer. This was written by Rodney Johnson from IBM, and was written in ILE C.
I modified it to support the devices that I needed. (The PJL for hole punching and stapling was different on my devices than the one Rodney had provided.) and also to set the userid and B&W printing mode (which, of course, is really grayscale as you correctly noted in your WSCST example.)
Unfortunately, I no longer have access to the code since it was a previous job -- but perhaps you can locate the TSPRWPR that has the stapling/punching support and start with that? Maybe someone on the list knows where to get that.
On 9/17/2015 1:24 AM, Don Brown wrote:--
Thanks for the information Scott.
I am thinking you needed to do this to be able to insert the user id as
this is dynamic information. (I have a customer in Adelaide that would
really benefit from having the user id in the job but that is a job for
As the information is static - will be for every job my next option is to
apply a WSCST with a printer initialisation string to set the mode.
Based on the HP PJL manual I am thinking;
/* Ec% - 1 2 3 4 5 X @ P J L CrLf */
DATA = '1B252D31323334355840504A4C0D0A'X
/* @ P J L S E T R E N D E R M O D E = G R A Y S C A L E
/* EcE (Initialize Printer) */
I am though very interested in investigating the use of the USRDTATFM
exit point. If anyone has any working example of this and would like to
share I would really appreciate it rather than starting by searching for
the relevant manual(s)
From: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 16/09/2015 11:27 AM
Subject: Re: Set spool file to be recognised as black and white as
opposed to colour
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
There is an escape code that needs to be sent to the printer to tell it
to use black & white mode -- and unfortunately, the Host Print Transform
does not send this code.
I fixed this at a previous job, about 10 years ago, by inserting some
code using the USRDTATFM exit point... but it was 10 years ago, and I
don't remember the specifics anymore, sorry.
In our case, we were using the printer's statistics to charge
appropriate departments within our organization (each employee used
their own signon to print to this printer, and we charged their
departments a different rate per page for B&W vs Color, this is why we
had to fix it.) So we had code in there to insert their userid for the
printer to recognize it when printing from IBM i, as well as set the B&W
mode (IBM i never printed color)... it was fairly complex.
Unfortunately, I don't have any of the specifics. But, maybe this will
help you look in the right place? (PJL manual, perhaps?)
On 9/15/2015 6:56 PM, Don Brown wrote:workstation
We have a new colour printer (Fuji-Xerox MFP model FX DocuCentre-IV
C2265 PCL 6)
We are using a remote output queue to connect to a Windows 2012 R2
server with LPR printing enabled.
The issue is the printer is detecting every print job from the System i
as a colour job and this results in being charge at a colour rate per
I have looked at the *HPCOLORLJ work station customising object for any
commands that relate to colour but nothing seems to be obvious. I have
tried HP5 and other options for manufacture type and model but always
the print job is received/identified as colour.
Could anyone suggest how I could configure the output queue or
customising object to enable the print jobs to be recognised as black
and white jobs.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.