DSXchange

Ok. Export / import should be fine as the import automatically deletes beforehand.

So... now it's resolved? What was the resolution?

Because RT_CONFIG113, the Config 'file' for job #113 is corrupt, missing or lacking permissions. Can you verify which?

There's no difference between Decimal and Numeric in DataStage Server. They're synonymous. So curious why the perceived need to convert?

How about some details about your job setup?

So, you have an after job routine that just sleeps?

Please post the job design, perhaps that will provide some clue.

There was no mention of 'unwanted' columns, they just needed to know how to read a fixed-width file. And to write it in csv format, you'd still need to read it first.

Assuming the 'no' is not AIX v. H-PUX but rather 7 v. 8, yes?

Ok, are we talking about the Monitor or job's Log here?

What was the resolution?

Your problem has nothing to do with the NullToZero transform, btw.

LINK 2 and LINK 1 are NOT completing simultaneously, LINK 2 will finish first so the hashed file is built for the main processing flow and only then will LINK 1 start. It may be fast enough that it appears to be simultaneous but it's not. As noted, you'll need to two jobs if you want to keep this i...

I'm no 8.x expert, but -

To prevent this error, try recreating this service with the -logRoot parameter. The value of the logRoot parameter should be the directory in which the server's .pid file is created.

Ernie, is the JavaPack one of the pieces you can get free now if you ask for it or do you still have to buy a ticket to ride that ride?

1. Wherever you tell it to look. Assuming a relative path, that would be controlled by your $PATH environment variable. In Windows it will look in your 'current working directory' first from what I recall, which for DataStage means the Project directory the job is running from, then check $PATH. It ...

And what did you find the difference to be? It should move it over untouched, unless perhaps it is getting truncated.

Still, the bottom line is it is unsupported in DataStage so your best answer may be to use a native tool to transport BLOB data.

You only lose functionality in an 'after job' subroutine if you don't code it in. So whatever you need it to log, code that in. If you need to abort the job, either log a fatal error or set the exit status to a non-zero value. If you need the routine to do multiple things, no reason you can't code m...