bdfs1m08 | Structured Programming Macros |
This book describes two sets of structured programming macros
(SPMs). One set of SPMs is provided with the TPF Database Facility
(TPFDF) product and the Transaction Processing Facility (TPF) system and is
referred to as the TPFDF SPMs. The other set of SPMs is provided with
the TPF system only and is referred to as the TPF SPMs.
In this book, abbreviations are often used instead of spelled-out
terms. Every term is spelled out at first mention followed by the
all-caps abbreviation enclosed in parentheses; for example, structured
programming macro (SPM). Abbreviations are defined again at various
intervals throughout the book. In addition, the majority of
abbreviations and their definitions are listed in the master glossary in Messages (System Error, Online, Offline) and Master
Glossary and the TPF Library Guide.
Before using this book:
- Read Structured Programming Macros Introduction and determine the set of SPMs that you want to use.
- If you are going to use the TPFDF SPMs, see TPFDF Structured Programming Macros.
- If you are going to use the TPF SPMs, see TPF Structured Programming Macros.
This book is intended for application programmers who are currently working
with one of the following:
- Transaction Processing Facility (TPF) system and IBM High Level
Assembler/MVS & VM & VSE (HLASM)
- Airline Control System (ALCS), also referred to as TPF/MVS, and IBM
Assembler H or IBM High Level Assembler/MVS & VM & VSE (HLASM).
This book has 3 parts as follows:
- Structured Programming Macros Overview
- Provides an overview of structured programming and contains some general
rules for using the structured programming macros (SPMs).
- TPFDF Structured Programming Macros
- Provides detailed information about the TPFDF SPMs.
- TPF Structured Programming Macros
- Provides detailed information about the TPF SPMs.
For your convenience, a set of tabs (GH31-0184) is available for this
book. These tabs help you to quickly access the major sections of this
book.
This book uses the following conventions:
Typography
| Examples of Usage
|
italic
|
Used for important words and phrases. For example:
A database is a collection of data.
Used to represent variable information. For example:
Enter ZUDFC DISPLAY ID-fileid, where
fileid is the file identifier (ID) of the file for which you want
statistics.
|
bold
| Used to represent keywords. For example:
Enter ZUDFC HELP to obtain help information for the ZUDFC
command.
|
monospaced
| Used for messages and information that displays on a screen. For
example:
PROCESSING COMPLETED
Used for C language functions. For example:
dfcls
Used for examples. For example:
ZUDFC DISPLAY ID-J5
|
bold italic
| Used for emphasis. For example:
You must type this command exactly as shown.
|
CAPital LETters
|
Used to indicate valid abbreviations for keywords. For
example:
KEYWord=option
|
This section describes how to read the syntax diagrams (informally called
railroad tracks) used in this book.
- Read the diagrams from left-to-right, top-to-bottom, following the main
path line. Each diagram begins on the left with double arrowheads and
ends on the right with 2 arrowheads facing each other.
- If a diagram is longer than one line, the first line ends with a single
arrowhead and the second line begins with a single arrowhead.
- A word in all uppercase is a parameter that you must spell
exactly as shown.
- If you can abbreviate a parameter, the optional part of the parameter is
shown in lowercase. (You must type the text that is shown in
uppercase. You can type none, one, or more of the letters that are
shown in lowercase.)
- Note:
- Some TPF commands are case-sensitive and contain parameters that must be
entered exactly as shown. This information is noted in the description
of the appropriate commands.
- A word in all lowercase italics is a variable. Where you
see a variable in the syntax, you must replace it with one of its allowable
names or values, as defined in the text.
- Required parameters and variables are shown on the main path line.
You must code required parameters and variables.
- If there is more than one mutually exclusive required parameter or
variable to choose from, they are stacked vertically.
- Optional parameters and variables are shown below the main path
line. You can choose not to code optional parameters and
variables.
- If there is more than one mutually exclusive optional parameter or
variable to choose from, they are stacked vertically below the main path
line.
- An arrow returning to the left above a parameter or variable on the main
path line means that the parameter or variable can be repeated. The
comma (,) means that each parameter or variable must be separated from the
next parameter or variable by a comma.
- An arrow returning to the left above a group of parameters or variables
means that more than one can be selected, or a single one can be
repeated.
- If a diagram shows a blank space, you must code the blank space as part of
the syntax. In the following example, you must code
PARAMETER variable.
- If a diagram shows a character that is not alphanumeric (such as commas,
parentheses, periods, and equal signs), you must code the character as part of
the syntax. In the following example, you must code
PARAMETER=(begin.end).
- Default parameters and values are shown above the main path line.
The TPF system uses the default if you omit the parameter or value
entirely.
- References to syntax notes are shown as numbers enclosed in parentheses
above the line. Do not code the parentheses or the number.
Notes:
- An example of a syntax note.
- Some diagrams contain syntax fragments, which serve to break up
diagrams that are too long, too complex, or too repetitious. Syntax
fragment names are in mixed case and are shown in the diagram and in the
heading of the fragment. The fragment is placed below the main
diagram.
A list of related information follows. For information on how to
order or access any of this information, call your IBM representative.
- TPF General Macros, SH31-0152.
- ALCS Application Programming Reference --
Assembler Language, SH19-6949.
- ESA/370 Principles of Operation, SA22-7200
- ESA/390 Principles of Operation, SA22-7201
- High Level Assembler for MVS & VM & VSE
Language Reference, SC26-4940.
- Messages (System Error, Online, Offline) and Master
Glossary.
Your feedback is important in helping to provide the most accurate and
highest quality information. If you have any comments about this book
or any other TPF information, use one of the methods that follow. Make
sure you include the title and number of the book, the version of your product
and, if applicable, the specific location of the text you are commenting on
(for example, a page number or table number).
When you send comments to IBM, you grant IBM a nonexclusive right to use or
distribute your comments in any way it believes appropriate without incurring
any obligation to you.
- If you prefer to send your comments electronically, do either of the
following:
- If you prefer to send your comments by mail, address your comments
to:
IBM Corporation
TPF Systems Information Development
Mail Station P923
2455 South Road
Poughkeepsie, NY 12601-5400
USA
- If you prefer to send your comments by FAX, use this number:
- United States and Canada: 1 + 845 + 432 + 9788
- Other countries: (international code) + 845 + 432 +9788