Munis. Using Munis Scheduler Version For more information, visit

Transcription

1 Munis Using Munis Scheduler Version 10.5 For more information, visit

2 TABLE OF CONTENTS Using Munis Scheduler... 3 User Permissions... 4 Scheduler-Enabled Programs... 5 Scheduler Queue... 6 Scheduler Menu... 6 Pause... 7 Properties... 7 Log... 7 Job Menu... 8 View Menu... 9 History Menu Queue Status Queued Jobs Scheduled Jobs Scheduler Engine Setup Tab Report Scheduling In Background (Now) At a Scheduled Time Notifications Appendix A Log Events Using Munis Scheduler, Version 10.5 Page 2

3 Using Munis Scheduler Munis Scheduler automates report and import/export processing at predetermined intervals. Scheduler automatically prints or saves results, and sends when jobs start, complete, or expire. The text file or PDF report storage options are available. In order to use Scheduler, the Enable Scheduling Dialog check box must be selected on the Setup tab for the Scheduler Engine program, and your system administrator must assign scheduler privileges to at least one role assigned to your user name. To receive alerts, a correct address must be included in your User Attributes record. Once the system administrator has enabled Scheduler privileges for you, programs that are enabled to work with Scheduler display the Execute This Report list. The Execute This Report list has three options: Now, In Background (Now), and At a Scheduled Time. Jobs scheduled to run on the thirty-first of each month run on months with 31 days. To schedule a job to run at the end of every month, select Daily, Monthly, or similar options from the date lists in programs. If your organization uses Tyler Content Manager for Munis, you can store reports in the Tyler Content Manager database. If you have the appropriate permissions, you can also include a link to the document in the notification . You must have the TylerCM Single Document Viewer installed in order to include document links in notification s. When you install Munis, the Munis Scheduler functionality is automatically installed. However, there is some manual setup and configuration that must take place before jobs can be scheduled. System administration personnel should be responsible for the setup and configuration of Munis Scheduler for your organization. Using Munis Scheduler, Version 10.5 Page 3

4 User Permissions System administrators must assign permissions for each Munis role that should include Munis Scheduler access for creating reports. In the Munis System Roles program (System Administration > Security > Roles > Munis System), the level of access given to individual users is determined by the Scheduler File Maintenance Access list. In addition to assigning permission levels, the Scheduler group in this program identifies additional Scheduler permissions. Scheduler Scheduler Engine Administrator Submit Jobs to be Scheduled Allowed to Include Document Links in Scheduler Notifications When this check box is selected, users assigned to the role can start up, pause, or resume the Scheduler Engine. When this check box is selected, users assigned to the role are able to use Munis Scheduler when processing reports, imports, and exports. When this check box is selected, links to documents are included in Scheduler notifications for jobs scheduled by users assigned to the role. Using Munis Scheduler, Version 10.5 Page 4

5 Scheduler-Enabled Programs Programs that are compatible with Munis Scheduler include the Execute This Report list on the screen. This list determines how the report is managed using Munis Scheduler or not using Munis Scheduler. The Now option creates the report immediately, without using Munis Scheduler; In Background (Now) or At a Scheduled Time schedule the report and notification options using Munis Scheduler. Some Scheduler-enabled programs include relative dates and times in addition to the specific definitions. For example, the Monthly Trial Balance by Fund Report can be defined based on a specific year/period, or it can be defined to run for the current or previous period. In this case, the program uses the selected option to determine the report parameters. For example, in the Monthly Trial Balance by Fund program, the General Ledger Settings program s current year and period determines the value of current or previous. The use of Using Munis Scheduler, Version 10.5 Page 5

6 relative definitions and the default time period varies from program to program. Programs are not limited to specific options; for example, options such as Last, First, and Next may also be used by various Scheduler-enabled programs. Scheduler Queue The Scheduler Queue program is available on the System Administration menu. This program displays all scheduled jobs that have not completed. It also gives status and recurrence information. If you make changes to the properties, the program directs the Scheduler Engine to restart and include the changes. On the Scheduler Queue screen, the Queue tab lists the job description, job, next schedule run, status, recurrence schedule, and the user ID of the person who initiated the job. Doubleclick the job entry in the list to modify the individual job entry details. Scheduler Menu The Scheduler menu provides options for pausing the engine, viewing the engine properties, or viewing the engine log. Using Munis Scheduler, Version 10.5 Page 6

7 Pause The Pause option displays a Pausing Engine dialog box. Select the parameter for pausing the engine and then click OK. Properties The Properties option opens the Scheduler Engine program. See the Scheduler Engine section for details on this program. Log The Log records entries for activities on the Scheduler Engine. When the engine sleeps or is paused, when a new job is scheduled, changed, run, or deleted, and when a change to the setup is made, the program makes an entry in the log. See Appendix A for log event descriptions. Using Munis Scheduler, Version 10.5 Page 7

8 Job Menu The Job menu option manages individual jobs in the queue. Highlight the job in the queued table, and then use the Job menu options to change the job settings. To change the status of a job from Scheduled to Held, select Hold, which prevents a job from running at its next scheduled occurrence. Release Hold resumes the job. Run Now runs the job s next scheduled occurrence immediately. When you highlight a detail job row on the Queue or History tab and then click Job Parameters, the program displays the Job Parameters screen with the parameters saved for the job. You can also view parameters by right-clicking a job and selecting Job Parameters from the menu. Using Munis Scheduler, Version 10.5 Page 8

9 The Properties option displays a dialog box similar to the Scheduler dialog box; use this option to update the job details. View Menu The View menu determines which jobs the program displays: only jobs that you queued, jobs queued by your department, jobs queued by other users or other departments, or all jobs queued. Using Munis Scheduler, Version 10.5 Page 9

10 History Menu The History menu provides the display selections for the History tab. Use these selections to determine the events to view or the time period of jobs to include. The History tab displays past events or occurrences of jobs. It also displays the times jobs started or ended, when they were deleted, and the result (whether or not the job completed successfully or if it failed). When you delete a recurring job, you can delete the entire recurring job or only the currently queued entry. The Scheduler Queue screen does not allow you to delete jobs that appear to be in-progress; however, you can delete jobs at any time using the Scheduler Engine. This allows you to update the queue if a job does not complete properly. After confirming that a job is to be deleted, the program changes the status to Deleted and creates a history entry to indicate when and by whom the job was deleted. The Scheduler Engine removes any deleted queue entries on the next idle processing cycle. If there are no future occurrences of the deleted job, the job record status is updated to deleted, after which the job record remains only for historical purposes. Using Munis Scheduler, Version 10.5 Page 10

11 Queue Status The engine scans for completed jobs during its idle processing when the engine is online and paused. When a nonrecurring job has been run, the job record s status is immediately updated to Complete and the queue entry is removed. If a recurring job has been run, the next occurrence is calculated based on the recurrence pattern. If no future occurrences exist, the job record is updated to Complete and the queue entry is removed. If another occurrence exists, the job record remains Active and the queue entry is updated to the next occurrence date. The queue entry is updated to Scheduled or Held according to the Hold Next Occurrence if a Recurring Job Fails check box on the Setup tab. When a nonrecurring job has been deleted or if all occurrences were deleted, the job record status is immediately updated to Deleted and the queue entry is removed. If a single occurrence of a recurring job has been deleted, the next occurrence is calculated based on the recurrence pattern. If no future occurrences exist, the job record is updated to Deleted and the queue entry is removed. If another occurrence exists, the job record status remains Active and the queue entry is updated to the next occurrence date with a status of Scheduled. When a nonrecurring job expires, the job record status is immediately updated to Expired and the queue entry is removed. If an occurrence of a recurring job expires, the next occurrence is calculated based on the recurrence pattern. If no future occurrences exist, the job record is updated to Expired and the queue entry is removed. If another occurrence exists, the job record status remains Active and the queue entry is updated to the next occurrence date with a status of Scheduled or Held. Queued Jobs When online, the Scheduler Engine runs queued jobs during its idle process. Queued jobs with a status of Scheduled are executed as they come due or are found to be overdue. (Jobs may become overdue if placed on hold beyond their scheduled run time or if the engine is taken off-line for any length of time.) Once a job reaches its scheduled run time, the job s target program is launched using the command stored in the job record during creation. A history record is created to note that the job was run. When the target program completes, the queue entry is updated to a status of Ran OK, indicating a successful job run, or Ran w/error, indicating an unsuccessful job run. The queue entry update is made through a call to a Scheduler API function. This also updates the end date and time stamp for the run history record. When a recurring job fails to complete successfully, the next occurrence will be placed on hold if the Hold Next Occurrence if a Recurring Job Fails check box on the Setup tab is selected. Scheduled Jobs During idle processing, the engine scans for jobs that do not already exist in the queue. This occurs when the engine is online or paused. For each new job, a queue entry is made using the requested schedule to compute the next run date and time. Only one occurrence of a scheduled job can be seen in the queue at any time. The next occurrence entry is Using Munis Scheduler, Version 10.5 Page 11

12 automatically created when the current one runs. A history entry is made each time a job is queued. Once a job is in the queue, it is viewable on the Queue tab of the Scheduler Queue program. The queue displays are sorted chronologically based on the next run date and time, with a sub-sort on job number. Once the job completes, the status again reads Scheduled, but the Next Run reflects next week s occurrence. Queue Maintenance also displays the next occurrence and adds an entry to the history record for the previous occurrence. Using Munis Scheduler, Version 10.5 Page 12

13 Scheduler Engine The Scheduler Engine provides a real-time view into Scheduler activity. To access the Scheduler Engine, select the Properties option from the Scheduler menu in the Scheduler Queue program. The Engine may either be online or paused. The initial engine startup mode setting determines which mode the engine initializes to when first opened. A paused engine updates the queue as new jobs are scheduled, but does not run scheduled jobs. The Resume After Inactivity setting forces the engine back to the Online mode after it has been paused. By leaving the field blank, the feature can be turned off. Using Munis Scheduler, Version 10.5 Page 13

14 Setup Tab The Setup tab determines the engine settings, including jobs and log event details. Field Setup Tab Engine Initial Engine Startup Mode Resume After Inactivity of Max Concurrent Jobs Run Command Delay Queue Scan Delay Idle Loop Delay For Daily Maintenance Description This list indicates the mode in which the engine starts: Paused or Online. This box specifies the number of seconds the engine remains inactive before automatically resuming activity. If this box is blank, the engine does not automatically resume activity. This is the maximum number of jobs the engine can accept before waiting for the current job to complete. The Scheduler Engine can run multiple jobs at once; however, jobs with identical start times are separated by a minimum of a one second delay. Both the number of concurrent jobs and the run delay are configurable using the Maximum Current Jobs and Run Command Delay settings. Complete the Maximum Current Jobs box to control the activity level at a specific type. For example, you may want to manage activity to ensure there are no server issues. In order to support concurrence, jobs are launched immediately from the engine through a stub-launcher program. The stublauncher program executes the program with waiting and reports the completion of the program using a provided Scheduler API function. The job queue displays only the current occurrence of recurring jobs and jobs that do not recur. This is the time delay in seconds between sequential program launches. The value of this box must be greater than 0; it cannot be blank. This check box, if selected, causes the engine to use queue scan delay. Queue scan delay controls how often the engine queues new jobs, runs pending jobs, removes expired jobs, deletes jobs, queues a job again, and inactivates completed jobs. This box identifies the time delay between idle processing to perform tasks on a regular interval. Idle processing only occurs when the Queued Jobs tab is the active tab. Idle Loop Delay controls how often the engine updates its current time display, polls to determine if the maintenance period (if any) has been reached, and looks for a status change from Scheduler Queue. The value of this box must be greater than 0; this box cannot be blank. To avoid conflicts with overnight maintenance and backups, Scheduler Engine allows a daily maintenance configuration. The engine can be set to either Sleep or Shutdown during a specified Using Munis Scheduler, Version 10.5 Page 14

15 Field Maintenance Start and End Maintenance Restriction Restriction Period Description window of time. This list allows you to configure daily maintenance time: Sleep - The engine disconnects from the database and remains idle until the end of the maintenance period. When the end of the period is reached, the engine reconnects to the database and resumes processing. While the engine is asleep, a screen displays a message that the engine is sleeping and how much time remains until it awakens. Maintenance mode can be cancelled from this dialog to allow the engine to resume processing early. Shutdown - The engine completely exits when the maintenance period is reached. Thirty seconds prior to exiting, a screen displays a message that indicates that the maintenance period has been reached and that shutdown is imminent. This message provides an opportunity to cancel the maintenance mode and continue processing jobs. If the engine is restarted during the maintenance period, this message is presented and unless Cancel is chosen, the engine shuts down again. Remaining Running - There is no maintenance period or associated warnings or error messages. These settings are retained; this selection is intended as a temporary suspension of maintenance. The engine is not able to proceed to maintenance mode until all running programs have completed. You cannot force jobs to stop running. To minimize this potential conflict, a premaintenance restriction period can be configured to either Warn But Allow or Error and Disallow scheduling within a defined period of time leading up to the maintenance window. The Customize Message option allows system administrators to customize the text of the disabled or warning message. These boxes define the start and end times for the maintenance periods. These boxes are not accessible if Remain Running is selected from the Maintenance Mode list. This list indicates if users are able to schedule jobs during the time prior to maintenance: Warn But Allow - Warns users that maintenance is pending but allows them to schedule a job. Error and Disallow - Prevents users from scheduling jobs during the premaintenance period. Allow (no message) - Allows all users to schedule jobs during the premaintenance period with no error or warning. This box determines the amount of time prior to maintenance that you can schedule jobs. Using Munis Scheduler, Version 10.5 Page 15

16 Field Connection Loss Timeout Timeout Notification Address Jobs Jobs Expire if Not Run After Retain Job History For Hold Next Occurrence if a Recurring Job Expires Hold Next Occurrence if a Recurring Job Fails Logging Activity Logging Level Auto-Increment Log Name Scheduling Dialog Description This box specifies the number of times the engines attempts to connect to the host work station when an error occurs. This box provides the address to which notifications are sent when a connection timeout occurs. This is how long an overdue job stays in the queue. Jobs may become overdue if placed on hold beyond their scheduled run time or if the engine is taken off-line for any length of time. If the expiration setting is blank, overdue jobs can exist forever. If the expiration setting has a value of one or more, jobs expire when the number of past-due hours reaches the expiration setting. A history entry records when a job expires. This is the amount of time history is retained. The Scheduler Engine automatically removes history entries. Purging occurs during idle processing when the engine is on line. Any history older than this setting (in days) is deleted. Inactive jobs are removed after all of their history has been deleted. This check box, if selected, causes the next occurrence of a job to be put on hold when a recurring job expires. This check box, if selected, causes the next occurrence of a job to be put on hold when a recurring job fails. This list indicates which events are logged: None - The program does not create an activity log. Critical Only - The program creates a log of only critical events. All Activity - The program creates a log of all events. The log name is generated using the engine program name (mescheng), concatenated with the engine number and the database name, ending with a suffix of.log. The engine can be configured to start a new log each time it starts. If you select the Auto-Increment Log Name check box, the file name also includes a 3-digit file counter, which is increased by one each time the engine is initialized. The current log file name is displayed in the Setup tab in the Logging group. This check box, if selected, causes the program to generate a new log file name when the engine is reinitialized. Using Munis Scheduler, Version 10.5 Page 16

17 Field Enable Scheduling Dialogue Default Start Time Background Delay Default Job Start Notification Default Job End Notification Default Job Expired Notification Description This check box, if selected, allows users to perform scheduling from Munis applications. This check box hides or displays the Execute This Report list, which is in all Scheduler-enabled programs. The default value for this setting is not selected. This is a global setting that takes effect immediately when changed. This box specifies the run start time for scheduled jobs. The start time should be a time when there is little or no workload from active users, as well as outside the daily maintenance schedule. This setting takes effect immediately when changed. This box specifies the amount of time between initiating a job using the Background (Now) option from a Munis program and the time that the job starts running. Type the delay time in the hh:mm:ss format. This setting creates a brief delay between time of entry and time of execution to allow the engine to queue the job ahead of its scheduled run time. Without this delay, background jobs may appear to run late. This setting takes effect immediately when changed. This check box, if selected, causes Munis Scheduler to distribute an notification when a job starts. This check box, if selected, causes Munis Scheduler to distribute an notification when a job completes. This check box, if selected, causes Munis Scheduler to distribute an notification when a job expires. Using Munis Scheduler, Version 10.5 Page 17

18 Report Scheduling For Scheduler-enabled programs, use the Execute This Report list to manage the Munis Scheduler process. The Execute This Report list has three options: Now Runs the program immediately without using Munis Scheduler. If you select this option, use the Preview, PDF, Print, or Text File buttons in the Output group of the ribbon to create the report. In Background (Now) Runs the job now using Scheduler. This allows the program to be run a single time, but with all of the benefits of Scheduler, including a log of events and notification of actions. At a Scheduled Time Sets up a scheduled occurrence or recurrence of a job to be run in the future. When you select In Background (Now) or At a Scheduled Time, the program displays the Munis Scheduler dialog box. Use this box to set the parameters for the specific report. Using Munis Scheduler, Version 10.5 Page 18

19 In Background (Now) The In Background (Now) option establishes job action notifications (for example, when the job begins or ends) and defines the output options for the scheduled report. To setup processing notifications, click Notify. The program displays the Notifications screen. Complete this screen to define the notification events and recipients. Field Event Description This list indicates when notifications are sent: When Job Starts - Notifications are sent when the job starts. When Job Completes - Notifications are sent when the job Using Munis Scheduler, Version 10.5 Page 19

20 Field Recipient: Users Recipient: Roles Recipient: Description completes. If Job Completes w/error - Notifications are sent if the job completes and errors occur during processing. If Job Expires - Notifications are sent when the recurring job expires. If Job is Deleted - Notifications are sent when the job is deleted. When Job Completes, Include Document Link(s) - Notifications are sent when the job is complete and the notification includes a link to the document that was created. Note: The When Job Completes, Include Document Link(s) option is only available if your organization uses Tyler Content Manager for Munis for document storage and you have the appropriate permissions. You must have the TylerCM Single Document Viewer installed to view documents from notifications. This box indicates the user IDs of the people receiving the notification. Type user IDs in the box, using a semi-colon to distinguish between the different users. Click the help button to access a list of all eligible recipients. This box indicates the role IDs of the people receiving the notification. Type role IDs in the box, using a semi-colon to distinguish between the different roles. Click the help button to access a list of all eligible roles. When you select a role ID, a notification is sent to all users assigned to the selected role. This box indicates the addresses of the people receiving the notification. Type the addresses in the box, using a semi-colon to distinguish between the addresses. Click the help button to select addresses. Using Munis Scheduler, Version 10.5 Page 20

21 When you click Output, the program displays the Output dialog box, where you can define the print or save options for the report. To save the report to a file, select Save as the output type and select a directory and file name for the output file. Field Output Type Munis Printer Save Printer Name Save In File Name Description When you select this option, the program prints the job. If you print the job, you must choose a printer. When you select this option, the program spools the job to the Saved Reports program or Tyler Content Manager for Munis according to the option you select from the Save In list. This box identifies the printer to which the job is sent. The default setting is to print the job to the Munis default printer, but you can change this. You can type the name of the printer in the box, or click the help button to select a printer. Click Properties to view information about the printer. This box is only available when you select the Munis Printer output type. This list indicates where the file is stored: Munis Spool Directory TylerCM Archive Both Munis Spool Directory and TylerCM Archive This list is only available if your organization uses Tyler Content Manager for Munis and you select the File output type. This is the name of the file that you are creating. The default naming convention for the file name is the 8-character program Using Munis Scheduler, Version 10.5 Page 21

22 Field Save as Type Include Link to Tyler CM Document in Scheduler Notifications Report Title Output Style Presentation/Standard Options Landscape Enable Hyperlinks if Present Copies Description name, followed by a 4-digit extension. When the report is scheduled for a future time, the 4-digit extension is not assigned until the job is processed. This box is available when you select the File output type. This list indicates the type of file to create. You can create a plain text (.txt) or PDF (.pdf) file. This list is only available when you select the File output type. You can only create a PDF file if the Output to PDF check box in Munis System Roles is selected for at least one role assigned to your user name. When you select this check box, a link to the document is included in notifications. This check box is only available when you select the Save output option, and select TylerCM Archive or Both Munis Spool Directory and TylerCM Archive on the Save In list. Your organization must use Tyler Content Manager and the TylerCM Single Document Viewer must be installed to include document links in notifications. You must also have the appropriate permissions. This is the title of the report that is being created. This is the format in which the report displays. These options are selected automatically, depending on your other output selections and you cannot change this. The Presentation option is only selected if you are saving the report as a PDF. Note: If your organization uses the Genero Report Writer with the Genero Desktop Client (GDC), the Presentation option is available. When you select this check box, the program prints the report or file in landscape format. This check box is only available when you select the Munis Printer output type. This check box indicates if hyperlinks to records are included in the report. This check box is only available if you are saving the report as a PDF. This box indicates the number of copies to be printed. Type the number of copies in the box, or click the up or down arrows until the appropriate number is in the box. This box is only available when you select the Munis Printer output type. Once all options are defined, the Scheduler screen displays the selections. When you click OK, the program displays a confirmation message. Click OK to confirm the scheduled activity. Using Munis Scheduler, Version 10.5 Page 22

23 The program returns to the program screen and displays a Scheduler notice in the status bar. At a Scheduled Time The At a Scheduled Time option establishes job action notifications (for example, when the job begins or ends), defines the output options for the scheduled report, and establishes a recurrence schedule for the report. Using Munis Scheduler, Version 10.5 Page 23

24 The Recur option displays the Scheduler Recurrence screen. Use this screen to define the recurrence pattern, time, and range for a job; you can also remove a recurrence using this screen. Field Description Recurrence Pattern Daily/Weekly/Monthly/Yearly These options allow you to define a recurrent pattern. Select an option to complete the job on a daily, weekly, monthly, or yearly basis. Daily - The job runs every n number of days or every weekday. Weekly - The job runs every n number of weeks on a specific day of the week. Monthly The job runs on a specific day of the month, such as the 21st, every n number of months, or on a specific day of a certain week every times the number of months, such as the third Thursday of every month. Yearly - The job runs on a specific day of a specific month or on a specific day of a specific week in a specific month. Time Run At Note: If a job is scheduled to run more than once, each recurrence is considered a part of the same job, therefore, given the same job number. This box indicates the time of day when the job is scheduled to be completed. Enter the time in standard format and the program converts it to military time format. Note: Use this field to run jobs at a time when server traffic is at a minimum. Using Munis Scheduler, Version 10.5 Page 24

25 Field Range of Recurrence Start No End Date/End After X Occurrences/End By Description This box determines the date when the job should be completed for the first time. This list indicates when the job should expire: No End Date End After X Occurrences End By Date Notifications If notifications are established for a job, the program distributes messages for job events. For example, when a job starts, the program sends a started message to the addresses included in the notification setup. The completed message includes the name of the printer or name of the file created. Using Munis Scheduler, Version 10.5 Page 25

26 Appendix A Log Events The log name is generated using the engine program name (mescheng) concatenated with the engine number and the database name, ending with a suffix of.log. The engine can be configured to start a new log each time it starts. If the Auto-Increment Log Name check box is selected, the file name includes a three-digit file counter, which increases by one each time the engine is initialized. The current log file name is displayed in the Setup tab. The following table provides a summary of logged event messages. Event Maintenance shutdown Maintenance sleep Engine mode change Engine mode change Setup tab-click Setup tab timeout Setup tab timeout Setup update Setup update On error On error Log tab-click Log tab timeout Job creation Job expiration Job started Job deleted Job completed Job completed History purge (on idle) Shutdown Message Cannot shutdown for scheduled maintenance - <nn> jobs appear to be running. Cannot sleep for scheduled maintenance - <nn> jobs appear to be running. Mode change failed: Could not retrieve current engine mode. Mode change failed: <status> to <status> by <userid ENGINE>. Engine paused for Setup. View-Setup, inactivity timeout hit. Edit-Setup, inactivity timeout hit. ERROR saving setup. Updated engine setup. Any error message normally displayed using spsysrec. Error info and program context reported by error handling function. Engine paused for Log. Logs inactivity timeout hit. Added job <jobkey> to queue on <mm/dd/yyyy> at <hh:mm:ss>. Expiring job <jobkey> on <mm/dd/yyyy> at <hh:mm:ss>. Launching job <jobkey> on <mm/dd/yyyy> at <hh:mm:ss>. Updated job <jobkey> to deleted on <mm/dd/yyyy> at <hh:mm:ss>. Job <jobkey> completed with error(s) on <mm/dd/yyyy> at <hh:mm:ss>. Job <jobkey> completed successfully on <mm/dd/yyyy> at <hh:mm:ss>. Purged <nn> history records [and <nn> job records with no remaining history] older than <mm/dd/yyyy>. Engine shutdown on <mm/dd/yyyy> at <hh:mm:ss>. Using Munis Scheduler, Version 10.5 Page 26