DSXchange

No, I suspect you are populating Ans each time through the loop, and that the last line in the file is empty.

Try this.
Replace with Where does Name come from?

Tools > Customize is only about being able to add extra commands to the Tools menu. For example I can start DS Administrator from there, or Notepad.

In short, it works as documented.

Why, if you've "handed it over"? Doesn't it become their problem?

If it has to be integer, then you need to strip out the ".". The leading zeroes are not a problem.

That'll do it. There is an explicit warning about special characters in passwords (including how to avoid problems when they're used by mapping to a special sequence such as __036__) in the documentation.

Two points.

OPENSEQ has four possible clauses. The ON ERROR clause is taken in the event of system error, and the LOCKED clause is taken in the event that the file is open by another process.

You need a REPEAT statement to terminate your uncounted loop.

Add ExecDOS as a before-job or after-job subroutine and execute any Windows command that will identify the user (such as echo %USER%).

Join stage needs sorted inputs for efficiency. With sorted inputs it only needs to deal with a single key value at a time. Depending on your settings, if you don't sort your data DataStage will insert a tsort operator so that they are sorted (you can see this in the score). Lookup can't do right out...

Something clever in sed or awk, or a simple job/routine to parse the entire line, or abandonment of the requirement that everything has to be generic and RCP driven.

Get yourself a premium membership.

At less than 30c (Rs12) per day it's not expensive, and the revenue is devoted to the hosting and bandwidth costs incurred by DSXchange. So you're helping to keep the site alive.

Any reason you're not using the bulk loader?

It may not look correct, but it IS correct.

Check the classification of PVT. (It doesn't occur in USNAME out of the box, but PTY is classified as W.)

Build the target table name as a constant (perhaps using a Column Generator stage or a Transformer stage) upstream of the Lookup stage.

A generic approach might use a job parameter for the target table name.

They may be unnecessary (to you) but they're not wrong. What exactly is the problem?

DataStage puts them there driven by the precision and scale settings of the Decimal field.