DSXchange

You need to clarify if this is a native xls file or one you've saved as a csv or prn or some other delimited format first.

So, 1GB of RAM... that's the minimum amount just for the O/S. I would see about having another 1 or 2GB added to it. Seriously.

Exactly. At some point it will be enforced, after all.

ArndW wrote:You are probably reading a .csv file, not an excel spreadsheet. could you post a sample line or three?

I wager 400 Quatloos on it being a .xls file.

No. What O/S are you running and how much memory is installed?

Yes.

As I said, never used them (or needed to do any such mainframe thing) so took a guess as to what might work. Time to involve your official support provider it seems, that or wait for someone who's done that kind of thing before to wander along.

Pretty much for what they're named... and seems to me like you'd use the 'Transaction Before' command to perform your 'quote site etc' command, though I've never used it.

The StringToDecimal() function comes to mind, as long as the contents are indeed convertable.

That's not a Julian date but rather an Ordinal date, meaning the first two digits are the year and the next three are the day number for that year. From the manual: "A Julian day specifies the date as the number of days from 4713 BCE January 1, 12:00 hours (noon) GMT" In other words, just ...

What changed in those 'some days'? And how about those details?

Had this worked before and then stopped? Or does it immediately fail? Trying to determine if this is somehow data related or if your reference lookup is not setup correctly. It would help if you detailed your lookup - post the sql, detail how many columns are defined in the stage, their order, key v...

So, execution of a perl script once per row inside your job? That's really going to kill performance, are you sure there's no better approach available here? What does the script do?

Job level.

Some flavor of 8.1, could depend on the platform. And 'XE' was more of a product edition 'bundle' and that particular ones no longer exists AFAIK.