IBM Support

SE46834 - OSP-DB DRDA INVALID SYNCLOG FAILING RESYNC

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 APAR (Authorized Program Analysis Report)

Abstract

OSP-DB DRDA INVALID SYNCLOG FAILING RESYNC

Error Description

Unable to resync to due invalid SYNCLOG data for DRDA TCP/IP    
two-phase connection.                                          

Problem Summary

****************************************************************
* PROBLEM: (SE46834) Licensed Program = 5770SS1                *
*           Usability of a Product's MAJOR Function            *
*            TCP/IP twophase resync failure over DRDA          *
****************************************************************
* USERS AFFECTED: All IBM i operating system Distributed       *
*                 Relational Database Access (DRDA)            *
*                 users for i 7.1.                             *
****************************************************************
* RECOMMENDATION: Apply PTF SI42658 for i 7.1.                 *
****************************************************************
                                                               
                                                               
                                                               
                                                               
Unable to resync due to invalid SYNCLOG data.                  
                                                               
This can be recreated by committing & exiting out of STRSQL (or
disconnecting) after a successful DRDA connection has been made
under commitment control and then subsequently re-connecting to
the same system as before in STRSQL under commitment control.  
                                                               
There are no external indications to the user that the SYNCLOG  
is invalid unless a resync occurs and it cannot make a resync  
connection.                                                    

Problem Conclusion

                                                               
                                                               
                                                               
                                                               
The SYNCLOG registered for the initial DRDA connection under    
commitment control is correct; however, after exiting STRSQL or
disconnecting, that SYNCLOG is removed from commitment control.
 The second two-phase DRDA connection never requests a new      
SYNCLOG from the server resulting in an invalid resync TCP/IP  
address and port in SYNCLOG.                                    

Temporary Fix

                        *********                              
                        * HIPER *                              
                        *********                              

Comments

COMMENTS:                                                      
COMMENTS:                                                      
COMMENTS:                                                      
COMMENTS:                                                      
COMMENTS:                                                      

Circumvention


Using RELEASE will close the connection and allow the SYNCLOG to

be re-requested on subsequent CONNECT.                          

PTFs Available

R710 SI42658 PTF Cover Letter   1116

Affected Modules

         
         

Affected Publications

Summary Information

Status............................................ CLOSED PER
HIPER........................................... Yes
Component.................................. 5770SS1CM
Failing Module.......................... RCHMGR
Reported Release................... R710
Duplicate Of..............................




System i Support

IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG15Q","label":"APARs - OS\/400 General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R1M0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 May 2011