A fix is available
APAR status
Closed as program error.
Error description
DB2DDF DB2TCPIP defect pm37030 dpm37030 DSNL511I messages with RETURN CODE=1121 may be issued by DB2 when the socket is cancelled and there is no transaction in progress. RETURN CODE 1121 is ECONNRESET The message is informational. Example of message: DSNL511I DSNLIENO TCP/IP CONVERSATION FAILED TO LOCATION (ipaddr) IPADDR=(ipaddr) PORT=(port) SOCKET=RECV RETURN CODE=1121 REASON CODE=00000000 ******************************************** Additional keywords and symptoms: DB2 DSNL511I MSGDSNL511I L511 ECONNRESET 1121
Local fix
no local workaround or fix
Problem summary
**************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically where remote client * * applications uses TCP/IP to access a * * DB2 for z/OS server. * **************************************************************** * PROBLEM DESCRIPTION: Many occurrences of message DSNL511I * * with RETURN CODE=1121 and * * REASON CODE=00000000 may appear in the * * system log. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a remote client application is accessing a DB2 for z/OS server via TCP/IP and closes its connection with DB2, message DSNL511I with RETURN CODE=1121 and REASON CODE=00000000 may be issued by CSECT DSNLIENO. This typically occurs because the remote client system did not close the TCP/IP socket connection gracefully on the application's behalf. Note: Not all remote client systems that access a DB2 server using TCP/IP will cause this message DSNL511I to occur. Only those remote client systems that do not gracefully close the TCP/IP socket connection may cause this DSNL511I message to occur. It is important to understand that the DSNL511I message with RETURN CODE=1121 and REASON CODE=00000000 reports that a connection is being reset by the peer (remote client system), and this could be due to an abnormal or normal condition. If the connection is reset (by the peer) while a transaction IS in progress, then this is considered to be an abnormal condition and it is therefore necessary for DB2 to issue the message. If the connection is reset (by the peer) while a transaction IS NOT in progress, then this likely indicates a normal condition in which case the DSNL511I message is basically noise and therefore is erroneous and can be suppressed.
Problem conclusion
DB2 has been changed to suppress the DSNL511I message, with RETURN CODE=1121 and REASON CODE=00000000, if the remote client system is closing its connection with DB2 while a transaction is not in progress.
Temporary fix
Comments
APAR Information
APAR number
PM37030
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-04-14
Closed date
2011-06-17
Last modified date
2013-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK68870 UK68871
Modules/Macros
DSNLIENO
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 March 2013