DSXchange

Obviously should be something that works just fine, probably just some silly thing you are missing. Did you involve your official support provider? I'm sure they would love to get it straighten out for you.

That mirrors my experience.

Well... if one of your fields in the target file needs a timestamp in a "different" format, AFAIK you'll need to define it as a string and build it out in that format. You may have a way to override the format as an advanced property of the field itself, others would have to confirm / deny...

Yes but isn't there some sort of a magic (maybe 4 byte) header on UTF-8 files? I recently had an issue where a particular set of files would come in either format and my tool when set to UTF-8 could read either without issue but when set to US-ASCII would barf on a UTF-8 file, adding some "garb...

How about in a hex dump format? od -h should shed more light on this, I would think.

There is no "expected format"... a timestamp is a timestamp and only has an external format when you put it into a string. That's why the StringToTimestamp function wants to know what the string looks like but doesn't ask you what you want the timestamp to look like. Does that make sense? ...

Craig, actually... not Chuck. :wink: I'm wondering what character encoding the file is being created with and if, perhaps, you've gone from single-byte to a multi-byte one. ISO 8859-1 is 8-bit single-byte coded graphic character set so guessing that's not the issue. Have you compared the two files, ...

Without looking at the code itself, the first thing that comes to mind when someone says "the output file size is getting increased by 2.5 times" that there is a codepage / characterset issue. Can you confirm / deny that?

I would check with your DBA to make sure your executing user has the correct grants to call that package. And that the syntax is correct, I believe you need to supply a "METHOD" and you may want to use TRUE rather than true, depending on settings in the database. AFAIK, you can't call an a...

I've never seen a use for it, being (IIRC) principally designed as a marketing counter for the same ability in <cough> some other tool. The "dynamic" part would allow you to switch databases under the covers without much work in the jobs themselves other than to change the setting that con...

COBOL PICTURE clauses aren't all that mysterious but you should probably ask for sample / test data to be delivered since it will typically come in EBCDIC rather than ASCII so not all that simple to generate. However, with nothing packed / comp you could get away with straight-up ASCII samples for ...

Okay... still just guessing from reading the docs but perhaps you can use whatever process "defines" the package to add more components to it? You must first define the package in the InfoSphere Information Server Manager, including specifying the assets that it contains and the build and ...

Look to me like you would use the -updatearchive or -up option.

It's a native Oracle stage rather than a "Dynamic" one that could be set to Oracle. Now, I don't know how the DRS works under the covers so it may very well work exactly the same as the Oracle Connector when set to Oracle.

Anyone know?

Just a guess but try supplying an actual directory for the 'Temporary Directory', one it could use as scratch space.