|
Text |
Cause |
Action |
|
DeleteCurrentRecord() Error 1090: kdelete() return code is non-zero. |
An SQL DELETE statement against a VSAM file returned an error code. |
kdelete() fails when invoked against an ESDS. Verify that the target file is a VSAM KSDS or an RRDS. If the error is reproducible, follow procedure A01 below. |
|
DeleteCurrentRecord() Error 1092: Delete is not supported for Entry-Sequenced Data Sets (ESDS). |
The client application attempted an SQL DELETE against an ESDS. |
Verify that the target data set is an ESDS; if it is, then remove the DELETE statements against the ESDS from the invoking application. If the target data set is not an ESDS, report the error scenario to CONNX Technical Support. |
|
DeleteCurrentRecord() Error 1093: Delete is not supported for QSAM physical sequential and partitioned data sets. |
The client application attempted an SQL DELETE against a QSAM physical sequential or a partitioned data set. |
Verify that the target data set is QSAM PS or PDS; if it is a QSAM PS or a PDS, then remove the DELETE statements against the data set from the invoking application. If the target data set is not a QSAM PS or a PDS, report the error scenario to CONNX Technical Support. |
|
DeleteCurrentRecord() Error 1094: The target file is not a VSAM data set. |
An SQL DELETE attempt against the target file failed because it is not a VSAM KSDS or RRDS 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 or RRDS data set. If the target data set is a VSAM KSDS or RRDS, then report the error to CONNX Technical Support. |