03-29-2018 05:30 AM - edited 03-01-2019 09:28 AM
I have a situation where there are 300+ Tidal jobs defined to run on a particular agent/adapter. I need to move 200 of them to a different agent/adapter. Is there an easy way to do this without having to open each job up one at a time?
Thanks in advance.
Solved! Go to Solution.
04-17-2018 11:52 AM - edited 04-17-2018 11:55 AM
You can also make use of the SACMD utility which allows for batch processing (mass updates).
Step 1.
The command can be as simple as: modrule -i job_ID -h agent_name
Step 2.
Insert the command above into a text file, and insert additional command lines as needed for each job ID
Step 3.
Now to run the batch file, type: sacmd file filepath_of_text file
Step 4.
Kick back, relax, and enjoy the popcorn!!!
Best,
Derrick Au
04-04-2018 09:20 AM
Hey Bruce
There is no native way using the client to change that many jobs to a different agent unless those jobs were inheriting the agent from a parent group.
Bob
04-17-2018 11:52 AM - edited 04-17-2018 11:55 AM
You can also make use of the SACMD utility which allows for batch processing (mass updates).
Step 1.
The command can be as simple as: modrule -i job_ID -h agent_name
Step 2.
Insert the command above into a text file, and insert additional command lines as needed for each job ID
Step 3.
Now to run the batch file, type: sacmd file filepath_of_text file
Step 4.
Kick back, relax, and enjoy the popcorn!!!
Best,
Derrick Au
04-19-2018 06:42 AM
Thank you so much, Derrick. That worked perfectly.
Sincerely,
Bruce
04-04-2018 09:23 AM
If you have the 6.3 transport utility, you could export all the definitions, update the agent and re-import the updated XML, no?
04-04-2018 09:29 AM
That sounds doable. I'm going to look into that further.
Thanks,
Bruce
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide