DSXchange

Lots of help out there from AIX folks when you google for "touch: 0652-046". Usually seems to be a corrupt filesystem but do the search yourself and run some of the tests they suggest.

Still... that's an "old school" template process you can follow when you don't have true templates. You have to remember to save a copy of the original under a new name and not accidentally modify or destroy the job that serves as the "template". In my mind, a true template would...

"Ruleset"? Where exactly are you doing this? Should this perhaps be over in the QualityStage forum?

Good to know. So, silly question perhaps but how does one determine if the "component ordering of the external date is the same as that of your locale"?

In. A. Reference. Lookup.

And you did not answer any of my questions, which makes it difficult for any continued help.

Perhaps IConv(YourDate,'DMDY[2,2,2]') for the internal conversion part?

Convert it into the format it is expecting.

You cannot if you want to leverage a bind parameter like that, I'm afraid. Where are you trying to do this, on the source or target side? What are you trying to bind into that :1 spot?

That would be correct. It may work (never tried) but you'd have no mechanism to capture the output.

That would need to be in a reference lookup for that parameter binding to have a chance to work correctly - are you?

Or let the stage generate the SQL. If your data types are correct in the job, it will automatically use a TO_DATE() in the generated sql.

So... in other words... the exact same problem you've already posted about. Why did you feel the need to start over again?

You can't, at least not there. You should be using the Stored Procedure stage for that.

Like normal - an Iconv/OConv pair (or substring / concatenation) to get it into a standard format and then a TO_DATE() with a matching format mask in your target SQL.

Ah, no worries... a resolved issue is a resolved issue.