DSXchange

Neither is quicker. It's a matter of time shifting, about where you choose to perform compilation.

Your question is too broad. What kind of source?

Technically sequential files don't have data types and therefore can't have nulls. But we often pretend that they have data types, and therefore must specify how null is represented. This is typically managed through the Null Field Value property.

Never kill DataStage processes from the command line.

Try closing the Director and Designer clients. That may force a release. You may need to open Web Console for Information Server to disconnect a (client) session that might be holding a lock in the repository.

Locking in the target database?

The one that jumps to mind is to do it in decimal - subtract the next higher power of 2 from the absolute value of the original number then convert to binary. It would probably be easy to create an AddBit function. FUNCTION AddBit(BinaryString) Begin Case Case UnAssigned(BinaryString) Or IsNull(Bina...

My preferred technique is to have a server job read the value and store the value in the job's user status area. This can be accessed as the Job activity's $UserStatus activity variable.

It's not really "add one" though, is it? It's more "set the sign bit". This can readily be done with string manipulation.

I had problems with MOD() on numbers over a certain size and I didn't see a need to bump up the EXACTNUMERIC value so I wrote an "SMOD" routine that used the string math functions I mentioned earlier to do a proper mod on any big ass number. Worked fine for me. Would you describe these, t...

DataStage isn't really the limiting factor here - the length of a list to which a wildcard pattern can be expanded (an operating system) is. If that becomes an issue, consider using a loop in a sequence.

It has since occurred to me that, because it's in IBM's manual, they would have to support it.

And it IS used in the product itself. Any job sequence will have calls to *DSR*Message, for example.

Nothing at all.

Afterwards, however, you will need to be careful not to start too many jobs at the same time - parallel jobs generate rather more processes than server jobs do.

Welcome aboard.

Why not just use a pattern to have a Sequential File stage read all the files directly?

I believe that that is correct in this case.

source.NULL will not even attempt the lookup, and will record it as failed. Use a conditional lookup and make your condition something like IsNotNull(source.columnname)