×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC AMI Log Master for Db2 12.1 Command and syntax reference

SORTOPTS statement

The SORTOPTS statement controls how Log Master dynamically allocates the memory and data sets that are related to sort actions (including sort routine memory and sort work data sets).

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

The following figure shows the SORTOPTS syntax.


OptionDescription

SMCORE

Specifies the maximum amount of memory that Log Master requests when it uses the sort routine. To specify this keyword, enter both of the following values.

ValueDescription
mainSize Specifies the total amount of memory that Log Master sort actions can use (both above and below the 16-MB line).
vscoret Specifies the amount of memory that Log Master sort actions can use below the 16-MB line.

See also SMCORE=0M,0K.

RESINV memValue

Specifies the amount of memory (below the 16-MB line) that Log Master instructs the sort routine to reserve for processing other than sort processing. Specify the memValue amount as bytes, kilobytes (use the suffix K), or megabytes (use the suffix M).

See also RESINV=0K.

PARMOPTS

Specifies how Log Master dynamically allocates data sets other than sort work data sets.

ValueDescription
STORCLAS (storageClass)

Specifies the storage class that Log Master uses for storage of other dynamically allocated data sets. Use this keyword only with DFSMS. Do not specify a value of VIO.

See also PARMSTOR=.

UNIT (unitName)

Specifies the storage device (or group of devices) where Log Master requests space for other dynamically allocated data sets. Enter any valid unit name or a generic unit name where you can allocate temporary data sets. Do not use this keyword with DFSMS.

See also PARMUNIT=.

SORTDYN

Determines whether Log Master uses the sort routine’s dynamic sort allocation rules or accepts your allocation attributes.

ValueDescription
SYSTEMDirects Log Master to use the sort routine’s rules.
USE (default) Enables you to enter allocation attributes.

See also SORTDYN=USE.

Sort file size parameters

Specifies the estimated size of the data that Log Master must sort during a given job. You can also specify the size of the data to be sorted during an individual log scan. These parameters specify the estimated size of the data to be sorted or a technique that Log Master uses to calculate the estimate.

For more information, see Sort file size parameters.

HISTORY

Determines whether Log Master stores information in the Repository about the current job’s sort actions. The information includes the number of log records that were sorted and the average size of the records. If historical information is stored in the Repository from previous runs of the current work ID, Log Master can use that information to estimate the size of the data to be sorted during the current run. For more information, see FILSZ. Log Master passes the estimated size to the sort routine in your environment.

Log Master stores and retrieves historical information by using the work ID of the job. If you run a Log Master job repeatedly, you can use this keyword (and the related USE HISTORY value) to optimize the sort actions of your job.

ValueDescription
WRITE (default) Specifies that Log Master writes information about the current job’s sort actions in the Repository.
NOWRITE Specifies that Log Master does not write information in the Repository.

WORKOPTS

Specifies how Log Master dynamically allocates sort work data sets.

ValueDescription
NUM (numOfFiles)

Specifies how many sort work data sets Log Master allocates for each sort action. You can specify any number from 1 to 255. The default value is 0.

See also WORKNUM=0.

STORCLAS (storageClass)

Specifies which storage class Log Master uses for storage of sort work data sets. Use this keyword only if you want DFSMS to manage the sort work data sets.

See also WKSTOR=.

UNIT (unitName)

Specifies the storage device (or group of devices) where Log Master requests space for sort work data sets. Enter any valid unit name or a generic unit name where you can allocate temporary data sets. Do not use this keyword if you want DFSMS to manage the sort work data sets.

See also WKUNIT=.

Sort file size parameters

The Sort file size parameters syntax occurs in both the SORTOPTS and LOGSCAN statements.

Use this syntax to improve the performance of Log Master sort actions as follows:

  • When these parameters are included in a SORTOPTS statement, they affect the sort actions of the entire job.

  • When these parameters are included in a LOGSCAN statement, they affect only the individual log scan.

Sort file size parameters syntax diagram

You can also use the following methods to affect the performance of sort actions:

  • You can control how much memory Log Master allocates for each invocation of the sort routine (for more information, see SMCORE=0M,0K).

  • You can control how the sort routine allocates sort work data sets (for more information, see Defining sort work data sets).

OptionDescription

FILESZ

Specifies the estimated size of the data that Log Master must sort during a given job or log scan. The value of this keyword determines the estimated size or the technique that Log Master uses to calculate an estimated size. Log Master passes the estimated size to the sort routine in your environment. The sort routine uses the estimated size value to efficiently allocate sort memory or sort work data sets.

ValueDescription
NONE

Directs Log Master not to pass any file size estimate to the sort routine. When this value is NONE, the sort routine in your environment uses its own default settings to allocate memory and sort work data sets.

For compatibility with earlier versions of Log Master, this is the default value.

USE HISTORY

Directs Log Master to calculate a file size estimate based on historical information about the current work ID. To use this value, you must have previously directed Log Master to write the historical information in the Repository (using the related HISTORY keyword of the SORTOPTS statement). The historical information describes the sort actions of previous runs of the current work ID (including the number of log records sorted and the average size of the records).

Log Master calculates the estimate based on a weighted average of previous runs, giving greater weight to more recent runs. If you run a Log Master job repeatedly, you can employ the USE HISTORY value (and the related HISTORY keyword) to optimize the sort actions of your job. For more information, see HISTORY.

VariableDescription
numOfRunsDetermines how many runs Log Master includes in its calculation of the file size estimate. The minimum value for numOfRuns is 1, the default value is 5, and the maximum value is 20.
LOGBYTES

Directs Log Master to calculate a file size estimate based on the total volume of the log records that the current work ID processes. Log Master examines the total volume of the log records (expressed as a number of bytes), not the number of log records.

Use the following keyword to give Log Master additional information that it can use to calculate a more precise file size estimate.

VariableDescription
USE HISTORY

To calculate a file size estimate, Log Master uses the total volume of log records and historical information stored in the Repository about previous runs of the current work ID. The historical information includes the number of log records and the average length of the log records for previous runs. This is the default value.

ESTnumOfRecs

Directs Log Master to use the value that you enter for numOfRecs as an estimate of the number of log records to be sorted. Log Master passes the estimated value to the sort routine in your environment.

VariableDescription
AVGRECLEN lenValue

Specifies the average record length of the log records to be sorted. Use this keyword to pass more precise file size estimate to the sort routine in your environment.

If you specify a FILSZ estimate, Log Master determines the default SMCORE values by using the minimum storage required by BMCSORT when all of the following conditions exist:

  • You accept the default values of 0 for the SMCORE installation option.

  • You specify a value for the FILSZ keyword in the SORTOPTS statement.

  • You do not specify SMCORE values in the SORTOPTS statement.


Was this page helpful? Yes No Submitting... Thank you
Last modified by Anagha Evans on Sep 30, 2021
command_reference syntax

Comments

Log in or register to comment.

XMLOPTS statement
WORKID statement
© Copyright 1996-2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.