DSXchange

Your original question specified a character string. Data type sizes are all specified precisely in Chapter 2 of the Parallel Job Developer's Guide.

Less traffic on the network between engine and client tiers.
More powerful server for engine tier.
Fewer columns in design.

You could use a User Variables activity. This is accessible anywhere downstream of itself.

The project is a DataStage project, which means that it's also an account name and a schema name and probably recorded in myriad locations in XMETA and maybe even XMETASR if you're using version 8.7. Probably easiest is create a new, empty DataStage project, export everything from ANALYZERPROJECT, i...

But, if you can find out what they are, you can convert them.

Another thought.

Is there a separate steward allocated to each project, and therefore to all of the terms originating from that project? If so you might use Steward as the differentiating factor.

That's why I recommended custom attribute. Labels are pure text, nothing else. That can not, as you have determined, be allocated during import of terms, only subsequently. Custom attributes can be imported if you are using an XML import format. Both custom attributes and labels can be used to filte...

No it's a salvo from someone with experience and knowledge of typography. You can only experiment. The small square is not really there; it's how your viewer tool displays the character. What you need to do is to find another viewer with hex dump capability (for example UltraEdit) and figure out exa...

I'd create a custom attribute called Project and provide it with a list of values such as HR, Finance, Healthcare.

You can filter on custom attributes when searching for terms.

Why not just have DataStage collect operational metadata automatically?

If you're on version 8.7 or later, you can use the Operations Console to keep a history and watch trends.

Engine credentials are a totally separate issue. You have not configured credentials in the services tier for the DataStage engine in question, at least not for that particular user.

After job subroutine would be my preferred mechanism. That way you can use DSJ.ME as the job handle. The only downside is you have to fake the "job finished" message based on DSJ.JOBINTERIMSTATUS.

It has nothing to do with the selected typeface. It has to do with the way that the characters are encoded, for example ASCII, UTF-8, ISO8859-1 or some other.

Pet peeve: Microsoft have foisted this improper use of "font" meaning "typeface" upon the world. Resist it.

What was the status before you ran the sequence? If it was Restartable, then any checkpointed activities will be skipped. You can reset or recompile the sequence to force all activities to be executed; this - among other things - clears the checkpoint record.