DSXchange

ds_search2008 wrote:
$Path String $PROJDEF
catFname String cat LKP_ACTCODE(Default value)
Cust_Id Integer

You can't use "cat LKP_ACTCODE" as a file name in a pathname. This is also the cause of the "LKP_ACTCODE not found" error.

No, because the update of Record1 happens in the same Transformer stage in which the failed lookup of Record1 occurs. That is, it happens before the Transformer stage begins processing Record2.

I'm not sure where the cutoff points (for the size of the prefix number) are, but they represent the smallest unsigned integer needed to describe the length of the string. For sufficiently short strings (I would have thought 32 or fewer characters) that fit in a single word in memory no prefix is re...

For the first you would need to effect a number of queries against DS_JOBOBJECTS - the ROOT record for before/after subroutines, each active stage record for active stages in server jobs, each Transformer stage record for transform functions in server jobs (and others for parallel jobs). A query on ...

Alas, no, for named message handlers. You need to manage these "manually". Local message handlers are, however, exported.

Open the table definition for the sequential file. You should see the prefix mentioned as part of the record schema. You can save this to a file then remove the "prefix" part, and re-import.

Please use a more professional standard of written English. What you claim is not true; there are functions in the DataStage API for obtaining information from a job log, so that the whole process could be implemented in a Routine. You can also manage the whole process in a shell script using dsjob...

Welcome aboard. Are you sure you mean TX ?

You can get the job names from the job sequence's log, and the category of each from DS_JOBS table.

It's not mandatory (to use hashed files), but it's much faster, particularly if the database is not on the same machine as the DataStage server.

Did you Search? How to use stage variables to "remember" values from the previous row has been discussed a bajillion times, I am sure that at least some of those deal with running counts.

Reporting Assistant was deprecated at version 5.2, and does not handle job sequences.

Welcome aboard. Not all environment variables exist by default in Administrator - though this does not preclude your putting any there that you need. DataStage environment variables are described in the manuals for parallel jobs - that is Parallel Job Developer's Guide and Parallel Job Advanced Deve...

Get "them" to supply you with a valid CSV file would be favourite. Commas within data require that character strings be quoted. Otherwise you're going to have to specify something else as field delimiter - something not in the data at all - and effect your own parsing in a Transformer stage.