gtpg1m06General Information


About This Book

This book provides a basic understanding of the IBM Transaction Processing Facility (TPF) Version 4 Release 1 system as well as an overview of the TPF operating system, describing its characteristics, functions, and the features that allow the TPF system to grow. This book helps your installation answer the question: "Should we buy the TPF 4.1 system?"

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, Systems Network Architecture (SNA). 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 the TPF Library Guide.

Who Should Read This Book

This book is intended for executives, managers, and system analysts to help them decide if the TPF system is suitable for their environment. It is also suitable for anyone who needs a general understanding of the TPF system.

The reader should have a basic knowledge of data processing and data communications.

How This Book is Organized

This book provides background information describing the TPF system, its concepts, structure, and features, and explains in detail the new functions in the TPF 4.1 system.

Conventions Used in the TPF Library

The TPF library uses the following conventions:

Conventions 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 ZFRST STATUS MODULE mod, where mod is the module for which you want status.


bold Used to represent text that you type. For example:

Enter ZNALS HELP to obtain help information for the ZNALS command.

Used to represent variable information in C language. For example:

level

monospaced Used for messages and information that displays on a screen. For example:
    PROCESSING COMPLETED

Used for C language functions. For example:

    maskc

Used for examples. For example:

    maskc(MASKC_ENABLE, MASKC_IO);
bold italic Used for emphasis. For example:

You must type this command exactly as shown.

Bold underscore Used to indicate the default in a list of options. For example:

Keyword=OPTION1 | DEFAULT

Vertical bar | Used to separate options in a list. (Also referred to as the OR symbol.) For example:

Keyword=Option1 | Option2

Note:
Sometimes the vertical bar is used as a pipe (which allows you to pass the output of one process as input to another process). The library information will clearly explain whenever the vertical bar is used for this reason.
CAPital LETters Used to indicate valid abbreviations for keywords. For example:

KEYWord=option

Scale Used to indicate the column location of input. The scale begins at column position 1. The plus sign (+) represents increments of 5 and the numerals represent increments of 10 on the scale. The first plus sign (+) represents column position 5; numeral 1 shows column position 10; numeral 2 shows column position 20 and so on. The following example shows the required text and column position for the image clear card.
|...+....1....+....2....+....3....+....4....+....5....+....6....+....7...
 
LOADER   IMAGE CLEAR
 

Notes:

  1. The word LOADER must begin in column 1.

  2. The word IMAGE must begin in column 10.

  3. The word CLEAR must begin in column 16.

Related Books

A list of related books for the TPF 4.1 announcement follows:

The following is an IBM Systems Application Architecture (SAA) book that can be purchased separately:

How to Send Your Comments

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.