Previous Topic: Range 300 MessagesNext Topic: Range 400 Messages


Range 350 Messages

Message ID

Message

C350002

ISAM READ - BLOCK COULD NOT BE REACHED

z/OS users only—The user requested ISAM file access, but the operating system encountered an unrecoverable error either while searching for the indexes or while following an overflow chain. To evaluate this error, examine the file.

Severity: F

Modules: CULLISAM

C350003

ISAM READ - CULPRIT SYSTEM ERROR

z/OS users only—The user submitted an ISAM file, but a faulty calling sequence exists between CA Culprit and the input module. Obtain a dump and contact CA Technical Support.

Severity: F

Modules: CULLISAM

C350004

SORT CONTROL MODEL STATEMENTS INVALID

(CONT) EXECUTION UNLIKELY. FILES CLOSED.

The module CULLSRTC either was modified incorrectly or could not be located by CA Culprit. Consult the software support staff at your installation.

Severity: F

Modules: CULLEXT

C350006

UNSPECIFIED SORT CONTROL PARAMETER field-description

(CONT) PROCESSING CONTINUES.

The parameter field &&n that was identified by field-description is missing in the CULLSRTC module. Unless a nonstandard sort package is used, this error will cause the subsequent sort to fail. If the sort fails, consult the software support staff at your installation.

Severity: W

Modules: CULLEXT

C350008

DUPLICATED SORT CONTROL PARAMETER field-description

The specified parameter field is invalid in the CULLSRTC module. This error will cause the subsequent sort to fail unless a nonstandard sort package is used. If the sort fails, contact the software support staff at your installation.

Severity: W

Modules: CULLEXT

C350009

EXTRACT RECORD LENGTH EXCEEDS BLOCKSIZE FOR ddname/file-name

z/VSE users only—The record length of the extract phase (that is, CULL step) extracted-items file exceeds the block size that was defined for that file in the system profile program (that is, CULPPROF). To correct this error, reassemble CULPPROF to increase the limit, or reduce the number of fields on the edit lines. For more information on reassembling CULPPROF, refer to the CA CULPRIT for CA IDMS Reference Guide.

Severity: F

Modules: CULLEXT

C350010

LOGIC ERROR. DCBLRECL EXCEEDED BY CULL

(CONT) CONTACT CA SUPPORT

z/OS users only—The record length of the extracted-items and statistics file exceeds the LRECL value specified in the SYS006 or SYS008 DD statement. CA Culprit abends with a return code of 101. To correct this error, modify the JCL as follows:

  • If a sort is performed on the extracted data, round up the LRECL round up to the nearest multiple of 4 the LRECL LRECL that is associated with SYS006.
  • If no sort is performed on the extracted data, round up to the nearest multiple of 4 both the LRECL that is associated with SYS006 and the LRECL that is associated with SYS008.

Severity: F

Modules: CULLEXT

C350012

NOSORT DATASET IS A NULLFILE

z/OS users only—The unsorted extracted-items file (that is, SYS008) was defined as a dummy file in the JCL, but one or more reports either specified the NOSORT option on the SORT parameter or did not include a SORT parameter. If any report in a CA Culprit run does not sort the extracted items, assign a temporary data set to SYS008.

Severity: F

Modules: CULLEXT

C350013

DCBLRECL DIFFERS FROM SPECIFIED RECORD SIZE FOR file-name

(CONT) DCBLRECL = dcblrecl

(CONT) SPECIFIED RECORD SIZE = record-size

CONT) SHORTER LENGTH USED

z/OS users only—A record was input that is either longer or shorter than the record size specified on the INPUT parameter. If the record is longer, the record is truncated; otherwise, the record is moved into the buffer and the contents of the remainder of the buffer remain unchanged.

Severity: W

Modules: CULLSEQ

C350017

VSAM SYNAD synad-error-text

(CONT) FILE CLOSED DUE TO I/O ERROR

A physical I/O error occurred on the VSAM input file. The system provides the portion of the SYNAD error message that can be printed and closes the file. For more information on handling I/O errors, consult the appropriate VSAM documentation for your installation.

Severity: F

Modules: CULLVSIN

C350018

LOGIC ERROR ON VSAM READ

(CONT) FILE CLOSED DUE TO I/O ERROR

A GET instruction for a VSAM input file resulted in an I/O error. Due to the error, the VSAM input file is closed.

Severity: F

Modules: CULLVSIN

C350020

UNABLE TO OPEN INPUT FILE.GENCB OR MODCB FAILURE

A nonzero return code was returned by VSAM for a GENCB macro or MODCB macro requesting an EXLIST, ACB, or RPL block. For VSE/ESA users, the probable cause of this error is insufficient virtual storage to process the request. Resubmit the job with a smaller SIZE parameter on the EXEC card for the extract phase (that is, CULL step).

Severity: F

Modules: CULLVSIN

C350021

I/O ERROR ON OPEN

CA Culprit returned a nonzero return code from a request to open a VSAM input file.

Severity: F

Modules: CULLVSIN

C350022

UNABLE TO CLOSE VSAM INPUT FILE

A nonzero return code was returned to Register 15 by VSAM close-file processing. Check the JCL for errors and resubmit the job.

Severity: F

Modules: CULLVSIN

C350023

INVALID NUMERIC DATA ENCOUNTERED IN REPORT report-number

A data exception occurred in an arithmetic or edit operation for the indicated report. CA Culprit treats the invalid field as though its value were 0 (zero) and continues to process the report. This message can occur because:

  • The field does not contain the type of data that was specified on the REC parameter
  • The result of a multiplication operation contains more than 30 digits

For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350024

OVERFLOW OCCURRED DOING ARITHMETIC IN REPORT report-number

The system encountered an overflow condition during an add, subtract, or multiplication operation for the indicated record. The result of the operation (after a possible shift for decimal alignment) contains too many digits to fit in the result field. CA Culprit ignores the overflow (that is, high-order digits are lost) and processing continues. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350025

DECIMAL DIVIDE EXCEPTION IN REPORT report-number

A divide exception occurred in a division operation in a type 7 or type 8 procedure statement. The quotient is set to 0 (zero). This error can occur in a type 7 or type 8 procedure statement, as follows:

  • Type 7 procedure statement— If the error occurred in a type 7 statement, the error message appears as part of an extended error-handling message.
  • Type 8 procedure statement— If the error occurred in a type 8 statement, the error message appears on the body of the report at the place where the error occurred.

A divide exception can occur during a division operation if any of the following conditions apply:

  • The divisor is 0 (zero).
  • The divisor contains more than 15 significant digits.
  • The dividend contains more than 30 digits; this can occur after decimal place adjustment.
  • The quotient contains more than 15 significant integer digits, but the result is an 8-byte work field.

For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350026

INVALID SUBSCRIPT VALUE USED IN REPORT report-number

An invalid subscript value was encountered in the indicated report; the value is either 0 (zero) or negative, or it caused CA Culprit to search beyond the area known to contain all occurrences of the fields being referenced. Processing cannot continue. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350027

INVALID USE OF PERFORM IN REPORT

The system encountered nested PERFORM statements in the type 7 input procedure code for the indicated report. The report terminates. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350028

INVALID USE OF RETURN IN REPORT report-number

A RETURN statement was encountered in type 7 input procedure code at execution time, but the chapter of code that contains the RETURN statement was not reached with a PERFORM statement. Processing cannot continue. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350029

INVALID USE OF DB-EXIT IN REPORT report-number

The user invoked a DB-EXIT call, but the input module does not support the DB-EXIT facility. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350032

DATA ERRORS IN USER PROCEDURE MODULE HAVE EXCEEDED error-limit

The number of data errors that were encountered exceeds the default or user-supplied limit for nonnumeric data errors in user procedure modules. Further errors of this type will not be reported; appropriate error-recovery action will be taken. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350033

NUMBER OF EXTRACT DATA ERRORS HAS EXCEEDED error-limit

The default or user-specified error limit for numeric data errors in type 7 input procedure code, in the processing of sort fields (and/or fields on type 4 or type 5 edit parameters), was exceeded. Further errors of this type will not be reported; appropriate error-recovery action will be taken. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350034

REPORT HAS BEEN TERMINATED

Because of the errors reported by previous error messages, processing for the report cannot continue.

Severity: F

Modules: CULLERR

C350035

DATA ERRORS IN INPUT MODULE HAVE EXCEEDED error-limit

The number of data errors that were encountered exceeds the default or user-supplied limit for nonnumeric data errors in input modules. Further errors of this type will not be reported; appropriate error-recovery action will be taken. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350036

RUN TERMINATED

Because of errors reported by the previous error messages, processing for the run cannot continue.

Severity: *

Modules: CULLERR

C350037

MESSAGES SUPPRESSED UNTIL END OF FILE

(CONT) MOST RECENT SUBSCRIPT VALUE nn

(CONT) INPUT BUFFER NUMBER nn

CA Culprit exceeded a default or user-supplied error limit and does not report more errors of that type until the end of input-file processing.

CA Culprit also prints the value of the last subscript referenced before the interrupt, the input buffer count at the time of the interrupt, and a message that identifies the area of processing in which the interrupt occurred.

Severity: *

Modules: CULLERR

C350041

PROGRAM CHECK OCCURRED DURING EXECUTION OF INPUT/USER PROCEDURE

(CONT) MODULE IN REPORT report-number

This message confirms that a program check occurred in the indicated module. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLERR

C350043

UNIDENTIFIABLE PROGRAM CHECK HAS OCCURRED

(CONT) ABEND CODE

CA Culprit invoked the extended error-handling routine to process a decimal overflow, decimal divide, or data error, but the routine cannot identify the type of code being processed (that is, CA Culprit main code, a user input module, a user procedure module, or a DB-EXIT call). The run terminates. This is an internal system error. For assistance, call CA Technical Support.

Severity: *

Modules: CULLERR

C350045

INTERNAL ERROR - RECOVERY CANNOT CONTINUE

CA Culprit invoked the extended error-handling routine but was unable to follow the normal recovery procedure. This is an internal system error. For assistance, call CA Technical Support.

Severity: *

Modules: CULLERR

C350046

PROGRAM CHECK INTERRUPT

(CONT) PSW AND REGS 0 - 15 ARE FORMATTED BELOW

(CONT) RECORD BUFFER DUMP

(CONT) WORKFIELDS AT TIME OF INTERRUPT

work-field-name

(CONT) RESULT CLEARED DUE TO INDETERMINATE

CONDITION

A program check occurred in the output phase (that is, CULE step). Associated messages identify the problem and the action to be taken by the runtime Extended Error-handling Facility:

  • CA Culprit prints a formatted listing of the PSW and the registers at the time a SPIE/STIXIT occurred. The listing is followed by a core dump.
  • CA Culprit prints the contents of the record buffer at the time of the interrupt.
  • CA Culprit prints work fields of the specified type.
  • CA Culprit sets the result field to 0 (zero) as the type of instruction causing the interrupt could not be determined or simulated.

For more information on this message, see Extended Error Handling Facility.

Severity: F

Modules: CULLERR

C350051

INVALID NUMERIC DATA IN MATCH KEY FIELD

The system detected a data exception while processing a numeric match-key field. The value of the invalid field is treated as though it were the largest possible negative number for match-file processing; processing continues. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLMTCH

C350052

NUMBER OF MATCH KEY NUMERIC ERRORS HAS EXCEEDED error-limit

The default or user-specified limit for numeric data errors in match-key fields was exceeded. Further errors of this type will not be reported; appropriate error recovery action will be taken. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLMTCH

C350053

RUN TERMINATED AT USER REQUEST

This message confirms that a default or user-supplied error limit was exceeded and that the action keyword specified on the PROFILE parameter for this type of error is either ABEND or CANCEL. End-of-run statistics follow the message.

Severity: *

Modules: CULLMTCH

CULLERR

C350055

NUMBER OF RECORDS RETURNED FOR— ddname/filename

This end-of-file statistic from the match-file facility indicates the number of records that were returned (that is, those passing the selection criteria, if any) for the named input file.

Severity: *

Modules: CULLMTCH

C350056

NUMBER OF INVALID MATCH KEYS— match-key-count

This end-of-match statistic from the match-file facility prints only if the number is not 0 (zero).

Severity: *

Modules: CULLMTCH

C350057

NUMBER OF RECORDS OUT OF SEQUENCErecord-count

This end-of-file statistics from the match-file facility prints only if the number is not 0 (zero).

Severity: *

Modules: CULLMTCH

C350058

AN OUT OF SEQUENCE CONDITION HAS ARISEN

(CONT) INPUT FILE IS input-file-number

(CONT) RECORD NUMBER IS record-count

(CONT) KEY POSITION IS match-key-position

(CONT) KEY DATA TYPE IS match-key-data-type

(CONT) STARTING BIT AND NUMBER OF BITS— bit-values

(CONT) KEY LENGTH IS match-key-length

(CONT) RECORD IS NOT IN BUFFER

(CONT) START POSITION WITHIN BUFFER buffer-position

A sequence error has been detected in a match-key field. CA Culprit prints additional messages that indicate which match-key field is in error and in which record number it occurred. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLMTCH

C350059

NUMBER OF SEQUENCE ERRORS HAS EXCEEDED me-error-limit

(CONT) INPUT FILE IS input-file-number

(CONT) RECORD NUMBER IS record-count

(CONT) KEY POSITION IS match-key-position

(CONT) KEY DATA TYPE IS match-key-data-type

(CONT) STARTING BIT AND NUMBER OF BITS— bit-value

(CONT) KEY LENGTH IS match-key-length

(CONT) RECORD IS NOT IN BUFFER

(CONT) START POSITION WITHIN BUFFER buffer-position

CA Culprit detected more than 25 errors (that is, the system limit) in a match-file sequence. For each error that occurs, CA Culprit prints additional information that indicates the match key and record number for which the error occurred. Further errors of this type will not be reported; appropriate error-recovery action will be taken. For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLMTCH

C350068

ERROR ON OPEN

An open error occurred while CA Culprit was trying to read an input file. Check your specifications on the INPUT parameter and JCL statement that define the file.

Severity: *

Modules: CULLMTCH

CULLJRNL

C350069

I/O ERROR ON READ

An I/O error occurred while CA Culprit was trying to read an input file. Check your specifications on the INPUT parameter and the JCL statement that define the file.

Severity: *

Modules: CULLMTCH

CULLJRNL

C350070

RECORD SIZE IS GREATER THAN record-size

A variable-length record that is longer than the maximum record specified on the INPUT parameter was encountered on the input file. The run terminates with an abend code of 33. For more information on this message, see Abend Codes.

Severity: *

Modules: CULLMTCH

C350071

MATCH ERROR ON FILE ddname/filename

An open or I/O error occurred on the named input file in a match-file run. CA Culprit prints additional messages following this one that describe the error further.

Severity: *

Modules: CULLMTCH

C350072

INTERRUPT DURING EXECUTION OF INPUT MODULE FOR ddname/filename

A program check interrupt occurred during processing by an input module for the indicated file in a match-file run.

Severity: *

Modules: CULLMTCH

C350073

INEXPLICABLE ERROR DURING CULLMTCH

This is an internal system error that occurred during the match process in the extract phase. Call CA Technical Support.

Severity: *

Modules: CULLMTCH

C350074

INPUT FILES ARE BEING SINGLE BUFFERED

z/VSE users only—One or more input files cannot be double buffered, due to limited storage. If a single buffer fits, the run will continue but performance may be downgraded. Available memory can be increased by relinking CULL and increasing the size specified after PHASE CULLWORK.

Severity: *

Modules: CULLMTCH

C350075

EXTRACT TERMINATED AT USERS REQUEST

A default or user-supplied error limit was exceeded, and the action keyword that was specified on the PROFILE parameter for this type of error is STOP. End-of-file statistics follow this message. Output reports will be produced on any data that was extracted up to this point.

Severity: *

Modules: CULLMTCH

CULLERR

C350078

UNKNOWN ERROR IN SELECT MODULE - RUN TERMINATED

CA Culprit invoked the Extended Error Handling Facility routine to handle an error that occurred during selection logic. CA Culprit eliminated an invalid subscript or invalid numeric data as the possible causes of the problem. This is an internal system error. Contact CA Technical Support.

Severity: *

Modules: CULLSEL

C350079

INVALID NUMERIC DATA IN SELECTION PROCESS

(CONT) SELECTION CONDITION REFERENCE

NUMBER reference-number

(CONT) INPUT RECORD NUMBER

CA Culprit encountered a data exception while processing a SELECT/BYPASS parameter. The tested value is set to low values for the current test (that is, the largest possible negative number, or hexadecimal 0s (zeros) for alphanumeric multiply-occurring fields referenced in a subscript that contains invalid numeric data), and processing continues.

CA Culprit also prints an additional message that indicates the number of the input record that was being processed when the data exception occurred.

For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLSEL

C350082

INVALID SUBSCRIPT VALUE IN SELECTION PROCESS

(CONT) SUBSCRIPT IS INVALID FOR FIELD ONE

(CONT) SUBSCRIPT IS INVALID FOR FIELD TWO

(CONT) FIELD ONE AT TIME OF INTERRUPT **INVALID**

(CONT) RECORD AT TIME OF INTERRUPT

(CONT) FIELD TWO AT TIME OF INTERRUPT

An invalid subscript value was coded on a SELECT/BYPASS parameter; the value is either negative or nonnumeric. Processing of the current report cannot continue.

CA Culprit prints additional information that indicates which field in the WHERE clause is invalid. CA Culprit also prints the contents of the invalid field and the record in the CA Culprit input buffer in hexadecimal format.

For more information on this message, see Extended Error Handling Facility.

Severity: *

Modules: CULLSEL

C350089

MORE THAN 999,999,999 INPUT RECORDS READ

CA Culprit read more than 999,999,999 input records. CA Culprit continues to process, but prints invalid end-of-file (EOF) statistics.

Severity: W

Modules: CULL

C350090

RECORD SIZE GREATER THAN SPECIFIED MAXIMUM

While reading a CA IDMS journal file, CA Culprit encountered a record that is larger than the maximum record size that was defined on the INPUT parameter. To correct this error, use the value of the journal block size for the record type.

Severity: W

Modules: CULLJRNL