I think I'm onto something:
The Assembler module establishes a VSAM ACB and buffer space for VSAM and establishes a VSAM Journal exit.
THe Assembler module calls the COBOL module that loads into it's own LE Enclave.
The COBOL module opens it own VSAM ACB (OK, it does know any better).
THe COBOL program does a read key on the VSAM file.
This drives the exit which accesses the ACB in the Assembler enclave which hasn't been used.... S0C4?
LE is intercepting my dumps.
- dick scherrer
- Global moderator
- Posts: 6268
- Joined: Sat Jun 09, 2007 8:58 am
Re: LE is intercepting my dumps.
Yup, quite possibly. . .
Depending on the specifics, you might consider a COBOL module that identifies the VSAM file, then calls the assembler code which later calls the problem COBOL code.
Depending on the specifics, you might consider a COBOL module that identifies the VSAM file, then calls the assembler code which later calls the problem COBOL code.
Hope this helps,
d.sch.
d.sch.
-
- Posts: 41
- Joined: Fri Oct 01, 2010 9:43 pm
- Skillset: Assembler, COBOL, CICS, DB2, Pl/I, JCL and tableBASE
- Referer: google search
Re: LE is intercepting my dumps.
Can't I force the COBOL module into the same enclave as the Assembler module by using a CEEENTRY macro to establish the LE Environment?