DSXchange

I didn't know that these were either documented or listed anywhere, they are part of the GCI. Where did you find references to these mnemonic codes?

I'm pretty sure that PX datasets and filesets avoid any 2Gb limit your filesystem might have by adding partfiles; but I'm not absolutely certain. If you can create files larger than 2Gb in your OS then there is no effective limit other than disk space.

The orphaned dataset data files have no link back to their "descriptor" so you will need to manually delete them. I wrote a program to search the machine for all descriptor files and link them to the corresponding data files, then any files that aren't linked in the data directory are junk files and...

Aakash - the INDEX function syntax is the same in PX, so it will work on both types of jobs.

You need to convert your CHAR column to VARCHAR and use TRIM. Then the extra space(s) won't bother the conversion to decimal.

Does the error go away when you set the array size to 1 and the commit frequency higher?

The DSN needs to be defined on the DataStage server, not your client. The Excel file also needs to be read from server as that is where the DataStage job is actually running.

data does not always equate to tables. Try a simple 1-worksheet file with 2 columns (with headers) - does that work? If so, then what is your data format in your non-working excel sheet?

Did you declare it as a system DSN? I usually double-check ODBC connectivity using the (free) tool MS QUERY; try seeing if that works.

I've used this in the past; no problems with concurrent reads on DataSets or LookupFileSets.

DataSets can be read from simultaneously by different processes, but cannot be written to and read from at the same time.

Look at them as glorified sequential files when it comes to concurrency control.

Introducing a modify stage isn't enough, you need to add a handler for null as the in the stage as message suggested. Look at page 28-4 of the Parallel Job Developer's Guide

Caltog - good news

Ray - I guess Caltog's response answered my previous post's question

You should activate your APT_DUMP_SCORE variable in order to see how many pids are actually started. This will depend on your APT_CONFIG node configuration as well as whether or not your database is partitioned and you use that functionality. Increasing/decreasing the number of nodes in your configu...

It is a DataStage BASIC header include file; I've never heard the term "library file" used for this. Just keep in mind that this is a user-written header, not one supplied as part of the package.