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

Unable to BIND: Resource Unavailable


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

New User


Joined: 26 Apr 2007
Posts: 12
Location: Mysore

PostPosted: Mon Sep 24, 2007 5:40 pm
Reply with quote

Hi all,
when i try to bind the COBOL-DB2 Program using IKJEFT01 the step return code was 8 and the Bind was unsuccessful the follwing error mesage displayed.

Resource Unavailable
Reason 00D70014
Type 00000220

What is the error?
Back to top
View user's profile Send private message
guptae

Moderator


Joined: 14 Oct 2005
Posts: 1208
Location: Bangalore,India

PostPosted: Mon Sep 24, 2007 5:41 pm
Reply with quote

Hi there,

Does it show which resource is not availbale?
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10873
Location: italy

PostPosted: Mon Sep 24, 2007 5:45 pm
Reply with quote

posting the full job sysout might be of more help to analyze the failure

regards

e.s
Back to top
View user's profile Send private message
senthilssg

New User


Joined: 09 Dec 2005
Posts: 64
Location: USA

PostPosted: Tue Sep 25, 2007 10:44 am
Reply with quote

Hi praveen,

According to Reason code (00D70014 ) and Resource type (00000220 - VSam dataset ) , the VSAM datasets which is corresponds to your tablespace reached max extents .

Note :

123 - is max extents for single volume VSAM dataset
255 - is Max extents for Multivolume datasets


Please use ISPF 3.4 option , to the check the max extents of the VSAM datasets for the tablespace . You can get the name of the datset from the joblog of your job .

Ask your DBA , to Alter the tablespace with more value of priqty and secqty . After that ask him to REORG the table space also .
This will resove the issue .

Regards
Senthil
Back to top
View user's profile Send private message
Mahesh-Frame

New User


Joined: 06 Sep 2007
Posts: 3
Location: Noida

PostPosted: Tue Sep 25, 2007 12:24 pm
Reply with quote

Hi,

The table might have got corrupted.

We had the same issue , and we raised a request to DBA team
to delete and create the table.This time with larger space.

Mahesh
icon_biggrin.gif
Back to top
View user's profile Send private message
mbr_raja

New User


Joined: 15 Nov 2004
Posts: 26
Location: Chennai, India

PostPosted: Wed Sep 26, 2007 5:29 pm
Reply with quote

The problem is due to space is not available within the tablespace of indexspace. You can try to use the option 3.4 and give the underlaying DB2 Vsam dataset and press f11 key (Function key F11). It will show you the free space, number of extents. Check the no. of extents if goes above 251 in both tablespace and indexspace.

The solution to this problem is to do alter tablespace to increasing primary and secondary quantity and do the Reorg utility inorder to reclaim the space.
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 Infosphere Optim - unable to save Col... IBM Tools 0
No new posts DFHCSDUP EXTRACT unable to open outpu... CICS 5
No new posts Unable to connect FTP over TLS from z... All Other Mainframe Topics 5
No new posts JCL for pl1 db2 precompile, compile a... JCL & VSAM 4
No new posts IEF085I REGION UNAVAILABLE,ERROR CODE... Java & MQSeries 0
Search our Forums:

Back to Top