EMU Edulog Maintenance Utility

1
EMUEdulog Maintenance Utility
2
EMU

• EMU is the edulog.nt version of System
  Maintenance
• Contains some utilities youre used to seeing.
• Contains some new ones.

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

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

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.

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.

7
Batch A Contains 3 Utilities

• Utilities
• 1
• 2
• 3
• 4
• 5
• 6
• 7

• Batches
• A 4
• 1
• 3

8
The Utilities Will Execute in Order 4, 1, 3

• Utilities
• 1
• 2
• 3
• 4
• 5
• 6
• 7

• Batches
• A 4
• 1
• 3

9
Batch B Also Contains 1 Utility

• Utilities
• 1
• 2
• 3
• 4
• 5
• 6
• 7

• Batches
• A 4
• 1
• 3
• B 1

10
EMU Related Programs

• EMUGUI
• EMUSRV
• KICKER

11
EMU Interface

• The program that creates and runs the EMU window
  is called EMUGUI.

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.

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.

14
Using EMU
15
EMUGUI

• Batch status
• Queued
• Running
• Done
• Error

16
EMUGUI

• Delete
• Old batch-status entries should be removed
  regularly.
• Highlight the entries to be deleted and click
  delete.

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.

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.

19
Creating a Batch
20
Click Batches Button

• Perform all batch operations
• Create
• Run
• Edit
• Delete
• Schedule
• Configure utilities

21
Select Create to make a new batch.

• This dialog box shows a list of available batches.

22
Available Utilities

• Listed on left
• If you need a utility thats not listed here,
  call your project leader.

23
Select Utilities for Batch

• Use the right-facing green arrow to send the
  utility over and build your batch

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.

25
Example Creating a Batch

• Create a batch for Deleteroutes.
• Call it Delete Empty Routes.
• Run it.
• Watch the batch status display.

26
Example Creating a Batch

• Create a batch containing Badstp and badstu.
• Call it Badstuff.
• Run it.
• Watch the batch status display.

27
Editing a Batch
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.

29
Removing Utilities from a Batch

• You can remove items from a batch by selecting
  them and clicking the arrow pointing to the left.
  

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!
31
EMUGUI

• Delete all history entries by highlighting them
  and pressing the Delete button
• View some of the badstp and badstu error and
  audit files.
• Note that you can print them from FilePrint.
  (opens in notepad)
• You can also open these files in a word processor.

32
Utility Configurations
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.

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.

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

36
Configuring A Utility

• Selecting New allows you to create a
  configuration.
• Once created, it will be added to the list for
  future use.

37
Configuring A Utility

• To use an existing configuration, simply select
  it and click OK.

38
Configuring A Utility

• To change or review an existing configuration,
  select it and click Edit.

39
Example Configure ADSCAN
40
Example Configuring Utilities

• Create a Batch Student Matching
• Utility 1 ADDUPD
• Responses
• Permanently update? Yes
• Logical path STAADDUPD.TXT
• Configuration Name ADDUPD Permanent
• Utility 2 PSTSTU
• Utility 3 ADSCAN
• Responses
• Configuration Name ADSCAN ALL

41
Your Batches
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.

43
11 Prepared Batches

• 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.

44
11 Prepared Batches

• 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

45
11 Prepared Batches

• 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

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.

47
11 Prepared Batches

• 10. Poststu modifies student mapzone or suffix
  for 11.
• 11. Student Addr Match locates student in
  geocode

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.

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

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

51
Running EMU Batches
52
EMU Rules

• All users should be out of other edulog programs
  before you start maintenance.
• No one will be able to get into edulog.nt while
  maintenance is running.

53
Queued Batches

• A batch will queue - rather than run immediately
  when EMU thinks the data files the utility
  needs are in use.

54
Reasons Batches Queue

• The data files are actually in use because
  someone has an edulog program open.
• Fix Ask the user to close out of edulog.

55
Reasons Batches Queue

• A user has closed or been closed out of edulog in
  a manner that did not allow programs to close
  properly.
• This can leave processes running and files in
  existence that make it appear to EMU that a user
  is still active.
• Fix close processes and remove files
• Note you may have to run elterminator.bat to
  stop some processes that have hung out there.

56
Fixing Batches That Queue When No User Is Logged
in

• Close Processes
• Open Task Manager.
• Open Processes tab
• Close instances of eltransservice and epa

57
Fixing Batches That Queue When No User Is Logged
in

• 2. Delete Files
• \elt\server\dyn\.lck
• \elt\server\geo\.taf
• \elt\exe\server\EP-InUse.dat

58
Scheduling Batches
59
Scheduling A Batch

• You can
• Schedule a batch to run at a certain time,
  perhaps at night when no one is working.
• Schedule a batch to run on a regular schedule.

60
Scheduled Batches

• Execution controlled by EMUSRV
• Must be running for scheduled utilities to run.
• If emusrv is shut down, missed scheduled
  maintenance will run when emusrv starts again.
  That usually occurs when you restart EMUGUI (the
  EMU program).

61
Scheduling A Batch

• If you have an automatic backup scheduled on your
  server, make sure you dont schedule maintenance
  to occur at the same time.
• The files being accessed by maintenance will not
  be available for backup and vice versa.

62
Scheduling A Batch

• From the Batch Work Dialog box,
• Select a batch
• Click Schedule

63
Scheduling A Batch

• Select a repetition period
• Only Once
• Every x hours/days
• Same day of every week
• Same day of every month
• Same time every day
• Up to four selected days in the month, one per
  week

64
Scheduling A Batch

• Enter a Start Date
• Date field format mm/dd/yyyy
• Use leading zeroes in single digit months and days

65
Scheduling A Batch

• Enter a start time, no matter which option you
  choose.
• Use leading zeroes in single digit hours and
  minutes

66
Scheduling A Batch

• If you are scheduling a process to run weekly or
  monthly, make sure the starting date falls on the
  day of the week you want the batch to run.

67
Scheduling A Batch

• Choose OK when finished. Choose Exit to return
  to the launch pad. The status of the scheduled
  process appears as Queued in the list box.

68
Canceling a Scheduled Batch

• You can cancel a scheduled batch process by
  selecting it from the batch status list and
  choosing delete.

69
Example Scheduling a Batch

• Schedule your Delete Empty Routes batch to run
  three minutes from the time shown on your
  computer.
• Repeat Only once
• Date today
• Time 3 minutes from your computer clock

Contd
70
Example Scheduling a Batch (contd)

• Close scheduling
• Display the opening EMU screen.
• At the bottom of the list of batches, you should
  see Delete Routes. It should be queued.
• Wait for it to run.

71
EMU - Edulog Maintenance Utility

• This concludes the training session.
• Please do one of the following
• Go Back and review areas that interest you.
• Try the exercises.
• Exit the presentation.