Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Source |  Entry Points |  Interaction Calls |  FileMan Files Accessed Via FileMan Db Call
Print Page as PDF
Routine: ECXPURG

Package: DSS Extracts

Routine: ECXPURG


Information

ECXPURG ;BIR/CML-Driver for Purge of DSS Data from Local Extract & Holding Files ; 10/8/08 4:25pm

Source Information

Source file <ECXPURG.m>

Entry Points

Name Comments DBIA/ICR reference
ENDEL ;entry point from delete extract files option 144 CVW
EN ;entry point from the purge option
QUIT ;
QUE
PUR1 ; entry point for queued purge job of extract files
PUR2 ; entry point for queued purge job of IVP holding file (#728.113)
PUR3 ; entry point for queued purge job of UDP holding file (#728.904)
MAIL ;send mail message
MAIL1 ;send mail message
PUR4 ; entry point for queued purge job of VBECS holding file (#6002.03)

Interaction Calls

Name Line Occurrences
Function Call: WRITE
  • Prompt: @IOF,!!,"This option will allow you to delete an"
  • Line Location: ENDEL+1
Function Call: WRITE
  • Prompt: !,"individual or a range of DSS extracts files."
  • Line Location: ENDEL+2
Function Call: WRITE
  • Prompt: !!,"Care must be taken for several reasons:"
  • Line Location: ENDEL+3
Function Call: WRITE
  • Prompt: !!,"- You can delete ANY existing extract. This includes transmitted and non-"
  • Line Location: ENDEL+4
Function Call: WRITE
  • Prompt: !," transmitted extracts as well as extracts that did not run to completion"
  • Line Location: ENDEL+5
Function Call: WRITE
  • Prompt: !," due to errors or system problems."
  • Line Location: ENDEL+6
Function Call: WRITE
  • Prompt: !,"- Choosing a range of extracts could mean an excessively large number "
  • Line Location: ENDEL+7
Function Call: WRITE
  • Prompt: !," of records and be very CPU intensive. "
  • Line Location: ENDEL+8
Function Call: WRITE
  • Prompt: !," Please be sure to queue this deletion for off-hours and"
  • Line Location: ENDEL+9
Function Call: WRITE
  • Prompt: !," limit the number of extracts to be deleted per a single queued session."
  • Line Location: ENDEL+10
Function Call: WRITE
  • Prompt: !
  • Line Location: ENDEL+12
Function Call: WRITE
  • Prompt: !!
  • Line Location: ENDEL+13
Function Call: WRITE
  • Prompt: @IOF,!!,"This option will allow you to purge:"
  • Line Location: EN+1
Function Call: WRITE
  • Prompt: !,"1. data that resides in the ""holding files"" for the IVP and UDP extracts."
  • Line Location: EN+2
Function Call: WRITE
  • Prompt: !,"2. data that resides in the ""holding file"" for the VBECS extract"
  • Line Location: EN+3
Function Call: WRITE
  • Prompt: !!,"Care must be taken for several reasons:"
  • Line Location: EN+4
Function Call: WRITE
  • Prompt: !,"- The IVP, UDP and VBECS ""holding"" files are intermediate files that"
  • Line Location: EN+5
Function Call: WRITE
  • Prompt: !," are populated ""realtime"" by inpatient pharmacy and VBECS activity. "
  • Line Location: EN+6
Function Call: WRITE
  • Prompt: !," These files are then used to generate the IVP, UDP and VBECS extracts."
  • Line Location: EN+7
Function Call: WRITE
  • Prompt: !," NOTE: The VBECS files CANNOT be regenerated."
  • Line Location: EN+8
Function Call: WRITE
  • Prompt: !," Once it is purged for a date range, extracts can no longer be"
  • Line Location: EN+9
Function Call: WRITE
  • Prompt: !," generated for that time period."
  • Line Location: EN+10
Function Call: WRITE
  • Prompt: !
  • Line Location: EN+12
Function Call: WRITE
  • Prompt: $C(7),$C(7),!!?3,"<<This deletion should be queued to run during non-peak hours.>>",!
  • Line Location: QUE+0
Function Call: WRITE
  • Prompt: !,"Request queued as Task #",ZTSK,".",!
  • Line Location: QUE+2

FileMan Files Accessed Via FileMan Db Call

FileNo Call Tags
^VBEC(6002.03 - [#6002.03] Classic Fileman Calls
^ECX(728.113 - [#728.113] Classic Fileman Calls
^ECX(728.904 - [#728.904] Classic Fileman Calls
Info |  Source |  Entry Points |  Interaction Calls |  FileMan Files Accessed Via FileMan Db Call