DSXchange

Chester has claimed that a call from Instance2 causes Instance1 to abort. It shouldn't. I am awaiting his design and code to be posted.

From memory (I don't have access to DataStage at the moment - I DO do other things!), the AsInteger() function would come close. Or, if it exists, something like Int32_from_Decimal() in a Modify stage.

Please note that BASIC-based techniques can not be use in a parallel job in an MPP (cluster) environment - only in an SMP (share everything) environment. That said, however, you can use job sequences (which are BASIC-based) in either environment; however, these can operate only on the conductor node...

True, it was introduced in version 7.x, so you need to interrogate tha job status after the job has completed successfully. Typically this will be from the job control routine from which you requested execution of the job run. Or upgrade.

SYS_ just means that whoever created the constraint was too lazy or indifferent (apathetic?) to give the constraint a name. This makes the database that little bit less easy to maintain, imho. In mitigation, it is also true that not every database allows NOT NULL constraints to be named.

Where are you executing this code? If - as seems to be the case - you're executing it from within a routine - even an after-job routine - the status of the job will always - necessarily - be 0 ("running"). You can, in an after-job subroutine, use the "interim status" argument to DSGetJobInfo. Resear...

Post your code and an outline of your job design (CopyOfCopyOfCopyOf... ?!!)

Not in all databases. UniVerse, for example, differentiates NOT NULL, NOT EMPTY, UNIQUE, ROWUNIQUE (for multi-valued data), CHECK and FOREIGN KEY constraints. Technically (SQL standards) a CHECK constraint is one where an SQL expression is satisfied by the row. I guess "column IS NOT NULL" could be ...

If you're on 7.5 you can derive output columns in a Lookup stage. However I don't think it's quite flexible enough to do what you require. I think you'll need to follow it with a Transformer or Switch stage. A Transformer stage offers the advantage of having stage variables available.

Sequencer_5 is an "All" sequencer, yet all its inputs can never be true simultaneously. A job can not, at the same time, have three different exit status values.

You can use job control code.
Create a job sequence with a Job activity set to "reset if required then run", compile it, and examine the generated job control code.

Modify the SQL so that data aren't truncated. For example use a SUBSTRING function on the SELECT clause.

However, the OP stated that this time it's a CHECK constraint. Get help from your DBA - there is a system table recording all constraints that you can use to determine the constraint rule and the table on which it is applied.

FILELOCK supports an optional LOCKED clause to handle the situation that a file lock can not be obtained. If there is no LOCKED clause, the application waits indefinitely until the block is released. Research the FILELOCK statement in the DataStage BASIC manual. But, as Kim said, you don't need to l...