Difference between revisions of "Taskman Recurring Tasks"

From VistApedia
Jump to: navigation, search
(Recurring Tasks (dependent on VistA System Manager Policies)
Line 22: Line 22:
 
* [[OPTION XUDEV RES-CLEAR|XUDEV RES-CLEAR]] --> Clear resources (use on startup)
 
* [[OPTION XUDEV RES-CLEAR|XUDEV RES-CLEAR]] --> Clear resources (use on startup)
  
=== Recurring Tasks (dependent on [[VistA System Manager Policies]] ===
+
=== Recurring Tasks (dependent on [[VistA System Manager Policies]]) ===
 +
* [[OPTION DG G&L RECALCULATION AUTO|DG G&L RECALCULATION AUTO]] --> Calculate Gains and Losses for the previous day. Run after midnight to get the previous day's data.
 
* [[OPTION DGPF BACKGROUND PROCESSING|DGPF BACKGROUND PROCESSING]] --> For PRF: To trigger Patient Record Flags reviews.
 
* [[OPTION DGPF BACKGROUND PROCESSING|DGPF BACKGROUND PROCESSING]] --> For PRF: To trigger Patient Record Flags reviews.
 
* [[OPTION DMSQ PROJECT|DMSQ PROJECT]] --> (only if running SQLI) (for e.g. Fileman Projection; to regenerate projection files)
 
* [[OPTION DMSQ PROJECT|DMSQ PROJECT]] --> (only if running SQLI) (for e.g. Fileman Projection; to regenerate projection files)

Revision as of 03:36, 9 November 2011

A proper VISTA installation will have a bunch of recurring tasks (like linux cron jobs or mac launchd jobs) that ensure that the database remains clean and periodic stuff is completed. For example, the TIU recurring task makes sure that everything is signed; otherwise it will send a notification. Another example: Scratch globals for storing temporary data can get very large. A daily task (XQ XUTL $J NODES) cleans them up.

Tasks running by default in WV but need to be removed

Cache Only Jobs

(Use if you are running WV on Cache; remove if you are running GT.M)

GT.M Only Jobs

  • Important XU PROC CNT CLUP --> (Task number cleaner) Need if you use GT.M. Run every hour.

Start-up Jobs

Recurring Tasks (dependent on VistA System Manager Policies)