I started a database with acess(force) now even after I start it with rw the runstats job gives an error

Hi  I ran a RUNSTATS on a table space and it gave me s322 on my job which indicates time out.
Now when I checked this table space was in RW,UTRW so I started the database with access(force)
.Now when I run the runstat again it is giving that access(force) prevails and runstats cannot be performed.Now I restarted again with access(rw) but still it gives the previous error.Please help
NigelleAsked:
Who is Participating?
 
muga11Connect With a Mentor Commented:
You have to terminate utility. Issue db2 command, to check the status of utility:
- dis util (*)

if there is stopped utility then terminate it:
- term util (utilid)

0
 
momi_sabagCommented:
what do you mean by the previous error  ?
the s322 error ?
if so, you have 2 options :
1) increase the time limit in your jcl
2) make your job process less, if you runstat several objects then split it to several jobs
if you only process one object you can try to process only the table and not the indexes and then runstats the indexes in a different job, or you can try to use the sample parameter in order to scan less data
0
 
NigelleAuthor Commented:
The problem here is after the ts has been started with access(force),I am not able to bring it back to r/w.can you please suggest something.start with acess(rw) is not working.start process executes succesfullya and ts comes to rw mode but when I run the runstats it it says table space in access(force).
I have already increased the time to time =1440
I am sure it is not because of splitting.
it is just because the utility is still finding the table in access(force) whatever that means.
0
 
momi_sabagCommented:
can you post here the exact output you recieve in sysprint ?
0
All Courses

From novice to tech pro — start learning today.