DSXchange

They need to be educated out of this practice using minimum necessary force.

Most message IDs can be found in a table called SYS.MESSAGE. Note that this has six-character keys (for example '081002' rather than '81002').

The others have to be looked up in manuals. They exist in various header files, but there's no convenient API for decoding them.

Do you want the summary without line breaks, or do you want the detail? To get the detail of any particular event, you need DSGetLogEvent(). To use this you will need the event number. The usual way to get the event number is to use DSGetNewestLogId(). Probably easiest is to get the absolutely last ...

Welcome aboard! :D First, why not search the forum? There's a Search option in the menu at the top of the page. Then qualify your question: are you interested, for example, in unit testing, end-to-end testing, integration testing, regression testing, performance testing, testing against specificatio...

In short, no.

DataStage roles are associated with operating system groups, not with operating system user IDs - but there is no practical limit to the number of groups on the operating system nor to the number of groups to which a user can belong.

No.

All you can do is to export from Windows with defaulted properties (just in case), then do a search and replace on the DSX/XML file before importing into UNIX.

Not easy. You get separate output row for each row coming in from the reference input link.

If all you want is the count, specify user-defined SQL that returns the count for those search key values.

What kinda UNIX is XP? Xewlett-Packard?

You need to find out what character is being used as a line terminator - it's probably one of Char(10), @FM, @VM or @TM. Simply convert these to space.

If you have a support contract, you will know how to obtain support. Your support provider may not be the vendor; it may be a reseller, in which case the vendor will insist that you work through your actual support provider. It follows that, if we were to give you contact details for a support provi...

Someone killed the process with kill -9

You're not viewing with a hex editor, or you're not showing us the hex representation (which should be eight bytes long).

As to your question, you did not read my prior response very well:

string_from_decimal (in a Modify stage)

Every job log is a separate table. You can't easily do it with SQL. Create yourself a Routine to do it. Loop through all the job names and find the corresponding job number from DS_JOBS, then count the records in RT_LOGnnn where nnn is the job number. Generate your report as you go.

So?

UniVerse (DataStage Engine) is a database, and hashed files are how that particular database implements its tables. Row-level locks are still taken.

If you populate it with a UV stage, the lock is promoted to table-level once a configurable threshold (MAXRLOCK) is reached.

You will best be able to perform this with an after-job subroutine (so that you don't interfere with the run-time performance of the job) using DSGetLinkInfo function.

After-job subroutines are written in DataStage BASIC.