Contents x
      Command Line
      • 1 Minute to read
      • Print
      • Dark
        Light
      • PDF
      Contents

      Command Line

      • 1 Minute to read
      • Print
      • Dark
        Light
      • PDF
      Article summary

      The Command Line window allows direct run-time configuration of the DataJet Server.   The following calls are supported:

      CAUTION
      Care must be taken when working with the command line as incorrect or inappropriate settings could destabilise the core processor.
      Do not change these settings without the knowledge or supervision of the Database Administrator.


      Debug Calls

      CAUTION
      Debug logging will affect performance and disk usage - if using it, put in place processes to ensure that the server logging process is not left unintentionally running.

      To turn on logging, type Debug Calls and hit enter. The "started recording" message will be displayed, and details of every post and response will be output to the DataJet/bin/debug folder.


      To turn off logging, repeat the process:


      Enable Script

      Forces Script Editor to re-enable if a script command doesn't come back from Windows


      rms

      !WARNING!
      An inappropriate RMS setting could destabilise the core processor - ensure that modifications and testing are conducted in a suitable environment before updating production servers.


      Requestable Memory Size - Defines the maximum amount of memory (in GB) that can be requested by the core.  

      When the core is started, the log will display the current RMS.

      To read the current RMS from the Desktop Application, view the ResourcePool setting in Admin | System Information | Status


      By default, RMS = 16, however, larger databases (250million +) may require more than this to perform memory intensive calculations (such as CreateKeyTable, Ranking)

      To temporarily change the rms (i.e., for the lifetime of the active core) enter rms XX where XX is the required size:

      Note that RMS should always be less than the total memory available on the server, and ideally not more than half.

      Configuring RMS permanently


      version

      Returns the current version number for DataJet.exe



      memtest

      Runs a test to allocate increasing amounts of memory in order to determine the maximum that can be allocated by the core.   (See RMS for additional information on this)

      !WARNING!
      • Do not run memtest without the direct supervision of DataJet - inappropriate use of this call could destabilise DataJet server and cause issues for any connected users or executing operations.



      fileinfo [table.field]

      Returns data on underlying data files for the specified field.

      !WARNING!
      • Do not run fileinfo without the direct supervision of DataJet - inappropriate use of this call could destabilise DataJet server and cause issues for any connected users or executing operations.


      Was this article helpful?
      What's Next