Demo / Evaluation Software:
Download and save the self-extracting software installation archive (TASKMSTR.EXE - full version / TMLITE.EXE - Lite version) from the Evaluation Software page on avanti's WEB site:

Licensed Software:
Download and save the self-extracting software installation archive (unique DOS 8.3 formatted name - ????????.EXE) from avanti's FTP Server using the instructions provided in the ESD (Electronic Software Delivery) Notice E-Mail sent to the principal End User contact as specified on the order.

Answer the prompts affirmatively to proceed through the installation process.

Notes:
• When prompted to "Choose the location for installing TaskMaster's files," specify the Server name, volume, and path in proper UNC format (i.e., two backslashes preceding the Server name and a single backslash separating the remaining components - Volume and Path).
• The destination directory will be created, if it does not exist.

The Installation Program will confirm successful completion.

Example: LOAD SYS:\SYSTEM\TASKMSTR\TASKMSTR


The above line is entered after the ServerName: prompt on the Server's System Console. If the software was not installed in the default \\ServerName\SYS\SYSTEM\TASKMSTR directory, substitute the appropriate Volume and Path as appropriate.

Note:
• It is advisable to add the LOAD command line to the Server SYS:\SYSTEM\AUTOEXEC.NCF configuration file to insure the NLM is automatically loaded whenever the Server starts.

Among the dozens of Extended Console Commands supported by the TMConsole (Shell) are the following key commands:

Task Scripting:
When loaded, the Batch Processor integrated into the Server Module is capable of processing ASCII text files which contain a series of instructions / commands intended to perform a specific set of operations (a scripted task). The instructions / commands in the file are parsed and interpreted by the integrated Batch Processor which either performs the scripted processing or submits it to the Server System Console to be processed.

The integrated Batch Processor supports a simple English language set of scripting commands which resemble a cross between the DOS Batch and NetWare Login syntax, with enhancements including dynamic variables, system environment variables, user defined variables, IF/WHILE structures, IF/WHILE conditional tests, data manipulation commands, display/file I/O commands, and support for the Extended Console Command set supported by the Server Module.

Task Execution:
Tasks can be executed either manually or as a scheduled process. The TMRUN Extended Console Command is used for manual execution. Scheduled processing can be accomplished using either the TMSCHEDULE Extended Console Command or the TMClient Task Management Windows Client (TMClient.EXE). Tasks can be scheduled to run on a specific date, a specific day of the month, or specific days of the week at a specific time, a specific time after each hour, or at specific intervals.

The SYNC command is as simple to use as the DOS XCOPY command, whether executed directly at the TMConsole (Shell) prompt or within a scheduled task. It not only replicates files / synchronizes data but also the names (DOS / Long / Macintosh / NFS), Ownership, Trustee Rights, DOS attributes, NetWare attributes, Inherited Rights Mask (IRM), and originating Name Space for both directories and files.

A source specification, a destination specification, and the appropriate options are required (no default options are assumed). The source specification can be a file, a file pattern, a directory, or a volume. The only requirement is that it MUST reside on the local Server and MUST be the first specification. The destination can be a directory within the same volume, a directory on a different Volume on the same (Local) Server, or a Volume and directory combination residing on a different Server, even across NDS trees.

The format of the SYNC command is as follows:

SYNC src dest opts [<sync.exc] [>sync.log]

/A		Add source entries that do not exist on destination
/D		Delete entries that exist on the destination but not on source
/H		Hidden / System entries are processed
/I		Ignore non-critical errors (default = Abort on any error)
/Q		Query mode (simulated processing - no changes made)
/S		Subdirectory recursion
/V		Verify destination (replace if different from source)
>sync.log		Redirected processing output (overwrite sync.log)
>>sync.log		Redirected processing output (append to sync.log)
<sync.exc		Redirected exclusion list input (source dirs/files to exclude)

SYNC Example:

SYNC DATA:\*.* RSERVER/DATA:\ /A /D /H /I /S /V
Process the DATA: volume starting at the root (\) and recursing through all subdirectories (/S) adding any entry (directory &/or file) on the source that does not exist on the destination (/A), deleting any entry on the destination that does not exist on the source (/D), process Hidden &/or System entries (/H), ignore any non-critical error (/I - i.e., ignore any open file conflict), and update any destination file which does not match the corresponding source file (/V - Last Modified Date/Time and Size comparison).


Exclusion List:

Using input redirection (<vol:\path\filename.ext), specific files, file patterns, and directories can be excluded from processing. The exclusion list must be an ASCII text file containing one specification per line which matches the source file(s) to be excluded from the SYNC process. Wild cards are supported in the exclusion specification.


The following criteria or rules apply:

• Exclusion entries are specific to the source. Destination entries cannot be excluded.
• NetWare Server or Volume specific system files, such as SYS:\_SWAP_.MEM, SYS\:VOLDATA.TDF, SYS:\VOL$LOG.ERR, SYS:\BACKOUT.TTS, and other common system files, are automatically excluded.
• A generic file pattern (*.JPG) excludes any files in the base source directory which match the pattern. If the /S option is appended to the file pattern (i.e., *.JPG /S), any files matching the file pattern which reside in the subdirectory tree beneath the source are also excluded.
• A path specific file or file pattern (e.g., SYS:\SYSTEM\DS.NLM or SYS:\SYSTEM\DS*.NLM) excludes any files in the specified directory which match (i.e., both examples will exclude the SYS:\SYSTEM\DS.NLM file). If the /S option is appended to the specification (i.e., SYS:\SYSTEM\DS.NLM /S), any files matching the file pattern which reside in the subdirectory tree beneath the specified path (SYS:\SYSTEM) are also excluded.
• A subdirectory specification without wild cards or file pattern (e.g., VOL:\PATH) will exclude all directories and files in the specified subdirectory, including any which reside beneath the specification. It is more efficient to specify only the subdirectory instead of the subdirectory with a generic all file wild card (i.e., VOL:\PATH is more efficient than VOL:\PATH\*.*) as both provide the same exclusion results but the wild card specification requires additional processing.



Input redirection of an exclusion file must follow all other options (except output redirection). A valid file specification must be provided (no wild cards). The file specification can be either fully qualified (vol:path) or relative to the Current Working Directory (CWD).




Log Processing Activity:

By default, SYNC will create a screen and display what processing occurs which can be redirected to a file for logging purposes by appending an output redirection option (>vol:\path\filename.ext - similar to DOS but using NetWare Volume:\Path format rather than Drive:\Path - use > to overwrite an existing log file or >> to append to an existing log file - either method will create the file if it does not already exist). Output redirection to a log file must follow all other options.