A hugely frustrating corollary is that even if you conclude that changing x to y caused the problem, changing y back to x does not necessarily fix it. ;-)
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Charles Mills Sent: Tuesday, February 07, 2017 11:44 AM To: [email protected] Subject: (External):Re: Program now working, but why? One important lesson of life in computer programming is that "it worked when I changed 'x' to 'y'" does not mean that 'x' is the problem and 'y' is the solution. Some aspect of your development compile (lack of optimization?) or test environment may be masking the real problem. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Ten Eyck Sent: Tuesday, February 07, 2017 11:33 AM To: [email protected] Subject: Re: Program now working, but why? The production assembler program is AM 24 and RM 24. The production COBOL program is AM 24 and RM 24. (runs, calls assembler program) The development COBOL program is AM ANY and RM 24. (does not run (SOC4 in assembler program), does run with mentioned coding change, calls assembler program) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
