IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Unsuccessful bind problem has been encountered


IBM Mainframe Forums -> DB2
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
ksivalakshmi

New User


Joined: 15 Nov 2005
Posts: 2
Location: Hyderabad

PostPosted: Wed Dec 14, 2005 7:05 pm
Reply with quote

while compiling a module, unsuccessful bind problem has been encountered as described below.

Can anyone please tell me how to find which user has locked a table. First of all can all the users get that information or do only the administrators have the privilege?


Code:

READY                                                                           
  DSN  SYSTEM(C30T)                                                             
DSN                                                                             
  BIND PACKAGE(ISSR3C)        MEMBER(G00P220)        OWNER(GENCUS?I)        QUAL
      RELEASE(COMMIT) CURRENTDATA(NO) ACTION(REP) VALIDATE(BIND)        ISOLATIO
DSNT500I  % DSNTBCM2 RESOURCE UNAVAILABLE                                       
           REASON 00E30083                                                     
           TYPE 00000801                                                       
           NAME ISSR3C            .G00P220 .17C1B8FA0D216418                   
DSNT233I  % UNSUCCESSFUL BIND FOR                                               
           PACKAGE = IPSC30T.ISSR3C.G00P220.()                                 
DSN                                                                             
  END                                                                           
READY                                                                           
END                                                                             


Thanks in advance
Back to top
View user's profile Send private message
muffirulz

New User


Joined: 14 Sep 2005
Posts: 74
Location: Atlanta, (USA)

PostPosted: Thu Dec 15, 2005 2:52 am
Reply with quote

hi

Well as it shows that the error has occured due to deadlock condition, there are many ways. One is that you can externally go to db2 bind options and give a bind command and check if it throws the error or else check which tables u are using and then see if anyone of that table is giving you a deadlock condition.
Back to top
View user's profile Send private message
senthilssg

New User


Joined: 09 Dec 2005
Posts: 64
Location: USA

PostPosted: Thu Dec 15, 2005 11:03 am
Reply with quote

Hi,

this problem may be due to deadlock or timeout . mostly resource unavailable problem is due to the timeout .actually your job is waiting for long time to get the resource . if it is crosses the time limit which is set in installation of DB2 .

you can tell to db2 admin people to check the any job is hold that resource or not . if it so cancel the thread which is hold that resource and you try to rebind it


Regards
senthil

''correct me if i am wrong''
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> DB2

 


Similar Topics
Topic Forum Replies
No new posts Map Vols and Problem Dataset All Other Mainframe Topics 2
No new posts z/vm installation problem All Other Mainframe Topics 0
No new posts WER999A - UNSUCCESSFUL SORT 8ED U Ab... SYNCSORT 5
No new posts Job scheduling problem. JCL & VSAM 9
No new posts Problem with IFTHEN=(WHEN=GROUP,BEGIN... DFSORT/ICETOOL 5
Search our Forums:

Back to Top