×
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.
Joel,
I can relate. I work with some people who resist ILE and RDi. I've learned
to "go with the flow", too. After all, it's only computer stuff. It's not
really religion--even if some treat it as such (like I used to).
Your coworker should at least be willing to go with the D in the indicator
area and the "with debugging" clause on the source-computer paragraph.
He'll just have to remember to do the STRCBLDBG before he runs it to have
the DISPLAY statements active. If he needs convincing, you should be able
to show him difference in run times with and without the DISPLAY
statements being executed. It's hard to argue with hard numbers.
If nothing else, it was refreshing to see a little activity on this
mailing list.
Michael Quigley
Computer Services
The Way International
www.TheWay.org
"COBOL400-L" <cobol400-l-bounces@xxxxxxxxxxxx> wrote on 01/21/2017
01:00:03 PM:
----- Message from "Stone, Joel" <Joel.Stone@xxxxxxxxxx> on Fri, 20
Jan 2017 18:04:29 +0000 -----
To:
"'COBOL Programming on the IBM i (AS/400 and iSeries)'" <cobol400-
l@xxxxxxxxxxxx>
Subject:
Re: [COBOL400-L] Any simple method of ignoring "Display" commands in
a Cobol pgm?
Yes I agree the dozens of DISPLAY commands in a production program
is over the top.
However the guy who wrote the pgm is still working here, and he
still uses them, and he hasn't removed them, so I didn't feel that
it was my place.
Hes an old-schooler, still only uses PDM and OPM-only Cobol (never
ILE) so I find it much easier to "go with the flow" :)
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.