DSXchange

This topic has been raised several times before. You will need to download a patch from IBM/Ascential in order to fix this bug.

The simplest solution in your case is to set the commit size to 0. That way if the job aborts or is terminated during the run it will not commit the database modifications and write nothing. When you re-run that job it will start at the beginning.

Way to to, DSGuru2B!

Roy, you can debug the core file using DBX to see which program/where in it the fatal error was triggered. The options are different depending on your OS but it shouldn't take much work to get that information. The install shouldn't core out, but finding a project directory without a core is pretty ...

The document is for the CFF in DataStage Server, in this case it is the PX/EE Version and, according to the documentation, the variable OCCURS DEPENDING ON is supported. If you search the Parallel Job Developer's Guide page the keywords and the "ODO" short form you will see some examples.

Is your sequence not an integer?

You cannot call DSAttachJob() to your own process; it will hang at 7.5 for about 30 minutes and then fail. You should amend your code to check something like: MyJob = DSGetJobInfo(DSJ.ME,DSJ.JOBNAME) IF MyJob = ParameterJobNamePassedIn THEN Handle = DSJ.ME ELSE Handle = DSAttachJob(Param...

As the error suggests, the datatype is unsupported. You can specify a cast as varchar in your select if the data will fit into that datatype.

No, it will not have an impact on the DataStage job if you open it and do not change it.

Sequential files cannot be updated that way. The filter command won't assist you there.
You can code your own method by copying the sequential file record by record and making the changes you want and then deleting the original and renaming the copy to the original name.

The error, as balajisr has already pointed out, is not related to NLS but to your data and metadata; the error would happen even on non-NLS installations.
You can tell the sequential stage to ignore missing columns to get rid of these warnings, but only if this makes sense in your job design.

sb_akarmarkar wrote:Please make rest of column col1, col2,col3 and col4 as key column also in datastage column defination tab......

I'm not sure what you mean by this suggestion - it won't affect the actual DELETE command at all.

There should be more to the error than just the routine name, could you post that part as well?

I don't know where you found Ray's post stating that the COBOL "OCCURS DEPENDING ON" is not supported; but that is not the case, it is implemented and supported (albeit not well). The Parallel Job Developer's Guide has several examples. You can also use a hybrid solution by using a server job to pro...

Saik,

if the links on the front page don't work for you, try linking by clicking here