I have sequencer job which calls up a routine (which requires one input parameter and that is the job name ) . I don;t know where I am going wrong in calling this routine in the sequencer but the sequencer fails and gives the follwing error.
Exception raised: @Job, Error calling DSSetParam(XYZ), code=-4 [ParamValue/Limitvalue is not appropriate]
If any one can help me with what may be the possible reasons or direct me to some post related to it , it will be gr8.
Thanks.
Sequencer aborting when it calls a routine.
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 503
- Joined: Wed Jun 29, 2005 8:14 am
-
- Premium Member
- Posts: 503
- Joined: Wed Jun 29, 2005 8:14 am
The routine is a type of lookup. It tries to find a number field on the basis of a date lookup.
It searches for todays date in a hash file and then selects a number from it to assign it to the next stage.
The output of this routine call is a parameter used in the next stage.Its something like -->
Select num from HASH where HASH.DT = @date
It searches for todays date in a hash file and then selects a number from it to assign it to the next stage.
The output of this routine call is a parameter used in the next stage.Its something like -->
Select num from HASH where HASH.DT = @date
chulett wrote:What does your routine do? Sounds more like an internal problem trying to put that input argument to use rather than an issue of actually calling the routine.
Include any datatypes of the various parameters involved.
That's a different problem, when a non-zero return code is interpreted as a failure when that "Automatically handle" option is checked.
This is a parameter passing problem. It sounds like your parameter value being passed back from the routine is "not appropriate" for the parameter's datatype in the next job that is trying to use it.
Double-check what is actually being returned from the routine.
This is a parameter passing problem. It sounds like your parameter value being passed back from the routine is "not appropriate" for the parameter's datatype in the next job that is trying to use it.
Double-check what is actually being returned from the routine.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 503
- Joined: Wed Jun 29, 2005 8:14 am
The parameter passed back by the routine is a integer of length 10 and I checked twice , the datatype is correct .
Can it be due to HASH file?? I tried deleting the HASH file and then rebuilding it but no use. The job still fails with the same problem.
Can it be due to HASH file?? I tried deleting the HASH file and then rebuilding it but no use. The job still fails with the same problem.
![Crying or Very sad :cry:](./images/smilies/icon_cry.gif)
chulett wrote:That's a different problem, when a non-zero return code is interpreted as a failure when that "Automatically handle" option is checked.
This is a parameter passing problem. It sounds like your parameter value being passed back from the routine is "not appropriate" for the parameter's datatype in the next job that is trying to use it.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Code -4 means that the value you have supplied (presumably the return value from the routine) is not appropriate for the parameter type when you're requesting the run of a job.
For example, "" is not appropriate for Integer, Date, Time, Pathname parameter types.
For example, "" is not appropriate for Integer, Date, Time, Pathname parameter types.
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.