rda-python-dscheck 2.0.3__tar.gz → 2.0.5__tar.gz

{rda_python_dscheck-2.0.3 → rda_python_dscheck-2.0.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rda_python_dscheck
-Version: 2.0.3
+Version: 2.0.5
 Summary: RDA python package to add and process batch jobs
 Author-email: Zaihua Ji <zji@ucar.edu>
 Project-URL: Homepage, https://github.com/NCAR/rda-python-dscheck
@@ -14,5 +14,9 @@ License-File: LICENSE
 Requires-Dist: rda_python_common
 Dynamic: license-file
 
-RDA python package to add and process batch jobs.
+# dscheck
+
+Python project to add and process batch jobs for the [NSF NCAR Geoscience Data Exchange (GDEX)](https://gdex.ucar.edu).
+
+The user guide for this utility tool can be viewed at: [User guide](https://gdex-docs-dscheck.readthedocs.io).
 

rda_python_dscheck-2.0.5/README.md

@@ -0,0 +1,6 @@
+# dscheck
+
+Python project to add and process batch jobs for the [NSF NCAR Geoscience Data Exchange (GDEX)](https://gdex.ucar.edu).
+
+The user guide for this utility tool can be viewed at: [User guide](https://gdex-docs-dscheck.readthedocs.io).
+

{rda_python_dscheck-2.0.3 → rda_python_dscheck-2.0.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "rda_python_dscheck"
-version = "2.0.3"
+version = "2.0.5"
 authors = [
   { name="Zaihua Ji", email="zji@ucar.edu" },
 ]

{rda_python_dscheck-2.0.3 → rda_python_dscheck-2.0.5}/src/rda_python_dscheck/dscheck.usg

@@ -2,28 +2,28 @@
 1 INTRODUCTION
 
 Program 'dscheck' is a utility to add, remove, view and process recorded commands
-of other utility programs in Research Data Archive Management System (RDAMS). For
+of other utility programs in Research Data Archive Management System (GDEXMS). For
 delayed execution, or called batch process, of utility programs, 'dsarch', 'dsupdt'
 and 'dsrqst', the commands information and the directories where the commands are
-initiated are saved into RDADB as check records. For any other specialist-defined
+initiated are saved into GDEXDB as check records. For any other specialist-defined
 commands, they can be also put in delayed mode if the commands are added to
 'dscheck' control via Action -AC (-AddCheck).
 
 The check records are processed automatically via a centralized 'dscheck' daemon,
 although they can be processed manually on command line. During the execution of a
-recorded command, the check record is locked in RDADB to prevent multiple executions
+recorded command, the check record is locked in GDEXDB to prevent multiple executions
 of the same command. The check records that retain command information are
 automatically purged into check history when the commands are finished.
 
 When a recorded command fails due to failures of computer system, storage disk/tape,
 or the Database Management System, the check record is normally purged with status 'E'
 for error, unless check-reprocessing ability is built into the utility program, such
-as 'dsarch'. For a check-reprocessing command, the check record is retained in RDADB
-Until the command is processed successfully or the number of executions reaches the
+as 'dsarch'. For a check-reprocessing command, the check record is retained in GDEXDB
+until the command is processed successfully or the number of executions reaches the
 try limits allowed. Utility programs 'dsrqst' and 'dsupdt' carry their own failure-
 recovering ability and they do not need check-reprocessing. 
 
-The purged check records are retained in RDADB. The check history can be viewed via
+The purged check records are retained in GDEXDB. The check history can be viewed via
 utility program 'viewcheckusage'.
 
 Program 'dscheck' supports the following major functions:
@@ -33,21 +33,21 @@ Program 'dscheck' supports the following major functions:
     a check. Without the daemon control information, a recorded command will not be
     started automatically.
   - ADD a check record for delayed command execution of any specialist-defined commands
-  - View utility command information currently saved in RDADB
+  - View utility command information currently saved in GDEXDB
   - Email the current status of a specified utility command or a list of commands,
     and include error messages if any, to a specialist
   - Delete recorded command information, because the command is not needed anymore
   - Unlock a given recorded command in case lock information was not cleaned
-    properly when the command was failed
+    properly when the command has failed
   - Interrupt a utility command that is under execution and kill recursively all
     the associated child processes
   - Add the due 'dsrqst' and 'dsupdt' actions into dscheck records
-  - Process commands that have been recorded into RDADB or the ones have failed
-    previously.
+  - Process commands that have been recorded into GDEXDB or the ones that have
+    failed previously.
 
 The specialist who executes a utility command under 'dscheck' control remains
-the exclusive owner of the check record in RDADB. This prevents the command to be
-processed or deleted accidentally by other specialists. 
+the exclusive owner of the check record in GDEXDB. This prevents the command from being
+processed or deleted accidentally by other specialists.
 
 In the following sections, general usages of 'dscheck' are described first; and
 detail descriptions of Action options are given; and finally Mode and Info
@@ -62,7 +62,7 @@ options are explained.
 Quotes [] indicate optional. A pipeline '|' in parentheses as in format (A|B)
 means either A or B can be used. The options applied to 'dscheck' are divided
 into three categories, Action, Mode, and Information (Info for short) options. 
-Action options are used to specify what tasks this utility program to execute,
+Action options are used to specify what task this utility program is to execute,
 Mode options are used to modify behaviors of the actions, and the Info options 
 are used to pass information, one or multiple values, to run 'dscheck'. An option
 can be given in form of either short name or long name, -DS or -Dataset for
@@ -77,18 +77,18 @@ and certain Mode options can be applied to alter the behaviors of the Action.
 
 All options, except Info option -IF (-InputFile), can be given either on command
 line or in input files. Input file names are presented per Info option -IF and
-can only be provided on command line. Referring to description of Info option -IF
-(-InputFile) for detail on how to present options in input files.  One or multiple
+can only be provided on command line. Refer to the description of Info option -IF
+(-InputFile) for details on how to present options in input files.  One or multiple
 input files, combined with options on command line, are allowed to run 'dscheck'.
 The option name, -IF (-InputFile), itself can be omitted if a single input file is
 given on command line and all other option information are provided inside the
 input file.
 
 When information of daemons and checks are retrieved, Info options are used to
-specify conditions for querying information from RDADB. Some special signs can be
+specify conditions for querying information from GDEXDB. Some special signs can be
 used to further confine the information with special and complicated conditions;
 they are '!', '<', '>' and '<>'.  These special signs, if provided on command
-line,  must be quoted or escaped to avoid of being interpreted by Unix OS system.
+line,  must be quoted or escaped to avoid being interpreted by the Unix shell.
 The '!', or \!, means exclusion to the following value(s) and it must be the
 first item following an Info option name, while '<' or '>' mean greater or less
 than the following value and '<>' means between the following two values.
@@ -102,11 +102,11 @@ command line as
 
 A description is displayed for an option given either before or after -(h|help).
 If no option is specified or 'dscheck' is issued by itself, this whole document
-is displayed per UNIX utility 'more'. A hard copy of this help document can be
-printed from the saved file: ${DSSHOME}/dssdb/prog_usage/dscheck.usg.
+is displayed via UNIX utility 'more'. A hard copy of this help document can be
+printed from the saved file, dscheck.usg, under python package rda_python_dscheck.
 
 #The online HTML version of this document is available at
-#http://dss.ucar.edu/internal/docs/dscheck/
+#https://gdex-docs-dscheck.readthedocs.io
 
 
 3 ACTION OPTIONS
@@ -117,27 +117,27 @@ simultaneously are blocked.
 
 Based on the information being manipulated, the actions are divided into three
 categories:
-  Daemon Control Actions - create, delete, modify and view daemon control information
-                           in RDADB, of specified specialist, command and hostname
-           Check Actions - add, delete, unlock and view check information of the
-                           active individual checks
-   Check Process Actions - process checks by starting commands on remote hosts as
-                           configured in daemon controls and purge checks by recording
-                           the commands and their execution information into check
-                           history; interrupt the current executing commands by killing
-                           the current process and its all children; and email status
-                           of current checks
+   Daemon Control Actions - create, delete, modify and view daemon control information
+                            in GDEXDB, of specified specialist, command and hostname
+            Check Actions - add, delete, unlock and view check information of the
+                            active individual checks
+    Check Process Actions - process checks by starting commands on remote hosts as
+                            configured in daemon controls and purge checks by recording
+                            the commands and their execution information into check
+                            history; interrupt the current executing commands by killing
+                            the current process and its all children; and email status
+                            of current checks
  Daemon Host Connectivity - check connectivity of daemon hosts for specialists
 
 3.1 Daemon Control Actions
 
   A daemon control record for a command, a specialist and a hostname is used to
   configure how many concurrent processes the specified command can be executed
-  for the specialist on specified hostname, and the priority the the hostname is
+  for the specialist on specified hostname, and the priority the hostname is
   picked to start the command. A running centralized daemon reads this record
   periodically in case the configuration is changed while the daemon is still
   running, so that specialists can reset the values in daemon control records to
-  change the behave of dscheck daemon dynamically without shutting the daemon down.
+  change the behavior of dscheck daemon dynamically without shutting the daemon down.
 
   Daemon control information can be created, modified and viewed via Actions
   included in this section:
@@ -148,7 +148,7 @@ categories:
 
 3.1.1 Set Daemon Control
   -SD or -SetDaemon, creates and modifies daemon control information into
-  RDADB for given specialist login names, commands, and hostnames of computers on
+  GDEXDB for given specialist login names, commands, and hostnames of computers on
   which the check commands are processed. One or multiple records can be set each
   time.
 
@@ -162,13 +162,13 @@ categories:
          [-(PO|Priority) HostListOrder]
 
   Mode option that can be specified for this action include:
-  -(ND|NewDaemon) - sets a new daemon control record into RDADB
+  -(ND|NewDaemon) - sets a new daemon control record into GDEXDB
 
-  If information of a daemon control exists already in RDADB for a given specialist,
+  If information of a daemon control exists already in GDEXDB for a given specialist,
   a command and a hostname, the daemon control record is modified; otherwise, a new
   daemon control record is added if daemon index is 0 and Mode option -ND (-NewDaemon)
   is present. Combination of specialist login name, command name and hostname of
-  computer must be unique for for each daemon control record.
+  computer must be unique for each daemon control record.
 
   Specify host name 'PBS' for putting the command in the PBS batch control system. If
   a specified command name is not found in the daemon control, the general 'dscheck'
@@ -176,12 +176,12 @@ categories:
   
   For example, set daemon control information for schuster, all commands on PBS hosts,
   for maximum 4 checks can be processed at the same time with priority 1, the smaller
-  the number the higher the priority is, via input file daemon.ctl
+  the number the higher the priority is, via input file daemon.ctl:
 
-  dsrqst SD -ND -IF daemon.ctl
+  dscheck -SD -ND -IF daemon.ctl
 
 <<Content of input file daemon.ctl>>
-DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
+DaemonIndex<:>Specialist<:>Command<:>Hostname<:>ProcessLimit<:>Priority<:>
 0<:>schuster<:>ALL<:>PBS<:>4<:>1<:>
 
 
@@ -217,11 +217,11 @@ DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
   I      -(DI|DaemonIndex)      daemon control index
   C      -(CM|Command)          command names of utility programs
   H      -(HN|Hostname)         computer hostname
-  M      -(MH|MatchHost)        Flage to control hostname match
+  M      -(MH|MatchHost)        Flags to control hostname match
   S      -(SN|Specialist)       DECS specialist the daemon set for
   P      -(PL|ProcessLimit)     Max check count to be processed at the same times
   O      -(PO|Priority)         host priority a specified command to start on
-  
+
   Daemon control information can be retrieved for specified specialist per option
   -SN (-Specialist), and/or other conditions. Info option -SN, -CM and -HN accept
   wildcard input of '%' for matching any number of characters. 
@@ -232,14 +232,14 @@ DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
   option -SN (-Specialist). To view all control records, you simply provide option
   -SN with value of 'ALL'.
   
-  For example, to get all daemon control information currently set for you
+  For example, to get all daemon control information currently set for you:
   
   dscheck GD
 
 
 3.1.3 Delete Daemon Control
   -DL or -Delete (Alias: -RM, -Remove), deletes one or multiple daemon control records
-  from RDADB for given daemon control indices. 
+  from GDEXDB for given daemon control indices. 
  
   dscheck -(DL|Delete)
           -(DI|DaemonIndex) DaemonControlIndices
@@ -289,7 +289,7 @@ DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
   as the owner of the added check record, and the current path is defaulted as the
   working directory when the command is executed later.
 
-  Specified addtional PBS batch options via Info option -QS (-QSubOptions) to add a check;
+  Specify additional PBS batch options via Info option -QS (-QsubOptions) to add a check;
   and specify a parent check index to put the current command on hold until the parent
   check is finished.
 
@@ -297,29 +297,33 @@ DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
   A simple shell script can be used to wrap a complicated command. 
   
   For example, to list file names in the current directory with name containing 'test'
-  by catching the standard output into a log and display it on screen
+  by catching the standard output into a log and display it on screen:
+  
+  dscheck -AC -CM test1.sh -HN PBS
 
 <<Content of shell script test1.sh>>
 #!/bin/sh
 (ls -l | grep test) | tee test1.out
 
   For example, to list file names in the current directory with name containing 'test'
-  by catching the standard output and error into separate log files
- 
+  by catching the standard output and error into separate log files:
+
+  dscheck -AC -CM test2.sh -HN PBS
+
 <<Content of shell script test2.sh>>
 #!/bin/sh
 (ls -l | grep test) 1> test2.out 2>test2.err
 
   For example, to add testing command 'test2' into 'dscheck' for delayed mode execution on
-  PBS
+  PBS:
 
-  dsheck AC -CM test2 -HN PBS
+  dscheck -AC -CM test3 -HN PBS
 
-  The command 'test2' must be executable at the current working directory on PBS machines.
+  The command 'test3' must be executable at the current working directory on PBS machines.
 
 
 3.2.2 Get Check
-  -GC or -GetCheck, gets check information recorded in RDADB.
+  -GC or -GetCheck, gets check information recorded in GDEXDB.
 
   dscheck -(GC|GetCheck) [Mode Options]
          [-(FN|FieldNames) FieldNameString]
@@ -343,7 +347,7 @@ DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
                        of a given field
 
   Use Info option -FN (-FieldNames) to specify what check fields to retrieve.
-  It defaults to "COVTUFJDNW" if -FN is not given.
+  It defaults to "COVTUPFJDNW" if -FN is not given.
 
   Valid check field names and their corresponding Info options:
 
@@ -354,21 +358,21 @@ DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
    T     -(DS|Dataset)         dataset ID, the original command run against
    A     -(AN|ActionName)      action name for a given command
    U     -(ST|Status)          check status for a recorded command
-   B     -(DF|DownFlags)       Storage system down flags: H-HPSS,D-DRDATA,G-GLADE,O-ObjectStore
-   P     -(PQ|PBSQueue)        PBS batch queue name: rda or htc
+   B     -(DF|DownFlags)       Storage system down flags: D-DRDATA,G-GLADE,O-ObjectStore
+   P     -(PQ|PBSQueue)        PBS batch queue name: gdex or htc
    R     -(PI|ParentIndex)     parent check index the current one to wait on
    F     -(FC|FileCount)       number of files need to be processed
    J     -(DC|DoneCount)       number of files are processed already
    K     -(TC|TryCount)        number of tries the command is executed
    L     -(MC|MaxCount)        upper limit for number of command tries
-   Z     -(SZ|DataSize)        total tytes of data processed for the command
+   Z     -(SZ|DataSize)        total bytes of data processed for the command
    D     -(CD|CheckDate)       date the command is initially recorded
    Y     -(CT|CheckTime)       time the command is initially recorded
    H     -(HN|HostName)        host names the command can or cannot run on
    N     -(SN|Specialist)      specialist login name who starts the command
    W     -(WD|WorkDir)         working directory where the command is started
    M     -(MO|Modules)         include modules to load to batch job script
-   I     -(EV|Environments)    include environment vairables to load to batch job script
+   I     -(EV|Environments)    include environment variables to load to batch job script
    Q     -(QS|QsubOptions)     additional PBS batch options for qsub
    X     -(AX|ArgumentExtra)   additional argument line beyond 100 characters
    E     -(ER|ErrorMessage)    error message from failed command
@@ -379,7 +383,7 @@ DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
 
 
 3.2.3 Delete Check
-  -DL or -Delete, deletes one or multiple 'dscheck' records from RDADB 
+  -DL or -Delete, deletes one or multiple 'dscheck' records from GDEXDB 
   for given check indices.
  
   dscheck -(DL|Delete)
@@ -391,23 +395,23 @@ DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
 
 
 3.2.4 Unlock Check
-  -UL or -UnLockCheck, (Alias: -UnLock), unlocks check records that their
-  commands aborted abnormally during processes.
+  -UL or -UnLockCheck, (Alias: -UnLock), unlocks check records whose
+  commands aborted abnormally during processing.
   
   Process ID and computer hostname are saved in a check record when the recorded
   command is running. If the process aborts abnormally, the PID and hostname may
   sometimes be not cleaned properly. Use this action to clean up the locking
   information to allow the command to be reprocessed or purged.
 
-  dscheck -(-UL|UnLockCheck)
-           -(CI|CheckIndex) CheckIndices
-          [-(DB|Debug) DebugModeInfo]
+  dscheck -(UL|UnLockCheck)
+          -(CI|CheckIndex) CheckIndices
+         [-(DB|Debug) DebugModeInfo]
 
   It is mandatory to provide a check index to remove lock on a recorded command.
 
 
 3.3 Check Process Actions
-  Delayed mode command executions recorded in RDADB are automatically started,
+  Delayed mode command executions recorded in GDEXDB are automatically started,
   or restarted, by the common 'dscheck' daemon. Running commands can be interrupted
   at any time and the child processed of the interrupted commands are also cleaned up.
   The status of the current check records can be gathered and emailed to a specialist.
@@ -454,13 +458,13 @@ DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
   according to the configured information in daemon controls.
   
 3.3.2 Interrupt Check
-  -IC or -InterruptCheck, interrupts checks that their commands are currently running
-  and also kills recursively all the child processes that are running under the
+  -IC or -InterruptCheck, interrupts checks whose commands are currently running
+  and also kills recursively all the child processes running under those
   commands. Locks are cleaned too when the checks are interrupted.
 
-  dscheck -(-IC|InterruptCheck) [Mode Option]
-           -(CI|CheckIndex) CheckIndices
-          [-(DB|Debug) DebugModeInfo]
+  dscheck -(IC|InterruptCheck) [Mode Option]
+          -(CI|CheckIndex) CheckIndices
+         [-(DB|Debug) DebugModeInfo]
 
   Mode option that can be specified for this action:
   -(FI|ForceInterrupt) - it must be present for this action to interrupt a check
@@ -518,13 +522,13 @@ Use proper Mode options to modify behaviors of Action options. Mode options
 are all optional. No value is allowed to be passed in following any Mode option.
 
   -AW or -AnyWhere, for Action -AC (-AddCheck), sets Working directory empty in
-  cehck record to start processing the check anywhere.
+  check record to start processing the check anywhere.
 
-  -BG or -BackGround (Alias: -b), background process. When it presents
-  screen display is turned off for both standard outputs and errors. -(CP|CheckPending) - Check and kill long pending checks
-  
-  -CP or -CheckPending, if present for Action -PC (-ProcessCheck), check and kill
-  long pending checks
+  -BG or -BackGround (Alias: -b), background process. When it is present,
+  screen display is turned off for both standard output and errors.
+
+  -CP or -CheckPending, if present for Action -PC (-ProcessCheck), checks and kills
+  long pending checks.
 
   -CS or -CheckStatus, if present, displays detailed status information of the
   recorded commands, including progress percentage for a running command and
@@ -545,7 +549,7 @@ are all optional. No value is allowed to be passed in following any Mode option.
   a given dataset listed for another specialist.
 
   -NC or -NoCommand (Alias: -NoRemoteCommand), does not issue remote commands if
-  this Mode option is present for action -PC (-Processcheck).
+  this Mode option is present for action -PC (-ProcessCheck).
 
   -ND or -NewDaemon, a new daemon control can only be added when this Mode option is
   present and daemon control index is given as 0 when Action -SD (-SetDaemon) of
@@ -558,7 +562,7 @@ are all optional. No value is allowed to be passed in following any Mode option.
   -WR or -WithdsRqst, adds requests due to be built or purged of command 'dsrqst'
   for 'dscheck' Action -PC (-ProcessCheck) in non-daemon mode.
   
-  -WU or -WithdsUpdt, adds due update controls of command 'dsrqst' for 'dscheck' 
+  -WU or -WithdsUpdt, adds due update controls of command 'dsupdt' for 'dscheck'
   Action -PC (-ProcessCheck) in non-daemon mode.
 
 5 INFORMATION OPTIONS
@@ -593,7 +597,7 @@ Information options are used to pass information, one or multiple values, into
   action -PC(-ProcessCheck). It defaults to '' to use the local host name. Specify
   PBS to process batch jobs.
 
-  -MT or -MaxrunTime, specify the maxmum run time for deamon mode. It defaults to 0
+  -MT or -MaxrunTime, specify the maximum run time for daemon mode. It defaults to 0
    for unlimit time. For examples, 5000 means seconds, and 1D means 1 day for 86400
    seconds.
 
@@ -633,7 +637,7 @@ Information options are used to pass information, one or multiple values, into
  
   -CD or -CheckDate, the check date of the recorded command is first processed.
   
-  -CI or -CechkIndex, check record indices for commands recorded in RDADB. A check
+  -CI or -CheckIndex, check record indices for commands recorded in GDEXDB. A check
   record is automatically purged if the command is finished.
 
   -CM or -Command (Alias: -CommandName), the command name recorded in check record.
@@ -646,14 +650,14 @@ Information options are used to pass information, one or multiple values, into
   single integer value, for example, 1000 means to log debug messages for debug
   levels 1 to 1000; or a range of values, for example, 200-1000 means to log
   debug messages from debug levels 200 to 1000. The default debug file path is
-  '$DSSHOME}/dssdb/log' and the default debug file name is 'mydss.dbg'. Provides
-  the second and third values for this option to override the default ones
+  '${DSSHOME}/dssdb/log' and the default debug file name is 'mydss.dbg'. Provide
+  the second and third values for this option to override the defaults
   respectively.
 
   -DC or -DoneCount, the number of files that are processed successfully already.
 
   -DF or -DownFlags, storage system down flags. The current supported flags are:
-  H-HPSS, D-DRDATA, G-GLADE, O-ObjectStore. It can hold multiple flags, up to 5,
+  D-DRDATA, G-GLADE, O-ObjectStore. It can hold multiple flags, up to 5,
   for all down storage systems.
 
   -DI or -DaemonIndex, daemon control indices. A daemon control record retains
@@ -666,7 +670,7 @@ Information options are used to pass information, one or multiple values, into
  
   -EV or -Environments, (Alias: -Envs), specifies environment variables, in form of 
   VarName=VarValue and separated by ',', needed to be set to execute a command as
-  a batch job. The environment varaibles will be set in the batch starting script.
+  a batch job. The environment variables will be set in the batch starting script.
 
   -FC or -FileCount, the number of files to be processed by a check command.
   
@@ -685,7 +689,7 @@ Information options are used to pass information, one or multiple values, into
   option -AO (-ActOption, default to <!>); and different equal sign of single
   value assignment can be provided by Info option -ES, (-EqualSign, default to
   '<=>'). Multi-value assignments can be given in columns delimited with
-  separator specified per option -SP (-Separator, default to '<:>'). It starts
+  separator specified per option -DV (-Divider, default to '<:>'). It starts
   with a column title line for multi-value option names and the rest holds
   values corresponding to each column titles. The value information stops at
   the end of the file or when a new column name line or another single value
@@ -693,11 +697,11 @@ Information options are used to pass information, one or multiple values, into
   additional separator must be appended for each line, including the column
   title line to end lines properly.
 
-  -MC or -MaxCount, the maximum number of tries for a check command can be processed
-  if the command is failed.
+  -MC or -MaxCount, the maximum number of tries a check command can be processed
+  if the command has failed.
 
   -MH or -MatchHost (Alias: -MatchHostname), flag to control hostname match.
-  'G' - general match, including emty hostname specified, or exclusive hostnames
+  'G' - general match, including empty hostname specified, or exclusive hostnames
   given but the hostname is not in the list, and 'M' - match only the hostname
   specified is identical to the current host.
 
@@ -718,7 +722,7 @@ Information options are used to pass information, one or multiple values, into
   -PQ or -PBSQueue, specifies PBS batch queue index the current check to submit to.
 
   -QS or -QsubOptions, (Alias: -PBSOptions), specifies options to execute a command
-  as a batch job via qsub on PBS nodes. The qsub options must be quoted when prsented
+  as a batch job via qsub on PBS nodes. The qsub options must be quoted when presented
   on command line, such as, -QS '-l walltime=12:00:00'.
   
   -SN or -Specialist, the specialist who runs the original command. This Info
@@ -728,7 +732,7 @@ Information options are used to pass information, one or multiple values, into
   -ST or -Status, check command status for a check record. Include command
   progress percentage if under process and error message for a failed command.
   
-  -SZ or -DataSize, the total bytes of data is processed for the check record.
+  -SZ or -DataSize, the total bytes of data processed for the check record.
 
   -TC or -TryCount, the number of tries for a check command being processed. It
   is up to the number of tries specified via info option -MC. 

{rda_python_dscheck-2.0.3 → rda_python_dscheck-2.0.5}/src/rda_python_dscheck/pg_check.py

@@ -48,7 +48,7 @@ class PgCheck(PgOPT, PgCMD):
          'FI': [0, 'ForceInterrrupt', 0],
          'FO': [0, 'FormatOutput',  0],
          'LO': [0, 'LogOn',         0],
-         'MD': [0, 'PgDataset',     3],
+         'MD': [0, 'MyDataset',     3],
          'NC': [0, 'NoCommand',     0],
          'ND': [0, 'NewDaemon',     0],
          'NT': [0, 'NoTrim',        0],

{rda_python_dscheck-2.0.3 → rda_python_dscheck-2.0.5}/src/rda_python_dscheck.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rda_python_dscheck
-Version: 2.0.3
+Version: 2.0.5
 Summary: RDA python package to add and process batch jobs
 Author-email: Zaihua Ji <zji@ucar.edu>
 Project-URL: Homepage, https://github.com/NCAR/rda-python-dscheck
@@ -14,5 +14,9 @@ License-File: LICENSE
 Requires-Dist: rda_python_common
 Dynamic: license-file
 
-RDA python package to add and process batch jobs.
+# dscheck
+
+Python project to add and process batch jobs for the [NSF NCAR Geoscience Data Exchange (GDEX)](https://gdex.ucar.edu).
+
+The user guide for this utility tool can be viewed at: [User guide](https://gdex-docs-dscheck.readthedocs.io).
 

rda_python_dscheck-2.0.3/README.md

@@ -1,2 +0,0 @@
-RDA python package to add and process batch jobs.
-