----- Message from "Stone, Joel" <Joel.Stone@xxxxxxxxxx> on Thu, 19G.
Jan 2017 15:55:13 +0000 -----
"COBOL Programming on the IBM i (AS/400 and iSeries)" <cobol400-
Re: [COBOL400-L] Any simple method of ignoring "Display" commands in
a Cobol pgm?
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!
From: COBOL400-L [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sent: Wednesday, January 18, 2017 10:05 PMcommandseems to
To: COBOL Programming on the IBM i (AS/400 and iSeries) <cobol400-
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
notsignificantly slow down the execution of a large batch run.
I will resolve by conditioning the DISPLAY statements (IF...END-IF) to
themexecute during a prod run, that will be doable. But there are 100+ of
7 sofor whatever reason???
What about conditioning all those DISPLAY statements with a D in column
that they get executed only when in COBOL debug mode (see STRCBLDBG)?
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.