DSXchange

I think File connector stage was introduced in 11.3.1 i.e. Fix pack 1 of 11.3. Check If you have fix pack 1 installed.


I will post the release notes link in a few for your reference.

Comp 3 is Packed Decimal. If you are getting anything other than decimal then I think there is something wrong with the cobol file definition. Or you may be getting multiple record types in the copy book. Double check if you have single or multiple record type/s in the copy book and if your file def...

That may sound slow but I have seen cases where development environment is very low spec and/or a lot of projects running on the same server ultilizing the same database and are very slow. Performance is not a criteria for test, just the correctness of data. Also the performance of the dev env shoul...

"DU 2015F21" does this value look like decimal. NO. So when converted to decimal default value is assigned.

If there is a conversion logic to convert this to a numeric value, you may want to implement the logic explicitly in the transformer stage and then map it to a decimal field.

yes Craig, last para is from Arch wiki. I generally put the excerpt and then link to it. But in this case I copied from the saved pages so didn't bother to find the link.

There isn't any criteria that throughput of 8-9 GB per hour is good or bad. It depends on the available resources and server configuration. To be content with performance you should review the design and option selected to make sure you are utilizing the resources well and not putting any un-necessa...

What are you trying to do, without the context and some details I don't think I can point you to correct reason for this failure.

GPG program throws an error even with 777. Change the owner of trustdb and the folder to dsadm and then reduce the permission to 700. If someone else can manipulate the key on the server then its identified as security issue by GPG and is not allowed. With 777 you are putting file security at risk. ...

I would suggest to use in-built convert function if it fits your requirements.

truncate is a ddl operation hence doesn't require much time to execute. why are you even worried about performance of truncate.

use Char instead of varchar and use same number of spaces as the field length to fill null (null field value) and explicitly define field delimiter as none.

not null to null? no function or transformation required. just map it to nullable column.

or if its null to not null, read Ray's reply.

Are you getting error or warning? whenever you are applying any function to the data.. the output can possibly be null.. (warning) in your case the timestamp format will take more than 20 bytes to store in text format and output not being able to fit in string(20), causing it to default the output m...

Hope this link helps.

and please delete other two posts with same question.

Moderator: done