<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenText Analytics Database 26.2.x – Variables</title>
    <link>/en/connecting-to/using-vsql/variables/</link>
    <description>Recent content in Variables on OpenText Analytics Database 26.2.x</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/connecting-to/using-vsql/variables/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Connecting-To: DBNAME</title>
      <link>/en/connecting-to/using-vsql/variables/dbname/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/dbname/</guid>
      <description>
        
        
        &lt;p&gt;The name of the database to which you are currently connected. DBNAME is set every time you connect to a database (including program startup), but it can be unset.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: ECHO</title>
      <link>/en/connecting-to/using-vsql/variables/echo/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/echo/</guid>
      <description>
        
        
        &lt;p&gt;If set to &lt;code&gt;all&lt;/code&gt;, all lines entered from the keyboard or from a script are written to the standard output before they are parsed or run.&lt;/p&gt;
&lt;p&gt;To select this behavior on program start-up, use the switch &lt;a href=&#34;../../../../en/connecting-to/using-vsql/connecting-from-command-line/command-line-options/echo-all/&#34;&gt;&lt;code&gt;-a&lt;/code&gt;&lt;/a&gt;. If set to &lt;code&gt;queries&lt;/code&gt;, vsql merely prints all queries as they are sent to the server. The switch for this is &lt;a href=&#34;../../../../en/connecting-to/using-vsql/connecting-from-command-line/command-line-options/e-echo-queries/&#34;&gt;&lt;code&gt;-e&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: ECHO_HIDDEN</title>
      <link>/en/connecting-to/using-vsql/variables/echo-hidden/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/echo-hidden/</guid>
      <description>
        
        
        &lt;p&gt;When this variable is set and a backslash command queries the database, the query is first shown. This way you can study the OpenText™ Analytics Database internals and provide similar functionality in your own programs. (To select this behavior on program start-up, use the switch &lt;a href=&#34;../../../../en/connecting-to/using-vsql/connecting-from-command-line/command-line-options/e/&#34;&gt;&lt;code&gt;-E&lt;/code&gt;&lt;/a&gt;.)&lt;/p&gt;
&lt;p&gt;If you set the variable to the value &lt;code&gt;noexec&lt;/code&gt;, the queries are just shown but are not actually sent to the server and run.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: ENCODING</title>
      <link>/en/connecting-to/using-vsql/variables/encoding/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/encoding/</guid>
      <description>
        
        
        &lt;p&gt;The current client character set encoding.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: HISTCONTROL</title>
      <link>/en/connecting-to/using-vsql/variables/histcontrol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/histcontrol/</guid>
      <description>
        
        
        &lt;p&gt;If this variable is set to &lt;code&gt;ignorespace&lt;/code&gt;, lines that begin with a space are not entered into the history list. If set to a value of &lt;code&gt;ignoredups&lt;/code&gt;, lines matching the previous history line are not entered. A value of &lt;code&gt;ignoreboth&lt;/code&gt; combines the two options. If unset, or if set to any other value than those previously mentioned, all lines read in interactive mode are saved on the history list.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Source:&lt;/strong&gt; Bash.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: HISTSIZE</title>
      <link>/en/connecting-to/using-vsql/variables/histsize/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/histsize/</guid>
      <description>
        
        
        &lt;p&gt;Specifies how much storage space is allocated to store the history of SQL statements issued in the current vsql session. vsql uses this setting, by default 500, to calculate the size of the history buffer:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;HISTSIZE * 50 (bytes)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;where 50 bytes approximates the average length of a SQL statement. The actual length of SQL statements in the current session determines how many statements vsql stores.&lt;/p&gt;
&lt;p&gt;HISTSIZE has no effect on the history that is stored in &lt;code&gt;.vsql_history&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Source:&lt;/strong&gt; Bash&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: HOST</title>
      <link>/en/connecting-to/using-vsql/variables/host/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/host/</guid>
      <description>
        
        
        &lt;p&gt;The database server host you are currently connected to. This is set every time you connect to a database (including program startup), but can be unset.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: IGNOREEOF</title>
      <link>/en/connecting-to/using-vsql/variables/ignoreeof/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/ignoreeof/</guid>
      <description>
        
        
        &lt;p&gt;If unset, sending an EOF character (usually Control+D) to an interactive session of vsql terminates the application. If set to a numeric value, that many EOF characters are ignored before the application terminates. If the variable is set but has no numeric value, the default is 10.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Source:&lt;/strong&gt; Bash.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: ON_ERROR_STOP</title>
      <link>/en/connecting-to/using-vsql/variables/on-error-stop/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/on-error-stop/</guid>
      <description>
        
        
        &lt;p&gt;By default, if a script command results in an error, for example, because of a malformed command or invalid data format, processing continues. If you set &lt;code&gt;ON_ERROR_STOP&lt;/code&gt; to &lt;code&gt;ON&lt;/code&gt; in a script and an error occurs during processing, the script terminates immediately.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; \set ON_ERROR_STOP ON
&lt;/code&gt;&lt;/pre&gt;
&lt;div class=&#34;alert admonition note&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Note&lt;/h4&gt;

If you invoke the script on Linux with
&lt;code&gt;&lt;a href=&#34;../../../../en/connecting-to/using-vsql/connecting-from-command-line/command-line-options/f-file/#&#34;&gt;vsql -f&lt;/a&gt;&lt;/code&gt;, vsql returns with error code 3 to indicate that an error occurred in the script.

&lt;/div&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: PORT</title>
      <link>/en/connecting-to/using-vsql/variables/port/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/port/</guid>
      <description>
        
        
        &lt;p&gt;The database server port to which you are currently connected. This is set every time you connect to a database (including program start-up), but can be unset.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: PROMPT1 PROMPT2 PROMPT3</title>
      <link>/en/connecting-to/using-vsql/variables/prompt1-prompt2-prompt3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/prompt1-prompt2-prompt3/</guid>
      <description>
        
        
        &lt;p&gt;These specify what the prompts vsql issues look like. See &lt;a href=&#34;../../../../en/connecting-to/using-vsql/prompting/#&#34;&gt;Prompting&lt;/a&gt; for details.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: QUIET</title>
      <link>/en/connecting-to/using-vsql/variables/quiet/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/quiet/</guid>
      <description>
        
        
        &lt;p&gt;This variable is equivalent to the command line option &lt;a href=&#34;../../../../en/connecting-to/using-vsql/connecting-from-command-line/command-line-options/q-quiet/&#34;&gt;&lt;code&gt;-q&lt;/code&gt;&lt;/a&gt;. It is probably not too useful in interactive mode.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: ROWS_AT_A_TIME</title>
      <link>/en/connecting-to/using-vsql/variables/rows-at-a-time/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/rows-at-a-time/</guid>
      <description>
        
        
        &lt;p&gt;&lt;code&gt;ROWS_AT_A_TIME&lt;/code&gt; is set by default to 1000, and retrieves results as blocks of rows of that size. The column formatting for the first block is used for all blocks, so in later blocks some entries could overflow.&lt;/p&gt;
&lt;p&gt;When formatting results, OpenText™ Analytics Database buffers &lt;code&gt;ROWS_AT_A_TIME&lt;/code&gt; rows in memory to calculate the maximum column widths. It is possible that rows after this initial fetch are not properly aligned if any of the field values are longer than those see in the first &lt;code&gt;ROWS_AT_A_TIME&lt;/code&gt; rows. &lt;code&gt;ROWS_AT_A_TIME&lt;/code&gt; can be unset with &lt;a href=&#34;../../../../en/connecting-to/using-vsql/meta-commands/meta-commands-quick-reference/&#34;&gt;vsql meta-command&lt;/a&gt;&lt;code&gt;\unset&lt;/code&gt; to guarantee perfect alignment. However, this requires re-buffering the entire result set in memory and might cause vsql to fail if the result set is too big.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: SINGLELINE</title>
      <link>/en/connecting-to/using-vsql/variables/singleline/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/singleline/</guid>
      <description>
        
        
        &lt;p&gt;This variable is equivalent to the command line option &lt;a href=&#34;../../../../en/connecting-to/using-vsql/connecting-from-command-line/command-line-options/s-single-line/&#34;&gt;&lt;code&gt;-S&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: SINGLESTEP</title>
      <link>/en/connecting-to/using-vsql/variables/singlestep/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/singlestep/</guid>
      <description>
        
        
        &lt;p&gt;This variable is equivalent to the command line option &lt;a href=&#34;../../../../en/connecting-to/using-vsql/connecting-from-command-line/command-line-options/s-single-step/&#34;&gt;&lt;code&gt;-s&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: USER</title>
      <link>/en/connecting-to/using-vsql/variables/user/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/user/</guid>
      <description>
        
        
        &lt;p&gt;The database user you are currently connected as. This is set every time you connect to a database (including program startup), but can be unset.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: VERBOSITY</title>
      <link>/en/connecting-to/using-vsql/variables/verbosity/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/verbosity/</guid>
      <description>
        
        
        &lt;p&gt;This variable can be set to the values &lt;code&gt;default&lt;/code&gt;, &lt;code&gt;verbose&lt;/code&gt;, or &lt;code&gt;terse&lt;/code&gt; to control the verbosity of error reports.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: VSQL_HOME</title>
      <link>/en/connecting-to/using-vsql/variables/vsql-home/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/vsql-home/</guid>
      <description>
        
        
        &lt;p&gt;By default, the vsql program reads configuration files from the user&#39;s home directory. In cases where this is not desirable, the configuration file location can be overridden by setting the VSQL_HOME environment variable in a way that does not require modifying a shared resource.&lt;/p&gt;
&lt;p&gt;In the following example, vsql reads configuration information out of /tmp/jsmith rather than out of ~.&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;# Make an alternate configuration file in /tmp/jsmith
mkdir -p /tmp/jsmith
echo &amp;#34;\\echo Using VSQLRC in tmp/jsmith&amp;#34; &amp;gt; /tmp/jsmith/.vsqlrc
# Note that nothing is echoed when invoked normally
vsql
# Note that the .vsqlrc is read and the following is
# displayed before the vsql prompt
#
# Using VSQLRC in tmp/jsmith
VSQL_HOME=/tmp/jsmith vsql
&lt;/code&gt;&lt;/pre&gt;
      </description>
    </item>
    
    <item>
      <title>Connecting-To: VSQL_SSLMODE</title>
      <link>/en/connecting-to/using-vsql/variables/vsql-sslmode/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/vsql-sslmode/</guid>
      <description>
        
        
        &lt;p&gt;VSQL_SSLMODE specifies how (or whether) clients (like admintools) use SSL when connecting to servers. The default value is &lt;code&gt;prefer&lt;/code&gt;, meaning to use SSL if the server offers it. Legal values are &lt;code&gt;require&lt;/code&gt;, &lt;code&gt;prefer&lt;/code&gt;, and &lt;code&gt;disable&lt;/code&gt;. This variable is equivalent to the command-line &lt;a href=&#34;../../../../en/connecting-to/using-vsql/connecting-from-command-line/command-line-options/m-sslmode/&#34;&gt;&lt;code&gt;-m&lt;/code&gt;&lt;/a&gt; option (or &lt;code&gt;--sslmode&lt;/code&gt;).&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Connecting-To: TOTP</title>
      <link>/en/connecting-to/using-vsql/variables/totp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/connecting-to/using-vsql/variables/totp/</guid>
      <description>
        
        
        &lt;p&gt;Specify the current Time-based One-time Password (Totp) value. The Totp is sent to the server in the connection string for validation. If MFA is enforced and you do not provide a Totp, a dialog is displayed. You need to enter the Totp before proceeding with authentication. Totp values are generated at 30-second intervals. A Totp code remains valid for up to 90 seconds.&lt;/p&gt;

      </description>
    </item>
    
  </channel>
</rss>
