Re: Using TCP/IP Jet Direct with Proprinter III XL

Vernon

The card is an external jet direct...i do have the raw1 specified.

The Winframe server is talking to it no problem. The 400 prints to it almost
just right execpt
the print quality is quite bad for some reason. Oddly, the header portion of
the report which specifies username and even the IP number prints just
fine...good quality...it's the actual report
that is fuzzy.

I'll give it some more time tomorrow and see if I can get it to work.

Thanks for the tips!


Vernon Hamberg wrote:

> Jim
>
> At 10:35 PM 7/5/1998 -0400, you wrote:
> >Hi
> >
> >I've got this printer to print using rmtoutq method and plan to try
> >creating a *WSCST object
> >to correct the print quality problem.
> >
> >Couple things I'm sure about...
> >
> >Is it necessary to use rmtoutq when this is a locally attached printer
> >on the *LAN ?
>
> Are you talking about the HP Jet Direct card? Can this be installed in and
> IBM printer?
>
> What is the direct attachment? Novell print server? AS/400 knows nothing
> about Novell. But you do need RMTOUTQ for IP attached printers.
>
> Having said that, you can use CRTDEVPRT for IP printers if you are on at
> least v4r2. This gives more functionality than CRTOUTQ.
>
> >On the MFGMDLTYP parm...should i specify *IBM42023 or is there a model
> >type for the
> >Jet Direct card that goes here ?
>
> I would think you specify the IBM printer type that is the closest match.
> More precisely, pick the item that best matches the emulation you're using,
> since many of these printers can look like an HP. If that's the case, use
> an HP setting or one of the IBM ones with 'HP' at the end. The card should
> basically be a 'wire' that just gives you the connection. Be sure to use a
> queue on the card that performs no translation, usually called 'raw' on the
> JetDirect.
>
> >The document in the knowledge base says to rtvwscst mfgmdltyp(IBM42021)
> >, modify
> >for print quality problem and save as IBMDRAFT.
> >
> >Should I retrieve IBM42011 or IBM42023 ( proprinter III ) ?
> >
> >If the latter would the mods be the same as for the 42021 ?
>
> I believe the mods will be in the same place in the source, at least. The
> source is a kind of tag language and you should be able to identify what
> you're working with, without too much difficulty. Retrieve the source for
> the closest match to your printer. The actual code strings may vary,
> according to model. Hope not, but you never know.
>
> If you use your own *WSCST, you need to use *WSCST for MFRTYPMDL and
> specify your own *WSCST object in the WSCST parameter.
>
> >I'm anxious to try this tomorrow as I got so close today but didn't have
> >the necessary info at work to do the job....will soon have web access at
> >work...can't wait!
>
> Good luck!!!!
>
> Vernon Hamberg
> Systems Software Programmer
> Old Republic National Title Insurance Company
> 400 Second Avenue South
> Minneapolis, MN  55401-2499
> (612) 371-1111 x480



--
Jim W
http://www.netcom.com/~jimwelsh/welcome/welcome.html
mailto:jimwelsh@ix.netcom.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---