DSJob Import command fail for Shared container

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Munish
Participant
Posts: 89
Joined: Sun Nov 19, 2006 10:34 pm

DSJob Import command fail for Shared container

Post by Munish »

Hi All,
My project is in deployment stage (Version 7.5).
We have aroung 70 jobs,
of those 26 jobs are using 3 shared containers.

I have created .DSX files for individual job Executables (With Design Information, Without Refrenced Shared Container)
Separate DSX file for Sequencer

Another DSX for individual Shared Containers.

We are importing them in Unix Env through
Import DSJob command.

Everything imports fine except
SHARED CONTAINER,
with the error than mentioned job is missing.

When I try to import that DSX (Shared COntainer) through DS Manager, it imports fine.

Please advice,
1. Is there separate command (DSJob) for importing Shared COntainer.
2. Am I missing something.
3. I am importing them without any order,
Does that effect import in any way i.e. do I need to import Shared Container first and rest later.
4. We are doing bulk import, when I tried importing individual DSX (Shared container), Got the same error.

Any input would be highly appreciated.

Thanks and regards,
Munish
MK
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

It appears to be a deficiency in the dsjob -import command. Report it to your support provider. Meanwhile, use Manager to import your shared containers.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Munish
Participant
Posts: 89
Joined: Sun Nov 19, 2006 10:34 pm

Post by Munish »

Hi Ray,
It looks as if DSJob -import works only with compiled jobs.
Shared container were left out because they were not compiled

//***
Can Shared container be compiled, if yes how??
///***

We found the similar import problem when 1 job which was (which was not compiled) left outside out of 70 jobs (rest of them were compiled).

Any input would be appreciated.

Thanks and regards,
Munish
MK
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Shared container cannot be compiled. Only the job which uses the container can be compiled, and hence the Container code will be a part of jobs Compiled code.
May I know what is the version that you are using?
I tried with 7.5.1, it did got imported without any errors.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Munish
Participant
Posts: 89
Joined: Sun Nov 19, 2006 10:34 pm

Post by Munish »

We are using 7.5.2
Our plan is create independent DSX for individual job.
Thus we are creating DSX for job WITHOUT DEPENDENT SHARED CONTAINERS.
And want to create independent DSX for Shared Container.

Did you imported Shared Container along with the relevant job or of its own.

Thanks and regards,
Munish
MK
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Does it work with Manager or Multiclient manager.
My case was the Shared container alone.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Munish
Participant
Posts: 89
Joined: Sun Nov 19, 2006 10:34 pm

Post by Munish »

Yes, it does work with manager.
Is there any special flag with (DSJob -import) to work with Shared Containers???

Any input would be appreciated...

Thanks and regards,
Munish
MK
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

May be the version that you work has a bug in it. Better approach your Support.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Post Reply