Error Codes and Messages › ENCI Messages

ENCI Messages

This section details messages generated in the course of object oriented I/O service processing, along with possible causes and corrective actions to take in error situations.

ENCI900I

No error messages are outstanding

Reason:

The application issued a RETRIEVE_ERROR_TEXT request but there was no error message associated with the I/O Object. This message is issued to indicate this fact.

Action:

No action is necessary.

ENCI901EI

An attempt was made to read past the end-of-file for data set data set name

Reason:

The application issued a READ_RECORD request after a previous READ_RECORD request has reached the end-of-file. The application had not issued an intervening CLOSE_DATA SET request. The I/O Object cannot read past the end-of-file.

Action:

The application does not contain the correct end-of-file processing logic. Contact the application developer.

ENCI902E

Allocation failed for data set data set name. S99ERROR=s99error, S99INFO=s99info

Reason:

The dynamic allocation request for the data set specified failed. The dynamic allocation service returned the error code and information code specified.

Action:

Refer to IBM manual GC28-1852 Systems Programming Library: Application Development Guide (or the equivalent manual for your release of z/OS) for an explanation of the S99INFO and S99ERROR codes. Take any corrective action possible and resubmit the request.

ENCI903E

An invalid data set type, value, was passed to the EDIT_DATA SET_ATTRIBUTES function.

Reason:

The application made an EDIT_DATA SET_ATTRIBUTES request but passed an invalid data set type code. The message contains the attribute code passed.

Action:

Contact the application developer to determine why an invalid data set type was passed with the request.

ENCI904E

An unrecoverable error occurred during a READ request. The READ RESULT code is value

Reason:

A READ_RECORD request failed for an I/O Object that is using the XP I/O services. The XP $BQIO RESULT code is provided in the message text.

Action:

If the RESULT code is ‘I/O ERR’, refer to the System job log to determine if any System related error messages were issued. If so, take the corrective action for those errors. For any other RESULT code, contact the application developer.

ENCI905E

Unable to allocate storage for an I/O buffer. The $BGETSTG RESULT was value

Reason:

An internal storage request for an I/O buffer failed. The storage management service return code is indicated in the message.

Action:

Increase the REGION= JCL parameter on the JOB or EXEC statement and resubmit the job.

ENCI905E

An unrecoverable error occurred during a READ request. The READ RESULT code is value

Reason:

A READ_RECORD request failed for an I/O Object that is using the XP I/O services. The XP $BQIO RESULT code is provided in the message text.

Action:

If the RESULT code is ‘I/O ERR’, refer to the System job log to determine if any System related error messages were issued. If so, take the corrective action for those errors. For any other RESULT code, contact the application developer.

ENCI907E

An unrecoverable error occurred during a WRITE request. The WRITE RESULT code is value

Reason:

A WRITE_RECORD request failed for an I/O Object that is using the XP I/O services. The XP $BQIO RESULT code is provided in the message text.

Action:

If the RESULT code is ‘I/O’ error, refer to the System job log to determine if any System related error messages were issued. If so, take the corrective action for those errors. For any other RESULT code, contact the application developer.

ENCI908E

An unrecoverable error occurred during a WRITE request. The ABEND Code is value

Reason:

A WRITE_RECORD request failed with the ABEND code identified.

Action:

If the ABEND code is SB37, SD37 or SE37, the output data set allocation is not large enough. In these cases, reallocate the data set with a larger allocation. Any other ABEND code indicates an application error.