Hi, I run a Job that execute a Sybase store procedure with two parameters and the message in the Subject of this topic appears. The sp must show 240 rows of data with 71 columns. I already checked "Procedure returns multiple rows" check box, in the columns tab I declare the 71 columns plus two columns for two parameters of input (73 columns total), and "Parameter marker/literal" tab show #$date# and #$branch# that I need to enter in the parameters.
I don't know why it didn't work. In DBArtisan I write the following sentence and its work:
exec spJob '20060228', 747
Please, could you help me?
Thanks!
expects parameter @date, which was not supplied
Moderators: chulett, rschirm, roy
-
DanielXBernal
- Participant
- Posts: 2
- Joined: Tue Jan 03, 2006 9:31 am
expects parameter @date, which was not supplied
Daniel Bernal
JPMorgan Chase Bank
Chile
JPMorgan Chase Bank
Chile
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard. :D
If you use constructions like #string# it means you are making reference to a job parameter for the server job. However, this is mediated by a $ at the start of the parameter name (for example #$TMPDIR#) being a reference to an environment variable.
My guess is that you have not got environment variables called date and branch.
If you have job parameters called date and branch, lose the "$" from each parameter reference.
Are you using an ODBC stage or a Stored Procedure stage to invoke the SP? If the former, you will need to have previously imported the SP definition (so DataStage can check the argument count), and invoke it via a CALL statement (method = "call stored procedure" or "user-defined SQL").
If you use constructions like #string# it means you are making reference to a job parameter for the server job. However, this is mediated by a $ at the start of the parameter name (for example #$TMPDIR#) being a reference to an environment variable.
My guess is that you have not got environment variables called date and branch.
If you have job parameters called date and branch, lose the "$" from each parameter reference.
Are you using an ODBC stage or a Stored Procedure stage to invoke the SP? If the former, you will need to have previously imported the SP definition (so DataStage can check the argument count), and invoke it via a CALL statement (method = "call stored procedure" or "user-defined SQL").
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.
-
DanielXBernal
- Participant
- Posts: 2
- Joined: Tue Jan 03, 2006 9:31 am