z/OS MVS Planning: Operations
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Steps for providing translated messages

z/OS MVS Planning: Operations
SA23-1390-00

The following steps describe what your installation must do for users to receive translated messages.

  1. Ensure that the appropriate system install message files have been installed on your system.

    For MVS™ messages, IBM® provides an install message file for U. S. English messages and an install message file for the Japanese translation. As a feature of TSO/E, IBM also provides an English and Japanese install message file for TSO/E messages. Each install message file for the language is a PDS. Your installation uses SMP/E to install each install message file on the system. You can install concatenated PDSs. For installation information, see the program directory for the product.

  2. Allocate space for each run-time message file.

    You use the MVS message compiler to format each install message file to a run-time message file. (The compiler formats one run-time message file for each language including English.) This run-time message file must be a VSAM linear data set. You must allocate a VSAM linear data set for each run-time message file. See Allocating storage for a run-time message file.

  3. 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 the previous step). See Compiling message files.

  4. If needed, create installation exit routines.

    IBM provides two exits that an installation can use for MMS processing. You specify the exit names in MMSLSTxx of SYS1.PARMLIB. See Controlling MMS through installation exits and Using parmlib to control message translation.

  5. Create or update the following 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 for translated messages
    • CONSOLxx to specify the MMSLSTxx member in effect for the system
    See Using parmlib to control message translation.
  6. Activate MMS.

    You can activate, refresh, or stop MMS. You can use the INIT statement in CONSOLxx to activate MMS at initialization. The operator can activate or stop MMS by using the SET MMS command. See Activating MMS.

On TSO/E, the installation can indicate in the TSO/E LOGON exit a primary or secondary language for message translation. Otherwise, TSO/E users can specify the primary or secondary language on the TSO/E PROFILE command, and TSO/E can deliver the translated messages. See z/OS TSO/E User's Guide for information.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014