[narendra]

Hi,
I was trying to use the command object for a particular requriement, I have used the same as below. This action did not perform any activity and did not deschedule the job that it has to. I was checking the opsp log in the server and could notice that this returned as an error.

Command used: opscmd object -obj <[JOB_NAME]> -inst <INST_NAME> -action f_desched

Error on the server:
10/06/24 12:03:56 E (18493) 45.ThreadExecCommand: Execution command 'opscmd object -obj JOB_NAME -inst INST_NAME -action f_desched': ret '32512'

Can someone help me if I have done something wrong here...

Regards,
Narendra.

[pascal]

Hello Narendra,

It's better to use a job and inside the script do the 'opscmd object',
because the 'command object' don't return the errors.


Regards
Pascal

[narendra]

Hi Pascal,
That helped.. Thanks alot. But when the timer is descheduled, the job following the same also got descheduled. Is there any way that we can avoid the same and just get the timer descheduled?
Or alternatively, what can be used for terminating the timer instead of descheduling ? f_term ??

Appreciate your response. Many Thanks..

Regards,
Narendra.

[pascal]

For the job following you must consult the link evaluation table.
(I attach it)

Attached File(s)

 links.JPG ( 73.56K ) Number of downloads: 2