Hi,
I has a Sequencer Job which has a routine to pick the LastUpdDatetime from the hashed file. it's working fine.
My problem is it the picked value should be passed to the JobActivity.
To do this i created a prarameter at the Job properties. I defined a parameter called mofieddatetime with the type string. and assigned to routine activty return value.
But the job is getting aborting.
And gibing error like reference of the parameter is invalid.
Can any one help me if i need to define the same parameter any where else?
Sequencer Job is getting aborted
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 82
- Joined: Fri Jun 03, 2005 5:23 am
- Location: Bangalore
- Contact:
Sequencer Job is getting aborted
Rajasekhar
Rather than giving us things 'like' your error message, it is always best to post the actual error from the logs.
That being said, there's something in your returned parameter value that is not valid in a string. Without knowing exactly what you are doing, about all we can do is guess what might fix it.
One such guess? See if you can add <1> to the end of your $ReturnValue statement so that it looks something like:
You may also need to remove an 'extra' Field Mark from your data in another fashion if that doesn't work:
One of those two should work, I would think. It may depend on your exact version of DataStage which, if either, are allowed.
That being said, there's something in your returned parameter value that is not valid in a string. Without knowing exactly what you are doing, about all we can do is guess what might fix it.
One such guess? See if you can add <1> to the end of your $ReturnValue statement so that it looks something like:
Code: Select all
StageName.$ReturnValue<1>
Code: Select all
EReplace(StageName.$ReturnValue,@FM,"")
-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:
You almost certainly need a Custom trigger on your Routine activity. Without one, DataStage will assume that a return value of 0 means success and any other value indicates failure (the same as the exit status of operating system commands).
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.
-
- Premium Member
- Posts: 82
- Joined: Fri Jun 03, 2005 5:23 am
- Location: Bangalore
- Contact:
sequencer job is getting aborted.
Yes type of the parameter is same in both places.kumar_s wrote:Hope data type of the JobActivity's parameter is also string.
For clear understand i am giving here the error.
SEQ_Type2_Dimension..JobControl (@AAA): Controller problem: Error calling DSSetParam(LastModifiedDateTime), code=-3
[ParamName does not reference a known parameter of the job]
When i am assigining the routine returnvalue to the jobparameter the sequencer job is getting aborted.
Can any body help me in resolving this?
Regds
Rajasekhar
[sigh]
Yes, now that you've posted the actual error, the clear understanding shows me your problem isn't anything that I thought it was.
ParamName does not reference a known parameter of the job
Isn't that easy to understand? The parameter name being used in the Sequence job does not exist in the job being run. This is hard to arrange - but can happen if you change parameters in the job but not in the Sequence itself.
Open up the Sequence job and check the job/parameter in question. Correct whatever needs to be corrected and then recompile the Sequence itself. Try again.
Yes, now that you've posted the actual error, the clear understanding shows me your problem isn't anything that I thought it was.
ParamName does not reference a known parameter of the job
Isn't that easy to understand? The parameter name being used in the Sequence job does not exist in the job being run. This is hard to arrange - but can happen if you change parameters in the job but not in the Sequence itself.
Open up the Sequence job and check the job/parameter in question. Correct whatever needs to be corrected and then recompile the Sequence itself. Try again.
-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:
Check both spelling and casing of the parameter names you use.
Use the expression editor or parameter helper to select them, rather than typing parameter names. Typing is the principal source of typing mistakes.
Use the expression editor or parameter helper to select them, rather than typing parameter names. Typing is the principal source of typing mistakes.
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.