DSXchange

Ok, I see what is meant by that. I'd be suprised if the SCD stage supports a mixture like that, however.

Are you sure you've got all of your terminology straight? I've never seen (and can't really imagine) a dimension with any kind of "mixture" of SCD types.

Once you posted after them, they couldn't delete anything... but I can.

If you look at the SQL posted, you can see they've done that - the 8 columns mentioned do not include the ID field, it is the 9th field. Hence my "don't see a problem" statement.

Any time you see a problem which only surfaces when running multiple jobs at a time but never does when they run one at a time, that screams "resource issue". I would take that error to your DBA and see what kind of limits your target Oracle instance and/or listener is configured with, sou...

You seem to be missing the big question here - how was the file "encrypted"? Without knowing that, you'll never get anywhere trying to "decrypt" it.

All I can say is it can take some time. I've also seen them stay forever and even survive a server reboot but that was on a Compaq Tru64 cluster. If they don't close on their own you'll need to recruit your SysAdmin to see if they can force them closed... I seem to recall a piece of freeware coming ...

D'oh! Forgot that it takes two arguments but a quick trip to the documentation shows them: DSLogFatal: Logs a fatal error message in a job's log file and terminates the job. Syntax Call DSLogFatal (Message, CallingProgName) Message (input) is the warning message you want to log. Message is automatic...

Immaculin wrote:data in the file: (has only 2 rows)

Server job.

For the 'from UNIX' question, you can't use datasets - you'll need to stick with sequential files if you want to take that route. As for the DataStage way, I'm sure there is but I'm out of time right now, really should be heading out the door.

They didn't and it's not.

Code not quote. Fixed.

These are all in the "online" help. From the Designer go to Help, then Index and then type DSGet and it will take you right there. It only takes one argument, the actual fatal (red) message to put in the log.

If nothing is happening then it's not being called. Post your code.

So... skip it.

Turn on the option to skip the header record, I'm assuming you don't actually need it.