Page 1 of 1
Phantom 14763 Variable previously undefined. Zero length s
Posted: Wed Dec 07, 2011 10:16 am
by ketfos
Hi,
I have job running fine in one enviornment.
While I run the job in another enviornment with teh same data set, I am getting a message in the log with following entries.
Phantom 14763
Variable previously undefined. Zero length string
Line 33, Variable previously undefined. Zero length string used.
Line 46, Variable previously undefined. Zero length string used.
Line 57, Variable previously undefined. Zero length string used.
Line 68, Variable previously undefined. Zero length string used.
Any help is appreciated.
Thanks
ketfos.
Posted: Wed Dec 07, 2011 2:50 pm
by ray.wurlod
Can you please identify which stage (and its type, which I'm guessing is Transformer) is throwing this error, and what that stage is doing?
Posted: Wed Dec 07, 2011 3:46 pm
by ketfos
The message is coming at the end of the job in the following order
TransInNote: DSD.StageRun Active stage finishing.
DataStage Job 468 Phantom 29860
Program "DSU.TranslatePicCodeOther": Line 13, Variable previously undefined. Zero length string used.
The transform DSU.TranslatePicCodeOther is being used in the first stage of the job which is selecting from table.
Finished Job PolicyNoteOther
Posted: Wed Dec 07, 2011 4:06 pm
by adams06
Whats the job design?
Posted: Wed Dec 07, 2011 4:19 pm
by ketfos
OCI Stage (Selects) -- Transformer (uses the trasnform routine) -- puts into another transformer --- does a look up against the hash file with code returned by transform -- inserts/updates into an table --
The warning messages appear at the end of the job.
None of the above stage ahs any warning message
Posted: Wed Dec 07, 2011 4:36 pm
by ray.wurlod
The problem is in your routine TranslatePicCodeOther. The code in the routine is attempting to use the value of a variable before that variable has been assigned a value.
Posted: Wed Dec 07, 2011 4:44 pm
by adams06
Post the routine
Posted: Wed Dec 07, 2011 4:46 pm
by ray.wurlod
The code may be subject to non-disclosure. In that case post a suitably anonymous variant of the code.
Posted: Thu Dec 08, 2011 1:45 pm
by ketfos
Hi Ray,
This is what I did to resolve the problem.
I deleted the job in the current enviornment.
Imported the job from QA enviornment and exported the dsx files to the current project.
Ran the job again and did not find any warning messages.
Any idea why it resolved the problem.
The existing code which gae the error message was earlier promoted from the Qa enviornment only.
Posted: Fri Dec 09, 2011 7:20 am
by chulett
No way to know without seeing the actual code. Perhaps someone 'fixed' it in the other environment...