My trusty IBM AS-400 Printing V Redbook says "AFP resources are
elements that PSF can use at print time. The resources are
referenced in the spool, not included in the spooled file themselves."
My trusty IBM AS-400 Printing V Redbook says "If the AFPDS spooled
file uses any resources, such as overlays, page segments or host
resident fonts, these resources must exist on the target system if
they are to be included in the printed output. The AS/400 does not
insert resources in the spooled file before sending the file to the
This is with respect to remote writers going from AS/400-->AS/400...
But I suspect the same thing applies to SNDNETSPLF
On Wed, Sep 26, 2012 at 4:25 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
Something is tickling the back of my mind....
AFP resources aren't embedded in the spool file....they are sent to
the printer by the spool system...
I think when you print AFP documents on another system you need to
make the the resources are already there...
On Wed, Sep 26, 2012 at 4:03 PM, Alan Shore <ashore@xxxxxxxx> wrote:
Good afternoon everyone
Before I forget, we are on V5r4 on both systems (see later).
I have created a print file using a Page Segment on one system and this prints perfectly on that system.
When I use the command SNDNETSPLF with the parameter DTAFMT set to *ALLDATA and send that same spool file to another system and print that same spool file on the other system, the page segment does NOT print, although the rest of the print file does.
Is there something that I am missing?
Is there some way that will tell me that the page segment is on the spool file?
Thanks in advance
Programmer/Analyst, Direct Response
"If you're going through Hell, keep going" - Winston Churchill
Disclaimer: This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives