Spurious Hash File Allocation message

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

Post Reply
flashgordon
Premium Member
Premium Member
Posts: 99
Joined: Tue Aug 17, 2004 7:50 am
Location: Boulder, Colorado

Spurious Hash File Allocation message

Post by flashgordon »

Hi,

We have "Create File" checked on a hash file and we are getting that spurious "Unable to create file /ibdd/..." message that is a know Datastage problem. We are running DS 7.5 and HP/UX 11.11. I re-run the job a few minutes later with no code changes and the job runs. We are running these sequences in tight succession, so the Create File is probably being encountered a few minutes after the hash file was read in a prior execution. Does anyone have a silver bullet for this spurious hash file allocation problem. We do have Create File and "Clear file before Writing" set on update action. Is that a no-no for some reason?

... Flash Gordon
Flash Gordon
Hyperborean Software Solution
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Flash,

are you intentionally deleting and re-creating the file on each job run? Unless you have specified this the job should never branch into the CREATE statement after the first job run. The CLEAR.FILE is no problem unless you have multiple processes running that read/write to this file; but even then you wouldn't be getting an abort, just unexplained data contents.

If you are intentionally deleting the hash file and creating it each run it might be worthwhile to rethink that approach as there is overhead involved with file creation and the delete does need exclusive access to the file.
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Your error appears to do with operating system permissions to create the hash file.

You may probably be using a script to move the hash-files around.

Also check whether you use any parameter(s) embedded in the hash-file names and ensure that the values are passed correctly.
Post Reply