DSXchange

Kernel parameters control the operating system and the resources that it can provide to applications. They may be stored in one file, they may be stored in several files - it depends on which kind of UNIX you're running. But however they're stored, you can be fairly certain that they're only accessi...

That's terribly one sided. Does your new senior have to do the same?
What's the stored procedure solution for Postgres DB?

On the server there's a directory called Quality in the project directory. The ruleset files are store in this directory. Therefore you need rwx permission to this directory for the agent process (usually given to the dstage group). If no rule sets have been provisioned this directory may not exist,...

blewip wrote:Run it sequentially

If the data get partitioned it won't do what you want.

False. If the data are partitioned properly it will do what is required.

Might be worth re-indexing your project repository.

Use type VarChar or set the length sufficiently longer.

I don't believe DataStage can do this. You might try using a sparse lookup (assuming you have a database that supports the same) with LIKE in the user-defined SQL.

Funnily enough, you can use the substring operator on the left hand side of an assignment statement to achieve exactly the same result. Even out of range position specifiers are handled. Ans = input_string Ans[start_position,length_str] = replace_string replace_string is truncated or right-padded wi...

It was unexpected. Is it repeatable? Have you tried re-starting all the services?

If the stored procedures don't already exist, then using DataStage would allow you to take advantage of Runtime Column Propagation and the change detection stages. You might be able to get away with one job to do the lot!

Do you need to use an in-band null or an out-of-band null?

Brave call.

Read the file as if it has one field.

Downstream of that in a Transformer stage, count the number of fields into a stage variable, possibly using the DCount() function. Base the constraint expressions on the two output links on that stage variable's value.

You could replace the angle bracket notation with a Field() function.

The System() function is not in the Repository - it is internal to the DataStage BASIC language itself. I assume, from other threads, that your premium membership is now operational again and that you can read the entirety of my earlier post. It does not require a routine at all, but shows an approa...