The logman command

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


logman -V|-U

     {-prod | symphony-file]
     [-smooth weighting]
     [-minmax {elapsed | cpu}]}


Displays command usage information and exits.
Displays the command version and exits.
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 Liberty Base 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]

The hostname of the master domain manager.
The port number used when establishing the connection with the master domain manager.
The protocol used during the communication. It can be HTTP with basic authentication, or HTTPS with certificate authentication.
The proxy hostname used in the connection.
The proxy port number used in the connection.
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".
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.
The name of the user running logman.
If any of these parameters is omitted when invoking logman, HCL Workload Automation 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.
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 {elapsed | cpu}
Defines how the minimum and maximum job run times are logged and reported. The available settings are:
Base the minimum and maximum run times on elapsed time.
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 -smooth 10. This setting is used when the logman command is run from the command line, as you may need in case of job recovery if you want to replace the job statistics in the database. When the logman command is run by JnextPlan, the setting used is the one specified in the logmanSmoothPolicy global option.
The name of an archived symphony file from which job statistics are extracted.
Specifies that logman retrieves job consumption information and ignores the remaining job statistics. Job consumption information consists of the number of successful jobs run during the day and is used to calculate your license usage. Job runs are counted only in the archived symphony plan. If the logman command is run more than once, jobs already counted in previous runs are not considered, so that no duplicate entries are present. Use this option to retrieve only the mandatory data for license usage calculation and avoid storing data which might be unnecessary. For more information about license management, see License computation model.


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


Log job statistics from the log file M201403170935:
logman schedlog/M201403170935