TERMINATE A STOPPED DB2 UTILITY
When your DB2 LOAD JOB stops with some issue, your TABLESPACE status will show UTUT, which means the LOAD utility that used in your job has actually held your TABLESPACE. At this point, you cannot even do a SELECT on your Table. So to re submit the LOAD job or to access the DB2 table, you have to first terminate the utility that has held your TABLESPACE. The UTILITY id usually will be your JOB NAME or you can even get it from the abended JOB in the SPOOL.
Once you have the UTILITY ID, follow the below steps to terminate it.
- Go to DB2I(DB2 interactive functions).
- Select your DB2 subsystem.
- Go to option 7 (DB2 commands).
- Use the command “-DISPLAY UTIL(*)” to see the utilities currently being executing or stopped.
- Use the command “-TERM UTIL(MYUTIL)” to terminate the problem utility id “MYUTIL”.
Note: This post is just to let you know the way to terminate the utility. Please read the comment from Jun below. As mentioned, this should be considered as last resort. It is always best to check with DBA before performing. In testing phase, if you are sure, you are not losing anything, you can go ahead and do this.
——————————————————————————————————–
In United States, If you would like to Earn Free Stocks, Credit card Points and Bank account Bonuses, Please visit My Finance Blog
——————————————————————————————————–
You may also like to look at:
| Working on Mainframes – Is Change to a different technology necessary |
F1 for Mainframe 
This is a last resort. Don’t just do a -TERM UTILITY without checking what phase it is in (even if its in STOPPED status). Or else, you’ll end up recovering the table space — and what a nightmare if you have more than one table in a TS !!
and don’t smile, its not good to other DBAs, even if you know you can’t do anything else but to recover that TS. Other DBAs might perceive your smile as if you think you’re laughing at a “joke”. — recovering a big TS is no joke! really! But just smile, not worth worrying or frowning 1
Yes I Agree with you Jun. When i posted this, i was doing my testing and all the tables were load replaced and each table was in different tablespace. At that point, this was valid to do. But in general, as you have quoted, either in TEST or PROD region, it is always advisable to get in touch with DBA and see factors that you have mentioned. Thanks for the update.