× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello Henrik

I wanted to optimize the performance. But I see, I have to go the IFS-way.

Thank you very much.

Jan

Am 16.06.2016 um 11:43 schrieb Henrik Rützou:
As far as I know you have to store the spool-file in PDF in the IFS since
you
can't write spool files into a storage address.

But what is the problem? You can just delete it after it is send to the
browser.

On Thu, Jun 16, 2016 at 11:17 AM, Jan Grove Vejlstrup <jgv@xxxxxxxx> wrote:

Hello

I create a webservice that receives a document-ID as input and shall
deliver a PDF of the document back to the consumer. I generate a spooled
file of the document and use the attributes wscst(*PDF) and tostmf of the
printer-file to convert the spooled file to a PDF and store it in the IFS.
With my program I read the PDF from the IFS, put a appropriate header
before it and use STDOUT to send it to the consumer.

Is there a way to do this without having to store the PDF temporarily in
the IFS?

Best regards

Jan


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.