Scott,

If you're on v5r3, take a look at the source for TSPRWPR in QUSRTOOL.

If not contact Rodney Johnson with IBM's AS/400 spool team and get the latest 
version.  From a conversation with him in the newsgroup:
http://groups-beta.google.com/group/comp.sys.ibm.as400.misc/browse_frm/thread/ac498c2f598ca7c7/e43d7fdfa590d86a?q=SNMP+IPP+Rodney#e43d7fdfa590d86a

or http://tinyurl.com/6qkgr

" In theory, TSPRWPR would then work with the SNMP, telnet 5250 printing, and 
LPR (remote
writer) to provide stapling and hole punching.  Course the version I
send out is written to only work with IBM 1145 and 1130 printers.  It is
also coded to supposedly work on the 4332 and 4324 printers, but was not
able to test and confirm.  Hopefully the code is written in a manner
that is easy to modify to match other printer finishers."

HTH,

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Scott Klement
> Sent: Wednesday, May 11, 2005 8:01 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: PJL, WSCST and Hole-Punching
> 
> 
> 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
> -- 
> 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,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 


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.