× 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.



Can you tell us how to reproduce this problem? You don't have to debug lp5250d for us -- just tell us how we can create the same problem on our machines.


On 4/23/2010 2:52 AM, Alberto wrote:
Hi James , thanks for your answer!
I'm sorry for the mistake, probably caused by my very BAD english and no, i
don't want that the split happens because i sometimes do some kind of
"postprocessing" of the output file and i really need to have only one file.
Means one spool file with one output file, nothing more and nothing less :-)

Looking at the spool file from the AS/400 side, dumping it with CPYSPLF
*FCFC and *PRTCTL it seems there isn't nothing special at the page where
the file get splitted.
Then i've generated a output file using Iseries Access for Windows using the
same configuration of lp5250d, and at the page where the split happens there
is no trace of the ÿ character, and the file is complete.

If i concatenate the two files i get when the problem happens, the output
pcl file is absolutely valid and usable.
So the lp5250d seems that sometimes receives some unpredictable char from
the AS/400 and closes the output file before the writer has completed the
job, then the writer still sends the remaining pages and the emulator
creates a new file.
This is what i've noticed, let me know if you need more informations and
tests.
Thanks a lot!
Ciao.
Alberto.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.