Netware Super Library

home *** CD-ROM | disk | FTP | other *** search

/ Netware Super Library / Netware Super Library.iso / timevent / taskmstr / manual.doc < prev next >

Wrap

Text File | 1995-05-07 | 75.2 KB | 2,044 lines

TaskMaster v1.12 ---------------- The following documentation is specific to the TaskMaster product developed by Avanti Technology, Inc. Overview: --------- TaskMaster is designed to provide an enhanced batch processor and task scheduler for NetWare v3.11, v3.12, & v4.0x servers. Scheduled task definition and initialization must be performed on a workstation using the TASKMSTR.EXE utility program. The TaskMaster NLM also adds a command line batch processor to NetWare. Once loaded, TaskMaster will process the commands in standard .NCF files, as well as those using the TaskMaster superset of batch commands listed below, merely by typing RUN [batch] at the console or scheduling the task through the TaskMaster client (.EXE) utility. The default extensions, if not specified, is .NCF and .TSK (in order). The default search path, if not specified, is the vol:path from which the TaskMaster NLM was loaded, the SYS:\SYSTEM directory, and the P=/PATH= vol:path, if provided as a command line option during TaskMaster load (in order). TaskMaster initiated batch files or tasks can be manually terminated by entering ABORT [batch] at the server console. Installation: ------------- 1). Create the destination network directory where the files are to be copied, if necessary. e.g.: md z:\public\taskmstr 2). Copy the files from the root (licensed copy) or TASKMSTR (demo/eval copy) subdirectory on the distribution diskette to the destination directory. e.g.: copy a:[source_dir]\*.* z:\public\taskmstr 3). Determine if the TaskMaster NLM is to be loaded from the NetWare default SYS:\SYSTEM directory or from the TaskMaster network directory. If the TaskMaster NLM is to be loaded from the NetWare default SYS:\SYSTEM directory, copy the TASKMSTR.NLM and TASKMSTR.SCH files to the SYS:\SYSTEM directory. [NOTE: The TaskMaster Master Log File is written to the same directory from which the NLM is loaded. Therefore, if the NLM is copied to/loaded from the SYS:\SYSTEM directory, the Master Log File will also reside in the SYS:\SYSTEM directory.] 4). Load the TaskMaster NLM (TASKMSTR.NLM) on the server using the LOAD command (at the server console or via a remote console utility such as RCONSOLE) specifying the desired options. e.g.: load taskmstr [option] [option]... (in SYS:\SYSTEM) e.g.: load [path\]taskmstr [option] [option] ... (not in SYS:\SYSTEM) e.g.: load [vol:path\]taskmstr [option] [option] ... (not on the SYS: volume) [NOTE: If the message 'Loader unable to resolve public symbol ...' appears, an old CLIB is loaded on the server. TaskMaster requires CLIB v3.11 revision D, dated 12/16/92, or later.] [NOTE: To review the modules loaded on the server, including the CLIB information, type MODULES at the console. The latest CLIB can usually be found in the file LIBUPx.EXE where the x is a numeric value representing the upload sequence for the NetWare library file updates. LIBUPx.EXE is available on CompuServe either in the NOVFILES forum or in Library 7 of the NOVLIB forum.] 5). Confirm proper installation by executing the TaskMaster client utility (TASKMSTR.EXE) as a File Server Console Operator (assigned through the Supervisor Options in SYSCON) or the system's SUPERVISOR. If properly installed, any File Server Console Operator can access the TaskMaster schedule information through the TaskMaster client (.EXE) utility. 6). Creating a Scheduled Task To schedule a new Task, press the Insert (INS) key or select the 'Insert/Add' option from the Tasks menu bar pull-down option list. At this point, a dialog box appears prompting the user to 'Select a Task Type.' The supported choices are as follows: Date Task Performed on a specific date (mm/dd) Weekly Task Performed one or more days each week (Sun - Sat) Monthly Task Performed on a specific day of the month (1 - 31) The following is a list of the fields required for a Date Task: Date Month and Day to execute the Task Time The time or frequency that the Task file should be processed TaskFile The name of the Task file to process The following is a list of the fields required for a Monthly Task: Date Day of the month to process the task Time The time or frequency that the task file should be processed TaskFile The name of the Task file to process The following is a list of the fields required for a Weekly Task: Sun-Sat Days on which to process the Task Time The time or frequency that the Task file should be processed TaskFile The name of the Task file to process To select a Task type, position the highlighted bar over the desired type and press Enter (the highlighted bar will move in response to the Up/Down arrow keys) or place the pointer over the desired type and press the left mouse button. At this point, the Task scheduler logic places the user in the Modify mode for editing the newly created Task (see Modifying a Scheduled Task). 7). Modifying a Scheduled Task To modify a scheduled Task, place the pointer on the desired Task and press the left mouse button or position the highlighted bar over the desired Task and press Enter (the highlighted bar will move in response to the Up/Down arrow keys). At this point, a dialog box appears displaying the current or, if a newly created Task, the default Task scheduling information. Depending upon the Task type (Date, Monthly, or Weekly), the prompt will be positioned as follows: Date Task At the Date column awaiting a valid date Monthly Task At the Date column awaiting a valid day of the month Weekly Task At the Sunday column awaiting the selection of the days of the week on which the Task should be executed [NOTE: It is possible to bypass this entry, or any other entry in this dialog box, by pressing the Tab (position at next column/field) or Shift-Tab (position at previous column/field). If using a pointing device, the pointer can be positioned at the desired column and the left button pressed to move the prompt.] Date Task types require a valid numeric value representing the month and day that the Task is to be processed (mm/dd). Each field, month and day, requires that the Enter key be pressed to accept the provided entry. The following is a list of the fields required for a Date Task: Date Month and Day to execute the Task Time The time or frequency that the Task file should be processed TaskFile The name of the Task file to process Monthly Task types require a valid numeric value representing the day of each month that the Task is to be processed (dd). Selecting 31 will result in the Task not being processed in months with less than 31 days. The following is a list of the fields required for a Monthly Task: Date Day of the month to process the task Time The time or frequency that the task file should be processed TaskFile The name of the Task file to process Weekly Task types require the selection of one or more days of the week that the Task is to be processed. The desired days may be selected by positioning the cursor prompt over each day using the Left/Right arrow keys and pressing the space bar to toggle the selection status or by positioning the mouse pointer over each day and pressing the left mouse button to toggle the selection status. The following is a list of the fields required for a Weekly Task: Sun-Sat Days on which to process the Task Time The time or frequency that the Task file should be processed TaskFile The name of the Task file to process Once the appropriate day or date scheduling information has been entered, the prompt will position at the Time column. At this point, one of three different Time formats must be selected: Specific At a given time (12:00 pm) Every ?? Every ?? minutes ?? After Hr At ?? minutes after the hour. The defined Time format can be changed by press the Alt-T key combination or positioning the pointer on the Time Option bar and pressing the left pointing device button. At this point, a dialog box will appear prompting the user to 'Select a Time Format.' To select a Time format, place the pointer or the highlighted bar over the desired format and press Enter (the highlighted bar will move in response to the Up/Down arrow keys) or place the pointer on the desired format and press the left mouse button. The Specific time format requires that a valid hour, minute, and am/pm specification be provided. The associated Task will only be processed at the specified time. The Every ?? time format requires that a valid number of minutes (01 - 60) be specified. The associated Task will be processed after each pass of the specified number of minutes. The ?? After Hr time format requires a valid number of minutes (00 - 59) be specified. The associated Task will be processed at the specified number of minutes after each hour. Once the appropriate Time scheduling information has been entered, the prompt will position at the Task File column. At this point, a valid Task file name must be entered. To view a list of existing Task files, press the Alt-F key combination or place the pointer on the 'Task File' option within the dialog box and press the left pointer device button. A subwindow containing the names of existing Task files will appear. The desired file can be selected by positioning the highlighted bar over it and pressing Enter (the highlighted bar will move in response to the Up/Down arrow keys) or the Alt-S key combination. Alternatively, the desired file can also be selected by placing the pointer on the name and pressing the left pointing device button. Once all the Task scheduling information is correct, pressing the Alt-O key combination or placing the pointer on the 'Ok' option within the dialog box and pressing the left mouse button will accept the Task as configured. 8). Deleting a Scheduled Task To delete a scheduled Task, place the pointer on the desired Task and press the left mouse button or position the highlighted bar over the desired Task and press Enter (the highlighted bar will move in response to the Up/Down arrow keys). Pressing the Delete (DEL) key or selecting the 'Delete' option from the Tasks menu bar pull-down list of options will result in a dialog box appearing prompting for confirmation of the deletion. To confirm the deletion, press the Alt-Y key combination or place the pointer over the 'Yes' option and press the left mouse button. The Escape, Alt-N, or Alt-C key combinations, along with placing the pointer over the 'No' or 'Cancel' options and pressing the left mouse button, will abort the deletion request. The Mark/UnMark and Mark/UnMark All options are also available when deleting scheduled Tasks. Pressing F4 key or selecting the Mark/UnMark option from the Tasks menu bar pull-down options acts as a toggle switch that marks and unmarks the highlighted task. The F5 key and the Mark/UnMark All option from the Tasks menu bar pull-down options toggle the marking of ALL Tasks on and off. Using these options, multiple Tasks can be deleted at once. Defining Task Operators and Task Users -------------------------------------- Once installed, the TaskMaster client (TASKMSTR.EXE) requires Supervisor equivalent or File Server Console Operator privileges for execution. However, the SUPERVISOR or a Supervisor Equivalent user can define Task Operators and Task Users who are each granted a limited subset of privileges. Task Operators and Task Users are defined through the Admin menu bar option which appears on the main screen. To manage these definitions, place the pointer over the Admin option on the main screen and press the left mouse button or press and hold the Alt key followed by the 'A' key (Alt-A) to activate the Admin pull- down menu. Place the pointer on the desired option and press the left mouse button or position the highlighted bar over the desired option and press Enter (the highlighted bar will move in response to the Up/Down arrow keys). Upon selecting one of the options in the Admin pull-down menu, a split subwindow will appear showing defined Task Operators/ Task Users on the left and other users on the right. The Tab key can be used to swap the highlighted bar between the split windows and the Up/Down arrow keys can be used to position the highlighted bar over the desired entry. Once the highlighted bar is positioned over the desired user name, the enter key can be used to Add the user name to the defined list (if the highlighted bar is in the right window) or Delete the user name from the defined list (if the highlighted bar is in the left window). Optionally, the mouse pointer can also be placed over the desired user name and the left mouse button can be pressed to highlight the entry. The left mouse button can then be pressed a second time or the mouse pointer can be positioned over the Add/Delete buttons and the left mouse button can be pressed to accomplish the same result. On-line Help is available by pressing and holding the Alt key and then the 'H' key (Alt-H) or positioning the mouse pointer over the Help button and pressing the left mouse button. Once the selection process is complete, the Escape key can be pressed or the mouse pointer can be positioned over the Cancel button and the left mouse button pressed to return to the main screen. (NOTE: Task Operator and Task User definitions are specific to each server. Granted rights are not transferrable between servers and must be specifically configured for each server.) Task Operators: --------------- Task Operators are managed by selecting the Operator option from the Admin pull-down menu on the main screen. Task Operators can schedule, manage, and execute those tasks for which they have sufficient file access rights. Task Users: ----------- Task Operators are managed by selecting the Operator option from the Admin pull-down menu on the main screen. Task Users can execute tasks via the TaskMaster client (TASKMSTR.EXE) using the command line options. However, the tasks which can be executed by Task Users must exist in the same directory from which the TaskMaster NLM (TASKMSTR.NLM) was loaded. Task Users cannot schedule or manage tasks through the TaskMaster client, only run them through the command line options. Executing a Task from the command line -------------------------------------- Task files can be executed directly from the command line through the TaskMaster client utility (TASKMSTR.EXE). To execute a task file from the command line, the user must be logged in to the server where the task file is to be executed as the SUPERVISOR, a Supervisor Equivalent user, or have been previously defined as a Task Operator or Task User. The format for executing task files directly from the command line through the TaskMaster client utility is as follows: TASKMSTR S=server T=taskfile [opts] (NOTE: Task Users can only execute tasks which exist in the same directory from which the TaskMaster NLM was loaded.) Operation: ---------- Upon loading, the NLM initializes the scheduler and the log file then begins scheduling defined tasks. The TaskMaster NLM assumes that the schedule file (TASKMSTR.SCH) and log file (TASKMSTR.LOG) reside in the same subdirectory from which the TASKMSTR.NLM was loaded (e.g., SYS:\SYSTEM, though it can be loaded from other subdirectories). The log file is created, appended to if it exists, in the same subdirectory from which the TASKMSTR.NLM was loaded (e.g., SYS:\SYSTEM\TASKMSTR.LOG). In addition to the scheduled tasks, TaskMaster compatible batch files can be executed manually by typing RUN [batch_name] at the console. The extensions .NCF and .TSK are assumed, if not specified. The default search paths of the vol:path from which TaskMaster was loaded and SYS:\SYSTEM are assumed. An additional path for TaskMaster to search for .NCF and .TSK files can be specified on the command line by appending: P=[vol:path] - or - PATH=[vol:path] to the LOAD TASKMSTR console command. If specified, this path will also be searched for .NCF and .TSK files. TaskMaster initiated batch files or tasks can be manually terminated by entering ABORT [batch] at the server console. The TaskMaster NLM can be unloaded manually via the UNLOAD TASKMSTR server console command. Documentation of TaskMaster batch processing extensions: -------------------------------------------------------- In addition to those console commands supported by NetWare, TaskMaster provides an extended batch file language for expanded processing capabilities. NOTE: - All structures and commands are case insensitive, unless otherwise noted. - Items separated by a vertical bar | indicate any one of the items may be used but not more than one. - Items in brackets [] are optional. - Items in signs <> require a supported test. - Items in parens () require a user supplied string/variable. - Items in lower case are user supplied commands/specifiers. - Lines beginning with REM (case insensitive) or a non-alpha character are considered comments and are ignored (see next note describing :labels). - Lines beginning with a colon : are treated as labels for GOTO execution. - Up to 10 arguments can be established by passing command line parameters as part of the RUN/CALL execution methods or by using the DEFINE or OPEN_READ\READ commands. These arguments (%0 - %9) can be substituted for any batch line item/entry as the parser provides the substitution during the reading of the batch file. - Arguments (%0 - %9) that are defined as numeric values can be incremented or decremented through the DEFINE command Conditional batch file structures: ---------------------------------- The following represent supported batch file command structures for performing conditional processing. NOTE: - Indention in the examples is provided for readability and is not required. IF/ELSEIF/ELSE/END/ENDIF ------------------------ Conditional command execution based upon the result of one or more test conditions which can be evaluated together (AND) or separately (OR). Refer to the supported <TEST> parameters for possible tests. structures: IF [NOT] <TEST> [THEN BEGIN] END[IF] IF [NOT] <TEST> OR [NOT] <TEST> [THEN BEGIN] END IF [NOT] <TEST> AND [NOT] <TEST> [THEN BEGIN] END[IF] IF [NOT] <TEST> [THEN BEGIN] ...command(s)... ELSE ...command(s)... END[IF] IF [NOT] <TEST> [AND|OR [NOT] <TEST>] [THEN BEGIN] ...command(s)... ELSE ...command(s)... END[IF] IF [NOT] <TEST> [THEN BEGIN] ...command(s)... ELSEIF [NOT] <TEST> ...command(s)... ELSE ...command(s)... END[IF] IF [NOT] <TEST> [THEN BEGIN] ...command(s)... ELSEIF [NOT] <TEST> OR [NOT] <TEST> ...command(s)... ELSE ...command(s)... END[IF] IF [NOT] <TEST> [THEN BEGIN] ...command(s)... ELSEIF [NOT] <TEST> AND [NOT] <TEST> ...command(s)... ELSE ...command(s)... END[IF] IF [NOT] <TEST> GOTO :label IF [NOT] <TEST> [AND|OR [NOT] <TEST>] GOTO :label IF [NOT] <TEST> THEN command IF [NOT] <TEST> [AND|OR [NOT] <TEST>] THEN command Note: Multiple AND/OR operators may be used provided that all such operators are of the same type. examples: IF <TEST> ...command(s)... END[IF] Execute command(s) only if <TEST> is succeeds. IF <TEST> THEN BEGIN ...command(s)... END Execute command(s) only if <TEST> is succeeds. IF NOT <TEST> ...command(s)... END[IF] Execute command(s) only if <TEST> is fails. IF <TEST1> OR <TEST2> ...command(s)... END[IF] Execute command(s) only if either <TEST1> or <TEST2> succeed. IF NOT <TEST1> AND NOT <TEST2> ...command(s)... END[IF] Execute command(s) only if both <TEST1> and <TEST2> fail. IF NOT <TEST1> AND <TEST2> ...command(s)... END[IF] Execute command(s) only if <TEST1> fails and <TEST2> succeeds. IF <TEST1> OR NOT <TEST2> ...command(s)... END[IF] Execute command(s) only if either <TEST1> or <TEST2> succeeds. IF <TEST> ...command(s)... ELSE ...command(s)... END[IF] Execute first set of commands if <TEST> succeeds. Execute second set of commands if <TEST> fails. IF NOT <TEST> ...command(s)... ELSE ...command(s)... END[IF] Execute first set of commands if <TEST> fails. Execute second set of commands if <TEST> succeeds. IF <TEST1> ...command(s)... ELSEIF <TEST2> ...command(s)... ELSE ...command(s)... END[IF] Execute 1st set of commands if <TEST1> succeeds. Execute 2nd set if <TEST1> fails and <TEST2> succeeds. Execute 3rd set if both <TEST1> and <TEST2> fail. IF NOT <TEST1> ...command(s)... ELSEIF NOT <TEST2> ...command(s)... ELSE ...command(s)... END[IF] Execute 1st set of commands if NOT <TEST1>. Execute 2nd set if <TEST1> succeeds and NOT <TEST2>. Execute 3rd set if both <TEST1> and <TEST2> succeed. IF <TEST> GOTO :label Move batch file pointer to :label if <TEST> succeeds. IF NOT <TEST> GOTO :label Move batch file pointer to :label if <TEST> fails. IF <TEST> THEN command Execute command if <TEST> succeeds. IF NOT <TEST> THEN command Execute command if <TEST> fails. WHILE/BREAK/CONTINUE/LOOP ------------------------- Conditional repetitive command execution based upon the result of one or more test conditions which can be evaluated together (AND) or separately (OR). Refer to the supported <TEST> parameters for possible tests. structures: WHILE [NOT] <TEST> ...command(s).... LOOP WHILE [NOT] <TEST> OR [NOT] TEST ...command(s).... LOOP WHILE [NOT] <TEST> AND [NOT] TEST ...command(s).... LOOP WHILE [NOT] <TEST> ...command(s).... IF [NOT] <TEST> [AND|OR [NOT] <TEST>] THEN BREAK ...command(s).... LOOP WHILE [NOT] <TEST> [AND|OR [NOT] <TEST>] ...command(s).... IF [NOT] <TEST> [AND/OR [NOT] <TEST>] THEN BREAK ...command(s).... LOOP WHILE [NOT] <TEST> ...command(s).... IF [NOT] <TEST> [AND|OR [NOT] <TEST>] THEN CONTINUE ...command(s).... LOOP WHILE [NOT] <TEST> [AND|OR [NOT] <TEST>] ...command(s).... IF [NOT] <TEST> [AND|OR [NOT] <TEST>] THEN CONTINUE ...command(s).... LOOP WHILE [NOT] <TEST> ...command(s).... IF [NOT] <TEST> [AND|OR [NOT] <TEST>] ...command(s)... BREAK END[IF] ...command(s).... LOOP WHILE [NOT] <TEST> ...command(s).... IF [NOT] <TEST> [AND|OR [NOT] <TEST>] ...command(s)... CONTINUE END[IF] ...command(s).... LOOP Note: Multiple AND/OR operators may be used provided that all such operators are of the same type. examples: WHILE <TEST> ...command(s)... LOOP Repetitively execute commands as long as <TEST> succeeds. WHILE NOT <TEST> ...command(s)... LOOP Repetitively execute commands as long as <TEST> fails. WHILE <TEST> ...command(s)... IF <TEST> THEN BREAK LOOP Repetitively execute commands as long as initial <TEST> succeeds. Terminate the repetitive execution upon failure of the secondary <TEST>. (NOTE: Refer to the IF/ELSEIF/ELSE/END/ENDIF section for examples of other possible IF <TEST> usage.) WHILE NOT <TEST> ...command(s)... IF <TEST> THEN CONTINUE ...command(s)... LOOP Repetitively execute the first set of commands as long as initial <TEST> fails. Restart the repetitive execution at the first set of commands upon success of the secondary <TEST>. Otherwise, execute the second set of commands before restarting the repetitive execution. (NOTE: Refer to the IF/ELSE/ENDIF section for examples of other possible IF <TEST> usage.) Supported <TEST> parameters for IF and WHILE: --------------------------------------------- "string of text"=="string of text" text==text Compares if two strings or text items are equal in contents, length, and/or case. Quotes are required surrounding strings which may be NULL or which may have spaces as part of the string. (NOTE: Spaces between the compare strings and the operators are not allowed, e.g., "TEST"=="TEST" is valid while "TEST" == "TEST" or test == test is not.) (NOTE: Any of the supported system environment variables may be used within a quoted string or as text items for comparison. TaskMaster will automatically substitute the system environment variable value prior to the comparison.) Examples: 123==123 - True "ABC"=="ABC" - True XYZ==XYZ - True 001==1 - False (0 < 1, hex compare) "abc"=="ABC" - False (a > A, hex compare) ABC==ABCD - False (ABCD is longer) "string of text">"string of text" text>text Compares if the first string or text item is greater than the second string or text item in contents, length, and/or case. Quotes are required surrounding strings which may be NULL or which may have spaces as part of the string. (NOTE: Spaces between the compare strings and the operators are not allowed, e.g., "TEST"=="TEST" is valid while "TEST" == "TEST" or test == test is not.) (NOTE: Any of the supported system environment variables may be used within a quoted string or as text items for comparison. TaskMaster will automatically substitute the system environment variable value prior to the comparison.) Examples: 123>122 - True "XYZ">"ABC" - True 9>123 - True (9 > 1, hex compare) "TEST ">"TEST" - True ("TEST " is longer) Z>a - False (a > Z, hex compare) XYZ>xyz - False (x > X, hex compare) "string of text"<"string of text" text<text Compares if the first string or text item is less than the second string or text item in contents, length, and/or case. Quotes are required surrounding strings which may be NULL or which may have spaces as part of the string. (NOTE: Spaces between the compare strings and the operators are not allowed, e.g., "TEST"=="TEST" is valid while "TEST" == "TEST" or test == test is not.) (NOTE: Any of the supported system environment variables may be used within a quoted string or as text items for comparison. TaskMaster will automatically substitute the system environment variable value prior to the comparison.) Examples: 122<123 - True "ABC"<"XYZ" - True 123<9 - True (1 < 9, hex compare) "TEST"<"TEST " - True ("TEST" is shorter) a<Z - False (Z < a, hex compare) xyz<XYZ - False (X < x, hex compare) "string of text">="string of text" text>=text Compares if the first string or text item is greater than or equal to the second string or text item in contents, length, and/or case. Quotes are required surrounding strings which may be NULL or which may have spaces as part of the string. (NOTE: Spaces between the compare strings and the operators are not allowed, e.g., "TEST"=="TEST" is valid while "TEST" == "TEST" or test == test is not.) (NOTE: Any of the supported system environment variables may be used within a quoted string or as text items for comparison. TaskMaster will automatically substitute the system environment variable value prior to the comparison.) "string of text"<="string of text" text<=text Compares if the first string or text item is less than or equal to the second string or text item in contents, length, and/or case. Quotes are required surrounding strings which may be NULL or which may have spaces as part of the string. (NOTE: Spaces between the compare strings and the operators are not allowed, e.g., "TEST"=="TEST" is valid while "TEST" == "TEST" or test == test is not.) (NOTE: Any of the supported system environment variables may be used within a quoted string or as text items for comparison. TaskMaster will automatically substitute the system environment variable value prior to the comparison.) CURRENT_SCREEN "screen name" Used to check if the screen currently displayed on the server console matches the specified "screen name" parameter. The quotes surrounding "screen name" are required. The "screen name" must exactly match the name of the currently displayed screen on the server console, both in case sensitivity and length. (NOTE: The defined name for any screen can be determined by pressing the Alt key on the console keyboard while the screen is actively displayed. The name will appear in the upper left hand corner of the screen.) ERRORLEVEL Used to check the status of the last executed command. (NOTE: This is a SUCCESS/FAILED status, not an error code.) EXIST [[vol:]path\]name.ext Used to verify the existence of any files matching the specification (vol:dir\name.ext). Wildcards are supported. (NOTE: The specification can be a fully qualified path or relative to the Current Working Directory. Refer to the CD or CHDIR batch command for more information on the Current Working Directory.) FILE_IN_USE [[vol:]path\]name.ext Used to determine if the specified file is open by any connection on the server, including NLMs. A full file name is required (i.e., wild cards are not supported). The test fails if the file does not exist or is not in use. (NOTE: The specification can be a fully qualified path or relative to the Current Working Directory. Refer to the CD or CHDIR batch command for more information on the Current Working Directory.) LOADED module.ext Used to verify the load status of the specified NetWare Loadable Module (NLM). LOGGED_IN user_name Used to verify if the specified user is logged in to the server. Requires a valid user name specification. MOUNTED volume Used to verify the mounted status of the specified NetWare volume. Only the volume name is required, not the trailing colon used with file specifications (i.e., SYS, not SYS:). However, it will accept and treat both SYS or SYS: equally. SCAN_SCREEN "string" Scans for the specified string anywhere within the screen currently displayed on the server console. The search string must be enclosed within double quotes. This is a case sensitive scan of the screen data for the specified string. (NOTE: The currently displayed screen can be checked using CURRENT_SCREEN and changed using CHANGE_SCREEN.) SCAN_STRING "search string" "source string" Scans for the specified string (search string) within the supplied data (source string). Both strings must be enclosed within double quotes. This is a case sensitive scan of the source string for the specified search string. (NOTE: Both the search string and the source string can be assigned using user defined or System Environment variables.) Supported system environment variables: --------------------------------------- The following represent special NetWare system environment variables which will be automatically substituted into any command line by TaskMaster as appropriate. The information returned is specific to the NetWare file system. These system environment variables presently do not support the DOS partition (i.e., C:\ boot partition). The values substituted for those system environment variables which return decimal counts can be incremented and decremented prior to substitution by immediately following the system environment variable with a += for incrementation or -= for decrementation and a decimal value. Examples: %CONNS_MAX% is 250, %CONNS_MAX%-=10 equals 240 %RECV_BUFFS_MAX% is 100, %RECV_BUFFS_MAX%+=10 equals 110 %AM_PM% Substitutes am or pm, depending upon the local time. Example: 8:00am = am, 8:00pm = pm %CACHE_RATIO% Substitutes the current Cache Buffer ratio, i.e., percent of server RAM used for cache (000 to 100 - 3 digits). %CONN_ADDRESS_####% Substitutes the net:node address (00000000:000000000000 for the specified connection number (#### must be a valid connection number or user variable (%0-%9) previously defined as a valid connection number). If the specified connection is INACTIVE, all zeroes are returned for the net:node address. %CONN_ID_####% Substitutes an ASCII string containing the object id for the logged in USER on the specified connection number (#### must be a valid connection number or user variable (%0-%9) previously defined as a valid connection number). If the specified connection is either NOT-LOGGED-IN or INACTIVE, a zero is returned. (NOTE: The returned string is the same as used for the SYS:\MAIL directory for the logged in USER.) Example: %CONN_ID_1% is replaced with the object id of the logged in USER on connection 1, e.g., 1 is returned if SUPERVISOR is logged into connection 1 and 0 is returned if connection 1 is INACTIVE or NOT-LOGGED-IN. %CONN_NAME_####% Substitutes the name of the logged in USER on the specified connection number (#### must be a valid connection number or user variable (%0-%9) previously defined as a valid connection number). If the USER has logged out of the connection but the slot has not yet been released, NOT-LOGGED-IN is returned. If the specified connection slot is free (not allocated), INACTIVE is returned. Example: %CONN_NAME_1% is replaced with the name of the logged in USER on connection 1, e.g., SUPERVISOR is returned if SUPERVISOR is logged into connection 1, NOT-LOGGED-IN is returned if connection 1 is allocated but no user is logged in, and INACTIVE is returned if connection 1 is unallocated. %CONNS_IN_USE% Substitutes the current number of licensed connections in use (0000 to 1000 - 4 digits to support 1000 users). %CONNS_MAX% Substitutes the maximum number of licensed connections supported (0000 to 1000 - 4 digits to support 1000 users). %CONNS_PEAK% Substitutes the peak number of licensed connections in use at one time since the server was last brought up (0000 to 1000 - 4 digits to support 1000 users). %CPU_UTIL% Substitutes the current CPU Utilization percentage (000 to 100 - 3 digits). %CWD% Substitutes the Current Working Directory (CWD). Example: SYS:\PUBLIC\IBM_PC\MSDOS\V6.23 SYS: (root dir of SYS:) %DAY% Substitutes the current day of the month (01 to 31 - 2 digits). %DAY_OF_WEEK% Substitutes the current day of the week. Example: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, or Sunday %DIR_FILE_[filespec]% Substitutes the name of the next file in the Current Working Directory (CWD - see CD/CHDIR for more information) which matches the specified [filespec] search pattern. The [filespec] provided must be a valid DOS file specification or user variable (%0-%9) previously defined as a valid DOS file specification. (NOTE: The search pattern must be supplied in the initial request. However, subsequent requests should not include a [filespec] since the inclusion of a file name/pattern indicates the desire to initiate a new file search.) Example: %DIR_FILE_*.*% searches for the first matching file %DIR_FILE_% retrieves the next matching file %DIR_SUB_[dirspec]% Substitutes the name of the next subdirectory in the Current Working Directory (CWD - see CD/CHDIR for more information) which matches the specified [dirspec] search pattern. The [dirspec] provided must be a valid DOS directory specification or user variable (%0-%9) previously defined as a valid DOS directory specification. (NOTE: The search pattern must be supplied in the initial request. However, subsequent requests should not include a [dirspec] since the inclusion of a subdirectory name/pattern indicates the desire to initiate a new subdirectory search.) Example: %DIR_SUB_*.*% searches for the first matching subdir %DIR_SUB_% retrieves the next matching subdir %DIR_TREE_[dirspec]% Substitutes the name of the next directory as %DIR_TREE_% traverses the tree starting at the specified [dirspec] subdirectory. The [dirspec] provided must be a valid DOS directory specification or user variable (%0-%9) previously defined as a valid DOS directory specification. The returned directory name also becomes the Current Working Directory (CWD - see CD/CHDIR for more information). (NOTE: The search pattern must be supplied in the initial request. However, subsequent requests should not include a [dirspec] since the inclusion of a subdirectory name/pattern indicates the desire to initiate a new subdirectory search.) Example: %DIR_TREE_SYS:\PUBLIC% retrieves the first directory under SYS:\PUBLIC (SYS:\PUBLIC is treated as the root directory for the tree search) %DIR_TREE_% retrieves the next subdir as the CWD %FILE_ACCESS_[filespec]% Substitutes the date (yyyy/mm/dd) the specified [filespec] was last accessed. The [filespec] provided must be a valid DOS file specification or user variable (%0-%9) previously defined as a valid DOS file specification. %FILE_ATTRIB_[filespec]% Substitutes the NetWare attributes for the specified [filespec]. The [filespec] provided must be a valid DOS file specification or user variable (%0-%9) previously defined as a valid DOS file specification. (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) Example: %FILE_ATTRIB_NET$LOG.DAT% searches the CWD %FILE_ATTRIB_SYS:\VOL$LOG.ERR searches SYS:\ Attribs: [ -- - - - - -- - - -- -- -- -- -- ] Ro Read Only Rw Read/Write S Shareable A Archive X Execute only H Hidden Sy System T Tranactional P Purge immediate Ra Read Audit (NW4) Wa Write Audit(NW4) CI Copy Inhibit DI Delete Inhibit RI Rename Inhibit (Attributes are displayed if set) %FILE_CREATE_[filespec]% Substitutes the date (yyyy/mm/dd) the specified [filespec] was created. The [filespec] provided must be a valid DOS file specification or user variable (%0-%9) previously defined as a valid DOS file specification. %FILE_OWNER_[filespec]% Substitutes the name of the NetWare user who created the specified [filespec]. The [filespec] provided must be a valid DOS file specification or user variable (%0-%9) previously defined as a valid DOS file specification. %FILE_SIZE_[filespec]% Substitutes the current size of the specified [filespec]. The [filespec] provided must be a valid DOS file specification or user variable (%0-%9) previously defined as a valid DOS file specification. %FILE_UPDATE_[filespec]% Substitutes the date (yyyy/mm/dd) the specified [filespec] was last updated. The [filespec] provided must be a valid DOS file specification or user variable (%0-%9) previously defined as a valid DOS file specification. %HOUR% Substitutes the current hour (01 to 12 - 2 digits). Example: Midnight = 12, Noon = 12, 3:00am/pm = 03 %HOUR24% Substitutes the current hour (00 to 23 - 2 digits). Example: Midnight = 00, 11:00pm = 23 %MINUTE% Substitutes the current minute (00 to 59 - 2 digits). %MONTH% Substitutes the current month (01 to 12 - 2 digits). %MONTH_NAME% Substitutes the current month name. Example: January, February, March, April, May, June, July, August, September, October, November, December %NDAY_OF_WEEK% Substitutes the number of the current day of the week. Example: Sunday = 1, Monday = 2, ... Saturday = 7 %NDAY_OF_YEAR% Substitutes the current day of the year (001 to 365 - 3 digits). Example: Jan 1 = 001, Dec 31 = 365 (non-Leap year) %PATH% Substitutes the path for the Current Working Directory (CWD). Example: \PUBLIC\IBM_PC\MSDOS\V6.23 (root dir of volume) (NOTE: The root directory %PATH% returns a null string.) %RECV_BUFFS_IN_USE% Substitutes the number of Packet Receive Buffers allocated by NetWare for use (0000 to 2000 - 4 digits). %RECV_BUFFS_MAX% Substitutes the current value for the SET Maximum Packet Receive Buffers parameter (0050 to 2000 - 4 digits). %SCREEN_NAME% Substitutes the name of the currently active screen (a text string value). %SECOND% Substitutes the current second (00 to 59 - 2 digits). %SERVER% Substitutes the server name. Example: AVANTI_1 %TASK_NAME% Substitutes the fully qualified name (vol:path\taskname.ext) of the currently executing task. Example: SYS:\SYSTEM\DIRCHECK.TSK %TEMP_NAME% Substitutes a unique temporary file name in the format of _T-?????.TMP, where the ?'s are replaced with an ASCII representation of a unique decimal value. Example: _T-00123.TMP %VOL_FREE% Substitutes the percent of available blocks on the volume associated with the Current Working Directory (CWD), including blocks which are purgeable (000 to 100 - 3 digits). %VOL_NAME% Substitutes the volume name for the Current Working Directory (CWD). Example: CWD = SYS:\SYSTEM, %VOL_NAME% = SYS: %VOL_USED% Substitutes the percent of in use blocks on the volume associated with the Current Working Directory (CWD), including blocks which are not yet purgeable (000 to 100 - 3 digits). %YEAR% Substitutes the current year (1900 to 1999). Example: 1994 Supported batch processing commands: ------------------------------------ The following represent special batch processing commands, supplemental to those server console commands available through NetWare. ABORT Terminates the currently executing batch process. APPEND [[drive|vol:]path\]name.ext [[drive|vol:]path\]name.ext Appends the specified source file (the first parameter) to the destination file (the second parameter). Copying to and from the DOS partition (i.e., C:\ boot partition) is supported, provided that the DOS specification includes the drive and path. Wildcards are not presently supported. (NOTE: Each file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR. Copying to or from the DOS partition requires that the DOS specification include the drive and path, e.g., C:\SERVER\STARTUP.NCF.) CALL batch[.ext] Suspends the current batch file processing and initiates the processing of the specified batch file. Original batch file processing does not resume until completion of the specified batch file. The same default/search path and extension rules apply as if executed on the console via the RUN command. CD [vol:]path CHDIR [vol:]path Used to change the Current Working Directory (CWD). The CWD is the default vol:path which is used for all file operations in which a specific vol:path is not provided. The CD/CHDIR specification can be relative to the current CWD (e.g., ..\NEWDIR or a subdirectory in the CWD) or an absolute destination directory (e.g., SYS:\HOME\USER). Changing the CWD for the DOS partition (i.e., C:\ boot partition) is not presently supported. (NOTE: Each task/batch job maintains its own CWD. Therefore, an initial CWD should be set using a fully qualified path, with volume and complete path, within the batch file to insure a valid default destination from which to work.) CHANGE_SCREEN "screen_name" Used to change the screen that is currently displayed on the server console, which is also the screen to that KEYIN and SCAN_SCREEN refers. If a specific screen name is desired, it must be enclosed in quotes and must exactly match the name of the desired screen (i.e., case and length sensitive). If the intent is to merely change to the next screen (i.e., as if pressing Alt-ESC at the server console), either provide a null screen name (CHANGE_SCREEN "") or do not provide any screen name at all (CHANGE_SCREEN). (NOTE: The defined name for any screen can be determined by pressing the Alt key on the console keyboard while the screen is actively displayed. The name will appear in the upper left hand corner of the screen.) CLEAR_FILE [[vol:]path\]name.ext Closes every occurrence of a file open (NetWare, NLM, or workstation) for the specified file. The file is flushed internally within NetWare and closed without terminating any connections. Wild cards are supported in the file name and extension. (NOTE: Caution should be exercised when using wild cards as this command will close any file matching the specification, including NetWare system and bindery files.) CLEAR_LOCK [[vol:]path\]name.ext Release any file locks (NetWare, NLM, or workstation) against the specified file. The file is unlocked internally within NetWare without terminating any connections. Wild cards are supported in the file name and extension. (NOTE: Caution should be exercised when using wild cards as this command will unlock any file matching the specification, including NetWare system and bindery files.) CLOSE Closes all previously opened OPEN_READ and/or OPEN_WRITE declarations. Refer to OPEN_READ or OPEN_WRITE for more additional information on their usage. (NOTE: OPEN_READ will also close any previously opened input file while OPEN_WRITE will close any previously opened output file.) COPY [[drive|vol:]path\]name.ext [[drive|vol:]path\]name.ext Copies the specified source file(s) <first parameter> to the destination file(s) <second parameter>. Copying to and from the DOS partition (i.e., C:\ boot partition) is supported, provided that the DOS specification includes the drive and path. Wild cards are supported. However, both a source and destination file specification must be provided (even with wild cards). (NOTE: Each file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR. Copying to or from the DOS partition requires that the DOS specification include the drive and path, e.g., C:\SERVER\STARTUP.NCF.) Wild card usage examples: ------------------------- COPY SYS:\*.* DATA:\*.* (between volumes) COPY *.* \PUBLIC\*.* (default dir to PUBLIC) COPY ..\*.* *.* (higher dir to default) COPY *.BAT *.BAK (copy w/ different .ext) COPY NEW*.* OLD*.* (copy w/ modified name) COPY ?123*.* ?456*.* (copy w/ modified name) DEFINE %# string Used to define an argument (%0 - %9) to be used within the batch file. Arguments can be used almost any place within the batch file, either as user supplied parameters or as batch command structures. However, they must be defined prior to actual usage in a batch command. (NOTE: The DEFINE string should be provided EXACTLY as required for the parameter or command structure it is intended to replace. If quotes {""} are required by the parameter, they should be included in the DEFINE string. Caution should be used in the string construction since the DEFINE string will be used as specified, including any trailing comments or characters.) (NOTE: If the value assigned to an argument is numeric, the value can be dynamically incremented and/or decremented as follows: DEFINE %0 %0+=1 to increment the %0 value by 1 DEFINE %0 %0-=1 to decrement the %0 value by 1 However, the DEFINE value must be predefined prior to being incremented/decremented and should be pre-formatted to the correct length/size for any comparisons: DEFINE %0 000 (for 3 digit comparisons) DEFINE %0 0000 (for 4 digit comparisons) Incrementation/decrementation only supports pre-defined numeric value strings.) DEL [[vol:]path\]name.ext DELETE [[vol:]path\]name.ext Deletes the specified file on the NetWare partition. Wildcards are allowed. Deleting files from the DOS partition (i.e., C:\ boot partition) is not presently supported. (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) ECHO. Displays a blank line on the console. Similar to the WRITE. command except the blank line is sent to the console. If LOG ON is active, the comments will also be recorded in the log file. ECHO ...comments... Displays the trailing comments on the console. Similar to the WRITE ...comments... except the output is sent to the console. If LOG ON is active, the comments will also be recorded in the log file. (NOTE: Any System Variables are automatically substituted prior to the comments being displayed.) ECHO ON ECHO OFF Enables/disables the display of processed batch file commands to the console. ECHO ON will display every batch file command processed. ECHO_WRITE. Displays a blank line on the console and also writes a blank line to the OPEN_WRITE file. Same as executing both the ECHO. and WRITE. commands. ECHO_WRITE ...comments... Displays the trailing comments on the console and also writes them to the OPEN_WRITE file. Same as executing both the ECHO and WRITE commands. Using ECHO_WRITE with out trailing comments will place a blank line on the screen and in the file (carriage return and line feed only - no text). (NOTE: Any System Variables are automatically substituted prior to the comments being displayed.) GOTO LABEL Moves the batch file pointer to the line specified by LABEL. Any batch file line beginning with a colon (:) is treated as an execution label for subsequent GOTO redirection. (NOTE: Caution should be used when using GOTO within IF/ENDIF and WHILE/LOOP blocks since jumping outside of the confines of the construct will most likely cause an IF/ENDIF or WHILE/LOOP count mismatch error to occur.) KEYIN keyword KEYIN "string" KEYIN ["string"|keyword] ["string"|keyword] ["string"|keyword] Used to enter "string" and/or special keys into the screen which is currently displayed on the server console as if input from the console keyboard. Multiple "string" and/or keyword combinations are allowed. The "string" may contain one or more alphanumeric characters and must be enclosed within quotes {""}. Refer to the keyword list for support of special key names. (NOTE: See CHANGE_SCREEN for definition of how to set the currently displayed screen on the server console.) KEYIN keyword list: ------------------- BACKSPACE, ENTER, ESC, ESCAPE F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12 UP, DOWN, LEFT, RIGHT, PGUP, PGDN, HOME, END INS, INSERT, DEL, DELETE SHIFT-keyword (hyphen/dash required) ALT-keyword (hyphen/dash required) CTRL-keyword (hyphen/dash required) LOAD [[drive:|vol:]path\]module[.ext] Load the specified module. The ERRORLEVEL flag is set TRUE is the load fails. LOG ON LOG OFF Enable/disable the recording of executed batch file commands in the log file (vol:path\batch_name.LOG), as well as lines displayed due to ECHO commands and ECHO ON activation. (NOTE: This should be used primarily as a debugging tool, not for normal operation. Each executed line in the batch file is fully resolved and written to the log which is flushed to disk after each entry. Use of LOG ON will impact server overhead due to the number of disk write operations which are likely to occur.) MD [vol:]path MKDIR [vol:]path Used to create a directory. The specification can be relative to the Current Working Directory (CWD - e.g., ..\NEWDIR) or an absolute destination directory (e.g., SYS:\HOME\USER). Creating directories on the DOS partition (i.e., C:\ boot partition) is not presently supported. (NOTE: See CD/CHDIR for more information on the CWD.) OPEN_READ [[vol:]path\]name.ext Open the specified file for reading data into arguments (%0-%9). The ERRORLEVEL flag is set if unable to open the specified file. (NOTE: Only one file can be opened concurrently for reading into the arguments. OPEN_READ closes any previously opened argument file. The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) OPEN_WRITE [[vol:]path\]name.ext [TRUNC | TRUNCATE] Open the specified file for sequential writes. If TRUNC or TRUNCATE is specified after the file name, the file is reset to overwrite previous contents. Otherwise, WRITE records are appended to the file if it already exists. The ERRORLEVEL flag is set if unable to open the specified file. (NOTE: Only one file can be opened concurrently for writing. OPEN_WRITE closes any previously opened write file. The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) PAUSE Suspend batch file processing until a key is pressed on the console keyboard. The System Console screen will be activated and the console will emit an audible beep once per second until a key is pressed. PURGE [filename.ext] [/A][/ALL] Purge previously erased files in the Current Working Directory (CWD). A specific filename.ext may be specified. Wild cards are supported. If a file spec is not provided, all previously erased files in the CWD will be purged. (NOTE: Specifying the /A or /ALL option will purge all previously erased files in the CWD, plus all previously erased files in the subdirectories beneath the CWD.) RD [vol:]path RMDIR [vol:]path Used to remove an empty directory. The specification can be relative to the Current Working Directory (CWD - e.g., ..\NEWDIR) or an absolute destination directory (e.g., SYS:\HOME\USER). Removing directories on the DOS partition (i.e., C:\ boot partition) is not presently supported. (NOTE: RD/RMDIR will fail if there are any files or subdirectories within the directory to be removed. See CD/CHDIR for more information on the CWD.) READ %# Read the next sequential record in the OPEN_READ file and store the data in the specified argument (%0-%9). Arguments can be used almost any place within the batch file, either as user supplied parameters or as batch command structures. However, they must be defined prior to actual usage in a batch command. The ERRORLEVEL flag is set if an error occurs during the read or the End Of File (EOF) is reached. Refer to OPEN_READ for further information on its usage. (NOTE: After the READ, the specified argument will contain the record EXACTLY as it existed in the file, excluding the carriage return/line feed, end of record marked. Therefore, the data in the file should be formatted exactly as required for the parameter or command structure it is intended to replace. If quotes {""} are required by the parameter, they should be included in the record to be read. Caution should be used in the string construction since the READ string will be used as specified, including any trailing comments or characters.) REN [[vol:]path\]name.ext [[vol:]path\]name.ext RENAME [[vol:]path\]name.ext [[vol:]path\]name.ext Renames the specified source file (the first parameter) to the destination file (the second parameter). Wildcards are supported. Files cannot be renamed across volumes or on the DOS partition (i.e., C:\ boot partition). (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) SAVE_SCREEN [[vol:]path\]name.ext SAVE_SCREEN [[vol:]path\]name.ext BIN[ARY] SAVE_SCREEN [[vol:]path\]name.ext TEXT SAVE_SCREEN [[vol:]path\]name.ext TXT Captures the image of the screen which is currently displayed on the server console to the specified file. Two modes of screen capturing are supported: Binary stores both the displayed character and attribute while Text stores only the displayed characters. Text mode is the default but can be overridden by specifying BIN or BINARY. (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) SHIFT Rotate the contents of all arguments left one position, clearing the last argument. The string in %1 is moved to %0, %2 to %1, %3 to %2, and so forth with %9 set to null. WAIT ### Suspend the batch file processing for the specified number of seconds (0-999). WRITE. Writes a blank line to the OPEN_WRITE file (carriage return and line feed only - no text). Similar to the ECHO. command except the output is written to the OPEN_WRITE file. WRITE ...comments... Writes the trailing comments to the OPEN_WRITE file. Similar to ECHO command. except the output is sent to the console. Using WRITE with out trailing comments will place a null line in the file (carriage return and line feed only - no text). (NOTE: Any System Variables are automatically substituted prior to the comments being displayed.) Extended server console commands: --------------------------------- The following represent server console commands which supplement those normally available through NetWare. These can be executed as part of a TaskMaster batch task, like any other NetWare server console command, or manually at the server console. ABORT [task_name] Terminates the processing of the specified task. The [task_name] specification can be the fully qualified vol:path\filename.ext of an executing Task file, the full filename.ext, or just the filename. APPEND [[drive|vol:]path\]name.ext [[drive|vol:]path\]name.ext Appends the specified source file (the first parameter) to the destination file (the second parameter). Copying to and from the DOS partition (i.e., C:\ boot partition) is supported, provided that the DOS specification includes the drive and path. Wildcards are not presently supported. (NOTE: Each file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR. Copying to or from the DOS partition requires that the DOS specification include the drive and path, e.g., C:\SERVER\STARTUP.NCF.) CD [vol:]path CHDIR [vol:]path Used to change the Current Working Directory (CWD). The CWD is the default vol:path which is used for all file operations in which a specific vol:path is not provided. The CD/CHDIR specification can be relative to the current CWD (e.g., ..\NEWDIR or a subdirectory in the CWD) or an absolute destination directory (e.g., SYS:\HOME\USER). Changing the CWD for the DOS partition (i.e., C:\ boot partition) is not presently supported. (NOTE: Each task/batch job maintains its own CWD. Therefore, an initial CWD should be set using a fully qualified path, with volume and complete path, within the batch file to insure a valid default destination from which to work.) CHMOD [vol:path\[filespec]] [[+|-]attributes] [/C] Changes the NetWare attributes associated with the files matching the provided search specification (wild cards are supported). If no search specification is provided, a listing of the files in the CWD is generated. The matching files and new attributes are displayed once changed. If no attributes are specified, a listing of the files with their associated attributes are displayed. By default, the listing will pause awaiting operator intervention after each screen of files. The /C option will override this pause and generate a continuous listing of all matching files. This command does not support the DOS partition (i.e., C:\ boot partition). (NOTE: The /C option is only supported when this command is executed directly at the server console, i.e., not from within a .NCF or .TSK batch task.) (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) Attribs: [ -- - - - - -- - - -- -- -- -- -- ] Ro Read Only Rw Read/Write S Shareable A Archive X Execute only H Hidden Sy System T Tranactional P Purge immediate Ra Read Audit (NW4) Wa Write Audit(NW4) CI Copy Inhibit DI Delete Inhibit RI Rename Inhibit (Attributes are displayed if set) CHOWN [vol:path\[filespec]] [user] [/C] Changes the NetWare owner associated with the files matching the provided search specification (wild cards are supported). If no search specification is provided, a listing of the files in the CWD is generated. The matching files with new owner are displayed once changed. If no user name is specified, a listing of the files with their associated owners are displayed. By default, the listing will pause awaiting operator intervention after each screen of files. The /C option will override this pause and generate a continuous listing of all matching files. (NOTE: The /C option is only supported when this command is executed directly at the server console, i.e., not from within a .NCF or .TSK batch task.) (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) COPY [[drive|vol:]path\]name.ext [[drive|vol:]path\]name.ext Copies the specified source file (the first parameter) to the destination file (the second parameter). Copying to and from the DOS partition (i.e., C:\ boot partition) is supported, provided that the DOS specification includes the drive and path. Wildcards are not presently supported. (NOTE: Each file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR. Copying to or from the DOS partition requires that the DOS specification include the drive and path, e.g., C:\SERVER\STARTUP.NCF.) DEL [[vol:]path\]name.ext DELETE [[vol:]path\]name.ext Deletes the specified file on the NetWare partition. Wildcards are allowed. Deleting files from the DOS partition (i.e., C:\ boot partition) is not presently supported. (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) DIR [drive|vol:path\[filespec]] [/C] Generates a listing of the files matching the provided search specification (wild cards are supported). If no file specification is provided, a listing of the files in the CWD is generated. By default, the listing will pause awaiting operator intervention after each screen of files. The /C option will override this pause and generate a continuous listing of all matching files. Support for listing files in the DOS partition (i.e., A:\ diskette and C:\ boot partition) is supported. (NOTE: The /C option is only supported when this command is executed directly at the server console, i.e., not from within a .NCF or .TSK batch task.) (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) DUMP [drive|vol:path\[filespec]] [/C] Displays the hex contents of the specified file on the console screen (similar to DOS DEBUG). By default, the display will pause awaiting operator intervention after each screen of data. The /C option will override this pause and generate a continuous display of the screen data. Support for displaying files in the DOS partition (i.e., A:\ diskette and C:\ boot partition) is supported. (NOTE: The /C option is only supported when this command is executed directly at the server console, i.e., not from within a .NCF or .TSK batch task.) (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) FLAG [vol:path\[filespec]] [[+|-]attributes] [/C] Changes the NetWare attributes associated with the files matching the provided search specification (wild cards are supported). If no search specification is provided, a listing of the files in the CWD is generated. The matching files and new attributes are displayed once changed. If no attributes are specified, a listing of the files with their associated attributes are displayed. By default, the listing will pause awaiting operator intervention after each screen of files. The /C option will override this pause and generate a continuous listing of all matching files. This command does not support the DOS partition (i.e., C:\ boot partition). (NOTE: The /C option is only supported when this command is executed directly at the server console, i.e., not from within a .NCF or .TSK batch task.) (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) Attribs: [ -- - - - - -- - - -- -- -- -- -- ] Ro Read Only Rw Read/Write S Shareable A Archive X Execute only H Hidden Sy System T Tranactional P Purge immediate Ra Read Audit (NW4) Wa Write Audit(NW4) CI Copy Inhibit DI Delete Inhibit RI Rename Inhibit (Attributes are displayed if set) MD [vol:]path MKDIR [vol:]path Used to create a directory. The specification can be relative to the Current Working Directory (CWD - e.g., ..\NEWDIR) or an absolute destination directory (e.g., SYS:\HOME\USER). Creating directories on the DOS partition (i.e., C:\ boot partition) is not presently supported. (NOTE: See CD/CHDIR for more information on the CWD.) PURGE [filename.ext] [/A][/ALL] Purge previously erased files in the Current Working Directory (CWD). A specific filename.ext may be specified. Wild cards are supported. If a file spec is not provided, all previously erased files in the CWD will be purged. (NOTE: Specifying the /A or /ALL option will purge all previously erased files in the CWD, plus all previously erased files in the subdirectories beneath the CWD.) RD [vol:]path RMDIR [vol:]path Used to remove an empty directory. The specification can be relative to the Current Working Directory (CWD - e.g., ..\NEWDIR) or an absolute destination directory (e.g., SYS:\HOME\USER). Removing directories on the DOS partition (i.e., C:\ boot partition) is not presently supported. (NOTE: RD/RMDIR will fail if there are any files or subdirectories within the directory to be removed. See CD/CHDIR for more information on the CWD.) REN [[vol:]path\]name.ext [[vol:]path\]name.ext RENAME [[vol:]path\]name.ext [[vol:]path\]name.ext Renames the specified source file (the first parameter) to the destination file (the second parameter). Wildcards are supported. Files cannot be renamed across volumes or on the DOS partition (i.e., C:\ boot partition). (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) TYPE [drive|vol:path\[filespec]] [/C] Displays the contents of the specified file on the console screen. By default, the display will pause awaiting operator intervention after each screen of data. The /C option will override this pause and generate a continuous display of the screen data. Support for displaying files in the DOS partition (i.e., A:\ diskette and C:\ boot partition) is supported. (NOTE: The /C option is only supported when this command is executed directly at the server console, i.e., not from within a .NCF or .TSK batch task.) (NOTE: The file specification can be either fully qualified, with the volume and path, or relative to the Current Working Directory established through CD or CHDIR.) VOLINFO Displays the currently mounted volumes and their disk space usage. Licensing: ---------- TaskMaster is offered as a licensed software product with continuous right to use so long as the user registers the software and remains in adherence with the terms and conditions of the Software License Agreement. TaskMaster is available the following licensing method: Licensed per File Server at $395.00/Server Under this licensing method, registered users are provided with free updates for the first ninety (90) days and free technical support for the first year following the initial software order. Upgrades after that period are available for a fee which may vary based upon the licensing method. Prices quoted are pre-paid in US Dollars, excluding any applicable sales taxes or export duties. The license fee includes ground delivery within the continental United States (call for quotes on express or non-continental U.S. delivery). The availability of credit terms and invoicing is at the sole discretion of Avanti Technology, Inc. Avanti Technology, Inc. is the manufacturer and sole source for TaskMaster. System Requirements: -------------------- The TaskMaster NLM requires NetWare v3.11, v3.12, v4.0x, or v4.10. CLIB v3.11 rev D or later is required for the TaskMaster NLM to run under NetWare v3.11. The standard CLIB which ships with NetWare v3.12, v4.0x, or v4.10 will support this NLM. Technical Support: ------------------ In order to provide the best and most expedient technical support possible, it is requested that the following information be known prior to initiating technical support contact: Workstation: DOS, IPX/NETx, or VLM versions, plus free RAM size File Server: NetWare version and CLIB revision In addition, the more indepth the problem can be described & isolated (including any error message), the greater the chances are for quick resolution. The following means may be used for technical support: Mail: Avanti Technology, Inc. 13492 Research Boulevard Suite 120-271 Austin, Texas 78750 USA Telephone: (+1)512/335-1168 08:30 to 17:30 (US Central time zone) Facsimile: (+1)512/335-7838 CompuServe: GO LANUTILS (NVENB - Message sec. 17 | 76711,1477) internet: prodinfo@avanti-tech.com or tech@avanti-tech.com