Is the assembler routine LE Compliant of Compatible? Does it use the CEE macros to establish the LE environment?
When was it last assembled? What does the summary dump look like? Is it S0C4-04? Is it an authorized program running in an unauthorized library? So many questions. The dump should tell you why the S0C4 occurred. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Peter Ten Eyck > Sent: Tuesday, February 07, 2017 11:45 AM > To: [email protected] > Subject: Program now working, but why? > > 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
