DSXchange

Depending on your version, Common Metadata Administrator or Common Metadata Importer.

Then use the first of the solutions that I offered.

Let's be clear about what you mean by "alphanumeric". In the industry this term is commonly understood to include alphabetic characters (letters) and numeric characters (digits). I suspect that's not what you mean in this case. A generic solution to preserve alphanumeric characters (as con...

Well, no, prepending a non-numeric to each string will force a string comparison to occur, as per your example.
But I think the Compare() function is better self-documenting.

In parallel Transformer stage, use MonthDayFromDate() to determine the day number for your range check. Use DateFromDaysSince() and that value to calculate the date of the first day of the current month or the last day of the previous month.

Transforms are available in BASIC Transformer stage.

You need to use BASIC Transformer stage if you want to use Iconv() or Oconv() functions.

They are simply not available in the parallel Transformer stage, and never will be.

From version 9.1 DataStage no longer uses MKS. It uses native Windows system calls.

Can't see why not.

This thread (final post) explains what (Auto) uses.

There is no global solution. DataStage server jobs inherently do not have data types. Context determines how comparisons are done (numeric or string, right- or left-justified). If both operands are numeric, a numeric comparison is performed. There IS a string comparison function (Compare( string1,st...

There is a limit of 2GiB on the size of the RT_LOGnnn hashed files. Any attempt to exceed that will corrupt the hashed file (generating a backward link (BLINK) error). If you believe that you need more than 2GiB of log events, you can use RESIZE to change that particular RT_LOGnnn to 64-bit addressi...

What error are you getting?

Or are we supposed to guess?

Check your documentation to verify whether or not File Pattern is supported, and consider the implications if it is. Every single one of the worksheets would necessarily have to have the same organization. Do yours fit this requirement? File Name should be able to be a job parameter (if not, "t...

All UV tables are hashed files.

Not all hashed files are UV tables. However every hashed file with a consistent record structure can be read as if it were a UV table.

VOC and DS_JOBOBJECTS are examples of hashed files that do not have consistent record structure.