Comet command line options

affected

The default TCP/IP port number for CometAnywhere is 11751. If you want to use another port number, you must specify the new value in two places:

on the remote CometAnywhere remote system using the /CAPORT command line option, or the following COSW.INI option on the host Comet system, via the following entries in the COSW.INI file (works on remote systems also): [NetConfig] CAPort=port

The valid TCP/IP ports are 0 to 65535, however please note that the first 1024 port numbers are reserved for applications other than CometAnywhere.

Example (using port number 54321):

command line option on remote system: cosw.exe /CAPORT:54321 /NET

COSW.INI entry on host system: [NetConfig] CAPort=54321

This option allows you to run Comet in demonstration mode. The restrictions of demonstration mode are:

a maximum of 1,000 keystrokes may be typed data files may not be larger than 640K bytes a maximum of 3 partitions may be configured

/KEYFILE:file

The default log filename is the user's profile name appended with ".LOG". For example, if the user's profile is NODE1, the log file is NODE1.LOG.

The log file is created in the Comet startup directory.

NET:IP-address NET:domain-name

/NET displays a dialog for the user to user an IP address or domain name. /NET:IP-address connects to the Comet host system at the specified IP address. /NET:domain-name connects to the Comet host system at the specified domain name.

The user profile is a file created during the system configuration process (SYSGEN). The extension for this file is CFG.

For example, to start Comet using a profile name of TEST (which equates to a configuration file of TEST.CFG), use the following option:

cosw /PN=TEST

Cosc

Allows a remote CometAnywhere user to request specific session number(s) on the host system. The following example requests session 005 on the host machine: c:\comet\comet.exe /S:005 /NET

If the requested session is not available, and if the /TSR option (see below) has NOT been specified by the host, Comet will run in the first available session on the host system.

Terminal names (term$) and sessions are different. Terminal names are changeable by any program to anything (with a 3 character limit). Comet does not change term$ itself, but a program could. Comet initializes term$ to correspond to the names specified in the comet.ini file. CA Sessions are fixed. They start with session 1 and go to the number specified in the ini file, with a maximum of 255 sessions.

This option refers to CometAnywhere sessions, not terminal names.

Multiple /s options may be specified in a single command line: c:\comet\comet.exe /NET:CAHost /S:005 /s:006 /s:007 /s:008 /tsr

When run, the first session will appear. Subsequent CTL/N keystrokes or mouse clicks to invoke a new CometAnywhere window will bring up the other sessions one at a time.

Cosh

This option attempts to load the Comet Security Server when Comet is started. This is a convenient way to start Comet on a single-user system.

Notes:

This option is for standalone systems only, where the Comet Security Server is to be run on the same system as Comet. This option is not intended for Comet systems that get security from the Comet Security Server running on another node in the network.

When the /SEC command line option is specified, Comet looks for a program named Csecsrv.exe in the specified start-in directory. The program, if found, is launched. · In Builds 300 through 307, this was an automatic feature (i.e., no command line parameter was required in order to launch the Comet Security Server). Starting with Build 308, it is no longer an automatic feature.

Cosc

Used on the CometAnywhere host this option will limit a session requested by a remote to only the specific session number requested. If that session is not available no session will be granted. This option is used in conjunction with the /S option (see above).

Here's an example:

cosw /TSR

If the requested session number is not available, Comet will not scan for another available session.

Cosc

Requires all remote sessions include a "/S:n" parameter to request a specific session. If they do not use this parameter then they'll get the "Target Session Unavaliable" error.