u2 basic developer toolkit user guide dbtools... · chapter 4: the u2 resource view ... you can...

U2 Basic Developer Toolkit

User Guide

Version JAN2015

January 2015DBT-JAN2015-RWS-UG-1

2

NoticesEdition

Publication date: January 2015Book number: DBT-JAN2015-RWS-UG-1Product version: Version JAN2015

Copyright© Rocket Software, Inc. or its affiliates 2005-2015. All Rights Reserved.

Trademarks

Rocket is a registered trademark of Rocket Software, Inc. For a list of Rocket registered trademarks goto: www.rocketsoftware.com/about/legal. All other products or services mentioned in this documentmay be covered by the trademarks, service marks, or product names of their respective owners.

Examples

This information might contain examples of data and reports. The examples include the names ofindividuals, companies, brands, and products. All of these names are fictitious and any similarity tothe names and addresses used by an actual business enterprise is entirely coincidental.

License agreement

This software and the associated documentation are proprietary and confidential to Rocket Software,Inc. or its affiliates, are furnished under license, and may be used and copied only in accordance withthe terms of such license.

Note: This product may contain encryption technology. Many countries prohibit or restrict theuse, import, or export of encryption technologies, and current use, import, and export regulationsshould be followed when exporting this product.

http://www.rocketsoftware.com/about/legal

3

Corporate informationRocket Software, Inc. develops enterprise infrastructure products in four key areas: storage, networks,and compliance; database servers and tools; business information and analytics; and applicationdevelopment, integration, and modernization.

Website: www.rocketsoftware.com

Rocket Global Headquarters77 4th Avenue, Suite 100Waltham, MA 02451-1468USA

To contact Rocket Software by telephone for any reason, including obtaining pre-sales informationand technical support, use one of the following telephone numbers.

Country Toll-free telephone number

United States 1-855-577-4323Australia 1-800-823-405Belgium 0800-266-65Canada 1-855-577-4323China 800-720-1170France 0800-180-0882Germany 08-05-08-05-62Italy 800-878-295Japan 0800-170-5464Netherlands 0-800-022-2961New Zealand 0800-003210South Africa 0-800-980-818United Kingdom 0800-520-0439

Contacting Technical Support

The Rocket Customer Portal is the primary method of obtaining support. If you have currentsupport and maintenance agreements with Rocket Software, you can access the Rocket CustomerPortal and report a problem, download an update, or find answers to in the U2 Knowledgebase.To log in to the Rocket Customer Portal or to request a Rocket Customer Portal account, go towww.rocketsoftware.com/support.

In addition to using the Rocket Customer Portal to obtain support, you can send an email [email protected] or use one of the following telephone numbers.

Country Telephone number

North America +1 800 729 3553United Kingdom/France +44 (0) 800 773 771 or +44 (0) 20 8867 3691Europe/Africa +44 (0) 20 8867 3692Australia +1 800 707 703 or +61 (0) 29412 5450New Zealand +0800 505 515

http://www.rocketsoftware.com

http://www.rocketsoftware.com/support

mailto:[email protected]

4

Contents

Notices................................................................................................................................................................................... 2

Corporate information......................................................................................................................................................... 3

Chapter 1: Getting started................................................................................................................................................... 5Welcome to BDT help...............................................................................................................................................5Installing and updating the DBTools using the Eclipse Update Manager.............................................................5XTOOLSUB................................................................................................................................................................. 5

Installing XTOOLSUB for UniData on Windows.......................................................................................... 6Installing XTOOLSUB for UniVerse on Windows......................................................................................... 7Installing XTOOLSUB for UNIX/Linux for UniData...................................................................................... 8Installing XTOOLSUB for UNIX/Linux on UniVerse..................................................................................... 8Installing XTOOLSUB on Windows.............................................................................................................. 9

Chapter 2: Administering servers...................................................................................................................................... 11Registering servers..................................................................................................................................................11Editing server information..................................................................................................................................... 11

Chapter 3: Managing server connections..........................................................................................................................12Connecting to a server........................................................................................................................................... 12Disconnecting from a server.................................................................................................................................. 12Disabling pattern configuration dialog boxes...................................................................................................... 12

Chapter 4: The U2 Resource view..................................................................................................................................... 13Filters....................................................................................................................................................................... 14Comparing source code......................................................................................................................................... 16Comparing local history......................................................................................................................................... 17Setting UniBasic and UniVerse BASIC program options...................................................................................... 17Working with a large amount of items................................................................................................................. 18Editing a dictionary record.................................................................................................................................... 18

Adding or modifying a standard dictionary record..................................................................................18Dictionary verification................................................................................................................................ 19

Chapter 5: The Basic Program Editor................................................................................................................................21Customizing syntax colors..................................................................................................................................... 21Code assist.............................................................................................................................................................. 21

Specifying symbols..................................................................................................................................... 21Specifying words.........................................................................................................................................22Using Code Assist........................................................................................................................................23

Collapsing blocks of text........................................................................................................................................25The Outline view.....................................................................................................................................................25Creating a code template...................................................................................................................................... 26

Creating a template automatically........................................................................................................... 27Refactoring.............................................................................................................................................................. 27Editing a program using a dynamic array editor................................................................................................. 28Editing a program using an XML editor................................................................................................................ 28Creating a program................................................................................................................................................ 29Compiling a program............................................................................................................................................. 29

Chapter 6: Debugging a program...................................................................................................................................... 30The Debug view...................................................................................................................................................... 30

Chapter 7: Default symbols and words.............................................................................................................................32

5

Chapter 1: Getting started

Welcome to BDT helpThe help provides conceptual, task-based, and reference information about BDT.

You can search for a word or phrase in these help topics by selecting the Search tab and entering yoursearch topic. To narrow the search results to an exact phrase, enclose the phrase within quotationmarks, for example, “dictionary files.”

Additional resources

For additional information about U2 products, training, and technical resources go to http://www.rocketsoftware.com/brand/rocket-u2.

Installing and updating the DBTools using the EclipseUpdate Manager

You can update and install any of the U2 DBTools using the Update Manager in Eclipse.

Find the latest information about updates for U2 DBTools at http://updates.rocketsoftware.com/u2.

Procedure

1. Launch any U2 DBTools or base Eclipse installations (beginning with Galileo) on your computer.2. From the Eclipse Help menu, select Help → Install New Software.3. Click Add, enter a name for the site, such as U2 Update Site, and in the Work with field enter

http://updates.rocketsoftware.com/u2. Click OK.4. Allow the repository to load and then expand the tree for U2 DBTools. Select the updates that you

want to apply. You can also choose to install any other U2 DBTools into your existing workspace.5. Click Next and follow the installation wizard to complete the installation of updates.6. Updates will take effect the next time an updated tool is launched.

Note: Only tools that are installed through separate InstallShield installations will appear onthe Start menu. Tools installed using the Eclipse Update Manager are installed as individualperspectives in a single Eclipse instance. You can access the different perspectives by selectingWindow → Open Perspective and then selecting the appropriate tool.

Note: You can check for updates to the DBTools by selecting Help → Check for Updates. To usethis option, you must have previously defined the http://updates.rocketsoftware.com/u2 locationin the Install New Software dialog, as described in step 3.

XTOOLSUBThis topic describes the XTOOLSUB program and how to upgrade to the latest version of XTOOLSUBon various operating systems.

http://www.rocketsoftware.com/brand/rocket-u2

http://www.rocketsoftware.com/brand/rocket-u2

http://updates.rocketsoftware.com/u2




6

Updating the XTOOLSUB Program

The XTOOLSUB program is a U2 database server-side BASIC program used by various U2 Client Tools.This includes U2 DataVu, U2 Web DE, Basic Developer's Toolkit (BDT), Extensible Administration Tool(XAdmin), Web Services Developer, and more. It also includes any tool that uses the U2 Resource View.

XTOOLSUB updates itself automatically. However, if something happens to the XTOOLSUB programyou can download the latest version from the public Tech Note site at:

https://u2tc.rocketsoftware.com/documentation/1410028.asp

The XTOOLSUB program contains several zip and tar files, and includes three or four files, dependingon the environment. The XTOOLSUB program is used by all the tools, but the other files included areonly used for the Basic Developer's Toolkit (BDT).

The XTOOLSUB_EXECPRE/XTOOLSUB_XPRE programs are for pre-execution functionality andXTOOLSUB_EXECPOST/XTOOLSUB_XPST are for post-execution functionality. These programs arediscussed further in the related public Tech Note, BDT Extensibility Details. If you have added your owncode to the pre- and post-functionality, copy those modified programs to the older database versionsrather than the pre- and post- files located here.

The files included for UniData are:

▪ XTOOLSUB▪ XTOOLSUB_EXECPRE▪ XTOOLSUB_EXECPOST▪ EDAMAPSUB (UniData 6.1 and lower)

The files included for UniVerse are:

▪ XTOOLSUB▪ XTOOLSUB_XPRE▪ XTOOLSUB_XPST▪ EDAMAPSUB (UniVerse 10.3 and lower)

Do not catalog the EDAMAPSUB subroutine when using UDT 7.1 or UV 11.1 and higher. This programalready exists on those versions.

There is a difference between the databases because UniVerse's catalog environment is a type 1 fileand has a 14–character file name limit.

Only extract the file that is needed for the database server/version and OS type you are using.The ...UX.tar (Unix) files come from AIX. You will need to run fnuxi/convcode if you use other UNIX/Linux operating systems. Files are not included for all operating systems in order to avoid unnecessaryconfusion. The files in the zip/tar files are the object code for the given programs; do not open them ina text editor.

Note: Log in as a root or administrator user when doing these steps to avoid any permissionserrors. If an overwrite message occurs, select "yes" to overwrite the file in question.

Installing XTOOLSUB for UniData on Windows

The XTOOLSUB program is installed and updated automatically through the U2 DBTools updates.However, if your version of XTOOLSUB somehow becomes unusable, you can install a new version.


Installing XTOOLSUB for UniVerse on Windows

7

Procedure

1. Download the latest version of XTOOLSUB from the public Tech Note site at https://u2tc.rocketsoftware.com/documentation/1410028.asp.

2. Copy the XTOOLSUB_UDT_NT.zip or XTOOLSUB_UDT_61_NT.zip file to a temporary directory onyour server (for example, c:\temp).

3. Extract the file to the c:\u2\ud##\sys\SYS_BP (where ## refers to the UniData major version. Forexample, 61, 71, 72, etc.) directory using your preferred unzipping utility. If UniData is installed inanother location, change the path accordingly.

4. Log in to the sys account using telnet or execute a udt shell command in the sys directory on theserver.

5. Catalog the three XTOOLSUB programs, as follows:

▪ CATALOG SYS_BP XTOOLSUB FORCE▪ CATALOG SYS_BP XTOOLSUB_EXECPRE FORCE▪ CATALOG SYS_BP XTOOLSUB_EXECPOST FORCE

Note: If you are using UniData 6.1 or lower, also run the CATALOG SYS_BP EDAMAPSUBFORCE command.

6. Connect with your U2 client tool to the U2 database server.

Installing XTOOLSUB for UniVerse on Windows


Procedure

1. Download the latest version of XTOOLSUB from the public Tech Note site at https://u2tc.rocketsoftware.com/documentation/1410028.asp

2. Copy the XTOOLSUB_UV_NT.zip or XTOOLSUB_UV_103_NT.zip file to a temporary directory onyour server. For example, c:\temp.

3. Extract the file to the c:\u2\uv\BP.O directory using your preferred unzipping utility. If UniVerse isinstalled in another location, change the path accordingly.

4. Log in to the UV home account via Telnet. The account name is UV or uv in the UV.ACCOUNT file.5. Catalog the three XTOOLSUB programs, as follows:


Note: You will receive a catalog error if you try to catalog all three programs on the samecommand line.

6. If you are using UniVerse 10.3 or later, also run CATALOG BP *EDAMAPSUB FORCE command.7. Connect with your U2 client tool to the U2 database server.






8

Installing XTOOLSUB for UNIX/Linux for UniData


The $UDTBIN referenced below is an environment variable pointing to your UniData bin directory, forexample, /usr/ud##/bin (where ##, is 61,71,72, etc.). If this variable is not set, then reference the fullpath to the UniData bin directory in the commands.

Procedure

1. Download the latest version of XTOOLSUB from the public Tech Note site at https://u2tc.rocketsoftware.com/documentation/1410028.asp.

2. Copy the XTOOLSUB_UDT_UX.tar or XTOOLSUB_UDT_61_UX.tar file to a temporary directory onyour server (for example, /tmp). If transferring using ftp, remember to use binary format.

3. Extract the file to the $UDTHOME/sys/SYS_BP directory.

a. To install using UniData 6.1 or earlier, the commands will be:cd $UDTHOME/sys/SYS_BPtar -xvf /tmp/XTOOLSUB_UDT_61_UX.tar

b. To install UniData 7.1 or later, the commands will be:cd $UDTHOME/sys/SYS_BPtar -xvf /tmp/XTOOLSUB_UDT_UX.tar

4. If you are using a non-AIX operating system, run the convcode command, as shown: $UDTHOME/sys/SYS_BP: $UDTBIN/convcode .

Note: The convcode command includes a period at the end of the line. This will converteverything in the SYS_BP file to the current format. All files report that they were converted,but this is the default answer for convcode. The existing files should already be in the correctformat.

5. Change directories to the $UDTHOME/sys directory and then and execute the UDT command, asshown:

a. CD $UDTHOME/sysb. $UDTBIN/udt





Installing XTOOLSUB for UNIX/Linux on UniVerse




Installing XTOOLSUB on Windows

9

Procedure


2. Copy the XTOOLSUB_UV_UX.tar or XTOOLSUB_UDT_UV_103_UX.tar file to a temporary directoryon your server (for example, /tmp). If transferring files using FTP, remember to use binary fileformat.

3. Extract the file to the /usr/uv/BP.O directory. If UniVerse is installed in another location, changethe path accordingly. Use 'cat /.uvhome' to find the path if needed.

Note: `cat /.uvhome` references include single backward quotation marks. This commandretrieves the current value for the UniVerse home directory before running the command.

a. To install using UniVerse 10.3 or earlier, the commands to use are:cd `cat /.uvhome`/BP.Otar -xvf /tmp/XTOOLSUB_UV_103_UX.tar

b. To install using UniVerse 11.1 or later, the commands to use are:cd `cat /.uvhome`/BP.Otar -xvf /tmp/XTOOLSUB_UV_UX.tar

4. If you are using a non-AIX operating system, run the convcode command, as shown:`cat /.uvhome`/bin/fnuxi XTOOLSUB*

5. Change directories to the UniVerse home directory and then and run the UV command, as shown:

a. cd `cat /.uvhome`b. bin/uv

6. Click Escape to exit the menu.7. Catalog the three XTOOLSUB programs, as follows:


Note: You will see a catalog error if you try to catalog all three programs on the samecommand line.

8. If you are using UniVerse 10.3 or earlier, also run the CATALOG BP *EDAMAPSUB FORCEcommand.


Installing XTOOLSUB on Windows


Procedure


2. Copy the XTOOLSUB_UDT_NT.zip or XTOOLSUB_UDT_61_NT.zip file to a temporary directory onyour server (for example, c:\temp).






10

3. Extract the file to the c:\u2\ud##\sys\SYS_BP (where ## refers to the UDT major version, i.e. 61, 71,72, etc.) directory using your preferred unzipping utility. If UniData is installed in another location,change the path accordingly.

4. Log into the sys account using telnet or execute a udt shell command in the sys directory on theserver.





11

Chapter 2: Administering serversYou must register each server that you want to access through the BASIC Developer Toolkit. The servermust be running UniVerse 10.3 or later.

Registering serversComplete the following steps to register server for the Basic Developer Toolkit.

1. From the Start menu, select All Programs, then select the folder where the Basic DeveloperToolkit resides, and then click Basic Developer Toolkit.

2. To define a server to register, using the right mouse button, right-click U2Servers, and then clickNew U2 Server.

3. Enter the name of the server you want to register in the Server Name box. Enter the host name orIP address in the Host box.

4. Select the database which you are using with Basic Developer Toolkit.The database is either UniData or UniVerse.

5. To define the following options, click Advanced:

a. Protocol Type - In the Protocol Type box, make sure the type of communication you areusing to the server is Default or TCP/IP.

b. RPC Port Number - In the RPC Port # field, enter the port number of the UniRPC serverrunning on the host. The default port number is 31438.

c. RPC Service Name - In the RPC Service Name field, enter the name of the RPC service onyour system. For UniData, this is normally udcs. On UniVerse, this is normally uvcs.

d. Login Account - In the Login Account field, enter the name of the account to which you wantto log on when accessing UniData or UniVerse.

e. Commands to Execute - If you want to execute a UniQuery or RetrieVe command, a savedparagraph, or a globally cataloged program, click Add. Enter the UniQuery or RetrieVecommand, saved paragraph name, or globally cataloged program name in the Specify aCommand field, then click OK.

f. Specify the type of session to run or debug your UniBasic or UniVerse BASIC program on theserver. Valid choices are Telnet or SSH.Enter the port number to use in the Port Number field. The default port number for SSH is22. The default port number for telnet is 23.Each session normally consumes one license. If you want to use device licensing, select theUse Device License check box.

g. Click Finish to return to the Create a New U2 Server dialog box.6. Click Finish to register the server.

The name of the server appears in the U2 Resource section of the Basic Developer Toolkit.

Editing server informationYou can change the information you previously entered about a registered server:

1. Right-click the server for which you want to edit information, then click Properties.2. Edit the information you want to change.3. Click Finish to save the changes, or click Cancel to exit the dialog box without saving changes.

12

Chapter 3: Managing server connectionsThis section describes how to connect and disconnect from a UniData or UniVerse server.

Connecting to a server1. To connect to a server, double-click the server to which you want to connect, or right-click the

server and then click Connect.2. Enter the login name of the user you are connecting as in the User ID field.3. Tab to the Password field and enter the password for the user.4. If you want the Basic Developer Toolkit to remember your login credentials, select the Remember

me check box.If you select this check box, the Basic Developer Toolkit logs on to the server directly and does notdisplay the Connect to a U2 Server dialog box.

5. If you want to connect to the server using a user ID and password different from the one yousaved, or you chose not to remember your password, right-click the server to which you want toconnect, then click Connect Using New User ID.After you connect to the server, the U2 Resource view of the Basic Developer Toolkit displays theAccounts and Cataloged programs on the server to which you are connected.

When connecting to the server, the Basic Developer Toolkit checks if the server side programs are upto date. If they are not, it displays the Update server programs dialog box and prompts if you want toupdate the programs. If you do not want to automatically check whether the programs are current,select the Disable automatic check for updates to server programs check box.

Disconnecting from a server▪ To disconnect from a server, right-click on the server from which you want to disconnect, then click

Disconnect.

Disabling pattern configuration dialog boxesWhen a container node contains multiple items, the Basic Developer Toolkit automatically displaysthe Configure name patterns dialog box.

If you do not want this dialog box to automatically appear, select the Do not show this patternconfiguration anymore check box.

13

Chapter 4: The U2 Resource viewThe following example illustrates the default Basic Developer Toolkit perspective:

The U2 Resource View contains information about each UniData or UniVerse account of the server towhich you are connected. This information includes accounts, data files, dictionary files, UniBasic orUniVerse BASIC programs, XML/DB mapping files, and cataloged programs.

Chapter 4: The U2 Resource view

14

FiltersYou can establish filters to filter out information you do not want the Basic Developer Toolkit todisplay. There are two types of filters, Resource-type filters and pattern filters.

Resource-type Filters

Resource-type filters include server filters, account filters, and file filters.

▪ Server Filter - Use the server filter to exclude UniData or UniVerse servers from being displayed inthe Basic Developer Toolkit. By default, the server filter is empty.

▪ Account Filter - Use the account filter to exclude UniData or UniVerse accounts from beingdisplayed in the Basic Developer Toolkit. By default, the Basic Developer Toolkit filters out UniDataand UniVerse system accounts using the following pattern:Master*, sys*, bin_*.

▪ File Filter - Use the file filter to exclude UniData or UniVerse files from being displayed in the BasicDeveloper Toolkit.By default, UniData excludes the following files:CTLGSAVELISTS_HOLD__PH__XML_savedlists_MAP__report_AE-related filesCTLGTBENGLISH.MSGERRMSGHELP.FILEMENUFILEREP_RECV_LOGREP_RECV_RECVOC

Filters

15

_DEBUG_vocprivilege_REPORT__SCREENAPP.PROGSBASIC.HELPcatdirGLOBAL.CATDIRDICT.filesBy default, UniVerse excludes the following files:CTLGSAVEDLISTS&HOLD&&PH&&XML&savedlists&MAP&&report&AE-related filesCTLGTBENGLISH.MSGERRMSGHELP.FILEMENUFILEREP_RECV_LOGREP_RECV_RECVOC&DEBUG&&MAP&vocprivilege&REPORT&&SCREEN&UV.ACCOUNTAPP.PROGSBASIC.HELPcatdirGLOBAL.CATDIRNLS-related filesDICT.filesUNIVERSE.filesUV_filesUV.filesSYS.filesREVISE.files

Pattern Filters

Use a pattern filter to exclude any name defined by the pattern you specify from being displayed in theBasic Developer Toolkit. This filter is disabled by default.

1. To enable, select Window → Preferences → UniData/UniVerse.2. Select

Enable Pattern Configuration, and then click Apply.


16

3. In the U2 Resource View, click Accounts to open the the filter dialog box.

Comparing source codeYou can compare two UniBasic or UniVerse BASIC programs with each other to display the differencesin the programs.

Select the first program you want to compare in the account and file where it resides. Holding downthe CTRL key, select the second program with which you want to compare the first. Right-clickCompare With and select Each Other.

The first program you select appears in the left frame, while the second program you select appears inthe right frame. The Basic Developer Toolkit highlights the differences in the program.

Comparing local history

17

Comparing local historyYou can compare the history of changes to a program made on your local machine.

1. To compare local history, right-click the program for which you want to view history, then selectTeam > Show Local History.The Basic Developer Toolkit shows the local history for the program you selected.

2. You can compare changes made to the program by selecting the two revision times you wantcompare, then follow the steps in Comparing source code, on page 16.

Setting UniBasic and UniVerse BASIC program optionsYou can specify compilation and cataloging options for UniBasic and UniVerse BASIC programs at theaccount level or the program level.

To set program options, right-click the account or directory file for which you want to set theoptions, then click U2 Basic Program Options.For UniData:

a. Select the BASICTYPE you want to use.


18

b. If you want UniBasic reserved words to be case insensitive, select the Reserved words inUniBasic are case insensitive check box.

c. Select the catalog options for the directory or account, then click Finish.Program options set at the directory level override program options set at the account level.

For UniVerse:

a. If you want UniVerse BASIC variables and labels to be case insensitive, select the Variablesand labels in UniVerse BASIC are case insensitive check box.

b. Select the catalog options for the directory or account, then click Finish.Program options set at the directory level override program options set at the account level.

Working with a large amount of itemsSometimes a directory contains a large amount of items, which may have increased the time the BasicDeveloper Toolkit took to load the items. To solve this problem, you can either select the page youwant to display, or select the page you want to display through pattern matching.

Selecting the page to display▪ To select the page you want to display, right-click the file containing the items, then highlight

Switch displaying page, then click the page where you want to begin the display.

Alternatively, you can click the Switch the displaying page icon ( ), then select the page whereyou want to begin the display.

Configure a pattern for the page to display

1. To configure a pattern for the page to display, right-click the file containing the items, then clickConfigure Patterns.

2. In the Configure Name Patterns dialog box, enter the file name patterns you want to match.Separate each pattern with a comma. Pattern matching characters are:

▪ * = any string▪ ? = any character▪ ,, (2 commas) = , (comma)

3. Select the page where you want to start displaying the filtered items in the Go To Page field.

Editing a dictionary recordTo edit a dictionary record, right-click the file for which you want to edit the dictionary, then clickOpen Dictionary.

Adding or modifying a standard dictionary record

You can add or change the first 8 attributes of a dictionary record.

1. To add a dictionary record, click Add.2. In the ID field, enter the ID for the dictionary record.3. In the Type field, enter the type of dictionary record.

Valid values are:

▪ D - Numeric and alphabetic character

Dictionary verification

19

▪ V or I - Virtual attribute formula▪ PH - Phrase▪ X - User-defined phrase

4. If the dictionary record is a D-type, enter the location of the attribute in the Formula field. If thedictionary record is a V-type or I-type, click Build under the Formula field.

5. Compose the virtual formula, or click the type of function, expression, or operator you need tobuild the formula.You can choose:

▪ Special Virtual Attribute Functions▪ UniBasic Functions▪ Virtual Attribute Functions▪ @variables▪ Arithmetic Operators▪ String Operators▪ Relational Operators▪ Conditional Expressions▪ Boolean Operator

6. If the dictionary record is a PH-type, enter the phrase in the Formula field.7. If the dictionary record is an X-type, enter the phrase in the Formula field.8. Enter a conversion code in the Conversion field, if necessary.9. Enter a column heading, if different from the record ID, in the Display Name box10. Enter the length, justification, and other formatting codes in the Display Format box.11. Select the type of attribute in the SM box.

For UniData, valid values are S for singlevalued, MV for multivalued, and MS for multi-subvalued.For UniVerse, valid values are S for singlevalued or M for multivalued.

12. If the dictionary record is part of an association, select the name of the association in theAssociation box.

13. Click Undo if you want to discard changes made to the dictionary record selected. Click Undo Allif you want to discard all changes made to the dictionary.

If you edit a dictionary record using the Dynamic Array Editor, you can add, delete, or update anyfield. This is useful for Pick-type dictionary records, where A-type and S-type dictionary records havedifferent field definitions. For example, field 3 is defined as the column heading for A-type and S-typedictionary records, but is the conversion code for D-type, I-type, and V-type records.

Dictionary verification

The Basic Developer Toolkit verifies the dictionary each time a field is changed.

An error is returned if the following problems are found:

▪ A record ID is empty▪ A record ID contains characters other than letters, numbers, and the"@", "_", ".", "S", and "/"

characters.▪ Two dictionary records have the same record ID.▪ A dictionary type is not defined, except for entries starting with "@."▪ If the dictionary record is a D-type, an error is returned if the location is not present. For I-type or V-

type attributes, a warning is returned if the expression value is not present.▪ The location is defined as a negative integer.▪ For UniVerse, the SQL data type must be valid if it is present.


20

A warning is returned if the following problems are found:

▪ For a PH-type dictionary record, the phrase should contain valid entries.▪ For D-type, I-type, V-type, A-type, or S-type dictionary records, singlevalued, multivalued, or multi-

subvalued (UniData only) should be defined.▪ If an association is defined, it should be a valid entry.

21

Chapter 5: The Basic Program EditorThe Basic Program Editor provides several options to assist you in creating or editing BASIC programs.

Customizing syntax colorsThe Basic Developer Toolkit recognizes UniBasic and UniVerse BASIC syntax, and provides syntaxhighlighting. You can configure the colors used and formatting for the code.

The Basic Developer Toolkit highlights syntax error marks after each unsuccessful compilation.Press F2 to switch focus to the window containing the syntax. You can now scroll up and down in thewindow to see the full syntax.

1. To customize the colors for syntax highlighting, select Window > Preferences.2. Click UniData/UniVerse.3. Click U2 Basic, expand Editor, then click Syntax Coloring.4. Customize the coloring for the following elements:

▪ Keyword▪ Reserved word▪ Function name▪ @ Variable▪ String▪ Comment▪ Other

Code assistCode assist uses code templates and helps in avoiding syntax errors.

Code assist checks the following elements in addition to the code template:

▪ Verbs▪ Keywords▪ Functions▪ @ Variables▪ $ Variables▪ Defined labels▪ Defined variables▪ Defined user functions

The Basic Developer Toolkit uses a set of default verbs, keywords, functions, @variables and $variables. You can override these defaults by creating the XTOOLSUB.DATA file in the udthome/sys for UniData or universe_home/include directory. This file contains two sections, one forsymbols and one for words.

Specifying symbols

The Basic Developer Toolkit uses a set of default verbs, keywords, functions, @variables and $variables. You can override these defaults by creating the XTOOLSUB.DATA file in the udthome/

Chapter 5: The Basic Program Editor

22

sys for UniData or universe_home/include directory. This file contains two sections, one forsymbols and one for words.

The symbols section should start with "*symbols" and each line of the section should have thefollowing format:

{"symbol_name", symbol_type, 0}

The symbol_type should be one of the following:

▪ Vavariable - @ Variable (read/write)▪ Vrvariable - @Variable (read only)▪ Vprequate - Pre-defined equate statement

The following example illustrates the symbols section of the file:

**symbols*{"@SYSTEM.RETURN.CODE", Vavariable, 0}{"@STDFIL", Vavariable, 0}{"@SELECTED", Vavariable, 0}{"@IM", Vprequate, 0, "Add: more ITM"}{"@FM", Vprequate, 0}{"@AM", Vprequate, 0}{"@VM", Vprequate, 0}...

Specifying words

The Basic Developer Toolkit uses a set of default verbs, keywords, functions, @variables and $variables. You can override these defaults by creating the XTOOLSUB.DATA file in the udthome/sys for UniData or universe_home/include directory. This file contains two sections, one forsymbols and one for words.

The word section should start with "*words" and each line of the section should have the followingformat:

{“name”, type, num_of_args, max_num_of_args, optional_arg_flag, left_value_arg_list, optional_description}

The following table describes valid values for the type variable:

Type Description

Lunknown Type unknownLbflag Statement that starts at the line.Lbfunc Function style statement (CONVERT, DELETE, REMOVE)Lbos Beginning of line statementLelse Special case: 'ELSE'Lend Special case: 'END'Lflag Check keyflagLfunct Check for following '('Lloc Special case: 'LOCATE'

Using Code Assist

23

Type Description

Llock Special case: 'LOCKED' (also checks keyflag)Lloop Special case: 'UNTIL' & 'WHILE'Lnext Special case: 'NEXT'Lsub Special case: 'SUBROUTINE'Lthen Special case: 'THEN'Lget Special case: 'GET('Lseek Special case: 'SEEK('Lprntr Special case: 'PRINTERR'Lexec Special case: 'PERFORM'Lstat Special case: 'STATUS'Lerror Special case: '(ON) ERROR'Lbig Special case: '$DEFINE, $UNDEFINE'Lcdir Special case: '$ELSE, $ENDIF'

The code assist feature uses the num_of_args, max_num_of_args, optional_arg_flag, andleft_value_arg_list for functions only.

The following example illustrates the words portion of the XTOOLSUB.DATA file:

**words*{"$DEFINE", Lbos, 0, 0, 0, 0}{"$ELSE", Lcdir, 0, 0, 0, 0}{"$ENDIF", Lcdir, 0, 0, 0, 0}{"$F", 0, 0, 0, 0, 0}{"$FALSE", 0, 0, 0, 0, 0}{"$IFDEF", Lbig, 0, 0, 0, 0}{"$IFNDEF", Lbig, 0, 0, 0, 0}{"$OPTIONS", Lbos, 0, 0, 0, 0}...

Using Code Assist

This section describes using Code Assist with GOSUB, CALL statements, functions, and viewing syntax.

Using Code Assist with GOSUB

If you enter a GOSUB or GOTO statement, the Basic Developer Toolkit displays all the labels containedin the program. Enter:

GOSUB(CTRL+SPACE)

Select the correct subroutine from the list.


24

Using Code Assist with CALL

If you enter a CALL statement followed by a (CTRL+SPACE), the Basic Developer Toolkit displays allglobally and locally cataloged programs in alphabetical order.

Using Code Assist with Functions

When you enter the name of UniBasic or UniVerse function, the Basic Developer Toolkit displaysdetailed information for the function. If you enter the following statement:

RET = XDOM(CTRL+SPACE)

The Basic Developer Toolkit will display all functions beginning with "XDOM." When you select thefunction, the Basic Developer Toolkit inserts the function as a template:

RET = XDOMOpen(xmlDocument, docLocation, domHandle)

Press the tab key to enter your values for the function parameters.

Collapsing blocks of text

25

Viewing Syntax

You can hover over a UniBasic or UniVerse BASIC function or statement to view the syntax. After thesyntax appears, press F2 to keep the syntax on the screen.

Collapsing blocks of textYou can collapse certain blocks of text within the program.

If you click the "-" icon, the Basic Developer Toolkit collapses the statement. After the statement iscollapsed, you can hover over the "+" to view the statements.

The Outline viewThe Basic Developer Toolkit displays all procedures and labels that appear in the source code youspecify. With this outline, you can easily jump to appropriate reference in the source code.


26

The Basic Developer Toolkit uses the following icons:

Included File

Label

Variable or user function

Common variable

Array

Creating a code templateThe Basic Developer Toolkit allows you to use code templates, which are definitions of the UniBasicor UniVerse BASIC syntactical constructions. You can create your own code templates to expand yourown shortcuts, such as a template to insert the author and date for the source code.

1. From the Window menu, click Preferences and expand UniData/UniVerse > U2 Basic > Editor,and then click Templates.

2. To create a new template, from the Template dialog box, click New.3. To edit an existing template, click Edit.4. To import a template, highlight the template you want to import, then click Import.5. To delete a template, click Remove.

Creating a template automatically

27

Creating a template automatically

From the Basic Developer Toolkit Editor, you can automatically create a template by marking asegment of the source code.

1. After marking the source code, click U2 Basic, then click Copy Selection as Template.2. In the Name field, enter the name for the new template.3. Enter a description for the template in the Description field.

RefactoringThe Basic Developer Toolkit supports refactoring for renaming variables or labels in the currentUniBasic or UniVerse BASIC source code. Refactoring changes a program's internal structure withoutmodifying its external behavior or existing functionality. You usually refactor a program to improve thereadability, improve extensibility, or simplify code structure.

1. Right-click the name of an element you want to change in your UniBasic or UniVerse BASIC sourcecode, expand Refactor, then click Rename.

2. Enter the new name of the element in the New name field, then click Preview.The Basic Developer Toolkit displays the instances of the original variable name and previews thechanges.

3. To process the changes, click OK, or click Cancel to exit the program without changing theelement name.


28

Editing a program using a dynamic array editorYou can edit a program using a dynamic array editor.

Select the source code you would like to edit, then click the U2 Basic menu, and then click EditSelection as Dynamic Array.

Editing a program using an XML editorYou can edit a program using an XML editor.

1. Select the source code you would like to edit, as shown in the following example:

doc='<ADDRBOOK cmt="my address book"> <ENTRY ID="id1"> <NAME>NameOne</NAME> <ADDRESS>101 Some Way</ADDRESS> <PHONENUM DESC="Work">303-111-1111</PHONENUM> <PHONENUM DESC="Fax">303-111-2222</PHONENUM><PHONENUM DESC="Pager">303-111-3333</PHONENUM> <EMAIL>[email protected]</EMAIL> </ENTRY> <ENTRY ID="id2"> <NAME>Name Two</NAME><ADDRESS>202 Some Way</ADDRESS> <PHONENUM DESC="Work">303-222-1111</PHONENUM> <PHONENUM DESC="Fax">303-222-2222</PHONENUM> <PHONENUMDESC="Home">303-222-3333</PHONENUM> <EMAIL>[email protected]</EMAIL> </ENTRY> </ADDRBOOK>'

2. Click the U2 Basic menu, then click Edit Selection as XML.The XML editor appears.

Creating a program

29

Creating a program1. To create a new UniBasic or UniVerse BASIC program, right-click the database file where you want

to create the program, then click New Basic Program.2. After you have completed the program, to save the program, click the Save icon, select File >

Save , or right-click within the program and click Save.

Compiling a program▪ To compile the UniBasic or UniVerse BASIC program, from the U2 Basic menu, click Compile U2

Program, or right-click within the program and click Compile U2 Program.The U2 Console pane displays messages generated during the compilation process.

30

Chapter 6: Debugging a program1.

From the Basic Developer Toolkit toolbar, click the arrow next to the debug icon ( ).2. Click Open Debug Dialog.

3. Click the Main tab.4. In the Program area of the Debug dialog box, expand the account where the UniVerse BASIC

program that you want to debug resides.5. Click the Source tab. In this tab, the Basic Developer Toolkit displays directory files for the source

locator to find the UniVerse BASIC source code.6. Click Add to include another path for the UniVerse BASIC source code.7. Click the Terminal tab.8. In the User ID box, enter the login ID on the server to which you want to connect. Enter the

corresponding password in the Password box.9. Select the terminal type you want to use in the Terminal Type box.10. Enter the port number you want to use in the Port Number box.11. Click Debug.

The Debug viewWhen you debug a UniVerse BASIC program in the Basic Developer Toolkit, the debug perspectiveappears, consisting of the several views.

The sections include:

The Debug view

31

▪ Stack view▪ Variable View▪ Breakpoints View▪ Outline View▪ Console View▪ U2 Console View▪ U2 Debug Terminal View

Stack view

The Stack View shows the current calling stack, as shown in the following example:

Variable view

The Variable View displays all the variables contained in the program and their values in the programthat is currently running, as shown in the following example:

Due to performance issues, the Basic Developer Toolkit does not automatically monitor all variables.To enable a watch flag, right-click the variable you want to monitor, then click Enable Watch Flag. Todisable a watch flag, right-click the variable you do not want to monitor and click Disable Watch Flag.

Right-click in the Variables view, then click Show Monitored Variables Only if you only want enabledvariables to appear in the list.

32

Chapter 7: Default symbols and wordsThis topic describes the default symbols and words for the Basic Developer Toolkit code assist feature.If you do not specify a symbol or word in the XTOOLSUB.DATA file, the code assist feature uses thedefault symbols and words described here.

Default Symbols

*symbols

*

{"@SYSTEM.RETURN.CODE", Vavariable, 0}

{"@STDFIL", Vavariable, 0}

{"@SELECTED", Vavariable, 0}

{"@IM", Vprequate, 0, "Add: more ITM"}

{"@FM", Vprequate, 0}

{"@AM", Vprequate, 0}

{"@VM", Vprequate, 0}

{"@SM", Vprequate, 0}

{"@SVM", Vprequate, 0}

{"@TM", Vprequate, 0}

{"@CRTHIGH", Vprequate, 0}

{"@CRTWIDE", Vprequate, 0}

{"@LPTRHIGH", Vprequate, 0}

{"@LPTRWIDE", Vprequate, 0}

{"@WHO", Vrvariable, 0}

{"@LOGNAME", Vrvariable, 0}

{"@ACCOUNT", Vrvariable, 0}

{"@USERNO", Vrvariable, 0}

{"@USER.NO", Vrvariable, 0}

{"@COMMAND", Vrvariable, 0}

{"@SENTENCE", Vavariable, 0}

{"@PARASENTENCE", Vrvariable, 0}

{"@SYS.BELL", Vrvariable, 0}

{"@LEVEL", Vrvariable, 0}

{"@TIME", Vavariable, 0}

{"@DATE", Vavariable, 0}

{"@DAY", Vavariable, 0}

{"@MONTH", Vavariable, 0}

{"@YEAR", Vavariable, 0}

Default symbols and words

33

{"@FILENAME", Vavariable, 0}

{"@FILE.NAME", Vavariable, 0}

{"@RECORD", Vavariable, 0}

{"@ID", Vavariable, 0}

{"@USER.RETURN.CODE", Vavariable, 0}

{"@SYSTEM.SET", Vavariable, 0}

{"@TERM.TYPE", Vrvariable, 0}

{"@NB", Vavariable, 0}

{"@ND", Vavariable, 0}

{"@NI", Vavariable, 0}

{"@RECCOUNT", Vavariable, 0}

{"@NV", Vavariable, 0}

{"@MV", Vavariable, 0}

{"@NS", Vavariable, 0}

{"@ANS", Vavariable, 0}

{"@CONV", Vavariable, 0}

{"@DICT", Vavariable, 0}

{"@FORMAT", Vavariable, 0}

{"@HEADER", Vavariable, 0}

{"@OPTION", Vavariable, 0}

{"@USER0", Vavariable, 0}





{"@RECUR0", Vavariable, 0}





{"@TTY", Vavariable, 0}

{"@NULL", Vrvariable, 0}

{"@NULL.STR", Vrvariable, 0}

{"@SQL.ERROR", Vrvariable, 0}

{"@SQL.WARNING", Vrvariable, 0}

{"@SQL.CODE", Vrvariable, 0}

{"@SQL.STATE", Vrvariable, 0}

{"@SCHEMA", Vrvariable, 0}

Chapter 7: Default symbols and words

34

{"@TRANSACTION.ID", Vrvariable, 0}

{"@AUTHORIZATION", Vrvariable, 0}

{"@ABORT.CODE", Vrvariable, 0}

{"@COMMAND.STACK", Vprequate, 0}

{"@DATA.PENDING", Vprequate, 0}

{"@PATH", Vrvariable, 0}

{"@TRANSACTION", Vrvariable, 0}

{"@ISOLATION", Vrvariable, 0}

{"@TRANSACTION.LEVEL", Vrvariable, 0}

{"@TRUE", Vprequate, 0}

{"@FALSE", Vprequate, 0}

{"@HENV", Vrvariable, 0}

{"@HDBC", Vrvariable, 0}

{"@HSTMT", Vrvariable, 0}

{"@SQLPROC.NAME", Vrvariable, 0}

{"@SQLPROC.TX.LEVEL", Vrvariable, 0}

{"@SQL.DATE", Vrvariable, 0}

{"@SQL.TIME", Vrvariable, 0}

{"@CASCADE", Vrvariable, 0}

{"@YEAR4", Vavariable, 0}

{"@DF.IOTYPE", Vrvariable, 0}

Default Words

This section describes the default words used by the code assist feature of the Basic Developer Toolkit.

*words

*

{"$DEFINE", Lbos, 0, 0, 0, 0}

{"$ELSE", Lcdir, 0, 0, 0, 0}

{"$ENDIF", Lcdir, 0, 0, 0, 0}

{"$F", 0, 0, 0, 0, 0}

{"$FALSE", 0, 0, 0, 0, 0}

{"$IFDEF", Lbig, 0, 0, 0, 0}

{"$IFNDEF", Lbig, 0, 0, 0, 0}

{"$OPTIONS", Lbos, 0, 0, 0, 0}

{"$T", 0, 0, 0, 0, 0}

{"$TRUE", 0, 0, 0, 0, 0}

{"$UNDEFINE", Lbos, 0, 0, 0, 0}

{"ABORT", Lbflag, 0, 0, 0, 0}


35

{"ABORTE", Lbos, 0, 0, 0, 0}

{"ABORTM", Lbos, 0, 0, 0, 0}

{"ABS", Lfunct, 1, 1, 0, 0}

{"ABSS", Lfunct, 1, 1, 0, 0}

{"acceptConnection", Lfunct, 6, 6, 0, LVA_4|LVA_5|LVA_6}

{"ACOS", Lfunct, 1, 1, Ftrig, 0}

{"ACTIVATEKEY", Lbos, 0, 0, 0, 0}

{"addAuthenticationRule",Lfunct, 4, 4, 0, 0}

{"addCertificate", Lfunct, 5, 5, 0, 0}

{"addRequestParameter", Lfunct, 4, 4, 0, 0}

{"ADDS", Lfunct, 2, 2, 0, 0}

{"ALL", Lflag, 0, 0, 0, 0}

{"ALPHA", Lfunct, 1, 1, 0, 0}

{"amInitialize", Lfunct, 4, 4, 0, LVA_1|LVA_4}

{"amReceiveMsg", Lfunct, 9, 10, 0, LVA_6|LVA_7|LVA_9}

{"amReceiveRequest",Lfunct, 9, 10, 0, LVA_5|LVA_6|LVA_9}

{"amSendMsg", Lfunct, 6, 6, 0, LVA_6}

{"amSendRequest", Lfunct, 7, 7, 0, LVA_7}

{"amSendResponse", Lfunct, 7, 7, 0, LVA_7}

{"amTerminate", Lfunct, 3, 3, 0, LVA_1|LVA_3}

{"analyzeCertificate", Lfunct, 3, 3, 0, 0}

{"AND", 0, 0, 0, 0, 0}

{"ANDS", Lfunct, 2, 2, 0, 0}

{"ARG.", Lflag, 0, 0, 0, 0}

{"ASCII", Lfunct, 1, 1, 0, 0}

{"ASIN", Lfunct, 1, 1, Ftrig, 0}

{"ASSIGN", Lbos, 0, 0, 0, 0}

{"ASSIGNED", Lfunct, 1, 1, 0, 0}

{"ATAN", Lfunct, 1, 1, Ftrig, 0}

{"AUTHORIZATION", Lbos, 2, 2, 0, 0}

{"AUTHORIZE", Lfunct, 2, 2, 0, 0}

{"AUXMAP", Lbos, 0, 0, 0, 0}

{"BCONVERT", Lfunct, 2, 2, 0, 0}

{"BEFORE", Lflag, 0, 0, 0, 0}

{"BEGIN", Lbos, 0, 0, 0, 0}

{"BITAND", Lfunct, 2, 2, 0, 0}

{"BITNOT", Lfunct, 1, 2, Fnego, 0}

{"BITOR", Lfunct, 2, 2, 0, 0}


36

{"BITRESET", Lfunct, 2, 2, 0, 0}

{"BITSET", Lfunct, 2, 2, 0, 0}

{"BITTEST", Lfunct, 2, 2, 0, 0}

{"BITXOR", Lfunct, 2, 2, 0, 0}

{"BREAK", Lbos, 0, 0, 0, 0}

{"BSCAN", Lbos, 0, 0, 0, 0}

{"BY", Lflag, 0, 0, 0, 0}

{"BYTE", Lfunct, 1, 1, 0, 0}

{"BYTELEN", Lfunct, 1, 1, 0, 0}

{"BYTETYPE", Lfunct, 1, 1, 0, 0}

{"BYTEVAL", Lfunct, 1, 2, Fone, 0}

{"CALL", Lbos, 0, 0, 0, 0}

{"CALLING", Lflag, 0, 0, 0, 0}

{"CAPTURING", Lflag, 0, 0, 0, 0}

{"CASE", Lbflag, 0, 0, 0, 0}

{"CAT", 0, 0, 0, 0, 0}

{"CATS", Lfunct, 2, 2, 0, 0}

{"CENTURY.PIVOT", Lfunct, 1, 1, 0, 0}

{"CHAIN", Lbos, 0, 0, 0, 0}

{"CHANGE", Lfunct, 3, 5, 0, 0}

{"CHAR", Lfunct, 1, 1, 0, 0}

{"CHARS", Lfunct, 1, 1, 0, 0}

{"CHECKSUM", Lfunct, 1, 1, 0, 0}

{"CLEAR", Lbos, 0, 0, 0, 0}

{"CLEARCOMMON", Lbos, 0, 0, 0, 0}

{"CLEARDATA", Lbos, 0, 0, 0, 0}

{"CLEARDIAGNOSTICS", Lfunct, 0, 0, 0, 0}

{"CLEARFILE", Lbos, 0, 0, 0, 0}

{"CLEARINPUT", Lbos, 0, 0, 0, 0}

{"CLEARPROMPTS", Lbos, 0, 0, 0, 0}

{"CLEARSELECT", Lbos, 0, 0, 0, 0}

{"CLOSE", Lbflag, 0, 0, 0, 0}

{"CLOSESEQ", Lbos, 0, 0, 0, 0}

{"closeSocket", Lfunct, 1, 1, 0, LVA_1}

{"CloseXMLData", Lfunct, 1, 1, 0, 0}

{"COL1", Lfunct, 0, 0, 0, 0}

{"COL2", Lfunct, 0, 0, 0, 0}

{"COM", Lbos, 0, 0, 0, 0}


37

{"COMMIT", Lbflag, 0, 0, 0, 0}

{"COMMON", Lbflag, 0, 0, 0, 0}

{"COMPARE", Lfunct, 2, 3, Fnull, 0}

{"CONTINUE", Lbos, 0, 0, 0, 0}

{"CONVERT", Lbfunc, 3, 3, 0, 0}

{"COS", Lfunct, 1, 1, Ftrig, 0}

{"COSH", Lfunct, 1, 1, Ftrig, 0}

{"COUNT", Lfunct, 2, 2, Fovlap, 0}

{"COUNTS", Lfunct, 2, 2, 0, 0}

{"CREATE", Lbos, 0, 0, 0, 0}

{"createCertificate", Lfunct, 8, 8, 0, 0}

{"createCertRequest", Lfunct, 9, 9, 0, 0}

{"createRequest", Lfunct, 3, 3, 0, LVA_3}

{"createSecureRequest", Lfunct, 4, 4, 0, LVA_3}

{"createSecurityContext", Lfunct, 2, 2, 0, LVA_1}

{"CRT", Lbos, 0, 0, 0, 0}

{"DATA", Lbos, 0, 0, 0, 0}

{"DATE", Lfunct, 0, 0, 0, 0}

{"DCOUNT", Lfunct, 2, 2, Fovlap, 0}

{"DEACTIVATEKEY", Lbos, 0, 0, 0, 0}

{"DEBUG", Lbos, 0, 0, 0, 0}

{"DECLARE", Lbos, 0, 0, 0, 0}

{"DEFFUN", Lbos, 0, 0, 0, 0}

{"DEL", Lbos, 0, 0, 0, 0}

{"DELETE", Lbfunc, 2, 4, 0, 0}

{"DELETELIST", Lbos, 0, 0, 0, 0}

{"DELETEU", Lbos, 0, 0, 0, 0}

{"DESCRINFO", Lfunct, 2, 2, 0, 0}

{"DIAGNOSTICS", Lfunct, 1, 2, 0, 0}

{"DIGEST", Lfunct, 4, 4, 0, LVA_4}

{"DIM", Lbos, 0, 0, 0, 0}

{"DIMENSION", Lbos, 0, 0, 0, 0}

{"DISABLEDEC", Lbos, 0, 0, 0, 0}

{"DISPLAY", Lbos, 0, 0, 0, 0}

{"DIV", Lfunct, 2, 2, 0, 0}

{"DIVS", Lfunct, 2, 2, 0, 0}

{"DO", Lflag, 0, 0, 0, 0}

{"DOWNCASE", Lfunct, 1, 1, 0, 0}


38

{"DQUOTE", Lfunct, 1, 1, 0, 0}

{"DTX", Lfunct, 1, 2, 0, 0}

{"EBCDIC", Lfunct, 1, 1, 0, 0}

{"ECHO", Lbos, 0, 0, 0, 0}

{"ELSE", Lelse, 0, 0, 0, 0}

{"ENABLEDEC", Lbos, 0, 0, 0, 0}

{"ENCODE", Lfunct, 6, 6, 0, LVA_5}

{"ENCRYPT", Lfunct, 11, 11, 0, LVA_10}

{"END", Lend, 0, 0, 0, 0}

{"ENTER", Lbos, 0, 0, 0, 0}

{"EOF", Lfunct, 0, 0, 0, 0}

{"EQ", 0, 0, 0, 0, 0}

{"EQS", Lfunct, 2, 2, 0, 0}

{"EQU", Lbos, 0, 0, 0, 0}

{"EQUATE", Lbos, 0, 0, 0, 0}

{"EREPLACE", Lfunct, 3, 5, 0, 0}

{"ERRMSG", Lbos, 0, 0, 0, 0}

{"ERROR", Lerror, 0, 0, 0, 0}

{"EXCHANGE", Lfunct, 0, 0, 0, 0}

{"EXEC", Lbos, 0, 0, 0, 0}

{"EXECUTE", Lbos, 0, 0, 0, 0}

{"EXIT", Lbos, 0, 0, 0, 0}

{"EXP", Lfunct, 1, 1, 0, 0}

{"EXTRACT", Lfunct, 2, 4, 0, 0}

{"FADD", Lfunct, 2, 2, 0, 0}

{"FDIV", Lfunct, 2, 2, 0, 0}

{"FFIX", Lfunct, 1, 1, 0, 0}

{"FFLT", Lfunct, 1, 1, 0, 0}

{"FIELD", Lfunct, 3, 4, Fone, 0}

{"FIELDS", Lfunct, 3, 4, Fone, 0}

{"FIELDSTORE", Lfunct, 5, 5, 0, 0}

{"FILEINFO", Lfunct, 2, 2, 0, 0}

{"FILELOCK", Lbos, 0, 0, 0, 0}

{"FILEUNLOCK", Lbos, 0, 0, 0, 0}

{"FIND", Lbos, 0, 0, 0, 0}

{"FINDSTR", Lbos, 0, 0, 0, 0}

{"FIX", Lfunct, 1, 3, 0, 0}

{"FLUSH", Lbos, 0, 0, 0, 0}


39

{"FMT", Lfunct, 2, 2, 0, 0}

{"FMTDP", Lfunct, 2, 3, Fnull, 0}

{"FMTS", Lfunct, 2, 2, 0, 0}

{"FMTSDP", Lfunct, 2, 3, Fnull, 0}

{"FMUL", Lfunct, 2, 2, 0, 0}

{"FOLD", Lfunct, 2, 2, 0, 0}

{"FOLDDP", Lfunct, 2, 3, 0, 0}

{"FOOTING", Lbos, 0, 0, 0, 0}

{"FOR", Lbos, 0, 0, 0, 0}

{"FORMLIST", Lbos, 0, 0, 0, 0}

{"FROM", Lflag, 0, 0, 0, 0}

{"FSUB", Lfunct, 2, 2, 0, 0}

{"FUNCTION", Lbos, 0, 0, 0, 0}

{"GARBAGECOLLECT", Lbos, 0, 0, 0, 0}

{"GCI", Lflag, 0, 0, 0, 0}

{"GE", 0, 0, 0, 0, 0}

{"generateKey", Lfunct, 8, 8, 0, LVA_1|LVA_2}

{"GES", Lfunct, 2, 2, 0, 0}

{"GET", Lget, 0, 0, 0, 0}

{"getCipherSuite", Lfunct, 2, 2, 0, LVA_2}

{"GETCONVERTTERMEURO", Lfunct, 0, 0, 0, 0}

{"GETDIAGNOSTICS", Lfunct, 0, 0, 0, 0}

{"getHTTPDefault", Lfunct, 2, 2, 0, LVA_2}

{"GETLIST", Lbos, 0, 0, 0, 0}

{"GETLOCALE", Lfunct, 1, 1, 0, 0}

{"GETREM", Lfunct, 1, 1, 0, 0}

{"getResponseHeader", Lfunct, 3, 3, 0, LVA_3}

{"getSocketErrorMessage",Lfunct, 2, 2, 0, LVA_2}

{"getSocketInformation",Lfunct, 3, 3, 0, LVA_3}

{"getSocketMap", Lfunct, 2, 2, 0, LVA_2}

{"getSocketOptions", Lfunct, 2, 2, 0, LVA_2}

{"GETSQLNULL", Lfunct, 0, 0, 0, 0}

{"GETSYSTEMEURO", Lfunct, 0, 0, 0, 0}

{"GETTERMEURO", Lfunct, 0, 0, 0, 0}

{"GETX", Lbos, 0, 0, 0, 0}

{"GO", Lbflag, 0, 0, 0, 0}

{"GOSUB", Lbflag, 0, 0, 0, 0}

{"GOTO", Lbflag, 0, 0, 0, 0}


40

{"GROUP", Lfunct, 3, 4, Fone, 0}

{"GROUPSTORE", Lbos, 0, 0, 0, 0}

{"GT", 0, 0, 0, 0, 0}

{"GTS", Lfunct, 2, 2, 0, 0}

{"HEADING", Lbos, 0, 0, 0, 0}

{"HEADINGE", Lbos, 0, 0, 0, 0}

{"HEADINGN", Lbos, 0, 0, 0, 0}

{"HUSH", Lbos, 0, 0, 0, 0}

{"ICHECK", Lfunct, 2, 4, Fnego, 0}

{"ICONV", Lfunct, 2, 2, 0, 0}

{"ICONVS", Lfunct, 2, 2, 0, 0}

{"IF", 0, 0, 0, 0, 0}

{"IFS", Lfunct, 3, 3, 0, 0}

{"ILPROMPT", Lfunct, 1, 1, 0, 0}

{"IN", Lflag, 0, 0, 0, 0}

{"INDEX", Lfunct, 3, 3, Fovlap, 0}

{"INDEXS", Lfunct, 3, 3, 0, 0}

{"INDICES", Lfunct, 1, 2, Fnull, 0}

{"initSecureServerSocket",Lfunct, 5, 5, 0, LVA_4}

{"initServerSocket", Lfunct, 4, 4, 0, LVA_4}

{"INMAT", Lfunct, 0, 0, 0, 0}

{"INPUT", Lbflag, 0, 0, 0, 0}

{"INPUTCLEAR", Lbos, 0, 0, 0, 0}

{"INPUTDISP", Lbos, 0, 0, 0, 0}

{"INPUTDP", Lbflag, 0, 0, 0, 0}

{"INPUTERR", Lbos, 0, 0, 0, 0}

{"INPUTIF", Lbos, 0, 0, 0, 0}

{"INPUTNULL", Lbos, 0, 0, 0, 0}

{"INPUTTRAP", Lbos, 0, 0, 0, 0}

{"INS", Lbos, 0, 0, 0, 0}

{"INSERT", Lfunct, 3, 5, Fsemi, 0}

{"INT", Lfunct, 1, 1, 0, 0}

{"ISNULL", Lfunct, 1, 1, 0, 0}

{"ISNULLS", Lfunct, 1, 1, 0, 0}

{"ISOLATION", Lflag, 0, 0, 0, 0}

{"ITYPE", Lfunct, 1, 1, 0, 0}

{"KEY", Lflag, 0, 0, 0, 0}

{"KEYEDIT", Lbos, 0, 0, 0, 0}


41

{"KEYEXIT", Lbos, 0, 0, 0, 0}

{"KEYIN", Lfunct, 0, 0, 0, 0}

{"KEYTRAP", Lbos, 0, 0, 0, 0}

{"LE", 0, 0, 0, 0, 0}

{"LEFT", Lfunct, 2, 2, 0, 0}

{"LEN", Lfunct, 1, 1, 0, 0}

{"LENDP", Lfunct, 1, 2, Fnull, 0}

{"LENS", Lfunct, 1, 1, 0, 0}

{"LENSDP", Lfunct, 1, 2, Fnull, 0}

{"LES", Lfunct, 2, 2, 0, 0}

{"LET", Lbos, 0, 0, 0, 0}

{"LEVEL", Lflag, 0, 0, 0, 0}

{"LIT", Lflag, 0, 0, 0, 0}

{"LITERALLY", Lflag, 0, 0, 0, 0}

{"LN", Lfunct, 1, 1, 0, 0}

{"loadSecurityContext", Lfunct, 3, 3, 0, LVA_1}

{"LOCALEINFO", Lfunct, 1, 1, 0, 0}

{"LOCATE", Lloc, 0, 0, 0, 0}

{"LOCK", Lbos, 0, 0, 0, 0}

{"LOCKED", Llock, 0, 0, 0, 0}

{"LOOP", Lbos, 0, 0, 0, 0}

{"LOWER", Lfunct, 1, 1, 0, 0}

{"LPTR", Lflag, 0, 0, 0, 0}

{"LT", 0, 0, 0, 0, 0}

{"LTS", Lfunct, 2, 2, 0, 0}

{"MAT", Lbflag, 0, 0, 0, 0}

{"MATBUILD", Lbos, 0, 0, 0, 0}

{"MATCH", 0, 0, 0, 0, 0}

{"MATCHES", 0, 0, 0, 0, 0}

{"MATCHFIELD", Lfunct, 3, 3, 0, 0}

{"MATPARSE", Lbos, 0, 0, 0, 0}

{"MATREAD", Lbos, 0, 0, 0, 0}

{"MATREADL", Lbos, 0, 0, 0, 0}

{"MATREADU", Lbos, 0, 0, 0, 0}

{"MATWRITE", Lbos, 0, 0, 0, 0}

{"MATWRITEU", Lbos, 0, 0, 0, 0}

{"MAXIMUM", Lfunct, 1, 1, 0, 0}

{"MESSAGE", Lbos, 0, 0, 0, 0}


42

{"MINIMUM", Lfunct, 1, 1, 0, 0}

{"MOD", Lfunct, 2, 2, 0, 0}

{"MODS", Lfunct, 2, 2, 0, 0}

{"MTU", Lflag, 0, 0, 0, 0}

{"MULS", Lfunct, 2, 2, 0, 0}

{"NAP", Lbos, 0, 0, 0, 0}

{"NE", 0, 0, 0, 0, 0}

{"NEG", Lfunct, 1, 1, 0, 0}

{"NEGS", Lfunct, 1, 1, 0, 0}

{"NES", Lfunct, 2, 2, 0, 0}

{"NEXT", Lnext, 0, 0, 0, 0}

{"NO.ISOLATION", Lflag, 0, 0, 0, 0}

{"NOBUF", Lbos, 0, 0, 0, 0}

{"NOT", Lfunct, 1, 1, 0, 0}

{"NOTS", Lfunct, 1, 1, 0, 0}

{"NULL", Lbos, 0, 0, 0, 0}

{"NUM", Lfunct, 1, 1, 0, 0}

{"NUMS", Lfunct, 1, 1, 0, 0}

{"OCONV", Lfunct, 2, 2, 0, 0}

{"OCONVS", Lfunct, 2, 2, 0, 0}

{"OFF", Lflag, 0, 0, 0, 0}

{"ON", Lbflag, 0, 0, 0, 0}

{"OPEN", Lbos, 0, 0, 0, 0}

{"OPENCHECK", Lbos, 0, 0, 0, 0}

{"OPENDEV", Lbos, 0, 0, 0, 0}

{"OPENPATH", Lbos, 0, 0, 0, 0}

{"openSecureSocket", Lfunct, 6, 6, 0, LVA_5}

{"OPENSEQ", Lbos, 0, 0, 0, 0}

{"openSocket", Lfunct, 5, 5, 0, LVA_5}

{"OpenXMLData", Lfunct, 3, 3, 0, LVA_3}

{"OR", 0, 0, 0, 0, 0}

{"ORS", Lfunct, 2, 2, 0, 0}

{"OUT", Lflag, 0, 0, 0, 0}

{"PAGE", Lbos, 0, 0, 0, 0}

{"PASSLIST", Lflag, 0, 0, 0, 0}

{"PCDRIVER", Lbos, 0, 0, 0, 0}

{"PERFORM", Lexec, 0, 0, 0, 0}

{"PRECISION", Lbos, 0, 0, 0, 0}


43

{"PrepareXML", Lfunct, 2, 2, 0, LVA_2}

{"PRINT", Lbos, 0, 0, 0, 0}

{"PRINTER", Lbos, 0, 0, 0, 0}

{"PRINTERIO", Lbos, 0, 0, 0, 0}

{"PRINTERR", Lprntr, 0, 0, 0, 0}

{"PROCREAD", Lbos, 0, 0, 0, 0}

{"PROCWRITE", Lbos, 0, 0, 0, 0}

{"PROG", Lbos, 0, 0, 0, 0}

{"PROGRAM", Lbos, 0, 0, 0, 0}

{"PROMPT", Lbos, 0, 0, 0, 0}

{"protocolLogging", Lfunct, 3, 3, 0, 0}

{"PWR", Lfunct, 2, 2, 0, 0}

{"QUOTE", Lfunct, 1, 1, 0, 0}

{"RAISE", Lfunct, 1, 1, 0, 0}

{"RANDOMIZE", Lbos, 0, 0, 0, 0}

{"READ", Lbos, 0, 0, 0, 0}

{"READ.COMMITTED", Lflag, 0, 0, 0, 0}

{"READ.UNCOMMITTED", Lflag, 0, 0, 0, 0}

{"READBLK", Lbos, 0, 0, 0, 0}

{"READL", Lbos, 0, 0, 0, 0}

{"READLIST", Lbos, 0, 0, 0, 0}

{"READNEXT", Lbos, 0, 0, 0, 0}

{"READSEQ", Lbos, 0, 0, 0, 0}

{"readSocket", Lfunct, 6, 6, 0, LVA_2|LVA_6}

{"READT", Lbos, 0, 0, 0, 0}

{"READU", Lbos, 0, 0, 0, 0}

{"READV", Lbos, 0, 0, 0, 0}

{"READVL", Lbos, 0, 0, 0, 0}

{"READVU", Lbos, 0, 0, 0, 0}

{"ReadXMLData", Lfunct, 2, 2, 0, LVA_2}

{"REAL", Lfunct, 1, 1, 0, 0}

{"RECIO", Lfunct, 2, 4, 0, 0}

{"RECORDLOCKED", Lfunct, 2, 2, 0, 0}

{"RECORDLOCKL", Lbos, 0, 0, 0, 0}

{"RECORDLOCKU", Lbos, 0, 0, 0, 0}

{"RELEASE", Lbos, 0, 0, 0, 0}

{"ReleaseXML", Lfunct, 1, 1, 0, 0}

{"REM", Lfunct, 2, 2, 0, 0}


44

{"REMOVE", Lbfunc, 2, 2, 0, 0}

{"REPEAT", Lloop, 0, 0, 0, 0}

{"REPEATABLE.READ", Lflag, 0, 0, 0, 0}

{"REPLACE", Lfunct, 3, 5, Fsemi, 0}

{"RESET", Lflag, 0, 0, 0, 0}

{"RETURN", Lsub, 0, 0, 0, 0}

{"RETURNING", Lflag, 0, 0, 0, 0}

{"REUSE", Lfunct, 1, 1, 0, 0}

{"REVREMOVE", Lbos, 0, 0, 0, 0}

{"REWIND", Lbos, 0, 0, 0, 0}

{"RIGHT", Lfunct, 2, 2, 0, 0}

{"RND", Lfunct, 1, 1, 0, 0}

{"ROLLBACK", Lbos, 0, 0, 0, 0}

{"RPC.CALL", Lfunct, 0, 0, 0, 0}

{"RPC.CONNECT", Lfunct, 2, 2, 0, 0}

{"RPC.DISCONNECT", Lfunct, 1, 1, 0, 0}

{"RQM", Lbos, 0, 0, 0, 0}

{"RTNLIST", Lflag, 0, 0, 0, 0}

{"SADD", Lfunct, 2, 2, 0, 0}

{"saveSecurityContext", Lfunct, 3, 3, 0, 0}

{"SCMP", Lfunct, 2, 2, 0, 0}

{"SDIV", Lfunct, 2, 3, Fnego, 0}

{"SEEK", Lseek, 0, 0, 0, 0}

{"SELECT", Lbflag, 0, 0, 0, 0}

{"SELECTE", Lbos, 0, 0, 0, 0}

{"SELECTINDEX", Lbos, 0, 0, 0, 0}

{"SELECTINFO", Lfunct, 2, 2, 0, 0}

{"SELECTN", Lbos, 0, 0, 0, 0}

{"SELECTV", Lbos, 0, 0, 0, 0}

{"SEND", Lbos, 0, 0, 0, 0}

{"SENTENCE", Lfunct, 0, 0, 0, 0}

{"SEQ", Lfunct, 1, 1, Fseq, 0}

{"SEQS", Lfunct, 1, 1, 0, 0}

{"SEQSUM", Lfunct, 1, 1, 0, 0}

{"SERIALIZABLE", Lflag, 0, 0, 0, 0}

{"SET", Lbos, 0, 0, 0, 0}

{"setAuthenticationDepth",Lfunct, 3, 3, 0, 0}

{"setCipherSuite", Lfunct, 2, 2, 0, 0}


45

{"setClientAuthentication", Lfunct, 2, 2, 0, 0}

{"SETCONVERTTERMEURO", Lfunct, 1, 1, 0, 0}

{"SETDIAGNOSTICS", Lfunct, 1, 3, Fnull, 0}

{"setHTTPDefault", Lfunct, 2, 2, 0, 0}

{"SETLOCALE", Lfunct, 2, 2, 0, 0}

{"setPrivateKey", Lfunct, 6, 6, 0, 0}

{"setRandomSeed", Lfunct, 4, 4, 0, 0}

{"SETREM", Lbos, 0, 0, 0, 0}

{"setRequestHeader", Lfunct, 3, 3, 0, 0}

{"setSocketMap", Lfunct, 1, 1, 0, 0}

{"setSocketOptions", Lfunct, 2, 2, 0, 0}

{"SETSYSTEMEURO", Lfunct, 1, 1, 0, 0}

{"SETTERMEURO", Lfunct, 1, 1, 0, 0}

{"SETTING", Lflag, 0, 0, 0, 0}

{"showSecurityContext", Lfunct, 2, 2, 0, 0}

{"SIGNATURE", Lfunct, 10, 10, 0, LVA_9}

{"SIN", Lfunct, 1, 1, Ftrig, 0}

{"SINH", Lfunct, 1, 1, Ftrig, 0}

{"SLEEP", Lbos, 0, 0, 0, 0}

{"SMUL", Lfunct, 2, 2, 0, 0}

{"SOAPCreateRequest", Lfunct, 3, 3, 0, LVA_3}

{"SOAPCreateSecureRequest", Lfunct, 4, 4, 0, LVA_4}

{"SOAPGetDefault", Lfunct, 2, 2, 0, LVA_2}

{"SOAPGetFault", Lfunct, 2, 2, 0, LVA_2}

{"SOAPGetResponseHeader",Lfunct, 3, 3, 0, LVA_3}

{"SOAPRequestWrite", Lfunct, 3, 3, 0, LVA_2}

{"SOAPSetDefault", Lfunct, 2, 2, 0, 0}

{"SOAPSetParameters", Lfunct, 4, 4, 0, 0}

{"SOAPSetRequestBody", Lfunct, 2, 2, 0, 0}

{"SOAPSetRequestContent",Lfunct, 3, 3, 0, 0}

{"SOAPSetRequestHeader",Lfunct, 2, 2, 0, 0}

{"SOAPSubmitRequest", Lfunct, 5, 5, 0, LVA_3|LVA_4|LVA_5}

{"SOUNDEX", Lfunct, 1, 1, 0, 0}

{"SPACE", Lfunct, 1, 1, 0, 0}

{"SPACES", Lfunct, 1, 1, 0, 0}

{"SPLICE", Lfunct, 3, 3, 0, 0}

{"SQLALLOCCONNECT", Lfunct, 2, 2, 0, LVA_2}

{"SQLALLOCENV", Lfunct, 1, 1, 0, LVA_1}


46

{"SQLALLOCSTMT", Lfunct, 2, 2, 0, LVA_2}

{"SQLBINDCOL", Lfunct, 4, 4, 0, LVA_4}

{"SQLBINDPARAMETER", Lfunct, 7, 8, Fone, LVA_7}

{"SQLCANCEL", Lfunct, 1, 1, 0, 0}

{"SQLCMP", Lfunct, 3, 3, Fnull, 0}

{"SQLCOLATTRIBUTES", Lfunct, 5, 5, 0, LVA_4|LVA_5}

{"SQLCOLUMNS", Lfunct, 5, 5, 0, 0}

{"SQLCONNECT", Lfunct, 4, 4, 0, 0}

{"SQLDESCRIBECOL", Lfunct, 7, 7, 0, LVA_3|LVA_4|LVA_5|LVA_6|LVA_7}

{"SQLDISCONNECT", Lfunct, 1, 1, 0, 0}

{"SQLERROR", Lfunct, 6, 6, 0, LVA_4|LVA_5|LVA_6}

{"SQLEXECDIRECT", Lfunct, 2, 2, 0, 0}

{"SQLEXECUTE", Lfunct, 1, 1, 0, 0}

{"SQLFETCH", Lfunct, 1, 1, 0, 0}

{"SQLFREECONNECT", Lfunct, 1, 1, 0, 0}

{"SQLFREEENV", Lfunct, 1, 1, 0, 0}

{"SQLFREESTMT", Lfunct, 2, 2, 0, 0}

{"SQLGETCURSORNAME", Lfunct, 2, 2, 0, LVA_2}

{"SQLGETINFO", Lfunct, 3, 3, 0, LVA_3}

{"SQLGETTYPEINFO", Lfunct, 2, 2, 0, 0}

{"SQLNUMPARAMS", Lfunct, 2, 2, 0, LVA_2}

{"SQLNUMRESULTCOLS", Lfunct, 2, 2, 0, LVA_2}

{"SQLPARAMOPTIONS", Lfunct, 3, 3, 0, LVA_3}

{"SQLPREPARE", Lfunct, 2, 2, 0, 0}

{"SQLROWCOUNT", Lfunct, 2, 2, 0, LVA_2}

{"SQLSETCONNECTOPTION", Lfunct, 3, 3, 0, 0}

{"SQLSETCURSORNAME", Lfunct, 2, 2, 0, 0}

{"SQLSETPARAM", Lfunct, 7, 8, Fone, LVA_7}

{"SQLSPECIALCOLUMNS", Lfunct, 7, 7, 0, 0}

{"SQLSTATISTICS", Lfunct, 6, 6, 0, 0}

{"SQLTABLES", Lfunct, 5, 5, 0, 0}

{"SQLTRANSACT", Lfunct, 3, 3, 0, 0}

{"SQRT", Lfunct, 1, 1, 0, 0}

{"SQUOTE", Lfunct, 1, 1, 0, 0}

{"SSELECT", Lbos, 0, 0, 0, 0}

{"SSELECTN", Lbos, 0, 0, 0, 0}

{"SSELECTV", Lbos, 0, 0, 0, 0}

{"SSUB", Lfunct, 2, 2, 0, 0}


47

{"START", Lflag, 0, 0, 0, 0}

{"STATUS", Lstat, 0, 0, 0, 0}

{"STEP", Lflag, 0, 0, 0, 0}

{"STOP", Lbos, 0, 0, 0, 0}

{"STOPE", Lbos, 0, 0, 0, 0}

{"STOPM", Lbos, 0, 0, 0, 0}

{"STORAGE", Lbos, 0, 0, 0, 0}

{"STR", Lfunct, 2, 2, 0, 0}

{"STRS", Lfunct, 2, 2, 0, 0}

{"SUB", Lsub, 0, 0, 0, 0}

{"submitRequest", Lfunct, 6, 6, 0, LVA_4|LVA_5|LVA_6}

{"SUBR", Lfunct, 0, 0, 0, 0}

{"SUBROUTINE", Lsub, 0, 0, 0, 0}

{"SUBS", Lfunct, 2, 2, 0, 0}

{"SUBSTRINGS", Lfunct, 3, 3, 0, 0}

{"SUM", Lfunct, 1, 1, 0, 0}

{"SUMMATION", Lfunct, 1, 1, 0, 0}

{"SWAP", Lbos, 2, 2, 0, 0}

{"SYSTEM", Lfunct, 1, 2, 0, 0}

{"TABSTOP", Lbos, 0, 0, 0, 0}

{"TAN", Lfunct, 1, 1, Ftrig, 0}

{"TANH", Lfunct, 1, 1, Ftrig, 0}

{"TERMINFO", Lfunct, 1, 1, 0, 0}

{"TESTDIAGNOSTICS", Lfunct, 0, 0, 0, 0}

{"THEN", Lthen, 0, 0, 0, 0}

{"TIME", Lfunct, 0, 0, 0, 0}

{"TIMEDATE", Lfunct, 0, 0, 0, 0}

{"TIMEOUT", Lbos, 0, 0, 0, 0}

{"TO", Lflag, 0, 0, 0, 0}

{"TPARM", Lfunct, 1, 9, 0, 0}

{"TPRINT", Lbos, 0, 0, 0, 0}

{"TRANS", Lfunct, 4, 4, 0, 0}

{"TRANSACTION", Lbflag, 0, 0, 0, 0}

{"TRIM", Lfunct, 1, 3, 0, 0}

{"TRIMB", Lfunct, 1, 1, 0, 0}

{"TRIMBS", Lfunct, 1, 1, 0, 0}

{"TRIMF", Lfunct, 1, 1, 0, 0}

{"TRIMFS", Lfunct, 1, 1, 0, 0}


48

{"TRIMS", Lfunct, 1, 1, 0, 0}

{"TTYCTL", Lbos, 0, 0, 0, 0}

{"TTYGET", Lbos, 0, 0, 0, 0}

{"TTYSET", Lbos, 0, 0, 0, 0}

{"UNASSIGNED", Lfunct, 1, 1, 0, 0}

{"UNICHAR", Lfunct, 1, 1, 0, 0}

{"UNICHARS", Lfunct, 1, 1, 0, 0}

{"UNISEQ", Lfunct, 1, 1, 0, 0}

{"UNISEQS", Lfunct, 1, 1, 0, 0}

{"UNIT", Lfunct, 0, 0, 0, 0}

{"UNLOCK", Lbos, 0, 0, 0, 0}

{"UNTIL", Lloop, 0, 0, 0, 0}

{"UPCASE", Lfunct, 1, 1, 0, 0}

{"UPRINT", Lbos, 0, 0, 0, 0}

{"USING", Lflag, 0, 0, 0, 0}

{"WAITING", Lflag, 0, 0, 0, 0}

{"WEOF", Lbos, 0, 0, 0, 0}

{"WEOFSEQ", Lbos, 0, 0, 0, 0}

{"WHILE", Lloop, 0, 0, 0, 0}

{"WORDSIZE", Lbos, 0, 0, 0, 0}

{"WORK", Lflag, 0, 0, 0, 0}

{"WRITE", Lbos, 0, 0, 0, 0}

{"WRITEBLK", Lbos, 0, 0, 0, 0}

{"WRITELIST", Lbos, 0, 0, 0, 0}

{"WRITESEQ", Lbos, 0, 0, 0, 0}

{"WRITESEQF", Lbos, 0, 0, 0, 0}

{"writeSocket", Lfunct, 5, 5, 0, LVA_5}

{"WRITET", Lbos, 0, 0, 0, 0}

{"WRITEU", Lbos, 0, 0, 0, 0}

{"WRITEV", Lbos, 0, 0, 0, 0}

{"WRITEVU", Lbos, 0, 0, 0, 0}

{"XDOMAddChild", Lfunct, 5, 5, 0, 0}

{"XDOMAppend", Lfunct, 5, 5, 0, 0}

{"XDOMClone", Lfunct, 3, 3, 0, LVA_2}

{"XDOMClose", Lfunct, 1, 1, 0, 0}

{"XDOMCreateNode", Lfunct, 5, 5, 0, LVA_5}

{"XDOMCreateRoot", Lfunct, 1, 2, 0, LVA_1}

{"XDOMEvaluate", Lfunct, 4, 4, 0, LVA_4}


49

{"XDOMGetAttribute", Lfunct, 3, 3, 0, LVA_3}

{"XDOMGetNodeName", Lfunct, 2, 2, 0, LVA_2}

{"XDOMGetNodeType", Lfunct, 2, 2, 0, LVA_2}

{"XDOMGetNodeValue", Lfunct, 2, 2, 0, LVA_2}

{"XDOMGetOwnerDocument",Lfunct, 2, 2, 0, LVA_2}

{"XDOMGetUserData", Lfunct, 2, 2, 0, LVA_2}

{"XDOMImportNode", Lfunct, 4, 4, 0, LVA_4}

{"XDOMInsert", Lfunct, 5, 5, 0, 0}

{"XDOMLocate", Lfunct, 4, 4, 0, LVA_4}

{"XDOMLocateNode", Lfunct, 5, 5, 0, LVA_5}

{"XDOMOpen", Lfunct, 3, 3, 0, LVA_3}

{"XDOMRemove", Lfunct, 5, 5, 0, LVA_5}

{"XDOMReplace", Lfunct, 5, 5, 0, 0}

{"XDOMSetNodeValue", Lfunct, 2, 2, 0, 0}

{"XDOMSetUserData", Lfunct, 2, 2, 0, 0}

{"XDOMTransform", Lfunct, 4, 5, 0, LVA_4}

{"XDOMValidate", Lfunct, 4, 5, 0, 0}

{"XDOMValidateDom", Lfunct, 3, 4, 0, 0}

{"XDOMWrite", Lfunct, 3, 4, 0, LVA_2}

{"XLATE", Lfunct, 4, 4, 0, 0}

{"XMAPAppendRec", Lfunct, 3, 3, 0, 0}

{"XMAPClose", Lfunct, 1, 1, 0, 0}

{"XMAPCreate", Lfunct, 3, 3, 0, LVA_3}

{"XMAPGetInfo", Lfunct, 2, 2, 0, LVA_2}

{"XMAPOpen", Lfunct, 5, 5, 0, LVA_5}

{"XMAPReadNext", Lfunct, 3, 3, 0, LVA_3}

{"XMAPSetOption", Lfunct, 3, 3, 0, 0}

{"XMAPToXMLDoc", Lfunct, 3, 4, 0, LVA_2}

{"XMLERROR", Lfunct, 1, 1, 0, LVA_1}

{"XMLExecute", Lfunct, 4, 4, 0, LVA_3|LVA_4}

{"XMLGetError", Lfunct, 2, 2, 0, LVA_1|LVA_2}

{"XMLGetOptions", Lfunct, 1, 2, 0, LVA_1}

{"XMLGetOptionValue", Lfunct, 2, 2, 0, LVA_1}

{"XMLSetOptions", Lfunct, 1, 1, 0, 0, "Since UV 10.3"}

{"XTD", Lfunct, 1, 1, 0, 0}

u2 basic developer toolkit user guide dbtools... · chapter 4: the u2 resource view ... you can...

Documents