Discrepancy in dsx files

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
patonp
Premium Member
Premium Member
Posts: 110
Joined: Thu Mar 11, 2004 7:59 am
Location: Toronto, ON

Discrepancy in dsx files

Post by patonp »

I've taken a dsx export of a category from our development server. Later, the admin promoted this same category to production and created a dsx export of the category from the production server.

Oddly, the two dsx files are significantly out of sync. Attributes that appear in the production dsx export do not appear in the development dsx. However, when I import the production dsx file into a test environment, the jobs in designer appear to match those in development.

Any idea what's going on here?
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Whats different? The system name might be different, along with some other environment variables. But the crux should be the same.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
patonp
Premium Member
Premium Member
Posts: 110
Joined: Thu Mar 11, 2004 7:59 am
Location: Toronto, ON

Post by patonp »

The differences appear to relate to additional attributes appearing within the data. For example, one subrecord that applies to an element of a transformer has 26 associated attributes defined in the development dsx, but 54 in the production dsx.
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

You sure your not appending to a file while doing exports. Either you or your production guy.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
patonp
Premium Member
Premium Member
Posts: 110
Joined: Thu Mar 11, 2004 7:59 am
Location: Toronto, ON

Post by patonp »

No appending is occurring. The problem is not that there are additional objects or jobs within the export. Instead, additional attributes are found within the subrecords of the objects.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Please post some specific examples so we can understand what you are seeing.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Is the development system on the same version as the production system? Exactly?

Were the Options settings in the Export dialog identical in both cases? For example, did the production export include defaulted properties and the development export not include them?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply