Assume that you customized the values in your POF, and now you are installing a new release of a product. To avoid having to customize the values again, you can specify that the Installation System use your existing POF to populate the values in the new initial POF.

The new POF contains your current values plus any new keywords (and their values) for the new release.

To reuse a POF

  1. Run the Installation System.
  2. From the Install System JCL Generation File Information panel, in the Use Existing POF to Populate the New Product Options File field, type Y.

    Reusing an existing POF

    AJXP041 Install System DB2 Administrative Components
Command ===>
Product Options File name (POF) . . . . . . . . . . . . . . ZAJXBPOF
Use Existing POF to Populate the New Product Options File . Y (Y/N) Press PF1 HELP for more information regarding the POF, its use, and how to avoid having to reenter the information for SSID installs.
Verify the ACS Common SQL API Alias Qualifier and the Collection ID.
BMC Software Inc. recommends accepting the defaults.
To make changes, type over the values shown.
Alias Creator . . . . . . . . . . 7CS111S1
ACS
Collection ID . . . . . . . . . ZCS111_D_MAIN
Execution for DB2
Collection ID . . . . . . . . . ZEX111_D_MAIN Press Enter to continue or F12 to go back.
  3. Enter the names of the data set and member for the existing POF (see the above figure).

    For the member name, use the name of the POF that is used as the initial POF when you invoke the product.

    Specifying the name of the existing POF

    AJXP044 Install System JCL Generation File Information
Command ===> __________________________________________________________________
Enter the data set and member name of an existing Product Options File (POF)
that is to be used to seed the new POF. An existence check will be
performed, including verifying the specified member has a format
consistent with the POF format.
POF Data Set . . . . . . . ______________________________________________
POF Member . . . . . . . ________