Hi,
I want to run a PX job for a specified number rows.
But, in Job Run Options --->Limits Tab --->Rows -----> both the radio buttons No Limit and Stop Stages after Rows options were disabled.
Could anyone tell a way to do it.
Running PX jobs for a limited number of rows
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 123
- Joined: Wed May 18, 2005 7:41 am
- Location: USA
Running PX jobs for a limited number of rows
Regards
VS
VS
-
- Participant
- Posts: 123
- Joined: Wed May 18, 2005 7:41 am
- Location: USA
Hi,
I don't exactly understand your reason for wanting this but it depends on what is your source, here are 2 examples:
1. A sequential file has a "read first rows" option for reading n number of rows (you can use a parameter as value)
2. An Oracle stage can use a where part constraining n rows (also use the $DB_ENABLE_RESERVED_CHAR_CONVERT to allow parameters in the where part to be translated by DS); I think you can't get a specific n rows returned this way since it might not be the same n rows each time.
IHTH,
I don't exactly understand your reason for wanting this but it depends on what is your source, here are 2 examples:
1. A sequential file has a "read first rows" option for reading n number of rows (you can use a parameter as value)
2. An Oracle stage can use a where part constraining n rows (also use the $DB_ENABLE_RESERVED_CHAR_CONVERT to allow parameters in the where part to be translated by DS); I think you can't get a specific n rows returned this way since it might not be the same n rows each time.
IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
This option is enabled in server jobs, but not in PX.
Also you can do a work around as Roy said, but this would only put a limit on the input rows and not on output rows. For Ex your job may be limited to read only 1000 rows and process them, but your output may still have just 10 rows, or 2000 rows.
Also you can do a work around as Roy said, but this would only put a limit on the input rows and not on output rows. For Ex your job may be limited to read only 1000 rows and process them, but your output may still have just 10 rows, or 2000 rows.