DSXchange

Well... 'in the knowledge that' means 'knowing that' or possibly 'assuming that', if that's what you are asking. This option should be used when a job needs *all* lookups to exist and the job will enforce that by writing any data that fails the lookup back into the hash file so that subsequent iterations of that data will not fail. I really don't think the process will be slowed down, but I would only use this option when a job needs this functionality and is designed to write missing data back into the lookup hash. If you don't take the 'lock' option, I believe that any changes to the hash file will not be seen by the job until the *next* time that it runs. Hope this helps.

-craig