Joined: 06 Jul 2010 Posts: 662 Location: Whitby, ON, Canada
The command was run under IKJEFT01, the TSO terminal monitor program. IKJEFT01 did not fail, so the RC was zero. It does not care that the command failed. Search the archives; there have been many threads on the topic of return codes and IKJEFT01.
The resource identified could not be started because it was unavailable.
The resource could be a database, a table space, an index space, or a
partition within a table space or an index space.
In our case it was a table space IA0042I .WTA1 which was held by some other job or user as implied by the reason code 00C900A8
The table space, index, or partition could not be started because of a
failure to acquire the lock. Activity on the table space, index, or
partition must quiesce before the START DB ACCESS(FORCE) command can acquire the necessary lock.
But I am facing 2 challenges here:
1. How to make sure that this type of error does not happen. i.e. Need a mechanism to check if the START DB command fails I am able to track it. The return code is zero. I would be glad if anyone can advise on this.
2. Unable to find out what was holding up the tablespace when the START DB command was run which caused the command to fail