PH65931: ADDI API CALL EXTENSIBILITY DOESN'T CORRECTLY RESOLVE A CALLED PROGRAM IF SPECIFIED AS A STRING IN A CALL STATEMENT

APAR status

• Closed as fixed if next.

Error description

• The Application Discovery API Call Extensibility does not
  correctly resolve the CALL statement when the called program is
  specified as a string within the statement.
  
  The following CALL statement calls YYYY whereas we expect it to
  reference XXXX instead via the API Call Extensibility feature.
  In this case, the paramete for the CALL statement is directly
  defined as the string 'XXXX'.
    WORKING-STORAGE SECTION.
     77 WKPLIST PIC X(10).
     01 CVCHEX0 PIC X(10).
     01 AIATOP  PIC X(10).
  	01 XXVAR    PIC X(08).
    PROCEDURE DIVISION.
  
  
   * API resolution does not work
     CALL 'YYYY' USING WKPLIST
  
   BY REFERENCE CVCHEX0
  
   BY CONTENT   'XXXX'
  
   BY REFERENCE AIATOP
  	END-CALL.
  

Local fix

• By adding "MOVE 'XXXX' TO XXVAR." to assign 'XXXX' to a
  variable, it is recognized as an argument by the API
  Extensiblity feature and links correctly with XXXX.
   * API resolution works
     MOVE 'XXXX' TO XXVAR.
     CALL 'YYYY' USING WKPLIST
       BY REFERENCE CVCHEX0
       BY CONTENT   XXVAR
  
   BY REFERENCE AIATOP
  	END-CALL.
  

Problem summary

• Only a parameter was saved because having the same parameter
  both as a variable or a string for the same API call is not a
  supported use case.
  

Problem conclusion

• The support for this scenario has been added and will be
  available in ADDI 6.1.3. iFix2
  

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

Applicable component levels