DSXchange

If these are ISD jobs, surely you should be looking in the Console?

You could use a BASIC Transformer stage and there employ the Oconv() function with "MX0C" as its second argument. I don't believe there's an out-of-the-box function in the parallel Transformer, but there's nothing to stop you writing your own. Traverse the string from right to left multipl...

Trim() function will reduce the multiples to singles.

Substring replacement can be done with the pxEreplace() function posted on DSXchange by DSGuru2B some time back. You can search for it.

When DataStage ingests a string containing line terminator characters it converts them into field marks (this allows DataStage to be operating system agnostic). The field mark character is available through the @FM system variable - its value in hex is 0xFE.

You really do need to specify more exactly and more completely what the mapping rules are here. Do it in English, not in pseudo-code.

Use a Modify stage and lookup_string_from_int16() function.

or

Use a Lookup stage sourced from a file containing the mappings (or even from an External Source stage containing 12 echo commands).

Probably the Null Field Value property is set to "all spaces".

No idea what the purpose might be - it seems to me to be a silly design.

Two outputs from Transformer stage combined in a downstream Funnel stage.

When you create a server routine one of the first things you do is to specify its routine type on the General tab.

Wouldn't a User Variables stage have been easier?

There's no such thing as a Pivot license. Your DataStage does have a Pivot stage and may, indeed, have a PXPivot state too.

That looks like a Julian date of some kind. Can you please provide more details about the source and how that was generated?

What do the numbers look like? Do you regards 20110125 as a number?

I'd advocate 60 meaningfully-named stage variables, then monitor the stage to determine its resource consumption. If that's less than 100%, leave it alone. Otherwise break it into two and monitor again. Repeat until no process is demanding more than 100% of one CPU.