TSO Useful Guide
TSO Useful Guide
TSO Useful Guide
IBM
GC28-1964-01
Note Before using this information and the product it supports, be sure to read the general information under Notices on page ix.
Contents
Notices . Trademarks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ix x xi xi xi xi xi xiii xiii 1-1 1-1 1-1 1-5 2-1 2-1 2-1 2-2 2-2 2-3 2-3 2-3 2-3 2-3 2-3 2-4
About This Book . . . . . . . Who Should Use This Book . . How This Book Is Organized . How to Use This Book . . . . . Where to Find More Information
Summary of Changes . . . . . . . . . . . . . . . . . . Changes to This Book for OS/390 Version 2 Release 4 Chapter 1. Introduction Users of TSO/E . . . . . Highlights of TSO/E . . Major Benefits of TSO/E
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
| | | | | | | | | | | |
Chapter 2. What's New in TSO/E for OS/390 Version 2 Release 4? . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel Sysplex Support TSO Generic Resource Support . . . . . . . . . . . . . . . . . . . . SEND Command Parallel Sysplex Support . . . . . . . . . . . . . . PARMLIB Command Parallel Sysplex Support . . . . . . . . . . . . CALL/TEST Data Set Search Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Log Size Allocation Dynamic LPA Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSO/E REXX DATE Function . . . . . . . . . . . . . . . . . . . . . . . . TSO/E Samples Renamed . . . . . . . . . . . . . . . . . . . . . . . . . Conditional Disposition Processing Improved . . . . . . . . . . . . . . . RECEIVE Command Processing Improved . . . . . . . . . . . . . . . . Chapter 3. End Use of TSO/E . . . . . TSO/E Information Center Facility . . . . News Service . . . . . . . . . . . . . . Names Directory . . . . . . . . . . . . . Conduit Dialogs . . . . . . . . . . . . . Education Services . . . . . . . . . . . Group and Private Application Manager Group Specification . . . . . . . . . . . Print Service . . . . . . . . . . . . . . . Tutorials and Help Information . . . . . TSO/E Enhanced Connectivity Facility . Services Available . . . . . . . . . . . . Accessing MVS Services from the PC Diagnosing Related Problems . . . . . Support for VM/PC Host Services . . . . Services Available to VM/PC Users . . Accessing the VM/PC Servers . . . . . Session Manager . . . . . . . . . . . . . . End User Commands . . . . . . . . . . . Assistance to Users . . . . . . . . . . .
Copyright IBM Corp. 1988, 1997
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
3-1 3-1 . 3-2 . 3-3 . 3-3 . 3-3 . 3-3 . 3-4 . 3-4 . 3-4 . 3-5 . 3-5 . 3-5 . 3-5 . 3-5 . 3-6 . 3-6 . 3-6 . 3-8 3-10
iii
Chapter 4. Programming . . . . . . . . . . . . . . . . . . . . REXX Programming Language . . . . . . . . . . . . . . . . . . Features of REXX . . . . . . . . . . . . . . . . . . . . . . . . Using APPC/MVS Services in a REXX Exec . . . . . . . . Additional TSO/E REXX Support . . . . . . . . . . . . . . . The Data Stack . . . . . . . . . . . . . . . . . . . . . . . . . Storing REXX Execs . . . . . . . . . . . . . . . . . . . . . . CLIST Programming Language . . . . . . . . . . . . . . . . . . ALTLIB Command . . . . . . . . . . . . . . . . . . . . . . . . . TSOLIB Command . . . . . . . . . . . . . . . . . . . . . . . . . Server-Requester Programming Interface . . . . . . . . . . . . Writing Servers on TSO/E . . . . . . . . . . . . . . . . . . . Support for Writing Command Processors . . . . . . . . . . . Support for Using TSO/E Services in Non-TSO/E Environment Programming Services . . . . . . . . . . . . . . . . . . . . . . . TEST and TESTAUTH Commands . . . . . . . . . . . . . . . Command Package . . . . . . . . . . . . . . . . . . . . . . . . Running Terminal Sessions as Batch Jobs . . . . . . . . . Automatic Saving of Data . . . . . . . . . . . . . . . . . . . Accounting Facilities Enhancements . . . . . . . . . . . . . Defaults for the User Attribute Data Set . . . . . . . . . . . ATTRIB and FREE Subcommands . . . . . . . . . . . . . . ALL Keyword for the FREE Command and Subcommand Eight-Character Station ID . . . . . . . . . . . . . . . . . . . APPC/MVS Administration Dialog . . . . . . . . . . . . . . . . TSO/E Support for a REXX Compiler . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1 . 4-2 . 4-2 . 4-4 . 4-4 . 4-6 . 4-7 . 4-8 . 4-8 . 4-9 . 4-9 4-10 4-10 4-11 4-11 4-13 4-13 4-13 4-14 4-14 4-14 4-15 4-15 4-15 4-15 4-15
Chapter 5. Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 TSO/E Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 VTAM and TCAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Logon Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 The Logon/Logoff Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 ISPF/PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Authorized Commands and Programs and Commands Not Supported in the Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 TRANSMIT and RECEIVE Availability . . . . . . . . . . . . . . . . . . . . . . 5-5 HELP Data Set Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Host Services Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Language Enablement Support . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Command/Program Invocation Platform Support . . . . . . . . . . . . . . . . 5-7 TSO/E Resource Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 The UADS and RACF Data Base . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 TSO/E Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 ALLOCATE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 CANCEL, OUTPUT, STATUS, and SUBMIT Commands . . . . . . . . . . . 5-9 CONSOLE and CONSPROF Commands . . . . . . . . . . . . . . . . . . . 5-10 EDIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 LISTBC, OPERATOR SEND, and SEND Commands . . . . . . . . . . . . 5-11 PRINTDS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 TEST and TESTAUTH Commands . . . . . . . . . . . . . . . . . . . . . . . 5-12 TRANSMIT and RECEIVE Commands . . . . . . . . . . . . . . . . . . . . . 5-13 SYS1.PARMLIB Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13 PARMLIB Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 CLIST Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
iv
REXX Processing . . . . . . . . . . . . . . . . . . . . Language Processor Environment Characteristics Replaceable Service Routines . . . . . . . . . . . . REXX Exits . . . . . . . . . . . . . . . . . . . . . . . Session Manager . . . . . . . . . . . . . . . . . . . . . Information Center Facility . . . . . . . . . . . . . . . Adding, Modifying, or Deleting a Product or Service Creating or Tailoring Application Definitions . . . . Adding Commands . . . . . . . . . . . . . . . . . . Modifying Start-Up and Termination Processing . Writing Exits . . . . . . . . . . . . . . . . . . . . . . Enhanced Connectivity Facility . . . . . . . . . . . . . User-Written Access Method Driver Interface . . . TSO/E Exits . . . . . . . . . . . . . . . . . . . . . . . . Chapter 6. Administration . . . . . . . . . . . . . Administering TSO/E . . . . . . . . . . . . . . . . . . ENROLL Option of the Information Center Facility RACF Commands . . . . . . . . . . . . . . . . . . TSO/E ACCOUNT Command . . . . . . . . . . . Converting to the RACF Data Base . . . . . . . . Administering the TSO/E Information Center Facility NEWS Maintain System News . . . . . . . . . NAMES Maintain the Name/Phone Directory ENROLL Enroll Users in the ICF . . . . . . . USERTYPE Set Defaults for User Types . . . SYSDEF Set System Defaults . . . . . . . . . COURSES Maintain Education Services . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-14 5-14 5-14 5-15 5-15 5-15 5-16 5-17 5-17 5-18 5-18 5-18 5-18 5-19 6-1 6-1 6-1 6-2 6-2 6-2 6-2 6-3 6-3 6-4 6-4 6-4 6-6 7-1 7-1 7-2 7-2 7-2 7-3 7-4 7-5 7-6 X-1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7. Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages and Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tracing Execution of Programs and Installation Exits . . . . . . . . . . . TRACE Function of the Information Center Facility . . . . . . . . . . . . . . . . . . . . . . . . MVSSERV Trace Facility and Trace Data Set TSO/E TEST and TESTAUTH Commands . . . . . . . . . . . . . . . Debug Facilities for REXX Execs . . . . . . . . . . . . . . . . . . . . . Using the OPERATOR SLIP Command to Diagnose Installation Exits TSODATA Dump Formatter . . . . . . . . . . . . . . . . . . . . . . . . . . Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
vi
Figures
| 2-1. 3-1. 3-2. 3-3. 5-1. 6-1. Settings in SYS1.PARMLIB(GRSRNL) . . . . . Information Center Facility User's Primary Panel Session Manager Display Screen . . . . . . . . Summary of the TSO/E Commands . . . . . . . Overview of Exit Points that TSO/E Provides . Main Menu Panel For Administrator Tasks . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vii
viii
Notices
References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program or service is not intended to state or imply that only IBM's product, program or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, programs, or services except those expressly designated by IBM, are the user's responsibility. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Corporation Mail Station P131 522 South Road Poughkeepsie, NY 12601-5400 USA Attention: Information Request Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact IBM Informationssysteme GmbH Abteilung Recht 0215 Pascalstr. 100 70569 Stuttgart Federal Republic of Germany Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. For online versions of this book, we authorize you to: Copy, modify, and print the documentation contained on the media, for use within your enterprise, provided you reproduce the copyright notice, all warning statements, and other required statements on each copy or partial copy. Transfer the original unaltered copy of the documentation when you transfer the related IBM product (which may be either machines you own, or programs, if the program's license terms permit a transfer). You must, at the same time, destroy all other copies of the documentation. You are responsible for payment of any taxes, including personal property taxes, resulting from this authorization. THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
ix
Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. Your failure to comply with the terms above terminates this authorization. Upon termination, you must destroy your machine readable documentation.
Trademarks
The following terms are trademarks of the IBM Corporation in the United States or other countries or both: ACF/VTAM AFP APL2 AT DFSMS/MVS Enterprise Systems Architecture/370 GDDM IBM MVS/ESA MVS/SP OS/2 OS/390 OS/400 Personal Computer AT Personal Computer XT Personal System/2 QMF RACF SAA System/370 Systems Application Architecture VTAM XT 3090 Other company, product, and service names, which may be denoted by a double asterisk (**), may be trademarks or service marks of others.
| | | | | | | | |
The latest OS/390 documentation is available on the OS/390 Collection CD ROM (GC23-3292). The following OS/390 TSO/E documentation has been updated for version 2 release 4. The updated documentation is available only on CD ROM. Hardcopy versions of these documents for OS/390 version 1 release 2 can still be ordered:
Primer (GC28-1967) REXX User's guide (SC28-1974) Guide to SRPI (SC28-1976) VM/PC User's Guide for OS/390 Host Services (SC28-1977)
xi
| | | | | | | | | | | | | | | | | | |
The following OS/390 TSO/E documentation has been updated for version 2 release 4, and is now available only on CD ROM:
General Information (GC28-1964) Messages (GC28-1978) Customization (GC28-1965) Programming Services (SC28-1971) System Programming Command Reference (SC28-1972) Command Reference (SC28-1969) CLISTs (SC28-1973) REXX Reference (SC28-1975)
The following OS/390 TSO/E documentation has not been updated for version 2 release 4. The version 1 release 2 documents are still available as hardcopy and on CD ROM:
OS/390 TSO/E Administration (SC28-1966) OS/390 TSO/E User's Guide (SC28-1968) OS/390 TSO/E Programming Guide (SC28-1970)
xii
Summary of Changes
| | |
The most significant command enhancements and other important changes in OS/390 version 2 release 4 are described in Chapter 2, What's New in TSO/E for OS/390 Version 2 Release 4? on page 2-1.
xiii
xiv
Highlights of TSO/E
Chapter 1. Introduction
Users of TSO/E . . . . . Highlights of TSO/E . . Major Benefits of TSO/E
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSO/E is a base element of OS/390.1 TSO/E allows users to interactively share computer time and resources. In general, TSO/E makes it easier for people with all levels of experience to interact with the MVS system.
Users of TSO/E
TSO/E has advantages for a wide range of computer users. TSO/E users include system programmers, application programmers, information center administrators, information center users, TSO/E administrators, and others who access applications that run under TSO/E. The different chapters of this book describe the major tasks that each of these users can perform using TSO/E.
Highlights of TSO/E
The TSO/E element of OS/390 originated from the former TSO/E component of previous MVS/ESA systems. It originally contained a set of commands and a set of system services that end users and programmers could use when writing their own commands. During its life it was continually enhanced and became the primary user interface to the OS/390 system. The highlights of TSO/E follow. Later chapters describe these highlights in more detail under the user tasks to which they apply. The Information Center Facility The Information Center Facility is the foundation for building an MVS-based information center (IC). An IC increases user productivity and the computer effectiveness by providing easy-to-use computing tools, data access, education, and other assistance for users who have little or no data processing experience. The Information Center Facility eases users into the data processing environment by providing a series of conversational panels. These panels eliminate numerous command-driven interactions between the user and the system. In addition to end user services, the Information Center Facility provides panels that enable an administrator to maintain the facility, enroll users, and add, modify, and delete products. TSO/E provides several new functions that help an administrator to easily install, maintain, and upgrade products in the Information Center Facility. TSO/E also provides support for tailoring Information Center Facility panels, functions, and environments to the needs of different departments or user groups and individual users. This enhancement eliminates the requirement to make all products in the Information Center Facility available to all users.
Before OS/390*, TSO Extensions (TSO/E) was a licensed program for the MVS and MVS/ESA System Products, and it was an extension of the Time Sharing Option (TSO) of former MVS systems.
1-1
Highlights of TSO/E
The Enhanced Connectivity Facility The Enhanced Connectivity Facility contains the MVS support for the IBM* System/370* to IBM Personal Computer Enhanced Connectivity Facilities. Those facilities allow a person using an IBM Personal Computer (PC), an IBM 3270 PC (also referred to as a PC), or an IBM Personal System/2* to use services, data, and resources available on an IBM System/370 host processor using MVS or VM. IBM products or customer-written programs can supply the services. The PC user does not have to leave the PC environment to access host services and data. Using the MVSSERV command, PC users can access MVS services and data available through TSO/E. VM/PC host services The MVSSERV command processor also supports the VM/PC host services. The VM/PC host services allow a VM/PC user on an IBM PC XT*/370 or an IBM PC AT*/370 to access data, services, and resources that run on an IBM System/370 host processor using MVS. Without leaving the PC environment, the user requests the services by issuing VM/PC commands. The Session Manager The TSO/E Session Manager is an interface to line mode TSO/E. It saves the commands that you enter and the responses that you receive and allows you to redisplay or print them. You can correct or change a command that is displayed on the screen without having to retype the entire command. By allowing you to redisplay, change, and reuse your input, the Session Manager makes TSO/E easier to use. Commands TSO/E provides numerous commands for both end users and programmers that allow them to interact with TSO/E and the MVS system. The ALLOCATE, FREE, and EDIT commands are examples of commands that allow users to manage their data sets. The TEST and TESTAUTH commands let programmers test assembler language programs, including command processors, APPC/MVS transaction programs, and other programs written in assembler language. The CONSOLE command lets users with CONSOLE command authority perform MVS operator activities from a TSO/E session. Figure 3-3 on page 3-8 provides brief descriptions of the TSO/E commands for end users. Descriptions of other commands are provided in the individual chapters that discuss the related tasks. Online help Terminal users can obtain online help for most TSO/E commands. Information Center Facility users can obtain help for each panel and message. TSO/E Enhanced Connectivity Facility users can also obtain online help for terminal messages. In addition, the HELP facility is enhanced to allow installations greater flexibility in adding help information. Installations can also provide online help information to users in different languages. Data and notice handling TSO/E simplifies the way in which data and notices are sent and received. For example, the TRANSMIT and RECEIVE commands let users send data and messages to other users in a network.
1-2
Highlights of TSO/E
TSO/E improves the LISTBC command so that it requires fewer I/O operations to list the contents of the broadcast data set. The broadcast data set or individual user logs contain messages that either the system or another user sends using the SEND command. In addition, a recovery routine prevents broken mail chains that could occur when message handling is interrupted. Notices are also handled more efficiently during logon processing. TSO/E keeps a copy of notices in storage, thereby reducing the I/O operations needed to inform users of waiting messages when they logon. Logon processing TSO/E provides a full-screen logon panel that makes the logon process easier by: Saving user attributes from one session to the next Allowing program function keys to be used during logon Allowing users to enter commands during logon Explaining the error when incorrect information is specified.
In addition to the full-screen enhancements, a user can request an expanded private area (region) during logon. The LOGON and ACCOUNT command processors allow users to request private areas of up to 2,096,128 K bytes for each terminal session. Your installation can also customize the logon panel, the logon help panel, and customize logon processing using different exits. Language enablement TSO/E takes advantage of the MVS message service 4 to allow installations to provide TSO/E messages and the TRANSMIT full-screen panel to users in different languages. The TSO/E CONSOLE command also supports the display of translated system messages issued during a console session. Several enhancements are provided for language enablement. The logon authorized pre-prompt exit and the PROFILE command support the specification of languages to be used in displaying translated information. Enhancements to SYS1.PARMLIB member IKJTSOxx allow installations to specify help data sets for different languages. The TRANSMIT command is also enhanced to allow users to enter Double-Byte Character Set (DBCS) text on the full-screen panel. Support for logon panels and their help text in different languages is also available. The TSO/E REXX external function, SYSVAR, provides support for new arguments that REXX execs can use to obtain language information. Execs can use this information together with the new SETLANG function to set the language in which REXX messages are displayed. Security Installations that have RACF installed can use security labels (SECLABELs) to protect system resources. TSO/E provides several enhancements to support the use of security labels. The LOGON command and full-screen logon panel support the specification of a security label to be associated with a user's TSO/E session. SUBMIT command enhancements enable users to submit jobs at a security label that is greater than the one they are currently logged on with. OUTDES command enhancements let users print the job's security label on each page of output. Installations can also control communication between users to protect the security classification of information. For example, installations can control and
Chapter 1. Introduction
1-3
Highlights of TSO/E
audit the use of the SEND command. LISTBC command processing enhancements let installations restrict users from viewing messages for which they do not have the proper security. The TRANSMIT command supports a new keyword that lets users specify an alternate data set to log transmitted data. This enhancement allows users to log transmitted data at different security labels. CLIST language The CLIST language is a high-level programming language that lets programmers issue lists of TSO/E commands and JCL statements in combination with logical, arithmetic, and string-handling functions provided by the language. The programs, called CLISTs, can simplify routine user tasks, invoke programs written in other languages, and perform complex programming functions by themselves. Restructured Extended Executor (REXX) language support TSO/E provides REXX support to MVS users. REXX is a high-level procedures language that enables inexperienced users as well as experienced programmers to write structured programs called REXX execs. You can execute REXX execs in any MVS address space (both TSO/E and non-TSO/E). TSO/E also allows users to write APPC/MVS transaction programs in the REXX language. The REXX language allows programmers to perform logical and arithmetic operations and communicate with terminal users. REXX built- in functions increase usability by allowing you to easily perform character manipulation and conversion operations. REXX also provides support for issuing host commands from within a REXX exec. TSO/E extends the programming capabilities of REXX by providing TSO/E functions, REXX commands, and programming and customizing services. These facilities allow you to perform additional tasks such as controlling the execution of a REXX exec and customizing how system services are accessed and used. Some of these facilities are available only to REXX execs that execute in the TSO/E address space. REXX execs perform functions similar to CLISTs and can call, and be called by, existing CLISTs and other TSO/E programs. Therefore, REXX is an attractive alternative to the CLIST language. TSO/E REXX is the implementation of the Systems Application Architecture* (SAA*) Procedures Language on the MVS system. By using the instructions and functions defined for the SAA Procedures Language, you can write execs that will run in any of the supported SAA environments, such as VM/SP (CMS). The TSO/E service facility The TSO/E service facility lets TSO/E users execute authorized or unauthorized programs, TSO/E commands, or CLISTs from an unauthorized environment, while maintaining system integrity. TSO/E Release 1 enhances the TSO/E service facility to allow users to optionally bypass some internal processing when accessing an unauthorized command, program, or CLIST from an unauthorized environment. This enhancement can result in a potential performance benefit and it also permits linkage to the ISPEXEC interface of ISPF. In TSO/E Release 2, the command/program invocation platform support, described in TSO/E Programming Services, SC28-1971, extends the bypassing of internal processing to the initialization and termination environments for the
1-4
TSO/E service facility. In TSO/E Release 3, the command/program invocation platform support further extends the TSO/E service facility enhancement to include authorized commands and also unauthorized and authorized programs. TSO Command Package The TSO Command Package provides functions that help to improve productivity. The functions included are: Support for running terminal sessions as batch jobs Automatic saving of data Accounting facility enhancements Defaults for the user-attribute data set Enhancements to several commands.
Support for a REXX compiler Installations can take advantage of the REXX compiler support by adding the IBM Compiler and Library for REXX/370 (licensed program number 5695-013) or a functionally equivalent compiler. A REXX compiler communicates with TSO/E using defined interfaces. A compiled REXX exec executes more efficiently because the exec does not need to be interpreted at run time. Support for OpenMVS Installations can use the functions provided by the TSO/E ALLOCATE and FREE commands to manipulate OpenMVS files.
Chapter 1. Introduction
1-5
TSO/E continues to improve usability for users. The TEST and TESTAUTH commands enable programmers to easily test unauthorized programs and APF-authorized programs. The support for language enablement allows users to receive TSO/E information in their national language. Applications running in non-TSO/E address spaces can use many TSO/E services and unauthorized commands. This includes writing APPC/MVS transaction programs that access TSO/E services. Applications can use the TSO/E environment service to build and initialize a TSO/E environment. TSO/E provides usability enhancements to logon processing. Installations can customize the logon panel and its help text. Installations can process fields on the logon panel using the pre-display and post-display logon installation exits. For installations that support more than one language, logon panels and their help text are also supported in different languages. In addition, LOGON command full-screen processing is enhanced to perform new password verification. Also provided is a post-prompt exit to customize the logon processing after logon prompting has completed. Improved productivity TSO/E can help improve end user and programmer productivity. The functions available through the Information Center Facility, the Enhanced Connectivity Facility, the TSO Command Package and the Session Manager are intended for that purpose. The CLIST language, TSO/E REXX support and TSO/E command enhancements are also intended to allow end users and programmers to work more productively. Improved performance TSO/E provides several enhancements that are intended to improve performance. For example, changes to the way TSO/E processes CLISTs improve CLIST performance. Work areas for TSO/E service routines are obtained during logon processing rather than each time they are required, thereby improving performance. Message-handling performance is also improved by decreasing the number of I/O operations needed to use the LISTBC command and to process notices during logon. The use of separate user logs provides a potential performance benefit. Installations can store messages in separate user logs rather than in the broadcast data set. The use of separate logs reduces possible contention that processors could experience when a large number of messages are being stored in or retrieved from the broadcast data set. TSO/E continues to provide ways to improve performance. For example, the ALTLIB command lets users dynamically allocate CLIST and REXX exec libraries. Dynamic definition of CLIST and REXX exec libraries reduces the time it takes to search for these libraries. Use of the MVS/ESA SP virtual lookaside facility (VLF) provides a potential performance benefit to CLIST and REXX exec users by helping to reduce data set I/O and DASD contention. Enhancements to TSO/E REXX support and the TSO/E service facility provide a potential performance benefit to users by helping to reduce the system overhead associated with task creation and termination on the invocation of unauthorized and authorized TSO/E commands and programs. REXX execs that are allocated to the SYSPROC system level or application level file are compressed when they are stored. The compression of REXX execs provides a potential performance benefit. This enhancement reduces the amount of virtual storage required for processing REXX execs.
1-6
TSO/E processing of the SYS1.BRODCAST data set has been enhanced to use the cross-system coupling facility. This enhancement provides a potential performance benefit during logon processing by helping to reduce I/O to the SYS1.BRODCAST data set for the display of system notices. Enhancements within the ALLOCATE command potentially improve performance by reducing I/O to the VTOC for existing catalogued data sets and by avoiding MVS LOAD processing on most invocations. In addition, the ALLOCATE command reduces the use of MVS services by streamlining its internal processing. TSO/E code optimization enhancements within the TSO/E I/O services, REXX processing, CLIST processing, and TSO/E exit processing, reduce the TSO/E working set size. APPC/MVS support TSO/E also supports writing APPC/MVS transaction programs in the REXX procedural language. The CPICOMM host command environment allows transaction programs written in REXX to be ported across SAA environments. The LU62 host command environment allows you to use specific features of MVS in conversations with transaction programs on other systems. Virtual storage constraint relief In the MVS environment, TSO/E provides virtual storage constraint relief. Many TSO/E modules and storage areas reside above 16 MB in virtual storage, thereby freeing more virtual storage below 16 MB for users' applications. In addition, whenever possible, new modules and storage areas are located above 16 MB in virtual storage. Installation simplification TSO/E provides ways to simplify the installation process. System programmers can use SYS1.PARMLIB rather than tables (IKJEFTE2, IKJEFTE8, IKJEFTNS, and IKJEFTAP) to specify authorized commands, authorized programs, and the commands that users cannot run in the background. They can use SYS1.PARMLIB to also specify system defaults for several commands. Using SYS1.PARMLIB makes it easier to customize a system because installations need to change only one file. Programmers no longer have to save tables, and assemble and link-edit them each time they install TSO/E. TSO/E enhances SYS1.PARMLIB support. System programmers can use SYS1.PARMLIB to set system defaults for additional commands. They can also use the new PARMLIB command to list the current TSO/E system defaults and dynamically update them (with the contents of IKJTSOxx) without having to re-IPL the system. SYS1.SAMPLIB contains samples that an installation can customize to simplify the installation process. For example, the IKJTSO00 member of SYS1.SAMPLIB contains samples of the statements that you can use in the IKJTSOxx member of SYS1.PARMLIB. In TSO/E, a table look-up service also helps simplify installation. System programmers can use the table look-up service to determine which commands and programs are authorized and which commands are restricted from use in the background.
Chapter 1. Introduction
1-7
Systems management TSO/E improves system management. The new CONSOLE command allows TSO/E users with CONSOLE command authority to issue MVS system and subsystem commands from a TSO/E session and receive responses to those commands. A message retrieval service, GETMSG, and enhancements to TSO/E REXX support allow application programs and REXX execs to also perform MVS operator tasks in the TSO/E environment. Systems Application Architecture support TSO/E supports Systems Application Architecture (SAA) by providing the procedures language interface elements of REXX in an MVS environment. The CALL command processor is also enhanced to support SAA. Improved debugging aids TSO/E provides improved debugging aids. For example, the TEST command contains support for debugging programs that use the IBM 3090* vector facility hardware. In TSO/E, the TEST command is further enhanced to allow programmers to debug programs that use access registers. TSO/E also provides a new command, TESTAUTH, that allows programmers to test and debug APF-authorized programs. The TEST and TESTAUTH commands also allow users to test APPC/MVS unauthorized and authorized transaction programs. The Interactive Problem Control System (IPCS) TSODATA verb exit lists additional information related to CLIST variables. In TSO/E, the IPCS TSODATA verb exit is updated to help programmers diagnose problems related to REXX code or the CONSOLE command. New keywords allow users to format REXX environment blocks and the CONSOLE command control block. Tracing functions similar to those available for CLISTs are available for REXX execs. The MVSSERV trace facility enables TSO/E Enhanced Connectivity Facility applications to write messages to the MVSSERV trace data set, the terminal, or both. TSO/E provides support for tracing installation exits. Programmers can use the OPERATOR SLIP command to trace exit points on the call and return from the exit and display the exit parameter list. Additional exits TSO/E provides more exits that allow you to modify or extend the processing of many TSO/E commands and functions to suit the needs of your installation. Many of the exits provide a standard exit parameter list to the exit routines receiving control.
1-8
| | | | | | | | | | | | | | |
2-1 2-1 2-2 2-2 2-3 2-3 2-3 2-3 2-3 2-3 2-4
This chapter summarizes the new functionality and important changes in TSO/E for OS/390 Version 2 Release 4.
| | | | | | | | | | | | | | |
2-1
| | | | | | | | | | Figure 2-1. Settings in SYS1.PARMLIB(GRSRNL) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For more information about the TSO generic resources see OS/390 MVS Initialization and Tuning Reference, SC28-1752 and also OS/390 MVS System Commands, GC28-1781. Reconnection support ensures that a user's address space is kept for a specified reconnect interval after a TSO user looses connectivity to the TSO system. During this interval, if the user tries to reconnect, he will be automatically reconnected to the system, application, and address space that he originally had. // / SYSTEM INCLUSION RESOURCE NAME LIST - RNLDEF STATEMENTS / // RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSIKJBC) RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSIKJUA)
2-2
| | | | |
| | | | | | | | |
| | | |
| | | | |
| | |
| | | | | | |
2-3
| | | | | |
2-4
3-1 3-2 . 3-3 . 3-3 . 3-3 . 3-3 . 3-4 . 3-4 . 3-4 . 3-5 . 3-5 . 3-5 . 3-5 . 3-5 . 3-6 . 3-6 . 3-6 . 3-8 3-10
End use means directly using a product for its intended purpose; in this case, using TSO/E to interact with MVS and perform work on the system. This work includes running programs, creating reports, and entering and managing data. The following topics describe the end use facilities that TSO/E provides.
3-1
The Information Center Facility end user interface begins with a main menu panel that displays a list of options with descriptions and characters for selecting the options. If your installation has not customized the Information Center Facility, your main menu panel for end user tasks will look something like the panel shown in Figure 3-1 on page 3-2.
TSO/E Information Center Facility User Services OPTION===>_ Select one of the following options. 1 2 3 4 5 6 7 8 9 1 I T X DESCRIBE NEWS NAMES OFFICE PROGRAM ANALYSIS CHART COURSES PDF PROBLEM UTIL INTRO TUTORIAL EXIT To scroll, press UP or DOWN.
Read a short description of the options on this panel Obtain system news Find a name/phone number Use mail/document/other office services Use program creation/execution services Perform decision support/data analysis/ report creation Create charts/graphs Use education services Use ISPF/PDF services Report problems Information Center Facility Utilities Learn to use the Information Center Facility Read a detailed description of the options on this panel Exit
To view PF key definitions, type KEYS on Command or Option line of any panel.
The Information Center Facility provides the following end use functions: News service Names directory Conduit dialogs (options 3, 4, 5, 6, 8, 9, 10) Education services Group and private Application Manager Group specification Print service Tutorials and help information.
News Service
The news service allows Information Center Facility users to view news items distributed online by an administrator. With TSO/E, users can also print news items. Users are notified of added news when they enter the Information Center Facility. They can use the NEW command within the news service to see just that news, or they can request to see news items dated on or after a specified date. Users can also make requests to the administrator to add news items.
3-2
Names Directory
The names directory gives Information Center Facility users access to information about other users, such as a person's phone number, user ID, address, and title. The directory can also contain groups. A group can contain names of individuals and names of other groups. Using a group name saves time because a user specifies the group name to represent frequently used combinations of names. Names and groups can be added, updated, and deleted by an Information Center Facility Administrator. The names directory also allows users to maintain and use a private directory as well as the master directory that the administrator maintains. A user can view private directory entries, master directory entries, or a merged list that contains the names in both the master directory and the private directory. A user can also use the Information Center Facility to ask the administrator to make updates to the master directory.
Conduit Dialogs
On the user's main menu panel, options 3, 4, 5, 6, 8, 9, and 10 support conduit dialogs. Each conduit dialog provides an interactive process for the user to access the associated licensed program product installed at an installation. Using the program products, users can generate reports, modify and manipulate data, perform business-related analyses, make spontaneous inquiries of the system, and perform other tasks that require the use of computing systems.
Education Services
Education services let users take a course, audit a course, produce (write) a course, view a course abstract, and request registration in a course. With TSO/E, users can also print course abstracts. Users can access IIPS, COMPUTER, and CLASSROOM type courses. The IIPS and COMPUTER courses are online courses. An IIPS course is a course that is developed using the Interactive Instructional Presentation System (IIPS) and the Interactive Instructional Authoring System (IIAS). A COMPUTER course is any course, other than an IIPS course, that the user can access online. CLASSROOM refers to a course that is conducted in a classroom. The Information Center Facility administrator can provide abstracts for the courses, register students, keep a record of course registration, and modify the administration defaults to indicate which courses are actually available at an installation.
3-3
an entire system. The group and private Application Manager dialogs are accessed from the user's primary panel (option 4, PROGRAM) and can be used to create or tailor application definitions to the needs of specific groups of users or individual users. If you have been assigned as the administrator for your group, you can use group Application Manager to customize the options available on Information Center Facility menus for your group. For example, your department may require a service that is not defined at the system level. You can use group Application Manager to add this service to the Information Center Facility and make it available just for your group. You can also make certain system level services unavailable to your group. If you are an experienced user and the system or group application definitions do not satisfy your needs, you can use private Application Manager to customize application definitions for your own use. For example, if the system administrator has installed the APL2* program product as an option on the programmer services panel, and you primarily use the Information Center Facility to write APL2 programs, you can use private Application Manager to make APL2 an option on your main menu panel. See Applications on page 6-5 for an overview of the operations you can perform on applications using Application Manager. See TSO/E Administration, SC28-1966, for complete information about how to use group and private Application Manager.
Group Specification
Your installation may have tailored Information Center Facility menus for different departments or user groups to satisfy their different needs. If you are given authorization, you can use the menus tailored for a specific group or department. The group specification function, which is accessed from option 4, PROGRAM, allows you to specify the name of a group whose menus you want to use for your next Information Center Facility session. For more information, see TSO/E Primer, GC28-1967.
Print Service
The print service, which is available under option 10, UTILITY, allows users to print both sequential and partitioned data sets, with all or selected members. If users are unsure of the data set name or member name, they can display data set and member selection lists from which they can specify a print request. They can also select a printer from the list of available printers and request multiple copies of the printed data set.
3-4
Services Available
The TSO/E Enhanced Connectivity Facility programs supplied by IBM allow a PC user to perform the following types of tasks: Access host data. Store PC data on the host system. Print PC data on the host. Off-load PC files and disks to the host. Execute host procedures.
3-5
Session Manager
Session Manager
TSO/E Session Manager is an interface to line mode TSO/E that provides full-screen display support for line-oriented commands, programs, CLISTs, and REXX execs. TSO/E Session Manager keeps a complete journal of everything that happens during your terminal session while you are in line mode TSO/E. It records everything you type in and everything the system displays. Any time during your terminal session, you can look at work you did in the beginning, middle, or end of your session. TSO/E Session Manager also lets you print a copy of this information. Using Session Manager, you can: Keep a record of your interaction with TSO/E. Edit and reuse previous input and output with a minimal number of keystrokes. This data can easily be reentered as input, saved in a data set, or printed. Access, compare, and manipulate the data needed to do your work directly on the screen. You no longer have to rely on physical documents and listings that are often outdated, time-consuming to obtain, and cumbersome to work with. You can use PF keys to locate data quickly and to move efficiently through data streams. TSO/E Session Manager enhances the usability of the TSO/E TEST command and other interactive debugging tools. You can keep track of which data areas you have viewed and print the output from the TEST command. To use Session Manager, you need access to a LOGON procedure that recognizes Session Manager.
3-6
Session Manager
The Session Manager default screen supplied by IBM is divided into five major areas called windows. These windows can be used to enter, look at, and change the work on the screen. Figure 3-2 shows the default display screen.
(1)
(2)
(4)
(5)
(3)
The following list describes each window: Windows (1) MAIN Definition The large portion of the display screen above the numbered line is the MAIN window. This window displays a certain number of lines in the stream of data containing TSO/E input and output. If you wish to submit one or more of these lines as input to TSO/E, type over any character on a line and press the Enter key. Just below the numbered line is the CURRENT window. When you first log on, this window displays the last two lines of output generated. A PF key lets you alternate the contents of this window between the last two lines of input entered and the last two lines of output generated. The STATUS windows for the MAIN window are located in the lower right hand corner of the display screen. The top window shows the scroll amount (labelled SCROLL===>HALF) and the bottom window indicates whether the MAIN window is locked or unlocked. The top of the MAIN window contains older data in the stream. When enough data has been generated to fill the MAIN window, the older data begins to be pushed out of the top of the window. You can use PF keys to scroll forward,
Chapter 3. End Use of TSO/E
(2) CURRENT
(3) STATUS
3-7
backward, left, and right in the stream. This action locks the window in place over the desired section of the stream. The keyboard remains unlocked so that you can edit lines in the window. (4) ENTRY The ENTRY window begins right after the arrow near the bottom of your display screen and continues to the vertical bar on the last line of the screen. This area is where you normally type in TSO/E commands. The window after the vertical bar is the PASSWORD window and can be used to type in passwords for your data sets. The information you type in the PASSWORD window does not appear on the display screen or in your session journal. The TSO/E Session Manager also uses the PASSWORD window to display any error messages to you. Installations can tailor the layout of the display screen and the terminal environment to the requirements of its users. Experienced users can also tailor the screen layout and PF key definitions to suit their own needs by using Session Manager commands. These commands can easily be put in a CLIST, enabling all users to tailor the environment for themselves.
(5) PASSWORD
The VLFNOTE command is an MVS/ESA SP command that TSO/E supports. OS/390 V2R4.0 TSO/E General Information
3-8
HELP
OUTDES OUTPUT
3-9
Assistance to Users
TSO/E provides users with online help for commands when they type a ? in response to a prompt. By default, TSO/E provides the prompt mode HELP function for all keyword operands on all commands except the TEST command. It is also available for positional operands of the ATTRIB, CALL, CANCEL, EDIT, EXEC, HELP, OUTPUT, RUN, and SEND commands. The additional information is not available for any subcommands. TSO/E also provides enhancements to the HELP facility that allow installations to customize help processing. See HELP Data Set Usage on page 5-5 for more information.
3-10
Chapter 4. Programming
REXX Programming Language . . . . . . . . . . . . . . . . . . Features of REXX . . . . . . . . . . . . . . . . . . . . . . . . Instructions, Syntax and Format . . . . . . . . . . . . . . Parsing Capabilities . . . . . . . . . . . . . . . . . . . . . Built-in Functions . . . . . . . . . . . . . . . . . . . . . . . Support for Issuing Host Commands in an Exec . . . . Testing and Executing REXX Execs . . . . . . . . . . . . Tracing Facilities and the Interactive Debug Facility . . . Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . Using APPC/MVS Services in a REXX Exec . . . . . . . . Additional TSO/E REXX Support . . . . . . . . . . . . . . . TSO/E Functions and REXX Commands . . . . . . . . . TSO/E REXX Programming Services . . . . . . . . . . . REXX Customizing Services . . . . . . . . . . . . . . . . The Data Stack . . . . . . . . . . . . . . . . . . . . . . . . . Storing REXX Execs . . . . . . . . . . . . . . . . . . . . . . Using the SYSPROC and SYSEXEC Files . . . . . . . . CLIST Programming Language . . . . . . . . . . . . . . . . . . ALTLIB Command . . . . . . . . . . . . . . . . . . . . . . . . . TSOLIB Command . . . . . . . . . . . . . . . . . . . . . . . . . Server-Requester Programming Interface . . . . . . . . . . . . Writing Servers on TSO/E . . . . . . . . . . . . . . . . . . . Writing Initialization/Termination Programs . . . . . . . . Support for Writing Command Processors . . . . . . . . . . . Support for Using TSO/E Services in Non-TSO/E Environment Programming Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TEST and TESTAUTH Commands Command Package . . . . . . . . . . . . . . . . . . . . . . . . Running Terminal Sessions as Batch Jobs . . . . . . . . . Using the SUBMIT Command . . . . . . . . . . . . . . . Automatic Saving of Data . . . . . . . . . . . . . . . . . . . Accounting Facilities Enhancements . . . . . . . . . . . . . Defaults for the User Attribute Data Set . . . . . . . . . . . ATTRIB and FREE Subcommands . . . . . . . . . . . . . . ALL Keyword for the FREE Command and Subcommand Eight-Character Station ID . . . . . . . . . . . . . . . . . . . APPC/MVS Administration Dialog . . . . . . . . . . . . . . . . TSO/E Support for a REXX Compiler . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2 4-2 . 4-2 . 4-2 . 4-3 . 4-3 . 4-3 . 4-3 . 4-3 . 4-4 . 4-4 . 4-4 . 4-5 . 4-6 . 4-6 . 4-7 . 4-7 . 4-8 . 4-8 . 4-9 . 4-9 4-10 4-10 4-10 4-11 4-11 4-13 4-13 4-13 4-14 4-14 4-14 4-14 4-15 4-15 4-15 4-15 4-15
Programming involves designing, coding, compiling, executing, and testing programs that put the computing system to work for your own purposes. The following topics describe the programming tools that TSO/E provides for the application or system programmer.
4-1
Features of REXX
The REXX language has several attractive features that make it a powerful programming tool. These include: Easy-to-use instructions and flexible syntax and format Extensive string manipulation capabilities Broad set of built-in functions Support for issuing host commands Easy testing and execution of REXX execs Tracing facilities and the interactive debug facility Compatibility with other languages and systems
Parsing Capabilities
REXX includes extensive parsing capabilities for string manipulation. This feature of REXX allows you to set up a pattern to separate words, groups of characters, or to edit any type of string.
4-2
Built-in Functions
REXX provides a broad set of built-in functions that perform string manipulation, conversion, and information retrieval operations. A complementary set of functions support the Double-Byte-Character Set (DBCS), which supports languages (such as Japanese Kanji) that have more than 256 characters, the maximum number that can be represented with one byte of data.
Compatibility
REXX execs perform functions similar to CLISTs, and can call and be called by existing CLISTs and other TSO/E programs. Therefore, REXX is an attractive alternative to the CLIST language. TSO/E REXX is the implementation of the Systems Application Architecture* (SAA*) Procedures Language on TSO/E. By using the instructions and functions defined for the SAA Procedures Language, you can write REXX execs that will run in any of the supported SAA environments, such as VM/SP (CMS). SAA Common
Chapter 4. Programming
4-3
Programming Interface Procedures Language Reference describes the instructions and functions the SAA Procedures Language offers.
4-4
system-unique data sets, for example. Both functions are available to REXX execs that run in any MVS address space. TSO/E also provides support for user-written external functions and subroutines. The REXX commands allow you to: Control or execute I/O processing to and from allocated data sets Change characteristics that control how a REXX exec executes Check for the existence of a specific host command environment Perform data stack requests (see The Data Stack on page 4-6 for a description of the data stack).
Chapter 4. Programming
4-5
routine to obtain a larger area of storage to store the result from an external function or subroutine. IRXSAY - SAY Instruction You can use the IRXSAY routine to write to the output stream. The output stream is typically directed toward the user for display at the workstation, but you can alter the output destination based on the implementation. This routine performs the same functions as the SAY keyword instruction. For additional information about the functions of the SAY instruction, see TSO/E REXX Reference, SC28-1975. IRXHLT - HALT Condition The IRXHLT routine allows application programs to query or reset the HALT condition. This routine provides an interface between programs that require direct access to information on the HALT condition and TSO/E, which maintains the information. For additional information about the HALT condition, see TSO/E REXX Reference, SC28-1975. IRXTXT - Text Retrieval The IRXTXT routine allows application programs to present the date in the same format presented by the REXX interpreter. The day is displayed in the format specified by the Weekday option of the DATE function. The month is presented in the format of either the Month option or the Normal option of the DATE function. See TSO/E REXX Reference, SC28-1975, for a description of the DATE function and the format of its options. The IRXTXT routine also allows you to retrieve syntax error messages provided by TSO/E REXX. You retrieve the error message by specifying the error message number. See TSO/E REXX Reference, SC28-1975, for error messages and message codes. IRXLIN - REXX Line size You can use the IRXLIN routine to determine the current terminal line width. This width represents the point at which the language processor breaks lines that are displayed using the SAY instruction or the IRXSAY routine. This routine performs the same function as the REXX LINESIZE function. See TSO/E REXX Reference, SC28-1975, for more information about the LINESIZE function.
4-6
Chapter 4. Programming
4-7
ALTLIB Command
exec can still be compressed. For details on REXX compression, refer to TSO/E Programming Guide, SC28-1970, and TSO/E REXX Reference, SC28-1975.
ALTLIB Command
When you implicitly invoke a CLIST or REXX exec, the EXEC command processor, by default, searches system-level libraries allocated to a system file (SYSPROC or SYSEXEC). You can use the ALTLIB command to specify alternative CLIST or REXX exec libraries for implicit execution. This command performs the same function for CLISTs and REXX execs as the LIBDEF command in ISPF performs for panels, messages, tables, skeletons, and load libraries. With ALTLIB, a user or ISPF application can easily activate and deactivate CLIST and REXX exec libraries as the need arises. This flexibility provides a potential performance benefit by reducing the time it takes to search for these libraries. The ALTLIB command lets you specify alternative libraries on the user, application, and system-level. The user-level includes libraries previously allocated to the SYSUEXEC or SYSUPROC file. The application-level includes libraries specified on the ALTLIB command using the data set or file name. The system-level includes libraries previously allocated to the SYSEXEC or SYSPROC file. During implicit execution, the EXEC command processor searches the libraries in the following order: user-level, application-level, and system-level. At the application and system-levels, the ALTLIB command uses the virtual lookaside facility (VLF) to provide potential increases in library search speed.
4-8
Using various operands on the ALTLIB command, a user or ISPF application can: Define alternative application-level libraries of CLISTs or REXX execs. Activate the search for execs in a library or libraries at the specified level(s), in the order specified. Exclude one or more library levels (user, application, system) from being searched. Reset the search order to the system level only. Obtain a display of the current search order. For more information about using the ALTLIB command, see TSO/E Command Reference, SC28-1969.
TSOLIB Command
The TSOLIB command provides system and application programmers with a means of linking to different versions of load module libraries while remaining in their active TSO/E session. TSO/E searches these libraries before those specified in the user's logon procedures and those searched by default. This provides for reduced access time to the modules the programmer may be working on and allows a flexible way to change a user's environment. With the TSOLIB command, a previous habit of having different user IDs or different logon procedures available for these users is no longer required. Using various operands of the TSOLIB command users can: Activate and deactivate load module libraries of their choice. Stack activation requests. Thus, the latest activation of libraries replaces a previous activation until the latest one is deactivated again. This provides for effective setups if, for example, a programmer works on several different versions of a product. Reset the search order for load module libraries to its original state. Display the current search order and any stacked activations. For more information about using the TSOLIB command, see TSO/E Command Reference, SC28-1969.
Chapter 4. Programming
4-9
4-10
Programming Services
write a command processor, what TSO/E services to use, and how to test and install the command processor, see TSO/E Programming Guide, SC28-1970.
Programming Services
TSO/E provides many services that you can use in system or application programs to perform various tasks. These services consist of programs, macros, and CLISTs. TSO/E services support a wide range of functions that are useful in writing system programs as well as application programs that exploit the full-screen capabilities of TSO/E. The following table describes the tasks you can perform and the service(s) that support the task. For complete information about how to use these services, see TSO/E Programming Services, SC28-1971.
Task Check the syntax of subcommand names Check the syntax of command and subcommand operands Service Command scan service routine Parse service routine
Chapter 4. Programming
4-11
Programming Services
Task Control terminal functions and attributes, such as full-screen mode and terminal line size Process terminal I/O and issue messages
BSAM and QSAM macro instructions TSO/E I/O service routines TGET/TPUT/TPG TSO/E message handling routine
Retrieve system messages that are issued during a console session Cause the system to recognize and schedule an attention exit that receives control when an attention interruption occurs Process a CLIST's attention routine when an attention interruption occurs Obtain a list of data set names that match specified criteria Ensure that a specified data set has adequate free space for additional data Create or delete alternative library environments and modify alternative library definitions for CLIST and REXX libraries Allocate, free, concatenate, and deconcatenate data sets during program execution Retrieve information from the system catalog, such as data set name, index name, control volume address or volume ID Construct a fully-qualified data set name when a partially-qualified name is entered by a terminal user Analyze return codes from dynamic allocation or DAIR and issue appropriate error messages Analyze VSAM macro instruction failures, subsystem request failures, parse service routine or PUTLINE failures, and ABEND codes, and issue an appropriate error message Determine if a command or program is authorized; determine if a command is not supported in the background Invoke commands, CLISTs, REXX execs and other programs Note: Unauthorized programs can use the TSO/E service facility to invoke APF-authorized functions.
CLIST attention facility ICQGCL00 Space management CLIST Alternative library interface routine
DAIRFAIL routine
GNRLFAIL/VSAMFAIL routine
4-12
Command Package
Task Establish a TSO/E environment outside of the TSO/E TMP Create, update, and return the values of CLIST and REXX variables Retrieve information from the Information Center Facility's names directory, such as phone numbers, user IDs, and addresses for specified names Display lists of printers for users to select and to print data sets on selected printers Invoke Information Center Facility applications
Command Package
The TSO/E Command Package is integrated into TSO/E. It includes: Support for running terminal sessions as batch jobs Automatic saving of data Accounting facilities enhancements Defaults for the user attribute data set ATTRIB and FREE subcommands ALL keyword for the FREE command and subcommand Eight-character station ID.
Chapter 4. Programming
4-13
Command Package
For your job, you need these job control language (JCL) statements: A JOB statement to identify your job An EXEC statement with the name of the TSO/E terminal monitor program (IKJEFT01, IKJEFT1A, or IKJEFT1B) Special DD statements to indicate that your input data contains executable TSO/E commands, and to indicate what you want done with your output. You also need commands (such as LOGON and EDIT) that you would have entered at the terminal to run your job. You need the commands in the sequence you would have entered them. If you create a data set and use the SUBMIT command, TSO/E provides a JOB statement for you. You need to provide only the commands you want executed.
4-14
A SYSOUT class default for job output where no SYSOUT class is specified on the ALLOCATE command.
Eight-Character Station ID
You can use an eight-character station ID with the DEST keyword of the ALLOCATE, FREE, and OUTPUT commands.
Chapter 4. Programming
4-15
Compiler Interface Variable Handling Routine If you install this routine, it accesses variables of a compiled exec. The compiler interface variable handling routine receives control whenever an external routine or host command requests access to REXX variables using IKJCT441 or IRXEXCOM. Compiler Interface Load Routine If you install this routine, it loads a compiled REXX exec from storage or frees the in-storage control block. The compiler interface load routine receives control when TSO/E REXX loads a compiled exec into storage and when TSO/E REXX needs to free the in-storage control block of the compiled REXX exec.
4-16
Chapter 5. Customization
TSO/E Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 VTAM and TCAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Logon Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 The Logon/Logoff Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Using Security Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 ISPF/PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Authorized Commands and Programs and Commands Not Supported in the Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 TRANSMIT and RECEIVE Availability . . . . . . . . . . . . . . . . . . . . . . 5-5 HELP Data Set Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Host Services Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 Language Enablement Support . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Command/Program Invocation Platform Support . . . . . . . . . . . . . . . . 5-7 TSO/E Resource Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 The UADS and RACF Data Base . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 TSO/E Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 ALLOCATE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 CANCEL, OUTPUT, STATUS, and SUBMIT Commands . . . . . . . . . . . 5-9 CONSOLE and CONSPROF Commands . . . . . . . . . . . . . . . . . . . 5-10 RACF Resource Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 EDIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 LISTBC, OPERATOR SEND, and SEND Commands . . . . . . . . . . . . 5-11 PRINTDS Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 TEST and TESTAUTH Commands . . . . . . . . . . . . . . . . . . . . . . . 5-12 TRANSMIT and RECEIVE Commands . . . . . . . . . . . . . . . . . . . . . 5-13 SYS1.PARMLIB Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13 PARMLIB Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 CLIST Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 REXX Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Language Processor Environment Characteristics . . . . . . . . . . . . . . 5-14 Replaceable Service Routines . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 REXX Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Session Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Information Center Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Adding, Modifying, or Deleting a Product or Service . . . . . . . . . . . . . 5-16 Adding a Product or Service . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 Modifying or Deleting a Product or Service . . . . . . . . . . . . . . . . . 5-17 Creating or Tailoring Application Definitions . . . . . . . . . . . . . . . . . . 5-17 Adding Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 Modifying Start-Up and Termination Processing . . . . . . . . . . . . . . . 5-18 Writing Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Enhanced Connectivity Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 User-Written Access Method Driver Interface . . . . . . . . . . . . . . . . . 5-18 TSO/E Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19 Customization is the process of tailoring TSO/E functions to fit the needs of your installation and making other IBM products available to TSO/E users. The following topics discuss a number of facilities to enable customization. For complete information see TSO/E Customization, SC28-1965.
5-1
TSO/E Environment
TSO/E Environment
Customization of the TSO/E environment generally refers to customization that makes a TSO/E facility available or customization that changes default values that affect TSO/E. Customizing the TSO/E environment includes customizing: VTAM* and TCAM Logon limits The logon/logoff process ISPF/PDF Authorized commands and programs and commands not supported in the background TRANSMIT and RECEIVE availability HELP data set usage Host services availability Language enablement support Command/program invocation platform support. You can also customize the TSO/E environment by providing TSO/E resource protection.
1 2
Virtual Telecommunications Access Method Telecommunications Access Method OS/390 V2R4.0 TSO/E General Information
5-2
TSO/E Environment
Logon Limits
TSO/E provides ways for you to limit and manage the maximum number of concurrent logons, limit the user's region size, and limit user access to applications. You can change the maximum number of users that can be logged on to TSO/E concurrently by adjusting the factors that determine the maximum number. If necessary, you can also write a logon pre-prompt exit routine to allow or disallow a user to log on depending on the user group to which the individual is assigned. You can define a region size default that applies to all users, that varies from one logon procedure to another, or that varies from one user to another. You can also use the logon pre-prompt exit to monitor and adjust the region size requested by a user. You can limit the applications to which a user has access by providing several logon procedures, each providing access to different applications, and by restricting users to only certain logon procedures.
5-3
TSO/E Environment
TSO/E provides a post-prompt exit that allows you to further customize the logon process. After the prompting for logon input is complete, you can use this exit to add, examine, and modify JCL statements associated with logon. TSO/E allows you to customize logon panels and logon help text panels using logon panel modules. If a language feature is installed, a logon panel for that language is available. There is one logon panel module for each language. You can also use the pre-display and post-display exits to customize the logon process. These exits allow you to supply default information, update information, validate user-supplied information, and re-prompt the user for information, if needed. Using these exits you can perform, but are not limited to, the following functions: The pre-display exit allows you to (1) update information contained on the logon panel, and (2) process any installation-defined fields on the logon panel. The post-display exit allows you to (1) process and validate fields on the logon panel, and (2) request display of help screens. TSO/E also provides an authorized logoff exit. You can use the logoff exit to perform clean-up operations, gather accounting information, control information written to the UADS and RACF data base, and issue the LOGOFF or LOGON command to control re-logons.
ISPF/PDF
The Interactive System Productivity Facility/Program Development Facility (ISPF/PDF) helps users develop different types of applications, including dialogs. It uses display terminals in an interactive environment to assist with many programming tasks. You can enable TSO/E users to use ISPF/PDF, by defining ISPF/PDF to TSO/E. You do this by modifying the users' logon procedures to allocate the ISPF/PDF data sets. In addition, you can modify the ISPF default list of TSO/E commands that a user can issue from ISPF/PDF panels and you can allow users to use the Session Manager from ISPF/PDF.
5-4
TSO/E Environment
Authorized Commands and Programs and Commands Not Supported in the Background
TSO/E users cannot use authorized commands or programs until you make them available by defining them in certain SYS1.PARMLIB members or CSECTs. TSO/E requires you to specify certain authorized commands and programs that users are able to use and certain commands that are not supported in the background. You can optionally add authorized commands and programs, such as VLFNOTE, LISTDS, and IEHMOVE, to the list to make them available to users at your installation. You can also add commands that you do not want users to execute in background jobs, such as user-written commands that do not work properly in the background. You can use the PARMLIB command to dynamically make the commands or programs in SYS1.PARMLIB member IKJTSOxx available or restricted, without having to re-IPL the system. You can also use the PARMLIB command to view the current list of authorized commands and programs, and commands not supported in the background. For more information about using SYS1.PARMLIB and the PARMLIB command, see SYS1.PARMLIB Data Set on page 5-13. TSO/E provides a table look-up service that also helps simplify installation. This service allows you to determine whether a given program or command is defined as authorized and whether a given command is not available for use in the background.
Chapter 5. Customization
5-5
TSO/E Environment
A program called an access method driver defines the protocol for managing server/requester communications. You can change this protocol by providing your own access method drivers. If your installation has VM/PC users, you can perform additional customization that allows them to use MVSSERV. You can also change the default space parameters that VM/PC servers use to allocate MVS data sets.
5-6
TSO/E Environment
Chapter 5. Customization
5-7
TSO/E Commands
With RACF active, you can use security labels (SECLABELs) and your security administrator can activate security label checking. In this case, resources and users have security labels associated with them. Users can access only those resources that they have been authorized to use through RACF. Security label checking affects the processing of several TSO/E commands, such as SEND, LISTBC, TRANSMIT, and RECEIVE. For information about the processing of these commands with security labels, see TSO/E Customization, SC28-1965. For information about setting up security labels, see OS/390 Security Server (RACF) Security Administrator's Guide, SC28-1915.
TSO/E Commands
TSO/E enables you to customize the use of many commands to suit your installation's data processing requirements. One way to customize a command is to write an exit routine. TSO/E provides exits for the following commands: ALLOCATE ALTLIB CANCEL CONSOLE CONSPROF EDIT - the COPY, MOVE, and RENUM subcommands EXEC FREE LISTBC LOGON and LOGOFF OPERATOR - the SEND subcommand OUTDES OUTPUT PARMLIB PRINTDS RECEIVE
5-8
TSO/E Commands
SEND STATUS SUBMIT TEST TESTAUTH TRANSMIT TSOLIB. Using the exits, you can customize commands in various ways. At a minimum, you can use the exits to restrict users from using a command or to change the operands a user specifies. In addition to exits, TSO/E provides other ways for you to customize certain commands. The following sections describe additional ways you can customize specific commands.
ALLOCATE Command
The TSO/E ALLOCATE command lets users dynamically allocate and manage data sets and OpenMVS files. In addition to writing exit routines for the ALLOCATE command, you can: Use the MVS allocation input validation routine to monitor and, if necessary, change information that a user provides on the ALLOCATE command. Use Storage Management Subsystem (SMS) to manage your system's data set and storage and to simplify how users allocate data sets. Use output descriptors to eliminate the need for users to specify output-related operands on the ALLOCATE command. You can define the output descriptors using OUTPUT JCL statements in the user's logon procedure. JES installations can also define and reuse dynamic output descriptors using the TSO/E OUTDES command. Change the default parameter values used by the Information Center Facility space management service to manage data set space. You can use member IKJTSOxx of SYS1.PARMLIB to set a default value (SHR or OLD) for the data set disposition specified on the ALLOCATE command. If a user issues the ALLOCATE command without specifying a data set disposition, the disposition defaults to the setting in IKJTSOxx. You can make the default data set disposition in IKJTSOxx take effect immediately using the PARMLIB command with the UPDATE operand. You can also list the current ALLOCATE default using the PARMLIB command with the LIST operand. For more information about using SYS1.PARMLIB and the PARMLIB command see SYS1.PARMLIB Data Set on page 5-13.
Chapter 5. Customization
5-9
TSO/E Commands
In addition to writing TSO/E exit routines for the CANCEL, OUTPUT, STATUS and SUBMIT commands, you can: Use JES initialization statements to change the default processing performed for jobs submitted by TSO/E users Use JES exits and SMF exits to perform similar processing as the TSO/E SUBMIT exit and the TSO/E OUTPUT, STATUS, CANCEL exit Use RACF resource classes to customize the way TSO/E users submit jobs and process the output.
5-10
TSO/E Commands
EDIT Command
The TSO/E EDIT command with its subcommands allow users to create, modify, store, submit, retrieve, and delete data sets with sequential or partitioned data set organization. To suit the needs of your installation, you can customize the EDIT command by writing exit routines and using the facilities described below: TSO/E has defined a number of data set types. If these types do not meet your installation's needs, you can either change the attributes of the TSO/E defined data set types or you can define your own data set types. For each installation-defined data set type, you can write a syntax checker and a syntax checker exit. The syntax checker can detect errors when a user edits a data set of the type recognized by the syntax checker. You can use the exit to obtain information that the user specifies on the EDIT command. If the functions provided by the EDIT command do not meet your installation's needs, you can supplement those functions by writing your own subcommand processors and adding them to the system. The MOVE and COPY subcommands of EDIT require the allocation of data sets for work space. You have the option to either preallocate utility work data sets, or to allow EDIT to allocate them dynamically as space is needed.
Chapter 5. Customization
5-11
TSO/E Commands
Specify whether the SEND command stores messages in the broadcast data set, if your installation is using user logs, and the target user does not have a user log Specify whether the individual user logs are security protected from the user. You can use the PARMLIB command to list the current SEND command processor defaults in SYS1.PARMLIB and dynamically update them (with the contents of IKJTSOxx) without having to re-IPL the system. For more information about using SYS1.PARMLIB and the PARMLIB command, see SYS1.PARMLIB Data Set on page 5-13. With TSO/E, and RACF installed, your installation can use the RACF security resource message class SMESSAGE to control which users can send messages to other users. For example, a user may send messages to another user only if permitted to the receiving user's resource within the SMESSAGE class. If a user does not have a resource defined in the SMESSAGE class, any user can send a message to that user. For information about setting up the SMESSAGE resource class, see OS/390 Security Server (RACF) Security Administrator's Guide, SC28-1915. When you use the PARMLIB command to update system defaults, the SEND statement's SYSPLEXSHR setting is updated on all systems in the sysplex. Sysplex communication facilities are used to notify the other systems of the change. As a result, a new message appears when the PARMLIB command lists the default settings. If your installation shares the SYS1.BRODCAST data set, you should ensure that you set the SYSPLEXSHR keyword correctly. For more information on setting the SYSPLEXSHR keyword, see TSO/E Customization, SC28-1965.
PRINTDS Command
The PRINTDS command allows users to print data sets. TSO/E provides two exits that enable you to control the use of the PRINTDS command. In addition, you can use output descriptors to simplify the use of the PRINTDS command. Output descriptors eliminate the need for users to specify output-related operands on the PRINTDS command. You can define the output descriptors using OUTPUT JCL statements in the user's logon procedure. JES2 installations can also define and reuse dynamic output descriptors using the TSO/E OUTDES command.
5-12
You can use the PARMLIB command to list the current system defaults for the installation-written TEST subcommands and the TSO/E commands that run under TEST. You can also use the PARMLIB command to dynamically update these defaults (with the contents of IKJTSOxx) without having to re-IPL the system. For more information about using SYS1.PARMLIB and the PARMLIB command, see SYS1.PARMLIB Data Set.
Chapter 5. Customization
5-13
REXX Processing
PARMLIB Command
You can use the PARMLIB command to dynamically update TSO/E system defaults (with the contents of IKJTSOxx) without having to re-IPL the system. You can also use the PARMLIB command to list current TSO/E system defaults. You can use the PARMLIB command to check the syntax of any IKJTSOxx member of SYS1.PARMLIB. For complete information about using the PARMLIB command, see TSO/E System Programming Command Reference, SC28-1972. For information about creating and initializing IKJTSOxx members of SYS1.PARMLIB, see TSO/E Customization, SC28-1965.
CLIST Processing
TSO/E provides two exits you can use to customize CLIST processing. These exits enable you to define and process your own built-in functions and CLIST statements, and do your own processing of TSO/E commands.
REXX Processing
TSO/E provides several services that let you customize REXX processing by tailoring the environment within which a REXX exec is interpreted. Many of these services let you change how an exec is processed and how the language processor interfaces with the system to access and use system services, such as I/O. Customization services include the following: Language processor environment characteristics Replaceable service routines REXX exits. For complete information about changing environment characteristics and using replaceable routines, see TSO/E REXX Reference, SC28-1975. For information about using the REXX exits, see TSO/E Customization, SC28-1965.
5-14
You can provide your own routines in non-TSO/E address spaces and in language processor environments that are not integrated into TSO/E.
REXX Exits
TSO/E provides several exits that you can use to customize REXX processing on a language processor environment basis. These exits enable you to perform various functions such as: Prevent the initialization of a language processor environment, change parameters used to initialize a language processor environment, or perform special pre-environment processing. Perform special attention processing in the TSO/E address space.
Session Manager
The Session Manager is an interface to TSO/E. It saves the commands entered by a user and the responses to the commands. It also allows the user to redisplay and change the commands or print them. You can customize the use of Session Manager by either modifying the environment definition provided by IBM or supplying your own environment definition(s). The environment definition defines the user's screen layout, program function key definitions, and stream defaults. You can provide multiple definitions so different users can use different definitions. Multiple definitions allow you to customize the environment definition to individual user needs. Three exits allow you to further customize Session Manager. The Session Manager exits enable you to monitor a user's interaction with the system while they are using Session Manager. You can use these exits to specifically: Monitor and intercept certain commands. Retain a log of a user's TSO/E session. Determine how long it takes a command to execute. Determine at what time certain operations were performed. Provide multiple default environments.
Chapter 5. Customization
5-15
5-16
Adding Commands
To extend the function of the Information Center Facility, you can add your own commands to the command table, ICQCMDS. For example, you can add commands to enter dialogs, act as aliases of other commands, or to execute CLISTs. To use a command in the command table, a user simply types that command after the COMMAND or OPTION arrow on any panel in the Information Center Facility and presses the Enter key. As shipped, the command table contains three commands. These commands allow you to quickly access, from any Information Center Facility panel, the user's or administrator's main menu panel, or a specific option (for example, the ENROLL option): The IC command displays the user's primary panel. The ADMIN command displays the administrator's primary panel. The GO commands goes to the option specified.
Chapter 5. Customization
5-17
Writing Exits
TSO/E provides several exits that you can use to customize the use of the Information Center Facility. These exits allow you to: Keep track of changes that users or administrators make in private and master names directories. Customize functions and panels that are invoked by the Application Manager If your installation has installed A Departmental Reporting System (ADRS) for use in the Information Center Facility, you can also write an exit routine for ADRS to perform various functions.
5-18
TSO/E Exits
TSO/E Exits
TSO/E provides exit points for many TSO/E functions and commands. At an exit point, the function or command invokes an exit routine if one exists. You can write an exit routine to perform special processing and customize how the function or command works. When your exit is finished processing, control returns to the command or function. Exits allow you to change default values or extend a TSO/E function or command. The following table lists each function and command that you can write an exit for, the exit(s) provided in TSO/E for the function or command, and the possible uses for each exit. If the name of an exit must follow a naming convention, the table also shows what the name must be. For complete information about each exit, see the associated processing function in TSO/E Customization, SC28-1965.
Figure 5-1 (Page 1 of 7). Overview of Exit Points that TSO/E Provides
Processing ALLOCATE command Exit Initialization IKJEFD47 Termination IKJEFD49 ALTLIB command Initialization IKJADINI Termination IKJADTER Application Manager Function pre-initialization ICQAMFX1 Function post-termination ICQAMFX2 Panel pre-display ICQAMPX1 Panel post-display ICQAMPX2 CANCEL See the entry for the OUTPUT command in this table. Built-in functions IKJCT44B Statements IKJCT44S Add installation-written built-in functions. Add installation-written CLIST statements. Uses of Exit Check and change the command users issue or provide pseudo-operands. Perform clean-up processing. Specify an alternative return code. Change the command the user issues. Perform clean-up processing. Check a user's authorization to use an application, allocate data sets for an application, and prepare to gather accounting data. Free data sets the function pre-initialization exit allocated and summarize accounting data. Set default values for the panel to be displayed. Validate the information the user entered on the panel.
CLIST processing
Chapter 5. Customization
5-19
TSO/E Exits
Figure 5-1 (Page 2 of 7). Overview of Exit Points that TSO/E Provides
Processing CONSOLE command Exit Pre-parse IKJCNXPP Activation IKJCNXAC 80% Message capacity IKJCNX50 100% Message capacity IKJCNX64 Deactivation IKJCNXDE CONSPROF command Initialization IKJCNXCI Pre-display IKJCNXCD Termination IKJCNXCT EDIT command RENUM, MOVE, and COPY subcommands Syntax checkers Uses of Exit Check and, if necessary, change the command the user issues. Establish communication area, end an activation request, change settings specified by the user, and grant or deny CONSOLE command authority to a user. 80% full. Take action when the solicited or unsolicited message table becomes 100% full. Perform clean-up processing. Check and, if necessary, change the command the user issues, update the profile with an installation portion, and grant or deny CONSOLE command authority to a user. Add information to the console profile display message IKJ55351I, or issue an installation-defined message instead of IKJ55351I. Perform clean-up processing, and store the installation portion of the console profile in a permanent place. Customize how the subcommands handle line numbering whenever a user issues the subcommands. Write an exit for syntax checkers that your installation provides. The exit fills in the option word with information the user specifies on the EDIT command. Change the command the user issues. Perform clean-up processing and set the defaults for the control characteristics of the CLISTs or REXX execs. Check and change the command users issue or provide pseudo-operands. Perform clean-up processing. Add processing, such as displaying panels or allocating data sets, whenever a user selects the ADRS option from the Information Center Facility. Keep track of changes that are made to the private and master directories whenever Information Center Facility users use the names service.
EXEC command
FREE command
ADRS
Names service
5-20
TSO/E Exits
Figure 5-1 (Page 3 of 7). Overview of Exit Points that TSO/E Provides
Processing LISTBC command Exit Initialization IKJEESX5 Pre-display IKJEESX6 Pre-list IKJEESX7 Pre-read IKJEESX8 Pre-allocate IKJEESX9 Failure IKJEESXA Termination IKJEESXB Logon and logoff processing Logon pre-prompt IKJEFLD Uses of Exit Initialize the environment for later exits, restrict users from using the command, or change the operands a user specifies on the command. If using individual user logs, provide special formatting, append diagnostic information to a message, and support special features of output devices. If using individual user logs, modify user log data set names and prepare for the pre-read exit. If using individual user logs, tailor I/O. If using individual user logs, allocate the user log data set. If using individual user logs, perform failure processing and clean-up after an I/O failure. Perform clean-up or special termination processing. Tailor the TSO/E logon process. Verify, change, or supply logon parameters and system characteristics, cancel logon requests, provide your own JCL statements, or display your own full-screen logon panel. Perform the functions of IKJEFLD, plus the following authorized functions: specify the first TSO/E command, return job and SYSOUT classes, bypass RACF, return the relative block address (RBA), pass data to the logoff exit, specify security label of current logon session, specify languages to be used for displaying translated information, and set up a console profile. Update information on the logon panel, process installation-defined fields on the logon panel. Validate and process fields on the logon panel, re-prompt the user for information, and also request display of help screens. Examine, modify, and add JCL statements associated with the logon process. Tailor the TSO/E logoff process. Gather accounting information, control UADS and RACF data base updates, control re-logons.
Logon pre-display IKJEFLN1 Logon post-display IKJEFLN2 Logon post-prompt IKJEFLD3 Logoff IKJEFLD2 OPERATOR SEND subcommand OUTDES command See the entry for the SEND command in this table. Initialization IKJEFY11 Termination IKJEFY12 OUTPUT, STATUS, and CANCEL commands IKJEFF53
Check and change the command users issue or provide pseudo-operands. Perform clean-up processing. Tailor the way users can handle the processing of batch jobs and their output.
Chapter 5. Customization
5-21
TSO/E Exits
Figure 5-1 (Page 4 of 7). Overview of Exit Points that TSO/E Provides
Processing PARMLIB command Exit Initialization IKJPRMX1 Termination IKJPRMX2 PRINTDS command Initialization IKJEFY60 Termination IKJEFY64 RECEIVE See the entry for the TRANSMIT command in this table. Pre-environment initialization IRXINITX Post-environment initialization IRXIITS or IRXITMV Environment termination IRXTERMX Exec processing Exec initialization Exec termination Attention handling SEND command OPERATOR SEND subcommand Initialization IKJEESX0 IEEVSNX0 Perform processing after the initialization routine receives control but before the new language processor environment is initialized. Perform processing after the language processor environment is initialized but before the initialization routine returns control. Perform processing before a language processor environment is terminated. Perform special processing before a REXX exec is executed. Access and update REXX variables. Access and update REXX variables. Perform special attention processing in an environment integrated into TSO/E. Initialize the environment for later exits, change the defaults in SYS1.PARMLIB, restrict users from using the command, provide different user log data set names, and reroute messages by changing the user ID of the target user. If using individual user logs, provide special formatting, add diagnostic information, and support special features of output devices. If using individual user logs, override the user log data set name, support special I/O, and perform open and write operations. If used with the LISTBC pre-read exit, process the message or add information to it such as a sequence number, compress the message, and change parameters. If using individual user logs, perform failure processing and clean-up after an I/O failure. Perform clean-up or special termination processing. Uses of Exit Change the command the user issues. Perform clean-up processing. Tailor the fixed default values for specific operands. Restrict users from using the command or change the operands a user specifies on the command. Perform clean-up processing.
REXX processing
5-22
TSO/E Exits
Figure 5-1 (Page 5 of 7). Overview of Exit Points that TSO/E Provides
Processing Session Manager Exit Initialization Uses of Exit Indicate which streams you want to monitor and whether the Session Manager should log line mode output while users are executing full-screen programs. Monitor the individual streams you specified in the initialization exit and perform required processing. Perform special processing before the Session Manager ends.
Stream monitoring Termination STATUS See the entry for the OUTPUT command in this table. IKJEFF10 Initialization IKJEGMIE Termination IKJEGMTE Subcommand Initialization IKJEGCIE Subcommand Termination IKJEGCTE TESTAUTH command Initialization IKJEGAUI Termination IKJEGAUT Subcommand Initialization IKJEGASI Subcommand Termination IKJEGAST
Check submitted JCL statements and accept, reject, or modify them. Change the command the user issues. Perform clean-up processing. Change the subcommand the user issues.
Perform security verification. Perform clean-up processing. Change the subcommand the user issues.
Chapter 5. Customization
5-23
TSO/E Exits
Figure 5-1 (Page 6 of 7). Overview of Exit Points that TSO/E Provides
Processing TRANSMIT and RECEIVE commands Exit Common exit: NAMES data set pre-allocation INMCZ21R TRANSMIT exits: Startup INMXZ01 INMXZ01R Log data set pre-allocation INMXZ21R Encryption INMXZ03 INMXZ03R Termination INMXZ02 INMXZ02R RECEIVE exits: Initialization INMRZ01 INMRZ01R Log data set pre-allocation INMRZ21R Data set pre-processing INMRZ11 INMRZ11R Data set decryption INMRZ13 INMRZ13R Notification INMRZ04 INMRZ04R Acknowledgement notification INMRZ05R Pre-acknowledgement notification INMRZ06R Data set post-processing INMRZ12 INMRZ12R Post-prompt INMRZ15R Termination INMRZ02 INMRZ02R TSOLIB command Initialization IDYTSINI Termination IDYTSTER Change the command the user issues. Perform clean-up processing. Uses of Exit Use the various TRANSMIT and RECEIVE exits together to perform different types of processing. Use the exits to monitor transmission activity or customize how TRANSMIT and RECEIVE operate. For example, you can use the exits to: Collect statistics about network usage Control which users can use a particular network path Support data sets that the Interactive Data Transmission Facility does not support Tailor encryption and decryption processing Suppress reception of data sets Determine what action to take with an arriving transmission after a user response Send an acknowledgment message back, using the receiver's security token.
5-24
TSO/E Exits
Figure 5-1 (Page 7 of 7). Overview of Exit Points that TSO/E Provides
Processing VM/PC servers Exit CHSFEXIT Uses of Exit Change the default space parameters that VM/PC servers use to dynamically allocate MVS data sets.
Chapter 5. Customization
5-25
TSO/E Exits
5-26
Administering TSO/E
Chapter 6. Administration
Administering TSO/E . . . . . . . . . . . . . . . . . . ENROLL Option of the Information Center Facility RACF Commands . . . . . . . . . . . . . . . . . . TSO/E ACCOUNT Command . . . . . . . . . . . Converting to the RACF Data Base . . . . . . . . Administering the TSO/E Information Center Facility NEWS Maintain System News . . . . . . . . . NAMES Maintain the Name/Phone Directory The TRANSMIT/RECEIVE Names File . . . . ENROLL Enroll Users in the ICF . . . . . . . USERTYPE Set Defaults for User Types . . . SYSDEF Set System Defaults . . . . . . . . . ISPF Profile . . . . . . . . . . . . . . . . . . . . Printer Support . . . . . . . . . . . . . . . . . . Applications . . . . . . . . . . . . . . . . . . . . COURSES Maintain Education Services . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-1 6-1 6-2 6-2 6-2 6-2 6-3 6-3 6-3 6-4 6-4 6-4 6-4 6-5 6-5 6-6
Administration consists of managing the data processing resources of TSO/E and TSO/E users. The following sections describe the administrator's tasks and the facilities that TSO/E provides to perform the tasks. For complete information see TSO/E Administration, SC28-1966.
Administering TSO/E
You can define users to TSO/E and maintain user type definitions using the ENROLL option of the Information Center Facility, RACF commands, or the TSO/E ACCOUNT command. You can also use RACF commands and the TSO/E ACCOUNT command to remove users from TSO/E.
6-1
Facility does not support security labels. See OS/390 Security Server (RACF) Security Administrator's Guide, SC28-1915, for information about defining security labels for users.
RACF Commands
If your installation has RACF active, you can use RACF commands to define users to both TSO/E and RACF, maintain those definitions in the RACF data base, and remove users. The RACF command: ADDUSER TSO adds a new user to TSO/E. ALTUSER TSO changes information about a previously-defined user. ALTUSER NOTSO removes a user from TSO/E. LISTUSER TSO lists information from the RACF data base about a user. Using the RACF commands to add, maintain, and delete users has the advantage that (1) you can use one set of commands to add, change, or delete information about TSO/E user IDs and RACF security, (2) you need maintain only the RACF data base for user information. For more information about RACF commands, see OS/390 Security Server (RACF) Command Language Reference, SC28-1919. For information about adding users to the RACF data base, see OS/390 Security Server (RACF) Security Administrator's Guide, SC28-1915.
6-2
TSO/E Information Center Facility Administration Option ===> Select one of the following options. 1 2 3 4 5 6 7 8 9 I T X DESCRIBE NEWS NAMES ENROLL USERTYPE SYSDEF ICFUSER COURSES PDF PROBLEM INTRO TUTORIAL EXIT To scroll, press UP or DOWN.
Read a short description of the options on this panel Maintain System News Maintain the name/phone directory Enroll users in the Information Center Facility Set defaults for user types Set system defaults Use Information Center Facility user services Maintain education services Use ISPF/PDF services Use problem reporting services Learn to use the Information Center Facility Read detailed descriptions of options on this panel Exit
To view PF key definitions, type KEYS on COMMAND or OPTION line of any panel.
In the figure above, options 1, 2, 3, 4, 5, and 7 describe the six major administrative tasks. When you select one of those options, the main menu leads to panels on which you can perform the specific task. The following sections describe the six major tasks that you would perform as an Information Center Facility administrator.
Chapter 6. Administration
6-3
ISPF Profile
The user's ISPF profile controls communication between the system and the user's terminal. The profile contains various information, such as terminal characteristics and PF key settings. During enrollment, the system copies the system default ISPF profile to initialize a profile for the person. You can then tailor the copied information to suit the person being enrolled. You can also change the system defaults when the standard defaults no longer apply to the average user being enrolled. Changing the system defaults requires you to do less customization when enrolling users. For TSO/E, the system default ISPF profile is shipped as part of the Information Center Facility. You can use the SYSDEF option to modify the system default ISPF profile. For TSO/E, the Information Center Facility uses the system default ISPF profile. You can use the SYSDEF option to modify the initial defaults supplied by ISPF/PDF. When you modify the initial defaults supplied by ISPF/PDF, a local copy of the profile is maintained by the Information Center Facility. In this case, the defaults supplied by ISPF/PDF are no longer used.
6-4
Printer Support
The printer support definition describes the printers available to your facility and their print characteristics. You can set up a print definition by entering information about print characteristics on Information Center Facility panels. You can also copy, modify, delete, and test an existing print definition.
Applications
The Information Center Facility is made up of different services that users can access. You can use the Application Manager to define services to the Information Center Facility. To be defined by Application Manager, a service must be broken down into parts called applications. There are three types of applications: environments, functions and panels. An environment defines the support for the service, such as the setup commands and the required libraries. A function is the CLIST, REXX exec, command, program, or menu panel that invokes the service. A panel is the interface that allows users to select different services, tutorials, and HELP information. With TSO/E, Application Manager supports three levels of application definitions: system, group, and private. This support allows departments, user groups, and individual users to create or tailor application definitions for their own use. Application definitions at the group or private level can be either unique definitions or copies of higher-level definitions. This support also enables installations to limit the availability of selected services to certain users. For example, the applications that define a service can be copied down from the system level to the group level for a specific group of users. The applications can then be deleted at the system level. To administer system level application definitions, you invoke Application Manager using the SYSDEF option on the administration main menu panel. To administer group or private application definitions, you invoke Application Manager using the PROGRAM option on the end user main menu panel. For information about accessing application definitions defined for a specific group, see Group Specification on page 3-4. Application Manager simplifies the task of integrating products and functions into the Information Center Facility. You can add a service by either loading installation files that define the service in terms of its applications or by entering specific information on Application Manager panels. After you add a service, you can copy its applications, modify them, view them, delete them, and determine where they are used. You can also replace an existing application with an application of the same name, language, and application type. You can use the EXPORT option to create an installation file from an existing application. The EXPORT option makes it possible to move Application Manager definitions installed on one system to other systems without having to repeat the initial installation process. You can specify alternate application libraries for CLISTs and REXX execs. The Application Manager invocation processing uses the ALTLIB command to dynamically allocate these libraries when a user invokes an application. The ALTLIB command eliminates the need for allocating user and application CLIST and REXX exec libraries to a fixed ddname in the user's logon procedure.
Chapter 6. Administration
6-5
With TSO/E, you can also: Use the HIERARCHY option to display a hierarchy of panels and functions for any defined panel application. Use the upgrade function to upgrade an existing installation file with the contents of an upgrade file. An upgrade file is in the format of an installation file and contains entries for adding, deleting, and replacing portions of an installation file. Using upgrade files to apply changes to installation files minimizes the possibility that the changes will conflict with any customization that may have been done. Specify any library required by an application. To differentiate the libraries specified, a library TYPE field is included on the Application Libraries panel. The valid library types are (1) ISPF for ISPF files, (2) CLIST for CLIST files, (3) EXEC for REXX files, (4) INPUT for any other file type with the intended use of input during invocation, (5) OUTPUT for any other file type with the intended use of output during invocation. All Application Manager menu panels have the same format. In addition, the menu panels are scrollable so that installations can fit more options on them. With TSO/E, you can process multiple installation files with or without upgrade files and export a list of applications without the use of Application Manager panels. The mass installation file process provides two separate functions. These are: Mass upgrade and install This function uses upgrade and/or installation files to upgrade or replace existing applications and install new applications. Each installed application is verified and made available. You can mass process installation files with or without corresponding upgrade files. You can also mass process upgrade files with or without corresponding installation files. Mass export This function uses a list of applications to drive an automated export process. Applications are exported to the output installation library You can invoke the mass installation file process in the batch TMP (no active terminal) or in the foreground (active terminal). Installations can use several exits to tailor the processing that occurs when users invoke applications defined by Application Manager. For a description of the exits, see TSO/E Customization, SC28-1965.
6-6
Chapter 7. Diagnosis
Messages and Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tracing Execution of Programs and Installation Exits . . . . . . . . . . . . TRACE Function of the Information Center Facility . . . . . . . . . . . . MVSSERV Trace Facility and Trace Data Set . . . . . . . . . . . . . . TSO/E TEST and TESTAUTH Commands . . . . . . . . . . . . . . . . Debug Facilities for REXX Execs . . . . . . . . . . . . . . . . . . . . . . REXX TRACE Instruction and Built-In Function . . . . . . . . . . . . Interactive Debug Facility . . . . . . . . . . . . . . . . . . . . . . . . . TSO/E REXX Immediate Commands and the EXECUTIL Command Trace and Execution Control Routine (IRXIC) . . . . . . . . . . . . . Using the OPERATOR SLIP Command to Diagnose Installation Exits TSODATA Dump Formatter . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1 7-2 7-2 7-2 7-3 7-4 7-4 7-4 7-4 7-5 7-5 7-6
Diagnosis involves reading system messages and reading and analyzing dumps to determine where a problem occurred and, if necessary, re-creating the problem with tracing facilities in effect to obtain further information. The final step, if necessary, is to report the problem to your IBM support center and supply the necessary information. The following topics describe the tools that TSO/E provides to help you diagnose errors.
7-1
7-2
The external trace data set is a pre-allocated TSO/E data set used to record informational and error messages issued during a TSO/E MVSSERV session, calls made between MVSSERV modules, and the requests and replies sent between the PC and the host. The history of module calls is contained in an execution path trace table which follows the messages in the trace data set. Depending on the type of trace requested on the MVSSERV command, the trace data set can also include I/O related information such as transmission data and the structured fields associated with the data.
7-3
For more information about using the TEST and TESTAUTH commands to test programs and locate programming errors, see TSO/E Programming Guide, SC28-1970.
7-4
The HE immediate command halts the execution of the currently executing REXX exec. The exec is terminated before control is returned to the currently executing exec. This command is useful to terminate a looping function, subroutine, or host command not written in REXX that has been invoked by a REXX exec. IBM recommends that you use HI instead of HE whenever possible. HE will not halt execution of any exec that called the currently running exec unless you are running under ISPF. Note: HE is not a valid operand of the EXECUTIL command. The TS immediate command or the EXECUTIL TS command puts the REXX exec into normal interactive debug and you can then execute REXX instructions as you would normally. These commands are also useful if you suspect a REXX exec is looping. You can step through the exec before you decide whether to allow the exec to continue or not. The TE immediate command or the EXECUTIL TE command stops tracing. These commands can be useful to stop tracing when not in interactive debug. In the TSO/E address space, you can use the HI, HE, TS, and TE immediate commands by pressing the attention key to enter attention mode and then entering the command. In any address space, you can use the TS and TE immediate commands in an exec. You can use the EXECUTIL command with the HI, TS, and TE operands: In an exec that executes in the TSO/E address space From TSO/E READY mode and ISPF In a TSO/E CLIST In a program written in a high-level programming language by using the TSO/E service facility.
Chapter 7. Diagnosis
7-5
7-6
Index A
access method driver (AMD) customizing host-to-PC communications 5-18 types 5-18 ACCOUNT command ADD subcommand 6-4 SYNC subcommand 5-8 accounting facilities enhancements 4-14 ADDUSER TSO command 6-4 administration adding products to TSO/E 6-5 defining users to TSO/E ACCOUNT command 6-2 ENROLL option of Information Center Facility classes of users. 6-1 RACF commands 5-8, 6-2 using ENROLL option of Information Center Facility 6-4 Information Center Facility 6-2 simplifying logon procedures 4-9 administration dialog 4-15 alias user catalog 6-4 ALL keyword for FREE command and subcommand 4-15 ALLOCATE command customizing 5-9 DEST keyword 4-15 exits, list of 5-19 function 3-8 alternate libraries for load modules 4-9 alternate libraries, specifying for CLISTs and REXX execs 4-8, 6-5 ALTLIB command Application Manager invocation processing 6-5 exits, list of 5-19 function 3-8 specifying alternate libraries for CLISTs and REXX execs 4-8 APPC/MVS administration dialog 4-15 data base token planning considerations side information transaction profile APPC/MVS transaction programs profiles using in a REXX exec 4-4 Application Manager See also applications description 3-3, 6-5 exits, list of 5-19 Application Manager (continued) group 3-3 limiting use of 5-17 limiting access to applications 5-17, 6-5 menu panels 6-6 private 3-3 limiting use of 5-17 application programming CLIST language 4-8 command processors 4-10 description 4-1 REXX language support 4-2 servers, writing 4-10 services 4-11 applications adding 5-16, 6-6 automatic integration on panels 5-16 creating installation files from 6-5, 6-6 definition 6-5 displaying a hierarchy 6-6 group level accessing 3-4 levels supported 3-3, 5-17, 6-5 library types 6-6 limiting user access 5-17, 6-5 replacing 6-5 tailoring definitions 3-3, 5-17, 6-5 upgrading 5-16, 6-6 viewing 6-5 assembler programs diagnosing errors 7-3 testing 4-13 ATTRIB command function 3-8 use of ? on prompt 3-10 ATTRIB subcommand of EDIT 4-15 authorized commands and programs specifying 5-5 authorized logoff exit 5-4 authorized logon pre-prompt exit 5-3 authorized programs, diagnosing 7-3 automatic saving of data 4-14
B
background limiting commands users can issue 5-7 specifying commands not supported in 5-5 batch job 4-13 benefits of TSO/E 1-5
X-1
5-8
C
CALL command function 3-8 use of ? on prompt 3-10 CANCEL command customizing 5-9 exits, list of 5-21 function 3-8 use of ? on prompt 3-10 catalog user 6-4 changing TSO/E system defaults 5-13 CLASSROOM course type 3-3 CLIST customizing 5-14 exits, list of 5-19 features 4-8 overview 1-4 specifying alternate libraries for 4-8, 6-5 command invocation platform See command/program invocation platform Command Package overview 1-5 programming considerations 4-13 command processors 4-10 command/program invocation platform customizing 5-6 performance benefit 1-7 planning considerations commands authorized, specifying 5-5 customizing 5-8 for end users 3-8 not supported in the background, specifying online help 1-2, 3-10 RACF 6-2 restricting use of 5-7 REXX 7-4 TSO/E REXX 4-4 compiler support, REXX highlight of TSO/E 1-5 planning considerations programming considerations 4-15 COMPUTER course type 3-3 conduit dialogs 3-3 CONSOLE command benefits 1-8 considerations console names customizing 5-10 exits, list of 5-20 planning considerations
5-5
console names planning considerations CONSPROF command customizing 5-10 exits, list of 5-20 Control Unit Terminal (CUT) 5-18 course types CLASSROOM 3-3 COMPUTER 3-3 IIPS 3-3 COURSES option 3-3, 6-6 CPI communications 1-6, 4-4 CSCB planning considerations customizing access method drivers 5-18 CLIST processing 5-14 command invocation platform support commands 5-8 CONSOLE command 5-8, 5-10 CONSPROF command 5-8, 5-10 HELP processing 5-5 host services 5-5 Information Center Facility 5-15 installation, simplifying 5-13 ISPF/PDF 5-4 job and output processing 5-11 language enablement support 5-6 logoff process 5-3 logon process 5-3 logons, concurrent 5-3 RACF data base 5-8 REXX processing 5-14 Session Manager 5-15 TCAM 5-2 TSO/E environment 5-2 TSO/E resources, user access 5-7 UADS 5-8 VTAM 5-2 CUT (Control Unit Terminal) 5-18
5-6
D
data base token See APPC/MVS administration dialog data base, RACF 6-2 data set See also individual data set names printing 3-4 user access, limiting 5-7 data stack 4-6 data, automatic saving of 4-14 defaults system, changing 5-14 user attribute data set 4-15 windows 3-7
X-2
DEFINE ALIAS command 6-4 defining TSO/E users through RACF 5-8 DELETE command function 3-8 DEST keyword of ALLOCATE 4-15 of FREE 4-15 of OUTPUT 4-15 DFT (Distributed Function Terminal) 5-18 diagnosing assembler programs 7-3 Enhanced Connectivity Facility programs 7-2 exit routines 7-5 Information Center Facility CLISTs/REXX execs installation exits 7-5 REXX execs 7-4 TSO/E 7-1 display screen 3-7 Distributed Function Terminal (DFT) 5-18 DSNMAP command 3-5
7-2
E
EDIT command ATTRIB subcommand 4-15 customizing 5-11 exits, list of 5-20 FREE subcommand 4-15 ALL keyword 4-15 function 3-8 use of ? on prompt 3-10 education services 3-3 maintaining 6-6 eight-character station ID using with DEST keyword 4-15 END command function 3-8 end use of TSO/E commands 3-8 Enhanced Connectivity Facility 3-5 Information Center Facility 3-1 Session Manager 3-6 VM/PC host services 3-5 Enhanced Connectivity Facility (ECF) access method drivers, types 5-18 accessing services 3-5 diagnosing errors 3-5, 7-2 end use functions 3-5 overview 1-2 requesters, writing 4-9 server-requester programming interface servers, writing 4-9 services available 3-5 ENROLL option 6-4 exec See also REXX language support
exec (continued) description 4-2 executing 4-3 issuing host commands from 4-3 specifying alternate libraries for 4-8, 6-5 storing 4-7 testing 4-3 EXEC command exits, list of 5-20 function 3-8 use of ? on prompt 3-10 EXECIO command execs debugging, interactively 7-4 tracing 7-4 EXECUTIL command function 3-8 tracing REXX execs 7-4 exit routines diagnosing 7-5 Information Center Facility 5-18 list of TSO/E 5-19 logon post-display (IKJEFLN2) 1-3, 5-3, 5-21 logon post-prompt (IKJEFLD3) 1-3, 5-3, 5-21 logon pre-display (IKJEFLN1) 1-3, 5-3, 5-21 logon pre-prompt (IKJEFLD1) REXX 5-15 Session Manager 5-15 tracing 7-5 EXPORT option 6-5
F
FREE command ALL keyword 4-15 DEST keyword 4-15 exits, list of 5-20 function 3-9 FREE subcommand of EDIT 4-15 function packages 4-5
G
generic naming of TSO 2-1 generic resource support 2-1 GETMSG service 4-4, 4-12 group Application Manager See also applications description 3-3, 6-5 limiting use of 5-17 group level applications See also applications accessing 3-4
4-9
Index
X-3
H
HE (Halt Execution) immediate command 7-4 HELP command function 3-9 MSGID operand 7-1 obtaining help for messages 7-1 use of ? on prompt 3-10 HELP data set customizing 5-5 help information description 3-4 providing in different languages 1-2, 5-6 HI (Halt Interpretation) immediate command 7-4 HI operand EXECUTIL command 7-4 HIERARCHY option 6-6 host command environment for APPC/MVS support 1-6, 4-4 issuing in an exec 4-3 host services making available to PC users 5-5
I
IC 1-1 IC (information center) 1-1 IEFDB401 (MVS allocation input validation routine) 5-7 IEHMOVE program making available 5-5 IIAS (Interactive Instructional Authoring System) 3-3, 6-6 IIPS (Interactive Instructional Presentation System) 3-3, 6-6 IKJCALLX 7-5 IKJEFLD3 5-3, 5-21 IKJEFLN1 5-3, 5-21 IKJEFLN2 5-3, 5-21 IKJEFTAP 1-7, 5-14 IKJEFTE2 1-7, 5-14 IKJEFTE8 1-7, 5-14 IKJEFTNS 1-7, 5-14 IKJRETNX 7-5 information center 1-1 information center (IC) 1-1 Information Center Facility accessing group level applications 3-4 adding a product or service 5-16, 6-5, 6-6 administrative services 6-3 administrator panel 6-3 Application Manager 6-5 displaying a hierarchy of applications 6-6 exits, list of 5-19 exporting installation files 6-5, 6-6 levels supported 3-3 replacing applications 6-5 tailoring application invocation processing 6-6
Information Center Facility (continued) Application Manager (continued) upgrading an application 5-16, 6-6 viewing applications 6-5 command table 5-17 conduit dialogs 3-3 courses service 3-3, 6-6 customizing 5-15 diagnosing errors 7-2 education services 3-3, 6-6 end use functions 3-1 ENROLL option 6-4 exits 5-18, 5-20 group Application Manager 3-3, 6-5 help information 3-4 highlight of TSO/E 1-1 ISPF default profile, customizing 6-4 mass installation file process 5-16 names directory 3-3 names service 6-3 news service 3-2, 6-3 planning considerations for print definitions 6-5 printing course abstracts 3-3, 6-6 data sets 3-4 news items 3-2, 6-3 private Application Manager 3-3, 6-5 specifying a group 3-4 start-up processing, customizing 5-18 termination processing, customizing 5-18 TRACE function 7-2 tutorial 3-4 user panel 3-2 user type service 6-4 INMRZ15R (RECEIVE post-prompt exit) 5-24 installation exits diagnosing 7-5 tracing 7-5 installation file INVOKING_PANEL entry 5-16 installation simplification 1-7, 5-13 interactive debug facility 7-4 Interactive Instructional Authoring System (IIAS) 3-3, 6-6 Interactive Instructional Presentation System (IIPS) 3-3, 6-6 interactive problem control system (IPCS) invoking TSODATA dump formatter 7-6 Interactive System Productivity Facility (ISPF) services used by the Information Center Facility 3-1 INVOKING_PANEL entry 5-16 IPCS See interactive problem control system (IPCS) IPCS VERBEXIT command 7-6
X-4
IRXEXCOM 4-5 IRXEXEC 4-5 IRXIC 4-5, 7-5 IRXJCL 4-5 IRXRLT 4-5 IRXSUBCM 4-5 ISPF See Interactive System Productivity Facility (ISPF) ISPF/PDF customizing 5-4 limiting commands users can issue 5-7 system default ISPF profile, customizing 6-4
J
JESJOBS 5-11 JESSPOOL 5-11 job submission customizing 5-9
LOGON command benefits 1-6 exits, list of 5-21 function 3-9 planning considerations logon limits, changing 5-3 logon panel, full-screen benefits 1-3, 1-6 language support 1-3 planning considerations logon pre-prompt exit IKJEFLD 5-3 logon pre-prompt exit IKJEFLD1 5-3 logon processing customizing 5-3 logon post-display exit 1-3, 5-3, 5-21 logon post-prompt exit 1-3, 5-3, 5-21 logon pre-display exit 1-3, 5-3, 5-21 LU 6.2 callable services See host command environment
K
keywords See individual keyword names
M
maintaining educational services 6-6 the names directory 6-3 the news service 6-3 the system default ISPF profile 6-4 user type definitions 6-4 mass installation file process description 5-16, 6-6 menu panel scrollable 6-6 messages and codes, TSO/E online help, obtaining 7-1 providing in different languages 5-6 modifying See customizing MSGID (list) operand HELP command 7-1 MVS allocation input validation routine (IEFDB401) MVSSERV command accessing services from the PC 3-5 function 3-9 issuing messages 7-1 trace data set 7-1, 7-2 trace options 7-2 VM/PC servers 3-5
L
language enablement 1-3 benefits 1-3 customizing 5-6 planning considerations library types for Information Center Facility applications 6-6 LINK command function 3-9 LISTALC command function 3-9 LISTBC command customizing 5-11 exits, list of 5-21 function 3-9 LISTCAT command function 3-9 LISTDS command function 3-9 making available 5-5 LOADGO command function 3-9 LOGOFF command exits, list of 5-21 function 3-9 logoff exit (IKJEFLD2) 5-21 logoff exit IKJEFLD2 5-4 logoff processing customizing 5-3
5-7
N
names directory 3-3 maintaining 6-3 NAMES option 3-3, 6-3 NAMES.TEXT file 6-3 naming, generic 2-1
Index
X-5
NEWS option 3-2, 6-3 news service 3-2 maintaining 6-3 NLS logon planning considerations
O
online help 1-2, 3-10 OPERATOR command SEND subcommand customizing 5-11 exits, list of 5-22 OPERATOR SEND subcommand 5-11, 5-22 parallel sysplex support 2-2 planning considerations OPERATOR SLIP command diagnosing installation exits 7-5 OUTDES command defining output descriptors 5-9, 5-12 exits, list of 5-21 function 3-9 OUTPUT command customizing 5-9 DEST keyword 4-15 exits, list of 5-21 function 3-9 use of ? on prompt 3-10 output descriptors defining 5-9, 5-12
P
panel administrator's primary 6-3 Application Manager 6-6 integrating applications automatically 5-16 menu 6-6 user's primary 3-2 parallel sysplex 2-1 parallel sysplex support PARMLIB command 2-2 SEND command 2-2 PARMLIB command changing system defaults 5-14 description 1-7 exits, list of 5-22 listing system defaults 5-14 listing USERLOGSIZE 2-3 parallel sysplex support 2-2 planning considerations for partitioned data set printing 3-4 performance enhancements 1-6 planning considerations for TSO/E command invocation platform support
planning considerations for TSO/E (continued) command/program platform support 1-7 CONSOLE command CSCB (command scheduler control block) language enablement support LWA (logon work area) OPERATOR SEND subcommand PROFILE command SEND command SYSPLEXSHR option UPT (user profile table) PLATCMD 5-6 PLATPGM 5-6 PRINTDS command customizing 5-12 exits, list of 5-22 function 3-9 printing 3-4 course abstracts 3-3, 6-6 data sets 3-4 news items 3-2, 6-3 private Application Manager See also applications description 3-3, 6-5 limiting use of 5-17 private level applications See applications products, adding 6-5, 6-6 PROFILE command function 3-9 program invocation platform See command/program invocation platform programming CLIST language 4-8 command processors 4-10 REXX language support 4-2 servers 4-10 services 4-11 PROTECT command function 3-9 protecting TSO/E resources 5-7 user logs 5-12
R
RACF adding users 5-8, 6-4 ADDUSER TSO command 6-2, 6-4 ALTUSER NOTSO command 6-2 ALTUSER TSO command 6-2 controlling console attributes 5-10 customizing job and output processing data base converting to 6-2 JESJOBS resource class 5-11
5-11
X-6
RACF (continued) JESSPOOL resource class 5-11 LISTUSER TSO command 6-2 resource classes 5-11, 5-12 security labels SMESSAGE class SMESSAGE resource class 5-12 SURROGAT resource class 5-11 synchronizing data base with broadcast data set 5-8 TESTAUTH resource 7-3 RACONVRT command 5-8 RACONVRT utility 6-2 READY mode limiting commands users can issue 5-7 RECEIVE command customizing 5-13 defaults, specifying 5-5 exits, list of 5-24 function 3-9 making available 5-5 NAMES.TEXT file, updating 6-3 reconnect interval 2-2 reconnection support 2-2 RENAME command function 3-9 replaceable routines 5-14 replacing existing applications 6-5 requester 4-9 resource support, generic 2-1 REXX compiler support highlight of TSO/E 1-5 planning considerations programming considerations 4-15 REXX exec See exec REXX language support APPC/MVS transaction programs 1-4, 1-6 built-in functions 4-3 compatibility 4-3 customizing services 4-6, 5-14 data stack 4-6 debug facilities 7-4 executing execs 4-3 exits 5-15, 5-22 external functions 4-4 features 4-2 format 4-2 function packages 4-5 instructions 4-2 interactive debug facility 7-4 IRXIC 7-5 issuing host commands in execs 4-3 overview 1-4 parsing capabilities 4-2 programming services 4-5
REXX language support (continued) SETLANG external function 4-4 syntax 4-2 Systems Application Architecture Procedures Language 4-3 testing execs 4-3 TRACE built-in function 7-4 trace facilities 7-4 TRACE instruction 7-4 TSO/E functions 4-4 TSO/E REXX commands 4-4 immediate commands 7-4 REXX processing customizing 5-14 RUN command function 3-9 use of ? on prompt 3-10 running terminal session as a batch job 4-13
S
SAA See Systems Application Architecture scrollable menu panel 6-6 SECLABEL operand 5-3 See also security labels security labels 5-8 defining users to TSO/E 6-1, 6-4 Information Center Facility restriction 6-1, 6-4 logon pre-prompt exit 5-3 logon processing 5-4 protecting TSO/E resources 5-8 TRANSMIT and RECEIVE processing 5-13 SEND command customizing 5-11 exits, list of 5-22 function 3-9 parallel sysplex support 2-2 sequential data set printing 3-4 server 4-9 server-requester programming interface (SRPI) description 4-9 Session Manager customizing 5-15 display screen 3-7 end use for 3-6 exits 5-15, 5-23 limiting commands users can issue 5-7 major functions 3-6 overview 1-2 set up See installation side information See APPC/MVS administration dialog
Index
X-7
SMCOPY command function 3-9 SMESSAGE 5-12 SMF (System Management Facilities) 4-14 SMFIND command function 3-9 SMPUT command function 3-9 station ID using with DEST keyword 4-15 STATUS command customizing 5-9 exits, list of 5-21 function 3-9 Storage Management Subsystem 5-9 subcommands See individual subcommand names SUBMIT command customizing 5-9 END(nn) operand 4-14 exit 5-23 function 3-9 PAUSE operand 4-14 submitting a job 4-13, 4-14 support, generic resource 2-1 SURROGAT 5-11 SYNC command 5-8 SYNC subcommand of ACCOUNT 5-8 SYS1.HELP See HELP data set SYS1.PARMLIB 5-14 advantages of using 1-7 customizing VTAM/TCAM 5-2 IKJTSO00 member 5-13 IKJTSOxx member 5-13 specifying system defaults 5-13 SYS1.SAMPLIB samples of SYS1.PARMLIB parameters 5-13 SYS1.UADS See UADS SYSDEF option 6-4 SYSEXEC 4-7 SYSPLEXSHR option SYSPROC 4-7 SYSPROC file system default ISPF profile 6-4 system defaults changing 5-14 listing 5-14 system dumps, formatting information from 7-6 System Management Facilities (SMF) 4-14 Systems Application Architecture 1-4 Procedures Language 1-4, 4-3 support 1-8
T
table look-up service 5-5 tailoring See customizing TCAM customizing 5-2 TE (Trace End) immediate command 7-4 TE operand EXECUTIL command 7-4 TERMINAL command function 3-9 TEST command APPC/MVS transaction programs 1-2, 1-8, 4-13, 7-3 assemble programs 4-13 customizing 5-12 diagnosing errors in programs 7-3 exits, list of 5-23 function 3-10 use of ? on prompt 3-10 TESTAUTH command APPC/MVS transaction programs 1-2, 1-8, 4-13, 7-3 customizing 5-12 diagnosing errors in APF-authorized programs 7-3 exits, list of 5-23 testing APF-authorized programs 4-13 testing assembler programs 4-13 trace data set 7-2 TRACE function of Information Center Facility 7-2 tracing program execution 7-2 transaction profile See APPC/MVS administration dialog transaction programs (APPC/MVS) profiles using in a REXX exec 4-4 TRANSMIT command customizing 5-13 defaults, specifying 5-5 exits, list of 5-24 function 3-10 making available 5-5 NAMES.TEXT file, updating 6-3 TS (Trace Start) immediate command 7-4 TS operand EXECUTIL command 7-4 TSO command 3-5 TSO/E adding products 6-5, 6-6 administration 6-1 application programming 4-1 assistance to users 3-10 benefits 1-7 changing system defaults 5-14 command/program invocation platform planning considerations
X-8
TSO/E (continued) command/program invocation platform (continued) support 1-7, 5-6 customizing 5-1 defining users ACCOUNT command 6-2 ENROLL option of Information Center Facility 6-1, 6-4 RACF commands 5-8, 6-2 derivation of acronym 1-1 diagnosis 7-1 end use 3-1 environment, customizing 5-2 exits, list of 5-19 generic resource support 2-1 highlights 1-1 introduction 1-1 language enablement support 5-6 major benefits 1-5 messages and codes 7-1 providing in different languages 5-6 name derivation 1-1 parallel sysplex 2-1 planning for programming 4-1 purpose 1-1 REXX commands 4-4 users 1-1 TSO/E environment service (IKJTSOEV) benefits 1-6 using 4-11, 4-12 TSO/E READY mode See READY mode TSO/E service facility 1-4, 4-12 TSODATA dump formatter 7-6 TSOEXEC command function 3-10 TSOLIB command exits, list of 5-24 function 3-10 simplifying logon procedures 4-9 specifying alternate libraries for load modules 4-9 tutorial 3-4
user (continued) defining to TSO/E (continued) RACF commands 6-2 RACF commands 5-8 user attributes data set See UADS user catalog alias 6-4 user ISPF profile 6-4 user logs default size allocation 2-3 protecting 5-12 user panel 3-2 user type definitions maintaining 6-4 USERLOGSIZE keyword 2-3 users of TSO/E 1-1 USERTYPE option 6-4
V
VIEW option 6-5 virtual storage constraint relief (VSCR) benefit 1-7 VLF data repository file compression 1-6 VLFNOTE command function 3-10 making available 5-5 VM/PC host services end use for 3-5 overview 1-2 VM/PC servers accessing 3-6 exit 5-25 services 3-6 VSAM DEFINE ALIAS command 6-4 VTAM customizing 5-2
W
WHEN command function 3-10
U
UADS converting to RACF data base 5-8, 6-2 defaults 4-15 upgrade function 6-6 description 5-16 user assistance to 3-10 defining to TSO/E ACCOUNT command 6-2 ENROLL option of Information Center Facility 6-1, 6-4
Index
X-9
How satisfied are you that the information in this book is:
Very Satisfied Accurate Complete Easy to find Easy to understand Well organized Applicable to your tasks Satisfied Neutral Dissatisfied Very Dissatisfied
Yes
No
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.
Name
Address
Company or Organization
Phone No.
IBM
IBM Corporation Department 55JA, Mail Station P384 522 South Road Poughkeepsie, NY 12601-5400 United States of America
GC28-1964-01
IBM
GC28-1964- 1