How Pre-VCS 4.0 Messages are Displayed by VCS 4.0 and Later

In the following examples, a message written in a VCS 3.5 agent is shown as it would appear in VCS 3.5 and as it appears in VCS 4.0 and later. Note that when messages from pre-VCS 4.0 agents are displayed by VCS 4.0 or later, a category ID of 10000 is included in the unique message identifier portion of the message. The category ID was introduced with VCS 4.0.

• Pre-VCS 4.0 message output:

TAG_B 2003/12/08 15:42:30 VCS:141549:Mount:nj_batches:monitor:Mount resource will not go online because FsckOpt is incomplete
• Pre-VCS 4.0 message displayed by VCS 4.0 and later

2003/12/15 12:39:32 VCS ERROR V-16-10000-141549 Mount:nj_batches:monitor:Mount resource will not go online because FsckOpt is incomplete

Comparing Pre-VCS 4.0 APIs and VCS 4.0 Logging Macros

The topic Logging Agent Messages describes how to use the VCS 4.0 logging macros for C++ agents and script-based agents.

For the purpose of comparison, the examples that follow show a pair of messages in C++ that are formatted using the pre-VCS 4.0 API and the VCS 4.0 macros.

• Pre-VCS 4.0 APIs:

sprintf(msg,
"VCS:140003:FileOnOff:%s:online:The value for PathName attribute is not specified", res_name);
   VCSAgLogI18NMsg(TAG_C, msg, 140003,
     res_name, NULL, NULL, NULL, LOG_DEFAULT);
   VCSAgLogI18NConsoleMsg(TAG_C, msg, 140003, res_name,
     NULL,NULL,NULL,LOG_DEFAULT);
• VCS 4.0 macros:

VCSAG_LOG_MSG(VCS_WARNING, 14003, VCS_DEFAULT_FLAGS,
   "The value for PathName attribute is not specified");
VCSAG_CONSOLE_LOG_MSG(VCS_WARNING, 14003, VCS_DEFAULT_FLAGS,
   "The value for PathName attribute is not specified");