DSXchange

ray.wurlod

From the world-wide head of DataStage (Keith Kohl) at a recent IOD conference, server edition will be around as long as DataStage is around. Although Keith did not say so, the main reason for this is the large number of server jobs out there, and the fact that sequences are in fact server jobs. So t...

ray.wurlod

It's not unit - it's uint - unsigned integer. NUMBER(19) does not fit into a regular integer (32 bits) but does fit in a 64-bit structure. That's the 64 of uint64 in the data type. uint64 is a data type. So talk of "equivalent" is moot. Since SQL does not support unsigned data types, there...

ray.wurlod

Look in the log file for each run type (alone and from sequence) and see what's being passed as this parameter. Compare the values. Please also advise your exact version of DataStage.

ray.wurlod

Did you make the environment variable Encrypted type?

ray.wurlod

No.

You'll never be able accurately to identify the process.

And it will only get more difficult when you move to version 8.

ray.wurlod

Node Pools can be subsets of the available nodes. The default node pool (which has the name "" in the configuration file) must include at least one node. Disk Pools can be subsets or supersets of the disk (resource or scratch) available. One site where I worked used a 34 node configuration...

ray.wurlod

Not possible.

Why do you think you want to do it that way?

There is a way, but you have to generate the query externally to the job (perhaps in a prior job) then pass the query into this job as a parameter value.

ray.wurlod

It says there's no key of that combination of values in your target table, therefore there's no such row that can be updated.

ray.wurlod

Warnings do not count as failures.

You will need to code your own, using (probably) explicit Warning triggers or custom multi-status triggers.

ray.wurlod

http://www-01.ibm.com/software/data/inf ... ation.html

ray.wurlod

The following function definition is reported in an installation log.

Code: Select all

FUNCTION getXmetaFormatTimeStamp (DBTIME TIMESTAMP)
RETURNS BIGINT
LANGUAGE SQL
CONTAINS SQL
DETERMINISTIC
BEGIN ATOMIC

RETURN CAST(((DAYS(DBTIME)-DAYS('1970-01-01'))*86400 + MIDNIGHT_SECONDS(DBTIME)) AS BIGINT)*1000;
END

ray.wurlod

You can Save the table definitions from your job designs back into the Repository. Once there they can be exported.

ray.wurlod

Then why not use IsValid() to test whether your number is valid as an unsigned BigInt (uint64)?

ray.wurlod

deepa_shenoy wrote:It is working fine except when the first stage is a Dataset. It keeps giving incorrect record count.

What record count do you get when using the dsrecords command with the Data Set?

ray.wurlod

That's not a bug, and it can happen with Copy stage also. There's no count because the stage is optimized out of the design. Inspecting the score can verify that this has happened.

Search found 53125 matches