Re: Problem with Infoprint 1125

Hi George,

The Infoprint 1125 offers IPDS support as an extra cost feature. It is
enabled by adding a small DIMM style of board into the printer itself. Do
you know whether your order included the IPDS option or not?

Also when building a device description for an IPDS printer that uses cut
sheet feed, it is typically helpful to specify the FORMFEED parameter as
*AUTOCUT rather than *CONT. If you use *CONT (continuous feed), the OS/400
operating system is supposed to update the value for you after it receives
the list of supported features from the printer itself. Sometimes this
doesn't happen, which will cause extra form feeds to be inserted into your
spool files that will make a mess out of your report format.

HTH

Best Regards,

/Paul
--
Paul Tykodi
National Product Manager
Print4sight Inc.

p: 603-431-0606 x115
f: 603-436-6432
E-mail: p.tykodi@xxxxxxxxxxxxxxx
www.print4sight.com

Special Note: On November 30th, 2002, Print4sight Inc. acquired the business
assets and business activity of Intermate US Inc.

Print4sight Inc. as an official North American distributor will continue to
sell and support Intermate and Praim Printing products from current offices
in Portsmouth, NH, USA.

>Date: Thu, 15 May 2003 15:01:21 -0400
>From: George Kinney <GKinney@xxxxxxxxxxxxxxxx>
>Subject: Problem with Infoprint 1125
>
>We're running an iSeries (v4r5) and just aquired a new Infoprint 1125.
>(Which was sold to us under the premise that it is a replacement for the
>Infoprint21.) I've tried to set it up as we've set up our InfoPrint32s.
>
>I created the device with:
>
>CRTDEVPRT DEVD(EXPWH1) DEVCLS(*LAN) TYPE(*IPDS) MODEL(0) +
>         LANATTACH(*IP) AFP(*YES) PORT(5001) ONLINE(*YES) +
>         FONT(011 *NONE) FORMFEED(*CONT) SEPDRAWER(*FILE) +
>         PRTERRMSG(*INFO) MSGQ(*CTLD) ACTTMR(170) IMGCFG(*NONE) +
>         MAXPNDRQS(6) PRTCVT(*YES) PRTRQSTMR(*NOMAX) +
>         FORMDF(*LIBL/F1C10110) CHRID(*SYSVAL) +
>         RMTLOCNAME('192.47.217.96') +
>         USRDFNOBJ(*LIBL/EXPWH1 *PSFCFG) +
>         TEXT('Export/Body - Warehouse 1') DEPLOCNAME(*NONE)
>
>then varied it on, started a writer, moved a few spool files into the
>associated outq, and nothing. They just go to pending and stay there.
>
>I tried this previously as a remote-outq and it will print ascii, but IPDS
>jobs just cause the printer to spew up reams of line noise.
>
>Has anyone experienced anything similar with this model?  Or better yet,
has
>anyone managed to get one of these to work?  Is this thing just not
supported under
>v4r5?
>
>This printer *HAS* to do *IPDS printing to be of any use to me.