HP-UX SNAplus2 Upgrade Guide (June 2003)

Porting Application Programs
CSV
Chapter 3 39
• The msg_act parameter no longer defines whether the message is
displayed on the system console; this information is now defined in
the message file. You do not need to modify the application's source
code because this parameter is ignored in Release 6.0 or 6.1, but
ensure that the new message file specifies whether a message is a
problem, exception, or audit.
• If the msg_act parameter corresponds to an audit or exception
message, the message is logged only if the SNAplus2 configuration
specifies that the appropriate type of logging is enabled. If it is not
enabled, the verb still receives an OK return code but the message is
not written to the log file. For example, if msg_act specifies
SV_NO_INTRV_8 (which corresponds to an audit log) but audit logging
is not enabled, the message is not logged. (In SNAplus, a message
would be written to the log file even if it was at an audit log level that
was not currently enabled.)
TRANSFER_MS_DATA
In SNAplus2 Release 6.0 or 6.1, this verb is provided as part of the MS
API and not the CSV API.
If you are not making modifications to the application's source code, no
action is required as the application is still able to access
TRANSFER_MS_DATA from within the CSV library.
In future versions of SNAplus2, TRANSFER_MS_DATA will be
supported only in the MS library and not in the CSV library.
Table 3-1
Release 4 values Release 6 value
Release 6
message type
SV_INTRV, SV_INTRV_16,
SV_NO_INTRV_16
SV_PROBLEM Problem message
SV_NO_INTRV,
SV_NO_INTRV_10
SV_EXCEPTION Exception
message
SV_NO_INTRV_8,
SV_NO_INTRV_6
SV_AUDIT Audit message