What are the details of the 0C4 in the assembler program: - what was it trying to access? - was it a read or a write?
Lou -- Artificial Intelligence is no match for Natural Stupidity - Unknown On Wed, Feb 8, 2017 at 9:26 AM, Peter Ten Eyck < peter.tene...@americannational.com> wrote: > Job TNCA1300 runs three times on the same LPAR with the same data and id. > > Run 1 – production COBOL program, calls production assembler program, runs > successfully. > > Bring production COBOL program into a development PDS and compile program > without changes. > > Run 2- development program, calls production assembler program, fails with > SOC4 in assembler program. > > Add these two lines of code to COBOL program to bypass header record on > input dataset: > > IF WS-NA-RECORDS-READ EQUAL 1 > GO TO 1200-READ-MASTER. > > Compile COBOL program with change. Compile output messages identical to > first compile. > > Run 3 – development COBOL program (changed), calls production assembler > program, runs successfully. > > Note: No overrides or changes to AMODE, RMODE or DATA during the test. > Using the shops default compile and link settings. > > Program moves from the FD to WORKING-STORAGE before the call to the > assembler program for all “input” parameters. > > I am missing something here; I do not see why this code would resolve the > SOC4. Or has mentioned, missing something else… the unknown unknowns > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
