DSXchange

Are the machines configured differently (CPU, memory, etc.)? What other load is there on the DEV machine that does not exist on the SIT environment when you're trying to open the Assembly Editor? How much memory exists in the client machines? Do all machines have the same patch levels? (Check their ...

Yes, use the istool build package variant.

Details here.

Some more thoughts.

You could build a Custom stage type to encapsulate a Data Set and a Head stage. But operator combination will achieve the same.

Or you could specify a Wrapped stage to effect the same using orchadmin and head commands in a pipeline.

If you compile the job in trace mode (which you set in job properties before compiling) you can then limit the number of rows processed.

A Head, Tail or Sample stage would be more efficient than a Filter stage.

But there is no such thing as a filter condition/WHERE clause on a Data Set.

Basically there is a large degree of overlap. As you would expect, the 11.3 certification includes questions about some of the new features in version 11.3.

You should also research use of the Exceptions stage and the Data Quality console - you may be able to save yourself a lot of work.

You're paying maintenance (which includes support) - why not use it?

Either get yourself set up on the engine (with appropriate group membership) or map your engine credentials to an existing user (that has appropriate group membership).

Don't forget to set automatic log purge in the ANALYZERPROJECT project.

I've just opened File Connector stage (version 11.3.1.2) for the first time, only to discover that the Help button is disabled.

I notified IBM of this through developerWorks

Contemplate using a server job with a Folder stage, or perhaps a Folder stage in a server Shared Container in your parallel job.

Just run as yourself if you're happy to do that. The tab in the Administrator client is there in case you want to use a different user name and password for running scheduled jobs. Note that this possibility only exists when the DataStage engine is running on a Windows server, not when running on UN...

The PeekHeader parameter is entirely irrelevant to the current question. It is the RecCountx parameters that drive the exercise's intent.

I don't know enough about Event Server to answer the question in that environment. In DataStage parallel job you would specify a timestamp format string that included microseconds, for example

When you submit jobs, select Retain Scripts. That having been done you will be able to view job logs using the DataStage Director client. The only pertinent logs you'll find in the WebSphere environment are SystemOut.log and SystemErr.log, which log ALL activity from Information Server, and might pr...