Initializing and activating the MVS message service

The following steps describe what your installation must do so TSO/E can display translated messages. For complete information about these tasks, see .

Ensure that the appropriate install message files have been installed on your MVS/ESA System Product (MVS/ESA SP) system.
If your installation uses installation-written languages or symbolic language names other then the standard three-character codes that are provided, these languages and symbolic names must be defined to the MVS™ message service.
Allocate space for each run-time message file.
This run-time message file must be a VSAM linear data set. First, allocate a VSAM linear data set for each run-time message file, then use the MVS message compiler to format each install message file to a run-time message file.
Use the MVS message compiler to format the install message file into a run-time message file.
The input to the compiler is the install message file PDS. The output from the compiler is the run-time message file allocated in step 2.
Create installation exits if you want to tailor MMS processing.
IBM® provides two installation exits that an installation can use to customize MMS processing. Specify the exit names in the MMSLSTxx member of SYS1.PARMLIB.
Update the following SYS1.PARMLIB members to initialize values for MMS:
- MMSLSTxx, to define the available languages for message translation and other message translation processing
- CNLcccxx, to define the date and time formats used in the display of translated messages
- CONSOLxx, to specify the MMSLSTxx member in effect for the system
Activate MMS.
You can use the INIT statement in CONSOLxx to activate MMS at initialization. The operator can activate MMS using the SET MMS command.