HP-UX SNAplus2 Upgrade Guide (June 2003)

Porting Application Programs
CSV
Chapter 338
CSV
If the application uses either of the verbs LOG_MESSAGE or , see
“LOG_MESSAGE” or “TRANSFER_MS_DATA”
If the applicationdoes not use the LOG_MESSAGE verb, and you are not
making changes to the application's source code, no action is necessary;
the application can run unchanged with the new shared libraries.
LOG_MESSAGE
This verb has been modified from the version in SNAplus to work with
the style of message logging introduced in SNAplus2 Release 5. Refer to
the description of this verb in the HP-UX SNAplus2 CSV Programmers
Guide for information.
Applications can no longer log messages from the system message file. If
your application logs messages from the system message file, you need to
create a new user-defined message file, and modify the application to
specify this file instead of the system message file.
The source file format for user-defined message files and the program
used to build the message file from the source file have been changed. If
your application logs messages from a user-defined message file, you
need to create a new source file and build a new message file from it; this
file can then be used without changes to the application's source code.
For more information about the new file format and on how to build the
new message file, refer to the description of LOG_MESSAGE in the
HP-UX SNAplus2 CSV Programmers Guide.
In addition, note the following changes to the action of the
LOG_MESSAGE verb:
• The msg_act parameter now defines the log message type (problem,
exception, or audit) used in Release 6, rather than the log message
level that was used in SNAplus. The SNAplus2 CSV library
continues to accept the old values for this parameter, and maps them
to the new log message types as listed below. If this mapping does not
correspond to the appropriate message type for your log messages,
you should modify the source code to specify the new message type
values.