|
Message ID |
Message |
|---|---|
|
C200001 |
DP= INVALID ON ALPHA REC PARM CA Culprit detected a DP= specification on a REC parameter that is defined as alphanumeric. Specify DP= on numeric fields only. The invalid entry is underscored with asterisks. Severity: E Modules: CULPRECH |
|
C200002 |
DP= CODED AFTER INITIAL VALUE The user coded DP= after the initial value or values for a work field. The DP= specification must precede the initial value. The invalid entry is underscored with asterisks. Severity: E Modules: CULP01CH |
|
C200003 |
USER MODULE NAME MISSING OR INVALID CA Culprit detected a missing or invalid module name; this error can be F-level or E-level, as follows:
The module name can be invalid for one of the following reasons:
Severity: E, F Modules: CULPFIPL CULPOUCH CULP78CH 'CALL' SPECIAL FUNCTION |
|
C200004 |
UNKNOWN PARAMETER CARD PASSED AS IS The indicated parameter cannot be recognized in the precompile phase (that is, CULPO step). The parameter is passed to the compile phase where it may be handled through a special database interface module. This error can also occur if the module that processed this parameter type is missing in the link of CULPO. Severity: W Modules: CULPDFRE |
|
C200005 |
INVALID TOKEN IGNORED The flagged string (underscored with asterisks) is invalid at the place where it was found; CA Culprit ignores the string. The severity level of this message depends on the parameter in which the invalid string occurs. Severity: F,E,W Modules: MANY CULPDFRE SUBMODULES |
|
C200006 |
INCOMPLETE PARAMETER CARD This is either an E- or an F-level message:
Severity: E, F Modules: CULP0 CULPDFRE SUBMODULES |
|
C200007 |
RIGHT PARENTHESIS INSERTED CA Culprit expected a right (that is, closing) parenthesis in the place that is underscored with asterisks; the system automatically supplies the missing parenthesis. Severity: W Modules: CULPDFRE CULPFIPL |
|
C200008 |
INCOMPLETE SUBSCRIPTED EXPRESSION A period was coded in a field reference, but no subscript value follows. The invalid field reference is underscored with asterisks. Severity: E Modules: CULPDFRE GETSUB SUBROUTINE |
|
C200009 |
INCOMPLETE QUALIFIED EXPRESSION The user coded an invalid field name on a REC or SELECT/BYPASS parameter. The field name is invalid because a qualifying record name or level is needed. The invalid entry is underscored with asterisks. Severity: E Modules: CULPDFRE CULPOUCH |
|
C200010 |
MORE VALUES THAN OCCURS ACCEPTED The number of initial values supplied exceeds the number of occurrences specified on a work field definition parameter that defines a multiply-occurring field. All initial values are stored and can be referenced by the user. The extra values are underscored with asterisks. Severity: W Modules: CULP01CH |
|
C200011 |
FILE MATCH WITH DATABASE INPUT INVALID The user specified database input on an INPUT parameter, but the system detected more than one INPUT parameter in the CA Culprit parameter stream. File matching is not permitted with database input. Severity: F Modules: CULPINCH |
|
C200012 |
SUBSCHEMA NAME MISSING FOR DATABASE ACCESS The user requested CA IDMS/DB or IMS access on the INPUT parameter, but the SS= specification is either missing or incorrectly coded. Severity: F Modules: CULPFIKL |
|
C200013 |
TOKEN TOO LONG - TRUNCATED A field name that exceeds 32 characters was specified on an input parameter. The flagged characters (underscored with asterisks) were truncated by CA Culprit. Severity: W Modules: CULPDFRE GETWORD SUBROUTINE |
|
C200014 |
LITERAL IS INVALID An invalid literal was coded on an INPUT parameter. The literal either has an invalid format or is in the wrong place (that is, out of sequence) in the parameter. The probable cause of this error is that no closing quotation mark was entered. The literal value is underscored with asterisks and set to a null status. Severity: W, E Modules: CULPDFRE GETWORD SUBROUTINE AND SUBMODULES CULP78CH 'CALL' SPECIAL FUNCTION |
|
C200015 |
PATH-ID ASSUMED ** The system encountered no primary path ID on a PATH parameter; CA Culprit assumes a path ID of **. Severity: W Modules: CULPPACH |
|
C200016 |
SET-NAME ASSUMED A parenthesized value was coded on a PATH parameter following the record type name but with no preceding comma. The flagged value (underscored with asterisks) is more than 2 characters long and is assumed to be a CA IDMS/DB set name. Severity: W Modules: CULPPACH |
|
C200017 |
ASSUMING KEY FOR IDMS ACCESS A KEY or KEYFILE parameter preceded an INPUT parameter in the parameter stream. CA Culprit assumes that the input is a CA IDMS/DB database. Severity: W Modules: CULPKECH |
|
C200018 |
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 Modules: CULP78CH AND LOWER-LEVEL MODULES |
|
C200019 |
VERSION NUMBER IS INVALID An invalid version number qualifies the subschema name on the INPUT parameter. The number is invalid for one of the following reasons:
Severity: F Modules: CULPFIKL |
|
C200020 |
AUTO-HEADER ORIGIN CODE INVALID A header-origin code other than HF, HH, or HR was specified on a type 5 or type 6 edit parameter. The invalid entry is underscored with asterisks. Severity: E Modules: CULP45V7 |
|
C200021 |
AUTO-HEADER LITERAL OVERFLOW The sum of each auto-header literal exceeds 99 characters. Make the literals shorter and resubmit the job. Severity: W Modules: CULP46CH CULPRECH |
|
C200022 |
DECIMAL POINT CODE IS INVALID This can be a W- or E-level message:
Severity: W, E Modules: CULP46C7 (W level) CULP46CH (E level) CULP01CH (E level) |
|
C200023 |
NON-NUMERIC PARAMETER This can be a E- or F-level message:
Severity: E, F Modules: CULPDFRE LEADZERO SUBROUTINE (E level) CULPFIKL (F level) CULPPRCH (F level) |
|
C200024 |
NUMERIC PARAMETER RIGHT JUSTIFIED In the fixed portion of the parameter, the user coded a numeric field that is not right-justified. CA Culprit moves the numeric field to the right and fills the field with zeros on the left. The adjusted field is underscored with asterisks. Severity: W Modules: CULPDFRE LEADZERO SUBROUTINE |
|
C200025 |
NOT AUTHORIZED FOR NON-IDD ACCESS A user who has IDD but whose installation is not licensed to use CA Culprit has tried to run a CA Culprit report against a file other than the data dictionary. Severity: F |
|
C200026 |
UNABLE TO OPEN ddname z/OS users only—CA Culprit could not open the file associated with ddname and cannot continue processing. The error probably occurred because of a JCL error. Severity: F Modules: CULXnnnn MODULES |
|
C200027 |
MATCH KEY DATA TYPE CONFLICTS WITH PREVIOUS KEY The system encountered a REC parameter that defines a match key for the current file, but the date type does not match the data type of the corresponding match key on a previous file. Match keys on a given level (for example, primary, secondary) must be either all numeric or all alphanumeric. |
|
C200028 |
ALTERNATE ASSIGN INVALID z/VSE users only—An invalid file name was specified for the DD2= option on the INPUT parameter. The invalid field name is underscored with asterisks. Severity: F Modules: CULPFIKL |
|
C200029 |
FILE TYPE OR QUALIFIER INVALID The message is an E- or F-level message as follows:
The file type or qualifier is invalid for one of the following reasons:
Correct your CA Culprit code and resubmit the job. Severity: E, F Modules: CULPOUCH (E level) CULPFIPL (F level) CULPKFCH (F level) |
|
C200030 |
RECORD SIZE IS MISSING OR INVALID This can be a W-, E-, or F-level message:
Correct the code on the OUTPUT parameter and resubmit the job.
Severity: W, E, F Modules: CULP2JC7 (W level and E level) CULPFIPL (F level) |
|
C200031 |
RECORD TYPE IS INVALID This can be a W- or F- level message:
Severity: W, F Modules: CULPFIPL |
|
C200032 |
BLOCK SIZE MISSING OR INVALID This can be a W-, E-, or F-level message:
Severity: W, E, F Modules: CULPFIPL (W level) CULPOUCH (W level and E level) |
|
C200033 |
USER LABELS SPECIFIED IN MATCH RUN The user coded LT=A (that is, standard and user labels) on one or more INPUT parameters in a match-file run. The invalid entries are underscored with asterisks. Do not use label A in a match-file run. Severity: F |
|
C200034 |
KEYWORD PARAMETER INVALID keyword-option A parameter contains an invalid keyword (for example, MK=). The keyword is invalid for one of the following reasons:
Severity: F Modules: CULP0 CULPDFRE SUBMODULES CULPFIKL |
|
C200035 |
LABEL TYPE IS INVALID This can be a W- or F- level message:
Severity: W, F Modules: CULPFIKL |
|
C200036 |
SPECIAL POSITIONING INVALID This can be a W- or F-level message:
Severity: W, F Modules: CULPFIF7 |
|
C200037 |
BLOCK SIZE CHANGED TO NEXT MULTIPLE OF RECORD SIZE An INPUT, KEYFILE, or OUTPUT parameter specifies a block size that is not a multiple of the record size (for a fixed-length record). CA Culprit rounds the block size up to the next multiple of the record size. Note: If the assumed block size is not the actual block size of the file, the I/O module may loop reading the first block on the file. Severity: W Modules: CULPFIF7 |
|
C200038 |
INVALID USE OF RESERVED WORD A reserved keyword was used illegally; reserved keywords cannot be used as field names. For a complete list of key and reserved words, see the CA Culprit for CA IDMS Reference Guide. Severity: E Modules: CULP78BL CULPSECH CULP46CH CULP01CH CULP15CH |
|
C200039 |
EMBEDDED BLANKS IN ALPHA PARAMETER A value in the fixed portion of a CA Culprit parameter contains embedded blanks. This message is followed by one that indicates which field is in error. Severity: E Modules: CULPDFRE IMBLANK SUBROUTINE |
|
C200040 |
ALPHA PARAMETER LEFT JUSTIFIED A value in the fixed portion of a CA Culprit parameter does not begin in the expected column. CA Culprit left-justifies the value and pads the right with blanks. Severity: W Modules: CULPDFRE IMBLANK SUBROUTINE |
|
C200041 |
SCHEMA NAME IS MISSING OR INVALID This can be a W- or F-level message:
Severity: W, F Modules: CULPDRES (W level) CULPFIKL (F level) |
|
C200042 |
FILE NAME INVALID The user coded a file name in an FN= keyword expression on an INPUT parameter that exceeds the system limit of 32 characters. Severity: F Modules: CULPFIV7 CULPKFV7 |
|
C200043 |
MATCH KEY FIELD INVALID CA Culprit detected an invalid match-key field description (that is, position and length) on an INPUT parameter. The field definition places part or all of the field beyond the end of the record, as defined by the record size. Severity: F Modules: CULPFIV7 |
|
C200044 |
NO CARDS AFFECTED BY =macro-clause CA Culprit located the indicated keyword on an =DROP or =CHANGE clause of an =MACRO parameter, but a matching operand could not be found on a copied parameter. CA Culprit continues processing. Severity: W Modules: CULP0 |
|
C200045 |
RESULT FIELD LEFT UNCHANGED sequence-number The =MACRO statement resequenced a set of parameters. One of the resequenced parameters contains a result-field sequence number that is not specified in columns 5 through 7 on any of the parameters that were resequenced. The result-field sequence number is unchanged. CA Culprit assumes that the sequence number will be resolved elsewhere. Severity: W Modules: CULP0 CULPUNUM |
|
C200046 |
ERROR READING CULPRIT PARAMETERS FROM culprit-source-library (CONT) ERROR OCCURRED DURING OPEN/PW CHECK/READ (CONT) MEMBER NOT FOUND (CONT) MEMBER REQUESTED AT TIME OF ERROR WAS member-name CA Culprit could not access source code stored in a source library or inline code. Possible reasons are:
CA Culprit prints the name of the member at the time of the error. Severity: F Modules: CULP0 CULPUSE |
|
C200050 |
PARAM= OPTION INVALID The system encountered the PARAM= keyword expression in the CA Culprit parameter stream and expected one of the associated keywords (that is, LIST, NOLIST, or EJECT), but an appropriate keyword option was not found. CA Culprit ignores the parameter. Severity: W Modules: CULP0 |
|
C200051 |
NESTED LIBRARY/DICTIONARY REQUEST REJECTED A nested =COPY, =MACRO, or REPORT= (data dictionary report request) statement was encountered in code that was inserted into the parameter stream by an =COPY, =MACRO, or REPORT= statement. The nested request and all associated statements (for example, =CHANGE, =DROP, =MEND) are ignored. Severity: F Modules: CULP0 |
|
C200052 |
INPUT CARD DROPPED This message confirms that the user coded an INPUT=NO keyword expression on an =COPY or =DROP statement. CA Culprit assumes that the user will supply an alternate INPUT parameter. Severity: W Modules: CULP0 |
|
C200053 |
REC CARD DROPPED - START POSITION IS INVALID The CA Culprit code includes a REC parameter with a starting position of zero (0) before any INPUT parameter. The REC parameter is ignored by CA Culprit. Note: If the REC parameter occurs after the INPUT parameter, CA Culprit interprets the start position as a match-file signal byte and relocates it 1 byte beyond the end of the record. Severity: W Modules: CULP0 |
|
C200054 |
NO EXPANSION DONE - NOT ENOUGH ARGS The system encountered a symbolic parameter in the form &.&x. in a copied =MACRO parameter set, but no associated argument exists in the =MACRO instruction. Severity: W Modules: CULP0 |
|
C200055 |
NO EXPANSION DONE - ARG TOO LONG An argument on an =MACRO parameter is too long to fit in the available space on the copied parameter card. Severity: W Modules: CULP0 |
|
C200056 |
NEW SEQUENCE NUMBER GREATER THAN 999 The =MACRO facility generated a sequence number that exceeds the system limit of 999 while it resequenced type 7 or type 8 process definition parameters. CA Culprit retains the original sequence number. Severity: F Modules: CULP0 CULPUNUM |
|
C200057 |
UNDEFINED MATCH KEY ON PRIOR FILE match-key-name The named match-key field was not resolved on the file preceding the file that is currently being processed. The match key is not resolved because either the REC parameter that defined the field has E-level errors or the field is not defined on a REC parameter. Severity: F Modules: CULP0 |
|
C200060 |
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 record. The field position limit was set on the INPUT or OUTPUT parameter. Severity: W Modules: CULP0 |
|
C200061 |
=MEND MISSING The system encountered an =MACRO instruction in the CA Culprit parameter stream, but no corresponding =MEND instruction was found. To correct this error, add an =MEND instruction and resubmit the job. Severity: F Modules: CULP0 |
|
C200062 |
MATCH WILL TAKE PLACE This message confirms that CA Culprit successfully processed two or more INPUT match-file parameters. Severity: I Modules: CULP0 |
|
C200063 |
NO INPUT CARD FOUND FOR FILE ddname/file-name The system did not encounter an INPUT parameter in the CA Culprit parameter stream. Severity: E Modules: CULP0 |
|
C200064 |
SEQUENCE TABLE OVERFLOW An attempt was made to resequence more than 250 type 7 or type 8 process definition parameters with one =MACRO statement. The parameters must be split into two or more groups with a maximum of 250 parameters in each group. These groups can then be inserted and renumbered in separate =MACRO statements. Severity: F Modules: CULP0 |
|
C200065 |
CHANGE CARD TABLE OVERFLOW An internal system error occurred. Call CA Technical Support. Severity: F Modules: CULP0 |
|
C200066 |
TOO MANY CARDS IN MACRO REQUEST The CA Culprit code contains more than 40 lines, including continuation lines between an =MACRO instruction and the corresponding =MEND instruction. Reduce the number of lines and resubmit the job. Severity: F Modules: CULP0 |
|
C200067 |
CONTROL CARD INVALID An equal sign was coded in column 1, but the equal sign is not followed by a recognizable keyword (that is, CHANGE, COPY, DROP, MACRO, or MEND). Severity: F Modules: CULP0 |
|
C200068 |
EXTRANEOUS =MEND An =MEND instruction was encountered in the CA Culprit parameter stream with no corresponding =MACRO instruction. Severity: F Modules: CULP0 |
|
C200069 |
OPERAND(S) MISSING Either an =COPY parameter does not contain any operands (for example, a member name or an asterisk (*)) or a keyword of the =COPY parameter does not contain an operand. CA Culprit either flags the column preceding the next keyword or the last column of the parameter with an asterisk. Severity: F Modules: CULP0 CULPCPC7 |
|
C200070 |
OPERAND INVALID operand The indicated operand is either illegal in the context of the keyword with which it is associated or exceeds the maximum length allowable for the operand type. Severity: F Modules: CULP0 CULPCPC7 |
|
C200071 |
MEMBER NAME IS INVALID CA Culprit detected a member or module name on an =COPY or =MACRO instruction that is either missing or invalid. The length of the member or module name cannot exceed the system limit of 32 characters. The name of a module that is stored in the data dictionary must be enclosed in single quotation marks. Severity: F Modules: CULP0 CULPCPC7 |
|
C200072 |
REPORT NUMBER IS INVALID An illegal report number was specified on a 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: F Modules: CULP0 CULPDFRE CULPIDDR |
|
C200073 |
TOO MANY PARAMETERS OF TYPE keyword More than 20 occurrences of the named keyword were specified in single =MACRO statement. Keyword may have the following values: TYPE=, REC=, CNST=, or OLD=. Severity: F Modules: CULP0 |
|
C200074 |
KEYWORD EXPECTED keyword This message occurs for one of two parameters:
Severity: F Modules: CULP0 CULPSEC7 |
|
C200075 |
TOO MANY ARGUMENTS This can be a W- or a F-level message:
Severity: W, F Modules: CULP78CH 'CALL' SPECIAL FUNCTION (W level) CULP0 (F level) |
|
C200076 |
TOO MANY TOKENS The system encountered more than 100 keywords, operands, or delimiters in a single =DROP instruction or =CHANGE instruction. To correct this error, split the instruction into two or more =CHANGE or =DROP instructions. Severity: F Modules: CULP0 |
|
C200077 |
ARGUMENT IS INVALID An argument that exceeds 53 characters was specified on an =MACRO instruction. Argument length includes bounding quotation marks, if they are present.) Severity: F Modules: CULP0 |
|
C200078 |
RIGHT PARENTHESIS MISSING This can be a W- or F-level message:
Severity: W, F Modules: CULP78CH 'CALL' SPECIAL FUNCTION (W level) CULP0 (F level) IDMSGEXP OR IDMSGCND—CULP0 (F level) |
|
C200079 |
ERRONEOUS TOKEN AFTER character-string An illegal keyword, operand, or delimiter was coded after the indicated character string on an =CHANGE or =DROP instruction. CA Culprit may compress multiple blanks into a single blank in the message. Severity: F Modules: CULP0 |
|
C200080 |
REPORT REQUEST PARAMETER report-number This message prints to the left of any REPORT= parameter. Severity: I Modules: CULPIDDR |
|
C200081 |
REPORT REQUESTED NOT ON DICTIONARY module-name CA Culprit requested either a data dictionary report module (for example, DREPORT 007) or a module in an =COPY or =MACRO parameter, but could not find the requested module in the data dictionary being accessed. CA Culprit also prints the version number of the module if a value was supplied in the input parameter stream. Severity: F Modules: CULPIDDR |
|
C200082 |
FILE REQUESTED NOT ON DICTIONARY file-name File-name and version-number (if defined on an INPUT parameter) were coded as the operand of an FN= keyword expression, but the indicated file (and version) does not exist in the data dictionary. CA Culprit also prints the version number of the file if a value was supplied in the input parameter stream. Severity: F Modules: CULPIDDR |
|
C200083 |
IDD NOT SUPPORTED A data dictionary request was encountered (that is, an FN= keyword expression on the INPUT parameter, a module name that follows either an =COPY or =MACRO instruction, or a REPORT= instruction), but IDD is not installed. Severity: F Modules: CULPIDDR |
|
C200084 |
CULPRIT/DIRECTORY INTERFACE idms/culpdres-version-number This message appears the first time CA Culprit tries to access the data dictionary. The variable portion of the message identifies which version of the CULPDRES module is being used. Severity: I Modules: CULPDRES |
|
C200085 |
UNABLE TO ACCESS DATA DICTIONARY The data dictionary cannot be opened or has been found to be incompatible with the CA IDMS/CA Culprit interface module. The message ABORTING CULPDRES, described as follows, always accompanies this message, followed by messages that display the contents of the IDMS communications block. Severity: F Modules: CULPDRES |
|
C200086 |
ABORTING CULPDRES idms-version culprit-version (CONT) DML SEQUENCE sequence-number (CONT) ERROR STATUS error-status-code (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 CA Culprit detected an error that relates to the data dictionary. If the error status is VERS, the database access module (that is, CULPDRES) is not compatible with the data dictionary indicated by idms-version. If the error status is numeric, refer to CA IDMS Messages and Codes Guide. for an explanation of the code. The messages that follow this message display the contents of the IDMS communications block. This error can occur when CA Culprit encounters an error accessing:
Severity: F Modules: CULPDRES |
|
C200094 |
NESTED OCCURS ON GENERATED REC PARAMETER field-name The named field cannot be defined to CA Culprit because it lies within a nested repeating group defined to a database record accessed by CA Culprit. Severity: E Modules: CULPDRES |
|
C200095 |
UNKNOWN SUBSCHEMA subschema-name (CONT) SCHEMA schema-name (CONT) VERSION version-number CA Culprit cannot find the named subschema, schema, and version number in the data dictionary. The schema name and version print only if the CA Culprit code specified schema and version number values. Severity: F Modules: CULPDRES |
|
C200098 |
SET NAME UNKNOWN TO SUBSCHEMA set-name The user coded a set name on a PATH parameter that is not known to the subschema named on the INPUT parameter. Severity: F Modules: CULPDRES |
|
C200099 |
NON-EXISTENT RECORD NAME record-name A record name that is not known to the data dictionary was coded on a PATH parameter or is a qualifier for a field name. Severity: F Modules: CULPDRES |
|
C200100 |
UNABLE TO DEFINE field-name CA Culprit cannot generate a field definition for the named field in a run that accesses the data dictionary. This message probably occurs because CA Culprit does not recognize the field name. Correct the field name and resubmit the job. Severity: E Modules: CULPDRES |
|
C200101 |
RECORD NAME UNKNOWN TO SUBSCHEMA record-name The record named on the PATH parameter is not defined to the subschema named on the INPUT parameter. Correct the code and resubmit the job. Severity: F Modules: CULPDRES |
|
C200102 |
UNABLE TO RESOLVE PATH path-id CA Culprit cannot resolve a reference to a path ID. This error can occur if an invalid record or set invalidates the PATH For information on how to specify a valid path, see the CA Culprit for CA IDMS Reference Guide. Severity: F Modules: CULPDRES |
|
C200105 |
FIELD NAME UNKNOWN TO LEGAL RECORD field-name CA Culprit named a field that is defined to the data dictionary but does not exist in any of the records defined on a PATH parameter or associated with a file named on an INPUT parameter. Correct the field name and resubmit the job. Severity: E Modules: CULPDRES |
|
C200106 |
FIELD NAME UNKNOWN TO DICTIONARY field-name CA Culprit cannot find the named field in the data dictionary. This message may be followed by a record name and level number if these were used to qualify the field. Severity: E Modules: CULPDRES |
|
C200107 |
INCONSISTENT PATH ENTRY RECORD record-name The user coded an entry record on a PATH parameter that differs from the entry record that was specified on a previous PATH parameter. All non-dummy PATH parameters in a CA Culprit run must specify the same entry record. Severity: F Modules: CULPDRES |
|
C200108 |
ENTRY RECORD SET INVALID set-name An invalid set name was specified on a PATH parameter for the entry record. The entry record set must be an index set known to the subschema that was specified on the INPUT parameter. Severity: F Modules: CULPDRES |
|
C200109 |
(CONT) RECORD NAME record-name (CONT) SET NAME set-name The user coded an illegal record name on the PATH CA Culprit could not relate the named record to a previous record for one of the following reasons:
Severity: F Modules: CULPDRES |
|
C200112 |
MAXIMUM NUMBER OF IDMS RECORD NAMES EXCEEDED More than 256 record names were specified on a PATH parameters. Severity: F Modules: CULPDRES |
|
C200113 |
KEYFIELD NAME INVALID key-field-name CA Culprit detected an invalid key-field name on a KEY parameter. The key-field name is invalid for one of the following reasons:
Severity: F Modules: CULPKCC7 CULPDRES |
|
C200114 |
INCONSISTENT PATH ENTRY SET set-name The user coded a set name for the entry record on a PATH parameter that differs from the set name specified for the entry record on a previous PATH parameter. All PATH parameters in a CA Culprit run must specify the same entry record and the same set name for the entry record. Severity: F Modules: CULPDRES |
|
C200115 |
SET NAME IGNORED ON DUMMY PATH ENTRY set-name The PATH parameter specifies a dummy path ID (that is, ──), indicating that CA Culprit will use the DB-EXIT facility to access the named records. CA Culprit ignores all set names specified on a PATH parameter that specifies a dummy path ID. Severity: W Modules: CULPDRES |
|
C200116 |
AUTO-HEADERS ON 6-CARD BUT NOT T-ONLY REPORT A header-origin code was specified on a type 6 edit parameter, but the OUTPUT parameter does not specify a totals-only report. Severity: E Modules: CULPTBL |
|
C200117 |
AUTO-HEADERS ON BOTH 5-CARDS AND 6-CARDS The CA Culprit code contains header origin codes (that is, HH, HR, or HF) on both type 5 and type 6 edit parameters. Header origin codes can appear on type 6 edit parameters only for a totals-only report. Additionally, the codes can be defined for either type 5 or type 6 edit parameters, but not for both. Severity: E Modules: CULPTBL |
|
C200118 |
AUTO-HEADERS NOT GENERATED—POSITION IS ZERO A header-origin code was specified on a type 5 edit parameter for an output data field, but this field is 0 (zero). Severity: E Modules: CULPTBL |
|
C200119 |
AUTO-HEADER REQUEST CANNOT BE RESOLVED rrllpppp The CA Culprit codes contains an auto-header request (that is, HR, HR, or HH) on a type 5 or 6 edit parameter, but no literal is associated with the specified field. The parameter that contains the auto-header request is identified as rrllpppp as follows:
Severity: E Modules: CULPTBL |
|
C200120 |
AUTO-HEADER GENERATED LINE NUMBER EXCEEDS 8 frrllpppp The system encountered a request for an auto-header in the input parameter stream, but the user-supplied or automatically generated headers occupy all eight available header lines. The edit parameter that contains the auto-header request is identified as rrllpppp, as follows:
Severity: E Modules: CULPTBL |
|
C200121 |
RUN CANCELLED DUE TO INSUFFICIENT STORAGE FOR CULPRIT-module (CONT) NUMBER OF BYTES REQUESTED bytes CA Culprit was unable to obtain the necessary storage to continue processing in the CULP0 step. The names of the CA Culprit module CSECT requesting the core and the table or buffer being requested are printed in the variable portion of the message. Increase the region size by at least as much core as specified in the continuation of the message. Possible CSECT and table name values are shown as follows: CSECT (TABLE or BUFFER) Description
CULPTBL (FILTABLE)—File statistics table CULPTBL (REPTABLE)—Report statistics table CULPTBL (NAMTABLE)—Runtime names table CULPTBL (AUTO4TBL)—Auto-header literal table CULPTBL (GEN4TBL)—Auto-header entry table CULP0 (OLDNEWSQ)—=CHANGE sequence number table CULP0 (G78BLOCK)—=CHANGE type-7 and 8 branch cards CULP0 (MXPTBL)—=MACRO expansion table CULP0 (CHPRMTBL)—=CHANGE parameter table CULP0 (DRRECTBL)—=DROP REC table CULP0 (DRCONTBL)—=DROP work field table CULP0 (DRNUMRNG)—=DROP range table CULP0 (CULLIB BUFFER)—=COPY/=MACRO z/OS library buffer CULPDFRE (GSNENTRY)—Generated type-15 name table block CULPPAC7 (PATHTBL)—PATH/record table block CULPKCC7 (KEYTBL)—Key entry table block Severity: F Modules: CULPGTMN |
|
Message ID |
Message |
|---|---|
|
C200123 |
POSITION INVALID This can be an E- or F-level message:
Severity: E, F Modules: CULPREC7 (E level) CULP46C7 (E level) CULPKFC7 (F level) |
|
C200124 |
SIZE IS INVALID This can be a W-, E-, or F-level message:
DATA TYPE DP= MAXIMUM SIZE SPECIFICATION Alphanumeric 37,767 FP Yes 16 FP No 8 All others Yes 31 All others No 15
DATA TYPE MAXIMUM FIELD SIZE
' ' 32,760 1 4 2 31 3 16 4 15 5 32 bits
Severity: W, E, F Modules: CULPREC7 (E level) CULP46C7 (W level and E level) CULPKFC7 (F level) |
|
C200125 |
DATA TYPE IS INVALID The system encountered an invalid or illegal data type on a REC parameter. For numeric field data types, code date types from 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 Modules: CULPREC7 |
|
C200126 |
START POSITION OF 1 ASSUMED The user coded a link ID on a GROUP REC parameter, but the starting position is not equal to 1. A starting position of 1 indicates that the starting position is relative to the end of the group that was specified by link ID. CA Culprit ignores the invalid specification and sets a starting position of 1 for the group. The invalid entry is underscored with asterisks. Severity: W Modules: CULPREC7 |
|
C200127 |
NUMBER OF OCCURRENCES INVALID The user coded an invalid occurrence count specification on a GROUP REC parameter. The specification is either a nonnumeric value or exceeds the system limit of 32K. The invalid entry is underscored with asterisks. Severity: E Modules: CULPREC7 CULP01C7 |
|
C200128 |
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: CULP46C7 |
|
C200129 |
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. The invalid character is underscored with an asterisk. Severity: E Modules: CULP46C7 |
|
C200130 |
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$, F-, FB, FC, FD, FF, FM, FN, FP, FS, FU, FW, FZ, or F0 through F9. Severity: E Modules: CULP46C7 |
|
C200131 |
TOTAL/DETAIL CODE INVALID The total/detail code specified on an OUTPUT parameter is not valid. Valid codes are a T, D, or blank. Severity: E Modules: CULPSOCH |
|
C200133 |
LINES/PAGE INVALID An OUTPUT parameter specifies an invalid LP= keyword expression for the number of lines for each report page. The value is either nonnumeric or exceeds 32K. The invalid specification is underscored with asterisks when the error appears in the Sequential Parameter Listing. Severity: E Modules: CULPSOCH |
|
C200134 |
SORT KEY IS INVALID CA Culprit detected an invalid sort key on a SORT parameter. This error can occur if the user specified more than 20 sort keys for one report, or if the sort key field is not a valid input or work field name. Severity: E Modules: CULPSOCH |
|
C200135 |
CULPRIT INPUT BUFFER CAPACITY EXCEEDED The user coded a value for the input record size, but the value exceeds the system buffer limit of 32K. For standard CA Culprit runs, the input buffer size is equal to the record size that was specified on the INPUT parameter. For match-file runs, the input buffer size is the sum of the record sizes of all input files, plus 1 byte per non-dummy file and 1 byte per run. Severity: F Modules: CULP0 |
|
C200136 |
MAXIMUM NUMBER OF FILES EXCEEDED The system encountered more than 32 INPUT parameters in a run that accesses nondatabase files. Severity: F Modules: CULP0 |
|
C200137 |
SECURITY MODULE NOT LINKED The installation security option in the CULPPROF program specifies YES, but CA Culprit cannot enforce security because the CULPDRES module has not been linked with the CULP0 module. Severity: F Modules: CULPDFRE |
|
C200138 |
INSTALLATION SECURITY OPTION IS option The installation security option specifies either YES or NO, depending on the option specified for the installation parameter, CULL-SECURE. Severity: I Modules: CULPDFRE |
|
C200139 |
OPERATION CODE INVALID This can be an E- or F-level message:
Severity: E, F Modules: CULP78C7 (E level) CULPSTKL (F level) |
|
C200140 |
INITIAL VALUE INVALID This can be an E- or F-level message:
Severity: E, F Modules: CULP01C7 (E level) CULPKCC7 (F level) |
|
C200141 |
LENGTH OF FIRST LITERAL VALUE USED A multiply-occurring work field parameter (that is, array) specifies initial values with different lengths. CA Culprit uses the length of the first value. It truncates values that are longer and pads shorter values on the right and underscores them with asterisks. Severity: W Modules: CULP01C7 |
|
C200142 |
SEQUENCE NUMBER IS INVALID The user coded an invalid sequence number on a type 7 or type 8 process definition parameter. The invalid entry is underscored with asterisks. To correct this error, use either numeric or blank sequence numbers. Severity: E Modules: CULP78C7 |
|
C200143 |
SEL STATEMENT OUT OF SEQUENCE The system encountered a SELECT/BYPASS parameter that preceded an INPUT, KEYFILE, or referenced PATH parameter. To correct this error, reorder the parameters so that appropriate INPUT, KEYFILE, or PATH parameters precede the SELECT/BYPASS parameter, and resubmit the job. Severity: F Modules: CULPSEC7 |
|
C200144 |
RECORD LEVEL IS INVALID This can be an E- or F-level message:
Severity: E, F Modules: CULPDFRE (E level) CULPSEC7 (F level) |
|
C200145 |
UNBALANCED PARENTHESES CA Culprit detected an unequal number of opening and closing parentheses on a SELECT/BYPASS or process definition parameter. Severity: F Modules: CULPSTKL CULP78AL |
|
C200146 |
RECORD OR SET NAME IS INVALID The user coded an invalid record name on a SELECT/BYPASS parameter or an invalid record or set name on a PATH parameter. This error can occur if the name is too long or if the name is not a valid COBOL name. The invalid entry is underscored with asterisks. Severity: F Modules: CULPSEC7 |
|
C200147 |
PATH-ID INVALID OR DUPLICATED The flagged path ID is either invalid or exists on another PATH parameter. Severity: F Modules: CULPSEC7 CULPPACH |
|
C200148 |
PASSWORD MISSING OR INVALID The CA Culprit code either specifies an invalid password on a PROFILE, INPUT, or OUTPUT parameter or fails to specify a password when required. Severity: F Modules: CULPFIV7 |
|
C200149 |
INVALID NUMERIC TOKEN An invalid numeric string has been coded on a parameter that applies to the entire run (for example, SELECT and INPUT parameters). The string is invalid because it either exceeds a maximum value or is less than the minimum allowed. CA Culprit underscores the invalid string with asterisks. Severity: F Modules: CULPFIPL CULPFIKL |
|
C200150 |
DUPLICATE LINE NUMBER IGNORED CA Culprit ignored a duplicate line number in a list of line numbers for a PICK, UNPICK, DROP, TAKE, or RELS operation on a process definition parameter. The invalid entry is underscored with asterisks. Severity: W Modules: CULP78CH |
|
C200151 |
TOO MANY OPERANDS The user coded too many operation codes on a COMPUTE statement, IF statement, or SELECT/BYPASS statement. The maximum number is 32 test conditions. Severity: E Modules: CULP78AL CULPSTKL |
|
C200152 |
TOO MANY OPERATORS A COMPUTE statement specifies too many operation codes. Severity: E Modules: CULP78AL |
|
C200153 |
OPERAND INVALID operand An operand was coded on a report-specific parameter (for example, OUTPUT and edit parameter) that is either illegal for the keyword with which it is associated, or exceeds the maximum length allowable for the operand type. Severity: E Modules: CULP |
|
C200154 |
KEY FIELD INDICATORS MISSING OR INVALID The user coded a KEYFILE parameter with an invalid or missing KF= keyword expression. The KF= value is invalid if it specifies an invalid keyfield position or length. Severity: F |
|
C200155 |
INCREMENT VALUE INVALID The system encountered an invalid increment on a type 15 implied subscript parameter. Valid increments are numeric literals in the range 1 through 4095. The invalid entry is underscored with asterisks. Severity: E |
|
C200156 |
GROUP ID IS INVALID A REC parameter that specifies the keyword GROUP specifies an invalid group ID. The group ID is a 2-byte alphanumeric field. Severity: F Modules: CULP0 |
|
C200157 |
INCONSISTENT DD SPECIFICATIONS This can be an E- or F-level message:
Severity: E, F Modules: CULPOUKL (E level) CULPFIKL (F level) |
|
C200158 |
SIGNAL BYTE IGNORED FOR DUMMY OR UNDEFINED FILE A REC parameter with a starting position of zero (0) was coded for a dummy file or was encountered before the first INPUT parameter in the parameter stream. Severity: W Modules: CULPO |
|
C200159 |
SELECT AND BYPASS MAY NOT BE MIXED Both SELECT and BYPASS parameters were encountered for the same file. Either SELECT or BYPASS, but not both, can be codes for each input file. Severity: E Modules: CULPSCH |
|
C200160 |
E-LEVEL ERRORS IN SEL STATEMENT E-level errors in a SELECT or BYPASS parameter force CA Culprit to terminate the run. Severity: F Modules: CULPSECH |
|
C200161 |
DD SPECIFIED FOR PRINTED OUTPUT The OUTPUT parameter specifies printed output (that is, the file type is omitted), but a DD= option was also specified for the same report. Because CA Culprit automatically makes assignments to a standard print file, no user-written specification is needed. The invalid DD= entry is underscored with asterisks. Severity: E Modules: CULPOUKL |
|
C200164 |
INVALID BREAK CODE A SORT parameter specifies an invalid break code. Valid codes are 1, 0, - (a hyphen), and +. Severity: E Modules: CULPSOCH |
|
C200165 |
COLUMN ONE IGNORED CA Culprit ignored a mispunch in column 1. The invalid entry is underscored with asterisks. Severity: W Modules: CULPDFRE |
|
C200166 |
SUBSCRIPT IS INVALID An invalid subscript value was coded. The value is nonnumeric, exceeds 32,767, or is an invalid field name. The invalid specification is underscored with asterisks. Severity: E Modules: CULPDFRE |
|
C200167 |
DUPLICATE OUTPUT OR SORT PARAMETER CA Culprit encountered more than one OUTPUT or SORT parameter for a report. Severity: E Modules: CULPTBL |
|
C200168 |
PARAMETER TYPE ILLEGAL The system encountered an illegal parameter in the CA Culprit parameter stream. To evaluate this error, review the Sequential Parameter Listing. CA Culprit also flags a DATABASE parameter if it is not the first CA Culprit parameter in the input stream or if it appears within a used dictionary module. Severity: F Modules: CULPDFRE |
|
C200169 |
UNAUTHORIZED USER/PASSWORD COMBINATION USER= and PASSWORD= keywords appear on the PROFILE parameter, but either the named user is not defined in the data dictionary or the specified password is incorrect. Severity: F Modules: CULPDRES |
|
C200170 |
FILE NOT DEFINED TO DIRECTORY/DICTIONARY The file named in an FN= keyword expression is not defined to the data dictionary. Severity: F Modules: CULPDRES |
|
C200171 |
ACCESS NOT AUTHORIZED FOR FILE/SUBSCHEMA The user specified on the PROFILE parameter is not authorized to access the file or subschema specified on the INPUT parameter. Severity: F Modules: CULPDRES |
|
C200172 |
NO FILE NAME SPECIFIED CA Culprit processed all keyword expressions on an INPUT parameter and determined the following:
Severity: F Modules: CULPFIKL |
|
C200173 |
DIRECTORY/DICTIONARY OVERRIDE ATTEMPT The OVERRIDES ARE NOT ALLOWED option is in effect in the data dictionary for the user that was named on the PROFILE parameter. One of the following conditions is true:
Severity: F Modules: CULPFIKL |
|
C200174 |
RECORD DESCRIPTION OVERRIDE ATTEMPT CA Culprit security is in effect in the data dictionary and the user has coded an entry other than a comment on a REC parameter. One of the following conditions is true:
Severity: F Modules: CULPRECH |
|
C200175 |
DICTIONARY SECURITY OPTION IS security-level This message tells you what level of security is in place. CA Culprit prints either ON or OFF for security-level. Severity: I Modules: CULPDRES |
|
C200176 |
DIRECTORY/DICTIONARY FILE(DEVICE) TYPES file-type device-type This message identifies the file and device type for a file that was defined in the data dictionary and was named in an FN= specification on an INPUT or a KEYFILE parameter. Severity: I Modules: CULPDRES |
|
C200177 |
LEFT PAREN MISSING CA Culprit encountered a field that follows the module name in a CALL statement on a type 7 parameter. The place where the left parenthesis was expected is underscored with asterisks. Severity: E Modules: CULP78CH |
|
C200178 |
FIELD NAME INVALID CA Culprit detected an invalid name in a CALL instruction on a type 7 parameter. The invalid entry is underscored with asterisks. Severity: E Modules: CULP78CH |
|
C200179 |
KEY FIELD EXTENDS BEYOND RECORD The user specified a KF= keyword expression on a KEYFILE parameter but the starting position plus the field size caused the keyfield to extend beyond the last position of the record. Note that the user determines the record size of the keyfile in one of two ways:
Review the layout of the keyfile and make the appropriate modifications to the KEYFILE parameter. Severity: F Modules: CULPFIKL |
|
C200180 |
SPECIAL POSITIONING SPECIFIED FOR NON-TAPE FILE The system encountered a request in the LT= keyword expression to bypass the indicated files or blocks, but the user did not specify tape input. The LT= option is valid only for tape input. Severity: F Modules: CULPFIKL |
|
C200181 |
DP= INVALID ON GROUP REC PARAMETER CA Culprit ignored a DP= specification on a GROUP REC parameter. A DP= specification can be coded on ELMNT REC parameters. Severity: W Modules: CULPRECH |
|
C200182 |
DP= SPECIFICATION IGNORED FOR MATCH The user coded a DP= specification for a match-key field. The match is performed as though the field represented an integer value. Severity: W Modules: CULP0 |
|
C200183 |
USER EDIT MASK EXCEEDS 64 CHARACTERS A user edit mask exceeds the system limit of 64 characters. Severity: E Modules: CULP46CH |
|
C200184 |
SIZE OF ZERO IS ILLEGAL CA Culprit encountered a size specification of SZ=0 on a type 4, type 5, or type 6 edit parameter. Severity: E Modules: CULP46CH |
|
C200185 |
SCALING FROM PICTURE IGNORED CA Culprit detected a picture clause with trailing Ps while generating REC parameters from the data dictionary. This type of scaling is not permitted in a CA Culprit run. Severity: W Modules: CULPDRES |
|
C200186 |
AUTO-ATTRIBUTES IS auto-attribute-option This message indicates whether the CA Culprit auto-attribute option is in effect in the data dictionary. CA Culprit prints ON if the option is in effect and OFF if it is not. Severity: I Modules: CULPDRES |
|
C200187 |
INVALID PASSWORD The CA Culprit code specifies an invalid or null password on an =COPY/=MACRO parameter for AllFusion CA-Librarian or AllFusion CA-Panvalet processing. Severity: E Modules: CULP0 |
|
C200188 |
ALL SUCCEEDING PARAMETERS IGNORED This message confirms that the system ignored all parameters that follow this message in the Sequential Parameter Listing. This is an internal system error. CA Culprit continues processing with only those parameters preceding the message. Severity: W Modules: CULP0 |
|
C200189 |
OPERAND TOO LONG In a keyword expression on a DATABASE parameter, the user coded an operand that exceeds the system limit of 8 characters. Severity: F Modules: CULP0 |
|
C200190 |
RECORD NOT INCLUDED IN LOGICAL RECORD CA Culprit encountered a database record that qualifies a field name in the format field-name (database-record OF logical-record), but the specified database record is not defined as part of the logical record on the data dictionary. Severity: F Modules: CULPDRES |
|
C200191 |
MORE THAN 100 LOGICAL RECORD PATHS The system encountered more than 100 PATH parameters that contain logical records. Reduce the number of PATH parameters and resubmit the job. Severity: F Modules: CULPDRES |
|
C200192 |
PATH MAY HAVE ONLY 1 LOGICAL RECORD CA Culprit detected a PATH parameter that references more than 1 logical record. Severity: F Modules: CULPDRES |
|
C200193 |
MORE THAN 100 RECORDS ON PATH The CA Culprit code specifies more than 100 record names on a single PATH parameter. Reduce the length of the path and resubmit the job. Severity: F Modules: CULPDRES |
|
C200194 |
ERROR ON GENERATED RECORD PAST SYSIN EOF Module CULPMASG generated a record after reading all the input parameters, for which the type of read necessary (for example, an AllFusion CA-Panvalet library or data dictionary) cannot be determined. This is an internal system error. Severity: E Modules: CULP0 |
|
C200195 |
(CONT) ERROR OCCURRED NEAR source-code The system detected an error while processing the WHERE clause on the indicated PATH parameter. This error message precedes the message that describes the specific WHERE clause error. Source-code is the last token in the token buffer when the error occurred. Severity: F Modules: CULPMERR |
|
C200197 |
QUALIFYING REC NAME NOT VALID CA Culprit encountered an error while processing the WHERE clause on a PATH parameter. The user coded a record name qualifier for the field name that exceeds the system limit of 32 characters. Severity: F Modules: IDMSGEXP CULP0 |
|
C200198 |
EXPECTING #, DATANAME, OR NESTED EXPR AFTER + OR - The user coded a keyword or a field name after a plus or minus sign in the WHERE clause on a PATH parameter. This error can occur if the element is not a numeric value, a database field name, or a nested expression. Severity: F Modules: IDMSGEXP CULP0 |
|
C200199 |
INVALID OR MISSING OPERAND FOR RELATIONAL OPERATOR The user coded a test operation (for example, EQ, GT) in the WHERE clause on a PATH parameter, but one of the operands is either missing or coded incorrectly. Valid operands are: numeric literals, numeric fields, and arithmetic expressions. Severity: F Modules: IDMSGCND CULP0 |
|
C200200 |
INVALID EXPRESSION IN PARENTHESES CA Culprit encountered an invalid parenthetical expression in the WHERE clause on a PATH parameter. Valid parenthetical expressions can be a boolean expression, an arithmetic expression, a comparison expression, or a keyword that is known to the data dictionary. Severity: F Modules: IDMSGEXP CULP0 |
|
C200201 |
2ND OPERAND MISSING IN EXPRESSION AFTER + OR - The WHERE clause contains a valid operand, that is an expression, data field name, or number was recognized preceding a + or - sign. However, an invalid operand was found following it. Severity: F Modules: IDMSGEXP CULP0 |
|
C200202 |
2ND OPERAND MISSING IN TERM AFTER * OR / The WHERE clause contains a valid operand, that is an expression, data field name, or number was recognized preceding a * or / sign. However, an invalid operand was found following it. Severity: F Modules: ADSOGEXP CULP0 |
|
C200203 |
NODE PASSED FROM CALLER IS IN ERROR. ABORT CA Culprit encountered an error with the dictionary node while processing a WHERE clause. This is an internal error. Call CA Technical Support. Severity: F Modules: IDMSGEXP OR IDMSGCND CULP0 |
|
C200204 |
CURRENT TERMINAL NODE HAS INVALID BR CODE. ABORT CA Culprit encountered a CA IDMS error with the current terminal node while processing a WHERE clause. This is an internal error. Call CA Technical Support. Severity: F Modules: IDMSGEXP OR IDMSGCND CULP0 |
|
C200205 |
INTERNAL STACK HAS INSUFFICIENT SPACE. ABORT If processing did not terminate, a parse stack overflow would have occurred during the parsing of a data field name or expression. Reduce the number of nested expressions or Call CA Technical Support to increase the size of the parse stack. Severity: F Modules: IDMSGEXP OR IDMSGCND CULP0 |
|
C200206 |
ELEMENT DOES NOT EXIST IN DICTIONARY A field that was encountered in the WHERE clause on a PATH parameter is not defined as either a field name or a keyword in the data dictionary. Severity: F Modules: IDMSGEXP OR IDMSGCND CULP0 |
|
C200207 |
ELEMENT DOES NOT EXIST IN SUBSCHEMA The user coded a field name in the WHERE clause on a PATH parameter, but the element is not defined as a field name or a keyword in the subschema that was specified on the INPUT parameter. Severity: F Modules: IDMSGEXP OR IDMSGCND CULP0 |
|
C200208 |
BAD RETURN CODE FROM GNRC.ABORT An internal routine (to validate data field names) passed an invalid return code to the expression parser for the WHERE clause. This is an internal error. Call CA Technical Support. Severity: F Modules: IDMSGEXP OR IDMSGCND CULP0 |
|
C200209 |
OVERFLOW OF EVALUATION BUFFER An expression may have a maximum total of fifty operands and operators. Reduce the number of operations performed within the current expression. Severity: F Modules: IDMSGEXP OR IDMSGCND CULP0 |
|
C200210 |
ELEMENT NOT UNIQUE IN SUBSCHEMA The user coded a field name in the WHERE clause on a PATH parameter, but the element exists in more than one record. Correct the CA Culprit code by qualifying the field name with a record name. Severity: F Modules: IDMSGEXP OR IDMSGCND CULP0 |
|
C200211 |
DATA TYPE INVALID WITH ARITHMETIC OPERATION CA Culprit detected an illegal data type in the WHERE clause on a PATH parameter. This error can occur if an operand in an arithmetic expression is defined in the data dictionary as an alphanumeric bit, 8-byte binary, or group field. Severity: F Modules: IDMSGEXP - CULP0 |
|
C200212 |
LOGICAL CONJUNCTION OPERAND NOT DATA TYPE = BIT CA Culprit detected an invalid operand of a logical conjunction (that is, AND, OR, or NOT) while analyzing the WHERE clause on a PATH parameter. The operand must be either a comparison expression or a keyword that is defined to the data dictionary. Severity: F Modules: IDMSGEXP OR IDMSGCND CULP0 |
|
C200213 |
INVALID DATA TYPE OR LENGTH FOR MATCHES/CONTAINS OP CA Culprit detected an error in the WHERE clause on a PATH parameter. This error can occur because of one of the following:
Severity: F Modules: IDMSGEXP CULP0 |
|
C200214 |
SUBSCRIPT IS EXPECTED FOR THIS DATANAME.SCAN CONT The user specified a multiply-occurring field in the WHERE clause on a PATH parameter, but the field was not referenced with a subscript. CA Culprit continues to scan the rest of the WHERE clause for errors. Severity: F Modules: IDMSGEXP CULP0 |
|
C200215 |
DIVISOR EXCEEDS MAXIMUM SIZE OF 8 BYTES CA Culprit detected a divisor in an arithmetic WHERE clause on a PATH parameter that exceeds the system limit of 8 bytes. Severity: F Modules: IDMSGEXP CULP0 |
|
C200216 |
INSUFFICIENT STORAGE FOR THIS LITERAL CA Culprit's WHERE clause parsing routine ran out of storage when CA Culprit tried to store a literal, a keyword, or a variable value. Severity: F Modules: IDMSGEXP CULP0 |
|
C200217 |
OCCURS DEPENDING ON CTL FIELD NOT HALF OR FULLWORD CA Culprit detected an error while processing the WHERE clause on a PATH parameter. A field that was referenced in the WHERE clause is defined to the data dictionary by the OCCURS clause, as follows: OCCURS occurrence-count-n TO occurrence-count-n TIME DEPENDING ON control-element-name The control-element-name is not defined as a binary halfword or fullword field. To correct the data dictionary, define the control-element-name as a binary halfword or fullword field in the fixed portion of the record. Severity: F Modules: IDMSGEXP CULP0 |
|
C200218 |
INSUFFICIENT STORAGE FOR THE GRE/GRD CA Culprit ran out of storage while processing the WHERE clause on a PATH parameter. This error can occur because of a complex WHERE clause. To correct the error, either simplify the clause or transfer some of the selection criteria to a SELECT parameter and resubmit the job. Severity: F Modules: IDMSGEXP OR IDMSGCND CULP0 |
|
C200219 |
CONDITION NAME NOT VALID IN ARITHMETIC EXPRESSION CA Culprit detected an illegal condition in the arithmetic expression of the WHERE clause on a PATH parameter. Numeric operands are required in all arithmetic expressions; true/false values are not permitted. Severity: F Modules: IDMSGEXP CULP0 |
|
C200220 |
KEYWORD NAME NOT VALID IN ARITHMETIC EXPRESSION The user coded a keyword that is known to the data dictionary in the WHERE clause arithmetic expression of a PATH parameter. Valid operands in arithmetic expressions are numeric literals and numeric fields. Severity: F Modules: IDMSGEXP CULP0 |
|
C200221 |
INVALID OR MISSING OPND FOR BOOLEAN AND/OR/NOT OP The user coded an invalid boolean AND/OR/NOT operator in the WHERE clause on a PATH parameter. One of the following errors has occurred:
Severity: F Modules: IDMSGCND CULP0 |
|
C200222 |
INVALID NESTED CONDITION The system encountered an invalid nested condition in the WHERE clause on a PATH parameter. Severity: F Modules: IDMSGCND CULP0 |
|
C200223 |
ERROR OF UNKNOWN ORIGIN CA Culprit detected an error while processing the WHERE clause on a PATH parameter, but the error code was not found in the CA Culprit error message table in the CULPMERR module. Severity: F Modules: CULPMERR CULP0 |
|
C200224 |
TOO FEW SUBSCRIPTS SPECIFIED CA Culprit detected the name of a multiply-occurring field WHERE clause on a PATH parameter, but no subscript is specified. Use a subscript to reference the multiply-occurring field. Severity: F Modules: IDMSGEXP CULP0 |
|
C200225 |
ILLEGAL SUBSCRIPT The user subscripted a field name that was coded in the WHERE clause expression on a PATH parameter, but the element is not a multiply- occurring field. Only multiply-occurring fields can be referenced with subscripts. For more information on multiply-occurring fields, refer to the CA Culprit for CA IDMS Reference Guide. Severity: F Modules: IDMSGEXP CULP0 |
|
C200226 |
UNABLE TO PARSE WHERE CLAUSE CA Culprit encountered an error while trying to analyze the WHERE clause on a PATH parameter. This error message may be accompanied by other messages that provide greater detail. To evaluate the error, review the WHERE clause. Severity: F Modules: CULPWHRE CULP0 |
|
C200227 |
TOKENS LEFT IN WHERE CLAUSE AFTER PARSE CA Culprit detected additional items while analyzing the WHERE clause on a PATH parameter and was unable to successfully complete the WHERE clause analysis. To evaluate this error, review the WHERE clause code. Severity: F Modules: CULPWHRE CULP0 |
|
C200228 |
INVALID ASSEMBLY OF PROFILE CSECT This message can occur if one or more errors were generated during the automatic assembly of the CULPPROF program at installation time. To evaluate the error, review the assembly listing of CULPPROF, make the appropriate changes, and reassemble the program. Severity: F Modules: CULPDFRE CULP0 |
|
C200229 |
PATH PARAMETER IS REQUIRED CA Culprit encountered an INPUT parameter with a DB file type. The DB file type on the INPUT parameter caused CA Culprit to expect a PATH parameter, and none was found. Severity: F Modules: CULP0 |
|
C200230 |
ILLEGAL CONTINUATION An =MACRO expansion caused a continuation line for a title parameter. A TITLE parameter cannot be continued to a second line. Severity: E Modules: CULPDFRE |
|
C200231 |
"USE" SYNTAX ERROR (CONT) EXPECTED use-option (CONT) FOUND incorrect-option CA Culprit prints this message when it encounters invalid syntax for the USE parameter. Severity: E Modules: CULPUSYN |
|
C200234 |
NO DEFINITION FOUND FOR "USE" KEYWORD - use-keyword A keyword that was not in a DEFAULT parameter was used in the WITH VALUES clause. The DEFAULT parameter is needed to associate argument numbers with values. Severity: E Modules: CULPUSYN |
|
C200236 |
"USE" OR "END" AND =MACRO/=COPY NOT ALLOWED IN SAME RUN The CA Culprit code contains both a USE parameter and either an =COPY or =MACRO parameter in the same run. Use one or the other, but not both. Severity: F Modules: CULP0 |
|
C200237 |
RETURN CODE FROM CULPMASG IS INVALID - HEX code The USE message routine returned an invalid code to CA Culprit. CA Culprit prints the 1-digit code in hexadecimal. Check the syntax of the line above this message. Severity: F Modules: CULP0 |
|
C200238 |
WILL USE STANDARD LIBRARIES - LIBRARY SYSTEM REQUESTED NOT KNOWN library-name The PROFILE parameter specifies a library name in the PARMLIB= keyword expression that is not known to CA Culprit. CA Culprit uses STANDARD as the default. Severity: W Modules: CULP0 |
|
C200239 |
CANCEL WITH DUMP TO AID PROBLEM DIAGNOSIS CA Culprit prints this message when it forces an abend with a dump. CA Culprit sets the error level to X'FF', which is detected by the CULP0 step. CULP0 then changes the level to F, prints the message, cancels the run, and prints the dump. Severity: F Modules: CULP0 |
|
C200240 |
MORE THAN 1 "WITH VALUES" CLAUSE SPECIFIED FOR "USE" CA Culprit encountered more than one WITH VALUES clause in a USE parameter. Only one WITH VALUES clause is allowed. Severity: E Modules: CULPUSYN |
|
C200241 |
MORE THAN 35 PARAMETER VALUES SPECIFIED More than 35 positional or keyword values were coded in the WITH VALUES clause of the USE parameter. Reduce the number to 35 or less and resubmit the job. Severity: E Modules: CULPUSYN |
|
C200242 |
INVALID SYNTAX IN "VALUE" OR "DEFAULT" EXPRESSION OR USE/&&N CA Culprit encountered invalid syntax in the WITH VALUES or DEFAULT clauses. The syntax is invalid for one of the following reasons:
CA Culprit skips over items subordinate to the clause in error and resumes parsing when it encounters the beginning of a new higher level item. Severity: E Modules: CULPUSYN |
|
C200244 |
INVALID RANGE OF COLUMNS/STMT # S/LINE # S/SEQ # CA Culprit encountered an invalid range of column numbers, process definition sequence numbers, edit line numbers, or identifiers coded in columns 73 through 80 in a USE parameter clause. Severity: E Modules: CULPUSYN |
|
C200245 |
MORE THAN 4K MAXIMUM REQUIRED FOR TABLE FOR table-name A CA Culprit internal control block exceeded its maximum size. One solution is to split a large USE member into two smaller members. Otherwise, try the following listed solutions for particular control blocks:
Severity: E Modules: CULPUSYN |
|
C200246 |
SPECIAL NAME IN DOUBLE QUOTES IS INVALID CA Culprit encountered an invalid name in double quotation marks for one of the following reasons:
Severity: E Modules: CULPDFRE GETWORD SUBROUTINE |
|
C200248 |
NO ROOM FOR RENUMBERED RESULT SEQUENCE NUMBER After renumbering the sequence numbers on a line, the line length exceeds 71 characters. Split the line in two by using a continuation character (*). Severity: E Modules: CULPUNUM |
|
C200249 |
DICTIONARY READ MODULE, CULPDICR, NOT LINKED The USE parameter specifies a dictionary module name, but the dictionary read module, CULPDICR, is not linked. Severity: E Modules: CULPUSYN |
|
C200250 |
SEARCH REQUESTED FOR STRING OF LENGTH ZERO A CHANGE, DROP, or KEEP instruction is invalid because it has a null literal string for which to search. Severity: E Modules: CULPUSYN |
|
C200251 |
"USE", "END", OR "DEFAULT" IS OUT OF PLACE A USE, END, or DEFAULT parameter is out of place. These parameters must be the first keywords on a line. Severity: E Modules: CULPUSYN |
|
C200252 |
"END" STATEMENT NOT PAIRED WITH "USE *" An END statement was found with no corresponding USE * parameter. Delete this line from your program. Severity: E Modules: CULPUSYN CULPUSE |
|
C200253 |
EXPANDED CARD IS INVALID Either 72 bytes of data on a parameter expanded to more than 256 bytes (excluding trailing blanks) or a quoted expression could not be completed on a single continuation card. CA Culprit continues the parameter on continuation lines, which may not be valid. Severity: E Modules: CULPUVCD |
|
C200254 |
TOO MANY NESTED "USE" STATEMENTS (CONT) CULPRIT WILL SUBSTITUTE The CA Culprit code contains more than 20 nested USE parameters. Twenty is the limit. Severity: E Modules: CULPUSE |
|
C202002 |
TYPE=COPY INVALID ON SECONDARY IN CARD In a CA Culprit run that consolidates tables, a secondary INPUT parameter specifies TYPE=COPY. CA Culprit automatically changes it to TYPE=CONSOL. Severity: W Modules: CULPFIKL |
|
C202003 |
TYPE=COPY REQUIRED FOR PRIMARY IN CARD In a CA Culprit run that consolidates tables, the first INPUT card must specify the keyword expression TYPE=COPY. Severity: W Modules: CULPFIKL |
|
C202004 |
OPERAND EXCEEDS LIMIT OF 8 CHARACTERS The names assigned to the following keyword expressions must be from 1 to 8 characters:
Severity: E Modules: CULPFIKL CULPIDB |
|
C202005 |
OPERAND EXCEEDS LIMIT OF 16 CHARACTERS The value assigned to the argument must be from 1 to 16 characters. Severity: E Modules: CULPFIKL CULPIDB |
|
C202006 |
OPERAND EXCEEDS LIMIT OF 32 CHARACTERS The values assigned to the following keyword expressions must be from 1 to 32 characters:
Severity: E Modules: CULPFIKL CULPIDB |
|
C202007 |
OPERAND EXCEEDS LIMIT OF 64 CHARACTERS The name assigned to the TABLE= keyword expression must be from 1 to 64 characters in length. Check the name assigned in your code and resubmit the job. Severity: E Modules: CULPFIKL CULPIDB |
|
C202008 |
KEYWORD ONLY VALID FOR DATA TABLES The CA Culprit code specifies a keyword that is valid only in runs that access an ASF table. These include:
Severity: E Modules: CULPFIKL CULPIDB |
|
C202009 |
KEYWORD ONLY VALID FOR PRIMARY DATA TABLE The CA Culprit code specifies a keyword that is valid only when it is associated with the primary table in a run that consolidates tables. Severity: E Modules: CULPFIKL CULPIDB |
|
C202010 |
DATA TABLES REQUIRE TABLE= KEYWORD The INPUT or OUTPUT parameters in a run that accesses tables must specify the keyword expression TABLE=, naming the table that you want to access. Severity: E Modules: CULPFIKL CULPIDB |
|
C202011 |
KEYWORD ONLY VALID FOR SQL ACCESS The following keywords are only valid if SQL access is specified:
Severity: E Modules: CULPFIKL |
|
C202012 |
EXPECTING "NOT NULL". UNKNOWN SYNTAX IGNORED When defining an edit parameter for an SQL CREATE function, the phrase NOT NULL has no abbreviations. The unknown syntax is ignored. Severity: W Modules: CULP46CH |
|
C202013 |
EXPECTING "WITH DEFAULT". UNKNOWN SYNTAX IGNORED When defining an edit parameter for an SQL CREATE function, the phrase WITH DEFAULT has no abbreviations. The unknown syntax is ignored. Severity: W Modules: CULP46CH |
|
Copyright © 2014 CA.
All rights reserved.
|
|