DSXchange

Update:

Version 11.3 processes a file pattern in parallel by default.

Version 11.3 processes a file pattern in parallel by default.

Version 11.3 processes a file pattern in parallel by default.

Here is one version 11.3 performance improvement of interest. Description: In InfoSphere DataStage Version 11.3 the behavior of the Sequential File stage was changed so that a file pattern is converted into a fileset before the files are imported. This change allows the files to be processed in para...

Version 11.3 is avialable for download today, in case you want to jump to the newest.

Double check your schema file. It looks like field3 is named twice, then after that 3 fields are not named.

If you have a job naming convention, such as sequence jobs names begin with "seq_" then you can check the first 3 or 4 characters.

It takes 7 hours to read the hashed file?

4. Check with your network team about working some magic. They may be able to setup an encrypted IP tunnel if given the source and target IP addresses and port numbers. It would encrypt packets during transport and decrypt packets as they reach your DataStage server.

Deprecated stages Connectors, which offer better functionality and performance, replace some stages, which have been deprecated and removed from the palette. However, you can still use the deprecated stages in jobs, and add them back to the palette. - Quoted from this link . I am curious if there a...

Have you tried searching this site on the error?

Have you tried searching the IBM support portal on the error?

If your server is on UNIX, then you should not have a SQL Server stage type available. I have seen it happen, after a botched migration from Windows to UNIX. Double check your stage type. What stage is it? What happens when you run it with tracing off?

Migration steps can be found in the IBM Knowledge Center. Here is a link.

Migrating to IBM InfoSphere Information Server, Version 9.1 (or 9.1.2)

Ah... so they've "fixed" that, good to know. What I found in 8.7: - An env var with type=Encrypted still shows the "encoded" text in the job log - A traditional parameter (non-env var) with type=Encrypted shows only stars in the job log, so that much is fixed. You can still expo...

I think your first step would need to be upgrading to version 9.1 or higher.