Hash File Lookup

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

branimir.kostic
Participant
Posts: 13
Joined: Thu Nov 04, 2004 4:30 am

Post by branimir.kostic »

Does this mean that if I set a pointer via SETFILE, DataStage is not able to delete the hashed file created in a directory?

How do you realize the import of Universe File Definitions if you specified it to a specific directory?

Because this was the reason of fooling in the database :wink:
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

If you use SETFILE, you're making the hashed file look like it was created in the account, by the fact that a VOC pointer exists. The fact that the hashed file is physically elsewhere is immaterial. Hashed files can always be deleted, but the correct method depends on how they were created.

Put another way, if a VOC pointer exists, it's as if the hashed file had been created with CREATE.FILE; without the VOC pointer the hashed file was created with mkdbfile. You can see the creation entry in the log.

Code: Select all

Created By      Deleted By
----------      ----------
CREATE.FILE     DELETE.FILE
mkdbfile        rm (UNIX) or DEL (Windows)
CREATE TABLE    DROP TABLE
Stage (in acc)  DELETE.FILE
Stage (in dir)  rm (UNIX) or DEL (Windows)
UV stage        DROP TABLE
With rm (UNIX) or DEL (Windows) you need to recursively delete for dynamic hashed files. For all hashed file type you also need to delete the dictionary portion (D_hashedfilename) if using rm/DEL.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply