×
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.
Wow that's an excellent idea!!
The IF/END-IF aren't so bad by themselves, but placed into already deeply nested condition statements, READ INVALID KEY statements, EVALUATEs, etc, that will make it a lot easier to maintain and read.
Also it will be far less likely that I will introduce my own bugs.
Thanks for the tip!
Joel
-----Original Message-----
From: COBOL400-L [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of G.
Sent: Wednesday, January 18, 2017 10:05 PM
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?
On Wed, 18 Jan 2017 20:54:59 +0000, you wrote:
The only reason I wanted to do this is because the DISPLAY command seems to
significantly slow down the execution of a large batch run.
I will resolve by conditioning the DISPLAY statements (IF...END-IF) to not
execute during a prod run, that will be doable. But there are 100+ of them
for whatever reason???
What about conditioning all those DISPLAY statements with a D in column 7 so
that they get executed only when in COBOL debug mode (see STRCBLDBG)?
It should be easier to do, maybe even automatically with a small program
that reads the source and adds a D in column 7 whenever it encounters a
DISPLAY statement (provided it is the only statement in the line), and a D
in that column does not add all the clutter an IF...END-IF pair would do.
HTH,
G.
midrange.com
