Default argument file

GGC tools can load command options from a default argument file named in a specific way in default locations.

Syntax

{ tool.command | .tool.command }

tool is the name of the GGC tool. For example, ggcadmin, or ggcgen. For BDL scenario, the tool is "bdl".
command is the name of the tool command. For example, startbdlserver.

The file name syntax option with a dot (.) prefix is used to indicate a hidden file.

Usage

ggcadmin, ggcgen, and BDL scenario tools accept arguments from a file. This allows you to save options to a file that tend to be long and that otherwise you would type over and over again.

For example, you can save the options to start the bdl server in a file named ggcadmin.startbdlserver in your user home path .ggc directory.

--idle-delay=2000
--port=9000

When you run the associated command, the options are automatically loaded from the file. However, the GGC expects to find default files in either your ${HOME}/.ggc/ Linux®, (%HOMEPATH%/.ggc/ Windows®) directory, or in your current working directory.

Note: It uses the first file it finds.

Table 1. Commands and default argument files
Command type	File name	Example
ggcadmin `command`	ggcadmin.`command`	.ggcadmin.startbdlserver ggcadmin.startbdlserver
BDL scenarios (for example, `fglrun scenario.42m tcp`)	bdl.`command`	.bdl.tcp bdl.tcp
ggcgen `command`	ggcgen.`command`	.ggcgen.bdl ggcgen.bdl

bdl tcp or ua

For BDL scenarios run with tcp type command (for example, fglrun scenario.42m tcp), the ggc will look for the argument file in one of these formats:

.bdl.tcp
bdl.tcp

For BDL scenarios run with the ua type command (for example, fglrun scenario.42m ua --url), the ggc expects the argument file in one of these formats:

.bdl.ua
bdl.ua

Show the expanded command line

If you wish to see what options are loaded with the command, use the --dump-command option.

ggcadmin startbdlserver --dump-command

The output is shown:

ggcadmin startbdlserver [--idle-delay=2000] [--port=9000]