Command-Line Parameters

The following parameters are available for use in the Post-Processing Command text field.

Parameter	Description	Report Types
$outputDir	Name of the output directory of the external copy of the generated report	All
$outputFiles	Comma-separated list of names of output report files	All
$errorStatus	Indicates whether a report ran successfully.	All
$errorLine	Error description (can be empty).	All
$reportType	The report type that was run.	All
$user	The FlexNet user who ran the report.	All
$features	Comma-separated list of features included in the report.	All
$servers	Comma-separated list of license servers included in the report	All
$vendorDaemons	Comma-separated list of vendor daemons included in the report	All
$startDate	Start date of the report.	All
$endDate	End date of the report	All
$showZero	Indicates where unused features are included	High Water Mark, Summary Barchart, Usage Over Time, Usage Summary
$filter	Comma-separated list of filter expressions	Raw
$eventFilter	Comma-separated list of event filters	All
$delimiter	Field delimiter on reports	All reports except Summary Barchart and Server Coverage
$showAvail	Indicates whether a group of available licenses is also on graphs (Usage Over Time)	High Water Mark, Usage Over Time
$elimFalseDenials	Denial elimination algorithm is turned on and has the specified window	Raw, Usage Summary
$sortOrder	Sort order of the records on the report	All
$featureUniq	Mode of feature identification	All
$timeInSeconds	Show time value in RIF files as UNIX seconds since 00:00:00 January 1, 1970 GMT	Raw

note

You should use parameters that are applicable to the report type you are defining. Using parameters not applicable to the report type will result in indeterminate values at run time.

Parameters that can have an empty value ($features, $servers, $vendorDaemons, $filter, $eventFilter) should be used only in cases where the corresponding report configuration values are not empty. If the report configuration setting does not contain a value for a specified parameter, no argument will be emitted, which can cause the argument interpreter in the post-processing script to confuse the next argument with the value of the current argument.

Example: The list of servers is specified ($servers), but in the License Server Host selection on the Naming page (step 1) of the Report Configuration Wizard, none has been selected (indicating to run the report for all license server hosts). Then no argument will be emitted by the post-processing invocation. In case another parameter is specified, the argument evaluation logic can easily mistake the value for the next argument as the list of servers.

After you specify the post-processing expression, you can complete the report configuration. When you finish the report configuration, FlexNet Manager for Engineering Applications validates the external output directory and the post-processing expression.

After saving the report configuration, you can run the report. FlexNet Manager for Engineering Applications will generate the report, copy the report to the external directory, and then invoke the post-processing script.