DSXchange

But, if there are only 2 updates per 100 records then doing it via the reject method might be more efficient; it depends upon the ratios.

<duplicate content removed>

Yes, if your method is "insert" and you have a reject link coming out of your database stage you can then modify the data and re-write it. Depending on your data volumes and the percentage of "failed inserts" you might want to design the job to do lookups on the record prior to deciding whether to d...

samythiru - no, there is no need to restart the DataStage engine when using different PX configuration files.

p.s. No need to quote messages, either.

krishnendusengupta - (you don't need to quote everything on reply) A sequential file? Does anything go dow that link? If you change your job so that instead of the Oracle stage you write to another sequential file, does the job also hang? I think it won't the "hang" you are seeing is probably associ...

Both the sequential and hashed files are best placed in another directory, preferably one mounted on another partition/attach point. That way the DataStage directory remains uncluttered, as narasimha pointed out, but in addition it keeps the project directory from filling up to 100% and potentially ...

Welcome to DSXchange, krishnendusengupta It is easier if you post in the appropriate forum; you posted in "General" and marked the product as "TX". It sounds like you have a Server job, though. The reject link from the transform stage shouldn't cause anything to hang - what is the passive stage that...

The problems look like they are coming from system file permissions; at least what you are seeing is typical of insufficient access to create, then R/W files. The fact that the view of jobs as "dsadm" is empty is probably because the cross reference file wasn't written correctly, and thus couldn't b...

I couldn't reproduce that here. Which "operator" is giving the error?

No. 1. You are opening up a local hashed file called "JobRunInfoParms". 2. You then try to open a sequential file, but instead of the giving path you are using the file handle from (1). This cannot work. The file is a hashed file or a sequential one, but not both. 3. Assuming you are reading the seq...

You are in a function, so all of your RETURN statements need to look like RETURN({some value}). You also have an exit statement in your loop that would get executed after the 1st read, and an unbalanced END in there as well.

Are you declaring your combine stage output schema or using RCP? I just created a test job with 3 columns and combined without any problems.

I'm confused as to your goal. The code does what you ask of it; but we don't know if it makes sense to do so.

Personally I would use a sequence to do this and not make one job abort depending upon some status in another.

If you call your script from the before-job subroutine then it will create the XYZ path before any of the job's stages try to access files.

Have you set up your sequence job so that the command stage is forced to execute before you start the job that needs the path? You need to do this.