DSXchange

Figured that would be the answer... or at least an answer to your resource issue.

That's a Java error and perhaps a bug, probably best to involve your official support provider.

While Informatica has a "number of records to skip" for flat files, I don't recall DataStage having anything other than the "First line is column headers" true/false option. Perhaps a question for your official support provider?

In your shoes I would be opening a support case while waiting for additional input from the community...

Open a support case.

From what I recall, you would need to define them as string fields in the flat file and then format them accordingly.

Sure but it's messy and painful... which is the whole reason that the DSODB was added to the product. You can leverage the API for this, either from BASIC routines or from the command line depending on where your skillset lies, equivalent functions exist in both. For BASIC routines, search the docum...

I haven't been through all of the documentation (thanks Paul) but perhaps something here might help.

It's got to be BYTE semantics or it would be working now, I'd wager.

That's what happens with you try to negotiate with a machine.

Have you tried... specifying "ustring" in the schema file? I'm sure there's more to it than that, but that's the first thing that comes to mind.

That seems oddly... restrictive... to me.

Let's see what others have to say.

It is a bit odd but it has been with us since the beginning... since you're suddenly at a different domain and not logged in there, it blocks all premium content. I've been fixing them since I was granted the power to do so, never really thought to announce the issue until it came up here.

Not that I am aware of, each is treated as a separate 'table' in essence from what I recall.

You can't do anything with the "previous" records unless we're talking a database as the target. I'm assuming we're talking about files here so the suggestion is to sort the data descending... i.e. process them in the opposite order posted so that the date in the current record can be used...