DSXchange

Saama wrote:iam defining column properties as MONTH.TO QUARTER('HIREDATE')

The quotes around the input column name are incorrect.

You misunderstood it totally.

It has nothing whatsoever to do with metadata.

Yet you posted the question on the Metadata forum.

Posting the question on the correct forum is more likely to yield a substantive answer.

It's a transform function and therefore can not be invoked as a before/after subroutine.

vijaykumar wrote:i need to make use of utilityhashlookup

You don't. It's the wrong answer to your requirement.

Source code is provided in the repository; examine it if you want to understand what it does and how it works.

Make the length 19 and supply an all-zeros time part. Your date picture indicates that you are supplying date and time components.

In the Transformer stage that you have not yet included in your design. However, it would be far more efficient to use a second Hashed File stage in the job design, and use the Transformer stage to perform the lookup against it. In this way, you do not incur the overhead of the routine, and possibly...

You build these tables according to the specifications of your customer. What information do they want recorded? Once you have those answers, you can figure out how to capture these from DataStage and elsewhere, and create tasks for recording them into the tables.

Maybe, maybe not. The network is a strange beast; it can be busy in some sectors and not in others, depending upon the topology. But domain controllers, it seems to me, are always busy.

Safer to assert that a job parameter can not legally be changed in a running job. Some folks out there are doing it illegally, and will need to re-think their strategy before upgrading to version 8.0, when their "hack" may cease to work.

All of these questions can be answered by searching the forum. You don't seem to want to use the user status area; if you do please search for DSSetUserStatus(). 3. If you've stored it in a file, read it from that file (maybe using a cat command in an Execute Command activity and trimming off the li...

It's informing you that you have not created a node pool called export in your configuration file so the export operator (which expects to find a node pool called export ) is using the default node pool - the one called "" - instead. This is a change from your design, so has to be reported. You migh...

How many identities do you have here?!! It is still not clear whether the source file contains all three records on one line or on three lines. If they are all one one line, you can simply treat the whole line as a single VarChar field, insert line terminator characters in the correct location, and ...

The "" character is how your data viewer represents a non-printable character, for example tab or esc. As for the "date filled by ''", look again at the hex dump to see what these characters actually are. If they're all 00 this suggests that NULL is represented by ten ASCII NUL characters...

How big is the field? How big is a signed packed decimal(9,3)? The difference is probably your input buffer overrun.

Substring is much faster than delimited field extraction. Therefore most bulk loaders recommend that you prefer fixed width format to delimited format.