Recently I have been developing a parallel job to populate a time dimension. The time dimension has the usual columns such Date, Year, Quarter, Month name, Month days remaining, weekday number, weekday name, Year days remaining, week no etc
I was using the BASIC Transformer to obtain all the above. (ICONV, OCONV,Week.tag, Year.last etc)
But it seems that the BASIC transformer will be unable to work on the parallel grid we are using.
So my question is, are the date functions available in parallel jobs sufficient enough to obtain all the above columns. I looked through the PX documentation, the date functions specified therein seem to return numbers as output and do not seem to be very broad relative to the OCONV options.
I guess there is always the option of generating all this with SQL and loading it to the table, but for some reason they want it run thru a parallel job/transformer stage.
Any other suggestions ?
Date options is Parallel transformer
Moderators: chulett, rschirm, roy
Date options is Parallel transformer
Last edited by gsym on Tue Feb 20, 2007 7:16 pm, edited 1 time in total.
StringFromDate pops into my head as something similar. And there are several posts on PX date handling, this is one that I have 'bookmarked'.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Re: Date options is Parallel transformer
Who said?gsym wrote:But it seems that the BASIC transformer will be unable to work on the parallel grid we are using.
Of course it can - you just need to make sure it runs on a node where the DataStage run machine is installed. You can use a node pool or a one-node configuration file.
Why?gsym wrote:for some reason they want it run thru a parallel job/transformer stage
If you already have a solution, why re-invent the wheel?
It probably CAN be done with parallel functions, but why would you bother? How many rows in your time dimension? A couple of thousand? I'd advocate using a server job.
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.
Re: Date options is Parallel transformer
ray.wurlod wrote:Who said?gsym wrote:But it seems that the BASIC transformer will be unable to work on the parallel grid we are using.
Of course it can - you just need to make sure it runs on a node where the DataStage run machine is installed. You can use a node pool or a one-node configuration file.
Why?gsym wrote:for some reason they want it run thru a parallel job/transformer stage
If you already have a solution, why re-invent the wheel?
It probably CAN be done with parallel functions, but why would you bother? How many rows in your time dimension? A couple of thousand? I'd advocate using a server job.
The grid is so designed that no BASIC functions will work on it. It has its own scheduling/sequencing engine. And even if it could run, they are not willing to change that.
Server jobs are out too.
So, was wondering if ppl here can point me to some relevant parallel functions that can assist in obtaining the above mentioned column values...
At the least, it will be a good exercise in using parallel date functions (trying to be an optimist here :D)
Am at present looking at the date functions in the Modify stage.
Simple question - how do I obtain the names of months and weeks i.e., what format will get me this either in the parallel transformer or in the Modify stage ?