The control characters in the first byte of each record in a spool file use
the ANSI Carriage Control standard. Here's an article that explains the
meanings of the various values:
http://www.outputlinks.com/content/al_cooper/display.cfm?id=4274

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Greg Garner
Sent: Monday, December 20, 2004 8:35 AM
To: COBOL Programming on the iSeries/AS400
Subject: RE: [COBOL400-L] Control characters in spool files


override the print file "QPRINT" specifying control character "*FCFC" and
override to the desired output queue...

Gregory A. Garner
Garner Data Systems, Inc.
4270 Grand Teton Parkway
Suwanee, GA 30024
Phone: 770 845 9636
Fax:   770 614 3496



-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx]On Behalf Of
geir.kildal@xxxxxxxxxxxxxxx
Sent: Monday, December 20, 2004 9:28 AM
To: COBOL Programming on the iSeries/AS400
Subject: [COBOL400-L] Control characters in spoolfiles


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


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

This mailing list archive is Copyright 1997-2026 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.