Modify Stage specification Parameterization
Moderators: chulett, rschirm, roy
Modify Stage specification Parameterization
Hi All,
I had parmeterized the modify stage specification to make my multi-instance job generic and reusable.In one of the execution, the job does not require the paramater. In that case i didn't pass anything to job parameter,It aborts.Could any body help what to pass in specification parameter if there in no transformation required.
Thanks in advance
I had parmeterized the modify stage specification to make my multi-instance job generic and reusable.In one of the execution, the job does not require the paramater. In that case i didn't pass anything to job parameter,It aborts.Could any body help what to pass in specification parameter if there in no transformation required.
Thanks in advance
thanks n regards
nani
nani
Could you give an example of what the parameter looks like? Perhaps you might need to add a dummy modify stage action such as dropping a non-existant column.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Could you give an example of what the parameter looks like?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Try passing "drop nothing" as the parameter.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Usually if You drop a nonexisting column I would expect Datastage to throw a warning telling You that column "nothing" is not present in the input schema. To prevent this You will either have to demote this warning to informational (with the risk that you miss messages related to other columns), or add a Dummy-column to the stream that you can safely drop within the modify stage.ArndW wrote:Try passing "drop nothing" as the parameter.
A modify stage with an empty specification is invalid.
"It is not the lucky ones are grateful.
There are the grateful those are happy." Francis Bacon
There are the grateful those are happy." Francis Bacon
I suggested dropping a nonexistant column in the OP's modify stage as a route to solving the problem. As you noted, the warning message would need to be deprecated. But with that approach, the OP could have added a field that would get dropped in the modify, or done a "{col}={col}" where "col" is known column name that is always in the data. As you noted, the core of the problem was than an empty command is not allowed.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>