Type 7 processing messages occur because of the following types of problems:
The following table lists the messages produced by EEHF for errors that occur while processing type 7 logic. The following table also shows each message as it appears on the Run Time Messages listing.
|
Message Number |
Message |
|---|---|
|
1 |
INVALID NUMERIC DATA ENCOUNTERED IN REPORT |
|
2 |
INVALID SUBSCRIPT VALUE USED IN REPORT |
|
3 |
OVERFLOW OCCURRED DOING ARITHMETIC IN REPORT |
|
4 |
DECIMAL DIVIDE EXCEPTION IN REPORT |
|
5 |
INVALID USE OF PERFORM IN REPORT |
|
6 |
INVALID USE OF RETURN IN REPORT |
|
7 |
INVALID USE OF DB-EXIT IN REPORT |
|
8 |
PROGRAM CHECK OCCURRED DURING EXECUTION OF INPUT MODULE |
|
9 |
PROGRAM CHECK OCCURRED DURING EXECUTION OF USER PROCEDURE MODULE IN REPORT |
The messages that follow describe additional information which appear along with those messages in the table above; each of the following messages is interrelated.
Error Occurred During Processing
ERROR OCCURRED DURING PROCESSING
This message identifies the CA Culprit statement on which the error occurred. The message identifies a SORT parameter field, header line field, detail line field, or type 7 procedure statement number.
Sort Field
SORT FIELD sort-field-number
This message identifies the number of a field on a SORT parameter. CA Culprit assigns numbers starting with 1 for the first (left-most) sort field. In the following example, EEHF assigns SORT FIELD 3 to INV-DATE:
01SORT BRANCH-NUMBER 0 ACCOUNT-NUMBER INV-DATE
▲
SORT FIELD 3
Header Line
HEADER LINE header-line-number FIELD variable-field-number
This message identifies a type 4 edit parameter. In the following example, EEHF assigns HEADER LINE 2 FIELD 1 to BRANCH-NUMBER:
01410010 'BRANCH' 01420010 BRANCH-NUMBER ◄ HEADER LINE 2 FIELD 1
Detail Line
DETAIL LINE detail-line-number FIELD variable-field-number
This message identifies a type 5 edit parameter. In the following example, EEHF assigns DETAIL LINE 1 FIELD 3 to EMP-SALARY:
0151*010 EMP-NAME 0151*020 EMP-ADDRESS 0151*030 EMP-SALARY ◄ DETAIL LINE 1 FIELD 3
Procedure Statement
PROCEDURE STMT internal-sequence-number
This message identifies the sequence number of the type 7 parameter where the error occurred. In the following example, EEHF assigns PROCEDURE STMT 100 to the PERFORM instruction:
017100 PERFORM 200 ◄ PROCEDURE STMT 100 017110 SALARY + BONUS TAXABLE-SALARY
Most recent subscript value
MOST RECENT SUBSCRIPT VALUE subscript-value *INVALID*
This message identifies the value of the last subscript calculated by any report in the run. If a subscript has not been calculated, the value is 0 (zero). If the value is invalid, the literal *INVALID* appears beside the value.
Input Buffer Number
INPUT BUFFER NUMBER record-count
This message identifies the number of the input buffer processed in the run. For match-file runs, the number equals the number of sets of records that were processed. For database access runs, that were processed.
Input File Is
INPUT FILE IS file-name
This message specifies the ddname (z/OS and z/VM), file-name (z/VSE) of a file used in a match-file run. For example, EEHF identifies the file defined in the second INPUT parameter by the DD= value:
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).
Start Position Within Buffer
START POSITION WITHIN BUFFER start-position
This message identifies the start position (in bytes) of the record in the input buffer. If the input buffer does not contain a record from the identified file, the following message appears instead:
RECORD IS NOT IN BUFFER
Record Buffer Dump
RECORD BUFFER DUMP
This message precedes a hexadecimal dump of the input buffer.
Workfields at Time of Interrupt
WORKFIELDS AT TIME OF INTERRUPT
This message precedes a dump of all work fields at the time of the interrupt. CA Culprit groups the work fields as follows:
Within each category, the work fields are listed in the same order they appear in the Input Parameter Listing.
Invalid Numeric Data
The following report shows an example of the message and the record layout when invalid numeric data is encountered in a report:
mm/dd/yy RUN TIME MESSAGES volser Vnn.n PAGE 1 C350023 INVALID NUMERIC DATA ENCOUNTERED IN REPORT 01 ERROR OCCURRED DURING PROCESSING DETAIL LINE 1 FIELD 1 ◄---------- CA Culprit identifies the error occurred on a type 5 edit parameter. MOST RECENT SUBSCRIPT VALUE 0 INPUT BUFFER NUMBER 1 RECORD BUFFER DUMP ┌─► │ 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 │ │ CA Culprit prints the contents of the record that contains invalid data.
Invalid Subscript Value
The following report shows an example of the message and the record layout when an invalid subscript value is used in a report:
mm/dd/yy RUN TIME MESSAGES volser Vnn.n PAGE 1 C350026 INVALID SUBSCRIPT VALUE USED IN REPORT 01 ERROR OCCURRED DURING PROCESSING PROCEDURE STMT 1 ◄-------- CA Culprit encountered an invalid subscript while processing a type MOST RECENT SUBSCRIPT VALUE 0 *INVALID* 7 process parameter. INPUT BUFFER NUMBER 1 RECORD BUFFER DUMP 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 WORKFIELDS AT TIME OF INTERRUPT - GLOBAL NUMERIC CHAR ZONE 00000001 DIGIT 0000000C 01...5... WORKFIELDS AT TIME OF INTERRUPT - REPORT NUMERIC ◄---------- CA Culprit prints the contents of the work fields at the time CHAR < * % of the error. ZONE 00000004000000050000000600000000 DIGIT 0000000C0000000C0000000C0000000C 01...5...10....5...20....5...30.. C350034 REPORT HAS BEEN TERMINATED *********** END OF FILE ****************************************************** 1 INPUT RECORDS READ
Overflow Occurred Doing Arithmetic
The following report shows an example of the message and the record layout when an overflow occurred while doing arithmetic in a report:
mm/dd/yy RUN TIME MESSAGES volser Vnn.n PAGE 1 C350024 OVERFLOW OCCURRED DOING ARITHMETIC IN REPORT 01 ERROR OCCURRED DURING PROCESSING PROCEDURE STMT 1 MOST RECENT SUBSCRIPT VALUE 0 INPUT BUFFER NUMBER 1 RECORD BUFFER DUMP 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 WORKFIELDS AT TIME OF INTERRUPT - REPORT NUMERIC CHAR ZONE 1482470102468024681355780000001345689223 DIGIT 3503680C135791357924667C000000245678012C 01...5...10....5...20....5...30....5...40
Decimal Divide Exception
The following report shows an example of the message and the record layout when a decimal divide exception occurs in a report:
mm/dd/yy RUN TIME MESSAGES volser Vnn.n PAGE 1 C350025 DECIMAL DIVIDE EXCEPTION IN REPORT 01 ERROR OCCURRED DURING PROCESSING PROCEDURE STMT 1 MOST RECENT SUBSCRIPT VALUE 0 INPUT BUFFER NUMBER 1 RECORD BUFFER DUMP 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 WORKFIELDS AT TIME OF INTERRUPT - REPORT NUMERIC CHAR ZONE 000000130000000000000000 DIGIT 0000002C0000000C0000000C 01...5...10....5...20....
Invalid Use of Perform
The following report shows an example of the message and the record layout when an invalid use of perform is encountered in a report:
mm/dd/yy RUN TIME MESSAGES volser Vnn.n PAGE 1 C350027 INVALID USE OF PERFORM IN REPORT 01 ERROR OCCURRED DURING PROCESSING PROCEDURE STMT 3 MOST RECENT SUBSCRIPT VALUE 0 INPUT BUFFER NUMBER 1 RECORD BUFFER DUMP 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 WORKFIELDS AT TIME OF INTERRUPT - GLOBAL ALPHANUMERIC CHAR W ZONE E DIGIT 6 01 WORKFIELDS AT TIME OF INTERRUPT - REPORT NUMERIC CHAR ZONE 000000130000000000000000 DIGIT 0000002C0000000C0000000C 01...5...10....5...20.... C350034 REPORT HAS BEEN TERMINATED *********** END OF FILE ****************************************************** 1 INPUT RECORDS READ
Invalid Use of Return
The following report shows an example of the message and the record layout when an invalid use of return is encountered in a report:
mm/dd/yy RUN TIME MESSAGES volser Vnn.n PAGE 1 C350028 INVALID USE OF RETURN IN REPORT 01 ERROR OCCURRED DURING PROCESSING PROCEDURE STMT 3 MOST RECENT SUBSCRIPT VALUE 0 INPUT BUFFER NUMBER 1 RECORD BUFFER DUMP 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 WORKFIELDS AT TIME OF INTERRUPT - GLOBAL ALPHANUMERIC CHAR W ZONE E DIGIT 6 01 WORKFIELDS AT TIME OF INTERRUPT - REPORT NUMERIC CHAR ZONE 000000130000000000000000 DIGIT 0000002C0000000C0000000C 01...5...10....5...20.... C350034 REPORT HAS BEEN TERMINATED *********** END OF FILE ****************************************************** 1 INPUT RECORDS READ
Invalid Use of DB-EXIT
The following report shows an example of the message and the record layout when an invalid use of DB-EXIT is encountered in a report:
mm/dd/yy RUN TIME MESSAGES volser Vnn.n PAGE 1 INVALID USE OF DB-EXIT IN REPORT 01 ERROR OCCURRED DURING PROCESSING PROCEDURE STMT 9 MOST RECENT SUBSCRIPT VALUE 1 INPUT BUFFER NUMBER 1 RECORD BUFFER DUMP CHAR 0502126AAAAA127BBBBB 25.000 ZONE FFFFFFFCCCCCFFFCCCCC444444444444444444444444444444444444444444444444444444FF4FFF DIGIT 0502126111111272222200000000000000000000000000000000000000000000000000000025B000 01...5...10....5...20....5...30....5...40....5...50....5...60....5...70....5...80 WORKFIELDS AT TIME OF INTERRUPT - GLOBAL ALPHANUMERIC CHAR NS ZONE DE DIGIT 52 01. WORKFIELDS AT TIME OF INTERRUPT - GLOBAL NUMERIC CHAR % ZONE 0000000600000000 DIGIT 0000001C0000002C 01...5...10....5.
Program Check During Input
The following report shows an example of the message and the record layout when a program check occurred during execution of the input module:
mm/dd/yy RUN TIME MESSAGES volser Vnn.n PAGE 1 PROGRAM CHECK OCCURRED DURING EXECUTION OF INPUT MODULE MOST RECENT SUBSCRIPT VALUE 1 INPUT BUFFER NUMBER 1 RECORD BUFFER DUMP CHAR 0502126AAAAA127BBBBB 25.000 ZONE FFFFFFFCCCCCFFFCCCCC444444444444444444444444444444444444444444444444444444FF4FFF DIGIT 0502126111111272222200000000000000000000000000000000000000000000000000000025B000 01...5...10....5...20....5...30....5...40....5...50....5...60....5...70....5...80 WORKFIELDS AT TIME OF INTERRUPT - GLOBAL ALPHANUMERIC CHAR NS ZONE DE DIGIT 52 01. WORKFIELDS AT TIME OF INTERRUPT - GLOBAL NUMERIC CHAR % ZONE 0000000600000000 DIGIT 0000001C0000002C 01...5...10....5.
Program Check During User Procedure IN REPORT
The following report shows an example of the message and the record layout when a program check occurred during execution of the user procedure module in a report:
mm/dd/yy RUN TIME MESSAGES volser Vnn.n PAGE 1 PROGRAM CHECK OCCURRED DURING EXECUTION OF USER PROCEDURE MODULE IN REPORT 01 ERROR OCCURRED DURING PROCESSING PROCEDURE STMT 9 MOST RECENT SUBSCRIPT VALUE 0 INPUT BUFFER NUMBER 1 RECORD BUFFER DUMP CHAR 0502126AAAAA127BBBBB 25.000 ZONE FFFFFFFCCCCCFFFCCCCC444444444444444444444444444444444444444444444444444444FF4FFF DIGIT 0502126111111272222200000000000000000000000000000000000000000000000000000025B000 01...5...10....5...20....5...30....5...40....5...50....5...60....5...70....5...80 WORKFIELDS AT TIME OF INTERRUPT - GLOBAL ALPHANUMERIC CHAR NS ZONE DE DIGIT 52 01. WORKFIELDS AT TIME OF INTERRUPT - GLOBAL NUMERIC CHAR % ZONE 0000000600000000 DIGIT 0000001C0000002C 01...5...10....5. WORKFIELDS AT TIME OF INTERRUPT - REPORT NUMERIC CHAR ZONE 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 DIGIT 0000000C0000000C0000000C0000000C0000000C0000000C0000000C0000000C0000000C0000000C0000000C0000000C0000 01...5...10....5...20....5...30....5...40....5...50....5...60....5...70....5...80....5...90....5...00 CHAR ZONE 00000000000000000000000000000000000000000000000000000000000000000000 DIGIT 000C0000000C0000000C0000000C0000000C0000000C0000000C0000000C0000000C 101...5...10....5...20....5...30....5...40....5...50....5...60....5... ******************** DATA ERRORS IN USER PROCEDURE MODULE HAVE EXCEEDED 1 MESSAGES SUPPRESSED UNTIL END OF FILE ********************
|
Copyright © 2014 CA.
All rights reserved.
|
|