PJL, WSCST and Hole-Punching

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Hello,

Our company has a Ricoh 2035e photocopier with a finishing unit that can 
punch holes in paper.  It's easy to make that hole punching work with the 
Windows print driver.

However, I'd like to have holes punched in reports coming from the 
iSeries. From the iSeries, the printer is configured as a PJL printer (the 
"port 9100" thing) with Host Print Transform turned on, and 
MFRTYPMDL(*RICOH2035).

However, there doesn't appear to be anything set up to allow hole punches!

So, I'm trying to edit the WSCST source, figuring I could insert escape 
codes to send the hole punching commands.  So, I contacted Ricoh, got a 
copy of the manuals for the PCL and PJL commands that this copier 
supports, and I'm trying to insert the correct sequences into the WDSCT.

Unfortunately, however, the hole punching appears to be a PJL command 
rather than a PCL command.  And WSCST doesn't appear to support PJL 
commands, as far as I can tell.

So I tried inserting the PJL into an RPG program (using the x'03' 
"transparent data" hex code) but it still doesn't work -- the PJL command 
appears to be ignored.

Now, I can write a sockets program that connects directly to port 9100 of 
the copier and sends the raw data to it -- and that works -- but that 
seems like a lot of screwing around just to get holes to punch.

Does anyone know of a way that I can have the system insert PJL sequences 
into the data stream as it's communicating with the pritner?  Or, am I 
out of luck?

Would this be possible with an exit program?  If so, which exit program 
would I have to write? (would the prgoram specified with USRDTATFM work, 
or do I need USRDRVPGM, or what?)

Here's the PJL code I'm trying to send:

Punch = ESC + '%-12345X@PJL' + CRLF
      + '@PJL SET PUNCH=LEFTPORT' + CRLF
      + '@PJL SET PUNCHHOLE=US3' + CRLF
      + '@PJL SET OUTBIN=FINISHERSHIFT' + CRLF
      + '@PJL ENTER LANGUAGE=PCL' + CRLF
      + ESC + 'E';

Has anyone made this work?  Anyone have any suggestions?

---
Scott Klement  http://www.scottklement.com