Rules for customizing the messages

The general rule for customizing or translating messages is to change only the text portion of the message.

Do not change the MARGIN, PRODUCT, and COMPONENT definitions at the top of the data set. These are required definitions for the program. For example, these entries at the top of the MISC server message data set should not be changed:
```
MARGINS(1,72)
PRODUCT EZA
COMPONENT MSC
```
Do not change the message numbers and the severity code. These parts of the message have specific meaning; if you change them the program may not work correctly.
Do not change the conversion characters. These indicate that the program is passing data, the type of data it is passing, and the appropriate way to display or print this data. For example, do not change or delete %s and %d in the following message:
```
4059 I "Connecting to agent %s on DPI port %d\n"
```
You can reorder the variables that are passed in the message. For example, you can reverse the order of the two string variables that are passed when translating a message by specifying the new order of the arguments in parentheses following the message text:
Before: 9999 I "Command %s received from user %s\n"

After: 9999 I "Utilisador %s envio instrucion %s\n"(2, 1)

The result would be EZY9999I Utilisador MANNY envio instrucion FTP instead of EZY9999I Command FTP received from user MANNY.
Watch for any program parameters or keywords that might be in the message text. In most cases, you should not translate them.
For example, in the following message, 'active' is a keyword used in the gateway definition and should not be translated:
```
3974 E   "First two elements must be 'active' for active gateway\n"
```