The logman command

The logman command logs job statistics from a production plan log file.

Syntax

logman -V|-U

Arguments

-U

Displays command usage information and exits.

-V

Displays the command version and exits.

connection_parameters

Represents the set of parameters that control the interaction between the product interface, logman running on the master domain manager in this case, and the WebSphere Application Server infrastructure using HTTP or HTTPS. Use this syntax to specify the settings for the connection parameters:

[-host hostname] [-port port_number] [-protocol protocol_name] [-proxy proxy_name] [-proxyport proxy_port_number] [-password user_password] [-timeout timeout] [-username username]

where:

hostname

Is the hostname of the master domain manager.

port_number

Is the port number used when establishing the connection with the master domain manager.

protocol_name

Is the protocol used during the communication. It can be HTTP with basic authentication, or HTTPS with certificate authentication.

proxy_name

Is the proxy hostname used in the connection.

proxy_port_number

Is the proxy port number used in the connection.

user_password

Is the password of the user that is used to run logman.

Note: On Windows workstations, when you specify a password that contains double quotation marks (") or other special characters, make sure that the character is escaped. For example, if your password is tws11"tws, write it as "tws11\"tws".

timeout

Is the maximum time, expressed in seconds, the connecting command-line program can wait for the master domain manager response before considering the communication request as failed.

username

Is the username of the user running logman.

If any of these parameters is omitted when invoking logman, Tivoli® Workload Scheduler searches for a value first in the useropts file and then in the localopts file. If a setting for the parameter is not found an error is displayed. Refer to Setting up options for using the user interfaces for information on useropts and localopts files.

-prod

Updates the preproduction plan with the information on the job streams in COMPLETE state in production. By doing so the preproduction plan is kept up-to-date with the latest processing information. This avoids the possibility of the new production plan running again, job streams already completed in the previous production period.

-minmax setting

Defines how the minimum and maximum job run times are logged and reported. The available settings are:

elapsed

Base the minimum and maximum run times on elapsed time.

cpu

Base the minimum and maximum run times on CPU time.

This setting is used when the logman command is run from the command line and not by the JnextPlan script. When the logman command is run by JnextPlan, the setting used is the one specified in the logmanMinMaxPolicy global option.

-smooth weighting

Uses a weighting factor that favors the most recent job run when calculating the normal (average) run time for a job. This is expressed as a percentage. For example, -smooth 40 applies a weighting factor of 40% to the most recent job run, and 60% to the existing average. The default is 0%. This setting is used when the logman command is run from the command line and not by the JnextPlan script. When the logman command is run by JnextPlan, the setting used is the one specified in the logmanSmoothPolicy global option.

symphony-file

The name of an archived symphony file from which job statistics are extracted.

Comments

Jobs that have already been logged, cannot be logged again. Attempting to do so generates a 0 jobs logged error message.

How average run times are calculated

The estimated duration of a job run is provided by logman as part of the daily planning cycle. The estimated duration of a job run is based on the average of its preceding runs. To compute the average run time for a job, logman divides the total run time for all successful runs by the number of successful runs. If a large number of runs is used to compute the average, a sudden change in a job's run time will not immediately be reflected in the average. To respond more quickly to such changes, you can use the smooth option so that the average can be weighted in favor of the most recent job runs. Use the -smooth option to enter a weighting factor, as a percentage, for current job runs. For example, the logman -smooth 40 command will cause logman to use a weighting factor of 40 percent for the most recent runs of the job, and 60 percent for the existing average. The logman -smooth 100 command will cause the most recent runs of the job to override the existing average.

Logman retains the statistical data of job runs in the Tivoli Workload Scheduler database. There is no limit to the number of job instances retained in the job history.