DSXchange

Would I be right in saying that LIST.LOCKS never shows any locks held? That's because - unless you've chosen to use them within your own routines - task synchronization locks are not used by DataStage. All user locks used by DataStage processes and clients can be viewed with LIST.READU EVERY. In mos...

FIX( number [,precision [,mode]] ) does indeed exist.

Find it in the DataStage BASIC reference guide.

precision is the number of decimal places.
mode is 0 to round, 1 to truncate.

Yes, because it re-reads the configuration file that specifies that MetaStage proxy mode is enabled, and checks that the listener process is started.

Every developer I mentor gets the following advice. Include conditionally compiled statements for test. * Change this to $UNDEFINE when compiling for production. $DEFINE TESTING This sets up a token that can be tested by the compiler. $IFDEF TESTING statements $ENDIF The statements between the $IFDE...

A lot of the lines are comments, or declarations. There are relatively few lines of actual processing code, unless you have lots of job parameters (the job sequence actually checks to see that they were actually set, a common deficiency in human-written code).

Actually, being connected will not prevent an export; it's only when they have objects open for editing that that object is skipped by the export process. It is sufficient, therefore, to check for locked design objects (though safer not to have any user connected). You can determine both using the c...

LIST.LOCKS is not the appropriate command; this shows task synchronization locks, which are not used by DataStage. LIST.FILE.STATS will be singularly unhelpful unless the statistics have first been gathered using ACCOUNT.FILE.STATS. As you can discern, there is much to learn, and much of which you s...

There is a C-callable API (called DSAPI) documented in both the Server Job Developer's Guide and the Parallel Job Developer's Guide . While there is no explicit Java API, or set of classes, I'm sure you could make use of the DSAPI from Java. But it won't make your work easier. Instead of leveraging ...

Umm... only run it on the occasions when it runs in three seconds? Check the log file and compare the job start and finish times with the active stage start and finish times. This will isolate the problem better. When you run the job from Director, switch to the Tracing tab. Select the Transformer s...

You can find it in the DataStage BASIC manual. It is a valid function: though your expression remains red it will compile and run successfully. If you want to switch off the red colour, which only signifies that the expression editor does not recognize the function name, edit the file called DSParam...

If you want delimiters, you have to concatenate them in, too. HR : ":" : MIN : ":" : SEC : " " : AM_PM_Flag Or, if you can be certain that each component is two characters long, you can concatenate first and format later. Fmt(HR:MIN:SEC:AM_PM_Flag, "R##:##:## #...

Use the SADD function rather than the arithmetic operator "+". By doing so you will suffer no loss of precision in integer arithmetic.

BTW, the configuration parameter to which leomauer is referring is actually called EXACTNUMERIC.

You can get around the problem of redimensioning in COMMON (which is prohibited) by using a dynamic array (or, in your case, a pair of them, one for the lower bound, one for the upper bound). I have used this technique in the past, and it is (used to be?) taught on the Programming with DataStage BAS...

All job types are accessed, and modified, by the one set of DataStage clients. The clients determine from the repository what job types you can create which, in turn, is determined by what version of DataStage server engine you have installed (server, EE or EE/MVS). All engines can create server job...

The staff at DSXChange forward all requests to Ascential. I am not sure what happens after that. There's also an enhancements wish list at Ascential Developer Net as well as which you are perfectly entitled to submit enhancement requests through your support provider. Finally, if you have a local us...