The idea of making any kind of last-minute change just before production makes 
my skin crawl. Even when we (rarely) install an emergency PTF, we insist on 
running the code at least on the sandbox and preferably on the development 
system before hitting production. I would call it irresponsible to move any 
object-code instance to production without at least some testing, including 
compiled COBOL. 

If I were in charge, OPT would be specified from the get-go. Likewise I would 
expect ABO code to be tested at least cursorily before jumping into prime time.

J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: Thursday, October 13, 2016 8:39 AM
Subject: (External):Re: ABO Automatic Binary Optimizer

Call me conservative after many years in this business but I say Yes. In my 
experience optimization sometimes exposes bugs that previously were masked. I 
have little experience with COBOL, but COBOL is notorious for allowing invalid 
constructs like array subscript over-cleverness.


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Thursday, October 13, 2016 7:00 AM
Subject: Re: ABO Automatic Binary Optimizer

On Thu, 13 Oct 2016 05:44:51 -0500, Bill Woodger wrote:

>Recompiling a program with no changes. Do you "regression test"? No.


So, if someone compiles their COBOL program without optimization and tests it, 
then compiles it with optimization before putting it into production, does it 
need to be tested again?

For IBM-MAIN subscribe / signoff / archive access instructions,
send email to with the message: INFO IBM-MAIN

Reply via email to