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

I don't believe this is true.

*AFPDS spool file resources are cached on the printer.  I'll take your word
that *IPDS ones are too.

Take a look at the resource retention parm (RSCRET) of the CRTPSFCFG.

If you read through the Printing V Redbook, you'll find that *IPDS is the
printer stream used for both *IPDS and *AFPDS spool files.  Which makes
sense considering that for either one the (native) printer type must be
*IPDS.  

Again, according to the Redbook.  *IPDS is all points addressable just the
same as *AFPDS.  As I recall there was a post from Rodney Johnson from the
iSeries print/spool team on the news group that basically said *AFPDS was an
expansion of *IPDS but *IPDS was still the underlying stream.


HTH,
Charles


> -----Original Message-----
> From: PaulMmn [mailto:PaulMmn@xxxxxxxxxxxxx]
> Sent: Friday, September 10, 2004 1:40 AM
> To: Brad Stone
> Cc: midrange-l@xxxxxxxxxxxx
> Subject: Re: IPDS to AFP (was Re: Confused about printing)
> 
> 
> IPDS is designed to work with form overlays.  The protocol will 
> transmit the overlay to the printer, which caches the overlay.  Then 
> the variable data is sent, page by page, to the printer.  If I 
> remember what I read correctly, the printer can cache several 
> overlays to save even more time.
> 
> AFP can't handle the caching--  you can print the same things that 
> IPDS prints, but the iSeries has to build a bit map of every page and 
> send it to the printer.  On a local connection it isn't too bad.  But 
> on a remote connection, you'll clog your comm link!
> 
> The variable data that IPDS sends for each page is only a few 
> characters-- a full 80 x 24 green screen is about 1920 characters; 
> the bit map is a whole lot larger.
> 
> --Paul E Musselman
> PaulMmn@xxxxxxxxxxxxxxxxxxxx
> --
> 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.
>