|
They may do that in the end but there are some issues. One has always
been the number of third party tools that mine the compiler listing for data.
Assuming the listing still has to fit in 132 (there has to be some
finite limit for that) then the compiler would have to line wrap and
that could present additional challenges for the miners. Not
impossible but the downside has tended to outweigh the plus.
Culling the compiler listing implies working with spool files, so the
physical limitation of printer/5250 session width don't really apply,
do they?
There is a finite limit- printer files can be created with a width of
378 columns in i 7.1. Not advocating going that wide, but there's
certainly room for expansion from 73 characters without wrapping
source lines on compiler listings.
IBM has addressed a similar issue with DDL source in 6.1, adding a
MARGINS parameter to the RUNSQLSTM command to accommodate wider SQL statements.
--
This is the RPG programming on the IBM i (AS/400 and iSeries)
(RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
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.