DSXchange

In the Administrator client select your project and click the Command button. This opens a dialog in which you can enter "TCL commands" in the project. It's here that you enter the SETFILE command and the COUNT command. SETFILE pathname_of_hashed_file name_of_hashed_file COUNT name_of_hash...

Output (the variable that collects the output from the command stream) will have line terminator character(s) in it. These will have been converted into field marks, which you need to remove, either in the routine itself Ans = Convert(@FM,"",Output) or in the job sequence expression that u...

I guess I'm being super-hopeful but is the error code BWPACK_E_00028 mentioned the manual for the SAP BW Extract PACK or in the Errors and Messages manual for DataStage?

What do you mean by "a lot"? One per column, or one per row processed? In the former case it's metadata related, in the latter case it's data related. Please verify that the row structure is identical on all inputs and on the output link of the Funnel stage.

Please Search

If that's really in the value, and the data type is Char or VarChar, then you have uncovered a bug and must report it to your support provider. In the meantime, and as a workaround, convert the "#" to some other character that does not occur in your data (maybe Char(1)), perform the concat...

My earlier post to this IS your solution. Read the files with a Sequential File stage with a filter command (cat). You now have a single stream of rows. Use a Transformer stage to generate the line number (@OUTROWNUM) and to constrain so that the heading lines from job2 and job3 aren't passed (bette...

SHOW us what you are attempting in the Modify stage: input and output data type plus specifications.

Are you using a NOWARN specification?

Not possible (except in original COBOL application, of course) without unpacking. Well, that's not entirely true, but it would need to be a custom routine to examine each possible bit pattern of each pair of bytes (allowing for byte order of the hardware, of course), which would probably be slower t...

So am I. Creating the Parameter Set causes an eponymous directory to be created in the project directory, and if you create values files these are stored in that directory as ordinary text files. Therefore you can edit them. I will be presenting a DSXchange Learning Center webinar on Parameter Sets ...

Welcome aboard. When you see #DBNAME# (or any value surrounded by "#") in your job log it suggests strongly that that job parameter was not set for this job run. Could it be that your job uses environment variables, and the parameter reference should therefore have been #$DBNAME# ? Or is t...

There's always that, which is why I asked about test results. I guess we now await feed back from the original poster.

Can you be more specific about where this "#" character appears? If it's in the data it should not be causing a problem. But if it's in a property field in the Transformer stage then it's understood to be part of a job parameter reference.

I think radarada means "decimal[38,10]" rather than 38,10 as the value.

Even so, in most European locales, 38,10 IS a valid decimal number.

It will remain that way and only propagate the columns at runtime. Whence "RCP".