DSXchange

Hi,

New project deploy to production environnement and while running sanity tests; the jobs using the Assembly Editor of the Hierarchical stage are failing with the following message in Director :

Operator initialization: Input port 0 already connected; text:

Hierarchical_Data_Tax: Operator initialization: Input port 0 already connected; text:
0< [] 'External_Source_Tax:in_HD.v'

Hierarchical_Data_AJSTPRBR: Operator initialization: Input port 0 already connected; text:
0< [] 'External_Source_ajustementpourboire:in_HD.v'

etc...

These jobs are having the same design topologie and have been working fine in our dev environment for months.

External Source -> Hierachical Data -> Dataset

We are using the Assembly Editor to read an xml file supplied as input to the External Source stage. The error seems to occur when it try to get to the second stage. We did a job copy and removed the Hierachical Data stage and it with no error.

If we rebuild the same job under another name from scratch in prod; it does run fine. We did a dsx export of the new job created in prod and imported it into our dev environnement where it ran fine. We then generate a dsx file to reimport in the prod environement and it ran fine this time.

No differences in the dsx files between prod and dev.

Th original deployment to prod was made using a package and we recompile everyhting in prod.

Anybody did experiment such behavior?

Thanks

Hi,

Problem seems to be related in using the hierachical data stage with a job using a parameter set value that has a single quote in it.

Running the same job with the same parameter set value without the hierarchical data stage is running fine with no error. Issue reported to IBM.

IBM replied that by design the parameter set content is exposed to the hierachical data stage. That is, even if the hierarchical stage does not make
use of the parameter set value. Therefore, if a param set value has a special xml-json character in it, it has to be escaped otherwise and error will occur at run time.

Since the DS jobs that make uses of the values with special characters are not using the hierachical stage, we resolved our problem by simply adding a new parameter set where we isolate the values with special characters.