Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Evaluation of message texts

&pagelevel(4)&pagelevel

Where message catalogs are in use, a UTM application always searches for message texts in the following order once it has started:

Unix and Linux systems

  1. First an application searches in the filebase/nls/msg/lang directory for NLS message catalogs (possibly modified by the application operator) with the names utmsys.cat (for K and P messages) and utmxprog.cat (U messages). Here lang corresponds to the contents of the $LANG variable of the relevant user. If there is no lang directory under filebase/nls/msg, then lang is shortened to the language component of the $LANG variable and the resultant name is used as the current catalog name. For example, En_US.ASCII is shortened to En if no directory called ../En_US.ASCII is found.

  2. If there is no message catalog in directory filebase/nls/msg/lang, the application searches in the UTM directory utmpath under nls/msg/lang for a message catalog. In the case of an error the value of lang is reduced as above to the language component. This directory contains NLS message catalogs which can be used on a shared basis by all the applications on the computer, i.e. if a message catalog under this directory is modified, then this change will apply to all the applications on the computer.

  3. If the application cannot find a message catalog under utm-path/nls/msg/lang, the UTM application reverts to the linked standard message module or to an additionally linked application-specific message module.

Windows systems

  1. First of all, an application searches the directory filebase\nls\msg\lang for any NLS message catalogs modified by the application operator with the name utmsys.dll (for K and P messages) and utmxprog.dll (for U messages). Here, lang corresponds to the content of the %LANG% environment variables for the relevant user. If filebase\nls\msg does not include a lang directory, lang is shortened to the language component of the %LANG% environment variable and the resulting name is used as the current catalog name. For example, En_US.ASCII is shortened to En if there is no .\En_US.ASCII directory.

  2. If no message catalog exists in the directory filebase\nls\msg\lang, the application searches for a message catalog in the UTM directory utmpath under nls\msg\lang. In case of error, the value of lang is reduced to the language component as above. This directory contains NLS message catalogs that are used jointly for all applications on the computer, i.e. if a message catalog under this directory is modified, this change applies to all applications on the computer.

  3. If the application is unable to find a message catalog under utmpath\nls\msg\lang either, the UTM application falls back on the linked default message module or an additional application-specific message module.

Editing the messages

If there are no NLS catalogs (case 3.) or if there is no agreement between the value of the $LANG variable or the %LANG% environment variable and the existing NLS catalogs, the linked standard message module is used. Since the dialog terminal process edits the messages of the transaction monitor itself, each user has his or her "own message system". If, for example, a user has entered LANG=French and there are only English and German NLS catalogs in the system and no French NLS catalogs, the standard messages of the linked message module are output for this user. For all other users the messages are edited in accordance with the entries in the NLS catalogs.

Message output exceptions

When UTM messages are output during operation, openUTM takes the message text and the current message destinations from the standard message module. However, the following exceptions to this exist:

  • For some messages output by ROOT modules (e.g. for K078), English message texts are programmed in, and the output for these messages thus cannot be changed.

  • In the start and end handling of the tasks, for technical reasons openUTM cannot access the application’s message module. In these cases, openUTM takes the message text and the message destinations from the German message module.