Docstoc

Global Command Line Arguments

Document Sample
Global Command Line Arguments Powered By Docstoc
					Global Command Line Arguments
In addition to the -i command line argument global recognises several other
parameters. The complete list, in alphabetic rather than functional order, is as
follows. The Bacnat Variant the option first appeared, is in brackets.


      -a            Re-attach to running glintd (3.207);

The –a option can be used to allow global to attach to an existing glintd background
process, rather than initiating a new glintd. Warning: This option must be used with
great care because glintd has not direct reference its parent global task. Using this
option under the wrong circumstances may inadvertently “take over” an existing
GSM (Unix) session.



      -b            Suppress execution of background glintd (3.227);

Use of the -b command line argument, which suppresses execution of the
background glintd process, thus allowing a debug version to be executed, is a
specialised technique which is beyond the scope of this manual and is documented
here for completeness only. DO NOT ATTEMPT TO USE THIS OPTION.



      -c            Allows a core dump to be generated (3.183);

       Use of the -c command line argument is a specialised technique which is fully
described below:

By default, the Global System Manager glintd process captures all Unix signals.
Those signals that are unexpected and cause glintd to die are displayed in a
message of the form:

      glintd: Error 1217 - Process terminated due to signal SIGxxxx

Occasionally, in order to investigate a problem that results in an Error 1217, a
special BACNAT will be produced by compiling the various sources that comprise
Global System Manager (Unix) with the debug option of the Unix c compiler. The
special BACNAT will be recognised by the inclusion of the phrase "DEBUG" in the
familiar message:

      Configuring Global System Manager (Bnnnn Vn.nnn); please wait

For example:

      Configuring Global System Manager (SCODEBUG V3.188); please wait

The global -c option must be used to run Global System Manager in a manner that
will result in the production of a Unix core dump with a special "debug BACNAT"
under the conditions that would normally result in an Error 1217 with a standard
BACNAT.

THIS OPTION SHOULD ONLY BE USED WITH A SPECIAL DEBUG BACNAT
AND ONLY IF YOU BEEN INSTRUCTED TO DO SO BY THE SERVICE CENTRE.

In order to check the "debug BACNAT" has been installed correctly and the global -c
option has been recognised a special (and extremely dangerous) program, CRASH,
is available (from the Service Centre) which will cause a SIGSEGV with a standard
BACNAT; or the production of a Unix core dump, if the global -c option has been
used with a "debug BACNAT". To protect against injudicious use, the CRASH utility
will only produce the desired effect (i.e. a SIGSEGV or a Unix core dump) if the
special GSM_CRASH Unix shell variable is set, to any value, and exported. For
example, if you are using the Bourne shell:

      GSM_CRASH="YES";export GSM_CRASH

THIS SHELL VARIABLE SHOULD ONLY BE SET "BY HAND" IN ORDER TO
TEST THE CRASH UTILITY AND SHOULD NEVER APPEAR IN A LOGIN
SCRIPT.



      -d            display diagnostic information (3.123);

The -d command line argument causes global to display various diagnostic
information during the Global System Manager initialisation process. This option also
results in more detailed diagnostic messages written to the $GLDIR/sys/messages
file.



      -e            Disables 32 bit option (3.317);

The –e option can be used to disable the GSM 32-bit run-time option. It may be
required for some non-PM GSM configurations that have not installed a 32-bit
software licence.



      -f            Use when logging on using GX (3.317);

The –f option MUST be used if GSM (Unix) is started from the telnet emulator within
the GX.EXE (or AX.EXE) thin-client. Note that GX/AX connections to GSM (Unix) are
normally made directly from the GX Connection Window, which bypasses the initial
telnet session, so this option should be considered as specialised.



      -F            Use when logging on using OneOffice 3000 WorkSpace
                    (3.348);

      The –F option MUST be used if GSM (Unix) is started from the telnet emulator
      within the OneOffice 3000 WorkSpace (OO3KWS) client. Note that OO3KWS
      connections to GSM (Unix) are normally made directly from the OO3KWS
      Connection Window, which bypasses the initial telnet session, so this option
      should be considered as specialised



      -g            Leaves glspad running (3.206);

      Use of the -g command line argument is a specialised technique which is fully
      described below:

      The global program distributed with BACNAT variant V3.206, and later,
      recognises the "-g" command line option. When this option is specified, the
      glspad daemon process, which is only used when the first user runs Global
      System Manager, is not killed once it has been used to initiate the other
      daemon processes (e.g. gltimd, glspod, glprid). This option is required to
      enable the special glspod retry mechanism described below:

On some AIX V4.1 configurations, the Global System Manager spooled printers were
found to be stopping for no apparent reason. An investigation showed that the
problem was caused by the Unix system() function returning an error when invoked
by the glspod daemon to execute the spooler command derived from the Systems
file. The cause of the problem could not be found and the simplistic retry mechanism
in glspod (i.e. retry the command a number of times) did not provide a work-around.

The glspod daemon distributed with BACNAT variant V3.206, and later, contains a
more sophisticated retry mechanism which appears to provide a work-around for this
intractable problem. If the simple retry mechanism fails to initiate the system()
function successfully, glspod will save the current Unix command (e.g. lp filename) in
the file $GLDIR/sys/spool/retry. The glspod daemon will then invoke another copy of
itself using the glspad spawner daemon The new invocation of glspod will
commence by retrying the original command before considering any more
outstanding spooled printer requests. This new retry mechanism is enabled
automatically but can only function if the global -g option has been used to leave the
glspad daemon running (i.e. in the global -g option is the switch that enables this
new retry mechanism). The implementation of this new retry mechanism has
resulted in the creation of several new diagnostic and error messages:

glspod: Diagnostics 2024 - Command retry mode enabled

      This message confirms that glspod has detected the "global -g" option. The
      spooler command retry mode has been enabled (see sections G.107 and
      G.109).

glspod: Diagnostics 2025 - Retry file detected, previous command will be
retried
      The glspod initialisation code has detected the presence of the spooler retry
      file:

             $GLDIR/sys/spool/retry

      The previous spooler command (that failed when a previous instance of
      glspod was running), obtained from the retry file, will be retried immediately.

glspod: Diagnostics 2026 - Retry file opened OK

      See message 2025. The $GLDIR/sys/spool/retry file has been opened
      successfully.

glspod: Diagnostics 2027 - Retry file read OK, command = %s, retry count =
%s

      See message 2025. The previous (failed) spooler command has been
      extracted from the $GLDIR/sys/spool/retry file.

glspod: Diagnostics 2028 - Retry file read failed (command retry aborted)

      See message 2025. The $GLDIR/sys/spool/retry file has been detected but
      the previous (failed) spooler command could not be read from the file. The
      command retry mode has been aborted - glspod will continue normally.

glspod: Diagnostics 2029 - Retry file open failed (command retry aborted)

      See message 2025. The $GLDIR/sys/spool/retry file has been detected but
      could not be opened. The command retry mode has been aborted - glspod
      will continue normally.

glspod: Diagnostics 2030 - Command failed, retry mode in progress

      The current spooler command has failed (even after a small number of
      internal retries). The command will be written to the $GLDIR/sys/spool/retry
      file, then glspod will terminate, invoking another copy of itself (i.e. retry mode
      will be enabled).

glspod: Diagnostics 2031 - Retry file created OK

      See message 2031. The $GLDIR/sys/spool/retry file has been created
      successfully.

glspod: Diagnostics 2032 - Retry file create failed (command retry aborted)

      See message 2031. The $GLDIR/sys/spool/retry file could not be created.
      Command retry mode has been aborted.

glspod: Diagnostics 2033 - Exiting glspod, awaiting new invocation
      See message 2031. The current glspod is about to invoke a new copy of itself
      (before closing down).

glspod: Diagnostics 2034 - New glspod exec failed [%s,%s] (command retry
aborted)

      This message is reserved for future use.

glspod: Diagnostics 2035 - %s spoolnext command was successful:\n%s

      The spooler command was successful. For a correctly functioning spooler
      sub-system, this message should appear at the conclusion of every print
      command (i.e. the spooler log file should consist of matching pairs of 2012
      and 2035 messages).

glspod: Diagnostics 2036 - %s spoolnext retry counter exhausted

      The $GLDIR/sys/spool/retry file includes an internal retry counter. The spooler
      command has been retried a number of times but has failed on every attempt.
      There is no point continuing with the command - retry mode (for the current
      printer command only) has been abandoned.

glspod: Diagnostics 2037 - %s spoolnext retry not possible (no glspad
running)

The previous spooler command failed and should be retried using the
$GLDIR/sys/spool/retry file. However, the glspad daemon is not running because the
"global -g" option was not used to invoke Global System Manager. The absence of
the glspad (spawner daemon) has prevented glspod from invoking another copy of
itself.



      -h            Hibernate During Locks

Use of the -h command line argument is a specialised technique which is beyond the
scope of this manual and is documented here for completeness only. DO NOT
ATTEMPT TO USE THIS OPTION. (3.123);


      -i            install Global System Manager from BACRES (3.123);



      -j            Disables the attempted re-open of the standard TTY device
                    (3.335);

The -j option disables the re-opening of the standard TTY device for stdout and stdin.
This option can be used when GSM (Unix) does not have sufficient permissions to
open these devices. For example when GSM (Unix) is being ruin from a cron job.



      -k            Ignores the results of statfs and always assume that the
                    filing system has 2Gb of free space (3.333);

For various reasons, and for some versions of Unix, the algorithm that is used to
calculate the free-space on filing systems that are much larger than 2Gb can
produce inaccurate results. Typically, the free space displayed by $F and used by $V
when allocating new subvolumes can be dramatically less than the GSM domain
limit of 2Gb, even though the actual free space on the Unix filing system exceeds
2Gb. If the free space on the Unix filing system(s) that hold the GSM domain
directories is larger than 2Gb, the –k option can be used to inform GSM (Unix) to
ignore the results of the statfs function call and to use a “free space” value of 2Gb.




      -l            Turns off most of the writes to the spooler log file (3.206);

This option disables most updates to the $GLDIR/sys/spool/log log file from the
glspod daemon process. Note that some messages, which are written before glspod
has attached to the GSM shared memory, will still appear in this log file.
Nevertheless, the –l option will drastically reduce the size of $GLDIR/sys/spool/log.




      -m            Suppress writing messages to the messages file (3.158);

The -m option prevents global and glintd from writing messages to the
$GLDIR/sys/messages file (It should not normally be necessary to use this option as
messages are written so infrequently that the effect on the performance of Global
System Manager is negligible. However, on large systems the message file may
rapidly increase in size. If the messages file is not deleted on a regular basis by the
System Administrator, the -m option can be used to prevent the file from occupying
too much space in the filing system.



      -n            Disable automatic date/time handling (3.163);

The -n command line argument is of little general use. It may be used to override the
date/time information that is normally supplied automatically by Unix. If the -n option
is used Global System Manager will prompt the user for the date and time.
       -o           Allows a name on the global command line to override the
                    Unix user name (3.336);

The -o option allows a NAME on the global command line to override the Unix User
name. This specialized option may be useful when GSM (Unix) is running as cron
job.



       -p           Display perror diagnostic information (3.220);

The -p command line argument causes global to display various diagnostic
information, using the Unix perror function during the Global System Manager
initiation process.



       -q           Allows a term name on the global command line to override
                    the Unix term shell variable (3.336);

The -q option allows a TERM name on the global command line to override the Unix
TERM shell variable. This specialized option may be useful when GSM (Unix) is
running as cron job.



       -r           Run global with root permissions (3.123);

The -r command line argument allows the glintd daemon to run with root privileges.
This may be necessary under some circumstances (e.g. if $REMOTE (see section
G.71) or SPD (see section G.72) are to be used). The -r option may also be useful in
diagnosing some classes of problems.



       -s           Ignore SIGHUP signal rather then terminating (3.266);

By default global will terminate if it receives a SIGHUP message from Unix. The –s
option can be used to ignore the SIGHUP message.



       -tstring           Pass type-ahead string to Global System Manager
(3.123);

The -t command line argument allows you to pass text to Global System Manager
(via the type-ahead buffer - see Chapter 2 of the Global Configurator Manual). This
technique can be used to execute any of the Global utilities, applications or menu
entries directly from the Unix shell. For example, if you wish to run $STATUS then
you can do so by keying:

       # global -t'$STATUS:'

Where -t informs global that you wish to use the rest of the parameter as a command
to execute. The colon character ":" is used to represent a <CR> as it is not normally
possible to insert a <CR> into a Unix command line argument. Note that the
parameter has been surrounded by single quotes because the characters "$" and ":"
would be treated as special characters by the Unix shell. This shell command will run
the Global utility $STATUS. On exit from $STATUS you will be returned to the Global
System Manager main menu.




       -u             Override new default umask value (3.332);

For BACNAT V3.331, and earlier, the value of the umask variable is 0003. For
BACNAT V3.332, and later, the value of the umask variable is 0000. This change
was to allow applications to specify the precise permissions of a Unix file created
using the Open BDAM Access Method or SVC-61 File Create functions. The –u
option, without any further parameters, can be used to set the umask variable to
0003 for backwards compatibility with BACNAT V3.331, and earlier.



       -vnn           Diskette timeout delay (3.254);

This option can be used to override the default delay period (1 second) that is
normally required before the first read/write operation after an open on a diskette
device. If this delay period is too short Buffer Write errors may be reported on some
diskette operations. For example, to increase the delay to 5 seconds:

# global -v5

       The special value of 0 will suppress all close operations on the diskette device
thus keeping it permanently open.



       -wnn           Wait nn seconds for glintd process (3.123);

During Global System Manager initialisation, the global process spawns the glintd
process and waits for it to respond. Normally, the delay is minimal (i.e. between 1 to
2 seconds) but on a sizeable configuration, with a large number of file-server
SYSTEMs defined in the Systems file, it may take a relatively long time for the first
glintd process to initialise all the file-servers. If the time-out period expires the Global
System Manager initialisation will be aborted. By default, the wait period is 20
seconds. The global -w option may be used to modify this delay. For example, to
increase the delay to 40 seconds:
      # global -w40




      -x            Disable XON/XOFF handshaking (3.123);

Use of the -x command line argument is a specialised technique which is fully
described in section G.70. Important note: This option is not supported by BACNAT
software version V3.313, or later.



      -X            Enable console XON/XOFF flag (3.313);

For BACNAT version V3.313, and later, the XON/XOFF hand-shaking protocol with
the TTY device driver is disabled by default. Note that prior to V3.313 the “global –x”
option (see section 6.3.3.9) was required to disable XON/XOFF hand-shaking. This
change to the default behaviour at the release of BACNAT V3.313 was implemented
to support the interface to GX which requires XON/XOFF hand-shaking to be
disabled. If it is required to enable the XON/XOFF hand-shaking protocol with the
TTY device driver for BACNAT V3.313, or later, the -X option must be used to
explicitly enable the option.



      -y            Clear I0XLAN flag (3.169);

Use of the -y command line argument is a specialised technique which is beyond the
scope of this manual and is documented here for completeness only. DO NOT
ATTEMPT TO USE THIS OPTION.



      -z            Suppress glintd hibernation (3.215).

Use of the -z command line argument is a specialised technique which is beyond the
scope of this manual and is documented here for completeness only. DO NOT
ATTEMPT TO USE THIS OPTION.



Note that unlike the glinstall command line options multiple global command line
options can be specified. For example:

      # global -p -d -r

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:106
posted:3/10/2010
language:English
pages:9
Description: Global Command Line Arguments