DP Tool Club 8/CDASC08.ISO/VRAC/TASKER19.ZIP/TASKER.DOC

Text File | 1993-08-29 | 19KB | 493 lines

                              TASKER ver. 1.9
                 Copyright (c) 1993 SkinnyMan Applications
                            All Rights Reserved

LET'S GET DOWN TO BUSINESS:

   If you want to try tasker without reading this well written and concise
   document,  run TASKER /A from the same path as the EXE, add a task, set
   your pc time to about 10 seconds prior and run TASKER.  After that, do the
   same only try the /redir option (TASKER /redir).  Look at the REDIR.TXT
   file.  Go ahead, put in any command, program or batch file (for batch
   files please use 'call'.  ex.  CALL BATCH1.BAT).  Give it a
   good work out.  Then check out the rest of this doc for all it's options
   and features.

   Support info is at the end of this doc for easy access.  Please don't
   hesitate to contact me for any reason during the evaluation period.

   This is an evaluation copy only.  If you continue to use this utility
   beyond 30 days please register.  By registering you receive free upgrades,
   support, the ability to suggest enhancements to future versions, etc...

                    SkinnyMan

WHAT IS TASKER?

   Tasker is an unattended program dispatcher.  It will execute any
   program and parameters, or command line input
   (Copy, dir, ren, md, del *.*, etc.. ) at any prescheduled time.

   This is great to load on unattended pc's for executing backups,
   production jobs, batch files, etc...

TASKER FEATURES:
   Jobs can be scheduled to run:
   -   Every day.
   -   Every business day (Mon - Fri).
   -   Every day for a specific month.
   -   On a specific day of the week every month.
   -   On a specific day of the week for a specific month.

   Tasker has the flexibility of using any specified taskfile.
   -   One way to use a specific taskfile is run Tasker from the same
       directory as your taskfile (provided its name is TASKFILE.TXT).
   -   You could also use the /t option and give tasker a full path and
       taskfile name (whatever name you choose).
   -   If neither option is used, and TASKER.EXE is in your PATH, it will
       use the default taskfile (same directory as tasker.exe)
   -   This taskfile flexibility makes Tasker multi-user (LAN) compatible.

      For example:

      If the tasker.exe file resides on a LAN everyone can use the same .EXE
      (Multi-User Registration Available) and be able to specify their own
      personal taskfile.

                                  - 1 -
     LAN administrators can take advantage of the default taskfile feature
      to have all LAN users use the same taskfile to execute LAN utilites
      off-hours so when they arrive their pc is ready for the day.  Have
      users load Tasker before they leave for the day to:
      -   Run virus scanning software.
      -   Disk cleanup utilities.
      -   LAN utilities.


   Comprehensive and informative logging feature.
   -  A log file keeps track of tasker activity, errors and other
      information.
   -  It will give you the status of the spawn, as well as, the return
      status of most programs so you can see if your program had trouble.
   -  Your logfile will reside in the same directory as your taskfile
      by default.
   -  You can also specify your own log file and location using /t.  This
      is great for LAN user's so they can have their own log file.



   Screen redirection to a text file while tasks are executing.
   -   By using the /redir option you can redirect all your screen output
       to a flat file so you can see exactly how your task executed.  No
       need to spend time wondering how a task performed while you were
       away.
   -   Save task activity for tracking purposes or see if any of your
       programs generated any problems or errors.
   -   The redirection file will alway reside in the same directory as
       the taskfile.  This could be useful for LAN administrators to be
       able to see exactly how each user's tasks performed.

   Does not necessitate a 'command /c' when executing DOS environment
   functinos such as: Copy, dir, ren, md, del *.*, etc...

   Swaps TASKER.EXE out of your conventional memory when your tasks execute.
   -  TASKER.EXE will swap itself to EMS, if present.  If no EMS is present
      it swaps TASKER to disk, thus freeing virtually all conventional memory
      TASKER was using so your tasks can run optimally.


                                  - 2 -
   No Schedule Conflicts
   -   Tasker will execute ALL jobs scheduled even if one runs beyond the
       execution time of the next scheduled task.  It will simply run the
       next task immediately upon completion of the previous one.
   -   It will still finish all scheduled tasks if one happens to run beyond
       midnight.  Tasker will simply execute the remaining tasks in succesion.
   -   Tasker will not miss early morning tasks should a task from the
       previous night run beyond a scheduled job for the next day.

       Below is an explanation of the 'No Schedule Conflicts' feature:

       Example schedule for Tuesday and Wednesday morning:
         Task 1 is scheduled for 4 pm on Tuesday.
         Task 2 is scheduled for 4:15 pm.
         Task 3 is scheduled for 11:30 pm.
         Task 4 is scheduled for 11:45 pm.
         Task 1 for Wednesday is scheduled for 1 am.

       Execution:
         Task 1 executes at 4 pm but runs until 4:30.
            Tasker will detect that Task 2's execution time has
            been surpassed and immediately execute it.

         Task 3 executes at 11:30 but runs until 2am Wednesday morning.

            Upon the completion of Task 3, Tasker will detect that it is
            past midnight and immediately execute all remaining tasks for
            Tuesday in succession.

            Tasker, upon loading the tasks for Wednesday, will detect that
            the previous night's Tasks have run over the execution time of
            Task 1 and immediately execute it (and any other tasks that have
            been surpassed).



REQUIREMENTS:

  Tasker will run on any AT compatible PC running DOS 3.3 & higher.  (an OS/2
  version may soon follow)

  You can run tasker from a floppy (although loading will be slower) or
  your hard disk.

  Tasker should be in your DOS PATH in order to utilize more of it's
  features.

  Tasker needs about 100K of ram when its waiting to run or waiting for
  midnight.  Don't panic though because Tasker swaps itself out of RAM
  when executing it's tasks.

  For windows, if you have a nominal amount of memory this should not be
  a problem.


                                  - 3 -

BASIC FLOW:

   Upon starting Tasker it will check the taskfile for any tasks that
   might be scheduled for the rest of that day.  If any tasks are
   present it will execute each task at their specified time until all
   tasks have been executed.  It will then wait until midnight to read
   the taskfile again and start the process over.


O  Choosing your taskfiles:

      Most users will have just one taskfile (default) but for those who need
      more than one taskfile, this section is for you.

      When you type TASKER (without the /t) Tasker will first look for it's
      TASKFILE.TXT in the current directory.  If not present Tasker will
      look for the default taskfile.txt (same directory as TASKER.EXE).  If
      that is also not present you will be informed that there are no tasks
      present and to add tasks.

      You can specify your own taskfile name and location by using the /t
      switch.  Example:

            TASKER /T C:\MYDIR\JIMSTASKS.TXT

      You can just use /T without the path/filename.  Tasker will prompt you
      for a path/filename for your taskfile and log file (this is how you
      can specify a log file in a different location than your taskfile).

      The /T switch can be used in conjuction with the /a, /d and /r options
      as long as the option comes before /T.  Thusly:

            TASKER /A /T [PATH/FILENAME]


O  Entering Tasks:

   -  To enter tasks type:

         TASKER /A

      Caution: If you have more than one taskfile be sure you are using
               the right one.  See 'Choosing your taskfiles'.

                                  - 4 -

O  Creating Tasks:

   -  To create a default taskfile (TASKFILE.TXT) type:

         TASKER /A

      with no parameters.

   -  To create a taskfile in another directory use the /t option.

         TASKER /T C:\MYDIR\TASKFILE.TXT

      Note:  keeping the filename TASKFILE.TXT will allow you to use this
             taskfile just by typing TASKER from the same directory.  If the
             filename is other than TASKFILE.TXT you will need to use
             the /t switch.


O  Removing Tasks:

   To remove tasks type:

      TASKER /R

   You will be prompted to 'Enter the Task Number to Remove'.  Type the
   desired task number and Tasker will display the task along with an
   'Are You Sure' screen.  Your task will then be removed.  If you want to
   delete all tasks just delete the taskfile and start over with a Tasker /A.


   Note: If you have more tasks than can fit on your screen you will be
         prompted to 'Continue Viewing' after the first screen.  If
         you know what task number you want to remove, answer 'N' and the
         removal steps will continue.

  Caution: If you have more than one taskfile be sure you are using
           the right one.  See 'Choosing your taskfiles'.


O  Display your tasks for viewing:

   To display your tasks type:

      TASKER /D

   Note: If you have more tasks than can fit on your screen you will be
         prompted to 'Continue Viewing' after the first screen full.

   Caution: If you have more than one taskfile be sure you are using
            the right one.  See 'Choosing your taskfiles'.

                                  - 5 -

O  Activating screen redirection to a flat file.

   To activate screen redirection type:

      TASKER [/t [path/filename] ] /redir

   Note: The /redir switch MUST be the last parameter.  Your redirection
         file will always reside in the same directory as your selected
         taskfile.  (The next version will be more flexable with the
         location of the REDIR.TXT file.)


O  To use Tasker in a Windows environment:

   Add Tasks to your default taskfile using DOS then edit the PIF file for
   the location of TASKER.EXE and any parameters (/t or /redir).  Tasker
   will then function in the background while you do other things.

   You can load tasker (minimized) automatically every time you run windows.
   To do this, add TASKER.PIF to the 'load=' command in your WIN.INI file
   (first few lines).  Now Tasker will load up minimized and will execute
   your tasks in the background.

   Note: Tasker is not a windows utility but by using the pif it can run
   in a Windows environment.

FILE NAMES & LOCATIONS:

   File:                  File Name:           Location:

   Default Taskfile:          TASKFILE.TXT \ _ Same directory as
   Default Log file:          TASKLOG.TXT  /   TASKER.EXE.

   Taskfiles in other
   locations:                 TASKFILE.TXT \
   Log files in other                        - Your choice of directories
   locations:                 TASKLOG.TXT  /


   Taskfiles by a name
   other than TASKFILE.TXT    Your choice \
   Log files by a name                      -  Your choice of directories
   other than LOGFILE.TXT     Your choice /

   Screen Redirection file:   REDIR.TXT         Same directory as your
                                                selected taskfile.

                                  - 6 -

HINTS:

O  If you plan on using only one taskfile I suggest you stick to the
   default location (create it just by typing TASKER /A with no parms).
   This way you will not have to concern yourself with /t.  For one
   taskfile this is the easiest way.

O  If you are going to use your own taskfile name you must use the /t switch.

O  Have TASKER.EXE in your path.  If you are unsure on how to do this look
   up 'PATH' in your DOS manual.

O  If you are calling a batch file, use the DOS 'call' function in your
   task, (ex. CALL TEST.BAT).  Tasker will act unpredictable if 'call' is
   not used for batch files.

O  Command Line Piping functions do not work with Tasker unless called from
   a batch file.  For instance, if you want to log in to a network and
   pipe in a password you can 'call' a small batch file to do this.

      Example:  You want to login to a network and execute some commands.

            Task1:      call log.bat
            Task2:      normal command1
            Task3:      normal command2
            Task4:      normal command3

      log.bat:
            REM load Lan drivers if not already loaded
            F:LOGIN jimmy <c:\mypass.txt


O  You can edit your taskfile using a standard editor although it is quick
   and easy to remove the task and re-add it using Tasker.  If you edit be
   careful, if you misplace even one character other than the task, Tasker
   will be unforgiving and produce an "Invalid Data in Taskfile" message or
   otherwise perform unpredictably.  I was able to edit mine using Brief as
   my editor and had no problems. I cannot guarantee what other editors
   might do to the taskfile.

   I realize I do not have a task edit feature yet, this is why I have
   tasker write your tasks out to a flat file (instead of using encryption)
   and allow minor editing.  An edit feature should be in the next version.

   Here are some editing tips:

   -  Make sure your last character in the taskfile is the last charactor
      of your last task.  Do NOT add a carrage return.  Again, your file
      should end at the end of your last task, not on the next (blank) line.

   -  It is advised to make a backup of your taskfile before you edit it.


                                  - 7 -

   o  Here is how each line of the taskfile works:

      ########Task

      - The first 2 numbers represent the month (99 means every month).
        The third number is the day of week (0 = Sunday, 1 = Monday, etc...)
        9 means everyday.
      - The next (fourth) number is a weekend switch, 0 if weekends included,
        1 if just every business day (this number is ignored unless everyday
        was selected)
      - The next 4 numbers represent the time (hours and minutes, military time).
      - The remaining characters is your task.

        Examples:  99500500call c:\jimslog.bat (every month, every Friday at
                                                5am call my login batch file)

                   99910700Virscan c: /a /v    (every month, every business
                                                day at 7am run a virus
                                                scanner with parms)


NOTES:

O  This program shells out to execute your tasks.  You will see in the logs
   and on screen a Spawn Status (ex. "Spawn Successful").  When a spawn is
   successful this does not mean that your program was.  Tasker is just
   letting you know it successfully spawned another command.com for your
   program.  Please verify each of your program's success.

O  Be advised that if you decide to use tasker in a Windows environment,
   Tasker does use approximately 90K of memory.  If you have a sufficient
   amount of memory for windows than this should not effect the system. A
   reminder that when tasker executes it swaps itself out of memory.

O  Because DOS environment calls (dir, ren, copy, etc...) normally would
   require a 'command /c' for the spawn function and program files do not,
   I have provided a feature so you would not have to decide if a
   'command /c' is needed or not.  Tasker will first attempt to execute
   them normally, if this fails it will precede the command with a
   'command /c' which will then function.  If your program returns an
   error, it will attempt to re-execute it with a 'command /c'
   (transparent).  So, if you notice in your redir.txt file and log file
   that it executed twice, this is the reason.

      For example if you tried to execute "TYPE C:\AUTOEXEC.BAT" and the
      file does not exist, tasker will return the DOS error but it will
      then try and run "command /cTYPE C:\AUTOEXEC.BAT" which will succeed.



                                  - 8 -


O  If you have one of your tasks logging in or out of a Novell network, be
   advised of the path errors you might receive depending on the following
   scenarios:

      If you are already logged in and have search maps, and then you login
      again through one of your tasks, Novell will append any search maps
      in your login script to your path (doubling your search maps in your
      path) then after you logout, Novell strips only one set of search maps
      off your path but your original set will still exist although you
      will be logged out.  You will receive "invalid drive in search path"
      errors.  Be careful.  Be sure you are logged out before any of your
      tasks log you in.  Also, it is easiest to perform multiple network
      tasks within a batch file.  If you login in one task your path and
      environment can become unreliable.  A Novell Network is the only one
      I have access to and was able to test.  Because it is a dos bases app
      it would perform on other dos type networks just as well.


THANKS:

   I would like to thank Ira Ashkenes (IJ Software) for all his insight
   and support in creating this utility.  Also, thanks to F. PIETTE for
   his ideas in screen redirection.

SUPPORT:

   If you have any questions or problems do not hesitate to contact me at

       703-368-8990 (Virginia).

   If there's no answer leave a message and I will promptly return your call.

   I can also be reached electronically on CompuServe.  My mail address is:

   72713,713.

   Thank you for trying Tasker.


   JIM


LEGAL MUMBO JUMBO

  These documents and all referenced and related program files are
  copyrighted by SkinnyMan Applications and is protected under the
  copyright laws.












                                  - 9 -