Needing to create a generic datastage job that can dynamically source from and load to a number of columns based on a set of job parameters.
Is there a way to specify which columns to import (and how many) based on job parameters?
e.g. of different source tables:
ID, Ts, Te, Firstname, Surname
ID, Ts, Te, Street, Suburb, Country
I've read a little about schema's to dynamically specify input... maybe?
Selecting columns using job parameters
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard. :D
Basically the answer is no. DataStage is metadata driven; the metadata (column definitions) need to be in place before the job is compiled.
Some people have implemented strategies to get around this, which you can read about by searching the forum. But there is nothing "out of the box" that can do what you ask.
Basically the answer is no. DataStage is metadata driven; the metadata (column definitions) need to be in place before the job is compiled.
Some people have implemented strategies to get around this, which you can read about by searching the forum. But there is nothing "out of the box" that can do what you ask.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.