Dsx export discrepancies

psluser · Post by **psluser** » Fri Mar 20, 2009 12:49 pm

Hi,

We are facing some discrepancies in dsx export of same jobs exported from two similar projects. We develop jobs on one system, export it as dsx and import & execute them on another system. Datastage servers are different and located on different machines. DataStage Projects on these different servers were created with default settings.

When we export a job from second system and compare it with original dsx received from first one, we see a lot of differences without doing any changes to the job. A lot of properties are added to dsx when exported from the second project. for ex.

OrchestrateCode ""
NULLIndicatorValue ""
FromTemplate ""
DBMSSystemName ""
NLSMapName ""
...
CobolProgramName ""
CompileJCLName ""
RunJCLName ""
DBMSUserName ""
DBMSPassword ""
....
Condition ""
ParsedCondition ""
SourceColumns ""
RoutineTransforms ""

An original dsx of 1450 lines is inflated to 2400 lines with such properties when imported & exported from second project.

Please advice what can be the cause of the discrepancies since DataStage versions are same and Projects have defaulted properties.
Also, can these changes affect functionality in any possible way?

Thanks.

ray.wurlod · Post by **ray.wurlod** » Fri Mar 20, 2009 3:47 pm

What is the exact server version on each system (for example 7.5.1.r2d2)

psluser · Post by **psluser** » Fri Mar 20, 2009 4:10 pm

What is the exact server version on each system (for example 7.5.1.r2d2)

Both of the Servers are running DataStage 7.5.1.A

ArndW · Post by **ArndW** » Mon Mar 23, 2009 6:26 am

Did you install the same optional components on both systems? It looks like defaulted empty values are being added to one and not the other export files and it shouldn't make a difference in execution.

ray.wurlod · Post by **ray.wurlod** » Mon Mar 23, 2009 2:36 pm

I'm thinking along the same lines as Arnd - was one of the exports "include default values"?