1 / 71

EMU Edulog Maintenance Utility

EMU Edulog Maintenance Utility. EMU. EMU is the edulog.nt version of System Maintenance Contains some utilities you’re used to seeing. Contains some new ones. Improvements Over PTS-III. History of maintenance activity Access to audit and error files within program.

omer
Download Presentation

EMU Edulog Maintenance Utility

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMUEdulog Maintenance Utility EMU - 2004

  2. EMU • EMU is the edulog.nt version of System Maintenance • Contains some utilities you’re used to seeing. • Contains some new ones. EMU - 2004

  3. Improvements Over PTS-III • History of maintenance activity • Access to audit and error files within program. • Adscan.Err, upstu.aud, etc. • Saved configurations • Store responses required to run utilities EMU - 2004

  4. Improvements over PTS-III • Batches • Run several utilities by starting one batch • Utility queuing • Initiate utilities while another is running • Utility scheduling • Set basic utilities to run same time every night EMU - 2004

  5. Utilities and Batches • Utility: Program that performs one or a set of closely related data maintenance functions. • Batch: A named, saved selection of one or more utilities listed in the order in which they need to run. We run batches, batches run utilities. EMU - 2004

  6. Utilities and Batches • A batch can contain one or more utilities. • A utility can be used in more than one batch. • Utilities are executed in the order in which they are placed in the batch. EMU - 2004

  7. Utilities 1 2 3 4 5 6 7 Batches A 4 1 3 Batch A Contains 3 Utilities EMU - 2004

  8. Utilities 1 2 3 4 5 6 7 Batches A 4 1 3 The Utilities Will Execute in Order: 4, 1, 3 EMU - 2004

  9. Utilities 1 2 3 4 5 6 7 Batches A 4 1 3 B 1 Batch B Also Contains 1 Utility EMU - 2004

  10. EMU Related Programs • EMUGUI • EMUSRV • KICKER EMU - 2004

  11. EMU Interface • The program that creates and runs the EMU window is called EMUGUI. EMU - 2004

  12. EMUSERV • Background program that starts when you start EMU from menu. • Continues to run until computer is shut down. • Must be running for utilities to run. EMU - 2004

  13. Kicker.Exe • When EMU batches are executed, a program called kicker.exe is started • displays a DOS window • may show the current process as it runs in EMU. • depending on your setup, you may or may not see the kicker window. EMU - 2004

  14. Using EMU EMU - 2004

  15. EMUGUI • Batch status • Queued • Running • Done • Error EMU - 2004

  16. EMUGUI • Delete • Old batch-status entries should be removed regularly. • Highlight the entries to be deleted and click “delete”. EMU - 2004

  17. Audit and Error Reports • As in TIMS for DOS, some utilities create useful error and audit files. • They can be viewed and printed from within EMU. EMU - 2004

  18. Audit and Error Reports • If you wish, you can browse to their location with Windows Explorer and open them with the word processor of your choice. • They are usually found in Elt\Exe\Emu\Output directory. EMU - 2004

  19. Creating a Batch EMU - 2004

  20. Click “Batches” Button • Perform all batch operations • Create • Run • Edit • Delete • Schedule • Configure utilities EMU - 2004

  21. Select “Create” to make a new batch. • This dialog box shows a list of available batches. EMU - 2004

  22. Available Utilities • Listed on left • If you need a utility that’s not listed here, call your project leader. EMU - 2004

  23. Select Utilities for Batch • Use the right-facing green arrow to send the utility over and build your batch EMU - 2004

  24. Name the Batch • If this is a new batch, type a unique name. • Try to make it descriptive of what the batch does. • Click OK to save. EMU - 2004

  25. Example: Creating a Batch • Create a batch for Deleteroutes. • Call it Delete Empty Routes. • Run it. • Watch the batch status display. EMU - 2004

  26. Example: Creating a Batch • Create a batch containing Badstp and badstu. • Call it Badstuff. • Run it. • Watch the batch status display. EMU - 2004

  27. Editing a Batch EMU - 2004

  28. Adding Utilities to an Existing Batch • You can add additional utilities to the end of the Batch Operations list as desired. • However, if you wish to place a new utility at any point within the existing list, you must remove the utilities below the desired location of the added utility and reinsert them after the addition. EMU - 2004

  29. Removing Utilities from a Batch • You can remove items from a batch by selecting them and clicking the arrow pointing to the left. EMU - 2004

  30. Example: Editing a Batch • Edit the Badstuff batch • Place kilstp in the first position. • Place badstp in the second position. • Place badstu in third position. • Can you rename the batch? No – you cannot! EMU - 2004

  31. EMUGUI • Delete all history entries by highlighting them and pressing the Delete button • View some of the badstp and badstuerror and audit files. • Note that you can print them from File:Print. (opens in notepad) • You can also open these files in a word processor. EMU - 2004

  32. Utility Configurations EMU - 2004

  33. Utility Configuration • Some utilities require the user to select from among options. • A set of option selections (a configuration) can be saved for future use. • Different circumstances may require the creation of multiple configurations for a single utility. EMU - 2004

  34. Configuring A Utility • When you select a utility that requires user input, the following dialog box appears. • It lists any configurations already defined for the utility. EMU - 2004

  35. Configuring Utilities • When you select a utility requiring configuration, you may • Use an existing configuration • Create a new one • Edit an existing one and use it EMU - 2004

  36. Configuring A Utility • Selecting “New” allows you to create a configuration. • Once created, it will be added to the list for future use. EMU - 2004

  37. Configuring A Utility • To use an existing configuration, simply select it and click “OK”. EMU - 2004

  38. Configuring A Utility • To change or review an existing configuration, select it and click “Edit”. EMU - 2004

  39. Example: Configure ADSCAN EMU - 2004

  40. Example: Configuring Utilities • Create a Batch: Student Matching • Utility 1: ADDUPD • Responses • Permanently update? Yes • Logical path: STA:ADDUPD.TXT • Configuration Name: ADDUPD Permanent • Utility 2: PSTSTU • Utility 3: ADSCAN • Responses • Configuration Name: ADSCAN ALL EMU - 2004

  41. Your Batches EMU - 2004

  42. Your Batches • The TIMS project leaders have created and given you a set of 11 batches which cover all routine maintenance. • You will rarely need to create batches. • Those you will need to create will usually be fairly simple. EMU - 2004

  43. 01. Rebuild all keys - maintains data file integrity 02A. Geocode changes - maintains the integrity of the Geocode files and updates secondary files pertaining to routing, stop locations, and student assignments. After 02.(A)Geocode Changes is run, review the STPSCN.ERR report. Treat this report like an unlocated student list and attempt to locate the stops. Ignore the 'Ambiguous corners skipped' error messages. After locating stops, continue rerunning this batch until the STPSCN.ERR report is clear of un-matched stops. 11 Prepared Batches EMU - 2004

  44. 02B. Geocode changes - This continues updating geocode files from #02(A) and rebuilds the Autostreet layer. When this finishes running, review BADSTP.ERR and attempt to relocate any stops found in the report. Rerun this batch after fixing stop locations. 03. Mileage and slack - updates these values for reporting 11 Prepared Batches EMU - 2004

  45. 04. Student distances - updates values dependent on student locations 05. Dumpall - wipes out old report tables and transfers all data to new report tables 06. Upload student data – transfers students from SIMS to TIMS files 11 Prepared Batches EMU - 2004

  46. 11 Prepared Batches • 07. Set deletion flags – flags for deletion students not updated by 06. • 08. Student purge – removes records flagged by 07. • 09. Address update – modifies student street names for 11. EMU - 2004

  47. 11 Prepared Batches • 10. Poststu – modifies student mapzone or suffix for 11. • 11. Student Addr Match – locates student in geocode EMU - 2004

  48. When to Run the 11 Prepared Batches • Batches fall into two groups in terms of frequency of use • Those you run daily • Those you run on special occasions. EMU - 2004

  49. Run These Daily and in This Order • 01. Rebuild all keys • 02A. Geocode changes • 02B. Geocode changes • 03. Mileage and slack • 04. Student distances (not on day of upstu) • 05. Dumpall EMU - 2004

  50. Run During Student Upload • 06. Upload student data • 07. Set deletion flags • 08. Student purge • 09. Address update • 10. Poststu • 11. Student Addr Match EMU - 2004

More Related