FIELD SET keywords

SET ID numbers (position 1-4) for SET control cards can be 0001-0767. For single-layout formatted compares, there is only one set and all SET ID numbers are the same and all SET control cards refer to that single layout. For unformatted compares, there is only one set and all SET ID numbers are the same.

Multiple SET ID numbers are used ONLY for XREF processing. Each layout member name and layout name combination has a unique SET ID number used to group all control cards for the XREF. SET control cards must always be together and arranged in order by SET ID. However, users may assign any unique SET ID number to any layout member name/layout name combination they wish.

The XREF member names must be present on the DDxxXR/DDxxXRN JCL statement.

OLD or NEW LAYOUT MEMBER

Layout member name and layout name must be provided for both OLD and NEW when comparing XREFs. These fields are optional for single-layout compares. If provided, File-AID uses them to verify and/or search for the appropriate layout in the specified member.

If not provided for a single-layout compare, member name(s) are determined via the JCL. If unspecified for a single-layout compare, the first layout in the member is used.

FIELDnnnn

When specifying FIELD associations, specify the FIELD number (POS. 11-14 for field numbers up to 9999, POS. 11-15 for field numbers from 10000 to 32767) groups associated sub-keywords together. FIELD association keywords must be in sequence by FIELD number. Sub-keywords may be continued on subsequent cards. A sub-keyword and its value must end on the card on which it begins. For an UNFORMATTED compare, you can specify up to 50 compare fields.

For field values (name, positions, length, and data type), please see the field value information in SYNC/KEYnnn.

or

or

OLD_NAME/NEW_NAME

Name of field selected

OLD_POSITION/NEW_POSITION

Starting position of the field within the record (relative to 1) to be compared

OLD_LENGTH/NEW_LENGTH

Number of bytes in the corresponding field

EXCLUDE_POSITION

Starting position of the field within the record (relative to 1) not to be compared

EXCLUDE_LENGTH

Number of bytes in the corresponding field

EXCLUDE example:

If the LRECL of the OLD and NEW files is 100, then coding the above exclude would cause bytes 1-9 and 14-100 to be compared. Values in 10,11,12,13 would not be compared.

Guidelines

• Minimum information for specifying FIELD associations is OLD_NAME, OLD_POSITION, or EXCLUDE_POSITION. If NEW information is omitted, OLD_ information is assumed for both.
• OLD_NAME or NEW_NAME cannot be used for an UNFORMATTED compare. OLD_NAME is mutually exclusive of OLD_LENGTH and OLD_DATA_TYPE.
• NEW_NAME is mutually exclusive of NEW_LENGTH and NEW_DATA_TYPE.
• The EXCLUDE parameters cannot include any SYNC key positions.
• OLD_, NEW_ and TOLERANCE are not compatible with EXCLUDE parameters, the first processed is the dominant parameter.
• If EXCLUDE_POSITION is coded without EXCLUDE_LENGTH, then a default length value of 1 is used.
• If EXCLUDE_LENGTH is coded without EXCLUDE_POSITION, this is an error and the job will end without performing the compare
• POSITION, LENGTH, and DATA_TYPE format may be used in place of NAME for a FORMATTED COMPARE.
• TOLERANCE sub-keyword means this compare field pair is to be compared using TOLERANCE logic. TOLERANCE logic means these numeric OLD and NEW fields can be within the value specified in TOLERANCE and be considered matched.
• CASE_SENSITIVE=CONVERT is valid for Character fields only and converts the field’s data to uppercase. Use this when you want to compare without regard to case.
• The PRINT_ONLY sub-keyword means this OLD/NEW field pair are not compare fields but are printed side-by-side on the formatted compare report.
• TOLERANCE/CASE_SENSITIVE and PRINT_ONLY are mutually exclusive and may not be coded for a SYNC/KEY field.
• The LENGTH default is 1 and the DATA_TYPE default is character (C).
• To specify OLD_NAME or NEW_NAME for fields that OCCUR multiple times, see FIELD Name with Occurs.

FIELD Name with Occurs

If you specify OLD_NAME= or NEW_NAME= with a field that occurs multiple times, you must also specify OLD_POSITION= and NEW_POSITION= to select a particular occurrence of the field. If POSITION is not coded, the field name defaults to the first occurrence.