Chapter Contents |
Previous |
Next |
770 |
Updates to Library Message Processing |
In Chapter 9, "LSCX Run-time Messages," in the section titled, "Library Message Processing," replace the last paragraph and the list that follows it with the following text.
You can control the generation and verbosity of library diagnostic messages using any of the following:
quiet
function to suppress
these messages, as described in
SAS/C Library Reference, Volume 1
=warning
run-time option to
force library diagnostics to be displayed, even if suppressed by quiet
=btrace
run-time option to
get a list of the active functions (a traceback)
at the time a diagnostic is generated
=rsntrace
run-time option to
print information about recent failures in operating system calls with library
messages
wmi_add
function to define
one or more exit routines to control the printing of diagnostic messages.
Updates to Message Types |
In Chapter 9, "LSCX Run-time Messages," make the following changes in the section titled, "Message Types:"
LSCX[num] **** [severity] **** ERRNO = [errno value] [info added by message exit] Generated in function-name called from line line-number of function-name, offset hex-value [C++/Extended] name: full-name message-text Last failing system call: [name], return code [code], reason code [code], info [code] [info added by message exit] Interrupted while: context
Note that some of the text above will not appear for every message.
The C++/extended name
line appears only if
the error occurred in a C++ function or one with an extended name. The Last failing system call
line appears only if the =rsntrace
run-time option is in effect, and a system call
has failed since the last run-time diagnostic message. info
added by message exit
indicates optional text which could
be added by a library message exit (defined with the wmi_add
function).
Replace Message 025
with the following
message
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright © 2004 by SAS Institute Inc., Cary, NC, USA. All rights reserved.