Merge pull request #13370 from JamesDeFabia/HPCC-23521RemoveECLPlus

HPCC-23521 RemoveECLPlus chapter from docs

Reviewed-By: Greg Panagiotatos <Greg.Panagiotatos@lexisnexis.com>
Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>

docs/EN_US/HPCCClientTools/CT_Mods/CT_Comm_Line_ECL.xml

@@ -1,517 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-<book xml:base="../">
-  <bookinfo>
-    <title>Client Tools Overview</title>
-
-    <author>
-      <firstname>Boca Raton</firstname>
-
-      <surname>Documentation Team</surname>
-
-      <affiliation>
-        <orgname>Lexis Nexis</orgname>
-      </affiliation>
-    </author>
-
-    <pubdate>Sept. 2011</pubdate>
-  </bookinfo>
-
-  <chapter id="Command_Line_ECL">
-    <title>ECL Plus</title>
-
-    <sect1 id="Command_Line_Interface" role="nobrk">
-      <title>Command Line Interface</title>
-
-      <sect2 id="ECLPlus_exe">
-        <title><emphasis>eclplus.exe</emphasis></title>
-
-        <para><emphasis role="bold">eclplus </emphasis><emphasis> action=
-        owner= user= password= cluster= server= queue= graph= timeout=
-        ecl=</emphasis><emphasis> file= format= output= jobname= -debugparam1=
-        _applicationparam1=</emphasis><emphasis>
-        /variablename1=</emphasis></para>
-
-        <para><informaltable colsep="1" frame="all" rowsep="1">
-            <tgroup cols="2">
-              <colspec align="left" colwidth="125.55pt" />
-
-              <colspec />
-
-              <tbody>
-                <row>
-                  <entry><emphasis>action=</emphasis></entry>
-
-                  <entry>One of the following options:
-                  list|view|dump|delete|abort|query|graph(the default option
-                  is "query").</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>owner=</emphasis></entry>
-
-                  <entry>The workunit owner.</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>user=</emphasis></entry>
-
-                  <entry>The userid.</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>password=</emphasis></entry>
-
-                  <entry>The password authorizing access for the user.</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>cluster=</emphasis></entry>
-
-                  <entry>The name of the cluster to use.</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>server=</emphasis></entry>
-
-                  <entry>The IP address or DNS name of the ECL Watch
-                  server.</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>queue=</emphasis></entry>
-
-                  <entry>The name of the job queue.</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>graph=</emphasis></entry>
-
-                  <entry>The name of graph.</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>timeout=</emphasis></entry>
-
-                  <entry>Query timeout in seconds (0 for
-                  asynchronous).</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>ecl=</emphasis></entry>
-
-                  <entry>The ECL code to execute. Optionally, this may be
-                  replaced by the name of an input file containing the ECL to
-                  execute (in the form: @inputfile).</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>file=</emphasis></entry>
-
-                  <entry>The logical name of the file, or the logical name
-                  with the starting and ending rows specified (in the form:
-                  !logicalName[startrow,endrow]).</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>format=</emphasis></entry>
-
-                  <entry>One of the following options: default | csv | csvh |
-                  xml | runecl | bin(ary)</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>output=</emphasis></entry>
-
-                  <entry>The name of the file to output.</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>jobname=</emphasis></entry>
-
-                  <entry>The name to give the job.</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>pagesize=</emphasis></entry>
-
-                  <entry>The number of rows per page. If omitted, the default
-                  is 500.</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>-debugparam=</emphasis></entry>
-
-                  <entry>Debug parameters to pass on the command line, in the
-                  form: -debugparam=debugvalue</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>_applicationparam=</emphasis></entry>
-
-                  <entry>Parameters to pass on the command line, in the form:
-                  _applicationparam=applicationvalue</entry>
-                </row>
-
-                <row>
-                  <entry><emphasis>/variablename= </emphasis></entry>
-
-                  <entry>Variables to pass on the command line, in the form:
-                  /variablename=[(int)|(bool)] valueThe default value type is
-                  string unless int or bool is specified (in parentheses
-                  preceding the value). The <emphasis>variablename</emphasis>
-                  is the STORED name of an EXL file in your ECL code.</entry>
-                </row>
-              </tbody>
-            </tgroup>
-          </informaltable></para>
-
-        <para>The <emphasis role="bold">eclplus</emphasis> executable accepts
-        command line parameters to send directly to an ECL execution engine.
-        These options can be typed directly on the command line, sent using a
-        script or batch file, through an <emphasis role="bold">ini</emphasis>
-        file in the same directory as the executable, or any
-        combination.</para>
-
-        <sect3 id="CT_CLI_eclplus.ini" role="brk">
-          <title>eclplus.ini</title>
-
-          <para>All the options can be put directly on the command line, or
-          placed in a file called eclplus.ini in the same directory as the
-          executable. If your operating system is case-sensitive, make sure
-          the filename is in lowercase. Options that do not change very often
-          can be put in the ini file. For example:</para>
-
-          <programlisting>;The values below are examples, you should change them to match your platform deployment
-server=10.150.50.12
-cluster=thor
-queue=mythor
-user=emilykate
-password=password</programlisting>
-
-          <para>In all the examples below, we'll assume eclplus.ini has the
-          above content.</para>
-
-          <para><informaltable colsep="1" frame="all" rowsep="1">
-              <tgroup cols="2">
-                <colspec colwidth="49.50pt" />
-
-                <colspec />
-
-                <tbody>
-                  <row>
-                    <entry><graphic fileref="images/caution.png" scale="noin"
-                    xml:base="../../" /></entry>
-
-                    <entry>We do not recommend storing your password in the
-                    ini file (which is clear text). The password is included
-                    in the ini file for these examples to simplify the example
-                    code.</entry>
-                  </row>
-                </tbody>
-              </tgroup>
-            </informaltable></para>
-        </sect3>
-
-        <sect3 id="CT_RunningQueriesBatchMode">
-          <title>Running queries in batch mode</title>
-
-          <para>Batch mode queries are executed using the
-          <emphasis>ecl=</emphasis> option, in any of its three forms. In the
-          first form you simply put your ECL code on the command line
-          itself:</para>
-
-          <programlisting>eclplus ecl=1+1
-            // Result = 2</programlisting>
-
-          <para>In the second form, your ECL code is in an input file. For
-          example, assume you have a text file called dataset.txt, which
-          contains the following ECL code:</para>
-
-          <programlisting>myrec := record
-string10 firstname,
-string10 lastname
-end;
-ds := dataset([{'Yanrui', 'Ma'}, {'Richard', 'Taylor'},
-{'Richard', 'Chapman'}], myrec);
-output(ds, ,'testdata::namesdb');</programlisting>
-
-          <para>Then if you run:</para>
-
-          <programlisting>eclplus @dataset.txt</programlisting>
-
-          <para>A dataset will be created and the result will be written to
-          the thor file testdata::namesdb.</para>
-
-          <para>If also have a text file called datasetquery.txt
-          containing:</para>
-
-          <programlisting>myrec := record
-string10 firstname,
-string10 lastname
-end;
-ds1 := dataset('testdata::namesdb', myrec, thor);
-output(ds1);</programlisting>
-
-          <para>then run:</para>
-
-          <programlisting>eclplus @datasetquery.txt</programlisting>
-
-          <para>You'll get:</para>
-
-          <programlisting>firstname lastname
-Yanrui Ma
-Richard Taylor
-Richard Chapman</programlisting>
-        </sect3>
-
-        <sect3 id="CT_CLI_WorkunitManipulation">
-          <title>Workunit manipulation</title>
-
-          <para>A workunit is a data structure that is passed among eclplus,
-          daliserver, and eclccserver. It contains real-time information about
-          the query, so you can control the process of a query by manipulating
-          the workunit.</para>
-        </sect3>
-
-        <sect3 id="CT_CLI_ListAllWorkunits">
-          <title>List all work units</title>
-
-          <para>To list all work units:</para>
-
-          <programlisting>eclplus action=list</programlisting>
-
-          <para></para>
-
-          <para>The output looks like:</para>
-
-          <programlisting>WUID OWNER JOBNAME STATUS
-W20090226-100258-85132143 yma dataset.txt completed
-W20090226-100958-85552898 yma datasetquery.txt completed</programlisting>
-
-          <para></para>
-
-          <para></para>
-
-          <para>Each workunit has a WUID (WorkUnit IDentifier), owner, jobname
-          and status. You can see that the jobname is simply the filename that
-          contains the query, but you can specify the jobname by your self,
-          like this:</para>
-
-          <programlisting>eclplus jobname=myquery1 @datasetquery.txt</programlisting>
-        </sect3>
-
-        <sect3 id="CT_CLI_ViewResultofWorkunit">
-          <title>View the result of a certain workunit</title>
-
-          <para>You can look at specific workunit results, like this:</para>
-
-          <programlisting>eclplus action=view wuid=
-          W20090226-100958-85552898</programlisting>
-
-          <para>The output will look like:</para>
-
-          <programlisting>firstname lastname
-Yanrui Ma
-Richard Taylor
-Richard Chapman</programlisting>
-        </sect3>
-
-        <sect3 id="CT_CLI_DumpWorkunit">
-          <title>Dump a workunit</title>
-
-          <para>If you want to get all the details describing a workunit, use
-          the dump option for the action parameter:</para>
-
-          <programlisting>eclplus action=dump wuid= W20090226-100958-85552898</programlisting>
-
-          <para>See the Workunit Dump section below for the result.</para>
-        </sect3>
-
-        <sect3 id="CT_CLI_SeeTheThorGraph">
-          <title>See the thor graph of a workunit:</title>
-
-          <para>This action returns the XML data for one or more workunit
-          graphs.</para>
-
-          <programlisting>eclplus action=graph graph=graph1 wuid=W20090226-100958-85552898</programlisting>
-
-          <para>Graph name must be supplied in the graph= parameter.</para>
-        </sect3>
-
-        <sect3 id="CT_CLI_AbortWorkunit">
-          <title>Aborting a workunit</title>
-
-          <para>If a query is taking an usually long time and you doubt
-          something is wrong, you can abort it by:</para>
-
-          <programlisting>eclplus action=abort wuid= W20090226-100958-85552898</programlisting>
-
-          <para>You can use list to find out the wuid the workunit and use
-          abort to abort it.</para>
-        </sect3>
-
-        <sect3 id="CT_CLI_Timeout">
-          <title>Timeout</title>
-
-          <para>Before you run a query, if you know the query is going to take
-          a long time, you can specify a timeout, then your eclplus will
-          return when it reaches the timeout, and the query will run in the
-          background.</para>
-
-          <para>For example:</para>
-
-          <programlisting>eclplus @datasetquery.txt timeout=0</programlisting>
-
-          <para>eclplus will return immediately.</para>
-
-          <programlisting>eclplus @datasetquery.txt timeout=2</programlisting>
-
-          <para>eclplus will return in 2 seconds.</para>
-
-          <para>You can list/view the workunit associated with the query to
-          monitor its status.</para>
-        </sect3>
-
-        <sect3 id="CT_CLI_OutputFormat">
-          <title>Output format</title>
-
-          <para>By default, the result displays on the screen. You can direct
-          it to a file, by using the output option:</para>
-
-          <programlisting>eclplus @datasetquery.txt output=o1.txt
-cat o1.txt
-firstname lastname
-Yanrui Ma
-Richard Taylor
-Richard Chapman</programlisting>
-
-          <para>Also, you may specify the following output formats:</para>
-        </sect3>
-
-        <sect3 id="CT_CLI_CSV">
-          <title>csv</title>
-
-          <programlisting>eclplus @datasetquery.txt format=csv
-[QUERY 0]
-"Yanrui ","Ma "
-"Richard ","Taylor "
-"Richard ","Chapman "</programlisting>
-        </sect3>
-
-        <sect3 id="CT_CLI_CSVH">
-          <title>csvh</title>
-
-          <programlisting>eclplus @datasetquery.txt format=csvh
-[QUERY 0]
-"firstname","lastname"
-"Yanrui ","Ma "
-"Richard ","Taylor "
-"Richard ","Chapman "</programlisting>
-        </sect3>
-
-        <sect3 id="CT_CLI_RAW">
-          <title>raw</title>
-
-          <programlisting>eclplus @datasetquery.txt format=raw
-Yanrui     Ma
-Richard    Taylor
-Richard    Chapman</programlisting>
-        </sect3>
-
-        <sect3 id="CT_CLI_RUNECL">
-          <title>runecl</title>
-
-          <programlisting>eclplus @datasetquery.txt format=runecl
-[QUERY 0]
-[0]
-firstname -&gt; Yanrui
-lastname -&gt; Ma
-[1]
-firstname -&gt; Richard
-lastname -&gt; Taylor
-[2]
-firstname -&gt; Richard
-lastname -&gt; Chapman</programlisting>
-        </sect3>
-
-        <sect3 id="CT_CLI_Bin-ary-">
-          <title>bin(ary)</title>
-
-          <programlisting>eclplus @datasetquery.txt format=bin
-Yanrui Ma Richard Taylor Richard Chapman</programlisting>
-        </sect3>
-
-        <sect3 id="CT_CLI_WorkUnitDump">
-          <title>Workunit Dump</title>
-
-          <para>A Workunit dump is an XML representation of every piece of
-          data in the workunit. This contains all the information that you
-          could discover about the workunit by using ECL Watch.</para>
-
-          <para>The following workunit dump came from a simple COUNT(person)
-          query in the Training environment:</para>
-
-          <programlisting>&lt;W20110615-160604 agentPID="4162" agentSession="4296042782" cloneable="1" 
- clusterName="thor" codeVersion="138"  isClone="1" scope="hpccdemo" 
- state="completed" submitID="hpccdemo" 
- token="X1lUMJ6oacON/1anTHTQW1JVHr1bbY8EWTSJhlDOrtYxmD13Z5ly4Qd26sEYVtxhW"&gt;
-  &lt;Action&gt;run&lt;/Action&gt;
-  &lt;Debug&gt;
-    &lt;applyinstantecltransformations&gt;1&lt;/applyinstantecltransformations&gt;
-    &lt;applyinstantecltransformationslimit&gt;100&lt;/applyinstantecltransformationslimit&gt;
-    &lt;created_by&gt;ws_workunits&lt;/created_by&gt;
-    &lt;created_for&gt;hpccdemo&lt;/created_for&gt;
-    &lt;eclagentlog&gt;//192.168.237.132/var/log/HPCCSystems/myeclagent/eclagent.06_15_11.log
-    &lt;/eclagentlog&gt;
-    &lt;targetclustertype&gt;hthor&lt;/targetclustertype&gt;
-  &lt;/Debug&gt;
-  &lt;Query fetchEntire="1"&gt;
-    &lt;Associated&gt;
-      &lt;File crc="701142319" filename="libW20110615-160604.so" type="dll"/&gt;
-    &lt;/Associated&gt;
-    &lt;Text&gt;
-      &lt;Archive build="community_3.0.0" eclVersion="3.0.0"&gt;  &lt;Query 
-       originalFilename="C:\DOCUME~1\Hpccdemo\LOCALS~1\Temp\TFR2CE.tmp"&gt; 
-       OUTPUT(&amp;apos;Hello World&amp;apos;); &lt;/Query&gt; &lt;/Archive&gt;
-    &lt;/Text&gt;
-  &lt;/Query&gt;
-  &lt;resultLimit&gt;100&lt;/resultLimit&gt;
-  &lt;Results&gt;
-    &lt;Result fetchEntire="1" name="Result 1" sequence="0" status="calculated"&gt;
-      &lt;rowCount&gt;1&lt;/rowCount&gt;
-      &lt;SchemaRaw xsi:type="SOAP-ENC:base64"&gt; UmVzdWx0XzEABPH///8BYXNjaWkAAWFzY2lpAAAYAAAAAA== 
-      &lt;/SchemaRaw&gt;
-      &lt;totalRowCount&gt;1&lt;/totalRowCount&gt;
-      &lt;Value xsi:type="SOAP-ENC:base64"&gt; CwAAAEhlbGxvIFdvcmxk &lt;/Value&gt;
-    &lt;/Result&gt;
-  &lt;/Results&gt;
-  &lt;TimeStamps&gt;
-    &lt;TimeStamp application="workunit"&gt;
-      &lt;Created ts="1308153964"&gt; 2011-06-15T16:06:04Z &lt;/Created&gt;
-    &lt;/TimeStamp&gt;
-    &lt;TimeStamp application="EclAgent" instance="localhost.localdom"&gt;
-      &lt;Started ts="1308153971"&gt; 2011-06-15T16:06:11Z &lt;/Started&gt;
-    &lt;/TimeStamp&gt;
-    &lt;TimeStamp application="EclAgent" instance="localhost.localdom"&gt;
-      &lt;Finished ts="1308153971"&gt; 2011-06-15T16:06:11Z &lt;/Finished&gt;
-    &lt;/TimeStamp&gt;
-  &lt;/TimeStamps&gt;
-  &lt;Timings&gt;
-    &lt;Timing count="1" duration="1" max="1308040" name="WorkUnit_lockRemote"/&gt;
-    &lt;Timing count="1" duration="6" max="6577412" name="SDS_Initialize"/&gt;
-    &lt;Timing count="1" duration="0" max="704338" name="Environment_Initialize"/&gt;
-    &lt;Timing count="1" duration="16" max="16414003" name="Process"/&gt;
-  &lt;/Timings&gt;
-  &lt;Workflow&gt;
-    &lt;Item mode="normal" state="done" type="normal" wfid="1"&gt;
-      &lt;Schedule/&gt;
-    &lt;/Item&gt;
-  &lt;/Workflow&gt;
-&lt;/W20110615-160604&gt;</programlisting>
-        </sect3>
-      </sect2>
-    </sect1>
-  </chapter>
-</book>

docs/EN_US/HPCCClientTools/CT_Mods/CT_Overview.xml

@@ -22,13 +22,6 @@
         </row>
 
         <row>
-          <entry><emphasis role="bold">ECLPlus</emphasis></entry>
-
-          <entry>Command line ECL execution tool to facilitate automation of
-          ECL Code execution.</entry>
-        </row>
-
-        <row>
           <entry><emphasis role="bold">ECL</emphasis></entry>
 
           <entry>Command line ECL tool.</entry>
@@ -111,7 +104,7 @@
       <title>Installation</title>
 
       <para>The installation program installs all client tools, including the
-      ECL IDE, ECLPlus, DFUPlus, and the ECL Command line tools.</para>
+      ECL IDE, DFUPlus, and the ECL Command line tool.</para>
 
       <orderedlist>
         <listitem>
@@ -142,7 +135,7 @@
       <para><emphasis role="bold">Windows: </emphasis></para>
 
       <para>Run the executable file, for example:
-      hpccsystems-clienttools_community-4.X.X-XWindows-i386.exe on your
+      hpccsystems-clienttools_community-7.X.X-XWindows-i386.exe on your
       machine. Follow the prompts to complete the installation.</para>
 
       <para><emphasis role="bold">RPM-Based Systems (CentOS/RedHat):
@@ -174,16 +167,16 @@
       <para><emphasis role="bold">Mac OSX:</emphasis></para>
 
       <para>Run the installation file, for example:
-      hpccsystems-clienttools_community-4.X.X-XDarwin-x86_64.dmg. Follow the
+      hpccsystems-clienttools_community-7.X.X-XDarwin-x86_64.dmg. Follow the
       prompts to complete the installation.</para>
     </sect2>
 
     <sect2 id="WinPath" role="brk">
       <title>Client Tools and the Windows Path</title>
 
-      <para>The HPCC Systems Client tools are designed to allow you to have more than
-      one version installed. For that reason, the choice to add the folder of
-      executable files to your system path is optional during
+      <para>The HPCC Systems Client tools are designed to allow you to have
+      more than one version installed. For that reason, the choice to add the
+      folder of executable files to your system path is optional during
       installation.</para>
 
       <para>If you plan to use only one version, it may be easier to add the

docs/EN_US/HPCCClientTools/CT_Mods/CT_Overview_withoutIDE.xml

@@ -15,16 +15,9 @@
 
       <tbody>
         <row>
-          <entry><emphasis role="bold">ECLPlus</emphasis></entry>
-
-          <entry>Command line ECL execution tool to facilitate automation of
-          ECL Code execution.</entry>
-        </row>
-
-        <row>
           <entry><emphasis role="bold">ECL</emphasis></entry>
 
-          <entry>Command line ECL tool.</entry>
+          <entry>Command line ECL tool</entry>
         </row>
 
         <row>
@@ -104,7 +97,7 @@
       <title>Installation</title>
 
       <para>The installation program installs all client tools, including the
-      ECLPlus, DFUPlus, and the ECL Command line tools.</para>
+      DFUPlus and the ECL Command line tools.</para>
 
       <orderedlist>
         <listitem>
@@ -125,7 +118,7 @@
       <para><emphasis role="bold">Windows: </emphasis></para>
 
       <para>Run the executable file, for example:
-      hpccsystems-clienttools_community-4.X.X-XWindows-i386.exe on your
+      hpccsystems-clienttools_community-7.X.X-XWindows-i386.exe on your
       machine. Follow the prompts to complete the installation.</para>
 
       <para><emphasis role="bold">RPM-Based Systems (CentOS/RedHat):
@@ -205,7 +198,7 @@
 
       <para>If you install a version other than the delivered client tools you
       will have a folder in /opt/HPCCSystems that corresponds to the set of
-      client tools. So you could have a client tools 4.0.x, 4.2.x, 4.4.x,
+      client tools. So you could have a client tools 7.0.x, 7.2.x, 7.4.x,
       etc.</para>
 
       <para>For older versions, download the package(s), and install. Install
@@ -221,26 +214,26 @@
       client tools you installed.</para>
 
       <para><emphasis role="bold">For example</emphasis>, if you wanted to run
-      eclplus:</para>
+      DFUplus:</para>
 
-      <programlisting>eclplus action=view wuid=W12345678</programlisting>
+      <programlisting>dfuplus action=list server=http://127.0.0.1:8010</programlisting>
 
-      <para>To run eclplus for an older or another version of client tools,
-      for instance 4.0.x:</para>
+      <para>To run DFUplus for an older or another version of client tools,
+      for instance 7.0.x:</para>
 
-      <para><programlisting>/opt/HPCCSystems/4.0.x/clienttools/bin/eclplus action=view wuid=W12345678</programlisting></para>
+      <para><programlisting>/opt/HPCCSystems/7.0.x/clienttools/bin/dfuplus action=list server=http://127.0.0.1:8010</programlisting></para>
 
       <para><emphasis role="bold">Windows</emphasis></para>
 
       <para>Client tools for Windows installs in a directory such as:
-      C:\Program Files (x86)\HPCCSystems\6.2.0\clienttools\bin where the
-      number (6.2.0 for example) corresponds to the version of the client
+      C:\Program Files (x86)\HPCCSystems\7.2.0\clienttools\bin where the
+      number (7.2.0 for example) corresponds to the version of the client
       tools.</para>
 
       <para>If you want access to one version of the command line client tools
       from any folder, you can add the \bin folder to your Path in Windows
       (for example, <emphasis role="bold">C:\Program Files
-      (x86)\HPCCSystems\6.2.0\clienttools\bin</emphasis> )</para>
+      (x86)\HPCCSystems\7.2.0\clienttools\bin</emphasis> )</para>
 
       <para>The Windows installer will prompt you to delete the previous
       version during installation. If you want to keep both, decline the offer

docs/EN_US/HPCCClientTools/ClientTools.xml

@@ -62,9 +62,7 @@
               xpointer="xpointer(//*[@id='CT_Overview'])"
               xmlns:xi="http://www.w3.org/2001/XInclude" />
 
-  <xi:include href="HPCCClientTools/CT_Mods/CT_Comm_Line_ECL.xml"
-              xpointer="xpointer(//*[@id='Command_Line_ECL'])"
-              xmlns:xi="http://www.w3.org/2001/XInclude" />
+  
 
   <xi:include href="HPCCClientTools/CT_Mods/CT_ECL_CLI.xml" xpointer="xpointer(//*[@id='ECL_CLI'])"
               xmlns:xi="http://www.w3.org/2001/XInclude" />

docs/EN_US/HPCCClientTools/TheECLIDEandHPCCClientTools.xml

@@ -69,10 +69,6 @@
               xpointer="xpointer(//*[@id='The_ECL_Ide'])"
               xmlns:xi="http://www.w3.org/2001/XInclude" />
 
-  <xi:include href="HPCCClientTools/CT_Mods/CT_Comm_Line_ECL.xml"
-              xpointer="xpointer(//*[@id='Command_Line_ECL'])"
-              xmlns:xi="http://www.w3.org/2001/XInclude" />
-
   <xi:include href="HPCCClientTools/CT_Mods/CT_ECL_CLI.xml"
               xpointer="xpointer(//*[@id='ECL_CLI'])"
               xmlns:xi="http://www.w3.org/2001/XInclude" />