SMC files must be encoded in UCS-2, ASCII, or UTF-8. See Naming SMC files, BMC files for a discussion of file naming conventions.
All messages should begin with "%s:" that represents the three-part header "Agent:Resource:EntryPoint" generated by the agent framework.
The HAD module must be specified in the header for custom agents. See Example SMC file.
The minor number of the version (for example, 2.x) can be modified each time a BMC is to be updated. The major number is only to be changed by VCS. The version number indicates to processes handling the messages which catalog is to be used. See Updating BMC Files.
In the SMC header, no space is permitted between the "#" and the "!" characters. Spaces can follow the "#" character and regular comments in the file. See the example above.
SMC filenames must use the extension: .smc.
A message should contain no more than six string format specifiers.
Message IDs must contain only numeric characters, not alphabetic characters. For example, 2001003A is invalid. Message IDs can range from 1 to 65535.
Message IDs within an SMC file must be in ascending order.
A message formatted to span across multiple lines must use the "\n" characters to break the line, not a hard carriage return. Line wrapping is permitted. See the examples that follow.
