Rational Developer for System z, Version 7.6


Glossary for Rational Developer for System z

3270
The 3270 Information Display System, a product from IBM® that before the arrival of the personal computer (PC) was the way that almost the entire corporate world interfaced with a computer. Many thousands of corporate application programs written to interact with users at 3270 terminals are being used from PCs equipped with software known generally as 3270 emulators. TN3270 is a program that provides PC users remote (Telnet) connection to an IBM computer that is running 3270 applications.
access control
In computer security, the process of ensuring that users can access only those resources of a computer system for which they are authorized.
accessibility
An attribute of a software or hardware product that is usable by individuals who have disabilities.
action ID
A numeric identifier between 0 and 999 for an action.
action set
In Eclipse, a group of commands that a perspective contributes to the main toolbar and menu bar.
Application Deployment Manager manifest
A file that is used to store CICS® resource definitions. Application Deployment Manager can either directly install CICS resource definitions defined in the Application Deployment Manager manifest, or the Application Deployment Manager manifest can be exported to a CICS test environment for later processing by a system programmer.
agent
A program that automatically performs a specific service, such as data collection, without user intervention or on a regular schedule.
alias
In EGL generation, a name that is placed in the output source file in place of the name that was in the EGL source code. In most cases, the original name is aliased because it was not valid in the target generation language.
In MVS™, an alternate label; for example, you can use a label and one or more aliases to refer to the same data element or point in a computer program.
APAR
See authorized program analysis report.
API
See application programming interface.
applet
A small application program that performs a specific task and is typically portable between operating systems. Often written in Java™, applets can be downloaded from the Internet and run in a Web browser.
application client
In J2EE, a first-tier client component that runs in its own Java virtual machine. Application clients have access to some J2EE platform APIs, for example JNDI, JDBC, RMI-IIOP, and JMS. (Sun)
application client module
A Java archive (JAR) file that contains a client that accesses a Java application. The Java application runs inside a client container and can connect to remote or client-side J2EE resources.
Application Client project
A structure and hierarchy of folders and files that contain a first-tier client component that executes in its own Java virtual machine.
Application Deployment Manager
The Application Deployment Manager provides CICS resource definition deployment services for Rational® Developer for System z® components. For example, during the generate phase components create an Application Deployment Manager manifest (.admr) file in the project. required CICS resource definitions are automatically added to the manifest. You can open the manifest with the Resource Definition Editor to edit, add, or delete CICS resource definitions from the manifest. You can then request that the manifest resources be installed immediately, or that the manifest be exported for later processing by a system programmer.
application programming interface (API)
An interface that allows an application program that is written in a high-level language to use specific data or functions of the operating system or another program.
application server
  1. A program that handles all application operations between browser-based computers and an organization's back-end business applications or databases. There is a special class of Java-based application servers that conform to the J2EE standard. J2EE code can be easily ported between these application servers. They can support JSP pages and servlets for dynamic Web content and EJB beans for transactions and database access.
  2. The target of a request from a remote application. In the DB2® environment, the application server function is provided by the distributed data facility and is used to access DB2 data from remote applications.
  3. A server program in a distributed network that provides the execution environment for an application program.
  4. The target of a request from an application requester. The database management system (DBMS) at the application server site provides the requested data.
  5. Software that handles communication with the client requesting an asset and queries of the Content Manager.
artifact
A physical piece of information that is used or produced by a software development process. Examples of artifacts include models, source files, scripts, and binary executable files.
Assign node
In Enterprise Service Tools, a node that is associated with a mapping routine that contains mappings. A mapping is a single instance of copying data from one message element to another, or of storing an immediate value (such as a number or a string) into a message element.
association
In enterprise beans, a relationship that exists between two container-managed persistence (CMP) entity beans. Two types of association exist: one-to-one and one-to-many.
For XML documents, the linkage of the document itself to the rules that govern its structure, which can be defined by a Document Type Definition (DTD) or an XML schema.
ASYNC
See asynchronous.
asynchronous (ASYNC)
Pertaining to events that are not synchronized in time or do not occur in regular or predictable time intervals.
attribute
In Enterprise Service Tools, an attribute represents an XML Schema attribute. Attributes are very similar to simple elements, but they require special treatment when used with XML messages. In messages that are not XML they are treated exactly like a simple element based on the same simple type.
authentication
The security service that provides proof that a user of a computer system is genuinely who that person claims to be. Common mechanisms for implementing this service are passwords and digital signatures. Authentication is distinct from authorization; authentication is not concerned with granting or denying access to system resources.
authorization
The method that determines which portlets a user or a user group can access.
authorized program analysis report (APAR)
A request for correction of a defect in a current release of an IBM-supplied program.
autosave
An LPEX editor preference for periodically saving a local backup copy of an editing session.
Axis
An implementation of SOAP on which Java Web services can be implemented.
base time
The time spent executing a particular method. Base time does not include time spent in other Java methods that the method calls.
Basic Mapping Support (BMS)
A design component of a CICS application that handles the presentation logic of the CICS transaction and relieves the application developer from having to encode and decode 3270 terminal data streams. BMS is an application programming interface between CICS programs and terminal devices. A BMS map set is made up of maps that specify how field data is to be formatted. At build time, an Application developer can use the BMS importer function in the service flow project tools to import a BMS map set from an application on the EIS into a service flow project. An application developer can also assign the actual BMS field names to fields on 3270 application screens that he or she has imported.
basic program
A type of EGL program part that performs tasks without interacting with users in real time.
bean
A definition or instance of a JavaBeans™ component. See also enterprise bean, JavaBeans.
bidirectional
Pertaining to scripts such as Arabic and Hebrew that generally run from right to left, except for numbers, which run from left to right. This definition is from the Localization Industry Standards Association (LISA) Glossary.
bidirectional attribute
Text type, text orientation, numeric swapping, and symmetric swapping.
bidirectional conversion
The process of transforming bidirectional text layout between incompatible systems.
bind
To establish a connection between software components on a network using an agreed-to protocol. In Web services, the bind operation occurs when the service requester invokes or initiates an interaction with the service at run time using the binding details in the service description to locate, contact, and invoke the service.
bottom-up development
In Web services, the process of developing a service from an existing artifact such as a Java bean or enterprise bean rather than a Web Services Definition Language (WSDL) file. See also top-down development.
branch
An object that specifies a linear sequence of versions of an element. Each branch is an instance of a branch type object.
In the CVS team development environment, a separate line of development where changes can be isolated. When a programmer changes files on a branch, those changes are not displayed on the main trunk or other branches.
breakpoint
A specified point in a program where the system stops processing and can be resumed after manual intervention.
build
In z/OS®, the process during which a build program produces one or more derived objects. This might involve actual translation of source files and construction of binary files by compilers, linkers, text formatters, and so on. A system build consists of a combination of actual target rebuilds and build avoidance.
To create or modify resources, typically based on the state of other resources. A Java builder converts Java source files into executable class files, for example, and a Web link builder updates links to files whose name or location has changed.
build descriptor part
An EGL part that controls the generation process through option-and-value pairs that specify how to generate and prepare output.
build path
The path that is used during compilation of Java source code to find referenced classes that are located in other projects.
build request
A request from the client to perform a build transaction.
build transaction
A job started on MVS to perform builds after a build request has been received from the client.
bundle
A directory that contains CICS artifacts and a manifest. The manifest describes the bundle and its dependencies. The bundle is the unit of deployment for an application.
bundle manifest
A special file that describes the resources, location of supporting artifacts, application prerequisites, and services that are included in a bundle to deploy part or all of a CICS application.
business method
A method of an enterprise bean that implements the business logic or rules of an application. (Sun)
business process
In Enterprise Service Tools, a group of logically related activities that use the resources of the organization to provide defined results in support of the organization's objectives.
business service
In Web services programming, a data structure type that contains information about groups of Web services. The business service structure is specified when a service is registered.
bytecode
Machine-independent code generated by the Java compiler and executed by the Java interpreter. (Sun)
call stack
A list of data elements that is constructed and maintained by the by the Java virtual machine (JVM) for a program to successfully call and return from a method.
capability
In Eclipse, a group of functions that can be hidden or revealed in order to simplify the user interface. Capabilities are enabled or disabled by changing preference settings.
cascading style sheet (CSS)
A file that defines a hierarchical set of style rules for controlling the rendering of HTML or XML files in browsers, viewers, or in print.
change set
A list of related versions associated with a Unified Change Management (UCM) activity. ClearCase® records the versions that developers create while working on an activity. An activity uses a change set to record the versions of files that are delivered, integrated, and released together.
Change bidirectional format
A special conversion utility to convert files from one bidirectional layout to another inside the Eclipse workspace.
channel
A specialized Web application within a portal to which a user can subscribe.
cheat sheet
An interface that guides users through the wizards and steps required to perform a complex task and that links to relevant sections of the online help.
check box
A square box with associated text that represents a choice. When a user selects the choice, the check box is filled to indicate that the choice is selected. You can clear the check box by selecting the choice again, thereby deselecting the choice.
check in
In certain software configuration management (SCM) systems, to copy files back into the repository after changing them.
check out
In certain software configuration management (SCM) systems, to copy the latest revision of a file from the repository so that it can be modified.
CICS
Customer Information Control System, a transaction server that runs primarily on IBM mainframe systems under z/OS or z/VSE™. CICS on distributed platforms is called TXSeries® and it is available on the AIX®, Windows®, Solaris, and HP-UX operating systems.
In Enterprise Service Tools, CICS is an online transaction processing (OLTP) program from IBM that, together with the COBOL programming language, has formed over the past several decades the most common set of tools for building customer transaction applications in the world of large enterprise mainframe computing. A great number of existing applications are COBOL or CICS applications. Using the application programming interface (API) provided by CICS, a programmer can write programs that communicate with online users and read from or write to customer and other records (orders, inventory figures, customer data, and so forth) in a database (typically referred to as "data sets") using CICS facilities rather than IBM's access methods directly. Like other transaction managers, CICS can ensure that transactions are completed and, if not, undo partly completed transactions so that the integrity of data records is maintained. Using the service flow project tools, an enterprise developer can deploy a service flow to multiple supported runtime environments (including CICS) to combine new business logic with the existing business logic and data present in existing systems.
CICS Explorer
An Eclipse plug-in by IBM to view and manage CICS resources.
CICS primary connection region
The CICS resource definition client for Application Deployment Manager implements a Web service connection to the CICS primary connection region. A CICS test environment can consist of several Multi-Region Option (MRO) connected regions. Over time, unofficial designations have been used to categorize these regions. Typical designations are terminal owning region (TOR), Web owning region (WOR), application owning region (AOR), and data owning region (DOR). A Web owning region is used to implement CICS Web services support, and the CICS resource definition server for Application Deployment Manager must run in this region. This region is known to Application Deployment Manager as the CICS primary connection region.
CICS resource definition
A definition that CICS uses to define and manage resources. CICS has more than 30 resource definitions. Some of the more common ones used by application developers are DB2TRAN, DOCTEMPLATE, FILE, MAPSET, PROCESSTYPE, PROGRAM, TDQUEUE, and TRANSACTION.
class
In object-oriented design or programming, a model or template that can be used to create objects with a common definition and common properties, operations, and behavior. An object is an instance of a class.
class diagram
A diagram that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships.
class file
A compiled Java source file.
class hierarchy
The relationships between classes that share a single inheritance. In Java programming, all classes inherit from the Object class.
class loader
Part of the Java virtual machine (JVM) that is responsible for finding and loading class files. A class loader affects the packaging of applications and the runtime behavior of packaged applications deployed on application servers.
class path
A list of directories and JAR files that contain resource files or Java classes that a program can load dynamically at run time.
client
The Rational Developer for System z component that is installed on a workstation and communicates with a remote system.
client/server
Pertains to the model of interaction in distributed data processing in which a program on one computer sends a request to a program on another computer and awaits a response. The requesting program is called a client; the answering program is called a server. See also distributed application.
clipboard
An area of computer memory, or storage, that temporarily holds data. Data in the clipboard is available to other applications.
code assist
See content assist.
collaboration
The ability to connect customers, employees, or business partners to the people and processes in a business or organization, in order to facilitate improved decision-making. Collaboration involves two or more individuals with complementary skills interacting together to resolve a business problem.
Common Object Request Broker Architecture (CORBA)
An architecture and a specification for distributed object-oriented computing that separates client and server programs with a formal interface definition.
communication area (COMMAREA)
In Enterprise Service Tools, a CICS area that is used to pass data between tasks that communicate with a given terminal. The area can also be used to pass data between programs within a task.
Compile
  1. In Integrated Language Environment® (ILE) languages, to translate source statements into modules that then can be bound into programs or service programs.
  2. To translate all or part of a program expressed in a high-level language into a computer program expressed in an intermediate language, an assembler language, or a machine language.
compilation unit
A portion of a computer program sufficiently complete to be compiled correctly.
complex element
In Enterprise Service Tools, a named structure that contains simple elements within the message. Complex elements can contain other complex elements and can also contain groups. The content of a complex element is defined by a complex type.
complex type
In XML, a type that allows elements in its content and can carry attributes. See also simple type.
In Enterprise Service Tools, a structure within a message. A complex type contains elements, attributes, and groups organized into a hierarchy.
component
In Eclipse, one or more plug-ins that work together to deliver a discrete set of functions.
A reusable object or program that performs a specific function and is designed to work with other components and applications.
component test
An automated test of one or more components of a J2EE application, which can include Java classes, EJB beans, or Web services. A component test comprises a Java test script based on the JUnit framework plus validation actions, initialization points, timing constraints, and associated test data that is maintained separately from the test script. See also test pattern.
composer
In EJB, a class used to map a single complex bean field to multiple database columns. Composition is needed for complex fields that are themselves objects with fields and behavior.
Concurrent Versions System (CVS)
An open-source, network-transparent version control system.
connection
A set of properties, such as host name, server launcher settings, and security settings are required when you to communicate with a specific remote system.
connector
In Enterprise Service Tools, a well-defined, durable communication or programming interface to an Enterprise Information System. A connector provides a means of accepting data in a definable format, invoking an operation, and receiving results in a definable format. Examples of a connector are as follows:
  • Host On Demand (HOD): 3270 or 5250 connector style
  • CICS Transaction Gateway (CTG) -- data structure / transactional style
  • Java Messaging Service
  • WebSphere® MQ: asynchronous Messaging style
  • JCA connectors for these interfaces:
    • IMSConnect interfaces
    • Runtime modules produced with MQSI Agent for CICS
    • The following interfaces in CICS: FEPI, Link3270 Bridge, LINK with COMMAREA, and LINK with Channel
  • SOAP listener.
container
For CARMA, a container is a CARMA resource that contains other CARMA resources.
content area
The Rational Developer for System z Welcome page experience has six content areas. On the Welcome page experience, you can select any of the six buttons in the center of the window to display the associated content area page. In this content area you can select buttons to open content pages within the Welcome Experience or help pages in the online helps.
The content area of the System z LPEX Editor is the working area used to create or edit source.
content assist
A feature of some source editors that prompts you with a list of valid alternatives for completing the current line of code or input field.
content model
The representation of any data that can be contained inside an XML element. There are four kinds of content models: element content, mixed content, EMPTY content and ANY content.
content provider
A source for content that can be incorporated into a portal page as a portlet.
context root
The Web application root, which is the top-level directory of an application when it is deployed to a Web server.
control
See widget.
copy book (copybook)
In Enterprise Service Tools, a COBOL header file that describes all the columns in an underlying data file.
CORBA
See Common Object Request Broker Architecture.
CSS
See cascading style sheet.
cursor column indicator
In System z LPEX Editor, a visual indicator of the column in which the cursor is currently located.
custom action
An action for a file or project that is created by using the Menu Manager preferences pages and is displayed on pop-up menus.
custom tag
An extension to the JavaServer Pages (JSP) language that performs a specialized task. Custom tags are typically distributed in the form of a tag library, which also contains the Java classes that implement the tags.
Custom Wire Format (CWF)
In Enterprise Service Tools, the physical representation of a message in the MRM domain that is composed of a number of fixed format data structures or elements, which are not separated by delimiters.
CVS
See Concurrent Versions System.
daemon
A program that runs unattended to perform continuous or periodic functions, such as network control.
database
A collection of interrelated or independent data items that are stored together to serve one or more applications.
data class
Most data and all literals used in a COBOL program are divided into classes and categories. Data classes are groupings of data categories. Data categories are determined by the attributes of data description entries or function definitions.
data definition
A data definition (DD) statement is a job control statement that defines a data set to the operating system, and is a request to the operating system for the allocation of input and output resources. If the data sets are not dynamically allocated, each job step must include a DD statement for each data set that is processed by the step.
Data Definition Language (DDL)
A language for describing data and its relationships in a database.
Data Definition view
A local representation of databases and their objects that provides features to manipulate these objects and export them to a remote database.
data item
In EGL, an area of memory that is not in a structure and is based either on a data item part or on an explicit primitive-type description such as CHAR(3).
data part
An EGL definition that specifies a data structure. The types of data parts are dataItem, dataTable, and record parts.
data set
The major unit of data storage and retrieval, consisting of a collection of data in one of several prescribed arrangements and described by control information to which the system has access.
data set mapping
An association between the lowest level qualifier in an MVS data set name and the file name extension used for the related workstation-based file.
data source
In JDBC, an interface that provides a logical representation of a pool of connections to a physical data source. Data source objects provide application portability by making it unnecessary to supply information specific to a particular database driver.
DB2
A family of IBM licensed programs for relational database management.
DDL
See Data Definition Language.
deadlock
A condition in which two independent threads of control are blocked, each waiting for the other to take some action. Deadlock often arises from adding synchronization mechanisms to avoid race conditions.
debug
To detect, diagnose, and eliminate errors in programs.
debug engine
The server component of the debugger, whose client/server design enables both local and remote debugging. The debug engine runs on the same system as the program being debugged.
debugger
A tool used to detect and trace errors in computer programs.
debugging session
The debugging activities that occur between the time that a developer starts a debugger and the time that the developer exits from it.
declaration
A statement that establishes the names and characteristics of data objects and functions used in a program. For PL/I, the scope of the declaration of a name is determined entirely by the position where the name is declared within the program. Implicit declarations are treated as if the name were declared in a DECLARE statement immediately following the PROCEDURE statement of the external procedure. Also, an (explicit) declaration of a name is the block containing the declaration. This includes all contained blocks, except those blocks (and any blocks contained within them) to which another explicit declaration of the same name is internal.
dependencies
The files, such as copybooks and include files, required for COBOL and PL/I programs to compile properly.
deploy
To place files or install software into an operational environment.
deployment descriptor
An XML file that describes how to deploy a module or application by specifying configuration and container options. For example, an EJB deployment descriptor passes information to an EJB container about how to manage and control an enterprise bean.
deployment directory
The directory where the published server configuration and Web application are located on the computer where the application server is installed.
deprecated
Pertaining to an entity, such as a programming element or feature, that is supported but no longer recommended and that might become obsolete.
descriptor
In Enterprise Service Tools, a property or characteristic of an instance of structured data that is either defined manually by a developer using the screen message editor component of the service flow project tools, or is assigned automatically (as part of a default screen descriptor) through a screen capture or screen import (BMS or HSC) operation. At build time, these descriptors are used for screen matching (matching the screen descriptors against a known pattern or structure). These same descriptors are also used for screen recognition purposes in the deployed service. Descriptors are components of a screen description.
deserializer
A method for converting a serialized variable into object data. See also serializer.
directive
For PL/I, by using directives, you can construct description files similar to batch files. Each directive begins with an exclamation mark (!) in the first column of the description file. Spaces can be placed between the exclamation point and the directive keyword. Following is an example code block of directives:
!INCLUDE <infrules.txt> 
!CMDSWITCHES +D
winner.exe:winner.obj
!IFDEF DEBUG
! IF "$(DEBUG)"=="y"
     ilink /de winner.obj;
! ELSE
     ilink winner.obj;
! ENDIF
!ELSE
! ERROR Macro named DEBUG is not defined.
!ENDIF<infrules.txt>
distributed application
An application made up of distinct components that are physically located on different computer systems, connected by a network. See also client/server.
distinguished property
A property value that has been altered from its original, inherited value.
Document Object Model (DOM)
A system in which a structured document, for example an XML file, is viewed as a tree of objects that can be programmatically accessed and updated.
document type definition (DTD)
The rules that specify the structure for a particular class of SGML or XML documents. The DTD defines the structure with elements, attributes, and notations, and it establishes constraints for how each element, attribute, and notation can be used within the particular class of documents.
DOM
See Document Object Model.
double-byte character set (DBCS)
In Enterprise Service Tools, a set of characters in which each character is represented by two bytes. These character sets are commonly used by national languages, such as Japanese and Chinese, that have more symbols than can be represented by a single byte.
DTD
See document type definition.
dynamic Web content
Programming elements such as JavaServer Pages (JSP) files, servlets, and scripts that require client or server-side processing for accurate runtime rendering in a Web browser.
dynamic Web project
A project that contains resources for a Web application with dynamic content such as servlets or JavaServer Pages (JSP) files. The structure of a dynamic Web project reflects the J2EE standard for Web content, classes, class paths, the deployment descriptor, and so on.
EAR
See enterprise archive. See also Web archive, Java archive.
EAR file
See also Web archive, Java archive. See enterprise archive.
EAR project
See enterprise application project.
Eclipse
An open-source initiative that provides independent software vendors (ISVs) and other tool developers with a standard platform for developing plug-compatible application development tools.
Eclipse Modeling Framework
The Eclipse components that define and implement structured data models, which are a set of related classes that are used to handle data in applications.
editor area
In Eclipse and Eclipse-based products, the area in the workbench window where files are opened for editing.
EGL
See Enterprise Generation Language.
EGL build file
An XML file with an .eglbld extension, used to store definitions of EGL build parts.
EGL file
An Enterprise Generation Language program file (extension .eglpgm), definitions file (extension .egldef), or build file (extension .eglbld).
EGL keyword
A term that begins an EGL statement that is neither a function invocation nor an assignment statement. Keywords include add and delete.
EGL source file
A text file with an .egl extension, used to store definitions of EGL data, logic, and UI parts.
EGL statement
A directive that is coded into an EGL function part to cause an action when the generated program runs. Examples include an EGL assignment statement and an EGL add statement.
EIS
See enterprise information system. See also resource adapter.
EIS interface
In Enterprise Service Tools, an interface that varies from organization to organization and whose nature is determined by the systems and application architecture. From the perspective of the service flow project tools user, the EIS interface represents the data source on which you focus your development efforts. Many enterprise information systems have interfaces that do not lend themselves to participation in SOA. Developers are able to use the service flow project tools to model and compose the EIS interface (5250 and 3270 screens, COBOL record descriptions, transactions) to a more SOA compliant programmatic interface, enabling the enterprise to transform or adapt to a new set of operations and methods that move the application toward SOA.
EJB
See Enterprise JavaBeans.
EJB bean
See also bean. See enterprise bean.
EJB container
A container that implements the EJB component contract of the J2EE architecture. This contract specifies a runtime environment for enterprise beans that includes security, concurrency, life cycle management, transaction, deployment, and other services. (Sun) See also EJB server.
EJB JAR file
A Java archive that contains an EJB module. (Sun)
EJB module
A software unit that consists of one or more enterprise beans and an EJB deployment descriptor. (Sun)
EJB object
In enterprise beans, an object whose class implements the enterprise bean remote interface. (Sun)
EJB project
A project that contains the resources needed for EJB applications, including enterprise beans; home, local, and remote interfaces; JSP files; servlets; and deployment descriptors.
EJB server
Software that provides services to an EJB container. An EJB server can host one or more EJB containers. (Sun) See also EJB container.
element
In the Java development tools (JDT) feature of Eclipse, a generic term that can refer to Java packages, classes, types, interfaces, methods, or fields.
In markup languages such as SGML, XML, and HTML, a basic unit consisting of a start tag, end tag, associated attributes and their values, and any text that is contained between the two.
In Enterprise Service Tools, a named piece of information, or a field, within a message, with a business meaning agreed by the applications that create and process the message.
endpoint
The system that is the origin or destination of a session.
In Enterprise Service Tools, an association between a binding and a network address, specified by a Uniform Resource Identifier, which can be used to communicate with an instance of a service. An end point indicates a specific location for accessing a service using a specific protocol and data.
enterprise application
See J2EE application.
enterprise application project (EAR project)
A structure and hierarchy of folders and files that contain a deployment descriptor and IBM extension document and files that are common to all J2EE modules that are defined in the deployment descriptor.
enterprise archive (EAR)
A specialized type of JAR file, defined by the J2EE standard, used to deploy J2EE applications to J2EE application servers. An EAR file contains EJB components, a deployment descriptor, and Web archive (WAR) files for individual Web applications. See also Web archive, Java archive.
enterprise bean
A component that implements a business task or business entity and resides in an EJB container. Entity beans, session beans, and message-driven beans are all enterprise beans. (Sun) See also bean.
Enterprise Generation Language (EGL)
A high-level language that allows developers to focus on business logic as they create complex business applications for deployment in any of several environments, including the Web. The language simplifies database and message-queue access and the use of J2EE.
enterprise information system (EIS)
The applications that compose an enterprise's existing system for handling companywide information. An enterprise information system offers a well-defined set of services that are exposed as local or remote interfaces or both. (Sun) See also resource adapter.
Enterprise JavaBeans (EJB)
A component architecture defined by Sun Microsystems for the development and deployment of object-oriented, distributed, enterprise-level applications.
Enterprise Service Tools
A component of Rational Developer for System z that comprises service flow project tools and single-service project tools.
entity
In markup languages such as XML, a collection of characters that can be referenced as a unit, for example to incorporate often repeated text or special characters within a document.
error buffer
A portion of storage used to hold error output information temporarily.
error feedback
In zIDE, a mechanism for capturing and displaying error messages generated by COBOL and PL/I language source files using the integrated DB2 coprocessor and CICS translator; this mechanism can be extended to support custom preprocessors and additional languages, such as Assembler.
export project
To save the property values, subprojects, and resources of a project for sharing with other users.
export project definition
To save the property values of a project for sharing with other users.
extensible error feedback
A Rational Developer for System z tool for capturing and displaying error messages generated by COBOL and PL/I language source files using the integrated DB2 coprocessor and CICS translator. This mechanism can be extended to support custom preprocessors and additional languages, such as Assembler.
Extensible Hypertext Markup Language (XHTML)
A reformulation of HTML 4.0 as an application of XML. XHTML is a family of current and future DTDs and modules that reproduce, subset, and extend HTML.
Extensible Markup Language (XML)
A standard metalanguage for defining markup languages that is based on Standard Generalized Markup Language (SGML).
Extensible Stylesheet Language (XSL)
A language for specifying style sheets for XML documents. Extensible Stylesheet Language Transformation (XSLT) is used with XSL to describe how an XML document is transformed into another document.
extension
In Eclipse, the mechanism that a plug-in uses to extend the platform. See also extension point.
extension point
In Eclipse, the specification that defines what attributes and values must be declared by an extension. See also extension.
Faces component
One of a collection of user interface components (such as input fields) and data components (representing data such as records in a database) that can be dragged to a Faces JSP file and then bound to each other to build a dynamic Web project. See also JavaServer Faces.
Faces JSP file
A file that represents a page in a dynamic Web project and contains JavaServer Faces UI and data components. See also JavaServer Faces.
factory
In object-oriented programming, a class that is used to create instances of another class. A factory is used to isolate the creation of objects of a particular class into one place so that new functions can be provided without widespread code changes.
fast view
In Eclipse, a view that is opened and closed by clicking a button on the shortcut bar.
feature
In Eclipse, a JAR file that is packaged in a form that the update manager accepts and uses to update the platform. Features have a manifest that provides basic information about the content of the feature, which can include plug-ins, fragments and other files.
FEPI
In Enterprise Service Tools, front-end programming interface, a separately installable function of CICS Transaction Server that enables communication with non-LU6.2 partners by simulating an LU0 or LU2 device.
field
In Java programming, a data member of a class.
File Transfer Protocol (FTP)
In the Internet suite of protocols, an application layer protocol that uses TCP and Telnet services to transfer bulk-data files between machines or hosts.
filter string
A Remote System Explorer setting that specifies data set name patterns to display in the Remote Systems view.
fire
In object-oriented programming, to cause a state transition.
firewall rules
TCP/IP communication settings that Rational Developer for System z clients use to communicate effectively with the server through a firewall.
fix pack
A cumulative collection of fixes that is made available between scheduled refresh packs, manufacturing refreshes, or releases. A fix pack brings your software up to a specific maintenance level. See also program temporary fix, interim fix, refresh pack.
flow
In Enterprise Service Tools, a graphical representation of the sequence of activities performed in accordance with the business processes of an enterprise. Flows consist of a graph of nodes, with defined entry and exit points. Each node represents invoking a service operation, controlling the flow of the sequence, or performing reusable business logic. Flows are exposed as a service themselves, to be driven externally.
flow editor
In Enterprise Service Tools, an editor that you can use to construct manually a service that represents a screen operations file and prepopulate a flow by using a captured WSDL screen operations file. You can also use the editor to annotate a flow with alternative paths that represent error paths and additional business behaviors that cannot be captured using real-time importers. The flow editor represents the programming model for a flow adapter. Bottom-up and top-down methodologies are supported.
flow message editor
In Enterprise Service Tools, the default editor provided by the service flow project tools perspective for editing message definition (.mxsd) files. The editor is started in the editor area when you open an existing message definition file using the Navigator or when you create a new message definition file using the New Message Definition wizard.
flow message set editor
In Enterprise Service Tools, the default editor provided by the service flow project tools perspective for editing message set (messageSet.mset) files. The editor is started in the editor area when you open an existing message definition file using the Navigator or when you create a new message definition file using the New Message Definition wizard. The following editing tasks are among those that can be performed from the flow message set editor:
  • The Properties Hierarchy, which provides a hierarchy at three levels: Message set, Physical properties and Documentation. Edit the message set details message definitions created by importing data structures using the XML Schema, DTD, C or COBOL importers. The message definition file that the import process creates is automatically populated with the imported content, which you can then edit as required.
  • Populate empty message definition files with message model objects by creating the elements, attributes, groups, types and messages needed to represent your message formats. The message model that you create can consist of both logical and physical information, if appropriate physical formats exist in the message set.
  • Edit the logical structure of a message.
  • Create and edit the physical structure and properties of a message.
  • Create message definitions.
  • Create common constructs within a message set for use with other message definition files.
fixed data set name
A data set name that contains a specific user ID as the high-level qualifier, such as MYUSERID.COBOL.SOURCE.
foreign key
In a relational database, a key in one table that references the primary key in another table. See also primary key.
form
A display screen, printed document, or file with defined spaces for information to be inserted.
formGroup
In EGL, a collection of form parts. A formGroup part is generated as an output separate from an EGL program.
frame
In hypertext markup language (HTML) coding, a subset of the Web browser window.
frameset
An HTML file that defines the layout of a Web page that is composed of other, separate HTML files.
FTP
See File Transfer Protocol.
full build
In Eclipse, a build in which all resources within the scope of the build are considered. See also incremental build.
garbage collection
Part of a language's runtime system or an add-on library that automatically determines the memory that a program no longer uses, and recycles it for other use. Garbage collection can be assisted by the compiler, the hardware, the operating system, or any combination of the three.
gateway
  1. A middleware component that bridges Internet and intranet environments during Web service invocations.
  2. Software that provides services between the endpoints and the rest of the Tivoli® environment.
  3. A component of a Voice over Internet Protocol that provides a bridge between VoIP and circuit-switched environments.
  4. A device or program used to connect networks or systems with different network architectures. The systems can have different characteristics, such as different communication protocols, different network architecture, or different security policies, in which case the gateway performs a translation role and a connection role.
getter method
A method whose purpose is to get the value of an instance or class variable. This allows another object to find out the value of one of its variables. See also setter method.
generic data set name
A data set name that contains <HLQ>, rather than a specific user ID, as the high-level qualifier, such as <HLQ>.COBOL.SOURCE.
GIF
See Graphics Interchange Format.
global attribute
In XML, an attribute that is declared as a child of the schema element rather than as part of a complex type definition. Global attributes can be referenced in one or more content models using the ref attribute.
global element
In XML, an element that is declared as a child of the schema element rather than as part of a complex type definition. Global elements can be referenced in one or more content models using the ref attribute.
global orientation
The direction in which text is stored. It can be right to left (RTL) or left to right (LTR).
Graphics Interchange Format (GIF)
A file format for storing images. GIF files are common on the World Wide Web because they only contain a maximum of 256 colors and are therefore very small.
group
A list of elements with information about how those elements are displayed in a message. The group can be displayed in the following ways: as a sequence, as unordered, or as selective. A sequence is an ordered group. An unordered group is one in which the entire list is shown and a selective group is one in which only the selected lists are shown.
handler
In Web services, a mechanism for processing service content and extending the function of a JAX-RPC runtime system.
handshake
The exchange of messages at the start of a Secure Sockets Layer session that allows the client to authenticate the server using public key techniques (and, optionally, for the server to authenticate the client), then allows the client and server to cooperate in creating symmetric keys for encryption, decryption, and detection of tampering.
HATS (Host Access Transformation Services)
In Enterprise Service Tools, an IBM software set of tools that provides Web-based access to existing data sources and host-based applications. Using the service flow project tools, an enterprise developer can deploy a service flow to multiple supported runtimes.
headless
Pertains to a program or application that can run without a graphical user interface or, in some cases, without any user interface at all. Headless operation is often used for network servers or embedded systems.
heap
In Java programming, a block of memory that the Java virtual machine uses at run time to store Java objects. Java heap memory is managed by a garbage collector, which automatically de-allocates Java objects that are no longer in use.
home interface
In enterprise beans, an interface that defines zero or more create and remove methods for a session bean or zero or more create, finder, and remove methods for an entity bean. See also remote interface.
home page
The top-level Web page of a portal.
host
In performance profiling, a computer that owns processes that are being profiled. See also server.
A computer that is connected to a network and provides an access point to that network. The host can be a client, a server, or both a client and server simultaneously. See also server.
host-based project
In zIDE, a project that has been defined on a z/OS system and can be downloaded to the workstation when you connect to the remote system.
host connection properties file
In Enterprise Service Tools, the resource in a service flow project that contains the information necessary for connecting to the host system during build time. The host connection information that is stored on the host connection properties file enables you to access the host system for the purpose of capturing screens and recording screen operations files. The host connection properties file also stores configuration properties that define the connection to the Enterprise Information System (EIS) at run time.
host editor
In Enterprise Service Tools, an editor that a software developer uses to interact with the EIS application as a user of that application and to record one or more action sets (navigational keystrokes) for each description. The output screen descriptions are also recorded. For each screen either an imported resource is associated or descriptors is defined, or the developer can optionally choose to have screens captured automatically if no association can be made to an existing schema. A developer uses the flow recording feature of the host editor to build the flow in a manner that resembles using the host application. The developer can start with or without an existing screen operations file and any required screens, screen descriptions, and screen operations files will be created or updated. (You must select a setting in Windows > Preferences > Enterprise Service Tools > Service Flow Projects that enables automatic screen captures.) At the end of the use case, the flow path through the application screens has been captured as metadata.
host name
In Internet communication, the name given to a computer. Sometimes, host name is used to mean the fully qualified domain name; other times, it is used to mean the most specific subname of a fully qualified domain name. For example, if mycomputer.city.company.com is the fully qualified domain name, either of the following host names can be used: mycomputer.city.company.com or mycomputer.
hover help
A form of online help that can be viewed by moving a cursor over a GUI item such as an icon or field.
HTML
See Hypertext Markup Language.
HTTP
See Hypertext Transfer Protocol.
HTTP over SSL (HTTPS)
A Web protocol for secure transactions that encrypts and decrypts user page requests and pages returned by the Web server.
HTTPS
See HTTP over SSL.
Hypertext Markup Language (HTML)
A markup language that conforms to the Standard Generalized Markup Language (SGML) standard and was designed primarily to support the online display of textual and graphical information, including hypertext links.
Hypertext Transfer Protocol (HTTP)
An Internet protocol that is used to transfer and display hypertext and XML documents on the Web.
IDE
See integrated development environment.
importer
In Enterprise Service Tools, a set of components that you can use to populate parts of the information model from existing resources. These resources can be data format definitions for messages or control blocks used by host applications, screen format definitions, for either entire screens or parts of screens, existing navigation information such as emulator macros, or captures of actual screens. For format definitions and screen captures, when the resource is imported, a schema is created. When navigation information is imported, flow info, WSDL and, if possible, schema are created.
import project
To add predefined property values, subprojects, and resources to a project.
import project definition
To add predefined property values to a project.
incremental build
In Eclipse, a build in which only resources that have changed since the last build are considered. See also full build.
infopop
A small window that displays context-sensitive help for a particular UI element and links to related online help topics.
information center
A collection of information that provides support for users of one or more products, can be launched separately from the product, and includes a list of topics for navigation and a search engine.
inheritance
An object-oriented programming technique that allows the use of existing classes as a basis for creating other classes.
inherited property
A property value that cascades from a container, such as a folder or subproject.
instance document
An XML document that conforms to a particular schema.
integrated development environment (IDE)
A set of software development tools, such as source editors, compilers, and debuggers, that are accessible from a single user interface.
Interactive System Productivity Facility (ISPF)
In zIDE, an IBM licensed program that serves as a full-screen editor and dialog manager. Used for writing application programs, it provides a means of generating standard screen panels and interactive dialogs between the application programmer and terminal user. ISPF consists of four major components: DM, PDF, SCLM, and C/S. The DM component is the Dialog Manager, which provides services to dialogs and end-users. The PDF component is the Program Development Facility, which provides services to assist the dialog or application developer. The SCLM component is the Software Configuration Library Manager, which provides services to application developers to manage their application development libraries. The C/S component is the Client/Server, which allows you to run ISPF on programmable workstation, to display the panels using the display function of your workstation operating system, and to integrate workstation tools and data with host tools and data.
interface
In Enterprise Service Tools, the contract between the service requester and the service provider expressed as a defined set of operations and the defined message formats for each operation. An Interface component describes sequences of messages that a service sends or receives. It does this by grouping related messages into operations. An operation is a sequence of input and output messages, and an interface is a set of operations. Thus, an interface defines the design of the application.
interim fix
A certified fix that is generally available to all customers between regularly scheduled fix packs, refresh packs, or releases. See also fix pack, refresh pack.
Internet Protocol (IP)
A protocol that routes data through a network or interconnected networks. This protocol acts as an intermediary between the higher protocol layers and the physical network. See also Transmission Control Protocol.
interoperability
The ability of a computer or program to work with other computers or programs.
interpreter
A program that translates and runs each instruction of a high-level programming language before it translates and runs the next instruction.
invoking a service
In Enterprise Service Tools, an action that a service requester performs to activated the service flow so that it can run the business operations that are necessary to fulfill what is being requested by the service requester. In order to invoke a service, the service requester sends a message through a messaging interface. A service flow supports the following message interface mechanisms:
  • Java Message Service (JMS) – A messaging standard that allows application components based on the Java 2 Platform, Enterprise Edition (J2EE) to create, send, receive, and read messages. It enables distributed communication that is loosely coupled, reliable, and asynchronous.
  • WebSphere MQ (CICS-MQ bridge) – A component of WebSphere MQ for z/OS that allows direct access from WebSphere MQ applications (the service requester in this scenario) to applications on your CICS system (the service flow). In bridge applications no WebSphere MQ calls exist within the CICS application (the bridge enables implicit MQI support). This means that you can re-engineer existing applications that were controlled by 3270-connected terminals to be controlled by WebSphere MQ messages without having to rewrite, recompile, or relink them.
  • J2C via CICS Transaction Gateway (CTG) – An interface that processes the application's External Call Interface (ECI) and External Presentation Interface requests, and transmits them to the server system using an appropriate communication protocol.
  • SOAP support in CICS – Support for a lightweight XML-based messaging protocol that is used to encode the information in Web service request and response messages before sending them over a network. SOAP messages are independent of any operating system or protocol and can be transported by using a variety of Internet protocols, including SMTP, MIME, HTTP, and JMS.
  • COMMAREA Invoke – A CICS area that is used to pass data between tasks that communicate with a given terminal. The area can also be used to pass data between programs within a task. At run time, the CICS Service Flow Runtime Stub program requires that information from the service requester be passed in the form of a communication area (COMMAREA).
Invoke node
In Enterprise Service Tools, a node that invokes an operation with an EIS application.
IP
See Internet Protocol. See also Transmission Control Protocol.
isomorphic
Each composed element (in other words, an element containing other elements) of the XML instance document starting from the root directory has one and only one corresponding COBOL group item whose nesting depth is identical to the nesting depth of its XML equivalent. Each non-composed element (in other words, an element that does not contain other elements) in the XML instance document starting from the top has one and only one corresponding COBOL elementary item whose nesting depth is identical to the nesting level of its XML equivalent and whose memory address at run time can be uniquely identified.
ISPF
See the Interactive System Productivity Facility entry.
ISPF editor profile
A System z LPEX Editor profile that simulates ISPF key settings.
item
In EGL, a named area of memory that contains a single value.
J2C (JCA)
See J2EE Connector architecture.
J2EE
See Java 2 Platform, Enterprise Edition. See also Java 2 Platform, Standard Edition.
J2EE application
Any deployable unit of J2EE functions. This unit can be a single module or a group of modules packaged into an enterprise archive (EAR) file with a J2EE application deployment descriptor. (Sun)
J2EE Connector architecture (J2C, JCA)
A standard architecture for connecting the J2EE platform to heterogeneous enterprise information systems (EIS).
J2EE Request Profiler
The name of an agent that is attached to the application server process for the purpose of collecting data on the interception points of the application's requests.
J2EE server
A runtime environment that provides EJB or Web containers.
J2SE
See Java 2 Platform, Standard Edition. See also Java 2 Platform, Enterprise Edition, Java Development Kit.
JAR file
A Java archive file. See also enterprise archive, Web archive.
Java
An object-oriented programming language for portable interpretive code that supports interaction among remote objects. Java was developed and specified by Sun Microsystems, Incorporated.
Java 2 Platform, Enterprise Edition (J2EE)
An environment for developing and deploying enterprise applications, defined by Sun Microsystems Inc. The J2EE platform consists of a set of services, application programming interfaces (APIs), and protocols that provide the functions for developing multitiered, Web-based applications. (Sun) See also Java 2 Platform, Standard Edition.
Java 2 Platform, Standard Edition (J2SE)
The core Java technology platform. (Sun) See also Java 2 Platform, Enterprise Edition, Java Development Kit.
Java archive
A compressed file format for storing all of the resources that are required to install and run a Java program in a single file. See also enterprise archive, Web archive.
Java bean
See also enterprise bean, JavaBeans. See bean.
JavaBeans
As defined for Java by Sun Microsystems, a portable, platform-independent, reusable component model. See also bean.
Java class
A class that is written in the Java language.
Java Database Connectivity (JDBC)
An industry standard for database-independent connectivity between the Java platform and a wide range of databases. The JDBC interface provides a call-level API for SQL-based and XQuery-based database access.
Java Development Kit (JDK)
The name of the software development kit that Sun Microsystems provided for the Java platform, up to and including v 1.1.x. See also Java 2 Platform, Standard Edition.
Javadoc
A tool that parses the declarations and documentation comments in a set of source files and produces a set of HTML pages describing the classes, inner classes, interfaces, constructors, methods, and fields. (Sun)
Java file
An editable source file (with .java extension) that can be compiled into bytecode (a .class file).
Java Naming and Directory Interface (JNDI)
An extension to the Java platform that provides a standard interface for heterogeneous naming and directory services.
Java project
In Eclipse, a project that contains compilable Java source code and is a container for source folders or packages.
Java runtime environment (JRE)
A subset of a Java developer kit that contains the executable files and other files that constitute the Java platform. The JRE includes a Java virtual machine, core classes, and supporting files.
JavaScript™
A Web scripting language that is used in both browsers and Web servers. (Sun)
JavaServer Faces (JSF)
A framework for building Web-based user interfaces in Java. Web developers can build applications by placing reusable UI components on a page, connecting the components to an application data source, and wiring client events to server event handlers. See also JavaServer Pages, Faces component, Faces JSP file.
JavaServer Pages (JSP)
A server-side scripting technology that enables Java code to be dynamically embedded within Web pages (HTML files) and executed when the page is served, in order to return dynamic content to a client. See also JSP file, JSP page, JavaServer Faces.
Java virtual machine (JVM)
A software implementation of a processor that runs compiled Java code (applets and applications).
JCL (job control language)
In Enterprise Service Tools, a command language that is used to identify a job to an operating system and to describe the job's requirements.
JDBC
See Java Database Connectivity.
JDBC connection filter
A control that limits the amount of data that is transferred during the JDBC metadata load. The filter enhances performance.
JDK
See Java Development Kit. See also Java 2 Platform, Standard Edition.
JES
Job Entry System.
JES job filter
Defines high-level qualifiers for displaying jobs in the Job Monitor view.
JNDI
See Java Naming and Directory Interface.
job control language (JCL)
In Enterprise Service Tools, a command language that is used to identify a job to an operating system and to describe the job's requirements.
join
An SQL relational operation that allows retrieval of data from two or more tables based on matching column values.
JRE
See Java runtime environment.
JSF
See JavaServer Faces. See also JavaServer Pages, Faces component, Faces JSP file.
JSP
See JavaServer Pages. See also JSP file, JSP page, JavaServer Faces.
JSP file
A scripted HTML file that has a .jsp extension and allows for the inclusion of dynamic content in Web pages. A JSP file can be directly requested as a URL, called by a servlet, or called from within an HTML page. See also JavaServer Pages, JSP page.
JSP page
A text-based document using fixed template data and JSP elements that describes how to process a request to create a response. (Sun) See also JavaServer Pages, JSP file.
JUnit
An open-source regression testing framework for unit-testing Java programs.
JVM
See Java virtual machine.
keyboard shortcut
A key or combination of keys that a user can press to perform an action that is available from a menu.
key field
In EJB, a container-managed field in an entity bean that corresponds to one of the primary-key columns of a row in a relational database. Each key field is a member of the entity bean's key class.
key file
See also keystore file. See key ring.
key ring
In computer security, a file that contains public keys, private keys, trusted roots, and certificates. See also keystore file.
keystore file
A key ring that contains both public keys stored as signer certificates and private keys stored in personal certificates.
launch configuration
A mechanism for defining and saving different workbench configurations that can be launched separately. Configurable options include run and debug settings.
layout box
In Page Designer, a control that Web designers can use to move text and images within the page. Layout boxes can be stacked or aligned by using a grid.
LDAP
See Lightweight Directory Access Protocol.
LDAP directory
A type of repository that stores information about people, organizations, and other resources and that is accessed using the LDAP protocol. The entries in the repository are organized into a hierarchical structure, and in some cases the hierarchical structure reflects the structure or geographical area of an organization.
Lightweight Directory Access Protocol (LDAP)
An open protocol that uses TCP/IP to provide access to directories that support an X.500 model and that does not incur the resource requirements of the more complex X.500 Directory Access Protocol (DAP). For example, LDAP can be used to locate people, organizations, and other resources in an Internet or intranet directory.
link
To interconnect items of data or portions of one or more computer programs, for example, the linking of object programs by a linkage editor or the linking of data items by pointers.
Link3270 Bridge
In Enterprise Service Tools, a programming interface that allows a CICS client to communicate with 3270-based CICS transactions.
linkage options part
In EGL, a build part that gives details on how a generated program calls and is called by other programs. The part also gives details on how a generated COBOL program accesses files on remote CICS regions. The information in this part is used at generation time, test time, and run time.
linkage properties file
An EGL-generated or handwritten text file that can be used at J2EE run time to give details on how an EGL-generated Java program or wrapper calls other code.
linkage section
The section in the data division of an activated unit (a called program or an invoked method) that describes data items available from the activating unit (a program or a method). These data items can be referred to by both the activated unit and the activating unit.
listener port
An object that defines the association between a connection factory, a destination, and a deployed message-driven bean. Listener ports simplify the administration of the associations between these resources.
load
Load is defined in the following ways:
  1. To move data or programs into storage.
  2. To bring all or part of a computer program into memory from auxiliary storage so that the computer can run the program.
load library
A library containing load modules.
local
Pertaining to a device, file, or system that is accessed directly from a user's system, without the use of a communication line. See also remote.
local history
Copies of files that are saved in the workbench in order to compare the current version with previous versions. Subject to configurable preferences, the workbench updates the local history each time an editable file is saved.
local home interface
In EJB, an interface that specifies the methods used by local clients for locating, creating, and removing instances of enterprise bean classes. See also remote home interface.
local syntax check
Uses the Windows COBOL or PL/I compiler to check the syntax of resources.
local z/OS project
A z/OS project used to develop COBOL or PL/I code that resides and runs on the workstation. Local projects are not related to a remote system.
lock action
An action that locks a member.
logging level
A preference setting that specifies the number of entries and the amount of detail generated by various loggers.
logic part
An EGL declaration that defines a runtime sequence. The types of logic parts are program, function, library, and page handler.
logical format
In Enterprise Service Tools, the logical organization of the message content.
logical ordering scheme
A mechanism for storing text in the order it is intended to be read.
loop
A sequence of instructions performed repeatedly until an ending condition is reached.
LPEX editor
An extensible editor that provides language parsing, view filtering, embedded informational and error messages, keyboard and command profiles, search and marking facilities, and keystroke-recording facilities. LPEX is the base for the System z LPEX Editor.
managed synchronization
The use of mapping files to synchronize a local z/OS project with a remote system.
manifest
A special file that can contain information about the files packaged in a JAR file. (Sun) Types of manifest include Application Deployment Manager, bundle, feature, and plug-in.
map
Map is defined in the following ways:
  1. In BMS, a format established for a page or a portion of a page, or a set of screen format descriptions. A map relates program variables to the positions in which their values are displayed on a display device. A map contains other formatting information such as field attributes. A map describes constant fields and their position on the display, the format of input and output fields, the attributes of constant and variable fields, and the symbolic names of variable fields.
  2. A specialized task that transforms data from one structure to another.
mapping
Mapping is defined in the following ways:
  1. In BMS, the process of transforming field data to and from its displayable form.
  2. The process of transforming data from one application-specific format to another.
  3. In Enterprise Service Tools, the act of the user who models data transformation between an output message (represented by output terminal on one node) and an input message (represented by an input terminal on another node). Data transformation can include a variety of functions:
    • Associating a field in one message with a field in another message.
    • String mapping such as specifying pad characters.
    • Date mapping, such as converting a date in one format to a date in another format.
    • Putting literal data into a message.
    • Adding custom code to perform other data transformation functions.
mapping cardinality
In Enterprise Service Tools, the granularity of the way that message elements are mapped from message source to message target. For example, one source element to one target element, or many source elements to one target element.
marker bar
The gray border at the left of the editor area of the workbench, where bookmarks and breakpoints are shown.
master build descriptor
In EGL, a build descriptor part whose options cannot be overridden.
meet-in-the-middle mapping
An approach for mapping enterprise beans to database tables in which enterprise beans and database schema are created simultaneously but independently.
Menu Manager
A feature of Rational Developer for System z that enables you to add custom menus and menu items to the z/OS Projects view and System z LPEX Editor.
message
In Enterprise Service Tools, a set of data that is passed from one application to another. A message can be modeled by a message definition file that describes the structure and content of the message. Messages must have a structure and format which is agreed by the sending and receiving applications.
message definition file
In Enterprise Service Tools, a logical description of a message. A message definition file is a structured collection of simple elements. It is a file that contains the messages, elements, types, and groups that make up a message set. The message definition file contains information about the structure (logical and physical) of the message model. You can create one or more message definition files to represent different formats of the message model, such as XML, COBOL, or C.
message format
In Enterprise Service Tools, the definition of the internal structure of a message, in terms of the fields and the order of those fields. A format can be self-defining, in which case the message is interpreted dynamically when it is read.
message set
In Enterprise Service Tools, a container; a logical grouping of messages and associated message resources (elements, types, groups). The message set contains or "holds" the message definition files.
metadata
Data that describes the characteristics of data; descriptive data.
method
In Java programming, a function that is defined in a class. (Sun)
In object-oriented programming, an operation that an object can perform. An object can have many methods.
MIME
See Multipurpose Internet Mail Extensions.
model view controller (MVC)
A software architecture that separates the components of the application: the model represents the business logic or data; the view represents the user interface; and the controller manages user input or, in some cases, the application flow.
module
Module is defined in the following ways:
  1. A program unit that is discrete and identifiable with respect to compiling, combining with other units, and loading.
  2. In programming languages, a language construct that consists of procedures or data declarations and that interact with other such constructs.
  3. In ESQL, a module is a named container of code. In the service flow project tools, this name is associated with a particular condition expression in a particular node (Switch or While) and returns a boolean value.
monitor
In performance profiling, to collect data about an application from the running agents that are associated with that application.
Multipurpose Internet Mail Extensions (MIME)
An Internet standard that allows different forms of data including video, audio, or binary data to be attached to e-mail without requiring translation into ASCII text.
MRM
In Enterprise Service Tools, the name given to the domain and parser associated with messages that are modeled in the workbench. MRM stands for Message Repository Manager and is used only to identify the MRM parser and MRM domain.
MRM domain
In Enterprise Service Tools, the message domain that includes all messages that are modeled in the workbench. Message models can be created to represent a wide range of message types, with one or more optional physical formats. Messages in this domain are processed by the MRM parser.
MRM parser
In Enterprise Service Tools, a program that interprets a bit stream or tree that represents a message that belongs to the MRM domain, and generates the corresponding tree from the bit stream on input, or bit stream from the tree on output. Its interpretation depends on the physical format that you have associated with the input or output message.
MVC
See model view controller.
MVS subproject
A subproject containing z/OS MVS resources.
namespace
Space reserved by a file system to contain the names of its objects.
In XML and XQuery, a uniform resource identifier (URI) that provides a unique name to associate with the element, attribute, and type definitions in an XML schema or with the names of elements, attributes, types, functions, and errors in XQuery expressions.
For Enterprise Service Tools: In XML, a uniform resource identifier (URI) that provides a unique name to associate with all the elements and type definitions in a schema. XML instance documents and XML schemas can make use of namespaces.
naming service
An implementation of the Java Naming and Directory Interface (JNDI) standard.
navigation bar
A set of links to other Web pages in a Web site. For example, navigation bars are typically located across the top or down the side of a page and contain direct links to the major sections within the Web site.
navigator view
Provides a hierarchical view of the resources in the Workbench.
node
In Enterprise Service Tools, one of a series of graphical elements in a flow diagram. A node represents an endpoint or junction used in a flow. Developers using the flow editor component of the service flow project tools can drag nodes from the Flow palette onto the flow editor area.
non-isomorphic
A simple mapping of COBOL items and XML elements belonging to XML documents and COBOL groups that are not identical in shape (non-isomorphic). Non-isomorphic mapping can also be created between non-isomorphic elements of isomorphic structures.
notation
A system of characters, symbols, or abbreviated expressions used to express technical facts or qualities.
numeric shaping
A characteristic of numbers that indicates whether they must be presented using the European digit shapes or the Arabic-Indic digit shapes.
object
In object-oriented design or programming, a concrete realization (instance) of a class that consists of data and the operations associated with that data. An object contains the instance data that is defined by the class, but the class owns the operations that are associated with the data.
object-oriented programming
A programming approach based on the concepts of data abstraction and inheritance. Unlike procedural programming techniques, object-oriented programming concentrates not on how something is accomplished but instead on what data objects compose the problem and how they are manipulated.
offline project
In zIDE, a project that is not connected to a remote system; the project can only access mainframe resources that were explicitly taken offline.
online project
In zIDE, a project that is connected to a remote system; you can directly change the data sets that are stored in the remote system.
open source
Pertaining to software source code that is available to the general public and does not have licensing restrictions that limit use, modification, or redistribution. Linux® is an example of an open source technology.
operation
In Enterprise Service Tools, a service that can be requested from an object to effect behavior. A web service can have multiple operations. An operation has a signature, which may restrict the actual parameters that are possible. EIS operations are generally not independent of each other. Only certain sequences are possible and the business client end of the conversation must be kept active for the duration of the conversation. This implies that the developers view of stateless connections and stateful ones should not be the same. Operations on a stateless connection are complete operations like those implemented by an EIS service.
ordering scheme
A mechanism that defines the relationship between the order of text as stored in memory or on external media and its order for correct display.
output console view
Displays the output of a process and allows you to provide keyboard input to a process.
output view
Displays messages, parameters, and results that are related to the objects that you work with.
package
To assemble components into modules and modules into J2EE applications.
In Java programming, a group of types. Packages are declared with the package keyword. (Sun)
page
Page is defined in the following ways:
  1. A fixed-length block of instructions, data, or both instructions and data that can be transferred between active physical memory and external page storage.
  2. A defined unit of space on a storage medium or within a database volume.
  3. In a graphical interface, a predefined display image that typically provides fields and controls that help users accomplish tasks.
  4. To transfer instructions, data, or both between active physical memory and external page storage.
page template
In Page Designer, a page that is used as a starting point to define consistent styles and layout for any new HTML or JavaServer Pages (JSP) page within a Web site.
palette
A range of graphically displayed choices, such as colors or collections of tools, that can be selected in an application.
parameter (parm)
A value or reference passed to a function, command, or program that serves as input or controls actions. The value is supplied by a user or by another program or process.
parm
See parameter.
parse
To break down a string of information, such as a command or file, into its constituent parts.
partitioned data set (PDS)
For Enterprise Service Tools in a z/OS environment, a data set in direct-access storage that is divided into partitions that are called members. Each partition can contain a program, part of a program, or data.
PCB
See program communication block. See also program specification block.
persist
To be maintained across session boundaries, typically in nonvolatile storage such as a database system or a directory.
persistence
A characteristic of data that is maintained across session boundaries, or of an object that continues to exist after the execution of the program or process that created it, typically in nonvolatile storage such as a database system.
In J2EE, the protocol for transferring the state of an entity bean between its instance variables and an underlying database. (Sun)
In Enterprise Service Tools, an instance state of data that is maintained across session boundaries, or an instance state of an object that continues to exist after the execution of the program or process that created it, typically in nonvolatile storage such as a database system. In the service flow project tools, the term persistent characterizes whether the transactional instance data will be persisted in a BTS repository data set for the named process under which the service flow is executing. A developer should make an adapter nonpersistent if he or she is not concerned with maintaining data if the process under which the adapter is running fails. Session state information is a good example of persisted state data.
perspective
A group of views that show various aspects of the resources in the workbench. The workbench user can switch perspectives, depending on the task at hand, and customize the layout of views and editors within the perspective.
physical format
In Enterprise Service Tools, the way in which the message data is physically organized for sending. The supported physical formats are Custom Wire Format, XML Wire Format, and Tagged/Delimited String Format.
plug-in
A software module that adds function to an existing program or application.
pop-up menu
A menu that appears as the result of some user action (typically clicking the right mouse button) and that contains choices appropriate for the selected object in its current context.
port
An end point for communication between applications, generally referring to a logical connection. A port provides queues for sending and receiving data. Each port has a port number for identification.
portal
A single, secure point of access to diverse information, applications, and people that can be customized and personalized.
portlet mode
A form assumed by a portlet to provide a distinctive interface for users to perform different tasks. Portlet modes can include view, edit, and help.
port type
An element in a Web Services Description Language (WSDL) document that comprises a set of abstract operations, each of which refers to input and output messages that are supported by the Web service.
For Enterprise Service Tools, an element in a WSDL document that defines a set of abstract operations that a Web service makes available. Each abstract operation is associated with input and output messages that are supported by the service. The type of a port is the interface that the port provides. An interface is a logical grouping of operations. An interface represents an abstract service type, independent of transmission protocol and data format.
POST
In HTTP, a parameter on the METHOD attribute of the FORM tag that specifies that a browser will send form data to a server in an HTTP transaction separate from that of the associated URL.
primary key
An object that uniquely identifies an entity bean within a home. (Sun)
In a relational database, a key that uniquely identifies one row of a database table. See also foreign key.
primary part
An EGL part whose name is the same as the source file in which the part resides. The primary parts are data table, form group, library, page handler, program, and UI record.
primitive type
In Java, a category of data type that describes a variable that contains a single value of the appropriate size and format for its type: a number, a character, or a Boolean value. Examples of primitive types include byte, short, int, long, float, double, char, boolean.
probe
A monitor that tests a transaction and then detects and reports any errors that were generated during that test.
program communication block (PCB)
A control block that contains pointers to Information Management System (IMS™) databases. See also program specification block.
program specification block (PSB)
In DL/I and IMS, a control block that identifies the destinations and databases used by the application program. A PSB consists of one or more program communication blocks (PCBs). See also program communication block.
program temporary fix (PTF)
For System i®, System p®, and System z products, a fix that is tested by IBM and is made available to all customers. See also fix pack.
project
In Eclipse, a unit of organization used to group folders or packages. Projects are used for building, version management, sharing, and organizing resources.
project definition file
In zIDE, a host-based project configuration file that lists the subprojects contained by a host-based project.
project instance file
In zIDE, a host-based project configuration file that defines the set of projects to be downloaded when a user connects to the remote system.
property group
In zIDE, a named set of build properties that you can use to define and save multiple build configurations for a project, subproject, or file.
proxy server
A server that receives requests intended for another server and that acts on the client's behalf (as the client's proxy) to obtain the requested service. A proxy server is often used when the client and the server are incompatible for direct connection. For example, the client is unable to meet the security authentication requirements of the server but should be permitted some services.
PSB
See program specification block. See also program communication block.
PTF
See program temporary fix. See also fix pack.
public
In object-oriented programming, pertaining to a method or variable that is accessible to all classes.
push button
In a window or dialog box, a rectangular control that, when clicked, immediately causes an action to be performed. Push buttons can be labeled with text, graphics, or both. The most familiar push buttons are OK and Cancel.
pushable manifest editor
A tool for creating mapping files for synchronizing local z/OS projects with remote systems.
queue
A line or list of items waiting to be processed; for example, work to be performed or messages to be displayed or transmitted.
RAM
See repository access manager.
RDB
See relational database.
Receive node
In Enterprise Service Tools, a node that represents an input message for a flow.
record
In Enterprise Service Tools, a schema or message that corresponds to a known COBOL COMMAREA data structure. A record also defines a set of record descriptions that describe different states for that record.
record boundary indicator
In System z LPEX Editor, a visual indicator of a file's record length limit.
record description
In Enterprise Service Tools, a set of record recognition criteria combined with Boolean operators which are used as a profile of the state of a record.
recursion
A programming technique in which a program or routine calls itself to perform successive steps in an operation, with each step using the output of the preceding step.
refactor
To transform a program, for example by renaming a package or method, while preserving its behavior.
refactoring
In Enterprise Service Tools, a process that propagates a file name change to all referencing artifacts when you are renaming an operations file or operation within a file. This prevents breaks in the project.
referential integrity
In Extensible Markup Language (XML) tools, the condition that exists when all references to items in the XML schema editor or DTD editor are automatically cleaned up when the schema is detected or renamed.
The condition that exists when all intended references from data in one column of a table to data in another column of the same or a different table are valid.
refresh pack
A cumulative collection of fixes that contains new functions. See also fix pack, interim fix.
relational database (RDB)
A database that can be perceived as a set of tables and manipulated in accordance with the relational model of data. Each database includes a set of system catalog tables that describe the logical and physical structure of the data, a configuration file containing the parameter values allocated for the database, and a recovery log with ongoing transactions and archivable transactions.
remote
Of or pertaining to a system, program, or device that is accessed through a communication line.
Remote Error List
A z/OS Projects view that displays the results of remote build and syntax check operations.
remote file system
A file system residing on a separate server or operating system.
remote file transfer instance
A file that contains information about the method used for remotely transferring a file.
remote home interface
In enterprise beans, an interface that specifies the methods used by remote clients for locating, creating, and removing instances of enterprise bean classes. See also local home interface.
remote index search
A search on remote RSE filters or folders using a preexisting index.
remote interface
In EJB, an interface that defines the business methods that can be called by a client. See also home interface.
Remote Job Monitor
A z/OS subsystem that provides you with access to your jobs in JES.
remote method
A business method in the remote interface that is callable by a client.
Remote Procedure Call (RPC)
A protocol that allows a program on a client computer to run a program on a server.
remote synchronization
A set of tools that you can use to quickly transfer resources from a local project to a remote system in a systematic, repeatable way.
remote syntax check
An action that uses Rational Developer for System z JCL procedure support to submit resources to a z/OS-based compiler for syntax checking.
remote system
Any other system in the network with which your system can communicate.
Remote System Details view
A z/OS Projects view that shows currently defined remote systems and allows you to display detailed information about their subsystems.
Remote System Explorer
A tool that provides an interface for connecting to and managing remote systems using conventions that are similar to ISPF.
Remote Systems view
A view in the Remote Systems Explorer perspective that lists defined connections to remote systems.
Reply node
In Enterprise Service Tools, a node that represents an output message where responses leave the flow.
repository
  1. A storage area for data. Every repository has a name and an associated business item type. By default, the name will be the same as the name of the business item. For example, a repository for invoices will be called Invoices. There are two types of information repositories: local (specific to the process) and global (reusable).
  2. A VSAM data set on which the states of BTS processes are stored. When a process is not executing under the control of BTS, its state (and the states of its constituent activities) are preserved by being written to a repository data set. The states of all processes of a particular process-type (and of their activity instances) are stored on the same repository data set. Records for multiple process-types can be written to the same repository.
  3. A persistent storage area for source code and other application resources. In a team programming environment, a shared repository enables multi-user access to application resources.
  4. A collection of information about the queue managers that are members of a cluster. This information includes queue manager names, their locations, their channels, what queues they host, and so on.
repository access manager
A piece of software that provides connections to a specific type of SCM, such as SCLM.
repository instance
A project or component that exists in an SCM.
response file
  1. A file that contains a set of predefined answers to questions asked by a program and that is used instead of entering those values one at a time.
  2. An ASCII file that you can customize with the setup and configuration data that automates an installation. You can enter the setup and configuration data interactively during installation or use a response file that permits the installation to proceed without any intervention.
resource
The collective term for projects, folders, subfolders, and files that can be manipulated in the Eclipse workbench.
resource adapter
A system-level software driver that an EJB container or an application client uses to connect to an enterprise information system (EIS). A resource adapter plugs in to a container; the application components deployed on the container then use the client API (exposed by adapter) or tool-generated, high-level abstractions to access the underlying EIS. (Sun) See also container, enterprise information system.
resource property
A characteristic of a system, project, subproject, or file. In Rational Developer for System z, certain resource properties are defined in a property group. Resource properties are created for each resource when the resource is first accessed and maintained until the resource is deleted.
result set
The set of rows that a procedure returns.
role
A job function that identifies the tasks that a user can perform and the resources to which a user has access. A user can be assigned one or more roles.
root configuration file
In zIDE, a host-based project configuration file that defines the folder in which all other host-based project definition files are located.
root node
In a graphical representation of data as a tree, a node that has no parents but typically has children.
RPC
See Remote Procedure Call.
RSE
See Remote System Explorer.
run time
In Enterprise Service Tools, the time period during which a service flow instance is operational with business transactions being managed and completed in the application server.
runtime
In Enterprise Service Tools: Of or pertaining to a supported environment in which a service flow modeled and generated using the service flow project tools cab be run.
schema
A collection of database objects such as tables, views, indexes, or triggers that define a database. A database schema provides a logical classification of database objects.
In Enterprise Service Tools, a logical grouping for user-defined functions, distinct types, triggers, and stored procedures. When an object of one of these types is created, it is assigned to one schema, which is determined by the name of the object. For example, in the service flow project tools, when the developer imports screens, the imported objects are assigned to the .mxsd schema, which is a language for describing XML files that contain schema.
SCM
See software configuration management.
SCLM
The Software Configuration Library Manager.
scope
A part of a source program in which an object is defined and recognized.
scrapbook
An editor that can be used to experiment and evaluate Java expressions. Workbench users can run, inspect, and display snippets of code in the scrapbook.
screen
In Enterprise Service Tools in its native state, the user interface to a 3270 or 5250 application on a host system. A single host application can contain many screens, each of which has a purpose within the context of the application. Screens contain both text and control (or formatting functions) and traditionally display as "green screens" on 3270 or 5250 terminals. In the service flow project tools a screen represents a schema or message that corresponds to a known terminal screen structure. Keep in mind that a single screen can have more than one state. Using the service flow project tools, you can address multiple states of a single screen by assigning a description that corresponds to each screen state. Therefore, a single screen can have multiple screen descriptions.
screen action
In Enterprise Service Tools, information stored in a recorded screen operations file. The stored information represents a particular user interaction with a screen, such as entering text, pressing an AID key, cursor repositioning, and so on. This stored information can be played back, or executed, on the same host screen to automate that user interaction.
screen interaction
In Enterprise Service Tools, a set of screen actions that make up the total user interaction necessary to process a given screen. A screen interaction is restricted to having a single AID key action. In total, the screen interaction describes the user interaction with a screen, which can have one of the following results:
  • A transition from the screen to a potential output screen
  • Extracting data from the screen
screen message editor
In Enterprise Service Tools, a component with which you can modify artifacts in the information model that only apply to screens or screen maps. Use the screen message editor (no host connection is necessary) to edit the screen definitions that you have previously saved to the workbench or those that the service flow project tools tool generated automatically. The editing tasks include editing the screen definition information (that is, field names) and defining and modifying descriptors or defining variations on a basic screen. By editing the screen definition you can make the information from the screen more usable for development tasks that may be performed later on.
screen operation
In the service flow project tools of Enterprise Service Tools, an operation that represents all of the possible paths (the allowed user interactions) from a single screen. A screen operation refers to one screen description of a particular state, specifying the screen state, zero to N screen interactions representing the possible user interactions with that screen, and zero to N screen descriptions representing of the potential screen outputs. A set of screen operations represents a screen operations file. In the service flow project tools, a screen operation is stored as a WSDL operation within a WSDL document.
screen operations editor
In Enterprise Service Tools, an editor that you can use offline to create operations for each screen description, with associated screen interactions and next screen descriptions.
screen operations file
In Enterprise Service Tools, a file that contains set of screen operations with no more than one operation corresponding to a given screen description. Most EIS applications contain multiple business functions. A screen operations file represents all of the paths (the allowed user interactions) through those screens that are part of a single business function. In the service flow project tools, these paths are stored as a WSDL document and therefore can be used as input to a flow of the EIS application. It is possible that the same screen or screens can be part of two separate business functions. The flow editor enables you to use of the same screen(s) in multiple screen operations files.
script
A series of commands, combined in a file, that carry out a particular function when the file is run. Scripts are interpreted as they are run.
scriptlet
A mechanism for adding scripting language fragments to a source file.
SDK
See software development kit.
Secure Sockets Layer (SSL)
A security protocol that provides communication privacy. With SSL, client/server applications can communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery.
self-defining message
In Enterprise Service Tools, an element or message for which no matching definition exists in the message model. For example, a message coded in XML is self-defining.
sequence numbers
A System z LPEX Editor preference for maintaining sequence numbers in files that have valid standard sequence numbers on all lines.
serializer
A method for converting object data to another form such as binary or XML. See also deserializer.
server
A definition that identifies where an application will be tested or published. See also host.
The server is the Rational Developer for System z component that operates on a z/OS system.
server configuration
A resource that contains information required to set up and deploy to an application server.
server project
A project that contains information about test and deployment servers and their configurations.
server-side
Pertaining to an application or component of an application that runs on a server rather than on the client. JSP and servlets are two examples of technologies that enable server-side programming.
servers view
A view that displays a list of all your servers and the configurations that are associated with them.
service description
The description of a Web service, which can be defined in a format such as WSDL, UDDI, or HTML.
service flow
In Enterprise Service Tools, the generated output of the runtime code generator of the service flow project tools. A service flow is a reusable composed business function that exposes a programmatic interface to a service requester in an Enterprise Information System. The service flow is deployed to, and works with, service flow project tools-supported runtime environments. The service flow can have characteristics that can support both metadata and generated code deployments. The service flow has port binding's specific to each potential deployment environment. WSDL binding information can be extended to save any of the additional metadata required to support application code generation or other deployment or runtime behavior. The service flow contains business services composed from a set of supported connector flow services. The service flow is composed from runtime patterns with varying degrees of complexity and persistence. The level of abstraction needed by a given customer for the business operations will determine if connector flows are sufficient or if connector flows all driving the same EIS, need to be combined into service flows.
service flow modeler
In Enterprise Service Tools, the logical concept of a set of tools for building ("modeling") service flows. The service flow project tools in the Enterprise Service Tools perspective are a real-life implementation of the concept of a service flow modeler.
service provider
In Enterprise Service Tools, the application that hosts access to a Web service. A service provider describes its service using WSDL. This definition is published to a directory of services. The directory could use Universal Description, Discovery, and Integration (UDDI). Other forms of directories can also be used.
service requester
In Enterprise Service Tools, an application that is looking for and invoking or initiating an interaction with a Web service provider. The requester role can be played by a browser driven by a person or a program without a user interface, for example, another Web service. A service requester issues one or more queries to locate a service and determine how to communicate with that service.
servlet
A Java program that runs on a Web server and extends the server's function by generating dynamic content in response to Web client requests. Servlets are commonly used to connect databases to the Web.
servlet container
A Web application server component that invokes the action servlet and that interacts with the action servlet to process requests.
session
A logical or virtual connection between two stations, programs, or devices on a network that allows the two elements to communicate and exchange data.
In J2EE, an object used by a servlet to track a user's interaction with a Web application across multiple HTTP requests.
session bean
An enterprise bean that is created by a client and that typically exists only for the duration of a single client/server session. (Sun)
setter method
A method whose purpose is to set the value of an instance or class variable. This capability allows another object to set the value of one of its variables. See also getter method.
shell
A software interface between users and the operating system that interprets commands and user interactions and communicates them to the operating system. A computer can have several layers of shells for various levels of user interaction.
shell name
The name of the shell interface.
shell script
A file containing commands that can be interpreted by the shell. You type the name of the script file at the shell command prompt to make the shell run the script commands.
show dependencies
A Rational Developer for System z function that detects dependencies, such as copybooks and include files, for COBOL and PL/I programs to compile properly.
shortcut bar
In Eclipse, the vertical toolbar at the left side of the workbench window that contains buttons for open perspectives and for fast views.
shortcut key
See keyboard shortcut.
sidedeck
A library that publishes the functions of a DLL program. The entry names and module names are stored in the library after the source code is compiled.
silent uninstallation
An uninstallation process that does not send messages to the console but instead stores messages and errors in log files after the uninstall command has been invoked.
simple element
In Enterprise Service Tools, a field in a message that is based on a simple type. A simple element can repeat, and it can define a default or a fixed value.
simple type
In the XML, a type that cannot have element content and cannot carry attributes. Elements that contain numbers (and strings, and dates, and so on) but do not contain any subelements are said to have simple types. See also complex type.
singleton
A class that can be instantiated only once. A singleton class cannot be an interface.
skeleton
Scaffolding for an implementation class.
smart logical ordering scheme
A mechanism for storing bidirectional text with a special algorithm introduced to improve the data exchange between zSeries® systems and Rational Developer for System z.
snippet
An excerpt of source code.
SOAP
A lightweight, XML-based protocol for exchanging information in a decentralized, distributed environment. SOAP can be used to query and return information and invoke services across the Internet.
SOAP encoding
Rules for serializing data over the SOAP protocol. SOAP encoding is based on a simple type system that is a generalization of the common features found in type systems in programming languages, databases, and semi-structured data.
software configuration management (SCM)
The tracking and control of software development. SCM systems typically offer version control and team programming features.
software development kit (SDK)
A set of tools, APIs, and documentation to assist with the development of software in a specific computer language or for a particular operating environment.
source code
A computer program in a format that is readable by people. Source code is converted into binary code that can be used by a computer.
source tree
The XML input document that is transformed by an XSL stylesheet.
SQL
See Structured Query Language.
SQLJ
See Structured Query Language for Java.
SQL query
A component of certain SQL statements that specifies a result table.
SSL
See Secure Sockets Layer.
stack
An area in memory that typically stores information such as temporary register information, parameters, and return addresses of subroutines.
stack frame
A section of the stack that contains the local variables, arguments, and register contents for an individual routine and a pointer to the previous stack frame.
Standard Widget Toolkit (SWT)
An Eclipse toolkit for Java developers that defines a common, portable, user interface API that uses the native widgets of the underlying operating system.
state artifacts
In Enterprise Service Tools, folders for the existing application resources that you will import into your service flow project. Existing application resources can include screen definitions, BMS maps, Copy books or recorded Macros. Often the resource imported is representative of the state of the host application at the time the resource was imported.
static Web page
A Web page that can be displayed without the additional client- or server-side processing required for JavaServer Pages, servlets, or scripts.
static Web project
A project that contains resources for a Web application with no dynamic content such as servlets or JavaServer Pages (JSP) files, or Java code. A static Web project can be deployed to a static HTTP server and does not require additional application server support.
stored procedure
A block of procedural constructs and embedded SQL statements that is stored in a database and that can be called by name. Stored procedures allow an application program to be run in two parts, one on the client and the other on the server, so that one call can produce several accesses to the database.
stream
A continuous sequence of data elements being transmitted one character at a time, or intended for transmission, using a defined format.
string
In programming languages, the form of data used for storing and manipulating text.
Structured Query Language (SQL)
A standardized language for defining and manipulating data in a relational database.
Structured Query Language for Java (SQLJ)
A standard for embedding SQL in Java programs, defining and calling Java procedures and user-defined functions, and using database structured types in Java.
structured viewing
The tabular aspect of the Design view of the XML editor that separates the structural constituents of an XML document, such as elements and attribute types, from values, such as attribute values and textual content.
structure item
In EGL, a field in a structure or record. Each structure item is substructured (as a word is substructured into letters) or is not divisible (as a letter is not divisible).
stub
A small program routine that substitutes for a longer, possibly remote, program. For example, a stub might be a program module that transfers procedure calls (RPCs) and responses between a client and a server. In Web services, a stub is an implementation of a Java interface generated from a Web Services Definition Language (WSDL) document.
style sheet
A specification of formatting instructions that, when applied to structured information, provides a particular rendering of that information (for example, online or printed). Different style sheets can be applied to the same piece of structured information to produce different presentations of the information.
subclass
In Java, a class that is derived from a particular class, either directly or indirectly.
subflow
In Enterprise Service Tools, a series of processing steps, implemented by flow nodes that are designed to be embedded in a flow or in another subflow. A subflow must include at least one Receive node or Reply node. A subflow can be executed only as part of the flow in which it is embedded, and therefore cannot be as a separate flow in and of itself. Any consistent pattern or sequence of nodes that may be required in more than one flow, is a good candidates for a subflow.
subproject
In zIDE, the programming resources that constitute a single load module; a z/OS project can contain one or more subprojects.
subproject definition file
In zIDE, a host-based project configuration file that defines the set of resources required to build a single load module.
subproject property file
In zIDE, a host-based project configuration file that defines the properties of a subproject.
superclass
In Java, a class from which a particular class is derived, perhaps with one or more classes in between.
supertype
In a type hierarchy, a type that subtypes inherit attributes from.
Switch node
In Enterprise Service Tools, a node that is used to test for a true/false condition in order to control the flow path. Multiple conditions can be tested by adding (composing) more outputs. The Switch node consists of the following parts:
  • An input terminal (in).
  • At least one conditional (out) terminal.
  • A default terminal.
A Switch node is commonly used whenever data from the request message, or data obtained during the processing of the flow, must be examined in order to control the flow path.
SWT
See Standard Widget Toolkit.
symmetric swapping
Interchanging specific characters such as ( > [ { with ) < ] } to preserve the logical meaning of the presented text.
symptom
In the logging tools, an error message. A symptom can have a solution associated with it in the symptom database.
syntax diagram
A diagram for a command that displays how to enter the command on the command line.
syntax highlighting
In source editors, the ability to differentiate text and structural elements, such as tags, attributes, and attribute values, using text highlighting differences, such as font face, emphasis, and color.
system menu
A drop-down menu that is activated by clicking the icon at the left of a window's title bar and that allows users to restore, move, size, minimize, or maximize the window.
System z LPEX Editor
An extension of the base LPEX editor that provides functions that are particularly useful as you develop COBOL, PL/I, and HLASM (High Level Assembler) programs for the System z platform.
table
In a relational database, a database object that consists of a specific number of columns and is used to store an unordered set of rows. See also view.
Tagged/Delimited String (TDS) Format
In Enterprise Service Tools, the physical representation of a message in the MRM domain that has a number of data elements separated by tags and delimiters.
tag library
In JSP technology, a collection of tags identifying custom actions described using a taglib descriptor and Java classes. A JSP tag library can be imported into any JSP file and used with various scripting languages. (Sun)
target
The destination for an action or operation.
target organization
In Enterprise Service Tools, a business running existing applications on enterprise information systems. The customer is looking for a solution that he or she can use to capture, process, store, and distribute the information from existing applications while utilizing the most up to date technology for repurposing their applications as services. The service flow project tools and the supported runtime implementations target those customers that still rely on critical business systems built on existing, terminal-based technologies, which limit their ability to evolve to modern service-oriented application environments.
task list
A list of procedures that can be executed by a single flow of control.
TCP
See Transmission Control Protocol. See also Internet Protocol.
TCP/IP monitoring server
A runtime environment that monitors all requests and responses between a Web browser and an application server and TCP/IP activity.
test case
A set of tasks, scripts, or routines that automate the task of testing software.
test environment
A specific instance of a configuration of hardware and software established for the purpose of conducting tests under known and controlled conditions.
test harness
A series of script files used to enable a DB2 database for use by the DB2 XML Extender. A test harness is optionally created when a DAD file is generated from a relational database to XML mapping. After it is enabled, it tests composing XML from data and decomposing XML files into relational data.
test pattern
A template used for the automatic generation of component tests. There are several test patterns available for testing both Java and EJB components. See also component test.
test suite
A collection of test cases that define test behavior and control test execution and deployment.
text orientation
See global orientation.
text shaping
A characteristic of the Arabic script in which characters assume different shapes according to their position in a word and how they connect to surrounding characters.
text type
See ordering scheme.
textUI program
A type of EGL program part that interacts with you by way of a character-based display. The display appears in a 3270 screen or a command window, not in a Web browser.
theme
The style element that gives a place a particular look. This element provides several themes, similar to virtual wallpaper, from which you can choose when creating a place.
thread
A stream of computer instructions that is in control of a process. In some operating systems, a thread is the smallest unit of operation in a process. Several threads can run concurrently, performing different jobs.
thread contention
A condition in which a thread is waiting for a lock or object that another thread holds.
Throw node
In Enterprise Service Tools, a node that represents a point at which exception and error conditions leave the flow.
thumbnail
An icon-sized rendering of a larger graphic image that permits a user to preview the image without opening a viewer or graphical editor.
Time Sharing Option/Extensions (TSO/E)
The facility in z/OS that allows users to share computer time and resources interactively.
timeout
A time interval that is allotted for an event to occur or complete before operation is interrupted.
ToolTip
See hover help.
top-down development
In Web services, the process of developing a service from a Web Services Definition Language (WSDL) file. See also bottom-up development.
top-down mapping
An approach for mapping enterprise beans to database tables, in which existing enterprise beans and their design determines the database design.
transaction
In Enterprise Service Tools, the controlled interaction between two entities, typically involving the passing of information. Transactions enforce ACID properties (atomicity, consistency, isolation, and durability) in the runtime environment, and in certain cases transactions can be rolled back, or reversed to a certain point. A unit of processing consisting of one or more application programs initiated by a single request. A transaction can require the initiation of one or more tasks for its execution. In the service flow project tools, a request from the service requester can result in transactions that run applications on existing systems. The transaction might be implemented as multiple user transactions, for example, the booking of the airline ticket might be undertaken by transactions that inquire about availability, reserve the seat, deal with payment, and print the ticket, for example. Using BTS, a business transaction might be implemented as multiple activities. Not all service flows composed and deployed using the service flow project tools are transactional. Generally this deployment style will involve a CICS DPL or EXEC CICS LINK style interface to one or more application targets with transactional semantics of BTS enforced.
transform
To change the structure and values of data from one form to another. In the Enterprise Service Tools component, the service flow project tools transforms or adapts existing interfaces on an EIS in order to facilitate participation of EIS applications in a service in an SOA.
transform connectivity
For Enterprise Service Tools, an application transformation style that changes the way in which enterprise applications are accessed and transforms the way in which the enterprise application is used. Specifically, in Enterprise Service Tools, using the service flow project tools, one can transform connectivity by exposing existing applications in a service-like interface, facilitating the move to service-oriented architecture (SOA).
Transmission Control Protocol (TCP)
A communication protocol used in the Internet and in any network that follows the Internet Engineering Task Force (IETF) standards for internetwork protocol. TCP provides a reliable host-to-host protocol in packet-switched communication networks and in interconnected systems of such networks. See also Internet Protocol.
Transmission Control Protocol/Internet Protocol
An industry-standard, nonproprietary set of communication protocols that provides reliable end-to-end connections between applications over interconnected networks of different types.
transport
A service plug-in for WebSphere Developer that manages the connection between a CARMA hierarchy and its CARMA host. The CARMA transport packages and sends commands from the CARMA hierarchy and returns responses from the CARMA host.
trigger
In database technology, a program that is called automatically whenever a specified action is performed on a specific table or view.
troubleshooting menu
A Rational Developer for System z menu that provides access to client and server information about remote resources and current environment variables.
TSO
Time sharing option. See Time Sharing Option/ Extensions (TSO/E).
TSO Commands
A subsystem of Remote System Explorer that allows you to open a TSO command prompt.
type
In a WSDL document, an element that contains data type definitions using some type system (such as XSD).
In Java programming, a class or interface.
In Enterprise Service Tools, a characteristic of an element that describes its data content.
typedef
In EGL, a part definition that can be used as a model of format.
type hierarchy
The complete context for a Java class or interface including its superclasses and subclasses.
UI part
An EGL declaration that is used for data presentation. The types of UI parts are forms, form groups, and UI records.
UI record
In EGL, a data structure that makes communication possible between an action program and a specific Web page. This type of record is used to migrate VisualAge® Generator Web transactions.
Unified Modeling Language
A standard notation for the modeling of real-world objects as a first step in developing an object-oriented design methodology.
Uniform Resource Identifier (URI)
A unique address that is used to identify content on the Web, such as a page of text, a video or sound clip, a still or animated image, or a program. The most common form of URI is the Web page address, which is a particular form or subset of URI called a Uniform Resource Locator (URL). A URI typically describes how to access the resource, the computer that contains the resource, and the name of the resource (a file name) on the computer. See also Uniform Resource Name.
Uniform Resource Locator (URL)
The unique address of an information resource that is accessible in a network such as the Internet. The URL includes the abbreviated name of the protocol used to access the information resource and the information used by the protocol to locate the information resource.
Uniform Resource Name (URN)
A name that uniquely identifies a Web service to a client. See also Uniform Resource Identifier.
URI
See Uniform Resource Identifier. See also Uniform Resource Name.
URL
See Uniform Resource Locator.
URN
See Uniform Resource Name. See also Uniform Resource Identifier.
user-defined function (UDF)
A function that is defined to the DB2 database system by using the CREATE FUNCTION statement and that can be referenced thereafter in SQL statements. A user-defined function can be an external function or an SQL function.
user ID
See user identifier.
user identifier (user ID)
A string of characters that uniquely identifies a user to a system.
validation
The checking of data or code for correctness or for compliance with applicable standards, rules, and conventions.
validation action
A mechanism for verifying whether the actual value of a variable at run time corresponds to the expected value of that variable.
validator
A program that checks data or code for correctness or for compliance with applicable standards, rules, and conventions.
version
In CARMA, a previous copy of a member held by an SCM. Versions in CARMA can be created only for CARMA members. The actions available on versions depend on the SCM it originates from and the RAM that is used to connect to the SCM. Some RAMs can alter versions; other RAMs make the versions read-only.
For SCLM, versioning must be enabled. The version window is accessible as a view in Eclipse and can be manually invoked by selecting Window > Show View > Other and selecting IBM SCLM Developer Toolkit > Version Explorer from the Show View dialog. The versioning function for SCLM is accessible through the Get Version Information function. Versioning support must be activated in the SCLM project in order for this service to work. When you run this function the Version information retrieval option page is displayed allowing you to select various groups from which to retrieve version information. One or more groups can be selected.
version control
The coordination and integration of the history of work submitted by a team.
version tree
The hierarchical structure in which all the versions of an element are (logically) organized. The version tree display also shows merge operations.
view
In Eclipse-based user interfaces, any pane in the workbench that is outside the editor area and can be stacked (dragged and dropped) on top of other views. Views provide different ways to look at or work with the resources in the workbench.
visual ordering scheme
A mechanism for storing text in exactly the same order as it is displayed.
VSAM
Virtual storage access method.
WAR
See Web archive. See also enterprise archive, Java archive.
WAR file
See also enterprise archive, Java archive. See Web archive.
watchpoint
A breakpoint that suspends execution when a specified field or expression is modified.
Web application
An application that is accessible by a Web browser and that provides some function beyond static display of information, for instance by allowing you to query a database. Common components of a Web application include HTML pages, JSP pages, and servlets.
Web archive (WAR)
A compressed file format, defined by the J2EE standard, for storing all the resources required to install and run a Web application in a single file. See also enterprise archive, Java archive.
Web browser
A client program that initiates requests to a Web server and displays the information that the server returns.
Web diagram
A Struts file that uses icons and other images on a free-form surface to help application developers visualize the flow structure of a Struts-based Web application.
Web module
A unit that consists of one or more Web components and a Web deployment descriptor. (Sun)
Web project
A container for other resources such as source files and metadata that corresponds to the J2EE-defined container structure and hierarchy of files necessary for Web applications to be deployed.
Web resource
Any one of the resources that are created during the development of a Web application for example Web projects, HTML pages, JavaServer Pages (JSP) files, servlets, custom tag libraries, and archive files.
Web server
A software program that is capable of servicing Hypertext Transfer Protocol (HTTP) requests.
Web service
A self-contained, self-describing modular application that can be published, discovered, and invoked over a network using standard network protocols. Typically, XML is used to tag the data, SOAP is used to transfer the data, WSDL is used for describing the services available, and UDDI is used for listing what services are available.
In Enterprise Service Tools, Web services describe their own functions and look for and dynamically interact with other Web services. Web services use open protocols and standards, such as HTTP, SOAP, and XML. Web services provide a means for different organizations to connect their applications with one another to conduct dynamic e-business over a network, regardless of their application, design, or runtime environment.
Web Services Description Language (WSDL)
An XML-based specification for describing networked services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information.
In Enterprise Service Tools, the standard format for describing a Web service. A WSDL definition describes how to access a Web service and what operations it will perform. WSDL, SOAP, and UDDI are considered to be the foundation standards for Web services.
Web site
A related collection of files available on the Web that is managed by a single entity (an organization or an individual) and contains information in hypertext for its users. A Web site often includes hypertext links to other Web sites.
WebSphere
An IBM brand name that encompasses tools for developing e-business applications and middleware for running Web applications.
WebSphere Application Server
Web application server software that runs on a Web server and that can be used to deploy, integrate, execute, and manage e-business applications.
While node
In Enterprise Service Tools, a node that represents repeatable patterns of logic or mapping or both. A While node allows you to repeat part of the flow at run time based on user settings or on the actual runtime data values. This node consists of a loop condition that can be tested for true or false. Extracting an entire list of data from a screen that can only display a portion of the list at one time is a common use of the While node within a flow.
widget
A reusable user interface component such as a button, scroll bar, control area, or text edit area, that can receive input from the keyboard or mouse and can communicate with an application or with another widget.
wire
A technique for connecting two or more cooperative portlets so that changes in the source portlet automatically update the target portlets without any user interaction.
Wireless Markup Language (WML)
A markup language based on XML that is used to present content and user interfaces for wireless devices such as cellular phones, pagers, and personal digital assistants.
wizard
An interactive form of help that guides users through each step of a particular task.
WML
See Wireless Markup Language.
workbench
The user interface and integrated development environment (IDE) in Eclipse and Eclipse-based tools such as IBM Rational Application Developer.
working set
The parts of a program's executable code, data areas, or both that are being used intensively and are therefore important to keep in the fastest possible type of storage. Thus a program's instruction cache working set is the set of program cache lines that need to be kept in the instruction cache if the program is to run at maximum speed.
workspace
In Eclipse, the collection of projects and other resources that you are currently developing in the workbench. Metadata about these resources resides in a directory on the file system; the resources might are located in the same directory.
workstation-based project
A z/OS project that is defined on your workstation. Contrast with host-based project.
wrapper
An object that encapsulates and delegates to another object to alter its interface or behavior in some way. (Sun)
WSDL
See Web Services Description Language.
WSDL document
A file that provides a set of definitions that describe a Web service in Web Services Description Language (WSDL) format.
WSDL file
See WSDL document.
XDoclet
An open source code generation engine that uses special JavaDoc tags to parse Java source files and generate output such as XML descriptors or source code, based on templates.
XHTML
See Extensible Hypertext Markup Language.
XML
See Extensible Markup Language.
XML catalog
A catalog that contains rules specifying how an XML processor should resolve references to entities. Use of a catalog eliminates the need to change URIs within XML documents as resources are moved during development.
XML domain
The message domain that includes all messages that conform to the W3C XML standard. The XMLNS domain is an extension of the XML domain and contains messages that conform to the same standard and that can use the namespaces feature of the XML specification. Messages in this domain are processed by the XML parser.
XML parser
A program that reads XML documents and provides an application with access to their content and structure.
XML Path Language (XPath)
A language that is designed to uniquely identify or address parts of source XML data, for use with XML-related technologies, such as XSLT, XQuery, and XML parsers. XPath is a World Wide Web Consortium standard.
XML schema
A mechanism for describing and constraining the content of XML files by indicating which elements are allowed and in which combinations. XML schemas are an alternative to document type definitions (DTDs) and can be used to extend function in the areas of data typing, inheritance, and presentation.
In Enterprise Service Tools, an international standard that defines a language for describing the structure of XML documents. An XML schema formally describes and constrains the content of XML documents by indicating which elements are allowed and in which combinations. (An XML Schema is an alternative to a document type definition (DTD), and can be used to extend function in the areas of data typing, inheritance, and presentation.) The XML Schema language is ideally suited to describing the messages which flow between business applications, and it is widely used in the business community for this purpose.
XML Schema Definition Language (XSD, XSDL)
A language for describing XML files that contain XML schema.
XML wire format
The physical representation of a message in the MRM domain that can be parsed as XML.
XPath
See XML Path Language.
XPath expression
An expression that searches through an XML document and extracts information from the nodes (any part of the document, such as an element or attribute) in that document.
XSD
See XML Schema Definition Language. A language for describing XML files that contain XML schema.
XSDL
See XML Schema Definition Language. A language for describing XML files that contain XML schema.
XSL
See Extensible Stylesheet Language.
XSL style sheet
Code that describes how an XML document should be rendered (displayed or printed).
zIDE
z/OS integrated development environment. A set of perspectives and views for developing applications using z/OS-based systems, projects, and resources.
z/OS
An IBM operating system for the IBM System z family of enterprise servers that includes and integrates functions previously provided by many IBM software products (including the MVS and OS/390® operating systems). z/OS is an open, secure operating system for the IBM System z family of enterprise servers, complies with industry standards, is enabled for network computing and e-business, and supports technology advances in networking server capability, parallel processing, and object-oriented programming.
z/OS File System Mapping view
A z/OS Projects view that shows how remote data set names map to workstation-based files.
z/OS project
An Eclipse-based project that contains z/OS-based resources, MVS subprojects, and z/OS UNIX® System Services subprojects.
z/OS Projects perspective
An interface in Rational Developer for System z for developing and building z/OS projects.
z/OS Projects view
A view in the z/OS Projects perspective that lists defined z/OS projects.
z/OS UNIX System Services subproject
A subproject containing z/OS UNIX System Services resources.

Terms of use | Feedback



This information center is powered by Eclipse technology. (http://www.eclipse.org)