>>> The programmer added code to bypass the header record on the first file read, now it runs at the development level.
You may want to check this out http://www-01.ibm.com/support/docview.wss?uid=swg21242182 Kolusu IBM Mainframe Discussion List <[email protected]> wrote on 02/07/2017 11:45:05 AM: > From: Peter Ten Eyck <[email protected]> > To: [email protected] > Date: 02/07/2017 11:45 AM > Subject: Program now working, but why? > Sent by: IBM Mainframe Discussion List <[email protected]> > > We have an OS/VS COBOL program that calls an assembler program that > runs fine in production (z/OS 2.2). > > We brought down the COBOL program to development and compiled the > program using Enterprise COBOL 4.2. The compile output and link > output look good, no concerning messages. I ran an AMBLIST on both > the production and the newly created development load modules and > they are identical in the "M O D U L E S U M M A R Y" report. > > The program gets a SOC4 (in the called assembler program) when run > at the development level and runs fine at the production level, the > only change is the compile. > > The programmer added code to bypass the header record on the first > file read, now it runs at the development level. > > Scratching my head why... did not see anything in the migration > guide that explained it to me. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
