Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

DSNR035I with BIND parameters

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2
View previous topic :: :: View next topic  
Author Message
eprasad629

New User


Joined: 25 Sep 2009
Posts: 9
Location: Bangalore

PostPosted: Thu Jul 07, 2011 11:00 am    Post subject: DSNR035I with BIND parameters
Reply with quote

Hi,

Does this DSNR035I message has anything to do with BIND parameters? This is because, after making a few changes to a program, I'm keep on getting this message.

Also, the programs that normally executes in 10 minutes, consumes nearly an hour after the implementation of new changes.

Should I check for cursors to corner this DSNR035I message? Are there any specific SQL code present, if mishandled, will raise this message?

Kindly let me know your suggestions.

Thanks a lot for your time
Back to top
View user's profile Send private message

dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne

PostPosted: Thu Jul 07, 2011 11:33 am    Post subject:
Reply with quote

Praelay,

it is early and I don't have enough self-control to say anything other than:

Quote:
Programmer response

Ensure that the application commits frequently enough, or consult with your DB2 administrator about decreasing the frequency of the check.
Back to top
View user's profile Send private message
gylbharat

Active Member


Joined: 31 Jul 2009
Posts: 565
Location: Bangalore

PostPosted: Thu Jul 07, 2011 11:35 am    Post subject:
Reply with quote

Code:

 DSNR035I  csect-name WARNING - UNCOMMITTED UR AFTER nn CHECKPOINTS -         
        CORRELATION NAME = xxxxxxxxxxxx   CONNECTION ID  = yyyyyyyy   LUWID   
        = logical-unit-of-work-id=token PLAN NAME = xxxxxxxx AUTHID =         
        xxxxxxx END USER ID = xxxxxxxx TRANSACTION NAME = xxxxxxxx           
        WORKSTATION NAME = xxxxxxxx                                           
                                                                             
 Explanation:  This message indicates that during checkpoint, DB2             
 encountered an uncommitted UR that has an INFLIGHT status.                   
                                                                             
 The value nn is cumulative, and it indicates the number of checkpoints       
 taken since the beginning of the UR. CORRELATION name, CONNECTION ID, and   
 LUWID together identify a thread associated with the UR. If the LUWID is     
 an '*', it indicates that the thread originated at this site.  token is a   
 unique token number associated with the LUWID. PLAN NAME and AUTHID         
 further identify the thread associated with the UR. If the thread was       
 created with client End User information, the End User's ID, TRANSACTION     
 NAME, and WORKSTATION NAME will be displayed. Otherwise, these fields will   
 contain an '*'.                                                             
                                                                             
 System Action:  DB2 continues processing. If statistics class 3 is turned   
 on, IFCID 0313 is written.                                                   
                                                                             
 System Programmer Response:  Consult with the application programmer to     
determine if this is a problem UR.  See Part 4 (Volume 1) of DB2         
Administration Guide for more information about problems caused by       
uncommitted URs. If the UR is caused by an application program, you can   
use CANCEL THREAD to delete the UR, if necessary. If an uncommitted UR is
deleted, DB2 will undo the changes. The amount of time required for this 
process depends on the amount of work done by the UR.                     
                                                                         
Programmer Response:  Ensure that the application commits frequently     
enough, or consult with your DB2 administrator about decreasing the       
frequency of the check.                                                 
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2 All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts CICS NEW SIT PARAMETERS CICS BEHAVIOR... Kyle Carroll CICS 0 Fri Nov 04, 2016 11:55 pm
No new posts Symbolic Parameters in SYSIN DD state... madishpa DFSORT/ICETOOL 3 Mon Jun 27, 2016 6:23 pm
No new posts Multiple parameters Csongor All Other Mainframe Topics 16 Thu Jun 09, 2016 7:54 pm
No new posts SYSUT2 - CONFLICTING DCB PARAMETERS raulravi7 JCL & VSAM 6 Thu May 19, 2016 9:43 am
No new posts What's plan, package, bind ? jackzhang75 DB2 2 Sun Feb 28, 2016 7:29 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us