DSXchange

A couple of possibilities: - Your userid doesn't have sufficient access rights to the file RT_STATUS164 (in your project directory) - The contents are larger than 2Gb (unlikely in a status file) - You have run out of space on the disk where the file is located - either during the run or on an earlie...

IsValid() and NUM()

You job is telling you that "'/work/data/ds_DATA.ds'" does not exist.

I guess you missed my earlier post, so I'll repeat myself:

It also seems as if you have hard-code paths to file objects in your job and haven't changed them for the new machine.

Not exactly what I was thinking, but not really wrong, either. First of all, if you have any 'unused' characters in the key or columns then remove them in order to reduce the file size. Delete any columns you aren't using in your lookup from the hashed file. The GENERAL and SEQ.NUM hashing algorithm...

Vinodanand wrote:...But teh last 6 digits of ID are always 0 out of (22)

If you strip this dummy data out of your key you would save 18Mb of key space alone.

Look at the rightmost characters of your key, would they be very similar on all keys or spread out - i.e. a sequential series of numbers would be well-spread out but if the last character is always 'X' or 'Y' that would not be well distributed. I've often found that using SEQ.NUM even on a string ke...

You only have a 55% load with a modulus of 678494; try using a MINIMUM.MODULUS of 284969. Also, what does your key look like? Are the rightmost couple of character/digits evenly spread? If so, you might try using the SEQ.NUM hashing algoritm.

It seems that you are using your hashed file with a path in your job, which is why there is no VOC entry. You will need to issue a
"SETFILE /dso/dsoweb/clients/jpmg/eligibility/logs/Hsh_PDSPersCovgPrevHist_coal_13058 TESTFILE" then do a "ANALYZE.FILE TESTFILE"

Each installation is somewhat different, so there is little to do until you encounter a specific error. The DataStage Install and Upgrade Guide chapter on configuring and installing Oracle is a good start (pp. 6-19 "Setting up Database connectivity" -> "Oracle Databases"

It also seems as if you have hard-code paths to file objects in your job and haven't changed them for the new machine.

how about

I'm not sure what you mean, could you post an example where you use the parameter in a transform?

Many implementations have the database server on a different machine than the DataStage server. Of course EE can access remote Oracle servers, this capability is necessary for distributed environments.

Don't enter the '{' and '}' characters. Every VOC has a 'ANALYZE.FILE' command, but I often mistype ANALZYE.FILE and get the same error you did. 64Bit files are going to be slower (and have more storage overhead) than the original files. Please do the ANALYZE.FILE Hsh_PDSPersCovgPrevHist_coal_13058 ...