CONNX Data Integration Suite 14.8.0 | Reference Guide | Error Messages | VSAM Error Messages | Started Task VSAM/QSAM/PDS: File Insert Error Messages
 
Started Task VSAM/QSAM/PDS: File Insert Error Messages
Text
Cause
Action
InsertRecord() Error 1100: kinsert() return code is non-zero.
SQL INSERT attempt failed against a VSAM KSDS, ESDS, or RRDS file.
If the file is a KSDS, verify that the key is unique. If the error is reproducible, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.
InsertRecord() Error 1101: The target VSAM file does not have the insert or add attribute.
The most recent import or open() of the target file did not return an insert or add attribute. The insert is rejected.
Ask your security administrator to verify that the target VSAM file is updatable. Re-import the target VSAM file into the CONNX CDD and retry the insert.
InsertRecord() Error 1102: osput() return code is non-zero.
The low-level BSAM record-oriented interface function osput() returned a non-zero value. This is either a file I/O (-2) or a record length error (-3).
If the error is reproducible, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.
InsertRecord() Error 1103: The record buffer pointer is NULL.
This is an internal logic error returned from the CONNX VSAM or QSAM InsertRecord() function.
Contact a Software AG technical representative.
InsertRecord() Error 1104: The record length is invalid.
This is an internal logic error returned from the CONNX VSAM InsertRecord() function. The record length for an insert against an ESDS or an RRDS file is zero or negative.
Contact a Software AG technical representative.
InsertRecord() Error 1105: fseek() to end-of-file failed.
Prior to processing an insert request to a QSAM physical sequential (PS) file, CONNX attempted to position the file pointer to end-of-file via the fseek() function, which failed with a non-zero return code.
If the error is reproducible, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.
InsertRecord() Error 1107: The record length is <= 0.
This is an internal logic error. The CONNX QSAM Insert() function was invoked with a non-positive record length.
Contact a Software AG technical representative.
InsertRecord() Error 1108: Insert is not supported for partitioned data sets.
The invoking application attempted to execute an SQL INSERT against a fully-qualified PDS(member). SQL INSERTs are only supported for VSAM and QSAM physical sequential data sets.
Remove the SQL Insert statement from the invoking CONNX client application.
InsertRecord() Error 1109: The target file is not a QSAM data set.
The invoking application attempted to execute an SQL INSERT against a data set which is not a QSAM physical sequential data set.
Verify that the CONNX CDD table entry refers to a JCL DDNAME or a fully-qualified data set name which is a QSAM physical sequential data set. If the target data set is a QSAM physical sequential file, re-import the file into the CONNX CDD and retry the INSERT. If the error message persists, contact a Software AG technical representative.
InsertRecord() Error 1160: The target file is not a VSAM data set.
Either there is an error in the CONNX CDD import or file open function, or the data set attributes have changed since the last import into the CONNX CDD file.
Re-import the target file COBOL copybook + JCL DDNAME or fully-qualified VSAM physical data set name into the CONNX CDD file. If the error is reproducible, follow procedure Started Task VSAM/QSAM/PDS: Error Message Diagnostics.