Unable to construct external null string

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
wdudek
Participant
Posts: 66
Joined: Mon Dec 08, 2003 10:44 am

Unable to construct external null string

Post by wdudek »

I have a sequential file stage, used as an input as well as an output. Previously there were no problems with this, but somewhere today I have managed to break it. When I run the job or try and open the output like I get the following message
TaxVendor..VendorRecord.strVendRecOrder: DSD.SEQOpen Unable to construct external null string for column 1.
I have been playing with the default padding, so that it will be blank space instead of the default # on null columns, could this have caused the problem?

Any thoughts on this would be great
Thanks,
Bill
wdudek
Participant
Posts: 66
Joined: Mon Dec 08, 2003 10:44 am

Post by wdudek »

Ok, I fixed the problem but it would be great if someone could explain it. I had changed the default NULL padding from # to 000, trying to get an empty string. Changing this back has resolved the issue. Can someone explain to me what the default null padding is?
kcbland
Participant
Posts: 5208
Joined: Wed Jan 15, 2003 8:56 am
Location: Lutz, FL
Contact:

Post by kcbland »

If the field is blank it will pad it with whatever you want. I don't know how you got the error mesasge, but you can supply the 3-digit ASCII number for fields when specifying delimiters or pad characters or quote characters etc. 032 is a space, 009 is a tab, blah blah blah
Kenneth Bland

Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

And '000' is a null. Some options interpret that to mean "I don't want this", but not the Padding character in the Sequential file stage.
-craig

"You can never have too many knives" -- Logan Nine Fingers
asitagrawal
Premium Member
Premium Member
Posts: 273
Joined: Wed Oct 18, 2006 12:20 pm
Location: Porto

Post by asitagrawal »

Hi,

I am facing the same problem today.. but I do not understand the soultion and the problem.

In my case, the output file is being created in EBCDIC and the column was initially defined as Decimal data type and default padding charatcer as #. Now after changing it to NVarChar , it started givign the error. It worled fine after I removed default padding character .

I am confused with whats has happened ??

Please help me in understanding this.
Share to Learn, and Learn to Share.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Is this latest incarnation a server job or a parallel job? The original post was a server job; your description suggests parallel to me. If so please start your new thread in the Parallel forum.
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