|
(→Job Step Traces)
|
(→Command Traces)
|
| Line 65: | |||
| == Command Traces == | == Command Traces == | ||
| Usually hidden behind the scenes, these might also need updated if any of the prior failed. | Usually hidden behind the scenes, these might also need updated if any of the prior failed. | ||
| - | === SQL to Set All Running Command Traces to a Status === | ||
| - | <pre>UPDATE JOB_STEP_CMD_TRACE SET STATUS = 'XX' WHERE STATUS = 'YY';</pre> | ||
| + | <table border=2 cellspacing=2 cellpadding=2 align=center> | ||
| + | <tr> | ||
| + | <th bgcolor=#000000><font color=white>Type</font></th> | ||
| + | <th bgcolor=#000000><font color=white>SQL</font></th> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td align=center bgcolor=#808080><font color=white>set all running command traces to a status</font></td> | ||
| + | <td><font face=monospace>UPDATE JOB_STEP_CMD_TRACE SET STATUS = 'XX' WHERE STATUS = 'YY'</font></td> | ||
| + | </tr> | ||
| + | </table> | ||
| == Lockable Resources & Lock Holders == | == Lockable Resources & Lock Holders == | ||
| Lockable resources, whether defined or scripted, as well as any resource acquired & holding a lock, should be present in the locking tables of anthillpro. If the locks need cleared, and cannot be revoked manually (or there are simply too many to revoke) it is possible to clean these up via SQL. | Lockable resources, whether defined or scripted, as well as any resource acquired & holding a lock, should be present in the locking tables of anthillpro. If the locks need cleared, and cannot be revoked manually (or there are simply too many to revoke) it is possible to clean these up via SQL. | ||
