DSXchange

What happened to "Schedule job in director every hour without instances"?

OAC wrote:It is not User Defined Query

I find that... interesting. I've never seen generated SQL not 'bind all columns', it usually takes a people to do that.

Either that or start using the OCI stage and 'Plug-in Metadata' rather than ODBC.

It's not that it can't handle a sequencer job with 'multiple paths', its just that its original functionality was to handle failures in the Sequencer itself. Job failures run by the sequencer are handled by triggers off the Job Activity stage. Your 'better/easier way' is to upgrade to 7.5. Pretty su...

No. Doing so would mean no parallelism.

Read vmcburney's reply here for a nice discussion on 'between' conditions and the sparse lookup.

I believe the 50 warnings limit before the job aborts is coded within DS and you can't change that. What I normally do is fix the cause of the problem, if you are generating duplicates then try to find a way to dedupe for instance. Very true, the best way to solve any problem like this is to ensure...

Welcome aboard. Typically, you define a Job Parameter and assign it the value of the environment variable. You then use it in your job like any other parameter. You will, however, need to clarify what exactly this means before we can make any meaningful comments: Basically, I have used env variable ...

No problem, Paul.

Let us know if you get this worked out.

It's called "Filter" before the table names are listed. Sometimes "Advanced". And unfortunately it doesn't exist in the OCI stages. Is there a way to filter out what tables to get from the database, instead of having to get the list of ALL tables? What could be the cause of this delay? What delay i...

Cool, thanks. Not much time for fun stuff like this right now but I'll check it out when I can.

Just take each job and 'Add to Schedule' multiple times.

From the Developer's Guide: An exception activity handles the situation where a job in the sequence fails to run (other exceptions in the job sequence are handled by triggers). An exception activity can only have a single unconditional output trigger, so does not require a Triggers page. It has no i...

Has to be user defined SQL to generate errors like this. The parameter markers they are using (:1, :2, etc) don't match with the columns defined in the stage. For example, if you have five columns in the stage you must have five parameter markers in your sql numbered from :1 to :5.

The post you replied to was a year and a half old. They probably got things all straightened out by now.

StefL wrote:However, dsjob seems to report 0 as status code regardless if the -wait option is used or not.

Use -jobstatus rather than -wait if you want the codes you've listed to be returned by dsjob.