Animating COBOL Code in Elliott V8.5


This documentation is intended for Netcellent or Netcellent's developers. It use Netcellent's own environment as an example of how to perform certain tasks. 

Our preferred method to test or debug a user's special custom mod is to make a working directory under folder like f:\nsi.pjt\85\cls. Then copy user's custom code to that directory, and then copy the contents of f:\nsi.pjt\85\mindev to the same working directory. You need to modify el850.cfg after the copy completes. You can then modify the code and update the LBT to include the IDY and CBL if necessary.

Disable RunLocal Synchronization

While you are developing, you will not want RunLocal synchronization to occur.  If it did, it would overlay any locally-changed B and U .LBRs and delete any non-matching E, C and V .LBRs.  You can avoid RunLocal synchronization three ways:
  • Start your testing in the Bin85 directory directly under the <Root> directory.  For example, you could copy your .LBR files to J:\COB\SHARE\ELI85\Bin85 and execute EL850CC from there.
  • From a standalone development directory (e.g., F:\NSI.PJT\85\CLS), make sure EL850.CFG has a [Path} section entry named Mprog.  The presence of an Mprog entry under [Path] in EL850.Cfg prevents RunLocal synchronization for developers.
  • From a Run Local or Run Hybrid folder, you can start EL850CC with a parameter that will eliminate synchronization:

This will cause the synchronization step to be skipped when Elliott starts up.

Edit the Registry (one time only)

  • At a command prompt, enter REGEDIT.
  • Navigate to the following node:

  • Update the value of the Animate-EL850P string to "Yes."  If the string value does not exist, add it and then set the value to "Yes."

Prepare the Program for Animation

  • Compile the program for Animation, just like for Elliott V7.5.
  • Add the .CBL, INT and .IDY to RU850E.Lbr or RU850C.Lbr or RU850V.Lbr, just as you did for V7.5.

Animate the Program

Main Programs and SubPrograms
  • Start the Elliott V8.5 Control Center.
  • Click the File menu.  You will see sub-menu named Animate.
  • Click the Animate sub-menu.  The sub-menu will display a checkmark next to it.
  • Start any menu item in the Control Center.  An Animate text box window will appear.  Continue animating as normal.

Drill Down Programs
  • Before starting the Control Center, set the following environment variable:
  • Then start the Control Center.
  • Whenever a program is drilled down to, it will be Animated instead of executed.


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: Registry Settings
  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
  74. Logging I-O Logic Errors
  75. Report Desk: Developer Documentation Roadmap
  76. Report Desk: Resolution of Pervasive.Data.SqlClient.dll
  77. TB API
  78. Creating HTML Emails for Professional Presentation
  79. EM API - Create and Send an Email
  80. DN API (Document Number Handling)

Feedback and Knowledge Base