CONNX Data Integration Suite 14.8.0 | Reference Guide | Error Messages | VSAM Error Messages | Started Task VSAM/QSAM/PDS: File Read Error Messages
 
Started Task VSAM/QSAM/PDS: File Read Error Messages
Text
Cause
Action
GetFirstRecord() Error 1021: Invalid key access method specified.
This is an internal CONNX logic error.
Contact a Software AG technical representative.
GetFirstRecord() Error 1023: Invalid READ direction specified.
This is an internal CONNX logic error.
Contact a Software AG technical representative.
GetFirstRecord() Error 1024: Invalid search operator specified.
This is an internal CONNX logic error.
Contact a Software AG technical representative.
GetFirstRecord() Error 1027: ksearch() / fseek() failed.
File-positioning function ksearch (VSAM) or fseek() (QSAM or PDS) failed; the file I/O request is unsuccessful.
GetFirstRecord() Error 1029: kretrv() failed.
The file I/O function kretrv() failed to read the target VSAM file.
GetFirstRecord() Error 1031: seek to start-of-file failed.
The function kseek() (VSAM) or fseek() (QSAM / PDS) failed to set the file pointer to start-of file.
GetFirstRecord() Error 1032: The target file is not searchable or seekable.
The target VSAM, QSAM, or PDS file does not have the saerchable / seekable attribute.
Re-import the file into the CONNX CDD and re-try the SQL statement. If the error persists, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.
GetFirstRecord() Error 1033: The file pointer is NULL.
The target VSAM, QSAM, or PDS file pointer is NULL, due to an open() error, a dataset sharing conflict with another job, process, or task, or an internal logic error.
Re-try the SQL statement. If the error persists, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.
GetFirstRecord() Error 1037: The target file is not a VSAM data set.
Either there was a CONNX file import error, or the DDNAME or fully-qualified data set name in the CONNX execution JCL points to a non-VSAM data set.
Re-import the file into the CONNX CDD and re-try the SQL statement. If the error persists, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.
DoReadNextPrev() Error 1051: afread() error: 0 bytes returned and ferror() != 0.
The afread() file I/O function returned 0 bytes plus an error return code.
If the error is reproducible, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.
DoReadNextPrev() Error 1052: afread() error: bytes returned > 0 and ferror() != 0.
The afread() file I/O function returned a positive byte count and an error return code.
If the error is reproducible, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.
DoReadNextPrev() Error 1053: afread() error: return code < 0.
The afread() file I/O function returned an error code.
If the error is reproducible, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.
DoReadNextPrev() Error 1054: osget() error: return code != 0 (OK) or -1 (EOF).
An attempt to read the target file using the SAS/C BSAM record-oriented interface function returned an error code which was not 0 (OK)
or -1 (EOF).
If the error is reproducible, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.
DoReadNextPrev() Error 1055: The target file is not a VSAM data set.
An attempt to read the target file failed because it is not a VSAM data set. Either the file attributes of the data set have been changed since it was last imported into the CONNX CDD, or this is an internal logic error.
Verify that the DDNAME or physical data set name stored in the CONNX CDD file points to a VSAM KSDS, ESDS, or RRDS dataset. If the target dataset is VSAM, contact a Software AG technical representative.
DoReadNextPrev() Error 1056: The target file is not a QSAM dataset or a PDS member.
An attempt to read the target file failed because it is not a QSAM physical sequential data set or a fully-qualified PDS(member). Either the file attributes of the data set have been changed since it was last imported into the CONNX CDD, or this is an internal logic error.
Verify that the DDNAME or physical data set name stored in the CONNX CDD file points to a QSAM physical sequential data set or a fully-qualified PDS(member). If the target dataset organization (QSAM or PDS(member)) is correct, contact a Software AG technical representative.