DSXchange

Create the file with DOS record delimiters, Windows needs a CR/LF pair rather than just the LF that UNIX uses.

So... why is it all spaces? What was the "default value" you used for null dates when you loaded the table?

Your 'otherwise' trigger needs to go to a Terminator stage. Either that or remove it and allow the 'Automatically handle' compiler option to take care of things for you.

Hmmm... there's a wee bit of difference between 'want' and 'have'. Which is it?

Post the actual SQL you are attempting to use, where clause and all.

Not really. If those components can come in with one or two digits, you need to check each one and add the zeroes yourself.

Of course, the easiest way to fix this is to get the producer of this data to standardize it for you so you don't have to futz with it.

Harini wrote:Still, the data is getting loaded with the zeros in the database.

No, it's not.

As noted, that is an external representation of the internal value and the viewer is "adding" the zeroes. Trimming the zeroes is a waste of time.

There are "DSGetLog" API functions to retrieve log information from a routine, or equivalent dsjob options can be used to the same purpose from the command line in a script.

How do you expect the tr command to know which file to process? You have to tell it - it is not picked up from the filename property in the stage. Actually, it is. :? While you can certainly specify it in the filter itself (and sometimes need to depending on the specific syntax) it will combine you...

FORM5500 would be the Project, I assume, and %1 is a bind variable for the job name, which is passed in at invocation.

If your target won't accept nulls, then you'll need to provide an 'in-band' value for those empty timestamps, something that equates to no date. I've seen either low or high values, like 01/01/1900 or 12/31/9999 used, amongst other values. Plus a time, of course.

Suggest you stick with the original post you created for this problem rather than starting the conversation all over again:

viewtopic.php?p=382124

Locking this version as well, here is a link to the original topic, if people want to help please do so there.

Posting the same questions multiple times just upsets the natives, please refrain from doing so in the future.

Locking this. Please use the original post to continue the conversation.

No. Perhaps the Pro/Ultimate version running in 'XP Mode' but not natively.