Is there public documentation of error numbers?

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Many of the error numbers are in a hashed file called SYS.MESSAGE, so that you could open the Command window from Administrator (for example) and execute the query:
SELECT MESSAGE FROM SYS.MESSAGE WHERE @ID = '081016';

Note that @ID is not a numeric type - some codes are non-numeric. Those that are numeric are six characters long (compliance with some POSIX standard).

Or, using the RetrieVe query language:
LIST SYS.MESSAGE '081016'

However, 031017 is one of those that appears not to be in the SYS.MESSAGE hashed file.

The next best source of error messages, in my opinion, is the "Intercall Developer's Guide" (http://www-3.ibm.com/software/data/u2/p ... trcall.pdf).
Intercall is the architecture on which the communication protocol between DataStage clients and server is built. In this manual you will determine that code 30107 is decoded as "subroutine failed to complete successfully". Oh, well, at least you now know where to look! The client's do a reasonable job of decoding for you.

Other UniVerse manuals do contain error codes that are not in the Intercall manual, but it's rare that I need to refer to these. They can all be had from http://www-3.ibm.com/software/data/u2/p ... index.html

The subroutine in question is *DataStage*DSR.ADMIN, one of the helper subroutines on the server that perform the tasks requested by the DataStage clients. The most usual reason for this message is that one of the inactivity timeouts for the connection has expired.

From the DSR_UVCONST.H header file (in DSINCLUDE) you can determine that action 2 for this subroutine is "read", so that the problem was not actually a write, but a read (probably a read for update prior to the write).
Post Reply