DSXchange

True. The hashed file must either reside in the Project or you must manually create a VOC record for it, however, in order to leverage it via a UV stage.

Actually, aren't they all cataloged in upper case? DSU.EXECSH And I thought that prefix was reserved for User written routines.

In my job , source and target are oracle tables .source having portfoliodate column and its datatype is TIMESTAMP. for ex its value is 1998-01-31 00:00:00 . while conveting portfoliodate(Timestamp) into target date(dd-mon-yy) format I am using following Iconv,Oconv function. Your 'default' or NLS_D...

Umm... no. As noted, the Sequential stage will always create an empty file when it is 'opened' - it cannot be avoided.

If you don't want the file, check the file(s) for a zero size 'after job' and delete them if they are.

120267 wrote:But it should not be the case ,it has to wait for all the five jobs to finish and finally check for the status and act accordingly.

Define 'act accordingly'. That will help cut down on the speculation.

If by 'modify the key' you mean change one of the key field values... you can't. As you've found, it will just insert the 'modified key' record as a new record. You'll need to do two things. There's no way to delete records from a hashed file, so you'll need to update the 'old key' record to mark it...

Ok... but first try to help yourself. Get your hands on an .xsd of the target xml file. Import that using the Manager: Import / Table Definitions / XML Table Definitions. This will generate the XPath expressions you'll need to create your output file. Use them in your job. Let us know what happens o...

And there are ways to make it still work with that checkbox selected. Read the online help, it is detailed there.

Ok... one more time. This is a DataStage limitation, not a UNIX limitation. It is a known issue with the Folder stage. Open up a support case with Ascential, see if there is any work-around or perhaps a patch they can offer. I'm not aware of one, unfortunately, other than to process smaller files.

You must be calling this from a Routine Activity stage in a Sequence job, yes? Keep in mind the fact that a routine that does not return a zero is considered to have failed when you let the Sequence 'automatically handle activities that fail'. You need to explicitly handle the 'failure' in the job s...

the problem i dnt have help and software.. only way im learning buy using this forum. from start of job to end of jobs what are all activites runs in datastage. How many of these kinds of nebulous questions are you going to post here? I'm glad that others seem to have the time and are willing to at...

Grep for the appropriate 'phantom' processes. You'll see one phantom 'DSD.RUN' for the job itself and then one 'DSD.StageRun' process for each 'active' process in the job. As Ray notes, different settings and stage usage will affect the end result. Each transformer, for instance, could generate a se...

Or... run the job and see!

Why not just run it and see?

Tulip - rather than taking that approach, you will be much better off if you sort the incoming data in a manner that matches the grouping you are doing. Then ensure you tell the Aggregator stage that the data is coming in sorted. It will be much happier. You will be much happier. The job will run fa...