Home
IBM Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
LotusScript® Language
Welcome to the LotusScript® Language section of Domino® Designer Help.
Data Types, Constants, and Variables
This chapter provides information about LotusScript® constants and variables and the data types of the values that they can represent.
Constants in LotusScript®
A constant names a location in memory that contains a value that is known at compile time and cannot be changed while the application is running. In less formal terms, a constant is a named fixed value. Constants are defined in the following ways:
Product-specific constants
Individual IBM® software applications may provide additional constants that you can use by including the file in which they are defined in your application with the %Include directive. A product may also provide internally defined constants that are automatically available to your application. For more information, see the product documentation.

IBM Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
- Accessibility and keyboard shortcuts
  Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.
- Application Design
  Welcome to the Application Design section of Domino® Designer Help.
- Application Management
  Welcome to the Application Management section of Domino® Designer Help.
- Domino® Query Language
  Domino Query Language (DQL) is a facility running in Domino core allowing for a terse shorthand syntax for finding documents according to a wide variety of complexity of terms. It leverages existing design elements without the need to write detailed code to access them.
- Composite Applications - Design and Management
  Composite applications are a key element in a service-oriented architecture (SOA) and contextual collaboration strategy. The ability to create and edit composite applications lets you easily integrate different types of components and technologies.
- DB2® Access views
  Domino® Designer includes two types of design elements to assist you in managing data contained in DB2® enabled Notes® databases:
- Programming Overview and User Interface
  This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
- Formula Language
  This section documents the formula language.
- LotusScript® Language
  Welcome to the LotusScript® Language section of Domino® Designer Help.
  - Introduction to LotusScript®
    This chapter introduces LotusScript® and describes, in general terms, how to use the script editor to write and modify scripts, how to compile scripts, and how to use the debugger to locate problems in the logic of your applications.
  - Script and Statement Construction Rules
    This chapter describes the rules for writing the basic elements of a script in the LotusScript® language.
  - Data Types, Constants, and Variables
    This chapter provides information about LotusScript® constants and variables and the data types of the values that they can represent.
    - Summary of LotusScript® data types
      LotusScript® recognizes the following scalar (numeric and string) data types:
    - Data type conversion
      LotusScript® implicitly converts data from one type to another in the following situations.
    - Explicit data type conversion
      LotusScript® provides several built-in functions for explicitly converting a value's data type. These functions include CBool, CByte, CCur, CDat, CDbl, CInt, CLng, CSng, CStr, and CVar.
    - Automatic data type conversion
      LotusScript® can automatically convert values from one data type to another. Automatic, or implicit data type conversion happens when:
    - Constants and Variables
      A LotusScript® application can manipulate data of several types through the use of constants and variables. Constants andvariables are identifiers that name locations in memory containing data of one or another of the types that LotusScript recognizes. Constants differ from variables in that the value that a constant represents must be known at compile time and can't be changed -- it must remain constant -- while the application is running, while a variable can refer to a value (or a set of values) that can change while the application is running.
    - Scope of declarations
      Scope is the context in which a variable, procedure, class, or type is declared. Scope affects the accessibility of an item's value outside that context. For example, variables declared within a procedure are typically not available outside of the scope of that procedure.
    - Constants in LotusScript®
      A constant names a location in memory that contains a value that is known at compile time and cannot be changed while the application is running. In less formal terms, a constant is a named fixed value. Constants are defined in the following ways:
      - Built-in constants
        LotusScript® provides several built-in constants that you can use in your scripts. LotusScript predefines other constants in the file LSCONST.LSS. To include this in your scripts, use the %Include directive.
      - Constants defined in LSCONST.LSS
        LotusScript® provides a set of constants that you can use in place of numeric arguments in certain LotusScript statements, such as MessageBox:
      - Constants defined in LSPRVAL.LSS
        LotusScript® provides a set of constants that you can use to get information about a running thread. The values of the constants are defined in LSPRVAL.LSS, which is automatically included through LSCONST.LSS.
      - Product-specific constants
        Individual IBM® software applications may provide additional constants that you can use by including the file in which they are defined in your application with the %Include directive. A product may also provide internally defined constants that are automatically available to your application. For more information, see the product documentation.
      - User-defined constants
        You can define your own constants within a module or a procedure, as long as the constants are the scalar data types that LotusScript® recognizes. Use the following syntax to define a constant:
    - Variables
      A variable names an area of storage whose value can change during execution of an application.
    - Arrays
      An array is a named collection of elements of the same data type, where each element can be accessed individually by its position within the collection. A LotusScript® array can have a maximum of eight dimensions.
    - Lists
      A list is a one-dimensional collection of elements of the same data type. You can change the size of a list at any time while the application is running and LotusScript® does not allocate any storage space at compile time for the elements of a list. Lists automatically shrink or grow when elements are deleted from or added to them. You access each element in a list by a unique String value, called a list tag.
    - Variants
      Variant is a special data type: variables of type Variant can hold values of any of the following data types that LotusScript® recognizes, except for user-defined data types:
  - Expressions and Operators
    This chapter describes the set of LotusScript® operators, how they may be combined with operands to form expressions, and how those expressions are evaluated.
  - Procedures: Functions, Subs, and Properties
  - File Handling
    This chapter describes file handling in the LotusScript® language.
  - Error Processing
    This chapter describes error processing in the LotusScript® language.
  - User-Defined Data Types and Classes
    This chapter describes two kinds of custom data structures that you can define in LotusScript®. Each can hold data of different types in a single data structure.
  - Managing Flow in Scripts
    The flow of execution of a script generally follows the sequence of statements in the script. This chapter describes the behavior of particular statements that alter the flow of execution.
  - Managing Asynchronous Web Agents in Domino®
    This chapter describes how to use multiple threads and synchronization to manage HTTP agents with Domino®.
  - Beyond Core LotusScript®
    This chapter discusses the role that LotusScript® plays with IBM® products, your operating environment, other programs, and interactive user applications.
  - LotusScript® Language Reference
    This chapter describes the use of statements, built-in functions, subs, data types, and directives in the LotusScript® language.
  - Language and Script Limits
    This appendix describes LotusScript® language limits of several kinds: for example, the legal ranges in data representation, the limits on numerical specifications within statements, and the maximum number of different kinds of elements that can be defined in a script.
  - Platform Differences
    The LotusScript® language and functionality on the UNIX™ platform, the Macintosh platform, and the OS/400® platform differ in various ways from the language and functionality described in the rest of this language reference. This appendix describes the differences.
  - LotusScript/REXX Integration
    This appendix provides an overview of REXX integration in the LotusScript® language.
  - LotusScript® Aliases
    This appendix lists the LotusScript® aliases and their equivalent text.
  - MIME Charset Names
  - Compile-time Error Messages
    This chapter describes the compile-time error messages in the LotusScript® language.
  - Run-time Error Messages
    This chapter describes the run-time error messages in the LotusScript® language.
- LotusScript/COM/OLE Classes
- Java/CORBA Classes
  This section documents the Java/CORBA classes.
- Lotus® Connectors
  Lotus® Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
- Javadoc™ for Domino® Designer related APIs
  As part of providing additional Java™ reference documentation, Domino® Designer ships with a help plugin that contains Javadoc™ for additional Domino Designer related APIs.

Product-specific constants

Individual IBM® software applications may provide additional constants that you can use by including the file in which they are defined in your application with the %Include directive. A product may also provide internally defined constants that are automatically available to your application. For more information, see the product documentation.