Hi Leonardo,
The PARMCHECK option doesn't check individual parameters. It helps address the common issue where the callee (subprogram) has a longer definition of a structure passed as a parameter than the caller does, and updates that structure, leading to an overlay which can extend past the end of working-storage, where it could damage some other data area. See the manual entry for more information.
PARMCHECK doesn't apply to CICS (DFHEI1) calls though.
Bernie
https://www.ibm.com/docs/en/cobol-zos/6.3?topic=options-parmcheckThe
PARMCHECK option tells the compiler to generate an extra data item following the last item in
WORKING-STORAGE. This buffer data item is then used at run time to check whether a called subprogram corrupted data beyond the end of
WORKING-STORAGE.
------------------------------
Bernie Rataj
Senior Software Developer
IBM Canada Ltd.
Markham ON Canada
https://www.ibm.com/marketplace/ibm-compilers------------------------------
Original Message:
Sent: Tue April 26, 2022 03:38 PM
From: Leonardo Zrycki
Subject: COBOL 6.3 - Compiler option PARMCHECK(ABD/MSG) using CICS LINK / XCTL
Hi people,
I started testing the PARMCHECK compiler option compiling a pair of programs MAIN and SUBPROG.
My question: what about CICS and EXEC CICS LINK / XCTL : PARMCHECK doesn't detect in runtime the diferrence between Commareas.
I searched the documentation but I didn't found nothing about if PARMCHECK detects this difference of lengths.
Do you have some information about this topic?
Thanks in advance
Leonardo
------------------------------
Leonardo Zrycki
------------------------------