Text | Cause | Action |
File Open Error 1001: Read/Write access requested, but the target file does not have the read attribute. | Your user id does not have read access to the target VSAM, QSAM or PDS file. | Ask your security administrator to grant your user id read access to the target file. |
File Open Error 1002: Read/Write access requested, but the target file does not have the write attribute. | Your user id does not have write or change access to the target VSAM or QSAM file. | Ask your security administrator to grant your user id write or change access to the target file. |
File Open Error 1003: afopen() or afreopen() returned a NULL file pointer. | The attempt to open the target file failed, probably because of a mismatch in the imported CONNX *.cdd file JCL DDNAME or fully-qualified data set name, or because another process has exclusive access to the target file. | Review the DDNAME or fully-qualified data set name of the target file in the CONNX Data Dictionary (*.cdd) file. If the file name is a JCL DDNAME, verify that the DDNAME in the *.cdd file matches a DDNAME defined in the execution JCL for the CONNX Started Task or batch job. If the the file is a fully-qualified data set name, verify that the target data set exists and can be opened and viewed using standard TSO / ISPF utilities such as Browse or DITTO. If there is a data set sharing conflict with another process, the view attempt will fail with an appropriate message. |
File Open Error 1004: osddinfo() return code != 0. | During file import or open, CONNX requested attribute information for the file corresponding to a user-entered JCL DDNAME in the File Name text box in the Table Properties tab of the CONNX Data Dictionary Manager. | Verify that the DDNAME in the *.cdd file matches a DDNAME defined in the execution JCL for the CONNX Started Task or batch job. |
File Open Error 1005: CnxRACF::CheckDSNAccess() < 0 or > 4. | The CONNX data set security interface has returned an error condition during the attempted open, read, write, or delete operation against the target file. If the return code is < 0, the DASD volume serial of the target data set could not be located. If the return code is > 4, the logged on user id does not have the requested file read, write, update, or delete privilege(s). | Verify that the target data set exists, and that your userid has the requested read, write, update, or delete file access privilege(s). If your userid has the necessary file access privileges, follow procedure
Started Task VSAM/QSAM/PDS: Error Message Diagnostics. |
File Open Error 1007: fattr() returned a NULL pointer. | After a call to afopen() or afreopen(), CONNX attempted to determine file attributes via the fattr() function call, which returned a NULL pointer. | Follow procedure
Started Task VSAM/QSAM/PDS: Error Message Diagnostics. |
File Open Error 1008: Read access requested, but the target file does not have the read attribute. | Your user id does not have read access to the target VSAM, QSAM or PDS file. | Ask your security administrator to grant your user id read access to the target file. |
File Open Error 1012: osdsinfo() return code != 0. | The CONNX file open logic invoked to the osdsinfo() function using the fully-qualified dataset name corresponding to the JCL DDNAME stored in the CONNX Data Dictionary file. This function returns necessary information such as data set organization, record format, length, and blocksize. The file is either already open, or there is a data set sharing conflict with another subtask, task, or job. | Follow procedure
Started Task VSAM/QSAM/PDS: Error Message Diagnostics. |
File Open Error 1013: The physical data set name is not a VSAM, QSAM or PDS file. | CONNX attempted to open a file with an unsupported file access format. | Verify that the JCL DDNAME or the actual physical data set name used in the import or open request is a valid type of file (VSAM, QSAM physical sequential, or partitioned data set + member name. |
File Open Error 1015: Read/Write access is not supported for partitioned data sets. | The invoking application has requested that CONNX open a fully-qualified PDS(member) data set name for read/write access. CONNX only supports read access for PDS members. | Revise the invoking application to issue read-only SELECTS against the fully-qualified PDS(member) data set name or JCL DDNAME. |
File Open Error 1016: Unsupported data set record format. | CONNX detected an unsupported record format (RECFM) during import or open() of a physical sequential or a partitioned data set (member). Supported record formats are F (Fixed) and FB (Fixed Block). Unsupported record formats include FBS, VB, VBS, and U ( Fixed Block Spanned, Variable Blocked, , Variable Blocked Spanned, and Undefined). | None. CONNX cannot import or open the designated file. |
File Open Error 1017: osopen() return code != 0. | During import or open() processing, CONNX unsuccessfully attempted to open the target file using the low-level osopen() BSAM (Basic Sequential Access Method) record-oriented interface function. | Follow procedure
Started Task VSAM/QSAM/PDS: Error Message Diagnostics. |
GetFirstRecord() Error 1021: Invalid key access method specified. | This is an internal CONNX logic error. | Report the error message to CONNX Technical Support. |
GetFirstRecord() Error 1023: Invalid READ direction specified. | This is an internal CONNX logic error. | Report the error message to CONNX Technical Support. |
GetFirstRecord() Error 1024: Invalid search operator specified. | This is an internal CONNX logic error. | Report the error message to CONNX Technical Support. |
GetFirstRecord() Error 1027: ksearch() / fseek() failed. | File-positioning function ksearch (VSAM) or fseek() (QSAM or PDS) failed; the file I/O request is unsuccessful. | Follow procedure
Started Task VSAM/QSAM/PDS: Error Message Diagnostics. |
GetFirstRecord() Error 1029: kretrv() failed. | The file I/O function kretrv() failed to read the target VSAM file. | Follow procedure
Started Task VSAM/QSAM/PDS: Error Message Diagnostics. |
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. | Follow procedure
Started Task VSAM/QSAM/PDS: Error Message Diagnostics. |
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, then report the error to CONNX Technical Support. |
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, then report the error to CONNX Technical Support. |