Modifying Function Parameters › Defining Function Parameters › Using Arrays as Parameters › Multiple-Instance Restrictions

Multiple-Instance Restrictions

When passing a multiple-instance array the following restrictions apply:

• Only EXCEXTFUN and EXCUSRPGM allow parameters to be passed as a multiple-instance array.
• Parameters can only be passed as a multiple-instance array when the parameter structure is defined using an array based over the *Arrays file.
• Parameters can only be passed as a multiple-instance array when they are being passed as RCD or KEY.
• No fields can be dropped on a parameter being passed as multiple-instance array.
• Do not allow a multiple-instance array parameter in a function call, either in ARR nor PAR context, except when calling an EXCEXTFUN or EXCUSRPGM, that has a multiple-instance array parameter. Additionally, the call must be from the top level action diagram of an EXCEXTFUN function.
• The Submit job (SBMJOB) feature and Y2CALL command do not support function calls that contain multiple-instance array parameters

When working with two functions, function A and function B, for example, you can model in the action diagram of function A a call to function B, where B has a parameter interface passed as an array. In this case these additional restrictions apply:

• Function A must be of type EXCEXTFUN, and function B must be of type EXCEXTFUN or EXCUSRPGM.
• The parameter context must be PAR, ARR, or PR1 through PR9 for Duplicate Parameters, and the array name must exactly match on the parameter definition of A and B.
• If a parameter is passed as a multiple-instance array on A it must be passed as an array on B.
• The multiple-instance array parameter must be passed as RCD on both A and B, or KEY on both A and B.
• Although the usages of the subfields on a parameter passed as an array can be mixed, the usages must be compatible, such that the calling function can call the called function.

  For more information, see the section Parameter Usage matrix.