1 / 41

M2K Purges Periodic Task Requirements Repetitive Process Scheduling

M2K Purges Periodic Task Requirements Repetitive Process Scheduling. Mary Kay Werry Brightlight Solutions. Why are these topics important to you?. Reports & selections running longer? Forgetting to do things? Don’t want to have to do repetitive tasks?. Get rid of old data – PURGE

kobe
Download Presentation

M2K Purges Periodic Task Requirements Repetitive Process Scheduling

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. M2K Purges Periodic Task RequirementsRepetitive Process Scheduling Mary Kay Werry Brightlight Solutions

  2. Why are these topics important to you? Reports & selections running longer? Forgetting to do things? Don’t want to have to do repetitive tasks? Get rid of old data – PURGE Disc space is cheap, employee time is not Document what needs to be done – SCHEDULE Excel, calendars, email notifications Get it done automagically – DJS – delayed job stream BATCH.MASTER MASTER.AGENT NOTE: If doing critical jobs (purging, resize, etc) – use REMOTE DESKTOP or a similar product when accessing remotely. Avoid nasty disconnects.

  3. What & Why of Purges • Purges remove data from files based on: • Functional Constants • Purge Controls • User Requirements/responses • Purges improve system performance • Purges recover valuable disk space Approaching that 2gb ceiling on non-dynamic files?

  4. Who determines purges • Not IT / MIS • Users discussion involving • Functional areas • Senior Management • Government • Each site will be different • Work up your own plan

  5. When to run purges • System performance issues • Slow screen response • Slow report processing • Slow batch functions • Historical data no longer of value • Mass storage limited • Preventative Maintenance

  6. How Often should you purge • How much data is needed, really… • What is actually needed for analysis • What Government requires • Payroll • General Ledger • Go easy at first, start small • Safety Nets • M2K alternate files • Data warehouse options • SQL data options • See Marc Harbeson’s presentation Tues, Oct 21 4:40 pm • EUG: Using Microsoft SQL Server as a Data Warehouse and Report Engine with Manage 2000 • Account copy

  7. Purge Functions (purge_ye.xls) *1

  8. Purge Functions (purge_ye.xls) *2

  9. Purge Functions (purge_ye.xls) *3

  10. SOP.CONSTANTS ( Other tab)

  11. AP.CONSTANTS, screen 2

  12. AP.CONSTANTS, screen 1

  13. SFC.CONSTANTS, screen 4 Make sure this is set or you can lose information

  14. PURGE.CONTROLS

  15. SHOW.PURGE.CONTROLS

  16. Special purge notes: Considerations - do purges outside normal business hours - no activity - print required reports, do full backup before purging purge to tape rarely used - restoration possible, but not easily done (may require custom programming to access) SA.PURGE copies to SA.HIST SBA limitations WO.PURGE run WO.PURGE.SETUP first print (or not) work order data updates CLOSED.WO file (summarized) deletes detailed information from various files

  17. Sample Purge Document

  18. Monthly Maintenance

  19. Monthly Maintenance Notes If hesitant to do a full resize files: CHECKOVER finds critical oversized files FILE.STAT information about file sizing recommends modulo size RESIZE filename newmodulo Purges do not shrink files, Resize does If doing regularly scheduled purges, resize before purging as file will just fill up again. SC.CONSTANTS, screen 1, prompt xx Maximum Decrease % 0=no limit, > 0 will only decrease size by that %

  20. Year End Processes Notes Full backup before, Full backup after Make an online account copy (xxx.200?) first if you have the disc space. Easy to LOGTO and check changed data. (include or not in Upgrade) Common forgotten functions: RESET.VEN SET.USAGE.PERIODS SHOP.CALENDAR CALENDAR.BUILD

  21. Year End Processes (purge_ye.xls) *1

  22. Year End Processes (purge_ye.xls) *2

  23. Year End Processes (purge_ye.xls) *3

  24. Sample Year End Process List

  25. Scheduling Notes – DJS DJS – Delayed Job Stream releases user systems from running long, repetitive functions/reports set up function as DJS using FN.BUILD. Always, Sometimes, Never. Determine queue Dedicated user system to be set for running all the time.

  26. Scheduling Notes – Batch Master Batch Master – run in Phantom or Dedicated mode. Phantom updates _PH_ file with information about the process – use for troubleshooting (clear out the file weekly, if not daily) Unable to handle file transfers in Phantom mode – can be set in dedicated mode (requires dedicated session) Can be used to send jobs to DJS!

  27. Scheduling Repetitive Functions UT.SCHED / DJS (pre 7.1) SYS.BATCH

  28. BATCH.MASTER (6.2 – 7.1) BATCH.MASTER.QUEUES

  29. BATCH.MASTER (6.2 – 7.1) BATCH.MASTER.QUEUES screen 2

  30. BATCH.MASTER (6.2 – 7.1) BATCH.MASTER.CTL

  31. Scheduling Notes – Master Agent • Key observations about Master Agent • Can be set to AUTO run at startup • You can specify queue to run at startup • You might want to include ECA.AGENT, BTI.PHANTOM, etc… • One Master Agent can service multiple M2K accounts • For a more indepth Master Agent discussion, see the breakout session Wednesday, Oct 22 at 9:00 am

  32. MASTER.AGENT (7.2 +) [SYS.MA]

  33. MASTER.AGENT (7.2 +) [MA.SETUP] Use the documentation: MA.CONSTANTS MA.TASKS MA.QUEUES MA.FAX.DEFS MA.TEXT SESC.MAINT MA.CONSOLE

  34. MASTER.AGENT (7.2 +) MA.CONSTANTS MA.CONSTANTS Notice, Accounts to service Startup Queues Scheduler Name, (Auto=Y or N), Login, Error Notification Polling Frequency Admin User

  35. MASTER.AGENT (7.2 +) MA.TASKS Prompt 7 is “your label” for the prompts (When you do load prompts, it will use more cryptic prompts) – think ECA.BUILD • MA.TASKS • Used to define functions or programs that will be executed from the queue script. • Must exist in the Function Master • Load prompts button to pull in screen prompts • Account Specific

  36. MASTER.AGENT (7.2 +) • MA.QUEUES • Uses queue scripting language • Execute tasks already defined to use a schedule already defined. • Important Capabilities • Run tasks under a specific user name • Email/Fax commands • Set Facility • Define Form Name/Queue • Define screen prompt responses • Account Specific MA.QUEUES -A queue (the script) Queue   OnLoad     EventSchedule NIGHTLY.MNT READY  * When do I want this run (If on an schedule) Task MRP.CALC BM * Run what “Task” using “User BM”   OnPrompt * Here are the answers to all the “Prompts” (and MV prompts can just be entered multiple times)  -  Also, there is no requirement here for a particular order     Data DivisionCode=ALL     Data ChangeWhichField=END   OnCompleted * do this when you’re done.  (There is also “OnError”)     Email SHOOTS TEXT=MRP     Email JSCHARRER TEXT=MRP

  37. MASTER.AGENT (7.2 +) SESC.MAINT Line .03 says “EventSchedule” using this schedule: (Run Monday – Friday, at 1 AM) • SESC.MAINT • Used to create/maintain schedules (Delphi App) • Daily or Recurring (You can exclude dates) • Days of the week, Dates, Day of a fiscal period, etc… • Account Specific (This is what I have found. Bruce may disagree)

  38. MASTER.AGENT (7.2 +) MA.CONSOLE (While jobs are executing) • MA.CONSOLE • Used to monitor Master Agent processing • Shows what is executing or errors • You can load queues • You can go into tasks or queues from here • You can view the event schedule to see what is scheduled to run and when • If you are running ONE MA to service multiple accounts, you can see what is scheduled to run in all accounts.

  39. MASTER.AGENT (7.2 +) Another example - MA.TASKS Task COST.ROLLUP MHARBESON   OnPrompt     FormQueue GREENBAR option=HS Copies=1 * send printout to this printer, 1 copy     Data Items=ALL     Data EngStatusToBypass=B * mv prompt     Data EngStatusToBypass=D     Data EngStatusToBypass=I     Data EngStatusToBypass=O     Data EngStatusToBypass=P     Data EngStatusToBypass=END     Data Divisions=ALL     Data RollType=RB     Data EffectSelection=T     Data EffectDate=T     Data CostSetToRoll=2     Data CostSetToAudit=2     Data SaveWorkFile=N     Data UpdateIfIncomplete=Y     Data BypassType=RB     Data ChangeWhichField=END

  40. MASTER.AGENT (7.2 +) Another example - M2K screen

  41. Comments, Questions and Answers Supplemental documents: purge_ye.xls Email: mwerry@msn.com

More Related