Glossary of COBOL

abend

An error condition that results in abnormal termination of a program.

absolute address

An address that can reference the specified memory location without further modification.

active module

The module in which execution is suspended.

active source file

See current source display.

address

A unique nonnegative integer that identifies a byte location in main memory.

address space

The range of addresses available to a programmer.

alternate entry points

An alternate entry point is created whenever an ENTRY statement is used in COBOL, even if the ENTRY statement is the first statement in the Procedure Division.

array

A collection of one or more elements with the same characteristics grouped into one or more dimensions.

assemble

The preparation of a machine language program from a symbolic language program by substituting absolute operation codes for symbolic operation codes and absolute or relocatable addresses for symbolic addresses.

Assembler language processor

One of the language processors provided by BMC, this lan­guage processor accepts Assembler output, builds work records, sorts and merges the records, and merges the records with the listing to produce processor control blocks that can then be used as input to other BMC AMI products.

base address

The beginning address of the storage area where the CSECT or DSECT resides.

base register

A general-purpose register used to store a base address.

batch

Processing in which jobs are grouped (batched). The jobs are executed sequentially, and each job must be processed to completion before the following job can begin execution.

BDAM

Basic direct access method.

Branch Coverage

When referencing Code Coverage (if installed at your site), Branch Cov­erage is defined as a methodology for tracking the number of paths which were taken during execu­tion of a conditional statement. For Code Coverage, this methodology designates a specific type of statistic. Branch Coverage is supported only for COBOL and PL/I, and it must be implemented to indi­cate whether the next verb in succession is intended for execution. The collection of Branch Cover­age statistics is optional during a Code Coverage session.

Qualifying condition statement types for Branch Coverage include IF (for COBOL and PL/I), and ON n and WHEN for COBOL. In terms of reliability, Branch Coverage is considered the most thorough method required for the testing of specialized application programs.

breakpoint

A location or offset (paragraph or statement) within the program where Code Debug “breaks” or temporarily suspends normal program execution to perform another function.

C370 language processor

One of the language processors provided by BMC, this language processor accepts C compiler output, builds work records, sorts and merges the records, and merges the records with the listing to produce processor control blocks that can then be used as input to other BMC AMI products

CA-Optimizer

A COBOL productivity and optimization product for the OS and OS/VS environ­ments. CA-Optimizer optimizes COBOL programs. It works on the object code of a program, reducing the size of the program and its run time by eliminating redundant machine instructions.

case sensitivity

Whether a group of letters is uppercase or lowercase.

CICS

Customer information control system.

COBOL language processor

One of the language processors provided by BMC, this language processor accepts COBOL compiler output, builds work records, sorts and merges the records, and merges the records with the listing to produce processor control blocks that can then be used as input to other BMC AMI products.

code coverage

The concept of measuring and reporting on how much of one or more programs have been executed by a set of tests. (see also BMC AMI DevX Code Coverage)

column template

A dashed line depicting column positions. When debugging with Code Debug, a col­umn template is displayed above each group item and each nonnumeric elementary item. The length of the column template corresponds to the length of the variable to be displayed as defined in the picture clause.

CMS

Conversational monitor system.

command area

The area of any display used to enter Code Debug primary commands. The command area is designated as the left side of the second line of the source display.

command delimiter

A character used to separate commands in a list of commands entered simulta­neously. The character used should be the same as the ISPF command delimiter. If the Code Debug and ISPF command delimiters are not the same, ISPF will break the stream down into illogical sections to be passed on to Code Debug one at a time for parsing.

command, CICS

In CICS, an instruction similar in format to a high-level programming language statement. CICS commands begin with the pseudo-verb EXEC (either EXEC CICS or EXEC DLI) and are terminated by END-EXEC. They can be issued by an application program to make use of CICS facilities.

command-language statement

Synonymous with command in relation to CICS.

command stacking

A method of entering multiple commands simultaneously by separating each command by a special delimiter. Command stacking is valid when testing with Code Debug TSO only if you are using ISPF version 2.1 or higher.

communication area (COMMAREA)

An area that is used to pass data between tasks that communi­cate with a specific terminal. The area is also used to pass data between programs within a task.

conditional expression

Any of the valid COBOL expressions supported by Code Debug that test condi­tions to select between alternate paths of control depending upon the truth value of the condition.

CSECT

Control section.

current source display

The program currently displayed on the Source screen. It is named in the third line of the Source screen.

data area

Storage space defined and reserved at assembly time for insertion and manipulation of data at execution time.

date/time stamp

The date and time of compilation that marks the load module. Code Debug stores the date/time stamp in the header record of the DDIO file. If there is a mismatch between the load mod­ule stamp and the DDIO file stamp, Code Debug responds with a message in the session log.

Db2 stored procedure

See stored procedure.

DDIO

A BMC file access method.

DDIO file

A generic name for an Code Debugsource listing file.

declaration statement

In PL/I, a DECLARE statement that specifies the attributes of a name.

declarative

Directives that reserve defined areas of storage (DS statements) or define constant val­ues (DC statements).

default delimiter

The delimiter set by Code Debug.

dimension

The size of a table or array and the arrangement of its elements.

directive

A statement that tells the assembler to take a special action and does not generate object code. For example, START, DSECT, and END are directives.

displacement

The number of bytes from the first byte of the storage area.

DL/I

Data language 1. IBM’s database management facility provided by the IMS/VS database pro­gram products.

doubleword

A binary constant that has a length of eight bytes and can be aligned on a doubleword boundary (a location whose address is divisible by eight).

DSECT

Dummy control section. Used by Assembler to format an area of storage without producing any object code.

dump

Hexadecimal representation of storage that may contain data useful for diagnosing an error.

duplication factor

A value that indicates the number of times to generate the data specified imme­diately following the duplication factor.

effective address

The address that results from adding a base register value and a displacement value.

enhanced FIND

For COBOL only, the FIND command has additional keywords that provide the ability to search data relationships and program structures.

entry point

The alternate name supplied in the ENTRY statement on the link-edit control cards: By default in COBOL, it is the program name.

execution monitor

The Code Debug execution monitor is used to allocate the test data and the envi­ronment to run the test, load and monitor execution of your program, and display and format the data in your program.

explicit declaration

In PL/I, a DECLARE statement that specifies the attributes of a name. Same as declaration statement.

figurative constant

A compiler-generated value referenced through the use of certain reserved words. The reserved word can be written in a program without having been defined.

File-AID for DB2

A Db2 database management and SQL development and analysis tool.

fullword

A binary constant that has a length of four bytes and can be aligned on a fullword bound­ary (a location whose address is divisible by four).

general-purpose registers

The 16 general-purpose registers are separate from main storage. They are numbered from 0 through 15 and are referenced by number. These 32-bit or 64-bit registers are used for binary arithmetic and to reference main storage positions by using base-displacement addressing.

halfword

A binary constant that has a length of two bytes and can be aligned on a halfword bound­ary (a location whose address is divisible by two).

HELP facility

Online support that can be invoked for clarification or aid in relation to a problem.

IBM MQ for z/OS

IBM MQ for z/OS (formerly MQSeries and WebSphere MQ) allows z/OS applica­tions to use message queuing to participate in message-driven processing. With message-driven pro­cessing, applications can communicate across different platforms by using the appropriate IBM MQ for z/OS products. All IBM MQ for z/OS products implement a common application programming interface for whatever platform the applications are able to run on. The calls made by the applica­tions and the messages they exchange are common.

INCLUDE library

Under MVS, a partitioned data set created and maintained by the user allocated to the ddname XINCLUDE. This library contains test scripts generated by a test session or used to set up a session.

INCLUDE test script

A predefined test script executed through the INCLUDE command. The com­mands in the test script are executed as they are read in, as if they had been entered serially from the terminal.

index register

A register whose content is added to (or subtracted from) the absolute address which is derived from a combination of a base address with a displacement.

initial test script

A special test script executed at the beginning of a session that is used to set up the testing environment. This test script is not executed through the INCLUDE command. Rather, it is specified on the appropriate environment test menu or command parameter.

intercommunication facilities

A term covering intersystem communication (ISC) and multiregion operation (MRO).

intersystem communication

Communications between separate systems by means of SNA facili­ties.

Keep window

The window at the top of the Source screen that automatically displays the values of data items referenced by the current execution line whenever execution halts. It also displays any data items specified by the KEEP command.

label

The entry in the name field of an Assembler language statement. The Assembler option sup­ports label names of up to 30 characters.

language processor (LP)

A processor that converts Assembler or compiler output into input for other BMC AMI products.

License Management System (LMS)

Facility that enables you to centrally administer BMC AMI product License Certificates and manage access to BMC AMI products at your site. The LMS includes several components that enable you to establish, maintain, diagnose, and upgrade access to those BMC AMI products licensed by your enterprise. The LMS replaces the utility previously known as the Customer Profile Utility.

line commands

Code Debug commands that are entered by typing over the compiler-generated state­ment numbers.

link pack area

In OS/VS2, an area of virtual storage containing reenterable routines loaded at IPL. It can be used concurrently by all tasks in the system.

literal

Any alphanumeric string of characters enclosed in apostrophes (’ ’).

load libraries

In the MVS environment, the set of partitioned data sets containing the link-edited application programs. Code Debug searches the list for the load module of the program to be tested.

macroinstruction

An instruction that causes the assembler to process a predefined set of statements called a macro definition. The statements from the macro definition replace the macroinstruction (or macro call) in the source program.

message area line

The line below the command area, generally the third line of any source display used to report brief error or informational messages.

MQSeries

See IBM MQ for z/OS.

multiregion operation

Communication between CICS systems in the same processor without the use of SNA facilities.

MVS

Multiple virtual storage.

native CMS

The VM/CMS environment without the use of ISPF.

native TSO

The MVS/TSO environment without the use of ISPF.

nonrepresentable characters

Characters that cannot be printed or displayed. By default Code Debug displays nonrepresentable characters as periods (.).

NOQ environment

An Code Debug TSO environment used to test IMS MPP or BMP programs when BTS is not available for testing. IMS database calls can be made since Code Debug TSO will provide addressability to any IOPCBs. However, all calls to the message queue must be skipped.

object module

A module that is the output of an Assembler or compiler.

offset

A relative location or position within a data area.

operating system

Software that controls the execution of jobs. It can provide resource allocation and scheduling.

PA keys

The terminal program access keys. Their definitions are unaltered by Code Debug.

panels

Menus or screens presented on a display terminal.

paragraph

For COBOL, a paragraph is a subdivision of a COBOL program: A paragraph contains one or more statements or sentences that work as a unit to perform a specific set of operations.

During an Assembler test, Code Debug TSO considers a paragraph to be a name, a label on one or more valid executable instructions, or a name label on an EQU * or DS 0H that is followed by one or more valid executable instructions.

pausing

All pause breakpoint commands direct Code Debug to unlock the keyboard and return control to the user. Any number of Code Debug commands can be entered while Code Debug is paused.

PCB

Program communication block.

PL/I language processor

One of the language processors provided by BMC, this language processor accepts PL/I compiler output, builds work records, sorts and merges the records, and merges the records with the listing to produce processor control blocks that can then be used as input to other BMC AMI products.

primary commands

Code Debug commands that are entered from the command area, as opposed to Code Debug line commands which are entered by typing over the compiler-generated statement number.

procedure

In PL/I, a block of programming statements that starts from various points in a program by CALL statements and processes data passed to it from the calling block.

procedure division

The section of a COBOL program that contains executable instructions.

PSW

Program status word. An operating system control block defining the current status and loca­tion of a program that is executing.

Quickstart

A File Allocation Utility (FAU) enhancement which provides the ability for users to point Code Debug at the JCL needed to run a test, therefore eliminating the need to use the FAU.

register

A device capable of storing a specified amount of data, such as one word (32 bit mode) or two words (64 bit mode).

review mode

An Code Debug dynamic analysis feature for COBOL programs that lets the programmer review the execution flow backwards.

screens

Menus or panels presented on a display terminal.

script data set/file

A data set or file created and used by Code Debug to record each executable com­mand entered during a debugging session. The script data set can be copied into an INCLUDE library, a sequential file, or another partitioned data set to be used again.

scroll amount area

The furthest right area of the second line of the source display. It is used to dis­play the current scroll amount, whenever scrolling is applicable.

scrollable fields

If a variable’s length exceeds the screen width, the field becomes scrollable. Scrollable fields are identifiable by the highlighted MORE-> message in the line command area. When the screen is scrolled left or right, only the scrollable values and their associated column templates actually move.

scrolling

The ability to move the screen window across the data in any of four directions.

sentence

For COBOL, a sentence is a statement or group of statements that ends with a period.

session log

A file created and used by Code Debug to record each command entered during a debugging session and the responses made to it.

session script

A file created by Code Debug containing the commands entered during a debugging ses­sion. This file can be saved as a member of an INCLUDE data set to be used as input to another debug­ging session.

Shared Directory

A variable length record VSAM Relative Record Data set (RRDS) that contains lan­guage processor (LP) directory records necessary to process LP database members.

Source display screen

The Code Debug screen used to display the program source. Within this display screen, Code Debug commands can be entered from the command area or by typing over the compiler-generated statement number. The data on the screen is scrollable in all four directions.

source listing

A compiled listing and other information about a file stored in a source listing file.

source listing file

A file containing source listings and accessed by DDIO.

split screen

A capability provided by ISPF/PDF that allows you to partition the display screen into multiple “logical” areas.

SQL

Structured query language.

stored procedure

A stored procedure is a user-written program stored at the Db2 server that can be invoked by a client application. A stored procedure can contain most statements that an application program usually contains. A stored procedure can also execute Structured Query Language (SQL) statements at the server and application logic for a specific function. A stored procedure can be writ­ten in COBOL, Assembler, C, PL/I, or many other different languages, depending on the platform where the Db2 server is installed.

structure

A collection of data items.

SUB environment

The Code Debug TSO environment that is used to test stand-alone subroutines that make IMS database calls.

System Flow

A feature which allows the user to capture linkage information between programs during an Code Debug CICS, Code Debug TSO, or Code Debug IMS test, storing the information in a Code Cov­erage repository. This data can be analyzed using BMC AMI DevX Code Coverage to report on transaction (Code Debug CICS) and program invocations that occurred during the test session.

temporary breakpoint (GOTO)

A breakpoint that occurs after a GOTO command is entered and before the target paragraph or statement is executed. The breakpoint is temporary and provides the opportunity to ensure that the target statement is the one intended.

test script

A predefined stream of Code Debug commands used to set up, run, or rerun a debugging ses­sion.

test script library

A partitioned data set allocated to the ddname XINCLUDE.

trace breakpoint

A breakpoint set by execution of the TRACE command in which modules are traced upon entry and exit.

unit testing subroutines

Testing a subroutine as a stand-alone program; that is, without the calling module being present.

user test scripts library

See INCLUDE library.

unattended batch

Processing data without interacting with the debugging session from your termi­nal. Code Debug debugging commands are read from a test script and the output from the test session is written to the session log.

VCON

V-type address constant. Reserves storage for the address of a location in a CSECT that lies in another source module. A VCON is often used to branch to the specified external address.

VSAM

Virtual Storage Access Method.

WebSphere MQ

See IBM MQ for z/OS.

wide screen

A terminal screen that is 32 or 43 lines long, and 133 characters wide.

working storage

A section of a COBOL program used to define the data items that are used in a pro­gram.

Workload Manager (WLM)

A component of MVS used for scheduling and dispatching of work within an MVS system. WLM is a prerequisite for the testing and debugging of Db2 stored procedures in an Code Debug TSO environment.

Code Coverage

A product that collects run-time execution data from the Code Debug TSO, Code Debug CICS, and Code Debug IMS debuggers to help users analyze, understand, improve, and docu­ment how much of their code has been tested and how execution flows from one program to another. Code Coverage interacts with DevEnterprise to make code coverage results viewable online and to give users an idea of where the risk lies in their testing of a program.

Code Debug ISPF interface

The Code Debug ISPF interface is a collection of menus, CLISTs or EXECs, and programs created to assist you in allocating test data and supplying the information required to start an Code Debug TSO debugging session.

Code Debug TSO

A symbolic debugging and testing tool used by COBOL, Assembler, PL/I, and C lan­guage programmers to simplify the tasks of diagnosing and fixing programming errors by giving the programmer control over the execution of the program interactively at the source level.