Page 1 of 1

Row Generator generated OSH script bug

Posted: Wed Mar 07, 2007 4:31 pm
by pratapsriram
I have a sample job given by the IBM support to read a XML file using a ROW GENERATOR stage. This is the part of the OSH generated:
(
filename:string[]{cycle={value='[&filename]'}};
)


I have designed the same job by using the stages provided in my DS. This is the OSH generated:


(
filepath:string[];
)


filepath is the parameter in my job and filename is the parameter in the sample job.
Why does my generated OSH not be the same as the sample job? I have saved the sample job as a copy and then did the same and it works because of the Generated OSH matches the sample one.

Is this a bug in the DS-PX or do I need to apply a package to do this?

-MSP

Posted: Wed Mar 07, 2007 4:50 pm
by ray.wurlod
Welcome aboard. :D

Choose the filepath column in the Columns grid. Right click on this row in the grid and choose Edit Row from the menu.

In the properties window, please advise what you have under the Generator property.

Posted: Thu Mar 08, 2007 7:54 am
by pratapsriram
Yah I followed what Ray said above and it worked like a charm. Only regret is why dont IBM have good documentation for things such as these? Who would dream that a Row generator will have such functionality as a Folder stage? Well if thats what it takes then thats what it is...

-MSP

Posted: Thu Mar 08, 2007 8:32 am
by ray.wurlod
It IS quite well documented, in Chapter 53 (Row Generator stage) or Chapter 54 (Column Generator stage) in the Parallel Job Developer's Guide.

And you didn't follow what I said, which was "please advise". That way someone else, in future, will be able to solve this problem more quickly.

Posted: Thu Mar 08, 2007 10:10 am
by trobinson
I see nothing in Chapter 53 in the Parallel Job Developer's Guide that documents anything about generating filepaths. I also don't see a filepath column in the column grid of the output tab of the Row Generator stage. Ray - Can you elaborate?

Posted: Thu Mar 08, 2007 10:28 am
by ray.wurlod
The reference is to a job parameter.

And I goofed, it's "filename" not "filepath" in the OP. (I am using filepath in my work today.)