DSXchange

I seem to recall the DB2 stage wanting dates in internal format...

So... the same problem you've already posted here:

viewtopic.php?p=385020

That's a "best practice" for things like this - the stage variable does the evaluation of the expression once and then you leverage it multiple times. This also means there's only one place to change if the rules change, not "n" number of places... and maybe you miss one. :wink:

I'm unclear how you can be saying that you are using "%yyyy%mm%dd%hh%nn%ss" in your function call and yet the error message shows "%yyyy-%mm-%dd %hh:%nn:%ss"... can you double-check, please?

For goodness sake, people, use the dang Reply to topic button that is always just below the most recent post. There's absolutely no reason to 'Reply with quote' and thus quote everything every dang time you post. Please. This isn't email or a list server.

Check your link ordering, the Reject link must be after the main target link.

Where did "is Sunday" come from? You need to check for "= 0" as you posted earlier.

There's no "and" after the "then". Do the Sunday check in a stage variable and then check it in both field's derivations.

Yes.

Pass in the date and it will pass out the weekday number, 0 thru 6, where 0 = Sunday since sunday is the default 'origin day'. There is also a way to override the origin day if you want the week to start on a different day like Monday but I wouldn't worry about that in your case.

Only when there is a metadata mismatch between the viewing stage and the actual data. Any chance there's "something wrong" with the rows that don't show up when you compare the column definitions to the actual data?

Your syntax for the WeekdayFromDate function is incorrect. Recheck the documentation and adjust accordingly.

I don't believe that the CFF stage supports wildcards. Look into alternate mechanisms to determine and deliver the filename - a Sequence job that leverages a script and then passes in the current filename as a job parameter, perhaps. A Looping Sequence for multiple files. Etc.

Same way you would from the command line. What UNIX? Typically a semi-colon but sometime "&&" is preferred in case of errors.

It's important to understand here that those areas are only executed once, not per row - hence their name and the problem.