0

I’m working with IBM InfoSphere DataStage 11.7.

I exported several jobs as XML files using istool export. Then, using a Python script, I modified the XML to add another database stage in parallel to an existing one (essentially duplicating and renaming a stage node).

After saving the modified XML, I ran istool import to re-import it back into the project. The import completed without any errors, but when I open the job in the Designer, the new stage doesn’t appear.

My questions are: 1.Is this some kind of access or permission restriction in DataStage? 2. Or does DataStage simply not support adding new stages by editing the XML directly? 3. Is there any supported or reliable programmatic method to add new stages (e.g., through DSX, API, or another approach)?

Any clarification on whether this kind of XML modification is supported (or an alternative way to automate stage creation) would be really helpful.

Improve this question

1 Answer 1

Reset to default
0

I have already answered on your nearly similar question from 12 hours ago. In theory it should work if the XML is correct (though I prefer DSX when doing so), but this is not a documented/supported way to do things, even though it is used to a certain extend by developers.

Besides that I can work, you should ask yourself if these 500 Jobs are very similar or not, if they actually do exactly the same , just for 500 different tables. Then you should rather have a single parameterized job that uses RCP, then you would need to only to add the stage to one job instead of 500.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.