Reporting Facility Rules for Coding › User-Defined Field Names › Field Types › Array

Array

An array is a scalar variable that occurs multiple times, in contiguous locations, within the GSA or the input record area. Arrays can be defined to the Reporting Facility only by the DEFINE command.

The same restrictions and attribute options apply to arrays as to scalar variables. However, when an array element is referenced in a procedural statement, you must supply an INDEX value to indicate which occurrence of the array is being referenced. Code an array element reference in the following format:

►►─ fieldname(indexval) ──────────────────────────────────────────────────────►◄

fieldname

Specifies the symbolic name assigned to the array.

indexval

Specifies the element within the array that is to be referenced. You can code it as either:

• an absolute index specification that specifies the element within the array to be referenced
• a relative index specification that contains the index value to identify the specific element within the array to be referenced

Note the following:

• The Reporting Facility supports only single dimensional arrays. The system flags as an error any condition encountered that would require multiple levels of indexing.
• If an array element is fully or partially redefined, the new field is also considered an array and you must index it when it is referenced.
• You can redefine and specify a scalar variable as an array however, the entire calculated length of the array must not exceed the original dimensions of the scalar variable.
• Most of the Reporting Facility commands support indexing an array element, but each command can impose its own special requirements or limitations.
• When you refer to an array element using an absolute index specification, the array element is treated internally as though it were simply a scalar variable.

  When you use a relative index specification, however, the Reporting Facility calculates the address of the desired element each time it is referenced during execution. This can cause the entire array to be written to the internal Hit File and overuse your resources. The Hit File is the file where the Reporting Facility temporarily stores the report as it selects records.