Hello Stan,
I am one of Bernie's co-workers. Could you check if AMODE3164 is specified in the IGZOPTS DD as follows in your execution JCL?
//IGZOPTS DD *
AMODE3164
/*
COBOL runtime option AMODE3164
By the way, the Bernie's suggestion, ...If you run with LE option RPTOPTS(ON), does AMODE3164 show up in the COBOL options section after the usual LE options? .... , might not work yet in the z/OS 3.1 Beta but it should not affect AMODE3164.
------------------------------
Roy Bae
------------------------------
Original Message:
Sent: Thu August 24, 2023 06:45 AM
From: Bernie Rataj
Subject: COBOL V6R4 running on a Z16 + z/OS V3R1 Beta - I have found a possible issue with ILC between COBOL V6R4, C/C++ and HLASM. Programs run successfully under z/OS 2.5
Hi Stan,
The COBOL runtime option AMODE3164 is required under z/OS 2.5, so it's not clear why you needed to add it under z/OS 3.1 if you are indeed running the same scenario?
If you run with LE option RPTOPTS(ON), does AMODE3164 show up in the COBOL options section after the usual LE options?
Bernie
COBOL runtime option AMODE3164
------------------------------
Bernie Rataj
Technical Support Professional
IBM Canada Ltd.
Markham ON Canada
https://www.ibm.com/products/cobol-compiler-zos
https://www.ibm.com/products/pli-compiler-zos
Original Message:
Sent: Wed August 23, 2023 08:54 AM
From: Stan Abramczyk
Subject: COBOL V6R4 running on a Z16 + z/OS V3R1 Beta - I have found a possible issue with ILC between COBOL V6R4, C/C++ and HLASM. Programs run successfully under z/OS 2.5
COBOL V6R4 Inter-Language Communications (ILC) program calls C/C++, COBOL and HLASM.
Working without any incidents under z/OS V2R5.
But with z/OS V3R1 the program call to the COBOL AMode (64) from the ILC COBOL program (Amode(31) fails with a 4038 abend
LE COND CODE=IGZ0383S / EXPECTED COMP CODE=U4038
CEEDUMP: It displays a message to use the runtime option AMODE3164, I added the runtime option same result 4038 abend
------------------------------
Stan Abramczyk
------------------------------