hi,
Is it possible to specify the output of SQL Query in the WHERE Property of Filter stage?
Filter Stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 222
- Joined: Tue Aug 30, 2005 2:07 am
- Location: pune
- Contact:
I think, it is not possible to do this directly in the where condition of filter stage. There should be a intermediate dataset/sequentail file to store the result of your SQL and then perform filter on the required column.
NageshSunkoji
If you know anything SHARE it.............
If you Don't know anything LEARN it...............
If you know anything SHARE it.............
If you Don't know anything LEARN it...............
#job_parameter# is a step in the right direction, but...
The #job_parameter# is easy enough to understand for the filter stage. I'm more curious about an easy way to do something like this on thesplayer wrote: = #job_parameter#
You have to define the job parameter in your job first.
Code: Select all
JobProperties.Paramters tab:
Parameter Name: job_parameter
Prompt: The job parameter
Type: Integer
Default Value: select 1+max(seq_foo) from somedb.sometable;
Description: Hit the database before we run this job.
(it is _really_ kind of a shame that the conductor doesn't have a "blackboard" to allow (essentially) global variables visible across all players).
Re: #job_parameter# is a step in the right direction, but...
Yup. One job to fetch the value and stash it somewhere. Simplest place seems to be in the USERSTATUS area each job has. Then a Sequence can auto-fetch that value into a Parameter in a downstream job:jgreve wrote:Am I on the right track here?
Code: Select all
JobActivityStageName.$UserStatus
Code: Select all
FUNCTION CallSetUserStatus(Arg1)
Call DSSetUserStatus(Arg1)
Ans=Arg1
You could also write the value to a flat file and use a routine to read it and pass the value back out. Or write it to a hashed file with a hard-coded key. The routine that fetches the value can either be used in a Routine Activity stage so the value can be passed in as a job parameter, or the routine can be used in the Initial Value of a stage variable if you just need to get it into a job for use in derivations. If a hashed file is used for storage and the desire is to seed a Stage Variable then the supplied sdk routine UtilityHashLookup can be used to retrieve it in most cases.
Note there is some Server specific answers in here, but much can also be leveraged by Parallel jobs.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers