Our PL/1 program (non CICS) which works fine when BAQSTUB is statically linked in, abends when using dynamic linking.
CEE3204S The system detected a protection exception (System Completion Code=0C4).
From compile unit //'ZOSCONN.B.R300.UI69481.BAQSRCL(BAQWEBT)' at entry point getVerboseOptions at statement 3516 at compile unit offset +000000AE at entry offset +000000AE at address 23E62A46.
The getVerboseOptions seems to me something internal in BAQSTUB.
Cobol dynamic linking works fine.
Source parts:
DCL BAQCSTUB EXTERNAL ENTRY OPTIONS(NODESCRIPTOR);
FETCH BAQCSTUB;
Remainder is identical to the static version
Linkedit:
//SYSLIN DD *
INCLUDE SYSLIB(EXPLCBA)
NAME EXPLCBA(R)
we run on z/OS Connect 03.00.35
When transmitting the load to another LPAR with z/OS Connect 03.00.31, I get similar but slightly different dump
CEE3204S The system detected a protection exception (System Completion Code=0C4).
From compile unit //'ZOSCONN.B.R300.UI70538.BAQSRCL(BAQWEBT)' at entry point BAQCSTUB at statement 509 at compile unit offset +000019A2 at entry offset +000019A2 at address 1AE7F35A.
Bot LPARS have 20200710111738020101 in SYS1.CEE300.SBAQLIB(BAQCSTUB)
Any idea ?
------------------------------
Bart Pastoor
------------------------------