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



** Proprietary **

I will be out of the office from Monday, December 13, 2004 thru December 20, 
2004. On
Wednesday December 22, 2004 I will be returning to the office.  If you are need 
of
assistance please contact Rodelle White @ 2461 or Tom Vu @ 1346. 

Thanks 
Dorainia Bell 

>>> cobol400-l 12/20/04 09:28 >>>

Once upon a time, there was an operator, who copied a spoolfile to a 
physical file, using, CPYSPLF.  Then the original spoolfile was deleted 
and gone forever, he thought.

But, is there a way to reconstruct the spoolfile, given the PF the 
spoolfile was copied into?.  I've been thinking of creating a small pgm, 
that reads the PF, and writes to a PRTF.  I can see the control characters 
from the spoolfile.  They  are "1"(new page), "-"(I don't know), "0"(I 
don't know) and " "(blank- I don't know).

Where can I find the meaning of these control characters, or even better - 
is there a way to "reconvert" the PF back to the original PRTF? 


Mvh.

Geir Kildal
TietoEnator AS
_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.