Hi I'm new on this forum who recommended me
I need your help
had a problem with the database and since the connection is reestablished control m
but now are jobs that do not end in yellow and the sysout indicate that they have already completed
ah agent is lowered, there has been kill -9 and jobs not change their status.
if they respond better in Spanish
Jobs in Yellow not ends
- nicolas_mulot
- Nouveau
- Posts: 149
- Joined: 07 Jan 2010 12:00
Geordie
Firts get your orderid in alphanumeric format (from the “Active” tab of your job properties). Copy the value in the clipboard (e.g.: 05xih).
Then open a terminal (DOS prompt if Windows, native terminal or putty if Unix/Linux). If Linux of Unix, logon with the control-m account.
Convert the orderid into numeric using the p_36 utility:
Example: p_36 05xih
Will return 276713
Then, open the sql prompt by typing “SQL”, which connects you to the control –m database, then enter the sql request as follows:
update CMR_AJF set STATUS=’N’, STATE=’5’ where orderno=<your>
Send the request by either “go” (MS/SQL ) or “;” (Oracle)
Go back to your EM GUI, then hold and free your job. It should turn into a manageable colour (red or gray) then you can hold-delete or rerun it
Cheers
Nicolas Mulot
Firts get your orderid in alphanumeric format (from the “Active” tab of your job properties). Copy the value in the clipboard (e.g.: 05xih).
Then open a terminal (DOS prompt if Windows, native terminal or putty if Unix/Linux). If Linux of Unix, logon with the control-m account.
Convert the orderid into numeric using the p_36 utility:
Example: p_36 05xih
Will return 276713
Then, open the sql prompt by typing “SQL”, which connects you to the control –m database, then enter the sql request as follows:
update CMR_AJF set STATUS=’N’, STATE=’5’ where orderno=<your>
Send the request by either “go” (MS/SQL ) or “;” (Oracle)
Go back to your EM GUI, then hold and free your job. It should turn into a manageable colour (red or gray) then you can hold-delete or rerun it
Cheers
Nicolas Mulot
I was a percussion major when I was in university, and during a particular rehearsal of the student orchestra, my section kept getting things worse.“When you’re too dumb to play anything,” the professor conducting us sneered, “they give you a couple of sticks, put you in the back and call you a percussionist.”"A friend next to me whispered, “And if you’re too dumb to hang on to both sticks, they put you in front and call you a conductor.”
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
--------------------
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