Console command-line configuration
The GUI console is run through a Java™ Runtime Environment (JRE). Parameters can be passed as arguments to the console. The commands are located in the console directory and are accessible by entering arguments in the jcon.bat or jcon64.bat file. Running one JCON command with the -SF parameter specified opens only one JRE.
Use the jcon.bat file to start one or more 32-bit console sessions. Use the jcon64.bat file to start one or more 64-bit console sessions.
Format
- -CONFIGFILE
- Specifies the configuration file to start a client session from the command line, where configfile is the configuration file name. This parameter provides flexibility, such as the ability to set up automation programs.
- -SF
- Specifies a file that contains configuration parameters to instantiate multiple sessions. Each
line is interpreted as a separate session definition, where sffile is the
configuration parameters file name. Environment variable substitution can be used inside the file.
For an example of using this parameter, see Examples.
If the LockConsole command is entered with the lock parameter specified, the -SF parameter is disabled.
The TPF Operations Server administrator can enable the -SF parameter after LockConsole lock command processing is completed by setting the ETOSENABLESF environment variable to Y.
- -CONFIGDIR
- Specifies the directory that is used by the graphical session starter interface when searching
for configuration files, where dirname is the directory name. This parameter
indicates that the directory provided is used by the base setup in the session starter view of the
console window to search for configuration files. By default, the
config\
subdirectory of the working directory for the application is used. - -NOSS
- Specifies a parameter so the graphical session starter interface is not displayed when a client is connected to the TPF Operations Server. This parameter is useful only when client sessions used are automated and do not require manual intervention.
- -SORTBYNAME
- Specifies that the graphical session starter interface use an alphabetic organization method for configurations. For more information about simple setup, see Console configuration.
- -SORTBYPROC
- Specifies that the graphical session starter interface organize the configurations by processor
using the connection processor configuration parameter. This is the default parameter. For more
information about the
connection.processor
parameter, see Connection information. - -HIDEMENUBAR
- Removes the menu bar from the top of the console window. For more information about the menu bar, see Menu bar (console menu options).
- -HIDEHORIZBAR
- Removes the horizontal scroll bars from the console window.
- -WINTITLE
- Customizes the title bar of the TPF Operations Server
console window when you specify this parameter with a user-defined title parameter, for example,
-wintitle "Blue Complex Operations"
. For more information about the TPF Operations Server console window components, see Operate the console. - -FILTERPATH
- Specifies locations for searching for custom filter engines, where path is
the location of the custom filter engine that you are using:
- If your filter engine is in a .jar file, you must specify the
path variable by using the full path of the .jar file, for
example:
C:\Program Files (x86)\IBM TOS\console64>jcon64 -filterpath "C:\Program Files (x86)\IBM TOS\console\LabFilter\ZSTATEngine.jar"
- If your filter engine is in a .class file, you must specify the
path variable by using the full path of the directory that contains the
.class file. For example, if the filter engine is in the
ZSTATEngine.class file in the ZSTATEngine directory,
specify the path variable as follows for a 64-bit
console:
C:\Program Files (x86)\IBM TOS\console64>jcon64 -filterpath "C:\Program Files (x86)\IBM TOS\console\ZSTATEngine"
If you have multiple custom filter engines with different locations, specify the FILTERPATH parameter once for each location. Alternatively, you can specify multiple locations by using one FILTERPATH parameter and separating each location (path) with a semicolon (;). You can specify an unlimited number of locations.
- If your filter engine is in a .jar file, you must specify the
path variable by using the full path of the .jar file, for
example:
- -DISABLECLOSEWINDOW
- Disable closing the main console window. To disable closing individual sessions, specify CLOSEWINDOW=DISABLE in the session configuration file.
Examples
c:\console> jcon.bat -CONFIGFILE tpf1.conf
c:\Program Files (x86)\IBM TOS\console64> jcon64.bat -CONFIGFILE tpf1.conf
c:\Program Files (x86)\IBM TOS\console64> jcon64.bat -SF localhp5.txt
localhp5.txt
file:
-configfile %USERPROFILE%\local5_PRC.conf
-configfile %USERPROFILE%\local5_RO.conf
The first line in the
localhp5.txt file causes a session to be started by using the
local5_PRC.conf file as the session configuration file. The second line causes
a session to be started by using the local5_RO.conf file as the session
configuration file. The console searches the .conf files in the directory that
is defined by the %USERPROFILE% environment variable.