Having programmed in both environments over the years, I think you'll find the
iSeries method easier to deal with.  All you need be concerned about is the
print line content and the system takes care of spacing controls independent of
the print output line.  So, if you have a 132 column report, just define a
printer file with a record length of 132.

I hope that's clear.

Rich Loeber
Kisco Information Systems

Michael Rosinger wrote:

This is related to my other post concerning print lines greater than 132...

In the mainframe world, there is a COBOL compiler option (ADV/NOADV) which
deals with the placement of printer control characters for print lines. If
ADV is specified, the compiler adds one byte to the record length to account
for the printer control character. ADV is only meaningful if you use
WRITE...ADVANCING in the source code. If NOADV is in effect, the assumption
is that the print line has already reserved a byte for the printer control

I've searched through what I can find are the available compiler options for
COBOL/ILE and I don't see anything comparable to ADV/NOADV.

How is the printer control character handled on the iSeries? Is this
something the average iSeries COBOL program needs to be concerned with?


Michael Rosinger
Systems Programmer / DBA
Computer Credit, Inc.
640 West Fourth Street
Winston-Salem, NC  27101
m rosinger at cciws dot com

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