error on reading vb script generated csv file

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
egsalayon
Participant
Posts: 27
Joined: Sun Sep 23, 2007 9:21 pm

error on reading vb script generated csv file

Post by egsalayon »

Hi,
We have multiple repeating (example would be a monthly report) excel files are sources. Instead of creating a DSN each time a new excel source, I created a vb script that would dump data into a csv file. I set the sequential file option/property 'Record Delimiter String' to 'DOS format'. But when I tried viewing the contects of the file, it encounters error:

Consumed more than 100000 bytes looking for record delimiter.


Hope you could help me on this, many thanks and more power...

Regards,
Eric
Last edited by egsalayon on Mon Apr 16, 2012 8:22 pm, edited 1 time in total.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You'd better tell us what the error is, since the record delimiter in this file clearly is DOS-style.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
egsalayon
Participant
Posts: 27
Joined: Sun Sep 23, 2007 9:21 pm

Post by egsalayon »

Hi Ray,

Thanks for the reply.
ray.wurlod wrote:You'd better tell us what the error is, since the record delimiter in this file clearly is DOS-style. ...
I mentioned the error in the first post which is:

"Consumed more than 100000 bytes looking for record delimiter. "

I am including the screenshot of the error:
Image

Screenshot of the Record delimiter property in sequential file stage:
Image

Sorry, I need to remove the screenshot of the vb script generated CSV file since its data is confidential..

Regards,
Eric
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Don't see anything obviously wrong... what exact 8.x release is this?
-craig

"You can never have too many knives" -- Logan Nine Fingers
egsalayon
Participant
Posts: 27
Joined: Sun Sep 23, 2007 9:21 pm

Post by egsalayon »

Hi Craig,

Version is 8.5 fixpack 1

Regards,
Eric
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

Any chance there are extra characters hiding after CR/LF?
Choose a job you love, and you will never have to work a day in your life. - Confucius
egsalayon
Participant
Posts: 27
Joined: Sun Sep 23, 2007 9:21 pm

Post by egsalayon »

Hi Eric,
qt_ky wrote:Any chance there are extra characters hiding after CR/LF?
None
kandyshandy
Participant
Posts: 597
Joined: Fri Apr 29, 2005 6:19 am
Location: Singapore

Post by kandyshandy »

how does data look when you open with Textpad or UltraEdit?
Kandy
_________________
Try and Try again…You will succeed atlast!!
egsalayon
Participant
Posts: 27
Joined: Sun Sep 23, 2007 9:21 pm

Post by egsalayon »

kandyshandy wrote:how does data look when you open with Textpad or UltraEdit?
What I use to view the file is Notepad++ and when I set the option View->Show Symbol->Show All, no extra character except for the CRLF which is the Carriage Return and Line Feed characters.

Will install Textpad for the checking you requested.

Does anyone here taken the same as route as mine:

Excel File-->Processed by VB Script-->Output to CSV/Text File

I think its the VB Script has putting extra characters, just my observation now
egsalayon
Participant
Posts: 27
Joined: Sun Sep 23, 2007 9:21 pm

Solved: Setting of Encoding in the vb script was set to ANSI

Post by egsalayon »

Hi,

Our hunch is correct, it is on the creation of the csv file on vb script. Need to set to encoding to ANSI.

Thanks for all who provided insight and time in this inquiry..

Best regards,
Eric
Post Reply