|
Message ID |
Message |
|---|---|
|
C300000 |
NO PARAMETER INPUT - JOB ENDED CA Culprit detected no valid user parameters in the run. To evaluate this error, check the JCL. Severity: F |
|
C300001 |
INPUT PARAMETER MISSING No INPUT parameters were encountered in the CA Culprit parameter stream. At least one INPUT parameter is required for a CA Culprit run. Severity: F |
|
C300002 |
REC PARAMETER IS MISSING The user coded no REC parameters, and the data dictionary generated no REC parameters for the run. Code at least one REC parameter for every CA Culprit run. Severity: F |
|
C300003 |
EXTRACT NOT PERFORMED AT USERS REQUEST This message confirms that the user requested that no extract be performed (that is, the user coded EX=NO on the PROFILE parameter). Severity: I |
|
C300004 |
EDIT PARAMETER MISSING No type 5 edit parameter was entered for a report. CA Culprit requires at least one type 5 edit parameter for each report. Severity: E |
|
C300005 |
REPORT NUMBER IS INVALID An illegal report number was specified on an input parameter or as an operand on an =COPY, =MACRO, or REPORT= instruction. Valid report numbers are 00 through 99. If the error occurs in the REPORT= instruction, the invalid entry is underscored with asterisks. Severity: E |
|
C300006 |
CARD TYPE IS INVALID A card type that cannot be identified by CA Culprit was encountered in the CA Culprit parameter stream. Severity: E |
|
C300007 |
FIELD NAME PREVIOUSLY DEFINED A field name was encountered that duplicates the name of a previously defined field. Duplicate field names must be qualified by unique record names. Severity: E |
|
C300008 |
DUPLICATE INPUT PARAMETER Two or more INPUT parameters have been entered for the same input file. Qualify each input file with a DD= keyword expression that points to a different input file. Severity: F |
|
C300009 |
INPUT RECORD SIZE IS INVALID CA Culprit detected an invalid record size on an INPUT or KEYFILE parameter. The record size is a nonnumeric value, 0 (zero), or it exceeds the system limit of 32K. Severity: F |
|
C300010 |
LABEL TYPE IS INVALID Either the label type specified on the INPUT parameter is N but the file type is not CARD or PS(TAPE) or the label is A but the file type is not PS. The invalid entry is underscored with asterisks. Severity: F |
|
C300011 |
EDIT INDICATORS GIVEN FOR A/N FIELD Edit specifications other than size (that is, format, decimal, or user mask) were coded on an edit parameter for a field that is defined as alphanumeric. All such specifications are ignored. Severity: W |
|
C300012 |
RECORD TYPE IS INVALID CA Culprit encountered an invalid record type on an INPUT or KEYFILE parameter. If a record type is coded, valid specifications are F, V, or U. Severity: F |
|
C300013 |
BLOCK SIZE MISSING OR INVALID The block size on an INPUT or KEYFILE parameter is invalid, as described as follows:
Severity: F |
|
C300014 |
RECSIZE OR BLKSIZE WRONG FOR CARD FILE z/VSE users only—The record or block size for a card input file is invalid. Severity: F |
|
C300017 |
SPECIFIED DEVICE TYPE IS INVALID CA Culprit encountered a request for a device type on an INPUT or KEYFILE parameter, but the device type is not known to the system. For a complete listing of valid device types, refer to the CA Culprit for CA IDMS Reference Guide. Severity: F |
|
C300018 |
ISAM KEY MISSING OR INVALID The user requested ISAM file output, but the first sort key that was coded on the SORT parameter does not appear on a type 5 edit parameter. Severity: F |
|
C300019 |
E-LEVEL ERRORS - EXTRACT NOT PERFORMED E-level errors occurred that prevent processing for all reports. Either no error-free reports exist or the PROFILE parameter does not indicate that error-free reports should be produced. Severity: F |
|
C300020 |
DUPLICATE SORT CARD CA Culprit encountered more than one SORT parameter for this report. Severity: E |
|
C300021 |
DUPLICATE OR INVALID FIELD POSITION The system encountered a duplicate or invalid starting position on a REC or edit parameter:
Severity: E |
|
C300022 |
DATA TYPE IS INVALID The system encountered an invalid or illegal data type on a REC parameter. For numeric field data types, code data types 1 through 5. Omit the data type on alphanumeric or GROUP REC parameters. For multiply-occurring fields, enter the data type on ELMNT REC parameters. Severity: E |
|
C300023 |
FIELD SIZE IS INVALID The system encountered an invalid field size on a REC, KEYFILE, or edit parameter. The invalid field size is 0 (zero), nonnumeric, or greater than the system limit for the associated data type. Severity: E |
|
C300024 |
FIELD POSITION EXTENDS BEYOND RECORD The sum of the starting position and the size of the data field placed part or all of the specified field beyond the end of the input record. CA Culprit does not read the data that extends beyond the end of the record. (This is an E-level message if it applies to a field on a type 5 or 6 edit parameter.) Severity: W, E |
|
C300025 |
DUPLICATE OUTPUT CARD The system encountered more than one OUTPUT parameter for this report. Correct your CA Culprit code so that there is only one OUTPUT parameter for each report number. Severity: E |
|
C300026 |
OUTPUT FILE TYPE INVALID The user coded an invalid file type or a file type with an invalid qualifier on an OUTPUT parameter. Severity: E |
|
C300027 |
CONTROL BREAK CODE INVALID The system encountered an invalid break code for a sort key on a SORT parameter. Valid codes are:
Severity: E |
|
C300028 |
LINES/PAGE INVALID An invalid LP= specification was coded on the OUTPUT parameter. The value either is nonnumeric or exceeds 32K. The invalid specification is underscored with asterisks when the error appears in the Sequential Parameter Listing. Severity: E Modules: CULPOUKL |
|
C300029 |
TOTAL/DETAIL NOT T, D, OR BLANK On an OUTPUT parameter, the total/detail indicator is not T, D, or blank. Severity: E Modules: CULPOUCH |
|
C300030 |
OUTPUT RECORD SIZE INVALID The user coded an invalid record size on an OUTPUT parameter; the record size is invalid for one of the following reasons:
Severity: E Modules: CULPOUCH |
|
C300031 |
RUN CANCELLED DUE TO INSUFFICIENT STORAGE CA Culprit canceled the job due to insufficient storage to hold the module, table, or buffer named in subsequent messages. The continuation message indicates the additional number of bytes that are necessary to hold the entity. For more information on this message, see Abend Codes. Severity: F |
|
C300032 |
FIELD IS UNDEFINED The user coded an invalid field on a CA Culprit parameter. This error can occur if the field is not defined or is defined incorrectly (for example, a misspelled field name) on a REC, work field definition, or implied subscript parameter. Severity: E |
|
C300033 |
SORT FIELD EXCEEDS PROGRAM CAPACITY The combined size of all sort fields specified on the SORT parameter exceeds 240 bytes. Note that one byte per sort field is reserved for CA Culprit system use. Severity: E |
|
C300034 |
NO ENDING APOSTROPHE A beginning apostrophe was found on a parameter, indicating that a literal will follow, but no ending apostrophe can be found. Note that two consecutive apostrophes with no intervening blank space (that is, '') do not constitute beginning and ending apostrophes. Severity: E |
|
C300036 |
SORT SEQUENCE UNSPECIFIED FOR ISAM OUTPUT The user requested ISAM file output, but the ISAM key is not specified as the major sort field on the sort parameter. Severity: E |
|
C300037 |
DUPLICATE OR ILLEGAL TITLE PARAMETER A duplicate or illegal type 3 title parameter was encountered in the CA Culprit parameter stream. Either the title parameter is not the first parameter encountered for the report or the number of characters in the title plus the 33 characters for report number, page, and date (40 characters if a time stamp was requested) exceeds the record size that was specified on the OUTPUT parameter. Severity: E |
|
C300038 |
LINE NUMBER IS INVALID The system encountered an invalid line number on a type 4, type 5, or type 6 edit parameter. Valid line number values are 1 through 8. Severity: E Modules: CULP46CH |
|
C300039 |
INCOMPATIBLE VERSIONS OF CULP0 AND CULL The version number from CULP0 does not match the version number in CULL. Check your STEPLIB specifications in your JCL. Be sure to use CULP0 and CULL programs from the same release of CA Culprit. Severity: F Modules: CULL |
|
C300040 |
OVERLAPPING OUTPUT FIELDS The user coded an output data field that overlaps the preceding output field on an edit parameter. The only output position that can overlap from one field to the next is a trailing sign on numeric data. Severity: E |
|
C300041 |
CARRIAGE CONTROL IS INVALID The user specified an invalid spacing (that is, carriage control) character on a type 4, type 5, or type 6 edit parameter. Valid codes are: -, +, A, B, C, V, W, 0 through 9, or a blank space. The invalid character is underscored with an asterisk. Severity: E |
|
C300042 |
USER MUST OUTPUT FIELD WITH HEAD COMMAND A field is referenced on a type 4 header edit parameter, but the field is not defined as a sort key field on the SORT parameter. Use the branch to HEAD instruction on a type 7 parameter to make the field available to the header line. This message prints whether or not such action is included in the procedure code. Severity: W |
|
C300043 |
USER MODULE NAME IS INVALID CA Culprit detected an invalid user module name. The user coded UM on an OUTPUT parameter, but the module name is invalid because of one of the following conditions:
Severity: E |
|
C300044 |
UNABLE TO CONTINUE COMPILATION DUE TO ERRORS CA Culprit detected an internal table overflow. This error can occur if the current or previously processed parameters contain E-level or F-level errors. If the error condition occurs while CA Culprit is processing a parameter, that parameter may not be printed. Correct any E-level or F-level errors. Be sure that no errors are in the parameter that was to be processed after the last printed parameter, and resubmit the job. Severity: E |
|
C300045 |
TOTAL LINE FIELD IS INVALID A field defined on a REC parameter was specified on a type 6 total edit parameter but was not named on a type 5 detail or SORT parameter. This field cannot be referenced in type 8 total-processing logic. Severity: E |
|
C300046 |
RESULT SEQUENCE IS INVALID The user coded an invalid result field sequence number on a process definition parameter; the result field sequence number must be numeric. Severity: E |
|
C300047 |
FIELD 1 IS INVALID The user coded an invalid value as the first operand of a type 7 or type 8 process definition parameter:
Severity: E |
|
C300048 |
FIELD 2 IS INVALID The user coded an invalid value as the second operand of a type 7 or type 8 process definition parameter:
Severity: E |
|
C300049 |
RESULT FIELD IS INVALID The user specified an invalid result field name on a process definition parameter. The invalid entry is underscored with asterisks. Possible causes of this error follow:
Severity: E |
|
C300050 |
BACKWARD SEQUENCE NUMBER REFERENCE MAY CAUSE LOOP The system encountered a process definition parameter whose result field is sequence number that identifies a process definition parameter that was already processed by the system. Processing continues, but check the logic to ensure that an infinite loop does not result. Severity: W |
|
C300051 |
OPERANDS ARE CONFLICTING DATA TYPES The user coded operands of different data types on the same type 7 or type 8 process definition parameter. Both operands must be either numeric or alphanumeric. Severity: E |
|
C300052 |
DUPLICATE OR INVALID SEQUENCE NUMBER The system encountered a duplicate or invalid sequence number on a type 7 or type 8 process definition parameter. This error can occur if the sequence number is nonnumeric, or if the sequence number was previously coded in the CA Culprit parameter stream. Severity: E |
|
C300053 |
OPERAND ILLEGAL WITH SPECIFIED OP CODE CA Culprit detected an operand that conflicts with the operation code on a type 7 or type 8 process definition parameter. Possible causes of this error follow:
Severity: E |
|
C300054 |
UNRESOLVED BRANCH LABEL branch-label (CONT) DETECTED IN STATEMENT—internal-sequence-number The system encountered a branch operation code on a type 7 or type 8 process definition parameter, but the result sequence number does not exist. The continuation message names the internal sequence number of the statement where the unresolved branch occurred. To evaluate this error, review the statement with the indicated internal sequence number in the process definition parameters in the Input Parameter Listing. Severity: E |
|
C300055 |
E-LEVEL ERRORS - REPORT NOT PROCESSED CA Culprit detected E-level errors that prevent processing for this report. To evaluate these errors, review the Sequential Parameter Listing and the Input Parameter Listing. Severity: E |
|
C300056 |
FATAL ERRORS - EXTRACT NOT PERFORMED The system detected F-level errors that prevent processing of the input file. To evaluate these errors, review the Sequential Parameter Listing and the Input Parameter Listing. Severity: F |
|
C300057 |
FIELD NAME IS INVALID The user coded an invalid name of a qualifying record name for a field. The entry is invalid because it exceeds the system limit of 32 characters, it does not contain at least one alphabetic character, or it begins or ends with - (a hyphen). Severity: E |
|
C300058 |
TOTAL ILLEGAL - DETAIL REPORT SPECIFIED Type 6 or type 8 total-time parameters were encountered in the CA Culprit parameter stream, but the OUTPUT parameter indicates that only detail lines should be generated for this report. Severity: E |
|
C300059 |
NO VALID REPORT-SPECIFIC PARAMETERS The system detected no report-specific parameters in this run. Each run must contain at least one type 5 edit parameter. Severity: F |
|
C300060 |
COMPARE FIELDS ARE UNEQUAL - SMALLER FIELD IS USED The user coded two alphanumeric fields of different sizes as operands in a test operation. CA Culprit performs the test operation from left to right and ignores the excess right-most characters of the longer field. Severity: W |
|
C300061 |
MOVE FIELDS UNEQUAL-RESULT LENGTH USED The user moved an alphanumeric field to a result field of a different length. CA Culprit executes the move, but truncates or pads the field, as follows:
Severity: W |
|
C300062 |
STOP OR STOP-RUN TERMINATES ALL REPORTS A STOP or STOP-RUN instruction was encountered on a type 7 input procedure parameter. When this instruction executes, the input file is closed and no further input records are available to any reports. The record being processed will be available to all reports, and an end-of-file (EOF) condition will be returned after all reports have seen that record. Severity: W |
|
C300063 |
ILLEGAL RESULT FIELD IN TOTAL PROCEDURE The system detected an invalid result field on a type 8 total-procedure parameter. The following field types cannot be used as result fields on type 8 parameters:
Severity: E |
|
C300064 |
FORMAT CODE IS INVALID The user coded an invalid format code on an edit parameter. This error can occur if the number of digits exceeds the field size, or if the format code is not F*, F$, FN, FM, FP, FZ, F0 through F9, F-, FF, FC, FS, FU, FW, FB, or FD. Severity: E |
|
C300065 |
FIELD POSITION EXCEEDS BUFFER CAPACITY A field position that extends beyond addressable space was specified on a REC or edit parameter. The maximum input and output buffer capacity is 32K. Severity: E |
|
C300066 |
INVALID CONTROL RECORDS.CULP0/SORT NOT RUN The parameter file that was input to the compile phase (that is, CULL step) contains invalid data. A probable cause of the problem is an error in the JCL for the precompile phase, the parameter sort phase, or the compile phase. Severity: F |
|
C300067 |
FIELD POSITION EXTENDS BEYOND RECORD The sum of the starting position and the size of the data field placed part or all of the specified field beyond the end of the OUTPUT record defined on an OUTPUT parameter. Severity: E |
|
C300068 |
ERRORS DETECTED IN CULP0 STEP CA Culprit detected errors in the precompiler phase (that is, CULP0 step) that prevent processing of the current report. This message prints during the compile phase (that is, CULL step). Severity: E |
|
C300069 |
MIXED POSITION DEFINITION Both exact print positions and info-columns were specified on edit parameters that describe a single edit line. Only one type of position definition can be used for a given edit line. Severity: E |
|
C300070 |
OVERLAPPING AUTOMATIC HEADERS The user specified auto-headers on edit parameters, but when the headers are centered over the data fields on the output report the auto-headers overlap. To correct this error, reduce the header length or increase the space between output fields and resubmit the job. Severity: E |
|
C300071 |
AUTO-HEADER EXTENDS BEYOND RECORD The placement of an auto-header over a data field resulted in an invalid starting or ending position for the header of an output record. Check the headers that are coded for this field in the type 5 edit or REC parameters. Note that an attempt to center a long header over a field that is in a valid position may cause the header to extend beyond the beginning or end of the record. Severity: E |
|
C300072 |
INFO-COLUMNS EXTEND BEYOND RECORD The sum of the widths of all info-column data exceeds the output record length. Note: The width of an info-column is the maximum size of any header, detail, or total field that appears in that column. At least one space must be left at each margin and between each pair of columns. Severity: E |
|
C300073 |
DECIMAL POINT SPECIFICATION IGNORED The user coded a decimal place specification (that is, DP=) on a field intended for use with a user edit mask (that is, the format code is FM). CA Culprit ignores the decimal place specification. Note: The user can correctly code a decimal point in an edit mask (that is, FM 'Z,ZZZ,ZZ9.99'). Severity: W |
|
C300074 |
USER MASK MISSING OR INVALID An invalid user edit mask was requested on a type 4, type 5, or type 6 edit parameter. Severity: E |
|
C300075 |
PRINTED OUTPUT RECORD SIZE EXCEEDS 132 z/VSE users only—The user coded a record size that exceeds the system limit of 132 characters for an output print file. Severity: W |
|
C300076 |
TITLE PARAMETER FOR NON-PRINTED REPORT This message confirms that CA Culprit accepted a type 3 title parameter for nonprint output. The report title appears as the first record in the output file. Severity: W |
|
C300077 |
PARAMETER HAS INVALID CHARACTER IN COLUMN 1 An invalid nonblank character was coded in column 1 of an output parameter. The only characters that are allowed in this column are the continuation character (that is, *) and the equal sign (that is, =). Severity: F |
|
C300078 |
F-LEVEL ERROR DETECTED IN CULP0 STEP CA Culprit encountered an F-level error during the precompile phase (that is, CULPO step). CULP0 may also have produced messages of a lower severity level (for example, E level or W level) for this parameter. Severity: F |
|
C300079 |
E-LEVEL ERROR DETECTED IN CULP0 STEP CA Culprit detected an E-level error during the precompile phase (that is, CULPO step). CULPO may have also produced messages of a lower severity (for example, W level) for this parameter. Severity: E |
|
C300080 |
W-LEVEL ERROR DETECTED IN CULP0 STEP This message indicates that the system flagged the parameters that associated with the message in the precompile phase (that is, CULPO step) with a severity-level W message. To evaluate this error, review the Sequential Parameter Listing. Severity: W |
|
C300081 |
ALPHA OR NUMERIC WORK FIELDS EXCEED 32K The total storage requested for either global or report-specific alphanumeric or numeric work fields exceeds 32K. If the job contains two or more reports, split the job in two. Severity: E |
|
C300082 |
FATAL ERRORS DETECTED IN CULP0 STEP The system detected F-level errors in the precompile phase (that is, CULPO step). To evaluate these errors, review the Sequential Parameter Listing and the Input Parameter Listing. Severity: F |
|
C300083 |
GROUP ID IS INVALID A group ID was not properly coded on a GROUP REC or ELMNT REC parameter. The invalid ID is underscored with asterisks. Severity: F |
|
C300084 |
GROUP ALREADY DEFINED The group ID specified on a GROUP REC parameter was specified for a previous group. Group ids must be unique. Severity: F |
|
C300085 |
GROUP ID NOT SPECIFIED A GROUP REC parameter has no group ID specification. Severity: F |
|
C300086 |
OCCURRENCE SIZE IS INVALID CA Culprit detected an invalid group length on a GROUP REC parameter. This error can occur for singly-occurring and multiply-occurring groups, as follows:
Severity: F |
|
C300087 |
NUMBER OF OCCURRENCES MISSING The system encountered no occurrence count specification on a GROUP REC parameter. A possible cause of this error is that a period does not immediately precede the specification. Severity: F |
|
C300088 |
NUMBER OF OCCURS IS INVALID The user coded an occurrence count specification on a GROUP REC parameter; the specification is invalid for one of the following reasons:
Severity: F |
|
C300089 |
LINK GROUP UNDEFINED link-group-id The user coded link-group-id on a GROUP REC parameter, but the entry was not defined correctly as a group ID on a previous GROUP REC parameter. Severity: F |
|
C300090 |
DEPENDING ON FIELD UNDEFINED FOR GROUP group-id The field name that was specified on a GROUP REC parameter as the occurrence count for a multiply-occurring input field is invalid; the field name either was not defined or was defined incorrectly in the fixed portion of the input record. Severity: F |
|
C300091 |
DEPENDING ON FIELD NOT FIXED FOR GROUP group-id The field name that was specified on a GROUP REC parameter as the occurrence count for an multiply-occurring field is invalid; the field was not defined in the fixed portion of the input record (that is, the portion with an absolute starting location within the record). Severity: F |
|
C300092 |
SYMBOL NAME PREVIOUSLY DEFINED The user coded a base field name on a type 15 implied subscript parameter, but that parameter was previously defined. The base field name is either a name that was defined on an implied subscript parameter or an element of a group that was referenced on an implied subscript parameter. Severity: E |
|
C300093 |
SUBSCRIPT IS NOT A NUMERIC WORKFIELD The user referenced a multiply-occurring field on a type 6 or type 8 total-time parameter. The subscript that references the field is neither a numeric work field nor an absolute numeric value. The subscript cannot be a sort key or a type 5 field parameter. Severity: E |
|
C300094 |
REFERENCE MUST USE SUBSCRIPT PARAMETER The user referenced a field without a subscript on an input parameter, but the field was defined in a multiply-occurring group on an ELMNT REC parameter. To correct this error, use a subscript to reference the field that is defined in the multiply-occurring group. Severity: E |
|
C300095 |
SUBSCRIPT IS NOT NUMERIC The system encountered a nonnumeric subscript in the CA Culprit parameter stream. To correct this error, use either a numeric literal or a numeric work or input field as a subscript. Severity: E |
|
C300096 |
SUBSCRIPT REFERENCE OUTSIDE USER AREA CA Culprit encountered an invalid subscript value at compile time. The entry is invalid because the subscripted field referenced an area in storage that is outside the defined limits for this type of data. Severity: E |
|
C300097 |
GROUP NOT DEFINED A group ID was specified on an implied subscript parameter, but the group ID either is not defined on a REC parameter or is not system generated for database input. Severity: E |
|
C300098 |
GROUP ALREADY HAS SUBSCRIPT The user identified a group on an implied subscript parameter with a subscript, but the group that was identified was previously assigned a subscript index. Only one implied subscript parameter can be defined for each group. Severity: E |
|
C300099 |
NON-NUMERIC DUPLICATION FACTOR The number of occurrences specified on a work field definition parameter is not numeric. Severity: E |
|
C300100 |
SUBSCRIPT MAY NOT BE SUBSCRIPTED CA Culprit detected an invalid subscripted field; this error can occur for one of the following reasons:
Severity: E |
|
C300101 |
DEPENDING ON FIELD NON-NUMERIC FOR GROUP group-id The field name that was specified on a GROUP REC parameter as the occurrence count for a multiply-occurring input field is invalid; the field was defined as alphanumeric. Severity: F |
|
C300102 |
NON MULTIPLY-OCCURRING INPUT FIELD An input field that is not multiply-occurring was referenced on a type 15 implied subscript parameter. Severity: E |
|
C300103 |
CALCULATED LRECL EXCEEDS FILE SPECIFICATION CA Culprit detected an error in the record length in the JCL. The record length for SYS006 (that is, the extracted-items file) is not large enough to hold a record extracted to that file or to SYS008 (that is, the no-sort extracted-items file) for the current report. To correct this error, calculate LRECL as the sum of the following, rounded to a multiple of 4 with a minimum of 256 bytes:
Note: The calculated record length does not have to be precise, but LRECL must be larger than the longest record. Severity: E |
|
C300104 |
REC LENGTH OF EXTRACT FILE LESS THAN MINIMUM The user specified a record length in the extract phase (that is, CULL step) for the extracted-items file (that is, SYS006) that is less than the system minimum of 256 bytes. To correct this error, modify the JCL and resubmit the job. Severity: F |
|
C300105 |
PARAMETER TABLE OVERFLOW - table-name An overflow has occurred in a system-maintained table (table-name ). The run will abend with a return code of 100. Contact CA. Severity: F |
|
C300106 |
EXTRACT WILL BE PERFORMED This message will follow the program compile if there are not any fatal errors. |
|
C300107 |
GENERATED CODE EXCEEDS 32K The code CA Culprit generates for type 7 and type 8 logic exceeds CA Culprit's internal limits. If the code contains two or more reports, split the code and submit two separate jobs. Severity: F |
|
C300108 |
TITLE IS TRUNCATED The user coded a report title on a type 3 title parameter that exceeds the system limit of 50 characters; CA Culprit truncates the trailing characters. Severity: W |
|
C300109 |
INVALID SIZE OR DP SPECIFICATION FOR SUBSCRIPT The user coded an invalid size or DP= specification; this error can occur for one of the following reasons:
Severity: E |
|
C300110 |
SELECT SPECIFIES WRONG FILE The user coded a SELECT/BYPASS parameter that referenced a REC parameter, but the REC parameter could not be found on that file. This error can occur if a SELECT parameter is misplaced or if an entry is misspelled on the REC parameter. Severity: F |
|
C300111 |
DEPENDING ON FIELD DECIMAL OR TOO LONG The user specified an OCCURS DEPENDING ON field on a GROUP REC parameter and the REC parameter that defines the field contains a DP= specification or its size and data type specify a field with more than 15 digits. Severity: F |
|
C300112 |
MINIMUM POSSIBLE RESULT EXCEEDS LIMIT Because of the number of decimal places that was specified in the operands and the quotient of a divide operation on a type 7 or type 8 parameter, the quotient will always contain more than 31 digits. To circumvent this problem:
Severity: E |
|
C300113 |
RESULT WILL BE ZERO Because of the number of decimal places that are assigned to the operands and the product of a multiplication operation, the product will always be 0 (zero) when rounded or truncated to the requested number of decimal places. Severity: W |
|
C300114 |
ILLEGAL DECIMAL POINT SPECIFICATION CA Culprit encountered an error in an explicit decimal place specification on an edit parameter. This error can occur if the explicit decimal place specification exceeds the implied or explicit output field size or if the explicit decimal place specification exceeds the maximum value permitted for the specified format code. Severity: E |
|
C300115 |
INPUT DECIMAL SPECIFICATION IGNORED On an edit parameter, the user specified a format code that implies that decimal places will not appear in output, but the number of decimal places specified on a REC or work field parameter is a value other than 0 (zero). CA Culprit treats the field as an integer value on output; no decimal alignment is performed. Severity: W |
|
C300116 |
EDIT LITERALS EXCEED LIMIT CA Culprit ran out of space to store literals on type 5 and type 6 parameters for a given report; the amount of storage that is required exceeds the system limit of 4K. To circumvent this problem, assign some of the literal values to alphanumeric work fields and specify the work fields on type 5 or type 6 parameters. Severity: E |
|
C300118 |
FIELD SIZE EXCEEDS LIMIT FOR B HEAD CA Culprit detected a field on a type 4 edit parameter that was not defined as a sort key. The system expected the defined field to be delivered through the B HEAD instruction on a process definition parameter, but the specified field size exceeds the system limit of 100 bytes for such fields. Severity: E |
|
C300119 |
PROFILE OPTION IN EFFECT: RELEASE = release-number This message indicates the release mode that is in effect. The value in release-number is either 5 or 6. If RELEASE= was not coded on the PROFILE parameter, CA Culprit uses the value that was set at installation time. Severity: I |
|
C300120 |
FIELD SIZE EXCEEDS LIMIT FOR CONVERT An error occurred on a type 7 or type 8 process definition parameter for a convert operation. The field size exceeds the system limit of 33 characters for the alphanumeric source. Severity: E |
|
C300121 |
UNDEFINED GROUP ID - group-id The user coded the indicated group ID on an ELMNT REC parameter, but no GROUP REC parameter with that group ID was found. To correct this error, code a GROUP REC parameter with the indicated group ID to define a multiply-occurring block of data and resubmit the job. Severity: F |
|
C300122 |
CULP HAS CORRECTED YOUR COLUMN SPECIFICATION For CA Culprit jobs that specify TYPE=CREATE, ADD, or REPLACE on the OUTPUT parameter, CA Culprit overrides the user's absolute column positions if the positions are incorrect. CA Culprit forces the columns to be contiguous. Severity: W Modules: CULLIDB |
|
C300123 |
SZ= HAS BEEN REDUCED TO COLUMN LENGTH ON TABLE For CA Culprit jobs that specify TYPE=ADD or REPLACE on the OUTPUT parameter, CA Culprit automatically truncates or pads the text fields that specify SZ= so that the field length matches the column definition. Severity: W Modules: CULLIDB |
|
C300124 |
TABLE SUCCESSFULLY GENERATED For a CA Culprit run that accesses tables and specifies CREATE or GENERATE on the OUTPUT parameter, CA Culprit prints a message that indicates the table has been successfully generated. Severity: I Modules: CULLIDB |
|
C300125 |
SQL COLUMN NAME TRUNCATED TO 18 CHARACTERS For CA Culprit jobs that specify SQLTYPE=CREATE, column names taken from the edit parameters will be truncated to 18 characters. Severity: W Modules: CULLSQL |
|
C300126 |
FORMAT CODE NOT SUPPORTED FOR SQL The format code specified for this column is not supported for SQL. Severity: E Modules: CULLSQL |
|
C300127 |
NULL INDICATOR MUST BE FB (BINARY) FORMAT When specifying a null indicator corresponding to an SQL column, the format must be FB. Severity: E Modules: CULLSQL |
|
C300128 |
NULL INDICATOR MUST BE SZ=4 When specifying a null indicator corresponding to an SQL column, the size must be 4. This should be coded as SZ=4. Severity: E Modules: CULLSQL |
|
Copyright © 2014 CA.
All rights reserved.
|
|