Importing a sequence and job drops parameters

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
PhilHibbs
Premium Member
Premium Member
Posts: 1044
Joined: Wed Sep 29, 2004 3:30 am
Location: Nottingham, UK
Contact:

Importing a sequence and job drops parameters

Post by PhilHibbs »

*Update*: I might be wrong about this. I'll do some more testing when I have time, a bit busy right now.

I think I've found a serious problem with DataStage, I've searched and can't find any other reference to it.

It occurs when you are importing a new version of a job and sequence into a project. If the job already exists, but the new version has a new parameter, and the sequence is imported first, then the new parameter is silently dropped from the sequence. The new job definition is then imported with the new parameter, but the sequence does not pass the parameter value any more.

One solution would be to import sequence jobs last, so that the new job definition is in place when the sequence is imported. I might amend my dsxsort utility to do this. Another solution would be to run the import twice.[/b]
Phil Hibbs | Capgemini
Technical Consultant
DS_SUPPORT
Premium Member
Premium Member
Posts: 232
Joined: Fri Aug 04, 2006 1:20 am
Location: Bangalore

Post by DS_SUPPORT »

I hope after importing, when you compile the jobs this issue wont occur.
Post Reply