Thread View: vmsnet.internals
2 messages
2 total messages
Started by Jaime C. Jansenwirth
Tue, 29 Dec 1992 16:17
Use of $PUTMSG system service
Author: Jaime C. Jansenwirth
Date: Tue, 29 Dec 1992 16:17
Date: Tue, 29 Dec 1992 16:17
39 lines
1936 bytes
1936 bytes
Hi, everybody!
I am a novice in MACRO32 programming and I have a little doubt:
I have created a message definition file (.MSG) that I have compiled and
linked with a compiled MACRO32 source. Some messages in that file have FAO
arguments, so that I want to know is how can I print to SYS$OUTPUT one of
these messages from my MACRO32 program using the $PUTMSG system service
(passing before the appropiate FAO arguments to the message, that is really
my problem). I want that the result will be a normal VMS message with the
identification, severity, facility and text parts.
I know that is an easy way to print a message with LIB$SIGNAL, but I do
not want to print the symbolic stack traceback each time an error occurs.
Could somebody help me?
Thanks in advance.
Please e-mail me direct
***** I wish you a Happy New Year 1993 ! *****
P.S.: Please excuse me if my english is not too good but I hope that you
can understand me ! :-)
---------------------------------------------------------------------------
Jaime C. Jansenwirth
* local DECNET: 16509::DIP115 (16509=EUIBVX)
* *
* * Internet: dip115@cc.uib.es
* U I B *
* *
* * Universitat de les Illes Balears
* Universidad de las Islas Baleares
University of the Balearic Islands
Palma, Mallorca
Spain
---------------------------------------------------------------------------
Re: Use of $PUTMSG system service
Author: Dave Pampreen
Date: Thu, 31 Dec 1992 18:54
Date: Thu, 31 Dec 1992 18:54
20 lines
1358 bytes
1358 bytes
In article Jaime C. Jansenwirth <dip115@cc.uib.es> writes: > Hi, everybody! [stuff deleted] > I know that is an easy way to print a message with LIB$SIGNAL, but I do >not want to print the symbolic stack traceback each time an error occurs. > >***** I wish you a Happy New Year 1993 ! ***** > Happy new year to you too. If you don't want the trace back information to be displayed, when you compile and link it, don't use the traceback feature. I do believe this is what you want to do: $ macro/debug=notraceback [your.dir]your.file $ link/notrace [your.dir]your.obj Then you will not see any traceback info. Dave Pampreen - Supervising Consultant - Goddard Lab Learning Technologies. Eastern Michigan University - pampreen@emunix.emich.edu
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads