DSXchange

32-bit addressable files have a 2.2 gigagbyte limit. DS Server by default uses 32-bit hash files. You can set DS to use 64-bit as the default, or, manually create hash files supplying the 64BIT keyword option. Search the forum, it's covered a lot.

Export the job and reimport. Somehow you corrupted the job status file.

chulett wrote:Your teapot seems to be running at a rolling boil today, Ken.

Yes, I'm on my annual fall diet and my tuna and rice lunch just doesn't compare to a chicken parmesan with fettucini alfredo and pasta fagioli lunch I like to enjoy.

chulett wrote:

kcbland wrote:Technically yes, but, how are you going to attach to both instances from your PC client?

That wasn't the question asked.

Okay, the question asked was akin to:

Can I put a screen door on a submarine?

And my reply was akin to:

Technically yes but you can't use it.

Have you configured the dsenv file?

Starting witn 7.x it is possible to run simultaneous server instances. You need to manipulate the "id" associated with them... whatever it is called. You know, the thing that defaults to "ade". That and the port for the dsrcpd daemon. Technically yes, but, how are you going to attach to both instan...

I'm talking about a DataStage Server job utilizing DataStage Server hash files. You are posting questions in the Server forum, so I'm giving you a Server solution.

If you want a Parallel solution, I'd tell you to a different solution.

No, you can't copy the file.

It is not possible for simultaneous server instances. You can toggle instances, which is difficult (to be kind) to manage.

You ran out of disk space, and yes the job fails to blow up. Just kill it.

It is not possible.

Doing it in DataStage is ugly, that's why I gave you an "elegant" SQL solution. Write source table "A" into a hash file, leaving the B phone number column blank. Read source table "B" and reference the hash file, if the row is there, add the B phone number to the B phone number column and write out ...

Your solution is not a loop, it is a UNION in your SQL. You need to collapse two rows into one. Imagine SQL like this: select key, max(bus_phone), max(home_phone) from ( select key, NULL "BUS_PHONE", home_phone from table A union all select key, bus_phone, NULL "HO...

Well, Google seems to be a good search tool

DSMigrate doesn't look like it has anything to do with DataStage

If you're on Solaris, use prstat -a and see if your job is using 100% of a cpu. If it is, then the only way to speed up that single job is to remove logic. Chances are if your job is seq-->xfm --> hash with a hash reference, your job is at 100% cpu speed unless you're disk thrashing. If you're not t...