PSQL Database Names And DDF Convention

Current & Future Database Naming Standards

Listed below is the current and future naming convention for PSQL Control Center database names:
  • ELLIOTTDATA           V7.X DDF
  • ELIDATA                    V8.x DDF
  • ELI90DATA                V9.0 & after DDF

Standards for V8.3

Beginning with Elliott V8.3, it is necessary to associate the database names in PSQL Control Center to the Company data directories.  They will default as follows:

  • ELIROOT               for tables in the root directory, this is needed for the new report writer in 8.3.
  • DDF: <ElliottRoot>\Bin\DDFROOT
  • Data: <ElliottRoot>
  • ELIDATA                 for Company 01 tables
  • DDF: <ElliottRoot>\Bin\DDF40
  • Data: <ElliottRoot>\Data
  • ELIDATA02             for Company 02 tables
  • ELIDATA03             for Company 03 tables
  • etc.

These are the defaults.  However, if your database is customized and a separate set of DDF and database names are created.  Then you be override the standard naming assumption by Elliott in EL800.CFG file. For example, you may add a section as follows:

  • [DatabaseName]:
  • Server=TS4
  • Root=XXXROOT
  • Company01=XXXDATA
  • Company02=XXXDATA02
  • etc.

The Server entry is required for using new Report Writer.  It is used to construct the connection strings to the databases.

The Root and Companynn entries do not have to be present in EL800.CFG.  When they are not present, the default database names (ELIROOT and ELIDATA ...etc.) are assumed.

The main changes of Elliott 8.3 DDF is we added the ELIROOT convention to support the root directory database files in order for the new report writer to function.  In addition, Elliott 8.3 DDF add the required report writer tables in the ELIDATA database.  Another big area of changes, we now added various NSCTLFIL_9999 table definition so you can access each NSCTLFIL records with proper column definition.


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. PSQL Database Names And DDF Convention
  16. ElisyscdService
  17. EliNoteService
  18. El2rstimService
  19. EliOrderService
  20. ItemInquiry
  21. EliitmiqService
  22. EliShiptoService
  23. El2getfrService
  24. Steps Required to Test ReportWriter in V8.2
  25. Installation of ElliottService, NETcellent’s Web Services for Elliott
  26. ResellerFinder
  27. EliaptrxService
  28. VendorInquiry
  29. EliloginService
  30. ElislsmnService
  31. EliserhsService
  32. EliatpobService
  33. ElievprcService
  34. ElihdtrxService
  35. ElicuswlService
  36. QueryTurnaround
  37. InvoiceInquiry
  38. ElicustmService
  39. EligetcdService
  40. OrderInquiry
  41. EliordiqService
  42. EliecontService
  43. EliautdpService
  44. El2CrCrdService
  45. Log-Timer / ElliottTimer.Ini Support
  46. Alpha Document Number Support (V8.5/V9.0)
  47. ElliottService System.TypeInitializationException
  48. Feature - Printing API to Dynamically Set Number of Copies
  49. The Values and Meanings of Distribution Types - ARDISFIL, APDISFIL, IMDISFIL, BMDISFIL
  50. DD API Changes (V9.0)
  51. Developing a New Elliott V8.3 ReportWriter User Defined Report (UDR)
  52. PA API (V9.0)
  53. ReportWriter Thresholds
  54. ReportWriter Delivery Strategy
  55. Animating COBOL Code in Elliott V8.5
  56. Validate License API
  57. AP API
  58. TP API: Temporary Path
  59. The lessons we learned from upgrading web service 8.2 to 8.5 in eStore

Feedback and Knowledge Base