DSXchange

It looks like you specified "binary" for the decimal output field in your column attributes.

If you create a minimalistic template sequence, how many changes would each one need? If they are simple, you could write a small program to make those changes on an exported copy (.dsx or .xml as you prefer) that would include renaming the sequence and then importing that changed version.

The Job control code is autogenerated but written in DS/Basic. Are the jobs similar enough that you could just write one generic job and pass everything in as parameters, including your SQL?

this might be a bit out of the scope of normal DataStage, but the backbone of the Server engine is the DS/BASIC language on top of what used to be the UniVerse DB. This language should allow you to generate the programs in question. It is more of a matter of defining what needs to be done and what i...

add the command "ulimit -a" as a before-job shell call, then see what your open files limit is displayed as at runtime.

Use stage variables to store the distinct column headers from the first row, i.e. SvarCol2 is "IF NOT(In.Col2) THEN In.Col2 ELSE SvarCol2". Then derive your output columns from the data and your stage variables. Manually add a line terminator after the column value and write to a sequentia...

Do you have NLS enabled - 0xA0 is a small a egu character and is, I think, a printable character but you would have to check your NLS.LC.TYPE file (I think that was the name), or just write a 1-line BASIC routine that returns LEN(OCONV(SEQ(160),'MCP')).

As part of the deletion process, DataStage renames the actual data files linked to by the descriptor to "...being_deleted", and then actually removes them at a later part of the delete. This usually only takes milliseconds but for same reason the last attempt was unsuccessful in removing t...

Craig's suggestion should to the trick.

If the routine generates warnings then it contains calls to DSLogWarn() which you can modify to just call DSLogInfo(). I would hesitate to recommend doing that unless you are certain that the warning are unavoidable and won't affect your job run.

The prefix of "." and a space before the "./dsenv" script call is very important, otherwise the script is executed in a different shell and the values set are lost; that seems to be happening in your case.

babuselvan, looking at your posts over the past few days they are all 1 liners whose answers are to be found either directly in the documentation or are general ETL questions that can be googled... This really looks like you are looking for answers to interview questions. Have you read the Parallel ...

The issue might be urgent for you, but not to DSXchange. Ray puts it into a much nicer wording than I do. "Binary" just means non-ascii unless you specify what format it is in. Without knowing what format it is, no conversion is possible. But my first guess is that you are looking at more ...

My point is that if the data is already partially sorted coming then writing to a dataset will lose that "work", so in that case another storage method should be used.

The 0x90 character is not mapped as part of standard EBCDIC, but is present in some variations. I don't know exactly which version is in use on your AS/400 system, but if you get that information and use that character map in APT_EBCDIC_VERSION the degree sign (and possibly other extended characters...