Customize the GCM client application
geometry. This includes window colors, sizes, and placement. This is
accomplished using GCM client menu functions. See the GCM client
help for more information.
Customize connection attributes. These include the IP port assignment, whether to retrieve
notices or banners upon connection, and various limits and diagnostic
attributes. You can modify all these attributes from the GCM client.
Note that if you change the IP port assignment, you must restart
the GCM servers.
Defining and Using
Commands The GCM supports distributed execution of OpenVMS DCL commands
and command procedures. However, at this time, the GCM does not
support interactive commands and procedures. A DCL command that
is a good candidate for execution using GCM has the following characteristics:
It is immediately executed.
It produces its output upon execution.
It returns immediately.
Many DCL commands require a response from the user or do not
return immediately. Such commands are not good candidates for use
with GCM. For example, the RUN command does not always return immediately. The
GCM server executes each command request within a subprocess but
does not return any response to you; nor does the subprocess terminate
if the program does not terminate. Therefore, to stop the subprocess you
must enter a SHOW SYSTEM command to identify the associated subprocess
to stop manually.
All GCM server commands are assigned subprocess names in the
form GCM_nodename_CMDnnnn ,
where nnnn is a command sequence number. Typically,
these subprocesses run to completion, delivering an AST to the GCM
server to let it know that related output can be found in a temporary
log file of the same name as the subprocess. After returning the
result file, the subprocess and its related file are deleted. If
the subprocess is executing a command that does not complete or
that is waiting for input, the GCM server never sees command completion
and never returns results. This does not prevent the GCM server
from performing other duties, but it can lead to unexpected command
behavior.
Future releases of GCM should provide additional command functionality.
However, there will always be a class of command functionality that
cannot be supported. Launching applications with graphical interfaces
or complex interaction is beyond the intended use of GCM. In many
cases, you can create a simple command procedure wrapper to allow
an application to manage its own display redirection.