Hello
I have worked on 7.5 px and there I have used the derivation in passing the parameter . it is just like a basic transformer .
eg.... param for infile = <File Patern>||current date
(it is done either at job level or seq level ...donot quite remember)
and this value --- out come = ccd1.plc.0005.03292006
----- will ne passed as parameter
Now i want to do the same thing in 7.1 ... and i dont see the option ,,, can anyone please help me out with this ...
Thanks
DS1
derivation in parameter
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
There were a LOT of sequencer job enhancements in 7.5. The two important improvements for you is BASIC-like expression syntax in most job sequence activities and the User Variable stage. Sequencer jobs in 7.1 do not have it and are not nearly as easy to use. You could try a basic routine that retrieves and sets parameters and calls the sequencer job.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
kumar_s wrote:Alternativly you can process the desired outcome in a job or routine and pass it as UserStatus to the Job Activity.
Thanks for all the ideas.. so as you say i may not be able to use the basic functions as in 7.5... and as both of you suggested i could use a routine .... if I have a simple today - 3 months logic to apply to pass values to the param ,, how can I do that through routines
Thanks for all the help
DS1
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Put the logic in a routine, invoke the routine from a Routine activity, and use its $ReturnValue activity variable to supply the value to the Job activity as a job parameter value.
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.