17 IOERR

17 IOERR

If the RESP of the CICS command is equal to "17", then it's meaning is IOERR. Double check the status of resorce.

Default Action - The task gets terminated abnormally.

Command RESP RESP2 Reason, Deafult Action & Solution
DELETE 17 120 Reason - There is an I/O error during the file control operation.

Solution - An I/O error is any unusual event that is not covered by a CICS condition. For VSAM files, IOERR usually indicates a hardware error.
ENDBR 17 120 Reason - There is an I/O error during the ENDBR operation.

Solution - An I/O error is any unusual event that is not covered by a CICS condition. For VSAM files, IOERR usually indicates a hardware error.
READ 17 120 Reason - There is an I/O error during the READ operation.

Solution - An I/O error is any unusual event that is not covered by a CICS condition. For VSAM files, IOERR usually indicates a hardware error.
READNEXT 17 120 Reason - There is an I/O error during the READNEXT operation.

Solution - An I/O error is any unusual event that is not covered by a CICS condition. For VSAM files, IOERR usually indicates a hardware error.
READPREV 17 120 Reason - There is an I/O error during the READNEXT operation.

Solution - An I/O error is any unusual event that is not covered by a CICS condition. For VSAM files, IOERR usually indicates a hardware error.
READQ TD 17 Reason - Occurs when an input/output error and the data record in error is skipped.

Solution - This condition occurs if writing the queue when the queue cannot be written and a QZERO condition occurs in this situation. Check the Queue opened mode before issuing a write command.

This condition can also occur if the FREE=CLOSE operand has been used in the data set definition for an extra-partition queue and the queue has been closed and reopened. Reopen the file to resolve the issue.
READQ TS 17 5 Reason - There is an irrecoverable input/output error for a shared queue.

Solution - This might be due to the memory access problem. Try after some time and the issue still exists, contact the storage support group to resolve the issue.
RESETBR 17 120 Reason - There is an I/O error during the RESETBR operation.

Solution - An I/O error is any unusual event that is not covered by a CICS condition. For VSAM files, IOERR usually indicates a hardware error.
REWRITE 17 120 Reason - There is an I/O error during the file control operation.

Solution - An I/O error is any unusual event that is not covered by a CICS condition. For VSAM files, IOERR usually indicates a hardware error. For BDAM files, IOERR could means you are trying to write to a BDAM track address that is not defined for the data set.
STARTBR 17 120 Reason - There is an I/O error during the READ operation.

Solution - An I/O error is any unusual event that is not covered by a CICS condition. For VSAM files, IOERR usually indicates a hardware error.
UNLOCK 17 120 Reason - There is an I/O error during the ENDBR operation.

Solution - An I/O error is any unusual event that is not covered by a CICS condition. For VSAM files, IOERR usually indicates a hardware error.
WRITE 17 120 Reason - There is an I/O error during the file control operation.

Solution - An I/O error is any unusual event that is not covered by a CICS condition. For VSAM files, IOERR usually indicates a hardware error. For BDAM files, IOERR could means you are trying to write to a BDAM track address that is not defined for the data set.
WRITEQ TS 17 5 Reason - There is an irrecoverable input/output error for a shared queue.

Solution - This might be due to the memory access problem. Try after some time and the issue still exists, contact the storage support group to resolve the issue.
WRITEQ TD 17 Reason - Occurs when an input/output error and the data record in error is skipped.

Solution - This condition occurs if writing the queue when the queue can’t be written and a QZERO condition occurs in this situation. Check the Queue opened mode before issuing a write command.

This condition can also occur if the FREE=CLOSE operand has been used in the data set definition for an extra-partition queue and the queue has been closed and reopened. Reopen the file to resolve the issue.