DSXchange

There's a Favorites piece in the Palette where you can put those stage types you use regularly use. It's a great aid to productivity. :D

Left(Convert(" ", "", TheString), 19) will remove ALL space characters then return the leftmost 19 (or fewer) characters of the result. If you want to guarantee exactly 19 characters, prefer Fmt() to Left(). Fmt(Convert(" ", "", TheStr...

If deadline's really an issue, hire a consultant for a couple of hours, and be mentored as the design comes together.

The ORABULK stage was created as an active stage type which, among other things, means that it supports the concept of an after-stage subroutine. You can set this up to invoke ExecSH, and put your entire sqlldr command line into the Input Value field. Or you could invoke a shell script (using the sa...

* Has the unusual habit of not aborting the job when the db2 load fails, just a warning. I have no idea why they built it this way. It is one of my personal standards that nothing ever aborts. Nothing even generates a warning unless something needs to be warned about, in which case it is picked up ...

That's all fine. You can get the leftmost 19 characters with the Left() function or substring For example TheString[1,19] You can trim redundant (multiple) space using Trim(). You can remove space characters using Convert(). For example Convert(" ", "", TheString) You can...

Look at the file using a hex editor of some kind (such as the UNIX command od -x) to determine exactly what the delimiter characters are. Then you're off and running. Until the AS/400 types change their program!

Determining whether there is a control character (the second requirement) is the same logic you already have. Counting how may you will need a routine. If you're not using NLS, something like the following. FUNCTION CountControlChars(TheString) Ans = 0 * Control characters are outside the AS...

dsrfcd is the daemon for communicating with SAP's RFC mechanism. I don't presently have access to a system from which I can get the answer. Is there a dsrfcd.config file (or something similar) in which the port number is mentioned? Otherwise, check the manual for the SAP R/3 or SAP BW stage, depend...

If the hashed file was created in a directory, rather than an account, then DELETE.FILE will not work; you'll need rm (UNIX) or del (Windows). If the hashed file was created with a UV stage, then DELETE.FILE will not work; you'll need DROP TABLE. If it was someone else who created the hashed file, t...

If inlink.colname <> Oconv(inlink.colname,"MCP")
Then you have a non-printing character
Else you don't have a non-printing character

There is a Lookup stage for Parallel jobs.
There is an entirely different Lookup stage for Mainframe jobs.
To get either you must have purchased the relevant edition.

The Pivot stage does not do any transformations.
It's easiest to follow the Pivot stage with a Transformer stage. That's where you'd use the stage variable.

No, it should be there automatically.
In the Repository browser (tree view) open the Parallel branch. Under there you should see a Processing category. Expand that and you should find it.

That's exactly what the Reporting Assistant is for.

Push your metadata, including job designs, into another place (by default Doc_Tool.mdb) and they can take it away and research it to their hearts' content. Ideally not in billable time.