DSXchange

Check out the FMT command. It can justify and zero fill to a specific number of digits in a derivation.

ps. The '#' symbol means 'not equal'.

Have you tried reinstalling the client?

IMHO, the best way to solve this problem is to stop using it.

Or perhaps a stage still named 'AfterJob'... that's why I asked.

Most times it doesn't really help to just say something "is not working", best to explain how something is it or is not working. In this case, though, suggest you read up on how the checkpoint restart works. I'm not on 7.5 yet, but from what I recall you'll need to remove the failure triggers from t...

I suspect so, too.

Did you go through the configuration steps required for the Oracle plug-ins, specifically the changes needed in the dsenv file? Do you have an Oracle client installed on this new server?

Those fields that contain the delimiter, are they quoted? They should be and if they aren't you should complain to whomever built it for you as that's not a valid text file. Have them fix it.

That would be one way to handle this.

Ross, curious... have you actually tried that and had it work? I assumed it would way back when, but was unable to actually make it work in my 7.0.1 version. Had to fall back to the 'cat them all together before job' approach.

I was wondering If I can read more than one file using seq file stage in a single datastage job.I don't want to use folder stage or don't want to merge the files before reading them using cat commands etc... Well, you've eliminated the two most common ways of doing that. As, as you've surmised, wil...

Are you using User Defined SQL in your source stage? This is typically where this error can occur as you may not have ever gotten anything into the 'Table Name' field in the stage. It is required by the stage even though it is not used by your User Defined SQL. One way to fix it is to switch to Colu...

Search the forum for tons of comments on handling Oracle DATE fields in DataStage. My personal standard is to always declare them as a Timestamp data type. DataStage will always deliver them in a fixed format and expect them in that same fixed format, one that will work regardless of the NLS_DATE fo...

I've also seen files in there that seem to have been used by IPC stages. Plus I always redirect the temporary files used by the Sort stage into /tmp rather than let them default into and build up in the Project directory.

My output file name was defined as uv/Projects/workfiles/x*.txt The file was populated correctly. It's not about it being 'populated' correctly, it's about the notion of using 'wildcards' in an output filename. Are you expecting it to literally create a two character filename - an 'x' followed by a...

Seconded... had no clue you can do that.

kaps wrote:does the wildcards allowed in the file name ?

Nope, not allowed in Input nor Output filenames. Not really sure how you would think that would even work on output...