PI70248: Developer for z Systems (RDz) COBOL SCAN FOR COMPATILITY RESULTSIN CRRZI0788E PROGA IS USING 3 PARMS BUT PROGB EXPECTS 4 PARMS.

Rational Developer for System z Fix Pack 3 (9.5.1.1) for 9.5.1.
Rational Developer for System z Fix Pack 4 (9.5.1.4) for 9.5.1.
Rational Developer for System z Fix Pack 5 (9.5.1.5) for 9.5.1.
Rational Developer for System z Fix Pack 5 (9.5.1.6) for 9.5.1.
Rational Developer for z Systems Fix Pack 7 (9.5.1.7) for 9.5.1.
Rational Developer for z Systems Fix Pack 8 (9.5.1.8) for 9.5.1.
Rational Developer for z Systems Fix Pack 9 (9.5.1.9) for 9.5.1.
Rational Developer for z Systems Fix Pack 10 (9.5.1.10) for 9.5.1.
Rational Developer for z Systems Fix Pack 11 (9.5.1.11) for 9.5.1.
Rational Developer for z Systems Fix Pack 12 (9.5.1.12) for 9.5.1.

APAR status

• Closed as program error.

Error description

• 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.
  

Local fix

• Remove from the Linkage Section the line:
  01 RCV-STRUC.
  

Problem summary

• 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.
  

Problem conclusion

• 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 V9.5.1.3 Fix Pack which
  is available from the Recommended Fixes support download page:
  http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATL DEV FOR SY

• Fixed component ID

  5724T0700

Applicable component levels

• R951 PSY

     UP