DSXchange

ray.wurlod

Verify the efficacy of your f_get_PX_ConfigFile command.

ray.wurlod

It's difficult to say - you haven't really supplied enough information for diagnosis. For example, have you specified a partitioned table? If so, do you have the requisite SELECT privilege on the system tables?

ray.wurlod

It's difficult to say - you haven't really supplied enough information for diagnosis. For example, have you specified a partitioned table? If so, do you have the requisite SELECT privilege on the system tables?

ray.wurlod

Code: Select all

SELECT CATEGORY FROM DS_JOBS WHERE NAME = 'TestTivoli' SUPPRESS COLUMN HEADING ;

ray.wurlod

Bulk loader.

ray.wurlod

Separation should match your hardware - that is, be a small whole multiple of your disk/memory page size.

As a guideline, try to get 5-9 records per group. More if they are very small records.

ray.wurlod

No index is created on the key. Hashing algorithm is much faster than using an index. Indexing key columns individually will only help if you run queries against the hashed file in which the report is constrained (or sorted) on those individual columns - in short, generally the answer is cost but no...

ray.wurlod

If you know in which fields the line terminator occurs, just mark those columns "contains line terminator" in the Columns grid. DataStage will do the rest.

ray.wurlod

I prefer to add them from the GUI, only because the rules test utility is right there on the same menu.

Other than that there's little to choose between them.

ray.wurlod

You did not specify that they were format strings, so I had to assume they were data.

ray.wurlod

Verify that they are really space characters. Convert() should definitely be able to eliminate them. Trim() should also remove redundant white space.

ray.wurlod

It's a bit hard to write a help manual for a stage in which you write the code ! What have you gleaned from the Parallel Job Advanced Developer's Guide ? Try asking for specific advice - the answer to this particular question can only be "any time you like" - but try not to "re-invent the wheel" by ...

ray.wurlod

Think of the 80% as "headroom". It allows for some degree of variation in how full each individual group buffer is, and thereby some protection against groups overflowing - one of the main vulnerabilities for file corruption. It is similar to, but not the same, as SPLIT.LOAD for dynamic hashed files.

ray.wurlod

Code: Select all

SELECT NAME FROM DS_JOBS WHERE JOBNO = '43';

Execute from command window in Administrator client.

ray.wurlod

How about an ExecuteCommand (do not skip) activity at the front of the job sequence?

Code: Select all

test -f #pathname# && rm -f #pathname#

Search found 53125 matches