Skip to main content
M
MH_1046367610-Marble
10-Marble
March 21, 2023
Question

Abort WVS custom jobs from WVS Job Scheduler Administration

  • March 21, 2023
  • 16 replies
  • 3475 views

Hi,

we think about generating custom jobs to create viewables for latest items that don't have one. Alone the "geneate jobs-job" runs a couple of days (testsystem) and would block users from productive work as the cad worker runs full.

 

Is it possible to abort these jobs?

 

Our plan would then be something like:

  1. Stop publishing queues
  2. Run latest-no-viewables-Job
  3. Abort latest-no-viewable-Job (after e.g. generation of 5k jobs in the queue)
  4. Filter queue (remove .drw, .asm etc.)
  5. Start publishing queues

Regards

16 replies

avillanueva
avillanueva23-Emerald I
23-Emerald I
March 21, 2023

Do you have these custom jobs implemented?

https://www.ptc.com/en/support/article/CS211115?source=search

These are great for assisting with what you are asking. You should be able to change filters until you get to a point where you can get the drawings and assemblies done. This will avoid too much of manually removing jobs already queued up. It is really easy however to delete jobs using provided table filters. however there is a table limit of what is displayed. 5000 would far surpass that. You can also take the approach of product by product scheduled jobs to batch things. There is also a CSV file if you need to tailor it using a defined list.

I myself made use of the last option with publish actions on the search results. This way I can search for latest items and define via a search query, Select only the number I want to publish in that session and submit them. I then control what is publish and how many will queue up. 

M
MH_1046367610-MarbleAuthor
10-Marble
March 21, 2023

Hi,

thanks, I bookmarked the article. But we currently try to achieve a few things ootb (<-> without customization).

Regards

avillanueva
avillanueva23-Emerald I
23-Emerald I
March 21, 2023

In that case, to your original question, it should be possible the way you described. You will see the queue jobs fill up but nothing will be processed until you turn them back on. I am not 100% sure how responsive it will to your request to abort the generation of jobs. Any idea of how many you will get? It will only increase your effort in reducing the jobs to a neat, nightly batch. Those additional jobs are really useful but I cannot find fault with your approach. 

Terms & ConditionsAccessibility statement