DSXchange

You have another thread active on the quotes issue. You might also try spelling SELECT correctly in the inner query.

Try NAP command instead of SLEEP. The argument for NAP is milliseconds.

Craig will shortly move this post to the server job forum.

Go to the DSXchange home page and link to the webinar on grid enablement that was presented recently. This should provide an extended answer to that question.

No I didn't. I asked a question designed to find out where this code was generated. That question has not been answered. Ideally please post the wrapper script that AutoSys uses. Please also report whether by "log" you mean the DataStage job log or the AutoSys log.

Server: (Oconv(Field(timestamp2," ",1,1),"DYMD") * 86400 + Oconv(Field(timestamp2," ",2,1),"MT")) - (OConv(Field(timestamp1," ",1,1),"DYMD") * 86400 + Oconv(Field(timestamp1," ",2,1),"MT)) Parallel: SecondsSinceFromTimestamp(...

Or use NextSurrogateKey() function if you actually want a surrogate key value.

There's no best way.

Use the method that's appropriate for your requirement. This might be hard coded values in Job activity, passing from the sequence parameters, use of Parameter Sets, use of environment variables set for the project and more.

Why did you post this in the server job forum?


What is your actual question?

That's a hazard of using user-defined SQL - the stage does not enforce that you use the table name in your SELECT statement. Indeed, the table name is probably a hangover from when the stage used generated SQL, and is ignored when user-defined SQL is used.

It would seem that, like James, I have used up my thinking quota for the month.

Those routines are here - however there's no TimestampDifference routine amongst them. The approach is still correct, even if I did specify a parallel function. :oops: Convert timestamps to seconds and subtract. To convert a timestamp to seconds since 1967-12-31 23:59:59 in a server Transformer stag...

That should work as an implicit conversion.

Apply SecondsSinceFromTimestamp() to each timestamp using the same base (maybe 1970-01-01 00:00:00) then subtract.

The ORCHESTRATE object is not available till the input link of the target stage (the one that writes to the table), so you can't use it in a Before-job subroutine. If you're referring to Before SQL in the ODBC Connector stage, the problem is slightly different. Values of properties of the ORCHESTRAT...

Check the script that Autosys runs to discover whether the exit status from dsjob is the exit status of that script and that the -jobstatus option is included in the dsjob command.