C850001

EXTRACT SUPPRESSED BECAUSE OF ERRORS

CA Culprit detected E-level errors that prevent processing for all reports on an INPUT parameter for a run that accesses CA IDMS/DB database records. To evaluate these errors, review the Sequential Parameter Listing and the Input Parameter Listing.

Severity: F

Modules: CULLDCLI

CULLIDBR

C850002

BIND ERROR, STATUS = idms-error-status

The system detected an error that relates to binding a run unit for a run that accesses a CA IDMS/DB database. The extract is terminated. Refer to CA IDMS Messages and Codes Guide, for an explanation of the CA IDMS/DB error status.

Severity: E

Modules: CULLDCLI

CULLIDBR

C850003

OPEN AREAS ERROR, STATUS = idms-error-status

The system could not ready a CA IDMS/DB area for a run that accesses a CA IDMS/DB database. The extract is terminated. Refer to CA IDMS Messages and Codes Guide, for an explanation of the CA IDMS/DB error status.

Severity: E

Modules: CULLDCLI

CULLIDBR

C850004

BASE RECORD READ ERROR, STATUS = idms-error-status

The system could not obtain the first record name on the PATH parameter in a run that accesses a CA IDMS/DB database. The extract is terminated. Refer to CA IDMS Messages and Codes Guide, for an explanation of the CA IDMS/DB error status.

Severity: E

Modules: CULLDCLI

C850005

OWNER RECORD READ ERROR, STATUS = idms-error-status

CA IDMS/DB could not obtain an owner record and returned a status code to CA Culprit that terminates execution. Refer to CA IDMS Messages and Codes Guide, for an explanation of the CA IDMS/DB error status.

Severity: E

Modules: CULLDCLI

C850006

MEMBER RECORD READ ERROR, STATUS = idms-error-status

CA IDMS/DB could not obtain the next member record of a set and returned a status code to CA Culprit that terminates execution. Refer to CA IDMS Messages and Codes Guide, for an explanation of the CA IDMS/DB error status.

Severity: E

Modules: CULLDCLI

C850010

KEYFILE READ ERROR

An I/O error occurred during an attempt to read the key file in a database access run. To evaluate this error, check the JCL. Refer to CA IDMS Messages and Codes Guide, for an explanation of the CA IDMS/DB error status.

Severity: E

Modules: CULLDCLI

C850011

IDMS ERROR STATUS = idms-error-status

(CONT) ERROR RECORD = record-name

(CONT) ERROR SET = set-name

(CONT) ERROR AREA = area-name

(CONT) LAST GOOD RECORD= record-name

(CONT) LAST GOOD AREA= area-name

(CONT) LOGICAL REC STATUS= logical-record-status-code

(CONT) LOGICAL RECRD NAME= logical-record-name

(CONT) LAST LR VERB = logical-record-verb

(CONT) LRPXELEN = lr-control-block

(CONT) LRMAXVXP = lr-control-block

The system detected an error that relates to the CA IDMS/DB database. Refer to CA IDMS Messages and Codes Guide, for the CA IDMS/DB error status code.

Severity: E

Modules: CULLDCLI

C850026

INVALID TYPE CODE

CA Culprit issued a call to DB-EXIT to obtain a set value. However, the fifth argument was not a valid code for a data type. Valid codes are 1 (binary), 2 (zoned), 3 (packed) and a blank (' ' for alphanumeric). No value was set by DB-EXIT. Correct the data type for the fifth argument and resubmit the job.

Severity: I

Modules: CULLDCLI

C850027

FIELD SIZE TOO LARGE— field-size

The user coded the indicated field size in the fourth argument of a DB-EXIT call to obtain a set value. The field length that is specified exceeds the maximum length permitted for the type of data that is described in the fifth argument.

Refer to the CA IDMS Messages and Codes Guide, for limits that apply to each data type. Adjust the field length in the CA Culprit code and resubmit the job.

Severity: I

Modules: CULLDCLI

C850029

CONSOLIDATION LIMIT OF 999 TABLES EXCEEDED

In a run that consolidates data tables, the CA Culprit code contains more than 999 INPUT parameters. CA Culprit can consolidate as many as 999 tables in a single run.

Correct your code and resubmit the job.

Severity: E

Modules: CULLIDBR

C850030

FINISH ERROR, STATUS = idms-status-code

A nonzero error status was returned during the @FINISH macro on your input data table. Refer to CA IDMS Messages and Codes Guide, for more information about CA IDMS/DB error status codes.

Severity: E

Modules: CULLIDBR

C850031

THIS TABLE CANNOT BE CONSOLIDATED: table-name

(CONT) CULLIDBR SKIPPING TO TABLE-ID table-id

(CONT) CULLIDBR CANNOT CONTINUE DATA EXTRACTION

In a run that consolidates data tables, CA Culprit encountered a table whose column definitions are not the same as the column definitions in the primary table. Depending on whether the PROFILE parameter specifies EX=E, one of the two continuation messages prints:

• EX=E—CA Culprit bypasses the table in error and extracts information from the next table in the CA Culprit job (table-id).
• No EX=E—CA Culprit prints a message stating that it cannot continue to extract data.

Severity: E

Modules: CULLIDBR

C850034

ERROR READING LOGICAL RECORD, STATUS = idms-error-status

(CONT) LRVERB = logical-record-verb

(CONT) LRSTATUS = logical-record-status

(CONT) LR PXE LENGTH = lr-control-block-length

(CONT) LR MAX VXP = lr-control-block-length

(CONT) LOGICAL RECORD NAME = logical-record-name

This message describes a logical-record error that occurred while obtaining a record from an input data table.

Severity: E

Modules: CULLIDBR

C850035

LAST XDE IN USER WHERE CLAUSE IS INVALID

CA Culprit detected an internal system error associated with a WHERE clause. Check the WHERE clause for errors before calling CA Technical Support.

Severity: F

Modules: CULLIDBR

C850036

A "KEY-VALUE" EXPRESSION IS REQUIRED IN YOUR WHERE CLAUSE.

(CONT) CULLIDBR CANNOT CONTINUE DATA EXTRACTION

In a CA Culprit run that accesses logical records, the WHERE clause of the path parameter can include the word 'KEY-VALUE'. KEY-VALUE instructs CA Culprit to compare values either on KEY parameters or in KEYFILE files to values in a field in a logical record.

Severity: F

Modules: CULLIDBR