DSXchange

Check your epoch setting. It may be defaulting (or have been set) to 2001-3000. Change it as required.

These functions appear under DS Function in the operand menu. DSJ.ME is a DS Constant, and can serve as the job handle for the current job. This is made clear in on-line help. All DS macros are predefined as calls to these functions with DSJ.ME as the job handle.

I present the IBM training classes in my part of the world, so can not offer an attendee's perspective. However, what I can say is that this class and the certification exam were written together so that ought to be sufficient reason to consider attending. Do check out the IBM course description to ...

All of these CAN be used in derivations, if DSJ.ME is used for the job handle argument. Most of them have associated macros.

Timestamp(38) is assuming something else about the data - namely that it's Unicode encoded. What happens if you specify Timestamp(19)?

Welcome aboard. These functions are documented in on-line help and in the DataStage BASIC manual. Fmt(InLink.TheString, "R%5") will handle the leading zeroes. You can handle the requirement to convert zero to spaces in one of a number of ways, but not really with a single Fmt() function. Maybe If In...

It is almost certain that the fastest solution will involve Oracle to Oracle utilities, and not use DataStage at all.

No, unless the export has already gone past that job. Otherwise the fact that you have the job (or any other object) open for editing means that it is locked, and will not be exported.

I'm surprised. On my system Int(1.50001) returned 1. This does not accord with the original requirement. Int() returns the largest integer smaller than the argument.

What do you mean by "special"? The Alpha and Num functions can isolate whether a string is alphabetic or numeric. The expression (Oconv(string,"MCP") = string) can report whether a character is printable. Some special characters live in particular code point ranges, for example "control set 0" compr...

Start by learning fundamental Bourne shell scripting, as these are the most portable, and used within the product itself to a large degree. The principles can then be extended to the other shell languages. Korn is an extension of Bourne, and bash is "Bourne again shell". Perl is a much more powerful...

The INT() function is not what you want. The FIX() function will be close. Use 0 for the mode argument to get correct arithmetic rounding.

It won't help me - I'm not doing the work.

The idea was to clarify your thoughts. Document precisely what needs to happen to these files, then choose your preferred mechanism for doing it (for example before-job subroutine, Execute Command activity in job sequence, etc.)

Does your machine have one CPU or two? Have you measured resource consumption on one instance of this job? Will the machine handle 36 times this demand? Your requirement to "run" the jobs may end up being "walk", "crawl" or even "refuse to go".

Set the Record Length property (in the Record level folder) to "fixed".
Make every string column Char rather than VarChar.