z/OS TSO/E Programming Guide
Previous topic |
Next topic
|
Contents
|
Contact z/OS
|
Library
|
PDF
Contents (exploded view)
z/OS TSO/E Programming Guide
SA32-0981-00
Abstract for TSO/E Programming Guide
z/OS Version 2 Release 1 summary of changes
Introduction
Programming Using TSO/E
What is a REXX Exec?
What is a CLIST?
What is a command processor?
Considerations for Writing REXX Execs, CLISTs and command processors
Storing REXX Execs in VLF Storage
Controlling REXX Exec Compression
What is an APPC/MVS Transaction Program?
What is a Server?
Overview of TSO/E Programming Services
Syntax Notational Conventions
Writing a command processor
What is a command processor?
The TSO/E Environment
The command processor parameter list (CPPL)
Accessing the user profile table without a CPPL
Command Syntax
What is a Subcommand Processor?
Writing a command processor
Validating command operands
Using the parse service routine
Checking positional operands for logical errors
Checking unidentified keyword operands
Using the prompt mode HELP
A sample command processor
Communicating with the Terminal User
Issuing Messages
Message Levels
Using the I/O Service Routines to Handle Messages
Using the TSO/E Message Issuer Routine (IKJEFF02)
Using generalized routines for issuing messages
Performing Terminal I/O
Changing Your command processor's Source of Input
Writing a Full-Screen command processor
Set Full-Screen Mode On
TERMINAL BREAK Support for Full-Screen Mode
Give Control to the command processor
Write to and Get Information from the Terminal
Unlocking the Keyboard
Receiving Data
NOEDIT Mode
Considerations for Invoking an External Function:
Protection of Screen Contents
Restoration of Screen Contents
Exiting and Reentering Full-Screen Mode
Clearing the Terminal Screen
Full-Screen command processor Termination
Examples of Full-Screen command processor Operation
Function of RESHOW in Full-Screen Message Processing
Function of INITIAL=YES when the First Message is Full Screen
Function of INITIAL=YES when the First Message is Non-Full-Screen
Example 1
Example 2
Function of INITIAL=NO
Passing Control to Subcommand Processors
Step 1. Issuing a Mode Message and Retrieving an Input Line
Step 2. Validating the Subcommand Name
Step 3. Passing control to the subcommand processor
Writing a subcommand processor
Step 4. Releasing the Subcommand Processor
Processing Abnormal Terminations
Error handling routines
ESTAE and ESTAI Exit Routines
When are Error Handling Routines Needed?
Guidelines for Writing ESTAE and ESTAI Exit Routines
Linkage Considerations
Processing Attention Interruptions
Responding to Attention Interruptions
How Attention Interruptions are Processed
Deferring Attention Exits
System Use of STAX DEFER=YES
Writing Attention Handling Routines
Parameters Received by Attention Handling Routines
The Attention Exit Parameter List
The Terminal Attention Interrupt Element (TAIE)
Full-Screen Protection Responsibilities of Attention Exit Routines
Creating HELP Information
Writing HELP Members
Format of HELP Members
The prompt mode HELP function
An Example of a HELP Member
Installing a command processor
Using a Private Step Library
Placing Your command processor in SYS1.CMDLIB
Creating Your Own Command Library
Executing and Testing a command processor
Executing a command processor
Testing an Unauthorized command processor
Testing a command processor That is Terminating Abnormally
Testing a command processor not currently executing
Testing an authorized command processor
Preparing, Executing and Testing a Program
Overview of Preparing, Executing and Testing a Program
Compiling and Assembling Programs
ASM Command
COBOL Command
FORT Command
PLI Command
RUN Command
Compiling Source Code Statements
Passing Parameters When Compiling
Specifying a Subroutine Library When Compiling - the LIB Operand
Specifying VSBASIC Compiler Options
Binding or Link-Editing a Program
LINK Command
Creating a Program Object or Load Module
Resolving External References - the LIB Operand
Producing Output Listings - the PRINT Operand
Creating a Map of the Program Object or Load Module - the MAP Operand
Producing a List of All Binder or Linkage Editor Control Statements - the LIST Operand
Producing a Cross Reference Table - the XREF Operand
Producing a Symbol Table - the TEST Operand
Sending Error Messages to Your Terminal - the TERM/NOTERM Operand
Loading and Executing a Program
LOADGO Command
Loading and Executing Programs with No Operands
Passing Parameters when Loading and Executing Programs
Requesting Output Listings when Loading and Executing Programs - the PRINT/NOPRINT and TERM/NOTERM Operands
Resolving External References when Loading and Executing Programs - the CALL/NOCALL and LIB Operands
Specifying an Entry Point when Loading and Executing Programs - the EP Operand
Specifying Names when Loading and Executing Programs - the NAME Operand
CALL Command
Loading and Executing Load Modules
Passing Parameters when Loading and Executing Load Modules
Testing a Program
The TEST and TESTAUTH Commands
The TEST Command
The TESTAUTH Command
Using TEST or TESTAUTH
When to Use the TEST and TESTAUTH Commands
Testing a Currently Executing Program
Testing a program not currently executing
Testing an APPC/MVS Transaction Program
Examples of Issuing the TEST and TESTAUTH Commands
Example 1
Example 2
Example 3
Example 4
Example 5
Example 6
Example 7
Example 8
Example 9
Example 10
TEST and TESTAUTH Subcommands
Addressing Conventions Associated with TEST and TESTAUTH
Absolute Address
Relative Address
Symbolic Address
[Module-Name].Entry-Name
Qualified Addresses
General Registers
Floating-Point Registers
Vector Registers
Vector Mask Register
Access Registers
Indirect Address
Address Expression
Restrictions on the Use of Symbols
External Symbols
Internal Symbols
Addressing Considerations
Examples of Valid Addresses in TEST and TESTAUTH Subcommands
Programming Considerations for Using TEST and TESTAUTH
Considerations for 31-Bit addressing
Considerations for Using the Virtual Fetch Services
Considerations for a Cross-Memory Environment
Considerations for the Vector Facility
Considerations for Extended Addressing
Considerations for Testing Inbound APPC/MVS Transaction Programs
Considerations for a Tested Program's Environment
A Tutorial Using the TEST Command
How to Use This Tutorial
Preparing to Use TEST
Viewing a Program in Storage
Monitoring and Controlling Program Execution
Altering Storage and Registers
Using Additional Features of TEST
More TEST Subcommands
GETMAIN and FREEMAIN
LOAD and DELETE
CALL
Testing Programs That Use the Vector Facility
Testing Programs That Use Extended Addressing
Displaying and modifying access registers
Displaying and modifying data in alternate address spaces
Copying Data to and from Alternate Address Spaces
Providing Symbolic Names for Locations in Alternate Address Spaces
Example programs for the TEST tutorial
Copyright IBM Corporation 1990, 2014