DSXchange

Dates are stored as binary quantities inside DataStage - format of a date data type is purely for human convenience.

Format is also important if converting the date to a string.

Decimal numbers are always displayed by the data browser and by Peek with leading and trailing zeroes. This mechanism allows you to verify that precision and scale are being accurately handled. Internally, of course, decimal numbers are represented as binary - just a pattern of bits.

This step has no datasets is the score used for licensing. It is an Informational message. But the message "Control job aborted" is significant. This job was being run under control (of a job sequence, a batch or a job control routine). You need to look in the log of the controlled to find out why T...

Why do you think that?

It may be only the Pivot stage that needs to be re-installed or re-registered. The first of these is accomplished on the server using DataStage Package Installer, the second using the Manager client.

Why are you all wasting your time guessing the requirement? Why not wait until dstest posts the precise requirement, as asked?

Set APT_PM_SHOW_PIDS to have player processes log their pids. The ppid of each is the section leader on that particular processing node. You can then use dsjob to read the relevant log entries, and ps to see the processes from the UNIX environment.

Having restored DSEngine and the projects, try reinstalling the server. This should go into maintenance mode. If there is a hidden file in the root directory its pathname would be .dshome - check for hidden files in the root directory

There are four major resource classes on a computer; processing, memory, disk I/O throughput and network bandwidth. Commands for monitoring all of these exist, for example prstat, vmstat for processors and virtual memory usage. More general tools, such as top, also exist. These should be run for a s...

For example, DELETE FOM table will always wait for any update lock on any row in the table to be released, if no "escape clause" (syntax varies with database, but is not provided from the "Clear table" method) is issued.

clarcombe wrote:Time does not permit anything else.

That is never really true.
There is never time to do it right, which means that you have to find time to do it again. Doing it right the first time is actually the more efficient solution.

Does your wildcard ever generate a list that is too long for the command parser to handle?

Colin already had a loop in his routine, so 'twas a simple matter to include the removal within the scope of the loop. I guess verifying that the removal had worked would have been preferable.

ag_ram wrote:Till yesterday it is running fine. Today only we are getting this error.

What has changed? Obviously something has.

Those symptoms suggest that either the DB2 client software is not properly/fully configured, that you have not run bind20 (or bind19, as the case may be), you may not have set required DB2 environment variables such as DB2INSTANCE, or that you have not properly created the DSN for connecting to your...

Three questions for basu.ds:
1. Please post YOUR input data and lookup table.
2. What output do you require:
(a) if there is no match
(b) if there is exactly one match
(c) if there is more than one match?
3. How have you currently designed this and what's happening in your design?

Unless you take the code generated by the job sequence as a prototype and load that into a server job, there is no activity that can alter the value assigned to the StartLoop.$Counter activity variable other than the Start Loop activity to which it belongs.