DSXchange

Theoretically it's possible but IBM usually advise against mixing platform types.

Let's start with what kind of user authentication you are using with WebSphere Application Server for Information Server - is it internal user registry (Information Server repository), operating system or LDAP? "Failed to authenticate the current user against the selected Domain" reports t...

That is so ugly. What's wrong with two jobs? I have to guess that dummy is a Transformer stage, and that the file to which you write in the sequential file stage downstream of dummy is not the same file read by this stage. Have you placed documentation in your job - ideally an annotation - alering f...

Information Server Manager (GUI tool). It has istool as its command line equivalent.

That log is native_stderr.log, and all its showing is one problem allocating memory (which was managed) and garbagecollect operations occurring as required (every minute suggests that some activity was finishing). There's nothing in this particular problem to indicate that you have the same problem ...

Ordinarily I recommend creating an alias/synonym for the table name, with no space or other illegal characters, and the use of that for interaction with DataStage.

An infinite list?!! Even an infinite number of monkeys could only manage the complete works of Shakespeare - not a single environment variable among them!

True (what Craig said) but a sufficiently severe setting of transaction isolation level can cause even inserts to take a page-level or table-level lock.

Shouldn't matter. The column does not exist in the named table.

I'd use a Sequential File stage with a PDF converter as the filter command.

The "Server to Parallel Transition Lab" training DVD, available from DSXchange Learning Center, has some material on partitioning.

So does the IBM training class "Advanced DataStage" or some such title.

The Field (column) called 'WORK_HISTORY_FUNCT_LOCAT_SHORT_DESCR_CHR' does not exist in the table 'Work History'. That is, the metadata (table definition) used in your job does not accurately reflect the column name(s) used in the 'Work History' table. This error may be being thrown spuriously becaus...

Change your Array Size to 1, at least while testing, so that the OLE provider can accurately report the actual row in which the allegedly invalid data occurs.

Seriously, though, rameshkm needs to elaborate what is meant by "Dat file", as requested.

Oh noes! You broke the juxtaposition with Read Dat file in DataStage!!