PI70248: Developer for z Systems (RDz) COBOL SCAN FOR COMPATILITY RESULTSIN CRRZI0788E PROGA IS USING 3 PARMS BUT PROGB EXPECTS 4 PARMS.
Fixes are available
Rational Developer for System z Fix Pack 3 (184.108.40.206) for 9.5.1.
Rational Developer for System z Fix Pack 4 (220.127.116.11) for 9.5.1.
Rational Developer for System z Fix Pack 5 (18.104.22.168) for 9.5.1.
Rational Developer for System z Fix Pack 5 (22.214.171.124) for 9.5.1.
Rational Developer for z Systems Fix Pack 7 (126.96.36.199) for 9.5.1.
Rational Developer for z Systems Fix Pack 8 (188.8.131.52) for 9.5.1.
Rational Developer for z Systems Fix Pack 9 (184.108.40.206) for 9.5.1.
Closed as program error.
IBM Rational Developer for z Systems (RDz) If you attempt to use the COBOL Scan for compatibility for two COBOL programs you may receive an incompatibility even though one does not exist. You may see an error such as: "CRRZI0788E PROGA is using 3 parms but PROGB expects 4 parms." Or, you may get a message such as: "CRRZI0791E PROGA is incompatible with PROGB; Parameter 2 has a size of 1601 but MUXRE is expecting a size 0."" In this case, PROGA contains the following in the LINKAGE SECTION: 01 RCV-STRUC. COPY TEST1. And with a PROCEDURE statement such as: PROCEDURE DIVISION USING RCV-GRP RCV-STRUC RELEASE-DATES. The COBOL parser will flag an error for the procedure statement stating, "Ambiguous reference to RCV-STRUC". The RCV-STRUC is defined in the copybook TEST1.
Remove from the Linkage Section the line: 01 RCV-STRUC.
The COBOL Scan for compatibility can incorrectly report errors in a couple cases. First, it can get the number of expected parameters wrong. Second it can miscalculate an expected parameter size when data from a copybook is needed to determine that number, particularly if the member to scan had not been opened in an editor before.
The scan was getting the wrong number of parameters because it was not properly reading the linkage section. The wrong expected parameter size came about because the scanner failed to determine the SYSLIB as a result of not finding the associated property group; a session object mapping the local temp file with the remote member is needed for this but it was not set if the editor had not be opened before. The problem listed in this APAR has been resolved with IBM Rational Developer for z Systems V220.127.116.11 Fix Pack which is available from the Recommended Fixes support download page: http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
Reported component name
EXP FOR Z/OS CL
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
RATL DEV FOR SY
Fixed component ID
Applicable component levels