HLASM Toolkit Feature Installation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Create Product Parameter File (PPF) override (z/VM)

HLASM Toolkit Feature Installation and Customization Guide
GC26-8711-09

This section provides information to help you create a product parameter file (PPF) override. The example used in this section shows how to change the shared file system (SFS) file pool where HLASM Toolkit Feature files reside.

Note: Do not modify the product supplied P696234K $PPF or P696234K PPF files to change the file pool name or any other installation parameters. If the P696234K $PPF file is serviced, the existing $PPF file will be replaced, and any changes to that file will be lost; by creating your own $PPF override, your updates will be preserved.
The following process describes changing the default file pool name, VMSYS, to MYPOOL1:
  1. Create a new $PPF override file, or edit the override file created via the 'Make Override Panel' function.
    Command Explanation
    xedit overname $PPF fm2
    overname is the PPF override file name (such as "myHLASM") that you want to use.

    fm is an appropriate file mode. If you create this file yourself, specify a file mode of A.  

    If you modify an existing override file, specify a file mode of A or D, based on where the file currently resides (A being the file mode of a R/W 191 minidisk, or equivalent; D, that of the MAINT 51D minidisk).

  2. Create (or modify as required) the Variable Declarations (:DCL.) section for the HLASMSFS override area, so that it resembles this :DCL. section. This override is used for the installation of HLASM Toolkit Feature.
    :OVERLST. HLASMSFS
    *
    * =================================================================== *
    * Override Section for Initial Installation (Using SFS Directories)   *
    * =================================================================== *
    :HLASMSFS. HLASMSFS P696234K
    :DCL. REPLACE
    &191     DIR MYPOOL1:P696234K.
    &SAMPZ   DIR MYPOOL1:P696234K.HLASMTL.LOCAL
    &DELTZ   DIR MYPOOL1:P696234K.HLASMTL.DELTA
    &APPLX   DIR MYPOOL1:P696234K.HLASMTL.APPLYALT
    &APPLZ   DIR MYPOOL1:P696234K.HLASMTL.APPLYPROD
    &BLD0Z   DIR MYPOOL1:P696234K.HLASMTL.TBUILD
    &BAS1Z   DIR MYPOOL1:P696234K.HLASMTL.OBJECT
    &HLAID1  USER  P696234K
    :EDCL.
    :END.
    *

    (This override replaces the :DCL. section of the HLASMSFS override area of the P696234K $PPF file.)

  3. If your $PPF override file was created on the A disk, copy it to file mode D—the Software Inventory minidisk (MAINT 51D). Then erase it from file mode A.
    Command Explanation
    copyfile overname $PPF fm = = d (olddate
    Move PPF file to software inventory disk.
    erase overname $PPF fm
    Erase redundant file on fm disk.
    Options:
    OLDDATE
    Use the date and time on the input file as the date and time of last update of the output file.
  4. Compile your changes to create the usable overname PPF file.
    Command Explanation
    vmfppf overname HLASMSFS
    overname is the file name of your $PPF override file.

Now that the overname PPF file has been created, you should specify overname instead of P696234K as the PPF name for those VMSES/E commands that require a PPF name.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014