Shared Containers

throbinson · Post by **throbinson** » Fri Jan 24, 2003 3:06 pm

I work with ten DataStage Developers who are all in the initial stages of incorporating a shared container in numerous jobs. I'll be conservative and say we will have 30 jobs all with the same shared conatiner embedded within. We are doing this to leverage common code for our Enterprise Exception Processing architecture. Unfortunately, while in debug mode the shared container is held exclusively. This prevents anyone else from compiling or debugging their own code at the same time. Ridiculous! Completely unacceptable! Can I mark the shared container as read only or otherwise prevent it from being held exclusively? If so, how? Will marking the object as read only in the VOC have any effect?

pkm7581 · Post by **pkm7581** » Tue Jan 28, 2003 8:21 pm

Instead of making entries into the VOC file, try doing this to make your shared containers read only. Design info about the job objects in a container are stored in basically two tables (or Hashfiles): DS_CONTAINERS AND DS_JOBOBJECTS. You will need to find the appropriate CONTNO and udate the field READONLY.

Hope this helps,

Pavan

ray.wurlod · Post by **ray.wurlod** » Wed Jan 29, 2003 5:59 am

But surely that (making the shared container read only) will not prevent DataStage from taking an exclusive lock on it when a job that uses it is running (even if in Debugger)?
Something someone needs to investigate, methinks (and I'm too busy at the moment).

throbinson · Post by **throbinson** » Fri Feb 14, 2003 2:18 pm

Ascential has developed a patch. Any shared object will not be exclusively held unless explicitly opened.

datastage · Post by **datastage** » Tue Feb 18, 2003 3:18 pm

throbinson wrote:Ascential has developed a patch. Any shared object will not be exclusively held unless explicitly opened.

Could you update us as to what version of DataStage you ran into this issue with? Thanks.

ray.wurlod · Post by **ray.wurlod** » Wed Feb 19, 2003 4:38 am

Encountered it in release 5.1 and 5.2
Details of the patch and how to obtain it would be useful!

throbinson · Post by **throbinson** » Wed Feb 19, 2003 2:24 pm

My Homeys at Ascential set me up. You guys will have to chase it down from them. I did not see it on the support site. It is a client side fix involving the replacement of the file vmdsobj.dll. I'm still testing but so far the fix looks good.

DSXchange

Shared Containers

Shared Containers

Locked Shared Container