A problem with Shared Containers
Posted: Mon Apr 18, 2005 2:59 pm
Hello Friends........
In our project....we have a couple of shared containers used as reference for different jobs...When we want to use a shared container we directly get a copy of it and insert in the job as usual... The jobs were working very well....
Recently..a problem started....Whenever someone is accessing a shared container..if any other person wants to access the same shared container...the job in which the shared container is used doesnt compile and shows an error in the shared container.....
The problem in detail............
Suppose the shared container used is SC1
If a DS programmer accesses SC1 in his job j1.....
IF another DS prgrammer designs a job j2 which has SC1 inserted in his job...at the same time
Now when they try to compile their jobs they cant....
BUT if they try compiling their jobs when no one else is accessing the shared container SC1 there are fine with the job....the job runs succesfully and no problems....
What might be the problem...In both the jobs the shared containers are used as lookups...Here the concept of shared container is not ompletely utilised...it is accessible but when it comes to compiling or running the job it is a problem.........
Are there any special instructions to follow before desiging a shared container....
Pls advise....
In our project....we have a couple of shared containers used as reference for different jobs...When we want to use a shared container we directly get a copy of it and insert in the job as usual... The jobs were working very well....
Recently..a problem started....Whenever someone is accessing a shared container..if any other person wants to access the same shared container...the job in which the shared container is used doesnt compile and shows an error in the shared container.....
The problem in detail............
Suppose the shared container used is SC1
If a DS programmer accesses SC1 in his job j1.....
IF another DS prgrammer designs a job j2 which has SC1 inserted in his job...at the same time
Now when they try to compile their jobs they cant....
BUT if they try compiling their jobs when no one else is accessing the shared container SC1 there are fine with the job....the job runs succesfully and no problems....
What might be the problem...In both the jobs the shared containers are used as lookups...Here the concept of shared container is not ompletely utilised...it is accessible but when it comes to compiling or running the job it is a problem.........
Are there any special instructions to follow before desiging a shared container....
Pls advise....