DSXchange

A parallel routine? How are your C++ programming skills? Regardless, I don't see the point - stick with whatever your current resolution is.

And also - while all help is appreciated - you might want to find more recent posts to be helping with.

Those kind of messages are common for any Server job with hashed files when it is reset. Seems odd to me that it takes that long, I don't recall seeing that kind of behaviour. Wait however long seems appropriate in your environment, all I'm saying is I've always had to do the same thing... just not ...

I believe that they are actually created on disk and then loaded to memory...

I personally don't do the Y/N thing, preferring to treat the stage variable as a Boolean since the expression will automatically resolve to true or false. I'd also suggest you always use meaningful names for your stage variables. Stage Variable svItemIs100: Inlink.Item = 100 Constraint Good row: svI...

Those have transforms associated with them, from what I remember. Once those are in place they no longer appear in the list of routines.

I've seen the same thing which is why our dsjob wrapper script always waited after resetting. We only waited something like 5 seconds from what I recall, shouldn't need to be two minutes.

Yes, you could, but I'm not sure I'd add the 'complexity' of a lookup when this can be solved with either the proper expression or a simple constraint to a reject row set to abort after 1 row.

Interesting but that must be behaviour that was changed in 8.x: When Auto-purging is in use, all instances of a job will be purged, without checking for the success or fail status. Before 8 auto-purge only worked for successful runs. Regardless, I have some concerns that it seems you want to remove ...

I want the script for the second part. that is for this condition "If it is a successful job then the log must be fully cleared, If it is an aborted job, then the log must clear for just one day." Two points: 1. We'll be glad to help you write one, don't expect someone to just hand one to...

Wrap the abort function in an if-then-else.

Ok, which part do you need help with? For the first requirement, why not just let 'Auto Purge' handle that?

What have you tried, anything?

I'd also be curious if you need to abort when the first is detected or do you need to report them all and then abort?

I'm confused too. :? If you are trying to compare non-file sourced data with 'UNKNOWN' as the value to that same value sourced from a file where you've converted that to null, then they won't match. Don't set the null field value if you want to compare them. If you were asking something else, please...

srds2 wrote:With the above settings in the CFF stage I am not able to read the file.

Seems to me it would help if you explained what this means, what happens.