DSXchange

I don't believe that != is a valid operator in server job expressions. The only valid operators in DataStage BASIC for "not equal to" are <> >< NE # You are not permitted to test against @NULL. You must use the IsNull function. Expressions do not support the CASE construct; in an expression you'll n...

In DataStage you need two Aggregator stages.

In most databases you need two separate queries.

Red Brick is the only database of which I am aware that allows multiple DISTINCT clauses in the one SELECT query. But, then, it's designed for data warehouse (business intelligence) queries.

That's a question best posed to your DB2 DBA who must configure sufficient space to handle transactions of the size you desire. Or, more likely, to tell you to use smaller transactions.

Give an example of what you are processing and what you expect to see. A single Aggregator will satisfy the request you originally posted.

Define your term "module". Without that, you have a "how long is a piece of string" question.

CLEAR.FILE will work via ExecTCL only if the hashed file was created in an account. If the hashed file was created in a directory you need the operating system variant (clear.file) with the pathname of the hashed file. $DSHOME/bin/clear.file pathname executed via ExecSH (for UNIX) or ExecDOS (for Wi...

Using the optional real time interface (RTI) component you can set the job up as a Web service and have anyone execute it at any time.

What ELSE (non-DataStage things) might be happening in the database that might hold locks for a long time? For (non-exhaustive) example backups, batch loads, defunct processes owning locks.

The reason that "fix" worked is that DS.REINDEX drops and re-creates the index. Dropping a corrupt index and building a clean one ought to fix most index problems!

Incidentally, you can use DS.REINDEX against a specific repository table, for example DS.REINDEX DS_JOBS.

Is it possible to COUNT hash file records created not in account but in a specified path?.Does not work for me even if I LOGTO uv. Create a DataStage job that processes all the keys from the hashed file and record the rows processed. The statistic can be found by interrogating the job itself (DSGet...

Hashed file lookups with hashed file stages involve ONLY the "=" operator. End of story. The rvalue (reference key expression value) given is passed through the hashing algorithm for the hashed file, and the location for the record thus determined. The record is then either retrieved or reported as ...

When you're using a Hashed File stage there are no special considerations. The stage (with the underlying engine) looks after everything. All you have to do is to make sure you've identified ALL the key columns accurately. As will all hashed file metadata (whether single or multiple key), the Positi...

No. No "." character is allowed in the invocation ID. This character is reserved for all kinds of things in the object programming and in the SQL world. What you could do is use invocation IDs "LoadDataRun1", "LoadDataRun2", etc. Then your job names become InitialCheck.LoadDataRun1, InitialCheck.Loa...

The "user status area" is a field in one of the records of the job's RT_CONFIGnnn hashed file. There is one RT_CONFIGnnn file for the job. As was pointed out, multi-instance is still one job; the most recent update of the user status area is the one you see. Create a hashed file (the overheads are n...

Appoint a metadata steward with full responsibility for metadata. That person can choose whether or not to delegate, and should have the power to threaten and punish! Don't lose sight of the bigger picture; the start of a project is THE BEST time to implement tools such as MetaStage and Parameter Ma...