DSNL030I csect-name DDF PROCESSING FAILURE FOR LUWID=luw-id REASON=reason-code THREAD-INFO=thread-information
Explanation
A requesting conversation was terminated because of DDF processing failure.
- csect-name
- The name of the control section that issued the message.
- luw-id
- The logical unit of work ID of the requesting agent, if that information is available, or a description of the logical unit that made the request in the format
netid.luname.000000000000
. - reason-code
- A numeric value that describes the nature of the DDF processing failure.
- thread-information
- Information about the thread. thread-information is a colon-delimited list that contains the following segments. An asterisk (*) in any segment indicates that the information is not available.
- The primary authorization ID that is associated with the thread.
- The name of the user's workstation.
- The ID of the user.
- The name of the application.
- The statement type for the previously executed statement: dynamic or static.
- The statement identifier for the previously executed statement, if available. The statement identifier can be used to identify the particular SQL statement. For static statements, the statement identifier correlates to the STMT_ID column in the SYSIBM.SYSPACKSTMT table. For dynamic statements, the statement identifier correlates to the STMT_ID column in the DSN_STATEMENT_CACHE_TABLE table. That statement might not have contributed to the current failure.
- The name of the role that is associated with the thread.
- The correlation token that can be used to correlate work at the remote system with work performed at the Db2 subsystem. The correlation token, if available, is enclosed in '<' and '>' characters, and contains three components, separated by periods:
- A 3 to 39 character IP address.
- A 1 to 8 character port address.
- A 12 character unique identifier.
System action
Processing continues, but the system will eventually abend the database access agent.
Operator response
Notify the system programmer for analysis.
System programmer response
If you suspect an error in Db2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.
Tip:
In Db2 13, you can reduce flooding of the z/OS® console by DSNL030I messages that occurs in situations by applying the PTF for APAR PH62137. For more information, see Reduced z/OS console flooding by DSNL030I messages (PH62137).


Problem determination
Collect the following diagnostic items:
- Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
- Dynamic dump, taken to SYS1.DUMPxx data set, by Db2 (04E and 04F abends).
- A listing of the SYS1.LOGREC data set, obtained by executing IFCEREP1.