| Title: | -={ H A C K E R S }=- |
| Notice: | Write locked - see NOTED::HACKERS |
| Moderator: | DIEHRD::MORRIS |
| Created: | Thu Feb 20 1986 |
| Last Modified: | Mon Aug 03 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 680 |
| Total number of notes: | 5456 |
Yesterday I had the need to get the error message number and NOT
the descriptive text. (I suspected a message file mismatch, and
a number is so much easier to spell over the phone then a text)
The sollution was easy: Used assign SYS$MESSAGE to someting that
is not valid. Run the program "et voila;" NOMSG #####.
The customer spelled out the number, I feed it back into the
mesage facility and the result is the EXACT error text in a file!
Perhaps useful to others as well, or am i sick in the head?
Hein.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 208.1 | Going the other way? | GUMDRP::NIKOPOULOS | Steve Nikopoulos | Fri Feb 21 1986 14:52 | 7 |
What I have wanted to do at times is take the message text and get
the message number that generates that text. Is there a way to do
that?
-Steve
| |||||
| 208.2 | I _thought_ that's what i dit. | RICARD::HEIN | Hein van den Heuvel, Valbonne. | Fri Feb 21 1986 15:04 | 11 |
re .1:
Well, that is more or les what i needed when I wrote .0
I was in the lucky circumstance to be able to run a progam
to reproduce the error (while F&*&ing up sys$message).
Occasionall I have been seen running a litle DCL procedure
that sit's in a loop incrementing an error number and
examining f$mess(x) until the right message walks by.
Having a list of starting error number for the various
facilities was hand in this process.
Hein.
| |||||
| 208.3 | Ooops | GUMDRP::NIKOPOULOS | Steve Nikopoulos | Sat Feb 22 1986 13:34 | 2 |
You're right, I didn't read .0 closely enough.
| |||||