Footnotes
...attribute.
Script function parameters are available only in Vortex versions 2.6 and later. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...<!DOCTYPE>
While not strictly an HTML comment, this has historically been interpreted as a comment by Vortex. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...local
Local variables are available only in Vortex versions 2.6 and later. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...lost
Except for reference arguments; see here. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.../cgi-bin/texis
Some licenses require that the URL have the word "texis" visible in the path for Vortex to run. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...issues
In Vortex versions prior to 5.0, the server's document root was always used, instead of ScriptRoot. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...extension
A Vortex file extension is optional when the web server is configured to map CGI by directory instead of by file extension. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...parameters
Script function parameters are available only in Vortex version 2.6 and later. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...named
Unlike user/builtin function calls, where arguments are unnamed and passed in declared order. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...clause
In Texis version 7 and earlier, some simple operand op operand conditions were handled by Vorex directly, not SQL. See the syntaxversion pragma (here). 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...side
Modifying variables inside a loop is only valid in Vortex versions after Sep. 1 1997. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...variable
Modifying variables inside a loop is only valid in Vortex versions after Sep. 1 1997. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...clauses.
In Vortex version 3.00.958700000 20000518 and earlier this feature may apply to non-SELECT clauses as well. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...set.
Prior to Windows 2000, the equivalent privileges were Logon Batch, Run as System, none, and Replace OS Token, respectively. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...first
Except for ErrorScript invoked during errors, where putmsg may be invoked first. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...sign.
This feature appeared in version 3.01.975500000 20001129. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...vCalendar
vCalendar is a trademark of Apple Computer, Inc., AT&T Corp., International Business Machines Corp., and Siemens. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...module.
In version 6 and earlier, this was not true; pragmas might be "remembered" across modules or script blocks. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...type.
Note that in version 6 (or compatibilityversion 6) and earlier, it was the data ($var) arguments that controlled the overall string-vs-numeric sum behavior: if one or more $var values was non-numeric, string concatenation occurred - regardless of $fmt value - otherwise numeric summation was used. Also, numeric summation used the $fmt string to print the final arithmetic sum - including any significant-digit truncation implied therein - before casting it back to the numeric type for return. This version-6-and-earlier behavior is restored if vxcp compatibilityversion is set to 6. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...strftime()
strftime() is a standard C function for formatting dates. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...one.
The l flag was actually added to the / and : codes in version 5.01.1270586000 20100406, but a bracketed class was not always printed, and a repetition operator was printed. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...as-is.
Unless some other translation is already indicated for CR and/or LF, such as hex escape for -Q. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...well
Before version 5.01.1138398232 20060127, NOT terms were marked up by default (without the N flag). 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...searches.
Currently only index and SPM searches are affected; PPM searches (equivs, parenthetical lists) do not yet support textsearchmode. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...in.
There is a small chance of misinterpreting ISO-8859-1 data, if adjacent characters coincidentally form a valid UTF-8 sequence. Hence it is preferable that all data be proper UTF-8 when iso-8859-1 is off. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...diacritics:
The expanddiacritics flag is not currently supported for indexes. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...value.
In versions prior to Dec. 16, 1999, these were assumed to be \$skip and 10, respectively. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...printed
A detailed discussion of HTTP cookies, their behavior and usage is beyond the scope of this manual. See RFC 2109 for more information. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...headers
Prior to version 7.07.1619560502 20210427, the content condition defaulted to false. Thus in such prior versions, e.g. secureif="https" would not have printed the Secure flag. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...given
Note that this is changed from versions prior to 5.01.00.1111422310 20050321, where PRINTIF implicitly defaulted to always. For backward-compatible behavior without modifying scripts, set [Texis] Default Header Printif to always in texis.ini. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...$ret
This is for backwards compatibility with early versions of sort. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...function
Note that only IPv4 addresses are currently supported by the isInNet() etc. ancillary support functions available to this script. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...security
"NTLMv2 session security" is a somewhat confusing misnomer, since it can be used under NTLMv1 as well as NTLMv2. The term refers to extended session security (for later in the transaction) that has limited or no applicability to NTLM authentication (at transaction start). The session aspects of NTLMv2 session security appear not to be used under HTTP; only the authentication-time aspects, i.e. flag negotiation and changes to NTLMv1 authentication responses. In fact, for NTLMv2 transactions (over HTTP), the Windows Local Security policy Require NTLMv2 session security has no effect other than requiring that the flag be present. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...instead.
Note that even when charsettext is set to "source", the page will still be internally translated to UTF-8 for processing, then translated back to the source charset. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...int64
int64 is only used when memory size could exceed the size of long on the system, and only in version 6.01 or later. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...Explorer
While Task Manager and Process Explorer periodically refresh their displays ala Unix top, they may not refresh their copy of the process command lines as top does. Thus, monitoring changes in a Vortex script's <syscp processdescription> with Task Manager or Process Explorer may require periodically restarting these viewers. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...array
If <sqlcp arrayconvert> is on, which it is in version 6 and later. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...modules
Library modules are available in Vortex version 2.6.936300000 19990902 and later. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...<SCHEDULE>
The <SCHEDULE> directive and associated options were added in Vortex version 3.01.985400000 20010323. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...way
Even attempting to undo changes, e.g. temporarily terminating an argument string but restoring it when done, is not permitted: arguments may potentially be in read-only memory. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...output
In version 8.00.1643152837 20220125 and later. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...conf/texis.ini
In versions prior to 6, the configuration file was called conf/texis.cnf instead of conf/texis.ini. Version 6 will try to load it from the old location if it cannot be found at the new location. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...Windows
This may vary if Texis was installed in a different directory than /usr/local/morph3. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...format
In version 4 and earlier, the format was MMM DD HH:MM:SS. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...called
In a future version, these will be parameters to the putmsg function instead of global variables. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...(tilde)
This is similar to, but distinct from, any substitution the shell may do on command line arguments. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...directory.
In version 5 and earlier the %INSTALLDIR% token was not supported, though the default was still effectively the Texis installation directory. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...set:
These should be verified as being from the server, for security; see the default ErrorScript <entry> function. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...prefixed.
In version 3.01.984200000 20010309 and earlier, only certain headers were passed: the ones listed as examples. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...SSL
Unless an anonymous cipher is used. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...inferred
These errors and their causes are based on observed OpenSSL 0.9.7e behavior. Other versions, and OpenSSL documentation, may differ. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...certificates
Unless an anonymous cipher is used, which is rarely if ever the case. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...cases
This was added in version 8.00.1645136290 20220217. Previous releases of version 8 behaved like version 7 in this respect, i.e. $loop/$next were not set by non-looping versions of loopable statements. 
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

Copyright © Thunderstone Software     Last updated: Apr 15 2024

 

Copyright © 2025 Thunderstone Software LLC. All rights reserved.