IBM Support

PM55373: THREAD CAN NOT BE CANCELLED BECAUSE OF TIGHT LOOP IN DSNLCITR. APPEARS TO BE HUNG.

A fix is available

Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DB2DRDA DB2LOB Defect pm55373 dpm55373
A thread is in a tight loop in DSNLCITR. The trace for IFCID180
is turned on and LOB data is being returned to the requester.
The problem is only seen if a DB2 trace using IFCID 180 is
running.
************************************************************
Additional Symptoms and Keywords:
  LOOP LP WT WAIT HANG HUNG
  IFCID 180 0180 IFCID180 IFCID0180 QWHS0180

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
*                 Specifically those who enabled IFCID 180     *
*                 tracing.                                     *
****************************************************************
* PROBLEM DESCRIPTION: Thread loops in DSNLCITR or DSNLCVTR    *
*                      if IFCID 180 tracing is started.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When IFCID 180 tracing is enabled, DDF related logic is
incorrectly interpreting user data as a DRDA code point and
hence gets into a tight loop.

    



Problem conclusion


    

  • DB2 for z/OS processing has been changed to correctly recognize
user data and not misinterpret it as a DRDA code point.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PM55373
    • 

  • 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
    2012-01-04
    • 

  • Closed date
    2012-03-07
    • 

  • Last modified date
    2012-04-03
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    
UK76870 UK76871
    

    • 



Modules/Macros


    

  • DSNLCITR DSNLCVTR

    



Fix information


    

  • Fixed component name
    DB2 OS/390 & Z/
    • 

  • Fixed component ID
    5740XYR00
    • 



Applicable component levels


    

  • RA10  PSY  UK76870
       UP12/03/23  P  F203
    • 

  • R910  PSY  UK76871
       UP12/03/23  P  F203
    • 



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:
            

            03 April 2012
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback