CRV errors generally indicate an inconsistence within the Data Storage record that needs further investigation. The errors are intended to help pinpoint what is incorrect.
CRV001E | CRV002E | CRV003E | CRV004E | CRV005E | CRV006E | CRV007E | CRV008E | CRV009E | CRV010E | CRV012E | CRV013E | CRV014E | CRV015E | CRV016E | CRV017E | CRV018E | CRV019E | CRV020E | CRV021E | CRV022E | CRV023E | CRV024E | CRV025E | CRV026E | CRV028E | CRV029E | CRV030E | CRV031E | CRV032E | CRV033E | CRV034E | CRV035E | CRV036E | CRV037E | CRV038E | CRV039E | CRV040ENote:
All CRV* errors for spanned Data Storage files can display additional
messages if the nucleus is up prior to the CRV* message. If an error occurs in
the decompression routines that is for a spanned Data Storage record, a call is
first made to the nucleus to ensure that the error was not due to a faulty
assembled spanned data storage record prior to reporting the CRV* error.
| CRV001E | ERROR: Invalid length for non null suppressed field fld. |
| Explanation |
A compressed field that is not null-suppressed has a length indicator of x'00', x'01', x'8000', x'8001', or x'8002'. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV002E | ERROR: Insufficient record length for field fld. |
| Explanation |
A field with FI option has a length that exceeds the remaining record length. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV003E | ERROR: Field length exceeds 253 bytes for field fld. |
| Explanation |
A field whose exclusive length exceeds 253 and is not defined with LA option. Note: |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV004E | ERROR: End of FDT encountered before end of record. |
| Explanation |
The end of the FDT has been reached but not the end of the record (an MU or PE at the end of the FDT can repeat). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV005E | ERROR: LOB indicator exists for field fld but field does not have LB option. |
| Explanation |
A LOB reference indicator exists for a field not defined with LB option. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV006E | ERROR: LOB reference is not properly formatted for field fld. |
| Explanation |
A LOB reference is not properly formatted (e.g. x'C0' is not followed by x'80'). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV007E | ERROR: Insufficient length remaining for LOB reference for field fld. |
| Explanation |
A LOB reference exceeds the remaining record length. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV008E | ERROR: Field fld defined with FI option but flagged as empty. |
| Explanation |
The field identified in the message (fld) is defined with the FI (fixed format) option but appears to be empty. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV009E | ERROR: Field fld defined with NN option but flagged as empty. |
| Explanation |
The field identified in the message (fld) is defined with the NN (not null) option but appears to be empty. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV010E | ERROR: Field fld defined without NU and NC option but flagged as empty. |
| Explanation |
The field identified in the message (fld) is empty but is defined without either the NU (null suppression) or NC (not counted) options. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV012E | ERROR: Alpha field fld has last byte of blank with inconsistent options. |
| Explanation |
An alphanumeric field without the NB option and with the NU option has a last byte of x'40'. This is not possible unless the field has a one-byte length of x'02' or is defined with the FI option. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV013E | ERROR: Value for packed field fld exceeds 15 bytes. |
| Explanation |
A packed/unpacked field with (exclusive) length exceeding 15 |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV014E | ERROR: Packed field fld not correctly compressed. |
| Explanation |
A packed/unpacked field has a leading x'00' as its first byte, indicating it might not be correctly compressed. This is not possible unless the field has the FI option. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV015E | ERROR: Packed field fld not null-suppressed. |
| Explanation |
A packed/unpacked field defined with NU option and with x'02' as its length where the data byte is x'0D' or x'0F' (e.g. the field should have been null-suppressed). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV016E | ERROR: Packed field fld contains invalid data. |
| Explanation |
A packed/unpacked field is not a properly packed value (e.g. any numbers ending with x'nA', x'nB'’, x'nC', or x'nE' are invalid). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV017E | ERROR: Value for binary field fld exceeds 126 bytes. |
| Explanation |
A binary field has a (exclusive) length exceeding 126 bytes. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV018E | ERROR: Binary field fld not correctly compressed. |
| Explanation |
A binary field with leading x'00' as its first byte has a one-byte length that exceeds x'02' (e.g. the field is not properly compressed). This is not applicable if the field is defined with the FI option. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV019E | ERROR: Binary field fld not null-suppressed. |
| Explanation |
A binary field defined with NU option and with x'02' as its length, but the data byte is x'00' (indicating the field should have been null-suppressed). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV020E | ERROR: Value for float field fld exceeds 8 bytes. |
| Explanation |
A floating point field cannot exceed eight bytes. in second record at offset x1B6 zapped float field length from x04 to x0A |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV021E | ERROR: Float field fld not correctly compressed. |
| Explanation |
A floating point field with a trailing x'00' as its last byte has a one-byte length that exceeds x'02' (e.g. the field is not properly compressed). This is not applicable if the field is defined with the FI option. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV022E | ERROR: Float field fld not null-suppressed. |
| Explanation |
A floating point field is defined with the NU option, but the data bytes are all x'00's (e.g. the field should have been null-suppressed). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV023E | ERROR: length for wchar field fld exceeds 252 or is less than wchar length. |
| Explanation |
A wide field is defined with a length that is less than the length of the defined wide space length (e.g. 2-byte wide space length + 1). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV024E | ERROR: wchar field fld not correctly compressed. |
| Explanation |
A wide field is defined without the NB option and with the NU option, but ends with the defined wide space. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV025E | ERROR: wchar field fld not null-suppressed. |
| Explanation |
A wide field is defined without the NB option and with the NU option, but ends with the defined wide space. This is not an error if the entire field contains only one wide space. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV026E | ERROR: Value for fixed field fld exceeds 8 bytes. |
| Explanation |
A fixed point field has a (exclusive) length that exceeds 8 bytes. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV028E | ERROR: Fixed field fld not null-suppressed. |
| Explanation |
A fixed point field is defined with the NU option, but the data bytes are all x'00's (e.g. the field should have been null-suppressed). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV029E | ERROR: MU Field fld has an invalid count. |
| Explanation |
A field is defined as an MU field, but has an MU count of zero. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV030E | ERROR: MU Field fld has two byte value. File not defined with two byte MUs. |
| Explanation |
A two-byte MU count is indicated (x'C0') for a field, but the field is not defined with a two-byte MU/PE option. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV031E | ERROR: MU Field fld has invalid two byte value. |
| Explanation |
A two-byte MU count is indicated (x'C0') for a field, but the next byte is not x'02'. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV032E | ERROR: MU Field fld at end of record. |
| Explanation |
The record ends with an MU count (one-byte or two-byte field). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV033E | ERROR: PE Field fld has an invalid count. |
| Explanation |
A field is defined as a PE field, but has a PE count of zero or a count greater than 191. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV034E | ERROR: PE Field fld has two byte value. File not defined with two byte PEs. |
| Explanation |
The record ends with a PE count (a one-byte or two-byte field). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV035E | ERROR: PE Field fld has invalid two byte value. |
| Explanation |
A two-byte PE count is indicated (x'C0'), but the file is not defined with a two-byte MU/PE option. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV036E | ERROR: PE Field fld at end of record. |
| Explanation |
The record cannot end with a PE count. This is invalid. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV037E | ERROR: Remaining MU occurrences for fld but insufficient data in record. |
| Explanation |
Remaining MU occurrences are indicated in the MU count, but the end of the record has been reached. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV038E | ERROR: Remaining PE occurrences for fld but insufficient data in record. |
| Explanation |
Remaining PE occurrences are indicated in the PE count, but the end of the record has been reached. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV039E | ERROR: Wchar field fld encountered for file without UES support. |
| Explanation |
A wide character field was encountered in a file without universal encoding support (UES). |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |
| CRV040E | ERROR: Wchar field fld length is invalid. |
| Explanation |
The Wchar length is invalid. |
| Action |
Determine the cause of the error and correct it. If you need assistance, contact your Software AG technical support representative. |