Found this with a quick search, specifically wanted to point out this bit:
Note: If you encounter a problem when running a job which uses a server shared container in a parallel job, you could try increasing the value of the DSIPC_OPEN_TIMEOUT environment variable in the Parallel ► Operator specific category of the environment variable dialog box in the InfoSphere DataStage Administrator.
Worth a shot.
-craig
"You can never have too many knives" -- Logan Nine Fingers
sometimes during a migration things hiccup and it's sometimes best to simply make a new container from scratch. I would rename the existing container. Create a new container (not a copy of process), and drag new stages onto the canvas and repolulate with the desired logic. Recompile container, (force) recompile the calling job. test.
Additional Information:
I can use the Container with Server Jobs without any problems. So I dont think rebuild will fix the problem ... but i will try.
Have you involved your official support provider yet? And are you aware of the limitations on the use of Server Shared Containers in a Parallel job? Things like no MPP or Cluster systems? And I would put any thoughts of it working on a really old release and a different architecture out of your head while trying to get it to work on the latest release.
I'll have to defer to others here who may actually be using them but I have vague memories of another requirement of using them... the need for the Server "engine" to be installed on any node you run the PX job on? Or is that another false memory implanted by my therapist? Haven't had any luck searching so thought I would throw that out there.
-craig
"You can never have too many knives" -- Logan Nine Fingers