Who's afraid of error messages?

See: http://jroller.com/page/ara_e/20040405#the_most_descriptive_error_message

The Most Descriptive Error Message Ever

Hereby I announce the winner of the most descriptive error message competition (encountered by Farzad):

"[ERROR] java.sql.SQLException: [PWS0001] Function did not complete successfully. Cause . . . . . : An error occurred while running the function which caused the function to end before it could be completed. Recovery . . . : Determine what caused the requested function to fail, correct the problem, and run the function again."

Reported by WebSphere on AS400 from a DB2 database. Viva IBM!

This is a from the i-Series messagefile QIWSMSG (IWS= Intelligent WorkStation):

Message ID . . . . . . . . . : PWS0001
Message file . . . . . . . . : QIWSMSG
Library . . . . . . . . . : QSYS2924

Message . . . . : Function did not complete successfully.
Cause . . . . . : An error occurred while running the function which caused
the function to end before it could be completed.
Recovery . . . : Determine what caused the requested function to fail,
correct the problem, and run the function again.

Message ID . . . . . . . . . : PWS0003

Message file . . . . . . . . : QIWSMSG
Library . . . . . . . . . : QSYS2924

Message . . . . : Problem occurred on the function, but the function
completed.
Cause . . . . . : A problem occurred while running the function, but was not
severe enough to cause the function to end. If data is to be returned for
the function, some data may not be returned.
Recovery . . . : Determine what caused the problem for the requested
function. If necessary, correct the problem, and run the function again.

Message ID . . . . . . . . . : PWS0005
Message file . . . . . . . . : QIWSMSG
Library . . . . . . . . . : QSYS2924

Message . . . . : Error occurred in the i5/OS database server code.
Cause . . . . . : An error occurred in the i5/OS database server code which
caused the function to not be completed.
Recovery . . . : Use F10 (if available) or the Display Joblog (DSPJOBLOG)
command to see the messages in the joblog for a more complete description of
what caused the error. If possible, correct the error. Try the function
again. If the error continues, contact your service representative.