Allocation and Open Errors

Allocation and open errors involve the source or destination files. This chapter describes errors in which the allocation or opening of a file fails, and the action to take and types of data you need to collect to troubleshoot the error.

Condition: Allocating a User File Fails

Use the following table to troubleshoot this error.

Note: IBM® Connect:Direct® initialization parameters (ALLOC.CODES and ALLOC.RETRIES) determine which allocation errors, if any, cause a Process that fails on an allocation error to be retried.

.

Error Cause Action Collect
SDAA001I

SDAA004I

SDAA005I

SDAA048I

IBM Connect:Direct received an error while allocating a file or data set. Review both the short text and long text messages. Check the SYSLOG, console, or IBM Connect:Direct statistics for the text of the SDAA004I and SDAB005I messages. The SDAA004I message contains the allocation parameters used by IBM Connect:Direct. If an error exists, the ERR=nnnn field of the SDAB005I message contains non-zeroes, and error text follows. Use the IBM Connect:Direct message facility to look up the error, which has a format of SDEnnnnI, where nnnn is the number in the ERR field. The operating system dynamic allocation routine returns the ERR value.
Note: IBM Connect:Direct initialization parameters (ALLOC.CODES and ALLOC.RETRIES) determine which allocation errors, if any, cause a Process that fails on an allocation error to be retried.
  • IBM Connect:Direct allocation string (found in the WTO records in the statistics file)
  • IBM Connect:Direct Process involved
  • SDAA004I message output
  • SDAB005I message output

Condition: TCQ File Below Defined Threshold Value

Use the following table to troubleshoot this problem.

Error Cause Action Collect
SPQL003I

TCQ file is now below the defined threshold of &VAR.

The number of VSAM file CIs used has reached the defined threshold. Reduce the number of Processes in the TCQ, or increase the size of the TCQ. Refer to Configure the TCQ for more information.
  • None