Changes between Version 2 and Version 3 of statmgr


Ignore:
Timestamp:
01/31/12 07:56:48 (10 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • statmgr

    v2 v3  
    3232Command names must be typed in the control file exactly as shown in this document (upper/lower case matters!). 
    3333 
    34 == EXAMPLE CONFIGURATION FILE == 
     34=== EXAMPLE CONFIGURATION FILE === 
    3535{{{ 
    3636 
     
    158158}}} 
    159159 
    160 == FUNCTIONAL COMMAND LISTING == 
     160=== FUNCTIONAL COMMAND LISTING === 
    161161 
    162162Below are the commands recognized by statmgr, grouped by the function they influence. Most of the commands are required. 
     
    176176                LogFile                 required 
    177177 
    178 == ALPHABETIC COMMAND LISTING & DESCRIPTION == 
     178=== ALPHABETIC COMMAND LISTING & DESCRIPTION === 
    179179 
    180180In the following section, all configuration file commands are listed in alphabetical order. Listed along with the command (bold-type) are its arguments (in red), the name of the subroutine that processes the command, and the function within the module that the command influences. A detailed description of the command and is also given. Default values and example commands are listed after each command description. 
     
    262262description is the default text string (up to 79 characters) that statmgr will report for this error code. Enclose the string in double-quotes if it contains embedded blanks. Each module may include a (hopefully more informative) text string in its error message; if so, that string overrides the default, description. 
    263263 
    264 == Helpful Hints ==''' 
     264== Helpful Hints ==