What does a generic job exactly means?

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
karthikgk0705
Premium Member
Premium Member
Posts: 45
Joined: Tue Aug 29, 2006 2:59 am
Location: Bangalore

What does a generic job exactly means?

Post by karthikgk0705 »

Hi,
I have recently joined a new project.
As per our Design, all our jobs are generic jobs.
What does exactly generic jobs mean by? How are they different from normal DS jobs? We are using parallel jobs.
Also our input is the sequential file and we are specifying the schema file instead of loading the metadata.
As far as I know, specifying schema file over rides the properties of Format tab and Columns tab.
But in our jobs, we do load Format.
Why is that it is done?
Thanks in Advance.
karthik.
gateleys
Premium Member
Premium Member
Posts: 992
Joined: Mon Aug 08, 2005 5:08 pm
Location: USA

Re: What does a generic job exactly means?

Post by gateleys »

It seems that you are developing kind of templates that will be filled with details later. 'Generic' means general, not specific. So, your jobs are not for any specific task, but can be moulded into one if the detail specs are provided. For example, templates to handle SCDs, loads, etc.
gateleys
gateleys
Premium Member
Premium Member
Posts: 992
Joined: Mon Aug 08, 2005 5:08 pm
Location: USA

Re: What does a generic job exactly means?

Post by gateleys »

But its a simple question that your manager should be able to answer.
gateleys
karthikgk0705
Premium Member
Premium Member
Posts: 45
Joined: Tue Aug 29, 2006 2:59 am
Location: Bangalore

Post by karthikgk0705 »

:lol: :lol: :lol:

You people are much more friendlier than my manager....
gateleys
Premium Member
Premium Member
Posts: 992
Joined: Mon Aug 08, 2005 5:08 pm
Location: USA

Post by gateleys »

karthikgk0705 wrote::lol: :lol: :lol:

You people are much more friendlier than my manager....
I hope your manager ( :evil: ) is not reading this post of yours.


BTW, did my earlier reponse address your query?
gateleys
karthikgk0705
Premium Member
Premium Member
Posts: 45
Joined: Tue Aug 29, 2006 2:59 am
Location: Bangalore

Post by karthikgk0705 »

Yeah..sort of...
We are doing SCD changes in our jobs.
But does that means that we have to use generic jobs? Cant it be done using Normal jobs?
Also , u didnt answer for the 2nd part of my question.
VCInDSX
Premium Member
Premium Member
Posts: 223
Joined: Fri Apr 13, 2007 10:02 am
Location: US

Post by VCInDSX »

From your description, i believe your "Original Designers" wanted to have one-job-does-all solution.
If you do a search on Runtime column propagation you will find a wealth of threads on this topic. I have pulled a few from my notes (when i was looking for similar information a few weeks ago...)
viewtopic.php?t=107818
viewtopic.php?t=110354
viewtopic.php?t=110304
viewtopic.php?t=109700

You should be able to understand pros and cons of using RCP from these discussions as well.

Good luck,
-V
gateleys
Premium Member
Premium Member
Posts: 992
Joined: Mon Aug 08, 2005 5:08 pm
Location: USA

Post by gateleys »

I think VCInDSX answered your question accurately. It seems your ETL is architected to use Runtime Column Propagation. Now since you have mentioned that you are using sequential files as input, you have been asked to use schema file so that the intermediate stages will have the metadata propagated to them during runtime.
gateleys
Post Reply