Phanto Error - Warning

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
satish_valavala
Participant
Posts: 123
Joined: Wed May 18, 2005 7:41 am
Location: USA

Phanto Error - Warning

Post by satish_valavala »

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
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

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.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Arnd, I thought you were on vacation! Didn't want to risk the slopes on Friday the thirteenth, eh?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Vijay Kumar
Participant
Posts: 59
Joined: Sat May 29, 2004 12:31 am
Location: Pune

Post by Vijay Kumar »

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
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply