Loading a User Message Repository into a CMS Logical Saved Segment

The following steps outline the procedure for loading a user message repository into a CMS logical saved segment. For additional information about defining and building a logical saved segment, see z/VM: CP Planning and Administration.

In this example, the repository contains American English messages for an application whose application ID is LCL. The name of the compiled message repository (the output of the GENMSG command) is LCLUME TEXT.

  1. Create a LANGMERG control file for the application (or update the existing control file for the application) to identify the compiled message repository and any other language-related files for the application that are to be combined into a single text file. The message repository is identified on a LANGUAGE record in the control file. In this example, a new control file named LCLAMENG LANGMCTL is created. It contains the following records:
    DISK 19D
    ETMODE OFF
    MESSAGE LCLUME (VMCTL DMSVM

    For information about the content and format of the LANGMERG control file, see the description of the LANGMERG command in the z/VM: CMS Commands and Utilities Reference.

  2. Use the LANGMERG command to combine the language information into a single text file:
    langmerg ameng lcl
    LANGMERG generates a file named LCLNLS TXTAMENG.
  3. Define a CP saved segment to use as the physical saved segment that holds the logical saved segment where you intend to load the user message repository. (If you plan to define the logical saved segment in an existing physical saved segment, you can skip this step.) Use the DEFSEG command to define either a member saved segment within a segment space or a stand-alone discontiguous saved segment (DCSS). In this example, a DCSS named LCL is created, of type SR (shared read-only access), located in pages 600-6FF:
    defseg lcl 600-6ff sr
    Note:
    1. For more information about the DEFSEG command, see the z/VM: CP Commands and Utilities Reference.
    2. To define a CP saved segment you need CP class E command privileges. You may have to contact your system support personnel.
    3. If you prefer, you can use VMSES/E (the VMFSGMAP and VMFBLD commands) to define and build your saved segments. In that case, omit this step and steps 5 and 7. For more information about using VMSES/E to define and build saved segments, see z/VM: CP Planning and Administration.
  4. If you want to add the message repository to an existing logical saved segment, edit the logical segment definition file and add a LANGUAGE record that identifies the language file; otherwise, create a new logical segment definition file. When the segments are built, the file name of the logical segment definition file becomes the name of the logical saved segment. In this example, a logical segment definition file named LCLAMENG LSEG is created for a new logical saved segment named LCLAMENG. It contains the following record:
    LANGUAGE LCL AMENG
  5. If you want to add the logical saved segment to an existing physical saved segment, edit the physical segment definition file and add a logical segment (LSEGMENT) record that identifies the logical segment definition file; otherwise, create a new physical segment definition file. The file name of the physical segment definition file must be the name of the DCSS or member saved segment you are using as the physical saved segment. In this example, a physical segment definition file named LCL PSEG is created for a new physical saved segment named LCL. It contains the following record:
    LSEGMENT LCLAMENG LSEG
  6. The system segment identification file, usually named SYSTEM SEGID, associates each logical saved segment with its physical saved segment. It must reside on the CMS system disk. This file is updated or created by the SEGGEN command. Because the file cannot be updated or created on the CMS system disk, you must make sure that a copy of the version you want to update is located on a read/write disk.
  7. Use the SEGGEN command to build (or rebuild) the physical and logical saved segments:
    seggen lcl pseg a system segid a (map gen

    For information about using the SEGGEN command, see the z/VM: CMS Commands and Utilities Reference.

  8. Copy the SYSTEM SEGID file to the system disk and resave CMS. There are special instructions for doing this, and some of the steps can be done only by authorized user IDs. You may have to contact your system support personnel. For more information, see the description of the SEGGEN command in the z/VM: CMS Commands and Utilities Reference or the chapter on planning and defining logical saved segments in z/VM: CP Planning and Administration.
  9. Users can then use the SEGMENT LOAD command to load the logical saved segment into their virtual machines:
    segment load lclameng

    For more information about the SEGMENT LOAD command, see the z/VM: CMS Commands and Utilities Reference.