What would be the following warning message,
DataStage Job 102 Phantom 20769
Program "JOB.122335461.DT.132456721.TRANS3": Line 1234, Variable previously undefined. Zero length string used.
Thanks
VS
Phanto Error - Warning
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 123
- Joined: Wed May 18, 2005 7:41 am
- Location: USA
Just what the message says - the program has referenced a variable before it was assigned a value. If you use an undeclared stage variable or similar in a derivation you will see this error. Check your transform variable usage - it may even show up in red in the designer.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 59
- Joined: Sat May 29, 2004 12:31 am
- Location: Pune
Hi,
I too get the same warning msg some times.
When I change the input file, then I am not getting this sort of warning. I though it might be the issue with the data.
I have verified all the routiens, tranformation functions and stage variables. None of them are undeclared.
Is there any other reason for these panthom warning??
Thanks & Regards
Vijay Kumar
I too get the same warning msg some times.
When I change the input file, then I am not getting this sort of warning. I though it might be the issue with the data.
I have verified all the routiens, tranformation functions and stage variables. None of them are undeclared.
Is there any other reason for these panthom warning??
Thanks & Regards
Vijay Kumar
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It's not undeclared so much as uninitialized.
When you create stage variables, make very sure that you always give them an initial value.
Of course it may not be a stage variable that's causing this message. It may (for example) be a variable within a routine that's not assigned, which may mean that there is a path through its code in which the variable named Ans is not assigned, or that there is some other variable name used where that variable was never assigned a value; this smacks of insufficient/incomplete testing of the Routine.
When you create stage variables, make very sure that you always give them an initial value.
Of course it may not be a stage variable that's causing this message. It may (for example) be a variable within a routine that's not assigned, which may mean that there is a path through its code in which the variable named Ans is not assigned, or that there is some other variable name used where that variable was never assigned a value; this smacks of insufficient/incomplete testing of the Routine.
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.