Extra printer codes? RE: pjl help, once again...

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
The printer now recognizes my first @PJL command, but will not respond to my
2nd PJL string...

So if is send it.
<esc:1b>X-12345X@PJL SET PAPER=LEGAL<CR:0d><LF:0a>
@PJL SET COPIES=2<cr:0d><lf:0a>


The sniffer on the ip port shows me this...
<esc:1b>X-12345X@PJL SET PAPER=LEGAL<CR:od><LF:0a>
followed by :
1b 26 61 30 30 30 30 30 48 1b 26 61 30 30 30 38 37 56
followed by:
@PJL SET COPIES=2<cr><lf>

Is there any way to turn off these extra bytes? That the as/400 thinks I
need?

Thanks, tim



> -----Original Message-----
> From: Vernon Hamberg [SMTP:vhamberg@attbi.com]
> Sent: Tuesday, August 20, 2002 10:06 PM
> To:   midrange-l@midrange.com
> Subject:      RE: pjl help, once again...
>
> Tim
>
> You probably want hex - those look like HP's output where <CR><LF> is
> x0D0A
> in ASCII.
>
> You might need to use a WSCST (workstation customization) object to handle
> converting the ESC (x1B). That code wreaked havoc with our printers, as I
> recall. The origginal solution used a 2-char sequence that was converted
> at
> a DecisionData workstation to the ASCII ESC. But that did not work when we
> moved to IP printing. Then we ran RTVWSCST against the printer
> manufacturer/model (see the prompt of the command for a match with your
> HP). Then I added an EBCDIC-ASCII translation section that used a
> seldom-used character in ASCII to convert to the ESC. I used x9E, I think
> -
> it was the character that looks like 'a' and 'e' stuck to each other. - Æ
> .
> An example can be seen at
> <http://www-912.ibm.com/s_dir/slkbase.NSF/acf2ee1e9d64b16e8625680b00020389
> /4a3112207b82f0ae862565c2007d0dbf?OpenDocument&Highlight=0,ebcasctbl>.
> You can find the values you need for the other code points in the WRKTBL
> command - find the table that corresponds to the EBCDIC->ASCII
> translation,
> display it , and build the DATA section of the WSCST accordingly.
>
> Good luck
>
> Vern
>
> At 10:50 AM 8/20/02 -0700, you wrote:
> >Thanks for the reply... But I have a question concerening this..
> >Ec%-12345X@PJL <CR> <LF> @PJL SET COPIES = 3 <CR> <LF> Ec%-12345X
> >the Ec%  is that straight text?  Or do I need a hex value to emulate the
> >escape sequence?
> >
> >Thanks, tim
> >
> > > -----Original Message-----
> > > From: Vernon Hamberg [SMTP:vhamberg@attbi.com]
> > > Sent: Monday, August 19, 2002 9:51 PM
> > > To:   midrange-l@midrange.com
> > > Subject:      Re: pjl help, once again...
> > >
> > > I seem to remember having a single field in a single format,
> SPACEB(0).
> > > You
> > > set the field to the string you want to send. You can fill it with hex
> > > strings as well as regular strings. Maybe put the various pieces into
> a
> > > file and just read it. Where I used to work we had an extensive system
> > > like
> > > this that built PCL on the fly - sorry, no code.
> > >
> > > DDS to define the format in a PRTF. And, optionally, a PF to contain
> the
> > > codes.
> > > RPG to set the field value and WRITE to the PRTF
> > >
> > > HTH
> > >
> > > Vern
> > >
> > > At 04:24 PM 8/19/02 -0700, you wrote:
> > > >How do I send these type of commands, to a printer connected to the
> > > as/400
> > > >via tcp/ip
> > > >
> > > >Is it via a CL? RPG?  DDS?  PRTF?
> > > >
> > > >Could someone please help, with a sample piece of code?
> > > >
> > > >Thanks...  Tim
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential or privileged
information.  Any unauthorized review; use, disclosure or distribution is
prohibited.  If you are not the intended recipient, please contact the
sender by reply e-mail and destroy the message.