|
Message ID |
Message |
|---|---|
|
C110001
|
UNSUCCESSFUL VSAM CONTROL BLOCK GENERATION—GENCB BLK vsam-macro While attempting to access key- or entry-sequenced VSAM files sequentially or directly, CULLVSAM detected an internal or logical error associated with VSAM software. As a result, the module could not generate the required VSAM control block. The module printed the VSAM macro under execution at the time the error occurred and forced an operation exception. Severity: * Modules: CULLVSAM |
|
C110004 |
UNSUCCESSFUL OPEN OF VSAM DATA SET While reading key- or entry-sequenced VSAM files sequentially or directly, CULLVSAM detected an error that prevented the opening of the VSAM file and forced an operation exception. Typically, this type of error results from a missing DD statement. Severity: * Modules: CULLVSAM |
|
C110005 |
SYNAD ERROR MESSAGE While reading key- or entry-sequenced VSAM files sequentially or directly, CULLVSAM detected a physical I/O error. The module printed this message during execution of the GENCB VSAM macro. Severity: * Modules: CULLVSAM |
|
C110006 |
CULPRIT SYSTEM ERROR While reading key- or entry-sequenced VSAM files sequentially or directly, CULLVSAM detected an internal system error that caused CA Culprit to force an operation exception. Severity: * Modules: CULLVSAM |
|
C110007 |
ERROR IN MODULE CONTROL CARD - syntax-error While reading key- or entry-sequenced VSAM files CULLVSAM encountered a syntax error on a KEY or ADR control statement and printed the invalid information. Severity: * Modules: CULLVSAM |
|
C120001
|
LAST TWO DIGITS OF DDNAME ddname/file-name ARE NOT NUMERIC CULEMLIN encountered a special-value-n specification on the OUTPUT parameter that is invalid for one of two reasons:
Severity: E Modules: CULEMLIN |
|
C120002 |
UNABLE TO OPEN OUTPUT FILE ddname/file-name Because CULEMLIN could not open the output file for the requested report, it printed the file name and terminated processing. Typically, this type of message results from a CA Culprit JCL error. Severity: E Modules: CULEMLIN |
|
C120003 |
RECORD SIZE record-size IS NOT A MULTIPLE OF 81 OR 133 CULEMLIN detected a record size specification on the OUTPUT parameter that is not a multiple of 81 or 133. As a result, the module could not calculate the logical line length. To correct this error, specify a multiple of 81 or 133 for record-size-n and resubmit the job. Severity: E Modules: CULEMLIN |
|
C120004 |
UNABLE TO OBTAIN STORAGE FOR HEADINGS OR FOOTINGS z/OS users only—CULEMLIN encountered header or footer lines defined on edit parameters, but insufficient storage was available to store these lines until print time. To correct this error, increase the core memory allocation in CA Culprit JCL. Severity: E Modules: CULEMLIN |
|
C120005 |
INTERNAL LIMITS DO NOT PERMIT FOOTINGS WHEN LOGICAL LINE SIZE EXCEEDS 256 The LRECL parameter in your DD statement assigned to CULEMLIN output needs to be 256 or less if you are using headers or footings in CULEMLIN. Severity: E Modules: CULEMLIN |
|
C120006 |
HEADERS/FOOTINGS EXCEED 1330 CHARACTER MAXIMUM z/VSE users only—CULEMLIN encountered header or footer specifications that exceed the module's 1330-byte limit. Severity: E Modules: CULEMLIN |
|
C120013 |
RECORD SIZE record-size IS NOT A MULTIPLE OF LRECL logical-record-length FOR ddname z/OS users only—CULEMLIN encountered a record size specification on the OUTPUT parameter that is invalid for one of two reasons:
Severity: E Modules: CULEMLIN |
|
C130001
|
VSAM SYNAD (CONT) FEEDBACK CODE IN DECIMAL IS vsam-feedback-code While attempting to write formatted records to a VSAM file, CULEVSAM detected a physical I/O error that prevents further processing. Before terminating processing, CA Culprit printed a VSAM feedback code, in hexadecimal format, to aid the user in debugging. For a definition of vsam-feedback-code, see appropriate VSAM publications. Severity: F Modules: CULEVSAM |
|
C130002 |
LOGIC ERROR ON VSAM PUT (CONT) FEEDBACK CODE IN DECIMAL IS vsam-feedback-code While attempting to write VSAM records, CULEVSAM detected a logical error. As a result, the module closed the VSAM output file. Before terminating processing, CA Culprit printed a VSAM feedback code, in hexadecimal format, to aid the user in debugging. For a definition of vsam-feedback-code, see appropriate VSAM publications. Severity: F Modules: CULEVSAM |
|
C130003 |
FILE CLOSED DUE TO I/O ERROR ON VSAM PUT (CONT) FEEDBACK CODE IN DECIMAL IS vsam-feedback-code While attempting to process a VSAM file, CULEVSAM detected an I/O error that caused the closing of the VSAM output file. Before terminating processing, CA Culprit printed a VSAM feedback code, in hexadecimal format, to aid the user in debugging. For a definition of vsam-feedback-code, see appropriate VSAM publications. To verify the VSAM file used for output, invoke the VSAM IDCAMS utility before resubmitting the job. Severity: F Modules: CULEVSAM |
|
C130004 |
UNABLE TO OPEN VSAM OUTPUT FILE, GENCB/MODCB FAILED (CONT) FEEDBACK CODE IN DECIMAL IS vsam-feedback-code While attempting to open a VSAM output file, CULEVSAM detected an error that prevents further processing. Before terminating processing, CA Culprit printed a VSAM feedback code, in hexadecimal format, to aid the user in debugging. Typically this type of error results from an invalid sequence type (that is, a sequence type other than ES, KS, or RS) coded on the OUTPUT parameter. Before resubmitting the job, check the IDCAMS job for nonzero return codes or an invalid VSAM cluster definition. For a definition of vsam-feedback-code, see appropriate VSAM publications. Severity: F Modules: CULEVSAM |
|
C130005 |
I/O ERROR ON OPEN VSAM FILE While attempting to write records to a user-defined VSAM file, CULEVSAM detected an error that prevents the opening of that file. Typically, invalid JCL causes this type of error. Check the IDCAMS job that created the VSAM file and the job log for more information. Severity: F Modules: CULEVSAM |
|
C130006 |
UNABLE TO CLOSE VSAM OUTPUT FILE Although OPEN and PUT requests were successfully executed, CULEVSAM could not close the VSAM file. Typically, this type of error occurs because of two simultaneous attempts to update the same VSAM file. Check with the DBA at your site, or see the job log for more information. Severity: F Modules: CULEVSAM |
|
C130007 |
DEFAULTED - VSAM KEY SEQUENCED OUTPUT CULEVSAM encountered an invalid sequence-type-a on the OUTPUT parameter (that is, a sequence type other than ES, KS, or RS). As a result, the module assumed a sequence of KS, and attempted to add key-sequenced records to the specified output file. Severity: W Modules: CULEVSAM |
|
C140001
|
REPORT TERMINATED FOR INVALID MODULE CONTROL SWITCH z/VSE users only—CULEPOWR, invoked as a subroutine, expected one of the following control information codes:
Severity: F Modules: CULEPOWR |
|
C140002 |
REPORT TERMINATED FOR READER INPUT ERROR: EITHER NO INPUT CARD OR MORE THAN ONE INPUT CARD WAS FOUND FOR THIS REPORT z/VSE users only—CULEPOWR received a request to read CULEPOWR control statements through SYSRDR, but more than one statement was specified for the report. Severity: F Modules: CULEPOWR |
|
C140003 |
REPORT TERMINATED FOR NON MATCHING REPORT NUMBERS. CULPRIT REPORT WAS report-number INPUT CARD RPT WAS report-number z/VSE users only—CULEPOWR, invoked as an output module, automatically compared the report number in the CULEPOWR control statement with that of the report number under execution. Because these report numbers differed, the module printed both report numbers and canceled the report. Severity: F Modules: CULEPOWR |
|
C140004 |
REPORT TERMINATED FOR INVALID KEYWORD. JECL KEYWORD SUPPLIED WAS jecl-keyword z/VSE users only—CULEPOWR expected a LST or PUN POWER key in columns 3 through 5 of the appropriate CULEPOWR control statement but found an invalid specification. Before terminating processing, the module printed the invalid expression. Severity: F Modules: CULEPOWR |
|
C140005 |
REPORT TERMINATED FOR UNRECOGNIZABLE VSE/POWER RETURN CODE. z/VSE users only—CULEPOWR received an unrecognizable error code from the VSE/POWER facility. Severity: F Modules: CULEPOWR |
|
C140006 |
REPORT TERMINATED FOR ONE OF THE FOLLOWING REASONS: 1.THE DEVICE TYPE ADDRESSED BY THE DEVADDR OPERAND IS NOT A DEVICE TYPE CURRENTLY BEING SPOOLED SPOOLED BY VSE/POWER. 2. VSE/POWER IS NOT ACTIVE 3. THE PARTITION IN WHICH YOUR PROGRAM IS RUNNING IS NOT SUPPORTED BY VSE/POWER. 4.THE SPOOLED DEVICE HAS A DISPOSITION OF n 5.THE JECL STATEMENT PROVIDED WAS NOT A * $$ JOB, LST, PUN STATEMENT z/VSE users only—While attempting to perform VSE/POWER segmentation, CULEPOWR encountered an error that prevents further processing. This error can occur for one of two reasons:
Severity: F Modules: CULEPOWR |
|
C140007 |
REPORT TERMINATED FOR THE FOLLOWING REASON: VSE/POWER CANNOT ACCEPT THE JECL STATEMENT BECAUSE THE PARTITION WAS NOT STARTED AS A MULTITASKING PARTITION AND THE PARTITION IS WAITING FOR WORK, OR THE PARTITION WAS STARTED AS A MULTITASKING PARTITION AND IS WAITING FOR WORK, BUT NO JECL STATEMENT WAS SUBMITTED FOR THIS DEVICE. z/VSE users only—CULEPOWR encountered an error that prevents further processing. As a result, the VSE/POWER facility returned X'08' to Register 15. Severity: F Modules: CULEPOWR |
|
Copyright © 2014 CA.
All rights reserved.
|
|