Rational Programming Patterns for System z

Glossary for Rational Programming Patterns for System z

This glossary includes terms and definitions for Rational Programming Patterns for System z.

The following cross-references are used in this glossary:
  • See refers you from a term to a preferred synonym, or from an acronym or abbreviation to the defined full form.
  • See also refers you to a related or contrasting term.

To view glossaries for other IBM products, go to www.ibm.com/software/globalization/terminology.

A B C D E G I L M O P R S T

A

action code
A one-character long command assigned to a line or to a screen to perform a specific action (creation, deletion, update, or text editing).

B

Business Component
An entity deployed on the server side of the application that contains the business logic and supports a set of services on a Logical View.

C

cblmsp
The extension of the file containing the COBOL code of a Macro.
-CD lines
The list of the external resources of a Program. These resources are represented by Data Structures.
-CE lines
The list of the elements which compose the current instance.
COBOL folder
A folder containing the COBOL files generated from an instance. The folder of the corresponding design file is the default folder.
See also COBOL target.
COBOL project
A project containing the COBOL files generated from an instance. The project of the corresponding design file is the default project.
See also COBOL target.
COBOL target
The location of the COBOL files generated from an instance (Progam, Screen or Server). The COBOL target is composed of a project and a folder.
COBOL type
The COBOL variant for the generated instance.
code derivation
The creation of a derived instance which inherits the complete source code (code generated from the design and specific code) of the reference instance.
communication monitor
A component managing the communication between the clients and the server programs.
continuation line
An additional line of source code where instructions are entered when the source code cannot be contained on the previous line.
conversational format
A format defined for Data Elements used as input and output to online programs.
-CP lines
The list of Macros called into a Program, Screen or Server.
cross-references
The link between instances (called in or called by), which enables impact analysis.
-CS lines
A list of the external resources (Segments) called in a Screen, Dialog, Server, or Server Dialog.

D

-D lines
Description depending on the entity.
For a Report, the description of the composition of a layout, especially its categories, and edition lines.
For a Data Element, the description as explanatory text, specific labels, presentation values (used in Screens or Reports layouts) and values or ranges of possible values with their meaning.
Data Element
An entity, considered as 'elementary' during at least one stage in the development of a project.
Data Structure
An entity which is a logical envelope with no physical characteristic, used to logically group Segments, which may be records of files, work areas of programs, Segments of databases.
Database Block
A set of Segments, each of which calls Data Elements. This entity is used to describe databases, both logically and physically.
-DBE lines
A list of tables of the elements called into a Segment which is used as a view.
-DC lines
The description of the CODASYL, DMSII, and TANDEM Database Blocks. –DC lines are used to declare the areas, call the records, and distribute them within the areas, call the sets and describe them.
DBD
See Database Block.
derivation
The process used to create a derived entity from a reference instance and then use the derived instance to generate the reference instance without duplicating its design.
See also code derivation.
See also design derivation.
derived entity
An entity which does not contain any design but points to a reference instance. It can be a Program, a Screen, a Dialog, a Server, a Server Dialog, or a Data Structure.
design build path
The hierarchy of the projects which is explored in an upward direction in order to resolve the dynamic links and references between the instances contained in the various projects.
design derivation
The creation of a derived instance to generate the instance from a library different from the library of the reference instance.
Design Explorer
A view of the PDP perspective used to view and modify the design of the applications. The user can work on the instances which constitute these applications: create, modify, import/export instances, search for references, generate instances...
design file
A file containing the design of an instance.
Design View
A view used to display the design of the generated instance whose code is currently displayed with the PDP COBOL editor, and selected. It is possible to modify this design in the view and generate the instance again in order to take these modifications into account.
-DH lines
The relationships between Segments in a hierarchical database (example: DL/1). Each line designates a Segment and its parent (except for the line referring to the root Segment). The description consists of records which make up the physical file.
Dialog
An entity grouping a logical family of Screens. This entity is used to develop and generate the online applications of the OnLine Systems Development function or the TUI applications of the Pacbench C/S function.
Dialog complement
The information and/or generation options common to all of the Screens of the Dialog and, data related to the physical environment of the transaction.
dispatch Macro
To import the file that contains the tagged code of the Macro into the location.
-DR lines
A list of SQL objects that make up the relational database (tables, views, index).
DS
See Data Structure.

E

export
To group instances into a file with an xmi extension. This file is then available for any subsequent import with the Import function of the Design Explorer view.
See also import.
extract method
A select access to a Business Component.

G

-GC lines
The comments on the instance.
-GE lines
A list of explicit error messages on the instance, automatic error messages that have been replaced or help on the instance.
-GG lines
In a Segment, lines used to customize SQL accesses.
In a Database Block, physical information necessary to generate the Database Block.
In a Screen, Dialog, Server, or Server Dialog, lines used to override some of the values of the generated constants.
-GO lines
The generation options for the instance.

I

import
To copy instances from a file which was exported with the export function of the Design Explorer view or output by the Pacbase batch migration procedures. These instances then populate the selected location of the Design Explorer view.
See also export.

L

-L lines
The label lines, which make up the layout of the current Report.
Library
An entity which is a structured subset of data in a database.
location
A collection of instances involved in the design of the application.
Logical View
A collection of elementary data (Data Elements) conveyed between the server and the client parts through the message that both parts exchange to communicate.
-LS lines
The list of the Segments to be associated with the Data Structure.

M

Macro
An entity containing both procedure and associated data. It is used to standardize sequences of structured language, with possible variations, in order to use them one or more times in one program or in several different programs.
metadata file
A technical file that contains the location of the design file and information required to process the generated COBOL code.
micropattern
A comment with a special format entered in the COBOL code of an instance, using PDP COBOL editor. This comment offers the capability of a microgenerator.
migrate
To move instances from Pacbase to Rational Programming Patterns for System z.
migration help
A tool used to see whether the COBOL generated in Pacbase is different from the locally generated code.

O

operation code
A code used to generate 6 standard operations (display, update, screen branching, end of conversation, same screen, call of another screen).

P

PDP COBOL editor
An editor providing additional functions on top of functions already provided by the standard COBOL editor. It can be used to modify the COBOL code while clearly seeing the origin of all the code lines (generated lines, Macro lines, or specific code lines), the deleted or overwritten lines.
PDP Macro editor
An editor used to modify the COBOL code of a Macro.
Program
An entity used to develop and implement all the batch procedures defined in the detailed analysis phase. It reads and writes files and creates Reports.

R

reconciliation
The process of synchronizing the code produced by the generation of the design, and the specific insertions.
references
Search for the use of an instance in other instances, with a view to immediately assess the impacts of the instance update.
See also super references.
See also sub references.
Report
An entity containing formatted data that result from running a query and applying a form to it. A Report must be called into a Program instance to be generated.

S

Screen
An entity which supports the processing of 3270 applications. This entity belongs to a Dialog and is considered as a list of fields.
Segment
An entity which is a structured collection of Data Elements. It must belong to a Data Structure.
-SE lines
SOCRATE lines that are used to enter the description of the Data Elements called in a Segment with SOCRATE characteristics.
Server
An entity which constitutes the server-side components of an application.
Server Dialog
An entity which is a logical envelope. It groups the various server-side components of an application.
specific code
Source code directly entered by the developer to extend the generated code coming from the model and not automatically generated by the product.
- SS lines
The list of subschemas used by a Logical View, or the list of subschemas and subsystems called in a Table.
sub references
The instances called by the current instance.
subschema
A group of Data Elements called in a Segment.
subsystem
A selection of Table items within a Table, each one being a different subset of data.
super references
The instances in which the current instance is called.

T

Table
An entity which is set of Data Elements, grouped because they are related to the same topic. A Table must belong to a Data Structure.
Text assignment
The association of an instance of the Text entity with an instance of another entity to document it.
Textual User Interface
A character-mode interface that uses only text, symbols, and colors available on a typical text terminal. It uses the entire screen area and does not necessarily provide line-by-line output.
TUI
See Textual User Interface.

Terms of use | Feedback

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