Solution Description
--------------------
1) Download the ForceEndJob.pl script from
ftp://ftp.bmc.com/pub/control-m/opensys ... eEndJob.pl
2) Determine the order id of the job that needs to be ended, via the Control-M/Enterprise Manager GUI in the Active tab of the Job Editing Form or via the ctmpsm utility on Control-M/Server.
NOTE: If the job is still executing on the Control-M/Agent, then this script will not end that process but only change it's state within Control-M/Server. Once the actual job ends on the Control-M/Agent after running ForceEndJob.pl, this status would NOT be reflected on Control-M/Server.
DO NOT run this script for a job that is still truly executing on the Control-M/Agent.
If the job is still executing on the Control-M/Agent, then use the Kill option in the Control-M/Enterprise Manager GUI or the ctmkilljob command on Control-M/Server.
3) Login as the Control-M/Server user and navigate to the location where ForceEndJob.pl was placed.
4) Use the following syntax to execute the ForceEndJob.pl command:
Unix Usage:
$HOME/bmcperl/perl ForceEndJob.pl <Order> [Y|N (debug)]
For example: $HOME/bmcperl/perl ForceEndJob.pl 0001aw
Windows Usage:
<CONTROL>\bmcperl\bin\perl ForceEndJob.pl <Order> [Y|N (debug)]
For example: "C:\Program Files\BMC Software\CONTROL-M Server\bmcperl\bin\perl" ForceEndJob.pl 0001aw
Where 0001aw is the Order ID of the problematic job.
NOTE: When the debug flag "Y" is included, log information will be written to the following locations:
<Control>/proclog
<Control>/tmp
Information from running the script similar to the following will be written to the Control-M job log.
MM/DD/YY HH:MM:SS UT5216 JOB FORCED TO END NOTOK BY USER username
MM/DD/YY HH:MM:SS UT5201 SHOUT TO IOALOG PERFORMED