@CLS@@31@ ┌───────────────────────────────────────────────────────────────────────────┐ @31@
 │  Quick Reference            @3F@Event Management @31@            Command Options  │ @31@
 └───────────────────────────────────────────────────────────────────────────┘ @0F@

   @0A@WILDCAT! contains an event processor that can be used to perform certain
   tasks at predefined times during the day or evening.  Up to 65,565 tasks
   can be defined with three methods of execution.  WILDCAT! has 9 internal
   events to choose from plus the capability of executing a batch file.

   Below is a description of the available commands.

      @0E@[@0F@A@0E@]dd      @0F@-@0A@ Create a new event and adds it to the schedule
      @0E@[@0F@D@0E@]isable  @0F@-@0A@ Leave the event in the schedule, but toggle it inactive
      @0E@[@0F@E@0E@]nable   @0F@-@0A@ Enables a previously disabled event
      @0E@[@0F@R@0E@]un      @0F@-@0A@ Execute the specified event now
      @0E@[@0F@K@0E@]ill     @0F@-@0A@ Remove a existing event either enabled or disabled
      @0E@[@0F@S@0E@]chedule @0F@-@0A@ Display last execution date or next scheduled date/time
      @0E@[@0F@H@0E@]elp     @0F@-@0A@ Displays this Help screen
      @0E@[@0F@Q@0E@]uit     @0F@-@0A@ Exit the event processor and return to the SysOp Menu

@0B@┌───────────────@31@ For Detailed Descriptions, select [C]ontinue @0B@────────────────┐
╘═════════════════════════════════════════════════════════════════════════════╛@0F@
@PAUSE@@CLS@@31@ ┌───────────────────────────────────────────────────────────────────────────┐ @31@
 │  Detailed Description       @3F@Event Management @31@            Command Options  │ @31@
 └───────────────────────────────────────────────────────────────────────────┘ @0F@

   @0A@WILDCAT!'s event processor is used to perform certain tasks at predefined
   times of the day or night.  These tasks may range from doing system
   maintenance such as purging deleted messages to running a batch file to
   perform a external maintenance task.  Up to 65,565 events can be scheduled
   for each node on the system.  Events can be selected in one of three
   different execution methods, hard, soft and flexible and can then be
   executed via a shell to DOS, or after actual termination of WILDCAT!

   Shown below is a sample event schedule.

   @0E@#  Act Description  SMTWTFS Type Start   Last Executed          Batch Name
   @0B@-- --- ------------ ------- ---- ------- ---------------------- ------------
   @0F@ 1 Yes Run Batch    XXXXXXX Hard  00:00  Tue 12/03/91 20:28     MAINT.BAT
   @0E@ 2 Yes Reset stats  XXXXXXX Soft  00:01  Tue 12/03/91 20:28

   Current System Clock: @0B@Tue 12/03/91 20:22
   @0E@[@0F@A@0E@]dd, [@0F@D@0E@]isable, [@0F@E@0E@]nable, [@0F@R@0E@]un, [@0F@K@0E@]ill, [@0F@S@0E@]chedule, [@0F@H@0E@]elp, [@0F@Q@0E@]uit?

   @0A@The header information displayed in the example schedule breaks down as
   follows:

        @0E@# -
             @0A@This is the actual event number.  This number is used for
             selecting which event to edit/modify and so on.  This number
             has no effect on actual execution sequence.

        @0E@Act -
             @0A@This field indicates the current status of the event.  Yes
             indicates the event is active and No indicates this event has
             been disabled and will not be executed at the specified time.

        @0E@Description -
             @0A@This indicates the type of event scheduled.

        @0E@SMTWTFS -
             @0A@This indicates the days this event is scheduled to execute by
             the placement of X's under the corresponding letter that is used
             to indicate the day of the week. i.e.  M-Mon, T-Tues and so on.

        @0E@Type -
             @0A@This indicates the execution method for this event, Flex, Soft
             or Hard.

        @0E@Start -
             @0A@Time of the day this event is to be executed.  This is in 24
             hour format (military time).  For example, @0E@[@0F@01:00@0E@]@0A@ indicates 1am
             and @0E@[@0F@21:00@0E@]@0A@ equals 9pm.

        @0E@Last Executed@0F@ or @0E@Next Scheduled Time -
             @0A@This field indicates the date and time the event was last
             executed.  By selecting the option @0E@[@0F@S@0E@]chedule@0A@, this field will
             change and display the next date and time the event is scheduled
             to execute.  The @0E@[@0F@S@0E@]chedule@0A@ option is used to toggle back and
             forth between these two fields.

        @0E@Batch Name -
             @0A@If this event type is selected to run a batch file, this field
             will indicate the name of the batch file that will be used.
             Depending on whether a shell or termination method is chosen,
             WILDCAT! will either execute the file directly or create a
             special copy and then execute it.

   Each event listed will be displayed in alternating colors to help
   distinguish it from the other events.  After displaying the events
   currently scheduled, you are presented with the following prompt.

   @0E@Current System Clock: @0B@Tue 12/03/91 20:22
   @0E@[@0F@A@0E@]dd, [@0F@D@0E@]isable, [@0F@E@0E@]nable, [@0F@R@0E@]un, [@0F@K@0E@]ill, [@0F@S@0E@]chedule, [@0F@H@0E@]elp, [@0F@Q@0E@]uit?

   @0A@Shown below is a description of the available commands.

      @0E@[@0F@A@0E@]dd -
           @0A@This option is used to create a new event.  Selecting this option
           presents the following sub-prompt.

           @0E@[@0F@ 1@0E@] - No  300 baud access    [@0F@ 8@0E@] -  300 baud access Ok
           @0E@[@0F@ 2@0E@] - No 1200 baud access    [@0F@ 9@0E@] - 1200 baud access Ok
           @0E@[@0F@ 3@0E@] - No 2400 baud access    [@0F@10@0E@] - 2400 baud access Ok
           @0E@[@0F@ 4@0E@] - No Sysop Page          [@0F@11@0E@] - Sysop Page Ok
           @0E@[@0F@ 5@0E@] - Reset quick status     [@0F@12@0E@] - Set DOS Next Flag
           @0E@[@0F@ 6@0E@] - Run a batch file       [@0F@13@0E@] - Dump deleted mail
           @0E@[@0F@ 7@0E@] - No Page System Wide    [@0F@14@0E@] - Page System Wide Ok

           Event Type, @0E@[@0F@ENTER@0E@] to abort? [  ]

           @0A@All the above listed events are considered internal with the
           exception of option #6.  These are executed directly without
           dropping to either a shell or via termination.  Option #6 provides
           the ability to execute a batch file from within a shell or after
           termination of WILDCAT!

           Shown below is a breakdown of the available event types.

           @0E@[@0F@ 1@0E@] No  300 baud access -
                @0A@This event is used to disable 300 baud callers for this node
                only.  Each node can turn on 300 baud access or turn it off as
                often as desired.  This event offers the flexibility to
                prohibit low speed calls during peak hours if desired, and to
                determine when the restriction is required (if at all) for
                each day.  When a caller tries to connect at 300 baud and this
                restriction is enabled, they will be sent a display file
                called NO300.BBS indicating the system is not accepting 300
                baud calls and will then be automatically logged off.

           @0E@[@0F@ 2@0E@] No 1200 baud access -
                @0A@This event is used to disable 1200 baud callers from logging
                onto this node.  This is similar to option #1, except when a
                1200 baud caller attempts to log on, they will be sent a
                display file called NO1200.BBS and then logged off.

           @0E@[@0F@ 3@0E@] No 2400 baud access -
                @0A@This event is used to disable 2400 baud callers from logging
                onto this node.  This is similar to option #1, except when a
                2400 baud caller attempts to log on, they will be sent a
                display file called NO2400.BBS and then logged off.

           @0E@[@0F@ 4@0E@] No Sysop Page -
                @0A@This event will turn off the @0E@[@0F@P@0E@]age SysOp@0A@ function found on
                the Main Menu.  When a caller attempts to page the SysOp,
                they will be sent the contents of PAGED.BBS and then given
                the option to leave a comment to the SysOp.  If this event
                is selected, only this node will have this option disabled.

           @0E@[@0F@ 5@0E@] Reset quick status -
                @0A@The quick statistics are displayed on the Idle Screen and
                show the number of calls, messages, downloads and uploads
                since the last time they were reset.  These values can be
                reset to 0 when selecting this event.  This is commonly used
                at midnight every night to indicate the current days totals.
                When this event is executed, the actual values of messages,
                uploads and so on will be recorded in the ACTIVITY.xxx log
                for this node prior to being reset.

           @0E@[@0F@ 6@0E@] Run a batch file -
                @0A@This event is one of the most powerful available.  This lets
                you run a batch file to perform any desired function at any
                time of the day or night.  Batch files for this option may be
                located in any directory since the full path is entered as
                part of the configuration.  Two methods of exiting WILDCAT!
                can be selected, either via a DOS shell, or termination.
                Termination will take the contents of the specified batch
                file and copies it to EVENT.BAT and places it in the nodes
                'work' directory and then executes it.  The shell method will
                execute the batch file directly.

           @0E@[@0F@ 7@0E@] No Page System Wide -
                @0A@This performs the exact same function as option #4, except
                this will disable SysOp pages across ALL the nodes on the
                system.

           @0E@[@0F@ 8@0E@] 300 baud access Ok -
                @0A@This event will enable 300 baud callers if they had been
                previously disabled.

           @0E@[@0F@ 9@0E@] 1200 baud access Ok -
                @0A@This event will enable 1200 baud callers if they had been
                previously disabled.

           @0E@[@0F@10@0E@] 2400 baud access Ok -
                @0A@This event will enable 2400 baud callers if they had been
                previously disabled.

           @0E@[@0F@11@0E@] Sysop Page Ok -
                @0A@This event is used to enable SysOp pages for this node if
                they had previously been disabled.

           @0E@[@0F@12@0E@] Set DOS Next Flag -
                @0A@This event performs the exact same function as pressing the
                F10 key locally.  This might be used to terminate WILDCAT!
                and allow the system to be used for other activities.

           @0E@[@0F@13@0E@] Dump deleted mail -
                @0A@This event purges all deleted messages from the system.  It
                is similar to the SysOp Menu selection @0E@[@0F@P@0E@]urge deleted mail@0A@,
                except it affects all conferences and cannot be limited to
                single conferences as can be done with the SysOp Menu choice.

           @0E@[@0F@14@0E@] Page System Wide Ok -
                @0A@This event performs exactly as option #11 except this will
                enable the SysOp Page across ALL the nodes on the system.

           After selecting the desired event, you are prompted to select the
           day(s) of the week this event is to be executed and shown below is
           the following sub-prompt.

           @0E@Execute event on:

            @0E@  [@0F@1@0E@] - Sunday
            @0E@* [@0F@2@0E@] - Monday
            @0E@  [@0F@3@0E@] - Tuesday
            @0E@  [@0F@4@0E@] - Wednesday
            @0E@  [@0F@5@0E@] - Thursday
            @0E@  [@0F@6@0E@] - Friday
            @0E@  [@0F@7@0E@] - Saturday

           @0E@[@0F@1..7@0E@], [@0F@E@0E@]very Day, [@0F@C@0E@]lear all, [@0F@A@0E@]bort, [@0F@S@0E@]ave & Continue? [S]

           @0A@Selecting the appropriate option will update the display with an
           asterisk (@0E@*@0A@) indicating the day(s) have been selected for this
           event to execute on.  Shown below is a description of the
           available options.

                 @0E@[@0F@1..7@0E@] -
                      @0A@These numbers are used to select the corresponding days
                      of the week to execute the event on.

                 @0E@[@0F@E@0E@]very Day -
                      @0A@This option is used to select every day of the week to
                      execute this event.

                 @0E@[@0F@C@0E@]lear all -
                      @0A@This option will clear all previously selected days to
                      execute this event.

                 @0E@[@0F@A@0E@]bort -
                      @0A@This option is used to stop the creation of this event
                      and redisplays the list of previously scheduled events.

                 @0E@[@0F@S@0E@]ave & Continue -
                      @0A@This will save the days selected, indicated by an
                      asterisk next to the day(s) and continue on to the
                      selection of the execution method.  After selecting
                      this option, the following sub-prompt appears.

                 @0E@Execution method:

                 [@0F@F@0E@]lexible - Execute during non busy flex hours.
                 [@0F@S@0E@]oft     - Execute after call, nearest to schedule time.
                 [@0F@H@0E@]ard     - Execute at schedule time, force caller off.

                 [@0F@A@0E@]bort new event

                 Event Type? [S]

                 @0A@Below is a description of the available event execution
                 methods.

                 @0E@[@0F@F@0E@]lexible -
                      @0A@Flexible events are those that must execute sometime
                      during the day they are scheduled.  Two settings in
                      MAKEWILD help control flexible events;  1) Inactivity
                      before flexible events and 2) Time to begin forcing
                      flexible events.  These two items from MAKEWILD General
                      Info - 2, options #14 and #15 control execution since
                      flex events are always executed during idle time when
                      the system is not taking calls.  A flex event will look
                      for an opportunity to execute on the day specified
                      starting at one second after midnight, and will succeed
                      as soon as the amount of idle time is equal to or
                      greater than the "Inactivity before flexible events"
                      option in MAKEWILD.  The default is 5 minutes of
                      inactivity.  If the minimum amount of time has not
                      occurred by the "Time to begin forcing flexible events"
                      the flex event will execute regardless of inactivity,
                      immediately following the next call.  In effect, the
                      flex event becomes a Soft event.

                 @0E@[@0F@S@0E@]oft -
                      @0A@These are events that need to execute at or near a
                      specified time, but can wait until a caller is finished
                      before executing.  Soft events execute at a time
                      specified if no one is online, but if a caller connects,
                      even a minute before the scheduled time, the event is
                      postponed until the call is completed.  The event will
                      then execute immediately after the call.  Many events
                      can be classified as soft events and it is the default
                      response.

                 @0E@[@0F@H@0E@]ard -
                      @0A@Hard events are those that absolutely MUST execute at
                      the time specified.  A hard event will reduce a caller's
                      online time before the event, and actually forces the
                      caller off if they fail to say @0E@[@0F@G@0E@]oodbye@0A@ after a 5 and
                      then 2 minute warning.  No calls are taken within 5
                      minutes before a hard event, and time in doors and
                      external protocols can be monitored by the use of a TSR
                      called TIMEOUT.EXE (included with WILDCAT!).

                 @0E@[@0F@A@0E@]bort new event -
                      @0A@This option will allow you to exit the creation process
                      and returns you to the list of scheduled events.

                 Once the execution method has been chosen, you are then
                 prompted for the time to start the event.  This start time is
                 then entered in a 24 hour format (military time).

                 If the event type selected was "Run a batch file", you will
                 then be required to select the exit method of WILDCAT!  You
                 will prompted as follows.

           @0E@[@0F@S@0E@]hell     - Execute a Dos Shell and execute batch file directly.
           @0E@[@0F@T@0E@]erminate - Copy Batch file to "EVENT.BAT", then terminate WC!

           [@0F@A@0E@]bort new event

           Method? [S]

                 @0A@Below is a description of the various execution methods.

                 @0E@[@0F@S@0E@]hell -
                      @0A@The shell process can be invoked with no SysOp
                      intervention or configuration except for creation of
                      the batch file to be run.  This batch file name can be
                      anything desired, but must exist in the correct
                      location assigned after selecting the execution method.
                      Since WILDCAT! will swap out to either EMS or disk,
                      the batch file MUST NOT RESTART WILDCAT!.  After all
                      the maintenance is performed, the batch file should just
                      simply end and then WILDCAT! will resume normally.  The
                      ideal method is to enable swapping and to use the shell
                      method.

                 @0E@[@0F@T@0E@]erminate -
                      @0A@This method will remove WILDCAT! from memory and then
                      copies the contents of the batch file specified to
                      the nodes 'work' directory and under a new name of
                      EVENT.BAT.  This new file will then be executed from
                      the nodes 'work' directory.  However, since WILDCAT!
                      terminates after creating the EVENT.BAT file, it is the
                      responsibility of the SysOp to include commands that
                      will restart WILDCAT! via the nodes CAT.BAT file.  For
                      a detailed explanation of this method and the associated
                      requirements, refer to the WILDCAT! SysOp's Guide.

                 @0E@[@0F@A@0E@]bort new event -
                      @0A@This will abort the creation process and return to the
                      list of scheduled events screen.

           After the event has been created, WILDCAT! will then add it to the
           list of scheduled events and you will be returned to the scheduled
           events screen for additional activities.  Any events added will now
           be active and will execute according to their respective parameters.

      @0E@[@0F@D@0E@]isable -
           @0A@This option is used to temporarily suspend an event.  After
           selecting the appropriate event number, this will toggle the 'Act'
           field to NO indicating this event will NOT be executed.

      @0E@[@0F@E@0E@]nable -
           @0A@This option is used to re-activate a previously @0E@[@0F@D@0E@]isabled@0A@ event
           number.

      @0E@[@0F@R@0E@]un -
           @0A@Selected events can be forced to immediately execute when using
           this option.  This can be useful to test newly @0E@[@0F@A@0E@]dded@0A@ events for
           proper operation.

      @0E@[@0F@K@0E@]ill -
           @0A@This option is used to delete a previously scheduled event from
           the list.

      @0E@[@0F@S@0E@]chedule -
           @0A@This option will toggle information displayed between Last Executed
           and Next Scheduled Time for the events listed.  The last executed
           field indicates the last date and time this event was run and the
           next scheduled time will display the date and time when they will
           be executed next.

      @0E@[@0F@H@0E@]elp -
           @0A@Displays this Help screen.

      @0E@[@0F@Q@0E@]uit -
           @0A@Exits the Event Management option and returns to the SysOp Menu.


@0B@┌──────────────────────────@2F@ End of Help Information @0B@──────────────────────────┐
╘═════════════════════════════════════════════════════════════════════════════╛@0F@
