Previous Topic: Type 7 MessagesNext Topic: Selection Messages

Extended Error Handling Facility › About the Extended Error Handling Facility › Input Phase Errors › Match-file Messages

Match-file Messages

Match-file messages occur because of the following type of errors:

The following table lists the messages produced by EEHF for errors that occur while processing match-files. The following table shows each message as it appears on the Run Time Messages listing.

Message Number

Message

10

AN OUT OF SEQUENCE CONDITION HAS ARISEN

11

INVALID NUMERIC DATA IN A MATCH KEY FIELD

The messages that follow describe additional information that appears along with the messages in the table above:

Input File Is

INPUT FILE IS file-name

This message identifies the ddname (z/OS and z/VM), file-name (z/VSE) of the file in which the incorrect sequence occurred. For example, EEHF identifies the file defined in the second INPUT parameter as INPUT FILE IS SYS011:

INPUT 80 F 400 DD=SYS010
 -
INPUT 80 F 400 DD=SYS011  ◄ INPUT FILE IS SYS011

Record Number Is

RECORD NUMBER IS record-number

This message identifies the record in the input buffer at the time of the interrupt. The record number is the number of the record in the input file. If no record is in the input buffer, the record number is 0 (zero).

Key Position Is

KEY POSITION IS key-field-position

This message specifies the start position of the match-key field in the input file.

Key Data Type Is

KEY DATA TYPE IS data-type-code data-type-literal

This message specifies the number of the data type defined for the match-key field on the REC parameter and the literal to which the data type number corresponds:

Data Type Code

Data Type Literal

0

ALPHANUMERIC

1

BINARY

2

ZONED DECIMAL

3

SIGNED PACKED DECIMAL

4

UNSIGNED PACKED DECIMAL

5

BIT

Key Length Is

KEY LENGTH IS key-field-length

This message identifies the number of bytes defined for the match-key field on the REC parameter.

After either of these match-file messages, EEHF produces a hexadecimal dump of the contents of the input buffer for the identified file.

Note: The system reads ahead to detect invalid or out-of-sequence match keys. While one record is in the input buffer, the system reads the next record, checking for errors. If an error is detected, the error is reported before the input buffer is processed. Therefore, a match-file error for record 3 can appear in the Run Time Messages listing before a non-match-file error for record 2. Other errors for record 3 can be reported after it is processed.

Out of Sequence Condition

The following report shows an example of the message and the record layout when an out of sequence condition has arisen:

mm/dd/yy                  RUN TIME MESSAGES               volser Vnn.n  PAGE     4


   C350058 AN OUT OF SEQUENCE CONDITION HAS ARISEN
   INPUT FILE IS  SYS010
   RECORD NUMBER IS          3  ◄------------ Third record in file SYS010

   KEY POSITION IS       1
   KEY DATA TYPE IS  2  DECIMAL  ◄------------ Information about the match-key field
   KEY LENGTH IS    4

                CHAR   035EMARK      TIME           44 CLOCK ST         MALDEN         MA01776617555191I0103456012H0E0E8A0
                ZONE   FFFCDCDD444444ECDC44444444444FF4CDDCD4EE444444444DCDCCD444444444DCFFFFFFFFFFFFFFCFFFFFFFFFFCFCFCFCFC
                DIGIT  0355419200000039450000000000044033632023000000000413455000000000410177661755519190103456012805058100
                      01...5...10....5...20....5...30....5...40....5...50....5...60....5...70....5...80....5...90....5...00

                CHAR   0 0 0C0I5H520 MAIL ROOM                   ?@  D       ?   1   Z8  ?                    H   G
                ZONE   FCFCFCFCFCFFFCDCCD4DDDD44444444440B140B1006770CE40B3006850F170EF006900000800080340A3000C000C0009022E
                DIGIT  0000030958520041930966400000000004D684B005FC844084EA05F88418849805F4000B00006B0E91460008000700100330
                     101...5...10....5...20....5...30....5...40....5...50....5...60....5...70....5...80....5...90....5...00

Invalid Numeric Data Used

The following report shows an example of the message and the record layout when invalid numeric data is used in a match key field:

mm/dd/yy                    RUN TIME MESSAGES    volser Vnn.n  PAGE     1


   C350051 INVALID NUMERIC DATA IN MATCH KEY FIELD
   INPUT FILE IS  SYS010
   RECORD NUMBER IS          1

   KEY POSITION IS       1
   KEY DATA TYPE IS  2  DECIMAL
   KEY LENGTH IS    4

                CHAR   %%%%TERRY     JANSEN         SESE-SEKO           EASTON         MA05491617773839H1202910166F1A0B7I0
                ZONE   6666ECDDE44444DCDECD444444444ECEC6ECDD44444444444CCEEDD444444444DCFFFFFFFFFFFFFFCFFFFFFFFFFCFCFCFCFC
                DIGIT  CCCC359980000011525500000000025250252600000000000512365000000000410549161777383981202910166611027900
                      01...5...10....5...20....5...30....5...40....5...50....5...60....5...70....5...80....5...90....5...00

                CHAR   0 0 0C0D4E520 MAIL ROOM                   ?@  D       ?   1   Z8  ?               ?    H   G       &
                ZONE   FCFCFCFCFCFFFCDCCD4DDDD44444444440B140B1006770CE40B3006850F170EF00690000080008030060000C000C00090225
                DIGIT  0000030445520041930966400000000004D684B005FC844084EA05F88418849805F4000B00006B0E05F40008000700100320
                     101...5...10....5...20....5...30....5...40....5...50....5...60....5...70....5...80....5...90....5...00