DSXchange

Hi All

I have a requirement of , create a script which will scan through all the set of jobs and then compiles if there are any jobs with "Not Compiled" State . Can anybody help me in this .

I would really appreciate your time and help on this.

Seems like a strange requirement, why would you need to do such a thing?

Not sure how simple this would be, regardless. Normally I'd say do this with "dsjob": first with "-ljobs" to get their names and then iterate thru the names using "-jobinfo" to see what state each one is in. Problem is, jobs in a "Not Compiled" state cannot be found by the "-jobinfo" option, you get an error instead. Hmmm... unless you assume that the:

ERROR: Failed to open job
Status code = -1004

messages it logs in that case can be assumed to mean a job in that status. After that, use dscc.exe to compile them.

All from the client side.

This can be done only on client machine .Because you want all the jobs in uncompiled state to be compiled through script .

Use : -jobstatus in tandem with dscc .

Also ...dsjob -ljobs as mentioned by craig

Even easier is this approach. Use the Multiple Job Compile tool and check the "select only uncompiled jobs" check box.

nagarjuna wrote:Use : -jobstatus in tandem with dscc .

Small correction: "-jobinfo" as there is no "-jobstatus" option.

ray.wurlod wrote:Even easier is this approach. Use the Multiple Job Compile tool and check the "select only uncompiled jobs" check box.

True... except for the apparent need to schedule this so as to run unattended.

How often do you need to check for uncompiled jobs?

There's only one way they can become uncompiled, and there's always a person present when that happens.

I know, which is why I asked why one would 'need' such a thing.

Thank you for all your responses .

we got this requirement because in our environment , by mistake some of the other people migrating the jobs but forgetting to compile and because of which we are getting problems .

To avoid that situation , we want to create a script which will scan through all the jobs and want to compile the jobs which are not in the compiled or runnable state.

Then while exporting use the option with executables ..

Or use Version Control to automate the process!