Need help with hashfile

zulfi123786 · Post by **zulfi123786** » Sat Jan 30, 2010 5:23 am

Can any one help me in understanding the two options "Enabled, Lock for Updates" and "Disabled, Lock for Updates" as i did not find the description given in the guide to be friendly.

ArndW · Post by **ArndW** » Sat Jan 30, 2010 6:39 am

What is enabled or disabled? For those who aren't at a DataStage client to check, which button or box in which stage are you referring to?

chulett · Post by **chulett** » Sat Jan 30, 2010 7:27 am

Pre-load file to memory enabled or disabled, with the added bonus of the record being 'looked up' locked during the process... and the manual seems pretty detailed on how it works to me:

Pre-load file to memory. You can use these options to
improve performance if the output link is a reference input to
a Transformer stage. If you select Enabled, the hashed file is
read into memory when the job is run (Disabled is selected
by default). The remaining two options are for specialist use
and cater for situations where you need to modify a lookup
table as a job runs. If Enabled, Lock for Updates is selected
the hashed file is read into memory when the job is run. If a
lookup is not found in memory, the job looks in the file on
disk, if the lookup is still not found, an update lock is taken
in the knowledge that the record will subsequently be
written in the hashed file by this job. The operation for
Disabled, Lock for Updates is similar, except that the hashed
file is not read into memory.

Which part is... less than friendly?

ray.wurlod · Post by **ray.wurlod** » Sat Jan 30, 2010 2:55 pm

Moderator: please move to Server forum