Space announcements

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

STOREOPTS statement

The STOREOPTS statement controls how Log Master maintains internal memory and file structures called key stores. These internal structures are built and maintained in below-the-bar memory, but if the memory requirements exceed the MEMORY specification, key stores offload data to above-the-bar memory.

The keywords of this statement correspond to the installation options described in Installation option descriptions.

The following figure shows the syntax.

STOREOPTS statement syntax diagram

MEMORY(data, index)

Defines the total amount of memory that Log Master uses for key stores. If you specify this keyword, ensure that it is the first keyword in the STOREOPTS statement. The keyword has the following values:

  • data

    Specifies the amount of memory that Log Master uses to store internal data as it processes log records. Enter an amount of memory in kilobytes (use the suffix K) or megabytes (use the suffix M). You might need to override the default value of this keyword frequently, because the amount of memory required for efficient processing can increase or decrease dramatically based on how many DB2 log data records that Log Master is processing.

  • index

    Prior to PTF BQU0316, this value is required, but not in use.
    (PTF BQU0316 applied) The index value specifies the target amount of memory used for the indexes in the key stores.

If the first value or (PTF BQU0316 applied) either value is exceeded, Log Master will offload (or "spill") the excess to above-the-bar storage which might result in a slight decrease in performance. The product adheres to the specifications provided in most cases. However, when large volumes of data are processed or when the specification is lower than the default values, the amount of below-the-bar memory used might exceed the specifications.

Log Master distributes the memory that you allocate between key stores based on the values that are specified for the MEMPERCENT keyword or the xxPCT installation options.

See also KSMEMORY=100M, 10M.

MEMPERCENT

Determines how Log Master distributes memory among its individual key stores. Each value represents a percentage of the total amount of key store memory. For more information, see MEMORY(data, index).

Note

BMC recommends that you do not change key store memory distribution unless you experience repeated performance problems related to key store use.

For each key store that it uses, Log Master displays sets of output messages that contain allocation and use information. Use this information to distribute key store memory optimally for your data and environment. The allocation and usage messages begin with message BMC097561I.

For more information about redistributing key store memory, see the Log Master for DB2 expert information, or contact Customer Support.

If you use the MEMPERCENT keyword, you must specify percentage values for each key store as an integer, using the following guidelines:

  • URID and LOGRECORD are required; the valid range is 1 through 99.

  • FORWARDCOMPLETION, BACKWARDCOMPLETION, and ANOMALY are optional; the valid range is 0 through 98.

  • The percentage values must add up to 100 percent (including any default values for key stores that you do not specify).

  • To avoid confusion, specify a percentage value for each key store, even if the value is 0 or unchanged from the default value.

  • Do not specify any key store more than once.

The keyword has the following values:

  • URID

    Specifies the percentage of key store memory that is allocated to the URID (UR) key store. In the UR key store, Log Master maintains information about each unit of recovery that it encounters within the range of a log scan. If you do not specify this percentage value, Log Master uses the value of the URPCT installation option.

    When your job reads input from a logical log file, Log Master redistributes all available key store memory to the UR key store, regardless of your specifications. Log Master takes this action because it does not require the other key stores to process logical log input.

  • LOGRECORD

    Specifies the percentage of key store memory that is allocated to the log record (LR) key store. In the LR key store, Log Master maintains a copy of log records that require row completion processing. If you do not specify this percentage value, Log Master uses the value of the LRPCT installation option.

  • FORWARDCOMPLETION

    Specifies the percentage of key store memory that is allocated to the forward completion (FC) key store. In the FC key store, Log Master maintains copies of complete row images that might be used for row completion processing. If you do not specify this percentage value, Log Master uses the value of the FCPCT installation option.

  • BACKWARDCOMPLETION

    Specifies the percentage of key store memory that is allocated to the backward completion (BC) key store. In the BC key store, Log Master maintains copies of complete row images that might be used for row completion processing. If you do not specify this percentage value, Log Master uses the value of the BCPCT installation option.

  • ANOMALY

    Specifies the percentage of key store memory that is allocated to the anomaly (AN) key store. In the AN key store, Log Master maintains information that is used to produce the Backout Integrity report. If you do not specify this percentage value, Log Master uses the value of the ANPCT installation option. When your job does not include a Backout Integrity report, Log Master disregards your specification and redistributes the memory of the AN key store to the FC and BC key stores.


Was this page helpful? Yes No Submitting... Thank you

Comments