DSXchange

pkll wrote:I need to use checksum stage only.

And why, pray tell, is that?

Not much to go on. All one can tell from that is it is coming from the MKS Toolkit on a Windows server. How about some details around your job design?

I'm curious how you determined that was the reason for the 'hang'? That just seems... odd. What is your target? If it is a database, have you had your DBA monitor it?

It's not an error, you can certainly design jobs that way if you like. I just would not consider it any kind of a 'Best Practice'. And no, there's no equivalent of Informatica's Target Load Plan in DataStage. If you want the "second job" to wait for the "first job" to complete be...

They will run simultaneously... and is generally NOT a good idea. Create them as individual jobs so you have full control over the order of execution. And atomic restartability.

I believe that in the Sequential file, you can set the individual field properties for those COMP fields to "Packed" and have it unpack them for you. Don't recall if it will handle any EBCDIC translation for string fields as well, however. As noted, the whole point of the CFF stage is to h...

Only if they moved it. Introduced in 8.1 in the DSParams file.

Probably so. Still, helpful for everyone else on the board.

Or select it with the proper scale and then use DecimalToDecimal() within the job to truncate it during the conversion to the lower scale.

You also have this option which will handle any month ending day 'overruns' automatically. I'll wager any functions that add months will do the same.

:idea: If you test a string for validity FIRST and then convert only valid values, you would not receive warnings like that... which is the whole point of testing validity first. srini.dw: did you get this working for you? Remove the StringToTimestamp from your code and for the "then" do w...

ssnegi wrote:We would have to convert to timestamp before checking for validity of timestamp.

Sorry but this is not correct.

As noted, you should be checking for validity BEFORE doing any conversion, the goal being to ensure that the conversion will work properly. The IsValid() function expects a string as its input so that isn't really working like you think it is.

Bascially correct, they control if the log entries go to the associated repository or not. Technically, both could be set to True and the logs could be going to both locations. I'm surprised that neither is present in your DSParams file, I wonder if the 'default' is true if the environment variable ...

Or transformer looping if you have 8.5 or higher.