DSXchange

In the hashed file stage, under the create options.

Hashed files can be used with composite keys in DataStage server jobs. What DataStage will actually do (under the covers) is to combine the columns that comprise the composite key into one string and use that as the physical file key, but for all intents and purposes it works out to having multiple ...

Please look at the Parallel Job Developer's Guide page 1101 , in the chapter "Type Conversion Functions" or use the search facility in the bar above the response and search for this type of function. The question has been asked and answered many, many times before. This question does not belong in t...

I fixed it -8).

You need to check for the other possible return values, as documented in the routine. These are DSJE.NOTINSTAGE and/or DSJE.BADSTAGE (which happen to be error codes -7 and -8)

Andrew, that makes more sense; in that in a sequence you are running the jobs sequentially and not concurrently. If you program this in job control or elsewhere, issue a DSRunJob() and don't call the DSWaitForJob() then you have achieved your intended result. The DSDetachJob() call isn't necessary, ...

Where do you want to do this? The format you showed can only be done in SQL yet you assigned the result to what looks like a stage variable. If it is SQL then you need to convert your string to_date; if in DataStage you would need to explain exactly what you are trying to achieve.

Andrew, normally jobs, even instances of the same job, are run completely independantly of each other. I don't know how you could easily program concurrent runs of job.a and job.b to trigger an abort of the job.a when job.b aborts. How did you effect this? Could one job aborting set the database sta...

Look in the hashed file folder - there should be 3 files in it, a DATA.30, a OVER.30 and a hidden file .Type30.
The other other occurs when trying to create your output sequential file. Is drive "F" local or remote and does your userid have permissions to write/create files in that directory?

Yes, there is a known issue that requires a SP2 patch from your service provider.

Null - is a term that comes from databases and means an undefined value Space - one or more space characters Zero - numeric value of 0 or a string value with text representations of zero Empty - a string of length 0 Usually the Null and Empty values are confused and people mistakenly interchange them.

PAvan,

takes things step-by-step. Read the SAP data and write straight to a text file, keeping the same chines character set (are you 100% that the SAP source is in ZHS16CGB231280?). Is it correct?

Try putting a "dummy" transform stage between your source hashed file and your current lookup transform stage; just to see if the error remains or if it changes to the new transfrom stage.

Make you job multiple instance and in your code change line hJob1 = DSAttachJob("Untitled1", DSJ.ERRFATAL) to hJob1 = DSAttachJob("Untitled1.":i, DSJ.ERRFATAL) in order to fire off multiple instances with distinct names. You will somehow have to differentiate the ...

What are the input and output links to this transformer going to? The error is an odd one to get - is this a new job or one that used to work?