Re: IPDS to AFP (was Re: Confused about printing)

[Pat Barber <mboceanside@xxxxxxxxxxxxxxxx>]

IPDS is a "hardware" function with ipds commands used
in DDS. It's been around for "many" years. AFP is another
horse that requires optional software for the most part.

HPT with *afpds can handle a "few" special operations
but not all.

CWilt@xxxxxxxxxxxx wrote:

> Brad,
>
> I'm no expert at this.  But as I understand it, *IPDS is basically a subset
> of *AFPDS.  So *AFPDS can do everything *IPDS can do and more.
>
> I've not yet had a problem just changing the printer file type from *IPDS to
> *AFPDS and printing it to a HPT printer.
>
> Note, the only catch is a native printer defined TYPE(*IPDS)  AFP(*NO) can
> print *IPDS but not *AFPDS.  Additionally to have a native printer defined
> TYPE(*IPDS) AFP(*YES) that can handle *AFPDS spool files, you need the extra
> cost PSF/400 license program.
>
> Charles
>
>
>
> > -----Original Message-----
> > From: Brad Stone [mailto:brad@xxxxxxxxxxxx]
> > Sent: Thursday, September 09, 2004 2:33 PM
> > To: Midrange Systems Technical Discussion
> > Subject: IPDS to AFP (was Re: Confused about printing)
> >
> >
> > Charles,
> >
> > Can you simply change an IPDS spooled file to AFPDS (the
> > printer device type attribute of the spooled file) and HPT
> > will work?  Or is there more involved?  I haven't work with
> > IPDS for a long time.  I would suspect (probably wrongly)
> > that there may be some proprietary IPDS information in
> > those spooled files?  Or maybe not...
> >
> > Brad
> >
> > On Thu, 9 Sep 2004 14:24:46 -0400 
> > CWilt@xxxxxxxxxxxx wrote:
> >
> > > Loyd,
> > >
> > > Host Print Transform (HPT) can't handle *IPDS spool
> > > files.  You need to
> > > change the spool file to *AFPDS.
> > >
> > > Leave the printer *DEVD alone.  You don't need AFP(*YES)
> > > when the printer is
> > > using HPT.
> > >
> > > In other words, HPT can't do *IPDS to ASCII.  But it can
> > > do *AFPDS to ASCII.
> > >
> > > HTH,
> > > Charles
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Goodbar, Loyd (ETS - Water Valley) 
> > > > [mailto:LGoodbar@xxxxxxxxxxxxxx]
> > > > Sent: Thursday, September 09, 2004 12:04 PM
> > > > To: Midrange Systems Technical Discussion
> > > > Subject: Confused about printing
> > > >
> > > >
> > > > I have an IBM 4312 printer I'd like to replace with a
> > >
> > > Dell 
> > >
> > > > M5200. Using the
> > > > recent "Help! Best Host Print Transform for Dell W5300 
> > > > Printer" thread as a
> > > > guide, I have set up the Dell as a *LAN/3812 with host
> > >
> > > print 
> > >
> > > > transform and
> > > > using the *IBMPJLDRV system driver. Currently no
> > >
> > > workstation 
> > >
> > > > customizing
> > > > object, user defined object, or data transformation
> > >
> > > program.
> > >
> > > > I was under the impression I was able to print IPDS
> > >
> > > spooled files with
> > >
> > > > barcodes to this printer, but the system holds the
> > >
> > > file. 
> > >
> > > > Also, printing
> > > > reports with MULTIUP(2) doesn't; it prints spooled
> > >
> > > files as 
> > >
> > > > if the multiup()
> > > > were not specified.
> > > >
> > > >
> > > >
> > > > Somewhere else I read I could use the barcodes if I 
> > > > recompiled the DDS using
> > > > spooled file type AFPDS. However, I can't seem to get
> > >
> > > the 
> > >
> > > > Dell printer to be
> > > > an AFP capable printer with a device class of *LAN and
> > >
> > > type 3812.
> > >
> > > > Is there a "simple" matrix of which spooled file types
> > >
> > > work with which
> > >
> > > > printer types?
> > > >
> > > >
> > > >
> > > > I have two goals with the Dell printer: 1) Support
> > >
> > > printing 
> > >
> > > > of bar codes -
> > > > how? What's the proper non-IPDS setup for the printer?
> > >
> > > 2) 
> > >
> > > > Support printing
> > > > of regular spooled files with MULTIUP(2). Is this an 
> > > > IPDS-only function or
> > > > is this supported with HPT?
> > > >
> > > >
> > > >
> > > > Loyd Goodbar
> > > >
> > > > Senior programmer/analyst
> > > >
> > > > BorgWarner
> > > >
> > > > E/TS Water Valley
> > > >
> > > > 662-473-5713
> > > >
> > > >
> > > >
> > > > --
> > > > 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.
> > >
> > > --
> > > 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.
> >
> > Bradley V. Stone
> > BVS.Tools
> > www.bvstools.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.
>
> --
> 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.