DB2 Server for VM: System Administration

Defining Message Repositories as Saved Segments

The DB2 Server for VM messages for each national language you have installed are stored in message repositories. There are two message repositories for each language. One (ARIMxxxx where xxxx represents the LANGKEY) is for messages that are issued while the database is running. The other (ARIUME) is installed according to the CMS-specified rules for NLS (national language support) support for CMS applications, and uses the CMS facility to issue NLS messages from EXECs. The ARIUME message repository is used during initialization or termination of services (that is by the database manager itself, ISQL, DBS utility, and preprocessors among other things) since the message services cannot be used at that time.

For each language that is frequently used, you can have ARIMxxxx and ARIUME as follows:

ARIMxxxx
The ARIMxxxx repository (where xxxx represents the LANGKEY) is the repository for DB2 Server for VM messages, and is used by modules that reside in the user machine. (The ARIMxxxx repository is also used by the modules in the database machine. However, the database machine will always load ARIMxxxx into free storage). The saved segment is identified to the database manager by the ARISNLSC MACRO. Defining ARIMxxxx as a saved segment is described in Defining Saved Segments. To refresh this segment after service, you have to run ARISDBMA.
ARIUME
The DB2 Server for VM EXEC repository (ARIUME) is accessed by the database and user machines, and uses the CMS facility to issue NLS messages from EXECs. It is installed according to the rules specified by CMS for NLS support for CMS applications, and is added to the segment that contains the CMS message repository. The CMS message repository for the default language can be defined as a nucleus extension to which the ARIUME message repository can be added. For a language other than the default you must first define the segment for that language. For more information, see the VM/ESA: Installation Guide. The name of this segment will be NLXY, where X is the langlev specified in DMSNGP ASSEMBLE LANGLEV parameter, and Y is the LANGID as specified in Table 24. For example, if you use the default LANGLEV=S, and are installing American English (AMENG), then the segment name would be NLSAMENG.
To add DB2 Server for VM messages to the nucleus extension containing the CMS messages (for the default language) or to the saved segment containing CMS messages (for non-default languages), perform the following steps:
1. Define an NLSlangid segment, if one had not been defined yet, using the instructions in the "Installing and Customizing National Language" chapter in the VM/ESA: Installation Guide.
2. Make sure that the ARIUME repository is placed on a file mode accessible by the machine (for example, file mode A).
3. Update the LANGMERG control file.
  You need to have a LANGMERG control file for the national language you are saving as a saved segment. See the LANGMERG command in the VM/ESA: CMS Command Reference manual. The line added for the database manager should look as follows:
```
   MESSAGE ARIUME TXTlangid *
```
  If this file does not exist in the system, create this file and add the above line into the file. The langid stands for the language identifier of the national language you are defining the saved segment for.
  If the language is AMENG and the SQL message repository is named ARIUME TEXT, this line should look as follows:
```
   MESSAGE ARIUME TEXT *
```
4. Issue the LANGMERG command.
  The syntax of the command is:
```
   LANGMERG langid ARI ( CTL fn
```
  The langid stands for the language identifier of the national language, and fn is the file name of the control file created or updated in step 3.
  For example, if the language is AMENG and the control file is DMSNLS LANGMCTL, the command should look as follows:
```
   LANGMERG AMENG ARI ( CTL DMSNLS
```
  This will create a file ARINLS TXTAMENG on your A disk.
5. Update the LANGGEN control file.
  You have to add a line to the LANGGEN control file for the language identifier for the national language you are saving as a saved segment. See the LANGGEN command in the VM/ESA: CMS Command Reference manual. The line should look as follows:
```
   ARINLS TXTlangid A
```
  The langid stands for the language identifier of the national language.
  If the LANGGEN control file does not exist in the system, create one and add the CMS message repository file in front of the SQL message repository file. The lines should look as follows:
```
   DMSMES TEXT *
   ARINLS TXTlangid A
```
  DMSMES TEXT is the name of the English CMS message repository file. Use the correct message repository file name for the national language chosen (see Step 4).
6. Issue the LANGGEN command.
  The syntax of the command is:
```
   LANGGEN langid ( CTL fn
```
  The langid stands for the language identifier of the national language, and fn is the file name of the control file created or updated in step 3.
  For example, if the language is AMENG and the control file is DMSNLS LANGGCTL, the command should look as follows:
```
   LANGGEN AMENG ( CTL DMSNLS
```
  LANGEN will invoke SAVESEG or SAVESYS to save the NLS language segment.
7. Build and load the segment using the instructions in the "Installing and Customizing National Language" chapter in the VM/ESA: Installation Guide.
8. Issue the SET LANGUAGE command from each machine that you want to be able to access the saved segment.
  For example:
```
   SET LANGUAGE AMENG ( ADD ARI SYSTEM
```
  This command can be added to the PROFILE EXEC, or issued as a CMS command before running or accessing the database manager.

After applying service to module ARIUME, you will need to repeat step 6 and step 7.

For complete instructions on how to set up an application message repository, see the national language information supplied with VM/ESA.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]