Process Parameters › Field-name-expression

Field-name-expression

Purpose

Specifies an occurrence of a singly- or multiply-occurring field defined on a REC parameter or work field parameter.

The field can be defined as alphanumeric or numeric. The data in a numeric field can be in any numeric format; that is, binary, zoned decimal, packed signed decimal, packed unsigned decimal, or bit.

Syntax

►►──── field-name ──┬─────────────────────────┬───────────────────────────────►◄
                    ├─ .subscript-value ──────┤
                    └─ .subscript-field-name ─┘

Syntax Rules

field-name

Specifies the name of a singly- or multiply-occurring field defined on a REC or work field parameter.

subscript-value/subscript-field-name

Specifies a subscript for a multiply-occurring input or work field.

If a subscript value is provided, it must be separated from the name of the multiply-occurring field by a period (.). The value of the subscript should be an integer in the range 1 to n, where n is the number of repetitions of the multiply-occurring field.

For example, if EMPLOYEE occurs ten times, the value of the subscript should not exceed 10. The value of the subscript can be tested in procedure logic.

subscript-value

Specifies a numeric literal that identifies a specific occurrence of a multiply-occurring field; for example, EMPLOYEE.4 identifies the fourth occurrence of EMPLOYEE.

subscript-field-name

Specifies the name of a singly-occurring numeric input or work field whose value identifies a specific occurrence of a multiply-occurring field; for example, if INDX has a value of 2, then EMPLOYEE.INDX identifies the second occurrence of EMPLOYEE.

The subscript field definition must not specify a decimal point.

Usage

The following CA Culprit reserved words can replace field-name-expression in procedure logic:

• M*ID applies exclusively to match-file runs and can be specified in type 7 procedure logic only. M*ID is used in procedure logic to test the status of input files in a match-file run.

  In a match-file run, CA Culprit creates a 1-byte binary field for each file; the field is called a file-specific status byte. M*ID is a binary combination of the file-specific status bytes for all files in a match run. This field can be tested for values that reflect various conditions, as listed in the following table.

Note: For more information on match-file runs, see the CA Culprit for CA IDMS User Guide.

• LEVL refers to the current level of a control break coded on a SORT parameter. It can be specified in type 8 procedure logic only.

  LEVL is used to test for a specific control break; if the test is true, CA Culprit executes procedure logic specified for the control break.

  LEVL can be equated to values in the range 1 through 21. For the most minor control break, LEVL equals 1; at grand totals time, LEVL equals one more than the number of control break codes specified on the SORT parameter.

More information:

Output Definition Parameters