System Lock File Requirements

Lock files are used in Elliott to prevent users from entering transactions when other users are posting, to prevent users from entering transactions when invoices are printed, or to prevent multiple people from printing purchase orders at the same time. For the lock file to work, it must meet the following conditions:

It should be an indexed file with the lock mode set to manual:

       SELECT LOCK-FILE
          ASSIGN TO RANDOM SYLCKFIL-PATH
          ORGANIZATION IS INDEXED
          ACCESS MODE IS DYNAMIC
          LOCK MODE IS MANUAL
          RECORD KEY IS LOCK-KEY
          FILE STATUS IS LOCK-FILE-STATUS.

The declarative should be coded like the following example so the application code can intercept a lock condition and give the user the appropriate error message:

       LOCK-FILE-ERROR SECTION.
          USE AFTER STANDARD ERROR PROCEDURE ON
              LOCK-FILE.

Notice that there is no error procedure.

To lock the file exclusively, the file should be opened I-O with lock. This is the same as using LOCK MODE IS EXCLUSIVE in the Select statement.

       OPEN-LOCK-FILE-WITH-LOCK.

          PERFORM GET-PATH.
          MOVE PASSING-DATA-PATH TO SYLCKFIL-PATH.
          OPEN I-O LOCK-FILE WITH LOCK.

The file naming convention must be ??LCK??? and the length of the record must be 24 bytes for the file handler to recognize that a lock file is being processed.

CLS

Developer Documentations

  1. Received Code 9999 with Web Services Call
  2. Received Return Status Code 3 When Using Elilogin Login Method
  3. Elliott Web Service Requirements
  4. Elliott eStore Checklist
  5. LN API
  6. FN API
  7. RN API
  8. IN and DF API Change (V9.0)
  9. FA API Changes (V9.0)
  10. VA API Changes (V9.0)
  11. CartService
  12. EliarachService
  13. ElicshtxService
  14. EliattrbService
  15. ElisyscdService
  16. EliNoteService
  17. El2rstimService
  18. EliOrderService
  19. ItemInquiry
  20. EliitmiqService
  21. EliShiptoService
  22. El2getfrService
  23. Steps Required to Test ReportWriter in V8.2
  24. Installation of ElliottService, NETcellent’s Web Services for Elliott
  25. ResellerFinder
  26. EliaptrxService
  27. VendorInquiry
  28. EliloginService
  29. ElislsmnService
  30. EliserhsService
  31. EliatpobService
  32. ElievprcService
  33. ElihdtrxService
  34. ElicuswlService
  35. QueryTurnaround
  36. InvoiceInquiry
  37. ElicustmService
  38. EligetcdService
  39. OrderInquiry
  40. EliordiqService
  41. EliecontService
  42. EliautdpService
  43. El2CrCrdService
  44. Log-Timer / ElliottTimer.Ini Support
  45. Alpha Document Number Support (V8.5/V9.0)
  46. ElliottService System.TypeInitializationException
  47. Feature - Printing API to Dynamically Set Number of Copies
  48. The Values and Meanings of Distribution Types - ARDISFIL, APDISFIL, IMDISFIL, BMDISFIL
  49. DD API Changes (V9.0)
  50. PA API (8.5)
  51. Validate License API
  52. AP API
  53. TP API: Temporary Path
  54. Data Structures for Report Desk Defaults and Enforcements
  55. COBOL to VB Interface Programs
  56. IN API: Option to Support Files and Folders Validation
  57. FF API: File Functions
  58. ID API
  59. LK: Links API
  60. FFLNearYou
  61. Report Desk Developing and Debugging
  62. Developing a New Elliott V8.6 Report Desk User Defined Report (UDR)
  63. CustomerInquiry
  64. Elliott API (JSON Web Service)
  65. Animating COBOL Code in Elliott V8.5
  66. Preliminary Programming Changes for Elliott 8.6
  67. CV API
  68. System Lock File Requirements
  69. How to Write Test Codes for C# ESS Projects
  70. Solving the Inability to Debug Elliott on a New Server
  71. Report Desk: Developing Custom Reports
  72. Report Desk Tables
  73. Report Desk Database Delivery Strategy

Feedback and Knowledge Base