There are two ways to handle this situation. To get your TIM going, perform this Workaround. To fix the situation, perform the Resolution.
To correct the issue, remove the /var/lock/subsys/tim file and restart the TIM with the command "service tim start".
One possible cause preventing the TIM from gracefully shutting down is a timeout present within the shutdown logic of the TIM. By default TIM will wait 60 seconds for the process and sub processes running on the OS to terminate. Should this process fail to complete in 60 seconds, TIM will report an error, such as "Stopping tim: /sbin service: line <line number>: <pid> Killed....", and fail to delete /var/lock/subsys/tim as described above. This issue is especially prevalent when there are large number of TIM worker processes (typically in a one to one ratio with the number of processors available on the server).
To permanently address this issue, it is recommend that you raise the timeout present within the shutdown logic of the TIM. To do this...
-Navigate to http://<TIM_Computer_Name or IP_Address>:<Port_Number>/cgi-bin/ca/apm/tim/index
-Click Configure TIM Settings
-Click Define a new value.
-Type the name: ExitWaitSeconds
-Enter a value. The default is 60 when undefined.
-Click Add. The new value takes effect immediately. Restarting the TIM is not necessary.