DSXchange

Yes and no, I would think. Yes in that you could do it as it's just another drive, no if you think that means you can move it from PC to PC with impunity.

UNIX to Windows (or vice-versa) would be cause for concern, but UNIX to UNIX? Not so much, unless you believe that you've done anything that might be considered "Solaris specific" in your scripting or other interactions with the operating system? Otherwise, the first suggestion would be to...

What exactly did you try? Post your StringToTimestamp attempt syntax and we'll go from there.

Change your "select *" to mention all of the columns you are selecting individually by name.

Yes, that's what the product known as RTI / SOA / WISD is all about. There's a specific forum for discussions of it as well, read about it there. It's also a good place to ask any other questions you may have.

The "VW_" prefix should mean you are sourcing from a view and not directly from a table, so there could be an 'order by' in the view definition for all you know.

As I said, get rid of the -jobstatus option. A simple -wait will change the exit status of the job to "zero = success" and "non-zero = failure" rather than 1=OK, 2=Warnings, 3=Aborted, etc.

It's returning a "1" for OK because you told it to, that's what the "-jobstatus" option does. If you want zero for success, change that option to "-wait".

Silly question, perhaps, but why not use a Job Activity stage for this?

There are 12 other posts that a search for "Import validation failed" turned up, did none of them help?

Why so sad?

So... based on your mention of "columns are G,H,I" can we assume this is an Excel spreadsheet exported or saved as in a tab-delimited format? I'm also wondering how the file gets over to the DataStage server, is it transferred from elsewhere, say with FTP or created directly there or what?...

The Monitor in the Director gives you that information for the most recent run, and it can be derived from the job's log for however far back that goes. Outside of that, you will need to capture and store this audit information run over run in order to persist it for long-term analysis. ETLStats com...

And *I* want... well, never mind what exactly it is that I want. As I said, I've had no issues with this, from either sequential file pathnames to pathed hashed filename so perhaps it varies from UNIX to UNIX. As noted, this typically comes from combining two parameters with a hard-coded slash (or p...

"Operator Access" requires released jobs to work, at least in versions before 8, a process that has been deprecated. From what I understand, that role is actually useful in the 8.x versions but before that... not so much.

What did you find when you searched the forums here for "[General repository interface 'other error']"? Nothing there help at all?