DSXchange

Have you tried leaving anything in square brackets out initially? They mean the parameter is optional. Also note that it says "useid" not "userid" and it is not expecting anything be passed along with it. Include "-useid" when you pass in the jobid (which you don't have...

Cool... so I'm going to close this conversation out and if you have something else that comes up, let's just start a new post rather than continue to pile on this one.

Thanks.

Anything less than 8.x does not have an XMETA repository.

My "if" was a little... rhetorical.

I run the script as followed: c:\script_folder\script_job.bat host username password project DSN_Name UserName Password JobName As noted already by priyadarshikunal, the batch / script as posted only expects four parameters on the command line. Anything after that is ignored and is expected to be h...

Yup, the OP already noted that. Thanks.

What's going to schedule the script?

I'm assuming you already have the job working outside of this script, yes? So if that's true and you already know the values the parameters need to have to run the job, if you still have an issue then it is specific to the script itself.

Don't really understand the "job scheduling in Director doesn't work" statement but I'll take it at face value. Regardless, still don't need a script. On the subject of once a day, schedule (however) the Sequence to start running first thing in the morning. The WFF will cause it to sit run...

On the subject of a Sequence job, at its most basic all we're talking about is a Wait For File stage and a Job Activity stage. Next question would be - how often during the day will this flag drop? It is quite simple to handle if it is once per day, if it can be multiple times during the day that co...

Knew that was yours, Kim. Or at least started off life as yours.

Syang - all you need is a Sequence job for that, no script required. No need to overly complicate things.

You're not sure where the jobs themselves live? That would be in each of your Project directories but that knowledge isn't needed in order to run them, all you need is the name of the project. You've picked quite a goofy example to start with. Usually a batch made to run jobs is generic and can run ...

Not that I'm aware of. You'd either need to roll your own or just stick with the native functionality in your database.

Probably other ways but off the top of my head:

Current_Month = OCONV(@Date,"DM[2]")

Your month parameter will also have to be a string, of course.

Can you detail for us the nature of the progress you made, what you've done to get this far? And also - you get that error message when / doing what exactly?