|
Mark, You were looking in a different manual that I was. I was looking in the DDS Reference for printer files. It only said: In order to print based on the values specified for certain keywords, PSF is required. For example, spooled files generated with DEVTYPE(*AFPDS) can only be printed by PSF. Here is a list of DDS keywords that are valid for printer files that have the printer device type (DEVTYPE) parameter value specified as *AFPDS. Restrictions on DDS keywords are contained in this list as well. v AFPRSC v BARCODE v BOX <snip> The DDS manual is not (entirely) correct. While it is true that all of those keywords require DEVTYPE(*AFPDS). PSF/400 is not always required to print DEVTYPE(*AFPDS) spool files You can print *AFPDS spool files: 1) via HPT to *ASCII printers with some limitations 2) via PSF/400 to *IPDS printers 3) via PSF/400 and Infoprint server to PDF printers Notice that PSF/400 is only used in options 2 & 3. As it happens, AFPRSC is one of the keywords that HPT doesn't support. But the DDS manual doesn't specifically say that. The DDS manual doesn't differentiate between keywords such as AFPRSC which are not supported by HPT and those such as BOX and BARCODE which HPT does support. I agree that the manual you are looking at specifically says PSF/400 is required for the AFPRSC keyword. However, they key is that HPT doesn't support the AFPRSC keyword, thus you are left with options #2 and #3 above both of which require PSF/400. PSF/400 doesn't add any capabilities to HPT. So you can't print a spool file that uses AFPRSC to an *ASCII printer even if you have PSF/400. It would be more correct to say that AFPRSC requires a device defined TYPE(*IPDS) AFP(*YES). Do you see the difference? Of course, this whole discussion is only looking at IBM products. There are third party products that support converting *AFPDS spool files to PDF. Those third party products don't require PSF/400; as PSF/400 only comes into play when the iSeries sends spool files to a printer. I wonder if any of the third party products support spool files that make use of the AFPRSC command? Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of mlazarus@xxxxxxxxxxxxx Sent: Tuesday, August 08, 2006 9:18 AM To: midrange-l@xxxxxxxxxxxx Subject: RE: Printing images from the /400 Charles, Maybe this will convince you - from a v5r4 manual: http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/bo oks/s5445319.p df Check out (printed) page 18, table 4 (it's on page 36 of the PDF.) Table 4. DDS Keywords that Require PSF AFP resource (AFPRSC) ... -mark Original Message: ----------------- From: Wilt, Charles CWilt@xxxxxxxxxxxx Date: Tue, 8 Aug 2006 07:34:52 -0400 To: midrange-l@xxxxxxxxxxxx Subject: RE: Printing images from the /400 Mark, I'm not convinced. The v5r4 manual says specifically: "In order to print based on the values specified for certain keywords, PSF is required. For example, spooled files generated with DEVTYPE(*AFPDS) can only be printed by PSF." The is most definitely not true as *AFPDS spool files can be printed to *ASCII printers via HPT without PSF/400. The fact remains, PSF/400 is not used when printing to *ASCII printers. Now it's entirely possible that HPT doesn't handle this keyword, but I don't see spelled out. If HPT doesn't handle this keyword, then to make use of it you'd need to print it to an *IPDS AFP(*YES) printer which would indeed require PSF/400. HTH, Charles-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of mlazarus@xxxxxxxxxxxxx Sent: Monday, August 07, 2006 4:24 PM To: midrange-l@xxxxxxxxxxxx Subject: RE: Printing images from the /400 Charles, From the v5.3 manual: http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.js p?topic=/rzakd /rzakdmstafprsc.htm Note: Feature PSF/400 is required for use of this keyword. IfPSF/400 is notinstalled, you will not be able to print files using thiskeyword andspecifying DEVTYPE(*AFPDS). -mark Original Message: ----------------- From: Wilt, Charles CWilt@xxxxxxxxxxxx Date: Mon, 7 Aug 2006 15:59:56 -0400 To: midrange-l@xxxxxxxxxxxx Subject: RE: Printing images from the /400 Doug, I don't see anything about AFPRSC requiring PSF/400 in the DDS Reference for printer files. As I understand it, PSF/400 plays no role when printing *AFPDS spool files to an *ASCII printer via HPT so I don't see why it would be required. Charles-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf OfDouglas HandySent: Monday, August 07, 2006 3:42 PM To: Midrange Systems Technical Discussion Subject: Re: Printing images from the /400 Charles, PSF/400 is _NOT_ required to print from the iSeries to *ASCII printers. Sorry to not be more specific. I was referring to the use of AFPRSC() for adding TIFF images dynamically to the output. In thiscase, I believePSF/400 is required, even if it is an ASCII printer. Please correct me if I am wrong. Doug-------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.