LANSA Glossary of terms
5250 Workstation |
A 5250 Workstation is a character-based display device used specifically with IBM i servers. |
Access Path |
An access path is an IBM i file concept. An access path defines the order in whichrecords are read from an IBM i physical or logical file. |
Access Route |
An access route is used to describe relationships between LANSA files. It is used by templates, Predetermined Joined Fields and LANSA Client. |
Action Bar |
An action bar is a style of user application interface. A detailed description can be found in the IBM SAA/CUA guidelines. |
Adaptive Server Anywhere |
See SQL Anywhere. |
AIX |
Operating system used by UNIX computers. |
API |
Application Programming Interface. |
Application Repository (LANSA Repository) |
The term Repository or Application Repository describes the application specific data entered by a customer, as in "a customer builds a repository for their business application". For example, fields, files, processes and functions are stored in the LANSA Repository. Each LANSA partition can be described as having its own application repository. |
APPC |
Advanced Peer-to-Peer Communications. A communication protocol used for the IBM i. |
Built-In Function |
Built-In Function. A standardized interface in LANSA for accessing external programs. |
C/C++ |
C is programming language. C++ is an object-oriented version on C. |
CASE |
Computer Aided Software Engineering |
CHEN E-R |
Chen Entity-Relationship is used in data modeling. |
Client |
See Visual LANSA Client Only, Local Client Only and Network Client Only. |
Commerce Edition |
Commerce Edition is a suite of Business-to-Business (B2B) and Business-to-Consumer (B2C) components that are built upon LANSA for the Web. |
Common Options |
The Common Options are a group of installation settings that are common to more than one product installation. Also see Visual LANSA Options. |
Communications Type |
The Communications Type specifies the communications methods used by your system when connecting to an IBM i or other server. |
Computer Name |
The Computer Name is the name assigned to your machine. This name is used as a unique identifier for connections to an IBM i host. |
Configuration |
A Configuration is used to store a specific group of settings for a LANSA Software installation. From V11.0 you no longer need to switch the current configuration to run a different LANSA installation and this means you could now run multiple post LANSA V10.x installations concurrently. |
CUA |
Common User Access. CUA is part of IBM's SAA strategy. CUA provides guidelines for the design of the application user interface. |
Data/Application Server |
The Data/Application Server is the machine used to host the LANSA Repository and application programs. |
Data Dictionary |
A data dictionary is an object used for storing fields, record formats and file definitions. |
Data Model |
A data model is a picture or representation of the information in an organization. |
Database |
A database is a collection of related files. |
Data Source |
The Data Source contains the tables for the database management system used by the Visual LANSA Repository. |
DBCS: |
Double Byte Character Set. |
Deployment Images |
The Deployment Images are a set of deployable versions of the LANSA Environment to support the deployment of LANSA Applications to end-user machines. These images are installed by default with a LANSA development environment. |
Development Languages |
Development Languages are the languages of the text that the Development Environment displays. For example, all the text on the login dialog is in the development language. You can install multiple languages if you want to be able to switch between them, e.g. French and English. Also see Partition Language. |
DLL |
Dynamic Link Library. |
e-Business Framework Wizard |
The e-Business Framework Wizard is a browser-based utility that allows you to quickly and easily customize the presentation of your LANSA Web applications. The e-Business Framework Wizard is installed at the partition level using Partition Initialization. |
Enable For Web |
In order to develop LANSA for the Web applications in a partition, you must enable the partition for Web development. Use the Enable for Web option when performing partition initialization. |
End-user |
An end-user executes or uses an application. |
English Development Language |
The English Development Language option will install English text and resource files. Also see Development Languages. |
Entity |
An entity is a data modeling term. It refers to a group of elements that belong together and are uniquely identified by a key or groups of keys. |
Exporting |
Exporting is the term used to describe the movement of information out of a LANSA partition for use in another partition. |
Feature |
The LANSA software is grouped into products and features. The list of LANSA features that can be installed is based upon the type of installation being performed. |
Field |
A field, in file terms, refers to a column in a table or a named group of values. |
File |
A file is a group of records. |
French Development Language |
The French Development Language option will install French text and resource files. Also see Development Languages. |
Function |
A function is a group of RDML commands that is compiled and executed by a user to manipulate the database in some way. |
GUI |
Graphical User Interface. GUI is a term commonly used to describe the Windows environment on personal computers or programmable workstations. |
Host Connection Information |
The Host Connection Information is used to specify the communications information (LU Name, user name, password, etc.) to allow your system to connect to a Master System. |
Host Monitor |
The Host Monitor is an integrated feature of the Visual LANSA IDE that connects a Master LANSA for iSeries system and the Slave Visual LANSA system. It is used to transfer data between the LANSA Repositories in the two systems. |
HPUX |
Operating system used by Hewlett Packard midrange computers. |
ILE |
Integrated Language Environment. A programming model used on the IBM i. |
Importing |
Importing is the term used to describe the movement of information into a LANSA partition from another partition. |
I/O Module |
An I/O Module is also known as an OAM or Object Access Module. It is a program created by LANSA to handle all input/output processing for a LANSA file. |
Independent LANSA System |
A LANSA System can be described as Independent if there are no other LANSA development systems that depend on the system, i.e. it has no slaves and it is not part of a distributed development model. |
Independent Server |
An Independent Server install includes an Independent LANSA System using a Server Database. |
Independent Workstation |
An Independent Workstation install includes an Independent LANSA System using a Workstation Database. |
Initialize Database |
The Initialization of a database involves the definition of the database files and loading of the current version of the LANSA software definitions. A newly installed LANSA database must be initialized before it can be used. |
Integrator Studio |
The LANSA Integrator Studio is an integrated set of applications including the SOAP Wizards, Visual XML Wizard, the Property Editor, XML Editor and XSL Compiler. Also see LANSA Integrator. |
Internet |
The Internet is a worldwide network of computers. Also referred to as the World Wide Web. |
Internet Explorer |
Internet Explorer (IE) is a Web browser that is shipped with the Windows operating system. You must use an IE browser for accessing the information on the LANSA CD-ROMs. |
Intranet |
An Intranet is an internal computer network using TCP/IP protocol. |
IIS |
Internet Information Services (IIS) is a Windows component for Web publishing. It is an installable feature shipped with the Windows 2000 operating system and later versions. |
IIS Plug-in |
The LANSA for the Web IIS Plug-in is an ISAPI-based Web serving technology that can be used to deploy LANSA applications using the Microsoft IIS Web Server. The IIS Plug-in is the component used to build the link between the Web Server and the Data/Application Server. |
IBM i Language Options |
The IBM i Language Options allow you to configure settings associated with the translation of data transferred between the IBM i and the workstation. |
Japanese Development Language |
The Japanese Development Language option will install Japanese text and resource files. Also see Development Languages. |
Java Runtime Environment (JRE) |
A Java Runtime Environment is required in order to support the execution of Java objects on a platform. The JRE includes the Java Virtual Machine (JVM) that executes the Java code. The JRE can be downloaded from the Web. |
Java Service Manager (Server) |
The LANSA Integrator Java Service Manager (JSM) allows developers to integrate Java programs with their existing LANSA or 3GL applications. The Java Service Manager provides a standardized interface for calling Java classes using Java service programs. Also see JSM Administrator, JSM Direct and JSM Instance. |
Java Service Manager Proxy (Server) |
The LANSA Integrator Java Service Manager Proxy server allows a proxy server to redirect the JSM server requests. |
Java Servlet |
The LANSA for the Web Java Servlet is a Java-based Web serving technology that can be used to deploy LANSA applications using a Java enabled Web Server such as WebSphere. The Java Servlet is the component used to build the link between the Web Server and the Data/Application Server. |
JSM Administrator |
The LANSA Integrator JSM Administrator is part of the JSM Server software that is used to set up and configure the JSM Server. |
JSM Direct |
The LANSA Integrator JSM Direct is part of the JSM Server software that supports the HTTP services. |
JSM Instance |
The LANSA Integrator JSM Instance is part of the JSM Server software that supports the Java Service instances. |
LANSA |
LANSA is an integrated family of highly productive design, development and maintenance products for multi-platform host and network applications. |
LANSA/AD |
LANSA Application Development tool. Now called LANSA for iSeries. |
LANSA Client |
LANSA Client is a PC-based, graphical query and reporting tool for accessing IBM i or Windows databases with the power and protection of the LANSA Repository and RDML. |
LANSA Database |
The LANSA Database consists of a group of files that support the LANSA System Definition data and the Application Repository data. |
LANSA for iSeries |
LANSA for iSeries allows you to rapidly develop online, batch and reporting applications for IBM i servers. LANSA's active object Repository and powerful RDML programming language combine to create a highly productive integrated development environment. |
LANSA for the Web |
LANSA for the Web allows you to build Web applications quickly and easily. It is an extension of the core LANSA integrated development environment (either Visual LANSA or LANSA for iSeries). LANSA for the Web applications can be deployed across a number of combinations of platforms including the IBM i, Windows, UNIX and Linux. |
LANSA for the Web Utilities |
The LANSA for the Web Utilities include the Web Administrator and Web Function Editor. |
LANSA Integrator |
LANSA Integrator enables integration of Application-to-Application (A2A) and Business-to-Business (B2B) transactions through XML and Java Services. |
LANSA Open |
LANSA Open (previously called LANSA/Server) is 'middleware' or software that facilitates the high-speed transfer of information and data between PC-based client applications and a server using the LANSA Repository. |
LANSA Open Core Files |
The LANSA Open Core Files must always be installed when LANSA Open is installed. |
LANSA Repository |
See Application Repository. |
LANSA System |
A LANSA System consists of the LANSA Software, the LANSA System Definition data, and the Application Repository data. A LANSA System can be a LANSA for iSeries system or a Visual LANSA System. A LANSA System can be defined as a Master LANSA System or Slave LANSA System. |
LANSA System Definition |
The LANSA System Definition describes the system specific data that is used by the LANSA software to define and support the development environment. The RDML commands, messages, templates, BIFs, are part of the system definition as well as information such as system owners, user authorities, machine date formats, etc. A LANSA System Definition is primarily identified by its version number. Parts of the System Definition data can be customized by the customer to create a specific development environment. |
LANSA Web Site |
The LANSA Web site is located at www.lansa.com. If you are not already familiar with this Web site, you will find that it contains information about such items as product releases, support desk tips and techniques, courses available, support contact details, demonstrations etc. |
Local Client Only |
This installation requires a Visual LANSA Server Installation. (The Server installation can be either a Slave or an Independent installation.) The Local Client Install includes a copy of the LANSA software on the local machine. The C/C++ compiler is optional. The local LANSA software accesses the Application Repository on the server. Also see Network Client Only. |
Local Database |
A Local Database is a database that is accessed by a single user and is stored on the same machine as the software that accesses the database. |
Local Data Directory |
The Local Data Directory is the directory where Visual LANSA puts temporary files. For example, the list of objects selected in the Work with Processes window. |
Logical File |
A logical file is a view of data in a physical file. It is used as a means of sorting or accessing data in a different order. |
Logical Models |
A logical model or conceptual model is a type of data model that describes data at a high level in user or business terms. |
Master LANSA System |
A Master LANSA System is identified by its ability to maintain its LANSA System Definition data. The Master System Definition data is loaded when a system is installed or upgraded. A Master LANSA System does not use a host monitor. (Note: In V10.0 and later, LANSA for iSeries system is always a Master LANSA System. Visual LANSA Master LANSA Systems are independent.) |
Master LU Name |
The Master Logical Unit (LU) Name is the name of the Master System server. For example, a server may be named as APPN.MYAS400 or MYAS400 for the server. |
Master Repository |
The Master Repository is the name given to the Repository that is located in the Master LANSA System. |
Microsoft Visual/C++ compiler |
This compiler (V7.0) is shipped on the LANSA Windows Software CD and it is the default compiler used for the C code generated by LANSA. |
Network Client Only |
This installation requires a Visual LANSA Server Installation. (The Server installation can be either a Slave or an Independent installation.) The LANSA software on the Server is executed by the Network Client Workstation (using shortcuts installed in a local folder) as well as sharing the Server database. Some of the LANSA software must still be installed locally (e.g. Visual Modeler) and some is optionally installed locally (e.g. Microsoft Compiler). All LANSA options are dictated by the server. The LANSA install reads the windows registry on the server and copies it to the local registry. This term replaces the Network Workstation install. Also see Local Client Only. |
Network Workstation |
This term is no longer used. See Network Client Only. |
node |
An entry in a tree view. |
OAM |
Object Access Module. Also known as an I/O Module. It is a program created by LANSA to handle all input/output processing for a LANSA file. |
ODBC |
Open Database Communications. A Microsoft-based standard for accessing databases. |
OLE |
Object Linking and Embedding. A Microsoft standard for linking objects together. |
OOUI |
Object-Oriented User Interface. |
OS/400 |
Operating System of the IBM i. |
Parent/Child |
Parent/child is a type of relationship used to describe entities in a data model. |
Partition |
A Partition is a means of dividing up a LANSA system. Each partition is completely separate from other partitions. Generally partitions will be used to separate classes of users from one another. |
Partition Initialization |
Partition Initialization allows you to specify how the Visual LANSA System partitions should be set up. You can specify the information and applications loaded into the partition. |
Partition Language |
Partition Language is the language of the LANSA repository. It is the language of the text that you assign to LANSA objects. For example, field description. Also see Development Language. |
PC |
Personal Computer. |
Personnel System Demonstration |
The Personnel System Demonstration includes examples for Visual LANSA and LANSA for the Web. This system is also used by all training materials shipped on the LANSA Windows product CD-ROM. |
Physical File |
A physical file is a type of file that stores data. |
Physical Model |
A physical or low-level model is a type of data model that describes data in terms of physical files and how the information is stored in the computer. |
PJF |
Predetermined Join Field. A special type of virtual field used for accessing information in other files. |
Process |
A process in LANSA is a group of related user tasks or functions. |
RDML |
RDML stands for Rapid Maintenance and Development Language. It is the programming language used by LANSA. |
RDMLX |
Full RDMLX refers to an optional extended set of capabilities and syntax for the LANSA repository and RDML language that enable and support a number of new features in LANSA V11.0. This includes new data types, a relaxation of language limitations and an enhanced language syntax as well as the new Web Application Modules (WAMs). |
Record |
A record is used to describe a file. It is a row of data. |
Record Format |
A record format is the name given to the identifier associated with a group of fields in a file. |
Relationship |
A relationship is a data modeling term. It refers to the characteristics of two entities whereby the information in one entity allows you to access information in the other. |
Repository |
A central location for storing information. |
RFI (Remote Function Invocation) |
The LANSA Integrator RFI is middleware that makes remote integration as easy as coding to a local object. It allows developers to write to local objects that automatically reflect changes to remote host objects with all network communications automated. |
RLTB |
Right Left Top Bottom. |
Root Directory |
The Root Directory is used to define the location where the LANSA software will be installed. |
RPG |
RPG is a programming language used on the IBM i. |
SAA/CUA |
Systems Application Architecture/Common User Access. SAA is a software approach created by IBM to provide consistency across software systems and systems architecture. |
Server Database |
A Server Database is a database that is accessed by one or more users and is stored on a server that is accessed using a network. This server on which the database is located may or may not contain the LANSA software. That is, the server can be dedicated as a database server or it can also be used by a LANSA developer. |
Server Install |
An install is classified as a Visual LANSA Server when the LANSA software is installed on the machine and it uses a Server Database. The Server Database may be accessed by one or more Visual LANSA Clients. Also, the LANSA software and the Server Database may be accessed by one or more Visual LANSA Network installations. |
SEU |
Source Edit Utility. SEU is the name given to the IBM software used to edit source files. |
Slave LANSA System |
A Slave LANSA System is not able to maintain the LANSA System Definition data. It receives its system definition from a Master LANSA System. It is dependent upon the Master LANSA System. The System Definitions must be updated whenever a change has been made to the Master System. A Slave LANSA System may use a host monitor. |
Slave Repository |
The Slave Repository is the name given to the Repository that is located in the Slave LANSA System. |
Slave Server |
A Slave Server install includes a Slave LANSA System using a Server Database. This term replaces the Windows Server install. |
Slave Workstation |
A Slave Workstation install includes a Slave LANSA System using a Workstation Database. This term replaces the Standalone Workstation install. |
SQL |
Structured Query Language. A language used for database access. |
SQL Anywhere™ |
The SQL Anywhere (also known as Adaptive Server Anywhere) database is shipped on the LANSA Windows Software CD and can be installed if a data source cannot be located. |
SQL Anywhere Deployable Images |
The SQL Anywhere Deployable Images provides database support for deployed LANSA applications. These images are only required if the deployed LANSA applications use the SQL Anywhere database. |
Standalone Workstation |
This term is no longer used. See Slave Workstation. |
TCP/IP |
Transmission Communication Protocol / Internet Protocol is a standard communication protocol used by the Internet. |
Template |
A template or application template is a "program" which generates RDML functions based on a question and answer session with the developer. |
Thin Client |
A computing model that minimizes code on the client PC and relies heavily on a "fat server" where the majority of code resides. |
TIMI |
Technology Independent Machine Interface. An approach used by IBM to make the hardware and software layers independent. |
TISI |
Technology Independent Software Interface. An approach used by LANSA to make the application software and operating system platform layers independent. |
Translation Tables |
The Translation Tables are used by LANSA Open when a non-English version of the software is required. Also see LANSA Open. |
Upgrade |
The software Upgrade option is used to load the latest version of the LANSA software to replace an older version of the software. |
User Agent |
The LANSA Integrator User Agent is a Java-based tool, that allows file upload to a JSM HTTP Service or MQ-Series based function. Also see LANSA Integrator. |
Utilities |
LANSA supplies a number of programs that are labelled "Utilities". For example, the Web Function Editor and Web Administrator. |
Validation Checks |
Validation checks are rules that can be associated with a field or a file. |
Virtual Field |
A virtual field is a field used with LANSA files. Its value is derived from other fields in a LANSA database. The field is not stored in the file. |
Visual LANSA |
Visual LANSA is an extremely flexible application development environment where you can use a single skill set to build and deploy applications for IBM i, Windows or Internet environments. LANSA's active object Repository and powerful RDML programming language combine to create a highly productive development environment. Visual LANSA acts as the core integrated development environment (IDE) on Windows that is used to support LANSA development. |
Visual LANSA Client Only |
A Client Only installation uses a Visual LANSA Server system installed on a Windows Server. Also see Local Client Only and Network Client Only. |
Visual LANSA Core Files |
The Visual LANSA Core Files must always be installed when Visual LANSA is installed. |
Visual LANSA Framework |
The Visual LANSA Framework is a framework that helps you design and implement large scale and highly integrated Visual LANSA applications. It is an executable environment that provides the structure and the basic functionality for applications, business objects, commands, menus etc. for both Windows and the Web. |
Visual LANSA Independent Server Installation |
This installation includes a Master Visual LANSA System using a Server Database. In V11.0, the Visual LANSA System has no slaves. |
Visual LANSA Independent Workstation Installation |
This installation includes a Master Visual LANSA System using a Workstation Database. In V11.0, the Visual LANSA System has no slaves. |
Visual LANSA Options |
The Visual LANSA Options are a group of installation settings that are specific to the Visual LANSA installation. Also see Common Options. |
Visual LANSA Slave Server Installation |
This installation includes a Slave Visual LANSA System using a Server Database. In V11.0, the Master System is a LANSA for iSeries System. |
Visual LANSA Slave Workstation Installation |
This installation includes a Slave Visual LANSA System using a Workstation Database. In V11.0, the Master System is a LANSA for iSeries System. |
Web Administrator |
The LANSA for the Web Administrator is used to configure the LANSA for the Web software on the Web Server and the Data/Application Server. |
Web Application Module |
LANSA for the Web component-based web development model. Also known as WAM. |
Web Function |
LANSA for the Web function-based web development model. |
Web Function Editor |
The LANSA for the Web Function Editor is a tool that allows developers to build Web components and edit the LANSA HTML pages stored on the Data/Application Server. |
Web Images |
The Web Images are a default set of image files used by LANSA for the Web. |
Web Server |
The Web Server is the machine used to host the Web Serving software. Also see Data/Application Server, IIS Plug-in and Java Servlet. |
WebSphere™ |
WebSphere is Integration and application infrastructure software from IBM for the IBM i, Windows, and other platforms. This includes Web serving software. |
Windows |
Windows is a graphical operating system interface produced by Microsoft. |
Windows NT/2000 Server Install |
This term is no longer used. See Slave Server. |
Workstation |
Workstation is another name used for a programmable device which has been attached |
Workstation Database |
A Workstation Database is a database that is accessed by a single user and is stored on the same machine as the software that accesses the database. |
Workstation Install |
An install is classified as a Visual LANSA Workstation when it contains a complete LANSA System, i.e. it has the LANSA software, LANSA System Definition data and Application Repository data on a single machine and the LANSA System is not accessed by any Visual LANSA Clients. |