added LSL2 stored procedures

LSL2/STPROC/SCRAPE_SERVICES_DEV.txt

@@ -0,0 +1,107 @@
+Compile function Scrape_Services_DEV(@Service, @Params)
+/***********************************************************************************************************************
+
+    Name        :   Engineering_Services
+
+    Description :   Handler program for all Disposition services.
+
+    Notes       :   Application errors should be logged using the Error Services module. There are a few methodological
+                    assumptions built into way errors are managed which are important to understand in order to properly
+                    work with Error Services:
+
+                    - The term 'top' refers to the originating procedure of a call stack and the term 'bottom' refers to
+                      the last routine (or the current routine) within a call stack. Within the OpenInsight Debugger
+                      this will appear backwards since the originating procedure always appears at the bottom of the
+                      list and the current routine appears at the top of the list. We are using this orientation because
+                      it is common to refer to the process of calling other procedures as 'drilling down'.
+
+                    - The reason for defining the orientation of the call stack is because Error_Services allows for
+                      multiple error conditions to be appended to an original error. In most cases this will happen when
+                      a procedure at the bottom of the stack generates an error condition and then returns to its
+                      calling procedure. This higher level procedure can optionally add more information relevant to
+                      itself. This continues as the call stack 'bubbles' its way back to the top to where the
+                      originating procedure is waiting.
+
+                    - Native OpenInsight commands that handle errors (e.g., Set_Status, Set_FSError, Set_EventStatus)
+                      preserve their error state until explicitly cleared. This can hinder the normal execution of code
+                      since subsequent procedures (usually SSPs) will fail if a pre-existing error condition exists.
+                      Our philosophy is that error conditions should automatically be cleared before a new procedure
+                      is executed to avoid this problem. However, the nature of Basic+ does not make this easy to
+                      automate for any given stored procedure. Therefore, if a stored procedure wants to conform to our
+                      philosophy then it should include a call into the 'Clear' service request at the top of the
+                      program. Alternatively this can be done through a common insert (see SERVICE_SETUP for example.)
+
+                    - Service modules will use the SERVICE_SETUP insert and therefore automatically clear out any
+                      error conditions that were set before.
+
+    Parameters  :
+        Service         [in] -- Name of the service being requested
+        Param1-10   [in/out] -- Additional request parameter holders
+        Response       [out] -- Response to be sent back to the Controller (MCP) or requesting procedure
+
+    Metadata    :
+
+    History     :   (Date, Initials, Notes)
+        08/24/20    djs     Original programmer.
+														
+
+***********************************************************************************************************************/
+#pragma precomp SRP_PreCompiler
+
+$insert SERVICE_SETUP
+$insert APP_INSERTS
+$insert ENVIRON_CONSTANTS
+
+Declare subroutine Copy_Backlog_Records_To_SQL, Copy_Backlog_WO_MAT_Records_To_SQL, Copy_Backlog_WO_LOG_Records_To_SQL
+Declare subroutine Set_Env
+Declare function   Database_Services
+
+// Set custom debug intercept routine
+Set_Env(ENV_DEBUGGER_INTERCEPT_PROC$, 'TEST_DANIEL3', 1)
+Set_Env(ENV_DEBUGGER_ENABLED$, 2, 1)
+
+GoToService else
+    Error_Services('Set', Service : ' is not a valid service request within the ' : ServiceModule : ' services module.')
+end
+
+// Restore debugger
+Set_Env(ENV_DEBUGGER_ENABLED$, 1, 1)
+
+Return Response or ""
+
+//-----------------------------------------------------------------------------
+// SERVICES
+//-----------------------------------------------------------------------------
+
+Service CopyRecordsToScrapeDB()
+    
+    hSysLists   = Database_Services('GetTableHandle', 'SYSLISTS')
+    Lock hSysLists, ServiceKeyID then
+        Copy_Backlog_Records_To_SQL()
+        Unlock hSysLists, ServiceKeyID else Null    
+    end
+    
+End Service
+
+
+Service CopyWO_MATRecordsToScrapeDB()
+    
+    hSysLists   = Database_Services('GetTableHandle', 'SYSLISTS')
+    Lock hSysLists, ServiceKeyID then
+        Copy_Backlog_WO_MAT_Records_To_SQL()
+        Unlock hSysLists, ServiceKeyID else Null    
+    end
+    
+end service
+
+
+Service CopyWO_LOGRecordsToScrapeDB()
+    
+    hSysLists   = Database_Services('GetTableHandle', 'SYSLISTS')
+    Lock hSysLists, ServiceKeyID then
+        Copy_Backlog_WO_LOG_Records_To_SQL()
+        Unlock hSysLists, ServiceKeyID else Null    
+    end
+    
+end service
+