Skip to Content
Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see DASD MANAGER PLUS for DB2 13.1.

Using the product options file (POF)

The POFDS parameter in the installation options module specifies an 80-character sequential file. This file, the product options file (POF), contains parameters and values for the JCL Generation options.

The POF is built during the installation of the products. The file is located in the HLQ.UBMCCNTL data set. The POF does not require assembly and linkage and does not need to reside in an APF-authorized data set.

When you install the products, only one POF is created. This initial POF is initialized and populated with the default ISPF variables and values from the installation panels. This POF is shared among several products, if those products are installed at the same time. With DASD MANAGER PLUS, you can create action POFs (also called user POFs) and associate their values with specific actions. For more information about action POFs, see Using action POFs to reset JCL options.

In addition, the installation system uses the same application ID (or profile) for the products in the BMCDB2 CLIST. This single application ID enables the JCL Generation options to be shared with other products, such as the BMC AMI Catalog Manager for Db2 product. Thus, when you specify an option for generating JCL in one product, your selection applies to all of the products. Although we recommend that you use a single application ID, you can choose individual product application IDs on the BMCDB2PR panel.

If the value of a POF keyword in your user POF uses a library from an earlier version of the product, update the keyword to use a library for the version of the product that has recently been installed.

Information
Example
  • If the value of the BMC_COPY_LOAD keyword is BMC1120.ASU.D11.LOADf, and
  • Then you installed version 12.1.00 of DASD MANAGER PLUS

Update the value of the keyword to a version 12.1.00 LINK library (BMC1210.ASU.D12.BMCLINK).

JCL Generation uses the variables in the ISPF profile when generating JCL. When you start DASD MANAGER PLUS, JCL Generation determines whether to reset the variables in the ISPF profile:

  • The first time that you run a product, it sets all of the values that are in the ISPF profile to the values in the initial POF. If you have not specified a POF, the product uses default values from the variables in the profile.
  • If the POFDATE parameter in the initial POF is greater than the value of the POF date in the ISPF profile, the product uses the values in the POF that are marked with refresh,(R) to reset the ISPF variables.
  • If you specify a new initial POF in the POFDS installation option, the values in the POF that are marked with refresh ,(R) are used to reset the ISPF variables. The value of the POFDATE keyword in the new initial POF is saved in the ISPF profile.

For more information about POFs, see the following:

Related topics

Overview

Using

Setting-up-DASD-MANAGER-PLUS

Using-options-to-control-your-environment

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

DASD MANAGER PLUS for DB2 12.1