DSXchange

I'm sure there is but you'd probably need to ask support to get the official answer as to the size of it.

A job can be written using the various DSGetLog* functions, check the help. Or you could script a solution using 'dsjob' with the equivalent 'get' options.

Not familiar with 8.x connectors yet, but you should always parameterize all of your connection information. A set of Job Parameters would do the trick.

And? The data types have nothing to do with your issue.

You mark one field as the 'repetion key', not all - and that generally the 'deepest' so try 'sal'. And no, while you can cat the contents of the file, the suggestion was to simply use the stage to get the filename. Check Ernie's blog post on the subject:

http://dsrealtime.wordpress.com/2007/12 ... -a-source/

arun_kumar wrote:s i have
s only one job is giving this erroe
s i have that prvilages

's'? What, are your 'y' and 'e' keys wearing out?

I know you said the design 'should not change' but why not just put the PX job inside the Sequence job?

You need to specify a repetition key - what happens when you do that?

Ah... ok, just wondering as for some reason it seemed reasonable to me that it might not and I didn't recall ever specifically testing that. [shrug]

However, jobinfo is returning a 99 - not a 98 - so that should mean it is compiled.

Routines are expected to return a zero, but it only comes into play when the 'automatic' handling is enabled. You just have to get used to the fact that routines that return other values (like your date) will always be problematic unless you explicitly handle the 'failures' yourself. Odd that you sa...

Two specific trigger types, I guess I should have said.

Ok, so one custom trigger (which doesn't count as error handling) and one other trigger which you called the 'failure trigger' - what type is it?

I assumed successfully compiled and run before this. Would -jobinfo work on an uncompiled or 'unsuccessfully compiled' job?

Search more better, we've talked about this more than once. That's one of the dangers of 'user defined' sql, especially when you don't understand the rules required by the stage. Check some things for a reference lookup: 1. You must select the same number of fields as you have columns defined in the...

That's ok and easy to solve - and has been discussed here quite a number of times. A routine that does not return a zero is considered to have failed when you have the 'automatically handle activities that fail' option turned on. If you read the online help for the Sequence job property page that co...