DSXchange

It's not easy to read that type of data in PX (or in Server). Make the data as flat as you can and preferrably fixed width prior to importing into PX. Then, tag each incoming row with an indicaor that specifies the format of each row, and use corresponding schemas to parse the row.

- BP

ld.so.1: dscs: fatal: libUtilWSClient.so: open failed: No such file or directory I think the above line is your main problem. If this is a DataStage library, then you might need to reinstall DataStage. The library might have been corrupted during the install, or perhaps on the install disk. If it is...

How did you create the dataset? Is it created by an upstream PX job? There is a utility called orchadmin that can be called thru the UNIX command line. You can use it to check the status of a .ds file. It has been described in other posts. If orchadmin has trouble with the .ds, then the problem isn'...

I don't know much about the PX CDC stage, but isn't this what it's supposed to do? It sounds like he's trying to implement a slowly changing dimension, right? PX can be used to do large lookups if the lookup table on the database is partitioned. PX can instantiate a separate reader per partition. -BP

PX is not freely-typed b/c it doesn't operate on DS's Basic engine. It uses a separate c-based engine.

I don't know the answer to the original question, but if someone has the APT_Ref cards, could they be kind enough to see if there is a str_to_num function for the APT_String class?

Thanks,
BP

It seems like you have a link-loader problem. Using the environment vars you set for the bin and lib within PX, you should be able to compile a simple c program outside PX. If that doesn't work, then you have set up your env improperly within PX.

-BP

You are gauranteed uniqueness if you use the technique above for generating a surrogate key. You are not gauranteed that there will be no blanks, which is not a problem - as Ken points out - if you don't assign other meaning to the surrogate key besides uniqueness.

- BP

I believe that there are some sample 'osh' scripts that come with PX. You could run them to make sure that the PX server is set up correctly. Also, always test a simple buildop with PX to make sure that your C compiler is compatible with your PX env.

-BP

Try running with a one node config. If that works, then the problem is with the partitioning.

Are the partition methods for both data sets set to 'clear'?

- BP

You could be running out of disk space or memory. To check disk space, do a ds -k . in the directory that holds PX temp and permanent files. To check memory, run top while PX is running and make sure you have ample swap space.

- BP

Does that file exist? If not, you may need to recreate the dataset it is trying to access.

-BP

Do you have the administrator's manual for PX? Setting up DB2 for PX is different than setting up DB2 for DataStage Server. After reviewing the manual, please write back.

- BP

You just need a transform and another filter/transform.. First hash and sort by the dup keys. Then use one transform to assign a sequential # to each record in a dup group. Then in the second transform/filter, use the sequential # as a constraint/filter: if the # = 1, then that's the record to retai...

If you look through the director log for that job, you should be able to find a reference to the right directory.

-BP

It should be in the RT_BP(??) directory that is created on the server for that particular job.
-BP