Hased file reading from different jobs

snassimr · Post by **snassimr** » Fri Sep 16, 2005 5:06 pm

Hi !

I use JOB SEQUENCE design where I rn three jobs in parallel and all three jobs read from the same hash file .

I wonder if its ok and it not corrupt data ? How to improve perfomance of reading . Whats the sharing options ?

chulett · Post by **chulett** » Fri Sep 16, 2005 5:35 pm

Yes, it works just fine and nothing about reading it with multiple jobs simultaneously will corrupt it.

For required reading on the subject of Hash Stage Disk Caching check out the dsdskche.pdf document of the same name included in your 'Docs' directory. This includes the option of sharing hashed files at the system level.

snassimr · Post by **snassimr** » Fri Sep 16, 2005 6:36 pm

What the advantages of setting Hash Stage Disk Caching in System Level ? Its written that the default value is READ.WRITE option ? Is there is better option for Reading from hashed file ?

chulett · Post by **chulett** » Fri Sep 16, 2005 8:22 pm

The advantage is the fact that one copy of the hashed file would be shared by your three jobs, rather than having three identical copies of the hashed file in memory.

snassimr · Post by **snassimr** » Sat Sep 17, 2005 4:05 am

I dont understand what I need exactly to do to set sharing in system level.

Its written in that Hash Stage Disk Caching that the default value is READ.WRITE option.

What , to run the set command one more time ?

chulett · Post by **chulett** » Sat Sep 17, 2005 9:22 am

snassimr wrote:I dont understand what I need exactly to do to set sharing in system level.

I know.

I almost didn't reply to this originally because I didn't want to get sucked into an endless thread of questions, something I really don't have the time or energy to handle right now.

This is an advanced subject, a path not to be taken lightly - and not really suited for casual discussion on a weboard. There are plenty of cons as well as pros and the distinct possibililty exists of horked things up badly. IMHO you need someone familiar with the process there onsite with you to handle this properly.

If you are feeling adventurous, read the pdf (again) and test out making changes to a test server installation, one you can afford to lose. Work out the kinks there. Or - better yet - note down the fact that you can do this and save the actual implementation for another day. I've got upwards of 1500 jobs running nightly across various projects and don't have this option enabled. I would guess most installations out there don't as well.

Unless there is a more adventurous soul in the audience willing to take this on?