View previous topic :: View next topic
|
Author |
Message |
blpraveen123 Currently Banned New User
Joined: 26 Apr 2007 Posts: 12 Location: Mysore
|
|
|
|
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 |
|
|
guptae
Moderator
Joined: 14 Oct 2005 Posts: 1208 Location: Bangalore,India
|
|
|
|
Hi there,
Does it show which resource is not availbale? |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
posting the full job sysout might be of more help to analyze the failure
regards
e.s |
|
Back to top |
|
|
senthilssg
New User
Joined: 09 Dec 2005 Posts: 64 Location: USA
|
|
|
|
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 |
|
|
Mahesh-Frame
New User
Joined: 06 Sep 2007 Posts: 3 Location: Noida
|
|
|
|
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
|
|
Back to top |
|
|
mbr_raja
New User
Joined: 15 Nov 2004 Posts: 26 Location: Chennai, India
|
|
|
|
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 |
|
|
|