Creating a POF and migrating product options to it (PTF BQU1644 applied)
If you have applied PTF BQU1644, you must use this one-time procedure to:
- Create a new product options file (POF) as an option set member in the CNTL data set
- Migrate your product options from the BMC Configuration Component for z/OS (LGC) to the new POF
Notes
If you previously created a POF member in the CNTL data set, which was an optional feature in earlier product versions, you can skip this procedure.
If you skip this procedure but did not previously create a POF, attempting to run the product displays the following message:
ALMPERR3 ================ PACLOG - Error Message List ============= Row 1 of 4
Command ===> ____________________________________________ Scroll ===> PAGE
The following error(s) were encountered.
For further detail, type 'S' next to any message. Then press Enter.
Sel Message
=== ==========================================================================
_ BMC93799E OPTION SET ALM$OPTS NOT FOUND
_ BMC93799E MEMBER ALM$OPTS MUST EXIST IN DSN HLQ.CNTL
_ BMC93799E USE MAIN MENU OPTION 2 TO MIGRATE OR CUSTOMIZE PRODUCT OPTIONS
_ BMC93799E SEE KNOWLEDGE ARTICLE 151347 FOR MORE INFORMATIONBefore you begin
Ensure that you have applied PTF BQU1644 to version 12.1.00 of the PACLOG for Db2 product.
Note
When the PACLOG and BMC AMI Recovery Manager for Db2 products coexist in an IBM Db2 subsystem, BMC recommends that they use the same options file. You can designate that the two products share a common options file in this migration procedure.
For more information about integrating PACLOG with BMC AMI Recovery Manager, see Installing.
To migrate product options to a POF
Access the PACLOG Main Menu.
ALMPRIM ========================== PACLOG FOR DB2 V12.01.00 =============== Command ===> ____________________________________________________________ Type selection. Then press Enter. _ 1. Logging environment - Display and/or model changes to DB2* logging - Display current statistics & model changes - Display active log information - Display archive log information 2. Product option sets - Manage product options Subsystem ID . . . . . . . . . . . . <ssID> Option Set . . . . . . . . . . . . . ALM$OPTS Copyright 1994-2018 BMC Software, Inc. as an unpublished licensed work. All rights reserved. DB2 is a registered trademark of International Business Machines Corp.Configure options for the POF:
At Subsystem ID, enter the subsystem ID (SSID) or group attach name.
- At Option Set, enter the name of the option set that you want to use for the POF.
The default is ALM$OPTS. - Select 2. Product option sets - Manage product options.
- Press Enter.
On the Product Options panel, select 0. Migrate product options to this product options data set and press Enter.
ALMST00A ====================== Product Options =============== Command ===> _______________________________________________ Product options data set is HLQ.CNTL Select Action and press Enter Product Option File (POF) Action. . . . . _ 0. Migrate product options to this product options data set 1. Edit product option file with ISPF ________ Optional backup member name ________ 2. Validate product option file ________ 3. View product option file validation rules 4. Edit product option file template member ALMPOFT 5. Create a product option file via template ________On the Product Options Migration panel, enter the following information:
At Release, select the version from which you are migrating product options.
(For Release 1) Under Action 1. Copy POF option set to product option file, complete the following entries:
Field Entry From DSN Specify the data set name from which to migrate product options. From POF member Specify the product options file from which to migrate product options. To POF member Specify the name of the option set you want to create. Replace existing member Set Y to replace an existing POF; otherwise N. (For Release 2, 3, or 4) Under Action 2. Migrate LGC option set to product option file, complete the following entries:
Field Entry From LGC Specify the LGC name from which to migrate product options. From POF member Specify the product options file from which to migrate product options. Replace existing member Set Y to replace an existing POF; otherwise N. Press Enter.
ALMST00B ================= Product Options Migration =================== Command ===> ______________________________________________________ Product options data set is <HLQ>.CNTL Select Release to migrate from MIGRATING FROM LGC REQUIRES DBC AND LGC TO BE ACTIVE TO ACCESS OPTIONS Release . . . _ 1. V10.10 or earlier (POF) valid with Action 1 2. V11.10 (LGC) valid with Action 2 3. V11.20 (LGC) valid with Action 2 4. V12.10 (LGC) valid with Action 2 Select Action and press Enter Action. . . . _ 1. Copy POF option set to product option file From DSN _______________________________________ From POF member ________ To POF member ________ Replace existing member N (Y or N) 2. Migrate LGC option set to product option file From LGC option set ________ To POF member ________ Replace existing member N (Y or N)
Result
After creating the POF option set member in the CNTL data set, the product migrates product options from the LGC to that member.
Global options and substitution variables (PTF BQU1729 applied)
In a product options file (POF), you can specify most product options at the global or common level, and specify or override all product options at the SSID level.
The POF is part of the CNTL data set.
After you modify the file, you can set it on the PACLOG Main Menu for online use, or on the EXEC PARM for use with batch programs.
User substitution variables
You can use #USER1 through #USER9 and #VER1 through #VER3 as substitution variables. The variables are optional and have a maximum length of 54 characters. The length represents a data set name of 44 characters and, if it is a PDS, a member name in parens.
If you define the same variable more than once, the system only reads the last value.
Every place where you use a variable in a POF, the specified value replaces the variable.
You cannot use the same #USERx and #VERx substitution variable more than once in the same option.
Global and specific options
Options are valid for all Db2 subsystems, unless you add the SSID to the beginning of the option. SSID represents a specific Db2 subsystem ID.
If you have two options, one that is global and one with the SSID, the option that is specified with the SSID overrides the value for that subsystem. Non-specified subsystems use the global value.
You can specify all options as global, except for the following, which must begin with an ssid:
- ssid.BSDS1=
- ssid.BSDS2=
- ssid.HIST=
Sample POF template
The following sample POF displays all the variables that you can specify.
THE FOLLOWING ARE OPTIONAL USER SPECIFIED SUBSTITUTION VARIABLES.
THE VALUE WILL REPLACE OCCURRENCES OF THE VARIABLE NAMES.
THE MAXIMUM LENGTH OF A SUBSTITUTION VALUE IS 54. THE SAME
SUBSTITUTION VARIABLE CANNOT BE USED MORE THAN ONCE IN A SINGLE
OPTION VALUE.
#USER1=
#USER2=
#USER3=
#USER4=
#USER5=
#USER6=
#USER7=
#USER8=
#USER9=
#VER1=
#VER2=
#VER3=
OPTIONS ARE SPECIFIC TO A DB2 SUBSYSTEM IF PRECEDED BY ssid.
OPTIONS ARE VALID FOR ALL DB2 SUBSYSTEMS IF NOT PRECEDED BY ssid.
OPTIONS PRECEDED BY ssid. WILL OVERRIDE THE SAME OPTION THAT IS
NOT PRECEDED BY ssid.
BSDS1 - required, length 44, valid data set name
BSDS2 - required, length 44, valid data set name
BUFPAGES - not required, numeric range 30-512, default 64
DSNLOAD - required, length 44, valid data set name
HIST - required, length 44, valid History file data set
TSTAMP - required, Y or N, default Y
WORKUNIT - required, length 8, default SYSALLDA
ZIIP - required, length 8, ENABLED or DISABLED
THE FOLLOWING OPTIONS MUST BE PRECEDED BY ssid.
WHERE ssid IS THE DB2 SUBSYSTEM ID.
ssid.BSDS1=
ssid.BSDS2=
ssid.HIST=
Comments