DSXchange

Client and server versions, fix packs, and patch levels should match, whether the client actually connects without warning/error or not.

Information Server 8.7 is the current version as of October 2011.

Just looking at the palette of a parallel job, I see 3 Informix stage types:

Informix CLI

Informix Enterprise (default)

Informix Load

In that case, you don't really need to take the timestamp into consideration. You could call an after-job script to rename the reject file immediately after each job run completes. It could increment the file name's extension by a number or it could name the file so the file name contains a timestam...

To apply auto-purge settings to existing jobs, you have to export and import all the existing jobs.

It should not cause any problems as long as all the file systems involved are available when needed. The *.apt config file(s) are flexible in allowing you to point to various paths across nodes.

You still have to decide and explain what you mean by partitioning on the timestamp. Example: - All timestamps ending in an odd number go to file1, ending in an even number go to file2... (like modulus partitioning in DataStage). - All timestamps from hour 1:00am to 2:00am go to file1, 2:00am to 3:0...

Compilation must be initiated from Designer on the client tier (Windows only). I wouldn't mind being proven wrong. :P FYI: Server side command line compile has been requested (future release): JR42097: REQUEST THE ABILITY TO COMPILE DATASTAGE JOBS ON THE SERVER SIDE(NON-WINDOWS ENVIRONMENT) http://...

FYI:

Server side command line compile has been requested:

JR42097: REQUEST THE ABILITY TO COMPILE DATASTAGE JOBS ON THE SERVER SIDE(NON-WINDOWS ENVIRONMENT)

http://www-01.ibm.com/support/docview.w ... wg1JR42097

Names of the Transformer stage functions are:

LastRowInGroup()

LastRow()

I believe these were first introduced in version 8.5.

Need more info:

Please give an example of a reject record including the timestamp column.

How are you wanting to decide on the partitions? Based on timestamp range? If so, how are you deciding ranges? Based on row counts, etc.?

Here is a recent IBM tech note about the Metadata Workbench 8.7 tutorial import failure:

InfoSphere Metadata Workbench tutorial: istool command to import ISX data fails

http://www-01.ibm.com/support/docview.w ... wg21584427

Have you tried making the metadata match what's actually coming out of the first OCI stage? You can change the data type after that stage to something that you really want.

Thanks!

FYI: For whom it may help in the future, there is an IBM tech note on the error message given:

Information Server DataStage error message: No Engine credentials were found on the Services Tier

http://www-01.ibm.com/support/docview.w ... wg21576785

FYI: I just learned that in version 8.5 and higher, you can set the DS_USE_SERVER_AUTH_ONLY environment variable to allow dsjob to work the same as if the -domain NONE option were used. See the following IBM tech note for details: Why the dsjob command can take longer to execute tasks than it did at...