t so command reference

8/21/2019 t So Command Reference

1/453

z/OS

TSO/E

Command Reference

SA22-7782-09


2/453


3/453

z/OS

TSO/E

Command Reference

SA22-7782-09


4/453

Note

Before using this information and the product it supports, be sure to read the general information under Notices on page

407.

Tenth Edition, September 2007

This edition applies to Version 1, Release 9 of z/OS (5694-A01) and to all subsequent releases and modificationsuntil otherwise indicated in new editions.

This is a major revision of SA22-7782-08.

IBM welcomes your comments. A form for readers comments may be provided at the back of this document, or youmay address your comments to the following address:

International Business Machines CorporationMHVRCFS, Mail Station P1812455 South RoadPoughkeepsie, NY 12601-5400United States of America

FAX (United States & Canada): 1+845+432-9405FAX (Other Countries):

Your International Access Code +1+845+432-9405

IBMLink (United States customers only): IBMUSM10(MHVRCFS)Internet e-mail: [email protected] Wide Web: http://www.ibm.com/servers/eserver/zseries/zos/webqs.html

If you would like a reply, be sure to include your name, address, telephone number, or FAX number.

Make sure to include the following in your comment or note:v Title and order number of this document

v Page number or topic related to your comment

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 1988, 2007. All rights reserved.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.
http://www.ibm.com/servers/eserver/zseries/zos/webqs.htmlhttp://www.ibm.com/servers/eserver/zseries/zos/webqs.html


5/453

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

About this document . . . . . . . . . . . . . . . . . . . . . . xiWho should use this document . . . . . . . . . . . . . . . . . . . xiHow this document is organized . . . . . . . . . . . . . . . . . . . xiWhere to find more information . . . . . . . . . . . . . . . . . . . xi

Summary of changes . . . . . . . . . . . . . . . . . . . . . . xiii

Chapter 1. TSO/E commands and subcommands . . . . . . . . . . . 1Using a TSO/E command . . . . . . . . . . . . . . . . . . . . . 9How to read the TSO/E command syntax . . . . . . . . . . . . . . . 10Using the HELP command . . . . . . . . . . . . . . . . . . . . 14Using commands for VSAM and Non-VSAM data sets . . . . . . . . . . 14TSO/E commands and subcommands . . . . . . . . . . . . . . . . 15

Summary of TSO/E commands . . . . . . . . . . . . . . . . . . . 15ALLOCATE command . . . . . . . . . . . . . . . . . . . . . . 17ALTLIB command . . . . . . . . . . . . . . . . . . . . . . . . 55ATTRIB command. . . . . . . . . . . . . . . . . . . . . . . . 62CALL command . . . . . . . . . . . . . . . . . . . . . . . . 70CANCEL command . . . . . . . . . . . . . . . . . . . . . . . 74DELETE command . . . . . . . . . . . . . . . . . . . . . . . 75EDIT command. . . . . . . . . . . . . . . . . . . . . . . . . 79END command . . . . . . . . . . . . . . . . . . . . . . . . 130EXEC command . . . . . . . . . . . . . . . . . . . . . . . . 130EXECUTIL command . . . . . . . . . . . . . . . . . . . . . . 142FREE command . . . . . . . . . . . . . . . . . . . . . . . . 149HELP command . . . . . . . . . . . . . . . . . . . . . . . . 154LINK command . . . . . . . . . . . . . . . . . . . . . . . . 158LISTALC command . . . . . . . . . . . . . . . . . . . . . . . 171LISTBC command . . . . . . . . . . . . . . . . . . . . . . . 174LISTCAT command . . . . . . . . . . . . . . . . . . . . . . . 176LISTDS command . . . . . . . . . . . . . . . . . . . . . . . 180LOADGO command . . . . . . . . . . . . . . . . . . . . . . 182LOGOFF command. . . . . . . . . . . . . . . . . . . . . . . 190LOGON command . . . . . . . . . . . . . . . . . . . . . . . 191MVSSERV command . . . . . . . . . . . . . . . . . . . . . . 196OUTDES command. . . . . . . . . . . . . . . . . . . . . . . 197OUTPUT command . . . . . . . . . . . . . . . . . . . . . . . 211OUTPUT subcommands (overview) . . . . . . . . . . . . . . . . . 217

OUTPUTCONTINUE subcommand . . . . . . . . . . . . . . . . 217OUTPUTEND subcommand . . . . . . . . . . . . . . . . . . . 218OUTPUTHELP subcommand . . . . . . . . . . . . . . . . . . 218OUTPUTSAVE subcommand . . . . . . . . . . . . . . . . . . 219PRINTDS command . . . . . . . . . . . . . . . . . . . . . . 219PROFILE command . . . . . . . . . . . . . . . . . . . . . . 234PROTECT command . . . . . . . . . . . . . . . . . . . . . . 241RECEIVE command . . . . . . . . . . . . . . . . . . . . . . 245RENAME command . . . . . . . . . . . . . . . . . . . . . . 256RUN command . . . . . . . . . . . . . . . . . . . . . . . . 257SEND command . . . . . . . . . . . . . . . . . . . . . . . . 261

Copyright IBM Corp. 1988, 2007 iii


6/453

SMCOPY command . . . . . . . . . . . . . . . . . . . . . . 266SMFIND command . . . . . . . . . . . . . . . . . . . . . . . 269SMPUT command . . . . . . . . . . . . . . . . . . . . . . . 271STATUS command . . . . . . . . . . . . . . . . . . . . . . . 272SUBMIT command . . . . . . . . . . . . . . . . . . . . . . . 273TERMINAL command . . . . . . . . . . . . . . . . . . . . . . 277TEST command . . . . . . . . . . . . . . . . . . . . . . . . 282

TEST subcommands (overview) . . . . . . . . . . . . . . . . . . 287TESTALLOCATE command . . . . . . . . . . . . . . . . . . . 289TESTAND subcommand . . . . . . . . . . . . . . . . . . . . 289Assignment of values function of TEST . . . . . . . . . . . . . . . 291TESTAT subcommand . . . . . . . . . . . . . . . . . . . . . 296TESTATTRIB command . . . . . . . . . . . . . . . . . . . . 300TESTCALL subcommand . . . . . . . . . . . . . . . . . . . . 300TESTCANCEL command . . . . . . . . . . . . . . . . . . . . 302TESTCOPY subcommand . . . . . . . . . . . . . . . . . . . 302TESTDELETE subcommand . . . . . . . . . . . . . . . . . . 305TESTDROP subcommand . . . . . . . . . . . . . . . . . . . 305TESTEND subcommand . . . . . . . . . . . . . . . . . . . . 306TESTEQUATE subcommand . . . . . . . . . . . . . . . . . . 307

TESTEXEC command . . . . . . . . . . . . . . . . . . . . . 309TESTFREEMAIN subcommand . . . . . . . . . . . . . . . . . 309TESTGETMAIN subcommand . . . . . . . . . . . . . . . . . . 310TESTGO subcommand . . . . . . . . . . . . . . . . . . . . 311TESTHELP command . . . . . . . . . . . . . . . . . . . . . 313TESTLINK command . . . . . . . . . . . . . . . . . . . . . 313TESTLIST subcommand . . . . . . . . . . . . . . . . . . . . 313TESTLISTALC command . . . . . . . . . . . . . . . . . . . . 319TESTLISTBC command . . . . . . . . . . . . . . . . . . . . 319TESTLISTCAT command . . . . . . . . . . . . . . . . . . . . 319TESTLISTDCB subcommand . . . . . . . . . . . . . . . . . . 319TESTLISTDEB subcommand . . . . . . . . . . . . . . . . . . 321TESTLISTDS command . . . . . . . . . . . . . . . . . . . . 322TESTLISTMAP subcommand . . . . . . . . . . . . . . . . . . 323TESTLISTPSW subcommand . . . . . . . . . . . . . . . . . . 324TESTLISTTCB subcommand . . . . . . . . . . . . . . . . . . 325TESTLISTVP subcommand . . . . . . . . . . . . . . . . . . . 327TESTLISTVSR subcommand . . . . . . . . . . . . . . . . . . 327TESTLOAD subcommand . . . . . . . . . . . . . . . . . . . 328TESTOFF subcommand . . . . . . . . . . . . . . . . . . . . 329TESTOR subcommand . . . . . . . . . . . . . . . . . . . . 331TESTPROFILE command . . . . . . . . . . . . . . . . . . . 333TESTPROTECT command . . . . . . . . . . . . . . . . . . . 333TESTQUALIFY subcommand . . . . . . . . . . . . . . . . . . 334TESTRENAME command . . . . . . . . . . . . . . . . . . . 336

TESTRUN subcommand . . . . . . . . . . . . . . . . . . . . 336TESTSEND command . . . . . . . . . . . . . . . . . . . . . 337TESTSETVSR subcommand . . . . . . . . . . . . . . . . . . 338TESTSTATUS command . . . . . . . . . . . . . . . . . . . . 338TESTSUBMIT command . . . . . . . . . . . . . . . . . . . . 339TESTTERMINAL command . . . . . . . . . . . . . . . . . . . 339TESTUNALLOC command . . . . . . . . . . . . . . . . . . . 339TESTWHERE subcommand. . . . . . . . . . . . . . . . . . . 339TIME command . . . . . . . . . . . . . . . . . . . . . . . . 341TRANSMIT command . . . . . . . . . . . . . . . . . . . . . . 342TSOEXEC command . . . . . . . . . . . . . . . . . . . . . . 356

iv z/OS V1R9.0 TSO/E Command Reference


7/453

TSOLIB command . . . . . . . . . . . . . . . . . . . . . . . 357VLFNOTE command . . . . . . . . . . . . . . . . . . . . . . 366WHEN command . . . . . . . . . . . . . . . . . . . . . . . 369

Chapter 2. Session Manager commands . . . . . . . . . . . . . . 371Entering Session Manager commands . . . . . . . . . . . . . . . . 371Command format . . . . . . . . . . . . . . . . . . . . . . . 372

Session Manager Command syntax. . . . . . . . . . . . . . . . . 373Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . 373Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . 373Session Manager Command summary. . . . . . . . . . . . . . . . 373CHANGE.CURSOR command. . . . . . . . . . . . . . . . . . . 375

Appendix. Accessibility. . . . . . . . . . . . . . . . . . . . . 405Using assistive technologies . . . . . . . . . . . . . . . . . . . 405Keyboard navigation of the user interface. . . . . . . . . . . . . . . 405z/OS information . . . . . . . . . . . . . . . . . . . . . . . . 405

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 407Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 409

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . 411TSO/E Publications . . . . . . . . . . . . . . . . . . . . . . . 411Related Publications . . . . . . . . . . . . . . . . . . . . . . 411

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

Contents v


8/453

vi z/OS V1R9.0 TSO/E Command Reference


9/453

Figures

1. Allocating and creating input data sets in the background . . . . . . . . . . . . . . . . 702. Information available through the HELP command . . . . . . . . . . . . . . . . . . 155

Copyright IBM Corp. 1988, 2007 vii


10/453

viii z/OS V1R9.0 TSO/E Command Reference


11/453

Tables

1. Commands preferred for VSAM/Non-VSAM data sets . . . . . . . . . . . . . . . . . 142. Summary of the TSO/E commands . . . . . . . . . . . . . . . . . . . . . . . . 153. ALLOCATE command return codes . . . . . . . . . . . . . . . . . . . . . . . . 494. Library search order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555. ALTLIB command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 616. ATTRIB command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 697. CALL command return codes . . . . . . . . . . . . . . . . . . . . . . . . . . 728. CANCEL Command Return Codes . . . . . . . . . . . . . . . . . . . . . . . . 759. DELETE Command Return Codes . . . . . . . . . . . . . . . . . . . . . . . . 78

10. EDIT command: default values for LINE or LRECL and BLOCK or BLKSIZE operands . . . . . 8611. EDIT command return codes . . . . . . . . . . . . . . . . . . . . . . . . . . 8612. Subcommands and functions of the EDIT command . . . . . . . . . . . . . . . . . . 8813. Default tab settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12614. Library search order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13715. EXEC command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 13916. EXECUTIL command return codes . . . . . . . . . . . . . . . . . . . . . . . . 148

17. FREE command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 15218. HELP command return codes. . . . . . . . . . . . . . . . . . . . . . . . . . 15719. LINK command return codes . . . . . . . . . . . . . . . . . . . . . . . . . . 17020. LISTALC command return codes . . . . . . . . . . . . . . . . . . . . . . . . 17221. LISTBC command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 17522. LISTBC command return codes (installation-defined user log data set) . . . . . . . . . . 17523. LISTCAT command return codes . . . . . . . . . . . . . . . . . . . . . . . . 18024. LISTDS command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 18225. LOADGO command return codes . . . . . . . . . . . . . . . . . . . . . . . . 18926. MVSSERV command return codes . . . . . . . . . . . . . . . . . . . . . . . . 19727. OUTDES command return codes . . . . . . . . . . . . . . . . . . . . . . . . 20928. OUTPUT command return codes . . . . . . . . . . . . . . . . . . . . . . . . 21629. Subcommands and functions of the OUTPUT command . . . . . . . . . . . . . . . . 217

30. Valid machine printer carriage control characters . . . . . . . . . . . . . . . . . . 22431. Summary of default values for the PRINTDS command . . . . . . . . . . . . . . . . 23132. Mutually exclusive operands on the PRINTDS command. . . . . . . . . . . . . . . . 23233. PRINTDS command return codes . . . . . . . . . . . . . . . . . . . . . . . . 23334. System defaults for control characters . . . . . . . . . . . . . . . . . . . . . . 23535. UPT/PSCB initialization table in the background . . . . . . . . . . . . . . . . . . . 23936. PROFILE command return codes . . . . . . . . . . . . . . . . . . . . . . . . 24037. PROTECT command return codes . . . . . . . . . . . . . . . . . . . . . . . . 24438. RECEIVE command return codes . . . . . . . . . . . . . . . . . . . . . . . . 25139. Combinations of source and target data sets . . . . . . . . . . . . . . . . . . . . 25240. RENAME command return codes . . . . . . . . . . . . . . . . . . . . . . . . 25741. Source statement/licensed program relationship . . . . . . . . . . . . . . . . . . . 25742. RUN command return codes . . . . . . . . . . . . . . . . . . . . . . . . . . 261

43. SEND command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 26544. SEND command return codes (installation-defined user log data set) . . . . . . . . . . . 26545. SMCOPY command return codes . . . . . . . . . . . . . . . . . . . . . . . . 26946. SMFIND command return codes. . . . . . . . . . . . . . . . . . . . . . . . . 27147. SMPUT command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 27248. STATUS command return codes. . . . . . . . . . . . . . . . . . . . . . . . . 27349. SUBMIT command return codes. . . . . . . . . . . . . . . . . . . . . . . . . 27750. TERMINAL command return codes. . . . . . . . . . . . . . . . . . . . . . . . 28151. TEST Command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 28552. Subcommands and functions of the TEST command . . . . . . . . . . . . . . . . . 28753. TRANSMIT command return codes . . . . . . . . . . . . . . . . . . . . . . . 347

Copyright IBM Corp. 1988, 2007 ix


12/453

54. TSOEXEC command return codes . . . . . . . . . . . . . . . . . . . . . . . . 35755. TSOLIB command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 36356. VLFNOTE command return codes . . . . . . . . . . . . . . . . . . . . . . . . 36957. Summary of the Session Manager commands . . . . . . . . . . . . . . . . . . . 37358. CHANGE.CURSOR command return codes . . . . . . . . . . . . . . . . . . . . 37659. CHANGE.FUNCTION command return codes. . . . . . . . . . . . . . . . . . . . 37860. CHANGE.MODE command return codes . . . . . . . . . . . . . . . . . . . . . 379

61. CHANGE.PFK command return codes . . . . . . . . . . . . . . . . . . . . . . 38162. CHANGE.STREAM command return codes . . . . . . . . . . . . . . . . . . . . 38263. CHANGE.TERMINAL command return codes . . . . . . . . . . . . . . . . . . . . 38364. CHANGE.WINDOW command return codes . . . . . . . . . . . . . . . . . . . . 38565. DEFINE.WINDOW command return codes . . . . . . . . . . . . . . . . . . . . . 38866. DELETE.WINDOW command return codes. . . . . . . . . . . . . . . . . . . . . 38967. FIND command return codes . . . . . . . . . . . . . . . . . . . . . . . . . . 39168. PUT command return codes . . . . . . . . . . . . . . . . . . . . . . . . . . 39269. QUERY command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 39470. RESET command return codes . . . . . . . . . . . . . . . . . . . . . . . . . 39671. RESTORE command return codes . . . . . . . . . . . . . . . . . . . . . . . . 39772. SAVE command return codes. . . . . . . . . . . . . . . . . . . . . . . . . . 39873. SCROLL command return codes . . . . . . . . . . . . . . . . . . . . . . . . 401

74. SHAPSHOT command return codes . . . . . . . . . . . . . . . . . . . . . . . 40275. UNLOCK command return codes . . . . . . . . . . . . . . . . . . . . . . . . 403

x z/OS V1R9.0 TSO/E Command Reference


13/453

About this document

This document supports z/OS (5694A01).

This document describes the syntax and function of the commands andsubcommands of the TSO/E command language and Session Manager. It providesonly reference material and assumes you are experienced in the use of TSO/E andSession Manager.

If you are not familiar with TSO/E, first read z/OS TSO/E Users Guide. If you havelittle or no knowledge of the use of TSO/E commands, z/OS TSO/E Users Guide,provides the prerequisite information for using this document. The guide explainshow to:v Enter and execute commandsv Name and create specific types of data setsv Edit, rename, list, copy, free, and delete data setsv Send and receive data setsv Print data sets on a JES printerv

Run programs in the foreground or backgroundv Use TSO/E through ISPF/PDFv Use Session Manager

Notes:

1. System programming commands are described in z/OS TSO/E SystemProgramming Command Reference.

2. When you see the term JESPLEX in this publication, understand it to meaneither a logical grouping of JES2 systems that share the same multi-accessspool (MAS) or a logical grouping of JES3 systems (each JES3 systemconsisting of one global JES3 system and some number of local JES3systems).

Who should use this documentAnyone who uses TSO/E and Session Manager commands.

How this document is organized

The major chapters in this document are:

v Chapter 1, TSO/E commands and subcommands, on page 1 contains generalinformation needed to use TSO/E commands. It describes the syntax notation indiagrams that accompany each command, positional and keyword operands,delimiters, line continuation, comments, and subcommands.

This document presents commands in alphabetical order. The subcommands are

alphabetized under their commands. For example, all TEST subcommands arealphabetized under the TEST command. Examples are included.

v Chapter 2, Session Manager commands, on page 371 describes the syntax andfunction of each Session Manager command. It presents the commands inalphabetical order and includes examples.

Where to find more information

See z/OS Information Roadmap for an overview of the documentation associatedwith z/OS, including the documentation available for z/OS TSO/E.

Copyright IBM Corp. 1988, 2007 xi
http://ikj4c230.pdf/http://ikj4c230.pdf/http://ikj4c230.pdf/http://ikj4c430.pdf/http://ikj4c430.pdf/http://e0z2c180.pdf/http://e0z2c180.pdf/http://ikj4c430.pdf/http://ikj4c430.pdf/http://ikj4c230.pdf/http://ikj4c230.pdf/


14/453

Introductory information about how to use TSO/E is described in z/OS TSO/EUsers Guide.

Using LookAt to lookup message explanationsLookAt is an online facility that lets you look up explanations for most of the IBM

messages you encounter, as well as for some system abends and codes. UsingLookAt to find information is faster than a conventional search because in mostcases LookAt goes directly to the message explanation.

You can use LookAt from these locations to find IBM message explanations forz/OS elements and features, z/VM, z/VSE, and Clusters for AIX and Linux:

v The Internet. You can access IBM message explanations directly from the LookAtWeb site at www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/.

v Your z/OS TSO/E host system. You can install code on your z/OS systems toaccess IBM message explanations using LookAt from a TSO/E command line(for example: TSO/E prompt, ISPF, or z/OS UNIX System Services).

v Your Microsoft Windows workstation. You can install LookAt directly from thez/OS Collection (SK3T-4269) or the z/OS and Software Products DVD Collection(SK3T-4271) and use it from the resulting Windows graphical user interface(GUI). The command prompt (also known as the DOS > command line) versioncan still be used from the directory in which you install the Windows version ofLookAt.

v Your wireless handheld device. You can use the LookAt Mobile Edition fromwww.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookatm.html with ahandheld device that has wireless access and an Internet browser (for example:Internet Explorer for Pocket PCs, Blazer or Eudora for Palm OS, or Opera forLinux handheld devices).

You can obtain code to install LookAt on your host system or Microsoft Windowsworkstation from:

v A CD-ROM in the z/OS Collection (SK3T-4269).

v The z/OS and Software Products DVD Collection(SK3T-4271).

v The LookAt Web site (click Download and then select the platform, release,collection, and location that suit your needs). More information is available in theLOOKAT.ME files available during the download process.

Using IBM Health Checker for z/OSIBM Health Checker for z/OS is a z/OS component that installations can use togather information about their system environment and system parameters to helpidentify potential configuration problems before they impact availability or causeoutages. Individual products, z/OS components, or ISV software can provide checksthat take advantage of the IBM Health Checker for z/OS framework. This bookmight refer to checks or messages associated with this component.

For additional information about checks and about IBM Health Checker for z/OS,see IBM Health Checker for z/OS: Users Guide.

SDSF also provides functions to simplify the management of checks. See z/OSSDSF Operation and Customization for additional information.

xii z/OS V1R9.0 TSO/E Command Reference
http://ikj4c230.pdf/http://ikj4c230.pdf/http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookatm.htmlhttp://e0z2l120.pdf/http://e0z2l120.pdf/http://isf4cs70.pdf/http://isf4cs70.pdf/http://isf4cs70.pdf/http://isf4cs70.pdf/http://e0z2l120.pdf/http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookatm.htmlhttp://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/http://ikj4c230.pdf/http://ikj4c230.pdf/


15/453

Summary of changes

Summary of changesfor SA22-7782-09

z/OS Version 1 Release 9

This book contains information previously presented in z/OS TSO/E CommandReference, SA22-7782-08, which supports z/OS Version 1 Release 8.

Changed Information

v The syntax diagram of the TRANSMIT command has been updated. SeeTRANSMIT command syntax on page 342.

v The syntax diagram of the LINK command has been updated. See LINKcommand syntax on page 158.

v The following operands have been changed for the ALLOCATE command onpage 17:

SPACE operand on page 27

AVBLOCK operand on page 28 TRACKS operand on page 28

CYLINDERS operand on page 28

AVGREC operand on page 28

Requirements of the RECFM(F) operand on page 29

PARALLEL operand on page 31

ACCODE operand on page 31

SECMODEL operand on page 34

The expiration date form 1 on page 36 of the EXPDT operand

MODIFY operand on page 41

v

The ATTRIB command, definition of the TRTCH operand on page 68 has beenupdated.

v The FREE command, definition of the SYSOUT operand on page 151 has beenindented.

v The LINK command, definition of the LOAD operand on page 160 has beenupdated.

v The OUTDES command, definition of the MODIFY operand on page 204 hasbeen updated.

v Under Further considerations on page 359 for the TSOLIB command, thesection on authorized commands and programs on page 359 has been updated.

v The PRINTDS command, definition of the MODIFY operand on page 228 andWRITER operand on page 231 have been updated.

v Under TRANSMIT command operands on page 343, the definition of theOUTDDNAME operand on page 347 and the definition of the OUTDSNAMEoperand on page 347 have been updated.

v For the LINK and LOADGO commands, a note under the LISTPRIV parameteron page 169 and page 189 has been updated.

New Information

v The parameters, LISTPRIV, INFO, NOINFO and MODMAP have been added tothe LINK command syntax diagram LINK command on page 158.

v A new parameter, INFO | NOINFO, has been added on page 169.

Copyright IBM Corp. 1988, 2007 xiii
http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/


16/453

v A new parameter, MODMAP, has been added on page 169.

v A new release has been added to the COMPAT parameter on page 163.

v New operands, WARN | NOWARN, have been added under the TRANSMITcommand on page 347.

v A new option, INTERNAL, has been added under the CN parameter of the SENDcommand on page 263.

This document has been enabled for the following types of advanced searches inthe online z/OS Library Center: commands.

This book contains terminology, maintenance, and editorial changes. Technicalchanges or additions to the text and illustrations are indicated by a vertical line tothe left of the change.

You may notice changes in the style and structure of some content in this bookforexample, headings that use uppercase for the first letter of initial words only, andprocedures that have a different look and format. The changes are ongoingimprovements to the consistency and retrievability of information in our books.

Summary of changesfor SA22-7782-08z/OS Version 1 Release 8


New Information

v A new operand, VARSTORAGE, was added to the PROFILE command on page238.

v A new operand, PM5, was added to the LINK command on page 162.

v A new option, release, was added to the operand LKED under the LINK

command on page 163.

Changed Information

v The operator under the SEND command on page 261 has been changed.

v The syntax of CN on page 263 has been changed.

v The LINK command syntax on page 158 has been changed.

v The definition of operand PM4, PM3, and PM1 under the LINK command onpage 162 has been changed.

v The operator under the LINK command on page 166 has been changed.

v The PROFILE command syntax on page 235 has been changed.

This document contains terminology, maintenance, and editorial changes, includingchanges to improve consistency and retrievability.

Summary of changesfor SA22-7782-07z/OS Version 1 Release 7


New Information

xiv z/OS V1R9.0 TSO/E Command Reference
http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/http://ikj4c580.pdf/


17/453

Information was added for large format sequential data set support in:v DSNTYPE keyword on page 43 contains new data set values for the DSNTYPE

keyword.

Information was added for data compression support in:

LINK command operands on page 160 and LOADGO command operands on

page 184 contains new operands.

Changed Informationv Updated DSNTYPE syntax on page 22 with new values for the DSNTYPE

keyword.v PATH operand on page 44 has been updated for the ALLOCATE command.

This document contains terminology, maintenance, and editorial changes, includingchanges to improve consistency and retrievability.

Summary of changes xv


18/453

xvi z/OS V1R9.0 TSO/E Command Reference


19/453

Chapter 1. TSO/E commands and subcommands

Using a TSO/E command . . . . . . . . . . . . . . . . . . . . . 9Positional operands . . . . . . . . . . . . . . . . . . . . . . 9Keyword operands . . . . . . . . . . . . . . . . . . . . . . . 9

How to read the TSO/E command syntax . . . . . . . . . . . . . . . 10Abbreviating keyword operands . . . . . . . . . . . . . . . . . . 12Comments . . . . . . . . . . . . . . . . . . . . . . . . . 12Line continuation . . . . . . . . . . . . . . . . . . . . . . . 13Delimiters . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Using the HELP command . . . . . . . . . . . . . . . . . . . . 14Explanations of commands . . . . . . . . . . . . . . . . . . . 14Syntax interpretation of HELP information . . . . . . . . . . . . . . 14Explanations of subcommands . . . . . . . . . . . . . . . . . . 14

Using commands for VSAM and Non-VSAM data sets . . . . . . . . . . 14TSO/E commands and subcommands . . . . . . . . . . . . . . . . 15Summary of TSO/E commands . . . . . . . . . . . . . . . . . . . 15ALLOCATE command . . . . . . . . . . . . . . . . . . . . . . 17

Data sets with SMS . . . . . . . . . . . . . . . . . . . . . . 17Allocating non-SMS-managed data sets. . . . . . . . . . . . . . . 18Allocating z/OS UNIX data sets . . . . . . . . . . . . . . . . . . 19ALLOCATE command syntax . . . . . . . . . . . . . . . . . . 19ALLOCATE command operands . . . . . . . . . . . . . . . . . 22ALLOCATE command return codes . . . . . . . . . . . . . . . . 49ALLOCATE command examples . . . . . . . . . . . . . . . . . 49

ALTLIB command . . . . . . . . . . . . . . . . . . . . . . . . 55Search order for libraries . . . . . . . . . . . . . . . . . . . . 55Using ALTLIB with most applications . . . . . . . . . . . . . . . . 56Using ALTLIB with concurrent applications . . . . . . . . . . . . . . 56Using ALTLIB in ISPF . . . . . . . . . . . . . . . . . . . . . 56Using ALTLIB in the IPCS dialog . . . . . . . . . . . . . . . . . 57

Stacking Application-Level library requests. . . . . . . . . . . . . . 57ALTLIB command syntax . . . . . . . . . . . . . . . . . . . . 58ALTLIB command operands . . . . . . . . . . . . . . . . . . . 59ALTLIB command return codes . . . . . . . . . . . . . . . . . . 61ALTLIB command examples . . . . . . . . . . . . . . . . . . . 61

ATTRIB command. . . . . . . . . . . . . . . . . . . . . . . . 62ATTRIB command syntax . . . . . . . . . . . . . . . . . . . . 62ATTRIB command operands . . . . . . . . . . . . . . . . . . . 63ATTRIB command return codes. . . . . . . . . . . . . . . . . . 69ATTRIB command examples . . . . . . . . . . . . . . . . . . . 69

CALL command . . . . . . . . . . . . . . . . . . . . . . . . 70CALL command in the background . . . . . . . . . . . . . . . . 70CALL command syntax . . . . . . . . . . . . . . . . . . . . . 71

CALL command operands . . . . . . . . . . . . . . . . . . . . 71CALL command return codes . . . . . . . . . . . . . . . . . . 72CALL command examples. . . . . . . . . . . . . . . . . . . . 72

CANCEL command . . . . . . . . . . . . . . . . . . . . . . . 74CANCEL command syntax . . . . . . . . . . . . . . . . . . . 74CANCEL command operands . . . . . . . . . . . . . . . . . . 74CANCEL command return codes . . . . . . . . . . . . . . . . . 75CANCEL command examples . . . . . . . . . . . . . . . . . . 75

DELETE command . . . . . . . . . . . . . . . . . . . . . . . 75DELETE command syntax. . . . . . . . . . . . . . . . . . . . 76DELETE command operands . . . . . . . . . . . . . . . . . . 77

Copyright IBM Corp. 1988, 2007 1


20/453

DELETE command return codes . . . . . . . . . . . . . . . . . 78DELETE command example . . . . . . . . . . . . . . . . . . . 79

EDIT command. . . . . . . . . . . . . . . . . . . . . . . . . 79EDIT command syntax . . . . . . . . . . . . . . . . . . . . . 80EDIT command operands . . . . . . . . . . . . . . . . . . . . 81EDIT command return codes. . . . . . . . . . . . . . . . . . . 86EDIT command examples . . . . . . . . . . . . . . . . . . . . 86

EDIT subcommands (overview) . . . . . . . . . . . . . . . . . . 87EDITALLOCATE subcommand . . . . . . . . . . . . . . . . . 88EDITATTRIB subcommand . . . . . . . . . . . . . . . . . . 88EDITBOTTOM subcommand . . . . . . . . . . . . . . . . . . 88EDITCHANGE subcommand . . . . . . . . . . . . . . . . . . 89EDITCKPOINT subcommand . . . . . . . . . . . . . . . . . . 93EDITCOPY subcommand . . . . . . . . . . . . . . . . . . . 94EDITDELETE subcommand . . . . . . . . . . . . . . . . . . 100EDITDOWN subcommand . . . . . . . . . . . . . . . . . . 102EDITEND subcommand . . . . . . . . . . . . . . . . . . . 102EDITEXEC subcommand . . . . . . . . . . . . . . . . . . . 103EDITFIND subcommand . . . . . . . . . . . . . . . . . . . 103EDITFREE subcommand . . . . . . . . . . . . . . . . . . . 104

EDITHELP subcommand . . . . . . . . . . . . . . . . . . . 104EDITINPUT subcommand . . . . . . . . . . . . . . . . . . 104EDITINSERT subcommand . . . . . . . . . . . . . . . . . . 106EDITinsert/replace/delete function . . . . . . . . . . . . . . . 107EDITLIST subcommand . . . . . . . . . . . . . . . . . . . 109EDITMOVE subcommand. . . . . . . . . . . . . . . . . . . 110EDITPROFILE subcommand . . . . . . . . . . . . . . . . . 115EDITRENUM subcommand . . . . . . . . . . . . . . . . . . 115EDITRUN subcommand . . . . . . . . . . . . . . . . . . . 117EDITSAVE subcommand . . . . . . . . . . . . . . . . . . . 119EDITSCAN subcommand. . . . . . . . . . . . . . . . . . . 121EDITSEND subcommand. . . . . . . . . . . . . . . . . . . 123EDITSUBMIT subcommand . . . . . . . . . . . . . . . . . . 123EDITTABSET subcommand . . . . . . . . . . . . . . . . . . 126EDITTOP subcommand . . . . . . . . . . . . . . . . . . . 128EDITUNNUM subcommand . . . . . . . . . . . . . . . . . . 128EDITUP subcommand . . . . . . . . . . . . . . . . . . . . 128EDITVERIFY subcommand . . . . . . . . . . . . . . . . . . 129

END command . . . . . . . . . . . . . . . . . . . . . . . . 130END command syntax. . . . . . . . . . . . . . . . . . . . . 130END command return code . . . . . . . . . . . . . . . . . . . 130

EXEC command . . . . . . . . . . . . . . . . . . . . . . . . 130Using EXEC as a subcommand . . . . . . . . . . . . . . . . . 130EXEC command syntax . . . . . . . . . . . . . . . . . . . . 131EXEC command operands . . . . . . . . . . . . . . . . . . . 132

Using the explicit form of the EXEC command . . . . . . . . . . . . 135Using the (extended) implicit form of the EXEC command . . . . . . . 137Considerations for passing quotation marks . . . . . . . . . . . . . 138EXEC command return codes . . . . . . . . . . . . . . . . . . 139EXEC command examples . . . . . . . . . . . . . . . . . . . 139

EXECUTIL command . . . . . . . . . . . . . . . . . . . . . . 142Additional considerations for using EXECUTIL . . . . . . . . . . . . 143EXECUTIL command syntax . . . . . . . . . . . . . . . . . . 143EXECUTIL command operands . . . . . . . . . . . . . . . . . 143EXECUTIL command return codes . . . . . . . . . . . . . . . . 148EXECUTIL command examples . . . . . . . . . . . . . . . . . 148

2 z/OS V1R9.0 TSO/E Command Reference


21/453

FREE command . . . . . . . . . . . . . . . . . . . . . . . . 149FREE command syntax . . . . . . . . . . . . . . . . . . . . 149FREE command operands . . . . . . . . . . . . . . . . . . . 150FREE command return codes . . . . . . . . . . . . . . . . . . 152FREE command examples . . . . . . . . . . . . . . . . . . . 153

HELP command . . . . . . . . . . . . . . . . . . . . . . . . 154Information available through HELP . . . . . . . . . . . . . . . . 154

HELP command syntax . . . . . . . . . . . . . . . . . . . . 156HELP command operands . . . . . . . . . . . . . . . . . . . 156HELP command return codes . . . . . . . . . . . . . . . . . . 157HELP command examples . . . . . . . . . . . . . . . . . . . 157

LINK command . . . . . . . . . . . . . . . . . . . . . . . . 158LINK command syntax . . . . . . . . . . . . . . . . . . . . 158LINK command operands . . . . . . . . . . . . . . . . . . . 160LINK command return codes . . . . . . . . . . . . . . . . . . 170LINK command examples . . . . . . . . . . . . . . . . . . . 170

LISTALC command . . . . . . . . . . . . . . . . . . . . . . . 171LISTALC command syntax . . . . . . . . . . . . . . . . . . . 171LISTALC command operands . . . . . . . . . . . . . . . . . . 171LISTALC command return codes . . . . . . . . . . . . . . . . . 172

LISTALC command examples . . . . . . . . . . . . . . . . . . 172LISTBC command . . . . . . . . . . . . . . . . . . . . . . . 174

LISTBC command syntax . . . . . . . . . . . . . . . . . . . 175LISTBC command operands . . . . . . . . . . . . . . . . . . 175LISTBC command return codes . . . . . . . . . . . . . . . . . 175LISTBC command examples . . . . . . . . . . . . . . . . . . 176

LISTCAT command . . . . . . . . . . . . . . . . . . . . . . . 176LISTCAT command syntax . . . . . . . . . . . . . . . . . . . 176LISTCAT command operands . . . . . . . . . . . . . . . . . . 177LISTCAT command return codes . . . . . . . . . . . . . . . . . 180

LISTDS command . . . . . . . . . . . . . . . . . . . . . . . 180LISTDS command syntax . . . . . . . . . . . . . . . . . . . 181LISTDS command operands . . . . . . . . . . . . . . . . . . 181LISTDS command return codes . . . . . . . . . . . . . . . . . 182LISTDS command examples . . . . . . . . . . . . . . . . . . 182

LOADGO command . . . . . . . . . . . . . . . . . . . . . . 182LOADGO command syntax . . . . . . . . . . . . . . . . . . . 183LOADGO command operands . . . . . . . . . . . . . . . . . . 184LOADGO command return codes . . . . . . . . . . . . . . . . 189LOADGO command examples. . . . . . . . . . . . . . . . . . 190

LOGOFF command. . . . . . . . . . . . . . . . . . . . . . . 190LOGOFF command syntax . . . . . . . . . . . . . . . . . . . 191LOGOFF command operands . . . . . . . . . . . . . . . . . . 191LOGOFF command examples . . . . . . . . . . . . . . . . . . 191

LOGON command . . . . . . . . . . . . . . . . . . . . . . . 191

Full-Screen LOGON versus line mode LOGON . . . . . . . . . . . 191Full-Screen LOGON processing . . . . . . . . . . . . . . . . . 192LOGON command syntax . . . . . . . . . . . . . . . . . . . 193LOGON command operands . . . . . . . . . . . . . . . . . . 193LOGON command examples . . . . . . . . . . . . . . . . . . 195

MVSSERV command . . . . . . . . . . . . . . . . . . . . . . 196MVSSERV command syntax . . . . . . . . . . . . . . . . . . 196MVSSERV command operands . . . . . . . . . . . . . . . . . 196MVSSERV command return codes . . . . . . . . . . . . . . . . 197MVSSERV command examples . . . . . . . . . . . . . . . . . 197

OUTDES command. . . . . . . . . . . . . . . . . . . . . . . 197

Chapter 1. TSO/E commands and subcommands 3


22/453

OUTDES command syntax . . . . . . . . . . . . . . . . . . . 197OUTDES command operands . . . . . . . . . . . . . . . . . . 199Coding rules . . . . . . . . . . . . . . . . . . . . . . . . 209OUTDES command return codes. . . . . . . . . . . . . . . . . 209OUTDES command examples . . . . . . . . . . . . . . . . . . 209

OUTPUT command . . . . . . . . . . . . . . . . . . . . . . . 211OUTPUT command syntax . . . . . . . . . . . . . . . . . . . 212

OUTPUT command operands . . . . . . . . . . . . . . . . . . 212Output sequence. . . . . . . . . . . . . . . . . . . . . . . 214Subcommands for the OUTPUT command . . . . . . . . . . . . . 215Checkpointed data set. . . . . . . . . . . . . . . . . . . . . 216OUTPUT command return codes . . . . . . . . . . . . . . . . . 216OUTPUT command examples . . . . . . . . . . . . . . . . . . 216

OUTPUT subcommands (overview) . . . . . . . . . . . . . . . . . 217OUTPUTCONTINUE subcommand . . . . . . . . . . . . . . . . 217

OUTPUTCONTINUE subcommand syntax . . . . . . . . . . . . 217OUTPUTCONTINUE subcommand operands . . . . . . . . . . . 217OUTPUTCONTINUE subcommand examples . . . . . . . . . . . 218

OUTPUTEND subcommand . . . . . . . . . . . . . . . . . . . 218OUTPUTEND subcommand syntax . . . . . . . . . . . . . . . 218

OUTPUTHELP subcommand . . . . . . . . . . . . . . . . . . 218OUTPUTSAVE subcommand . . . . . . . . . . . . . . . . . . 219

OUTPUTSAVE subcommand syntax. . . . . . . . . . . . . . . 219OUTPUTSAVE subcommand operand . . . . . . . . . . . . . . 219OUTPUTSAVE subcommand examples . . . . . . . . . . . . . 219

PRINTDS command . . . . . . . . . . . . . . . . . . . . . . 219Process for the input data set or file . . . . . . . . . . . . . . . 220Output for a data set or file . . . . . . . . . . . . . . . . . . . 220PRINTDS command syntax . . . . . . . . . . . . . . . . . . . 220PRINTDS command operands. . . . . . . . . . . . . . . . . . 222Default values for PRINTDS . . . . . . . . . . . . . . . . . . 231Mutually exclusive operands on PRINTDS . . . . . . . . . . . . . 232PRINTDS command return codes . . . . . . . . . . . . . . . . 233PRINTDS command examples . . . . . . . . . . . . . . . . . 233

PROFILE command . . . . . . . . . . . . . . . . . . . . . . 234PROFILE command syntax . . . . . . . . . . . . . . . . . . . 235PROFILE command operands . . . . . . . . . . . . . . . . . . 235PROFILE language setting notes . . . . . . . . . . . . . . . . . 239PROFILE foreground/background processing differences . . . . . . . . 239PROFILE command return codes . . . . . . . . . . . . . . . . 240PROFILE command examples. . . . . . . . . . . . . . . . . . 240

PROTECT command . . . . . . . . . . . . . . . . . . . . . . 241PROTECT command syntax . . . . . . . . . . . . . . . . . . 242PROTECT command operands . . . . . . . . . . . . . . . . . 242Passwords . . . . . . . . . . . . . . . . . . . . . . . . . 243

Types of access . . . . . . . . . . . . . . . . . . . . . . . 243Password data set . . . . . . . . . . . . . . . . . . . . . . 244PROTECT command return codes . . . . . . . . . . . . . . . . 244PROTECT command examples . . . . . . . . . . . . . . . . . 244

RECEIVE command . . . . . . . . . . . . . . . . . . . . . . 245RECEIVE command syntax . . . . . . . . . . . . . . . . . . . 246RECEIVE command operands. . . . . . . . . . . . . . . . . . 246RECEIVE command prompt parameters . . . . . . . . . . . . . . 247RECEIVE command prompt parameter syntax . . . . . . . . . . . . 248RECEIVE command prompt parameters . . . . . . . . . . . . . . 248RECEIVE command return codes . . . . . . . . . . . . . . . . 251



23/453

Receiving data . . . . . . . . . . . . . . . . . . . . . . . 251Data set organization . . . . . . . . . . . . . . . . . . . . . 251Receiving PDSE data sets . . . . . . . . . . . . . . . . . . . 252Receiving protected data sets . . . . . . . . . . . . . . . . . . 252Receiving enciphered data . . . . . . . . . . . . . . . . . . . 253Receiving data sets and messages with security labels . . . . . . . . 253RECEIVE command examples . . . . . . . . . . . . . . . . . 253

RENAME command . . . . . . . . . . . . . . . . . . . . . . 256RENAME command syntax . . . . . . . . . . . . . . . . . . . 256RENAME command operands . . . . . . . . . . . . . . . . . . 256RENAME command return codes . . . . . . . . . . . . . . . . 257RENAME command examples. . . . . . . . . . . . . . . . . . 257

RUN command . . . . . . . . . . . . . . . . . . . . . . . . 257RUN command syntax . . . . . . . . . . . . . . . . . . . . 257RUN command operands . . . . . . . . . . . . . . . . . . . 259Determining compiler type . . . . . . . . . . . . . . . . . . . 261RUN command return codes . . . . . . . . . . . . . . . . . . 261RUN command examples . . . . . . . . . . . . . . . . . . . 261

SEND command . . . . . . . . . . . . . . . . . . . . . . . . 261SEND command syntax . . . . . . . . . . . . . . . . . . . . 263

SEND command operands . . . . . . . . . . . . . . . . . . . 263SEND command return codes . . . . . . . . . . . . . . . . . . 265SEND command examples . . . . . . . . . . . . . . . . . . . 265

SMCOPY command . . . . . . . . . . . . . . . . . . . . . . 266SMCOPY command syntax . . . . . . . . . . . . . . . . . . . 266SMCOPY command operands . . . . . . . . . . . . . . . . . . 267SMCOPY command return codes . . . . . . . . . . . . . . . . 269SMCOPY command examples. . . . . . . . . . . . . . . . . . 269

SMFIND command . . . . . . . . . . . . . . . . . . . . . . . 269SMFIND command syntax . . . . . . . . . . . . . . . . . . . 269SMFIND command operands . . . . . . . . . . . . . . . . . . 270SMFIND command return codes . . . . . . . . . . . . . . . . . 271SMFIND command examples . . . . . . . . . . . . . . . . . . 271

SMPUT command . . . . . . . . . . . . . . . . . . . . . . . 271SMPUT command syntax . . . . . . . . . . . . . . . . . . . 271SMPUT command operands . . . . . . . . . . . . . . . . . . 271SMPUT command return codes . . . . . . . . . . . . . . . . . 272SMPUT command examples . . . . . . . . . . . . . . . . . . 272

STATUS command . . . . . . . . . . . . . . . . . . . . . . . 272STATUS command syntax . . . . . . . . . . . . . . . . . . . 272STATUS command operand . . . . . . . . . . . . . . . . . . 272STATUS command return codes . . . . . . . . . . . . . . . . . 273

SUBMIT command . . . . . . . . . . . . . . . . . . . . . . . 273SUBMIT command syntax . . . . . . . . . . . . . . . . . . . 274SUBMIT command operands . . . . . . . . . . . . . . . . . . 274

SUBMIT command return codes . . . . . . . . . . . . . . . . . 277SUBMIT command examples . . . . . . . . . . . . . . . . . . 277TERMINAL command . . . . . . . . . . . . . . . . . . . . . . 277

TERMINAL command syntax . . . . . . . . . . . . . . . . . . 278TERMINAL command operands . . . . . . . . . . . . . . . . . 278TERMINAL command return codes . . . . . . . . . . . . . . . . 281TERMINAL command examples . . . . . . . . . . . . . . . . . 281

TEST command . . . . . . . . . . . . . . . . . . . . . . . . 282TEST command syntax . . . . . . . . . . . . . . . . . . . . 283TEST command operands . . . . . . . . . . . . . . . . . . . 283TEST command return codes . . . . . . . . . . . . . . . . . . 285



24/453

TEST command examples . . . . . . . . . . . . . . . . . . . 285TEST subcommands (overview) . . . . . . . . . . . . . . . . . . 287TESTALLOCATE command . . . . . . . . . . . . . . . . . . . 289TESTAND subcommand . . . . . . . . . . . . . . . . . . . . 289

TESTAND subcommand syntax . . . . . . . . . . . . . . . . 289TESTAND subcommand operands . . . . . . . . . . . . . . . 289TESTAND subcommand examples . . . . . . . . . . . . . . . 291

Assignment of values function of TEST . . . . . . . . . . . . . . . 291Syntax of values function of TEST . . . . . . . . . . . . . . . . 292Operands of values function of TEST . . . . . . . . . . . . . . . 292Examples of values function of TEST . . . . . . . . . . . . . . . 294

TESTAT subcommand . . . . . . . . . . . . . . . . . . . . . 296TESTAT subcommand syntax . . . . . . . . . . . . . . . . . 297TESTAT subcommand operands . . . . . . . . . . . . . . . . 297TESTAT subcommand examples . . . . . . . . . . . . . . . . 298

TESTATTRIB command . . . . . . . . . . . . . . . . . . . . 300TESTCALL subcommand . . . . . . . . . . . . . . . . . . . . 300

TESTCALL subcommand syntax . . . . . . . . . . . . . . . . 300TESTCALL subcommand operands . . . . . . . . . . . . . . . 300TESTCALL subcommand examples . . . . . . . . . . . . . . . 301

TESTCANCEL command . . . . . . . . . . . . . . . . . . . . 302TESTCOPY subcommand . . . . . . . . . . . . . . . . . . . 302

TESTCOPY subcommand syntax . . . . . . . . . . . . . . . . 302TESTCOPY subcommand operands. . . . . . . . . . . . . . . 302TESTCOPY subcommand examples . . . . . . . . . . . . . . 303

TESTDELETE subcommand . . . . . . . . . . . . . . . . . . 305TESTDELETE subcommand syntax . . . . . . . . . . . . . . . 305TESTDELETE subcommand operand . . . . . . . . . . . . . . 305TESTDELETE subcommand examples. . . . . . . . . . . . . . 305

TESTDROP subcommand . . . . . . . . . . . . . . . . . . . 305TESTDROP subcommand syntax . . . . . . . . . . . . . . . . 305TESTDROP subcommand operand . . . . . . . . . . . . . . . 306TESTDROP subcommand examples . . . . . . . . . . . . . . 306

TESTEND subcommand . . . . . . . . . . . . . . . . . . . . 306TESTEND subcommand syntax . . . . . . . . . . . . . . . . 306

TESTEQUATE subcommand . . . . . . . . . . . . . . . . . . 307TESTEQUATE subcommand syntax . . . . . . . . . . . . . . . 307TESTEQUATE subcommand operands. . . . . . . . . . . . . . 307TESTEQUATE subcommand examples . . . . . . . . . . . . . 308

TESTEXEC command . . . . . . . . . . . . . . . . . . . . . 309TESTFREEMAIN subcommand . . . . . . . . . . . . . . . . . 309

TESTFREEMAIN subcommand syntax . . . . . . . . . . . . . . 309TESTFREEMAIN subcommand operands . . . . . . . . . . . . . 309TESTFREEMAIN subcommand examples. . . . . . . . . . . . . 310

TESTGETMAIN subcommand . . . . . . . . . . . . . . . . . . 310

TESTGETMAIN subcommand syntax . . . . . . . . . . . . . . 310TESTGETMAIN subcommand sperands . . . . . . . . . . . . . 311TESTGETMAIN subcommand examples . . . . . . . . . . . . . 311

TESTGO subcommand . . . . . . . . . . . . . . . . . . . . 311TESTGO subcommand syntax . . . . . . . . . . . . . . . . . 312TESTGO subcommand operands . . . . . . . . . . . . . . . . 312TESTGO subcommand examples. . . . . . . . . . . . . . . . 313

TESTHELP command . . . . . . . . . . . . . . . . . . . . . 313TESTLINK command . . . . . . . . . . . . . . . . . . . . . 313TESTLIST subcommand . . . . . . . . . . . . . . . . . . . . 313

TESTLIST subcommand syntax . . . . . . . . . . . . . . . . 313



25/453

TESTLIST subcommand operands . . . . . . . . . . . . . . . 313TESTLIST subcommand examples . . . . . . . . . . . . . . . 317

TESTLISTALC command . . . . . . . . . . . . . . . . . . . . 319TESTLISTBC command . . . . . . . . . . . . . . . . . . . . 319TESTLISTCAT command . . . . . . . . . . . . . . . . . . . . 319TESTLISTDCB subcommand . . . . . . . . . . . . . . . . . . 319

TESTLISTDCB subcommand syntax . . . . . . . . . . . . . . 320

TESTLISTDCB subcommand operands . . . . . . . . . . . . . 320TESTLISTDCB subcommand examples . . . . . . . . . . . . . 321

TESTLISTDEB subcommand . . . . . . . . . . . . . . . . . . 321TESTLISTDEB subcommand syntax. . . . . . . . . . . . . . . 321TESTLISTDEB subcommand operands . . . . . . . . . . . . . 321TESTLISTDEB subcommand examples . . . . . . . . . . . . . 322

TESTLISTDS command . . . . . . . . . . . . . . . . . . . . 322TESTLISTMAP subcommand . . . . . . . . . . . . . . . . . . 323

TESTLISTMAP subcommand syntax . . . . . . . . . . . . . . 323TESTLISTMAP subcommand sperands . . . . . . . . . . . . . 323TESTLISTMAP subcommand examples . . . . . . . . . . . . . 323

TESTLISTPSW subcommand . . . . . . . . . . . . . . . . . . 324TESTLISTPSW subcommand syntax . . . . . . . . . . . . . . 324

TESTLISTPSW subcommand operands . . . . . . . . . . . . . 324TESTLISTPSW subcommand examples . . . . . . . . . . . . . 325

TESTLISTTCB subcommand . . . . . . . . . . . . . . . . . . 325TESTLISTTCB subcommand syntax. . . . . . . . . . . . . . . 325TESTLISTTCB subcommand operands . . . . . . . . . . . . . 325TESTLISTTCB subcommand examples . . . . . . . . . . . . . 326

TESTLISTVP subcommand . . . . . . . . . . . . . . . . . . . 327TESTLISTVP subcommand syntax . . . . . . . . . . . . . . . 327TESTLISTVP subcommand examples . . . . . . . . . . . . . . 327

TESTLISTVSR subcommand . . . . . . . . . . . . . . . . . . 327TESTLISTVSR subcommand syntax. . . . . . . . . . . . . . . 327TESTLISTVSR subcommand operands . . . . . . . . . . . . . 327TESTLISTVSR subcommand examples . . . . . . . . . . . . . 328

TESTLOAD subcommand . . . . . . . . . . . . . . . . . . . 328TESTLOAD subcommand syntax . . . . . . . . . . . . . . . . 328TESTLOAD subcommand operands . . . . . . . . . . . . . . . 329TESTLOAD subcommand examples. . . . . . . . . . . . . . . 329

TESTOFF subcommand . . . . . . . . . . . . . . . . . . . . 329TESTOFF subcommand syntax . . . . . . . . . . . . . . . . 330TESTOFF subcommand operands . . . . . . . . . . . . . . . 330TESTOFF subcommand examples . . . . . . . . . . . . . . . 330

TESTOR subcommand . . . . . . . . . . . . . . . . . . . . 331TESTOR subcommand syntax . . . . . . . . . . . . . . . . . 331TESTOR subcommand operands . . . . . . . . . . . . . . . . 331TESTOR subcommand examples. . . . . . . . . . . . . . . . 332

TESTPROFILE command . . . . . . . . . . . . . . . . . . . 333TESTPROTECT command . . . . . . . . . . . . . . . . . . . 333TESTQUALIFY subcommand . . . . . . . . . . . . . . . . . . 334

TESTQUALIFY subcommand syntax . . . . . . . . . . . . . . 334TESTQUALIFY subcommand operands . . . . . . . . . . . . . 334TESTQUALIFY subcommand examples . . . . . . . . . . . . . 335

TESTRENAME command . . . . . . . . . . . . . . . . . . . 336TESTRUN subcommand . . . . . . . . . . . . . . . . . . . . 336

TESTRUN subcommand syntax . . . . . . . . . . . . . . . . 336TESTRUN subcommand operands . . . . . . . . . . . . . . . 336TESTRUN subcommand examples . . . . . . . . . . . . . . . 337



26/453

TESTSEND command . . . . . . . . . . . . . . . . . . . . . 337TESTSETVSR subcommand . . . . . . . . . . . . . . . . . . 338

TESTSETVSR subcommand syntax . . . . . . . . . . . . . . . 338TESTSETVSR subcommand operands. . . . . . . . . . . . . . 338TESTSETVSR subcommand examples. . . . . . . . . . . . . . 338

TESTSTATUS command . . . . . . . . . . . . . . . . . . . . 338TESTSUBMIT command . . . . . . . . . . . . . . . . . . . . 339

TESTTERMINAL command . . . . . . . . . . . . . . . . . . . 339TESTUNALLOC command . . . . . . . . . . . . . . . . . . . 339TESTWHERE subcommand. . . . . . . . . . . . . . . . . . . 339

TESTWHERE subcommand syntax . . . . . . . . . . . . . . . 339TESTWHERE subcommand operands . . . . . . . . . . . . . . 339TESTWHERE subcommand examples . . . . . . . . . . . . . . 340

TIME command . . . . . . . . . . . . . . . . . . . . . . . . 341TIME command syntax . . . . . . . . . . . . . . . . . . . . 342TIME command return code . . . . . . . . . . . . . . . . . . 342

TRANSMIT command . . . . . . . . . . . . . . . . . . . . . . 342TRANSMIT command syntax . . . . . . . . . . . . . . . . . . 342TRANSMIT command operands . . . . . . . . . . . . . . . . . 343TRANSMIT command return codes . . . . . . . . . . . . . . . . 347

Transmitting data sets . . . . . . . . . . . . . . . . . . . . . 347Transmitting data sets as messages . . . . . . . . . . . . . . . 348Transmitting messages . . . . . . . . . . . . . . . . . . . . 348Transmitting enciphered data . . . . . . . . . . . . . . . . . . 348Transmitting data sets and messages with security labels. . . . . . . . 349Logging function of TRANSMIT and RECEIVE . . . . . . . . . . . . 349NAMES data set function . . . . . . . . . . . . . . . . . . . 350Control section tags . . . . . . . . . . . . . . . . . . . . . 351Nicknames section tags . . . . . . . . . . . . . . . . . . . . 352TRANSMIT command examples . . . . . . . . . . . . . . . . . 354

TSOEXEC command . . . . . . . . . . . . . . . . . . . . . . 356TSOEXEC command syntax . . . . . . . . . . . . . . . . . . 357TSOEXEC command operand . . . . . . . . . . . . . . . . . . 357TSOEXEC command return codes . . . . . . . . . . . . . . . . 357TSOEXEC command examples . . . . . . . . . . . . . . . . . 357

TSOLIB command . . . . . . . . . . . . . . . . . . . . . . . 357Search order for load modules. . . . . . . . . . . . . . . . . . 358Further considerations. . . . . . . . . . . . . . . . . . . . . 359Command usage. . . . . . . . . . . . . . . . . . . . . . . 359Stacking load module and program object library requests . . . . . . . 360TSOLIB command syntax . . . . . . . . . . . . . . . . . . . 360TSOLIB command operands . . . . . . . . . . . . . . . . . . 361TSOLIB command return codes . . . . . . . . . . . . . . . . . 363TSOLIB command examples . . . . . . . . . . . . . . . . . . 363

VLFNOTE command . . . . . . . . . . . . . . . . . . . . . . 366

Changing data associated with a partitioned data set . . . . . . . . . 367VLFNOTE command syntax (partitioned data set) . . . . . . . . . . 367VLFNOTE command operands (partitioned data set) . . . . . . . . . 367VLFNOTE command examples (partitioned data set) . . . . . . . . . 368Changing non-PDS data . . . . . . . . . . . . . . . . . . . . 368VLFNOTE command syntax (non-PDS) . . . . . . . . . . . . . . 368VLFNOTE command operands (non-PDS) . . . . . . . . . . . . . 368VLFNOTE command examples (non-PDS) . . . . . . . . . . . . . 369VLFNOTE command return codes . . . . . . . . . . . . . . . . 369

WHEN command . . . . . . . . . . . . . . . . . . . . . . . 369WHEN command syntax . . . . . . . . . . . . . . . . . . . . 369



27/453

WHEN command operands . . . . . . . . . . . . . . . . . . . 369WHEN command return code . . . . . . . . . . . . . . . . . . 370WHEN command examples. . . . . . . . . . . . . . . . . . . 370

This section describes the functions and syntax of TSO/E commands and theirsubcommands. It includes:

v

The general format and syntax rules for the commandsv A description of each command. The commands are described in alphabetical

order.

v Examples of how to use commands and subcommands.

The commands are presented in alphabetical order. Subcommands are alsopresented in alphabetical order following the command to which they apply.

Introductory information about how to use TSO/E is described in z/OS TSO/EUsers Guide.

Using a TSO/E command

A command consists of a command name typically followed by one or moreoperands. Operands provide the specific information required to perform therequested operation. For example, operands for the RENAME command identify thedata set you want to rename:

RENAME OLDNAME NEWNAME

command name operand_1(old data set name)

operand_2(new data set name)

You can use two types of operands with the commands: positionaland keyword.

Positional operands

Positional operands follow the command name in a certain order. In the commanddescriptions within this book, the positional operands are shown in lowercasecharacters. For example,

EDIT reports.data

where reports.data is the data_set_namepositional operand with the EDITcommand.

When you enter a positional operand that is a list of several names or values, youmust enclose the list within parentheses. For example,

LISTDS (PARTS.DATA TEST.DATA)

Keyword operandsKeyword operands (keywords) are specific names or symbols that have a particularmeaning to the system. You can include keywords in any order following thepositional operands. In the command descriptions within this book, keywords areshown in uppercase characters.

You can specify values with some keywords. Enclose the value with parenthesesfollowing the keyword. For example, a typical keyword operand with a value is:

LINESIZE(integer)

Using a TSO/E Command

http://ikj4c230.pdf/http://ikj4c230.pdf/http://ikj4c230.pdf/http://ikj4c230.pdf/


28/453

Continuing this example, you need to select the number of characters that you wantto appear in a line and substitute that number for integerwhen you enter theoperand:

LINESIZE(80)

However, if you enter conflicting, mutually exclusive keywords, the last keyword youenter overrides the previous ones.

How to read the TSO/E command syntax describes the syntax notation for theTSO/E commands and subcommands.

How to read the TSO/E command syntax

Throughout this book, syntax of the whole command is described using thestructure defined later in this section.

Read the syntax diagrams from left to right, from top to bottom, following the path ofthe line.

Double arrows indicate the beginning and ending of a statement.

STATEMENT

If a statement syntax requires more than one line to be shown, single arrowsindicate their continuation.

STATEMENT ............ ............ ............ ............

............ ............ ............ ............ .........

Required items appear on the horizontal line (the main path).

STATEMENT required_item

Optional items appear below the main path.

STATEMENToptional_item

If you can choose from two or more items, they are stacked vertically.

v If you mustchoose one of the items, an item of the stack appears on the main

path.

STATEMENT required_choice_1required_choice_2

v If choosing one of the items is optional, the entire stack appears below the mainpath.

Using a TSO/E Command



29/453

STATEMENToptional_choice_1

optional_choice_2

An arrow returning to the left above the main line indicates an item that can berepeated.

STATEMENT repeatable_item

A repeat arrow above a stack indicates that you can make more than one choicefrom the stacked items, or repeat a single choice.

STATEMENT repeatable_item_1repeatable_item_2

Default values appear above the main path. For example, if you choose neitherchoice_2nor choice_3, choice_1 is assumed. (Defaults canbe coded for clarityreasons.)

STATEMENTchoice_1

choice_2

choice_3

If a syntax diagram becomes too large or too complex to be printed or shown,

fragments of it are shown below the main diagram as details.

STATEMENT required_variableoptional_parameter

FRAGMENT

FRAGMENT:

OPERANDoptional_choice_1aoptional_choice_1b

optional_choice_2aoptional_choice_2b



The previous syntax diagram is equivalent to the following diagram:

STATEMENT required_variableoptional_parameter

OPERAND

How to Read the TSO/E Command Syntax



30/453





Keywords appear in uppercase (for example, PARM1). They can be spelled exactlyas shown, but they can be in mixed or lower case. Variables appear in alllowercase letters (for example, parmx). They represent user-supplied names orvalues.

If punctuation marks, parentheses, arithmetic operators, or such symbols areshown, they must be entered as part of the syntax.

Abbreviating keyword operandsYou can enter keywords spelled exactly as they are shown or you can use anacceptable abbreviation. You can abbreviate any keyword by entering only thesignificant characters; that is, you must type as much of the keyword as is

necessary to distinguish it from the other keywords of the command orsubcommand. For example, the LISTBC command has four keywords:v MAILv NOMAILv NOTICESv NONOTICES

The abbreviations are:

M for MAIL (also MA and MAI)

NOM for NOMAIL (also NOMA and NOMAI)

NOT for NOTICES (also NOTI, NOTIC, and NOTICE)

NON for NONOTICES (also NONO, NONOT, NONOTI, NONOTIC, andNONOTICE)

Also, the DELETE and LISTCAT commands allow unique abbreviations for some oftheir keywords. The abbreviations are shown with the syntax and operanddescriptions of DELETE and LISTCAT.

CommentsYou can include comments in a TSO/E command anywhere a blank might appear.To include a comment, start with delimiter /*. If you want to continue the commandafter the comment, close the comment with delimiter */.

listd (data_set_list) /* my data sets

or

listd /* my data sets */ (data_set_list)

You do not need to end a comment with */ if the comment is the last thing on theline. Ending a comment with */ is a convention, not a requirement here. Commentsare most useful in CLISTs.



|

|

|

|


31/453

Line continuation

CAUTION:A plus sign causes leading delimiters to be removed from the continuation

line.

When it is necessary to continue to the next line, use a plus or minus sign as thelast character of the line you want to continue.

list (data_set_list) /* this is a list of my -active data sets */

or

alloc dataset(out.data) file(output) new +space(10,2) tracks release

Note: If you are using REXX commands and want to continue to the next line, theplus or minus sign does not work. You must use the comma.

The following example shows how to use the comma with the REXX command

(PUSH), to continue to the next line. The comma must be outside the quotationmarks.

/* REXX * test ACCOUNT */x = Outtrap("var.")PUSH ENDPUSH ADD (NEWUSER * * TPROC),

UNIT(SYSTS),SIZE(4000)

Address TSO "ACCOUNT"x = Outtrap("OFF")Say RC from account was: rcDo i=1 to var.0 /* loop through all messages */Say var.i /* display each message */

End

To continue a line that contains a comment, use a continuation character after thecomment:

allocate dataset(my.text) /* data set name */ +new volume(tsomar2)

DelimitersWhen you type a command, you must separate the command name from the firstoperand by one or more blanks. You must separate operands by one or moreblanks or a comma. Do not use a semicolon as a delimiter because any characteryou enter after a semicolon is ignored. For example, if you use a blank or a commaas a delimiter, you can type the LISTBC command as follows:

LISTBC NOMAIL NONOTICES

LISTBC NOMAIL,NONOTICESLISTBC NOMAIL NONOTICES

When creating (or updating) a CLIST, do not use any of the following as a delimiter:v The special characters @, $, or #v A single quotev A numberv A blankv A tabv A commav A semicolon




32/453

v A parenthesisv An asterisk

Note: When entering commands under ISPF or Program Control Facility (PCF), donot use the ISPF or PCF command delimiter character that your installationhas set for these facilities. The default delimiter character for each ISPF andPCF command is the semicolon (;), but your installation can specify a

different delimiter character.

Using the HELP command

Use the HELP command to receive all the information about the system on how touse any TSO/E command. The requested information is displayed on your terminal.

Explanations of commandsTo receive a list of all the TSO/E commands in the SYS1.HELP data set along witha description of each, enter the HELP command as follows:

help

You can place information about installation-written commands in the SYS1.HELPdata set. You can also get all the information available about a specific command inSYS1.HELP by entering the specific command name as an operand on the HELPcommand, as follows:

help ALLOCATE

where ALLOCATE is the command name.

Syntax interpretation of HELP informationThe syntax notation for the HELP information is different from the syntax notationpresented in this book because it is restricted to characters that are displayed onyour terminal. You can get the syntax interpretation by entering the HELP command

as follows:help help

Explanations of subcommandsWhen HELP exists as a subcommand, you can use it to obtain a list ofsubcommands or additional information about a particular subcommand. The syntaxof HELP as a subcommand is the same as the HELP command.

Using commands for VSAM and Non-VSAM data sets

Access Method Services is a multi-function service program that primarilyestablishes and maintains Virtual Storage Access Method (VSAM) data sets.

Table 1 shows recommended commands, by function, for VSAM and non-VSAMdata sets. Numbers indicate order of preference. Licensed program commands areidentified with an asterisk (*). For commands not covered in this book, see z/OSDFSMS Access Method Services for Catalogs.

Table 1. Commands preferred for VSAM/Non-VSAM data sets

Function Non-VSAM VSAM

Build lists of attributes ATTRIB (None)




33/453

Table 1. Commands preferred for VSAM/Non-VSAM data sets (continued)

Function Non-VSAM VSAM

Allocate new DASD space ALLOCATE DEFINE orALLOCATE

Connect data set to terminal ALLOCATE ALLOCATE

List names of allocated (connected) data sets LISTALC LISTALC

Modify passwords PROTECT DEFINE, ALTERList attributes of one or more objects 1. LISTDS,2. LISTCAT

1. LISTCAT,2. LISTDS

List names of cataloged data sets (limit by type) LISTCAT LISTCAT

List names of cataloged data sets (limit by namingconvention)

LISTDS LISTDS

Catalog data sets 1. DEFINE,2. ALLOCATE

DEFINE

List contents of data set EDIT, LIST* PRINT

Rename data set RENAME ALTER

Delete data set DELETE DELETE

Copy data set COPY* REPRO

TSO/E commands and subcommands

TSO/E commands which require a data set name (for example, Edit, DELete, XMIT)first search the current allocations to see if the data set is already allocated to theTSO/E session. If the data set name is already allocated, it will be used by thecommand. If the data set name is not allocated, it will be allocated based on thestandard catalog search order. Therefore, if a data set is desired that is notcataloged, you must use the ALLOCATE command to allocate it to the TSO/Esession (see ALLOCATE command on page 17). This data set will then be usedby all subsequent commands that use this data set name as one of the parameters.Conversely, if an uncataloged data set is allocated to the TSO/E session with thesame name as a cataloged data set, and the cataloged data set is desired, you

must first use the FREE command for the uncataloged data set so that the standardcatalog search order will be used to find the cataloged data set.

Summary of TSO/E commands

Table 2. Summary of the TSO/Ecommands

Command Function

ALLOCATE Dynamically allocates data sets.

ALTLIB Defines alternative application-level libraries of REXX EXECs or CLISTs.

ATTRIB Builds a list of attributes for non-VSAM data sets.

CALL Loads and executes a program.

CANCEL Ends the processing of batch jobs submitted at your terminal.

DELETE Deletes data set entries or members of a partitioned data set.EDIT Creates, modifies, stores, submits, retrieves, and deletes data sets. See

command definitions for definitions of EDIT subcommands.

END Ends a CLIST.

EXEC Executes a CLIST or REXX exec.

EXECUTIL Changes various characteristics that control how REXX execs run in theTSO/E address space only.

FREE Releases previously allocated data sets, changes the output of a SYSOUTdata set, deletes attribute lists, or changes data set disposition.

HELP Gets information about the function, syntax, and operands of commandsand subcommands and information about certain messages.




34/453

Table 2. Summary of the TSO/E commands (continued)

Command Function

LINK Invokes the linkage editor service program.

LISTALC Lists data sets that are currently allocated to the TSO/E session.

LISTBC Displays messages of general interest.

LISTCAT Lists entries from a catalog by name or entry type.

LISTDS Displays attributes of data sets.LOADGO Loads a compiled or assembled program into real storage and begins

execution.

LOGOFF Ends your terminal session.

LOGON Starts your terminal session.

MVSSERV Starts a TSO/E Enhanced Connectivity Facility session between an IBMPersonal Computer and a host computer running TSO/E MVS.

OUTDES Creates or reuses dynamic output descriptors.

OUTPUT Directs output from a job to your terminal or to a specific data set; deletesthe output, changes output class, routes output to a remote workstation, orreleases the output for a job for printing by the subsystem.

PRINTDS Formats and prints data sets on any printer defined to JES.

PROFILE Changes or lists your user profile.

PROTECT Prevents unauthorized access to your non-VSAM data sets.RECEIVE Retrieves transmitted files and restore them to their original format.

RENAME Changes the name of a non-VSAM cataloged data set, changes themember name of a partitioned data set, or creates an alias for a partitioneddata set member.

RUN Compiles, loads, and executes the source statements in a data set.

SEND Sends a message to another terminal user or to the system operator.

SMCOPY Copies all or part of a stream or data set to another stream or data set.

SMFIND Locates a string of characters in a stream.

SMPUT Places a string of characters in a stream.

STATUS Displays the status of a job.

SUBMIT Submits one or more batch jobs for processing.

TERMINAL Lists or changes operating characteristics of your terminal.

TEST Tests a program or command processor written in Assembler language.TIME Displays CPU and session time, total service units used, local time of day

and date.

TRANSMIT Sends information, such as a message or a copy of information in a dataset, to another user in the network.

TSOEXEC Invokes an authorized command from an unauthorized environment.

TSOLIB Dynamically links to different versions of load module libraries from within ausers TSO/E session.

VLFNOTE Notifies VLF that a change has been made to a partitioned data set or anon-partitioned data set.

WHEN Tests return codes from programs invoked from an immediately precedingCALL or LOADGO command, and to take prescribed action if the returncode meets a specified condition.

Note: Except for the DELETE and LISTCAT commands, TSO/E does not supportgeneration data group (GDG) data sets.

Summary of TSO/E Commands



35/453

ALLOCATE command

Use the ALLOCATE command or the ALLOCATE subcommand of EDIT (thesubcommands function and syntax are identical to the ALLOCATE command) toallocate dynamically the VSAM and non-VSAM data sets, and UNIX files requiredby a program that you intend to execute. Each UNIX file system data set containszero or more UNIX files.

Each UNIX file system data set has a 44-byte data set name and must becapitalized and cataloged. A UNIX file has a mixed-case name of up to 250characters.

There is no documented API for an UNIX file system data set. Users can accessUNIX files with BSAM, QSAM, VSAM and UNIX calls.

You can specify data set attributes for non-VSAM data sets that you intend toallocate dynamically in several ways:

v Use the LIKE operand to obtain the attributes from an existing model data set (adata set that must be cataloged) whose data set attributes you want to use. You

can override model data set attributes by explicitly specifying the desiredattributes on the ALLOCATE command.

v Identify a data set and describe its attributes explicitly on the ALLOCATEcommand.

v Use the ATTRIB command to build a list of attributes. During the remainder ofyour terminal session, you can have the system refer to this list for data setattributes by specifying the USING operand when you enter the ALLOCATEcommand. The ALLOCATE command converts the attributes into the data controlblock (DCB) operands for data sets being allocated. If you code DCB attributes inan attribute-list and you refer to the attribute-list using the USING operand on theALLOCATE command, any DCB attribute you code on the ALLOCATE commandis ignored.

v

With the Storage Management Subsystem (SMS) installed and active, use theDATACLAS operand. Your storage administrator might provide default data setattributes through the automatic class selection (ACS) routine. Using DATACLASto define the data class for the data set makes specifying all the attributesunnecessary.

In this book, with SMS indicates that SMS is installed and is active. Without SMSindicates that SMS is not installed. Requesting space, in terms of a quantity oflogical records, is device-independent and is particularly useful in conjunction with asystem-determined BLKSIZE. This space can be obtained by omitting the BLKSIZEoperand and coding LRECL, RECFM, and DSORG, or acquiring these from SMSDATACLAS.

Data sets with SMSIf your installation has the Storage Management Subsystem (SMS), and it is active,SMS allows you to more easily define new data sets by managing storagerequirements for you. The storage administrator at your installation determines thedata sets that are to be managed by SMS. The administrator writes the automaticclass selection (ACS) routine that SMS uses to assign definitions or classes to anew data set. See SMS classes.

SMS can manage the following types of data sets:v Physical sequential data sets

ALLOCATE Command



36/453

v Partitioned data setsv VSAM data setsv Generation data group (GDG) data setsv Temporary data setsv Virtual input output (VIO) data sets

SMS does notmanage the following types of data sets:

v Tape data setsv ISAM data setsv Sysout data setsv Subsystem data setsv TSO/E data sets coming from or going to a terminalv In-stream data sets

SMS classesWith SMS, a new data set can have one or more of the following three classes:

v Data classcontains the data set attributes related to the allocation of the dataset, such as LRECL, RECFM, SPACE, and TRACKS.

v Storage classcontains performance and availability attributes related to the

storage occupied by the data set. A data set that has a storage class assigned toit is defined as an SMS-managed data set.

v Management classcontains the data set attributes related to the migration andbackup of the data set, such as performed by DFSMShsm, and the expirationdate of the data set. A management class can be assigned only to a data set thatalso has a storage class assigned.

All of the preceding classes are defined by the storage administrator at yourinstallation. The administrator writes the automatic class selection (ACS) routinesthat SMS uses to assign the classes to a new data set.

The DATACLAS, MGMTCLAS, and STORCLAS operands of the ALLOCATEcommand simplify the process of allocating a new data set. For example, assigning

the DATACLAS operand to a data set keeps you from having to specify all theattributes of the data set on the ALLOCATE command. If you assign a storage class(STORCLAS) to a data set, you do not have to specify a volume serial number(VOLUME) or a unit type (UNIT).

If you do not specify DATACLAS, MGMTCLAS, and STORCLAS or the overridingattributes (DSORG, RECFM, LRECL, and so forth), the system assumes thedefaults that the storage administrator defined through the ACS routines. The ACSroutines can either change or retain the specified data set attributes. You canspecify both a class attribute and an overriding attribute, such as DATACLAS andSPACE. The system uses SPACE as the storage value and the allocation attributesassociated with the name specified on DATACLAS.

Note: You must explicitly allocate a new SMS-managed data set with a dispositionof NEW.

Allocating non-SMS-managed data setsWith SMS, you can specify DATACLAS to allocate non-SMS-managed data sets.You cannot, however, use the STORCLAS and MGMTCLAS operands. STORCLASand MGMTCLAS determine whether a data set is managed by SMS.

ALLOCATE Command



37/453

Allocating z/OS UNIX data setsFor z/OS UNIX, you can specify the following operands: PATH, PATHDISP,PATHMODE, PATHOPTS, DSNTYPE(HFS), and DSNTYPE(PIPE). For moreinformation, see z/OS TSO/E Users Guide.

ALLOCATE command syntax

ALLOCATEALLOC

DATASET ( * )DSNAME FILE (name)

DDNAMEdsname

DUMMYFILE (name)DDNAME DATASET ( * )

DSNAME

dsname

DUMMY

OLDSHRMODNEWSYSOUT

(class)

DATACLAS(data_class_name)

MGMTCLAS(management_class_name) STORCLAS(storage_class_name)

VOLUME(serial_list)

SPACE(quantity ) BLOCK(value)

,increment AVBLOCK(value)TRACKSCYLINDERS

AVGREC( U )

KM

BLKSIZE(value) DIR(integer)

ALTFILE(name) DEST( destination )

destination.user_idREUSE

ALLOCATE Command

http://ikj4c230.pdf/http://ikj4c230.pdf/http://ikj4c230.pdf/


38/453

NOHOLD

HOLD UNIT(type) UCOUNT(count)PARALLEL

LABEL(type)

ACCODE(access_code) POSITION(sequence_no.) MAXVOL(count)

PRIVATE VSEQ(vol_seq_no.) LIKE(model_dsname)

USING(attr_list_name)

REFDD(file_name) SECMODEL(profile_name )

,GENERICRELEASE

ROUND KEEP

DELETE

CATALOGUNCATALOG

BUFL(buffer_length)BUFNO(number_of_buffers)

LRECL( logical_record_length )

X

nnnnnK

NCP(1)

NCP(no._of_channel_programs)

INPUTOUTPUT

EXPDT(year_day)RETPD(no._of_days)

BFALN( F )D

,

OPTCD( A )BCEFHJ

QRTWZ

EROPT( ACC )SKPABE

BFTEK( S )EAR

ALLOCATE Command



39/453

,

RECFM( A )BDFMSTUV

DIAGNS(TRACE) LIMCT(search_number)

BUFOFF( block_prefix_length )

LDSORG( DA )

DAUPOPOUPSPSU

DEN( 0 )

1234

NOCOMPTRTCH( C )

E COMPTET

KEYLEN(bytes)

KEYOFF(offset)

RECORG( ES )

KSLSRR

PROTECT

COPIES(nnn ),

, ( group_value )

BURSTNOBURST

CHARS( , table_name )

FLASH(overlay_name )copies

MODIFY(module_name )

,trcFCB(image_id )

,ALIGN,VERIFY

FORMS(forms_name)

OUTDES( output_descriptor_name )

ALLOCATE Command



40/453

SPIN( UNALLOC )

NOSEGMENT(page_count)

DSNTYPE( LIBRARY )

PDSHFSPIPELARGEBASICEXTREQEXTPREF

UCS(universal_character_set_name)

WRITER(external_writer_name)

PATH( /pathname )

KEEP ,KEEPPATHDISP( )DELETE ,DELETE

PATHMODE( file_access_attribute ) PATHOPTS( file_option )

BINARY

FILEDATA( TEXT )RLS( NRI )

CR

ALLOCATE command operands

DATASET(dsname | *) | DSNAME(dsname | *)specifies the name or a list of names of the data sets that are to be allocated. Ifa list of data set names is entered, ALLOCATE allocates and concatenatesnon-VSAM data sets. The data set name must include the descriptive(rightmost) qualifier and can contain a member name in parentheses.

If you specify a password, you are not prompted for it when you open anon-VSAM data set.

If you want to allocate a file to the terminal for input or output, only the followingoperands are processed:

ALLOCATE DA(*) FILE, DDNAME, BLOCK, BLKSIZE, USING

If you allocate more than one data set to your terminal, the block size and otherdata set characteristics, which default on the first usage, are also used for allother data sets. This happens for input or output. Use the ATTRIB commandand the USING operand of ALLOCATE to control the data set characteristics.

v Data sets residing on the same physical tape volume cannot be allocatedconcurrently.

v The following items should be noted when using the concatenate function:

ALLOCATE Command



41/453

The data sets specified in the list must be cataloged. You can use theCATALOG operand of either the ALLOCATE or FREE commands tocatalog a data set.

The maximum number of data sets that you can concatenate is 255. Thismaximum applies to sequential data sets. For more information about themaximum number of partitioned data sets that you can concatenate, seez/OS DFSMS Using Data Sets. The data sets to be concatenated must all

have the same record format (RECFM). If you omit the BLKSIZE operandfrom the concatenation statement, the system uses the block size of thefirst data set. If the data sets have different block sizes, you must specifythe data set with the largest block size first. In most situations the accessmethod automatically handles block size differences. For more informationsee z/OS DFSMS Using Data Sets.

The data set group is concatenated. You must free it to deconcatenate it.The file name specified for the FILE or DDNAME operand on theALLOCATE command must be the same as that specified for the FILE orDDNAME operand on the FREE command.

The system ignores all operands except for DATASET/DSNAME,FILE/DDNAME, and status operands. The following DCB attribute

operands are allowed when concatenating data sets:BLKSIZE INPUT EROPT BUFOFF USINGBUFL OUTPUT BFTEK DENBUFNO BFALN DIAGNS TRTCHNCP OPTCD LIMCT KEYLEN

v To allocate a member of a generation data group, specify the fully-qualifieddata set name, including the generation number.

v The ALLOCATE command verifies the existence of a data set on thespecified volume(s) only when the VOLUME operand is also specified.

v When you invoke ALLOCATE to perform dsname dynamic allocation, anallocation environment already exists for your request. It consists of theallocation requests, made through your JCL or internal dynamic allocation,

that have not yet been deallocated. These resources are considered to beexisting allocations, and are considered first in the attempt to fill yourALLOCATE requests.

If possible, ALLOCATE will use an existing allocation to satisfy your dsnameallocation request. Although some parameters can be changed if necessary,the request and the existing allocation must match according to severalcriteria before the allocation can be selected to satisfy your request.

For more information about this criteria and using an existing allocation, seez/OS MVS Programming: Authorized Assembler Services Guide.

DUMMYspecifies that no devi

t so command reference

Documents