Hi,
While excuteing routine excute.sql of to excute sql query's in routine I am facing below problem.
TEST #1
*******
Arg1 = SELECT * FROM PROCS_LOG
Arg2 = gmodc
Arg3 = gwmoraods
Arg4 = gwmoraods
Test completed.
DSLogInfo called from : ExecuteSQL
Message to be logged is...
> SQL State = 08S01, DBMS error code = 0
> [DataStage][SQL Client][ODBC][DataDirect][ODBC 20101 driver]7505
DSLogInfo called from : ExecuteSQL
Message to be logged is...
> SQL State = 21, DBMS error code = -1
> [DataStage][SQL Client][ODBC][DataDirect][ODBC 20101 driver][20101]11603
Program "DSU.ExecuteSQL": Line 77, Variable previously undefined. Zero length string used.
Result =
Any one has idea ple let me know
Thanks In Advance
Error related to Routine of excute.sql
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 111
- Joined: Thu Jun 01, 2006 5:12 am
- Location: Detroit
Error related to Routine of excute.sql
kOTI,
1586-738-7785
1586-738-7785
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The problem is in YOUR ExecuteSQL routine. At line 77 there is a variable used to which no value had been assigned. That is, there is some path through the code where no assignment has been made to that variable, then at line 77 an attempt is made to use the variable as an rvalue (that is, something that might appear on the right hand side of an assignment statement, or some similar location where it needs to deliver a value).
It's your routine (not one of the out-of-the-box routines shipped with DataStage), so you need to fix it. If it's from a third party vendor, get them to fix it. If you downloaded it from here, contact the author.
It's your routine (not one of the out-of-the-box routines shipped with DataStage), so you need to fix it. If it's from a third party vendor, get them to fix it. If you downloaded it from here, contact the author.
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.