z/OS

MVS System CommandsVersion 2 Release 3

SA38-0666-30

IBM

NoteBefore using this information and the product it supports, read the information in Notices on page 997.

This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modificationsuntil otherwise indicated in new editions.

Last updated: April 18, 2018

Copyright IBM Corporation 1988, 2017.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . xi

Tables . . . . . . . . . . . . . . . xiii

About this information . . . . . . . . xvWho should use this information . . . . . . . xvHow to use this information. . . . . . . . . xvz/OS information . . . . . . . . . . . . xv

How to send your comments to IBM xviiIf you have a technical problem . . . . . . . xvii

Summary of changes . . . . . . . . xixSummary of changes in z/OS Version 2 Release 3(V2R3) . . . . . . . . . . . . . . . . xixSummary of changes for Version 2 Release 2 (V2R2),as updated December 2016 . . . . . . . . . xxSummary of changes for Version 2 Release 2(V2R2), as updated June 2016 . . . . . . . . xxiSummary of changes for Version 2 Release 2(V2R2), as updated March 2016 . . . . . . . xxiSummary of changes for Version 2 Release 2(V2R2), as updated December 2015 . . . . . . xxiSummary of changes in z/OS Version 2 Release 2(V2R2) . . . . . . . . . . . . . . . xxiiSummary of changes for z/OS Version 2 Release 1(V2R1), as updated February 2015 . . . . . . xxivSummary of changes for z/OS Version 2 Release 1(V2R1), as updated March 2014 . . . . . . . xxvz/OS Version 2 Release 1 summary of changes . . xxv

Chapter 1. System operations . . . . . 1Starting, loading, and initializing the system. . . . 2

Starting the system . . . . . . . . . . . 2Preparing the system hardware . . . . . . . 3Loading the system software . . . . . . . . 3Initializing the system software . . . . . . . 7Logging on to the system . . . . . . . . . 9Starting and specifying parameters for the jobentry subsystem . . . . . . . . . . . . 10

Controlling the system. . . . . . . . . . . 10Displaying current system status . . . . . . 11Displaying the status of devices and availabilityof paths . . . . . . . . . . . . . . 11Sending commands to systems in a sysplex. . . 12Using commands that have sysplex scope . . . 12Sharing system commands . . . . . . . . 15Setting the time and changing the systemparameters . . . . . . . . . . . . . 19Using the system restart function . . . . . . 19Responding to IEA502A . . . . . . . . . 20Responding to BLW004A . . . . . . . . . 21Activating a workload management servicepolicy . . . . . . . . . . . . . . . 21

Controlling time-sharing . . . . . . . . . . 22Controlling jobs . . . . . . . . . . . . . 22

Starting a job . . . . . . . . . . . . . 22Stopping a job . . . . . . . . . . . . 22Cancelling a job . . . . . . . . . . . . 23Passing information to a job . . . . . . . . 23Restarting a job . . . . . . . . . . . . 23Deferred restart . . . . . . . . . . . . 24

Controlling started tasks . . . . . . . . . . 25Controlling system information recording . . . . 25

System management facilities . . . . . . . 26System trace . . . . . . . . . . . . . 27The generalized trace facility . . . . . . . 27Master trace . . . . . . . . . . . . . 27Component trace . . . . . . . . . . . 27Logrec recording medium . . . . . . . . 27

Controlling automatic tape switching . . . . . . 28Defining automatically switchable devices . . . 28Displaying information about automaticallyswitchable devices . . . . . . . . . . . 29

Interacting with system functions . . . . . . . 29Device allocation . . . . . . . . . . . 30Hot I/O detection . . . . . . . . . . . 32Device boxing . . . . . . . . . . . . 32

Command flooding. . . . . . . . . . . . 36Class M1 commands . . . . . . . . . . 36Class M2 commands . . . . . . . . . . 37Class M3 commands . . . . . . . . . . 39Class C1 commands . . . . . . . . . . 39Class C2 commands . . . . . . . . . . 39Class C3 commands . . . . . . . . . . 39Inline commands . . . . . . . . . . . 39

Setting up hardware event data collection . . . . 40Accessing the output from a hardware event datacollection run. . . . . . . . . . . . . . 43

Interpreting the z/OS UNIX system servicesoutput files . . . . . . . . . . . . . 45

HISSERV service overview . . . . . . . . . 52Bypassing HIS to exploit the CPU MeasurementFacility . . . . . . . . . . . . . . . . 52Responding to failing devices . . . . . . . . 53Quiescing the system . . . . . . . . . . . 53Stopping the system . . . . . . . . . . . 54Recovery from hardware problems . . . . . . 54

Hardware problems . . . . . . . . . . 54Information provided with machine checks . . . 55CPU errors . . . . . . . . . . . . . 55Service processor damage . . . . . . . . 58Storage errors . . . . . . . . . . . . 59Channel subsystem errors . . . . . . . . 60I/O device errors . . . . . . . . . . . 64Diagnosing problems in a switched fabric . . . 73Additional recovery actions . . . . . . . . 87

Copyright IBM Corp. 1988, 2017 iii

Chapter 2. System Reconfiguration . . 89Dynamic I/O configuration . . . . . . . . . 89Logical and physical reconfiguration . . . . . . 90Reconfiguration support according to processortypes . . . . . . . . . . . . . . . . 90

Uniprocessor (UP) . . . . . . . . . . . 90Multiprocessor (MP) . . . . . . . . . . 90

Reconfiguring a central processor . . . . . . . 91Actions to reconfigure a central processor offline 91Reconfiguring a central processor with an ICRF 91Actions to bring online a central processor andits ICRF . . . . . . . . . . . . . . 92Removing the last ICRF . . . . . . . . . 92Actions to take offline a central processor and itsICRF . . . . . . . . . . . . . . . 92

Reconfiguring central storage . . . . . . . . 92Physical view of central storage . . . . . . 93Specifying the RSU parameter . . . . . . . 93

Reconfiguring channel paths. . . . . . . . . 96Actions to reconfigure channel paths . . . . . 97

Reconfiguring I/O devices . . . . . . . . . 97Reconfiguring a coupling facility . . . . . . . 98

Chapter 3. z/OS operator consoleoperations . . . . . . . . . . . . . 99Console characteristics and operations . . . . . 99

General characteristics of display consoles . . . 99Operations on display consoles in full-capabilitymode . . . . . . . . . . . . . . . 104Handling consoles in error conditions . . . . 113Placing a console in offline status. . . . . . 117Interchanging your consoles on a control unit 117

Defining and changing console characteristics . . 118Using operator commands to changeCONSOLxx statements . . . . . . . . . 118Changing console characteristics . . . . . . 122Controlling system messages and commands 137Defining program function keys (PFKs) . . . 143Processing hardcopy . . . . . . . . . . 146

Chapter 4. MVS system commandsreference . . . . . . . . . . . . . 151Command syntax notation . . . . . . . . . 165

How to read syntax conventions . . . . . . 165System command formats . . . . . . . . . 166

Typical format . . . . . . . . . . . . 166A second format . . . . . . . . . . . 167

ACTIVATE command . . . . . . . . . . 168Restrictions . . . . . . . . . . . . . 168Syntax. . . . . . . . . . . . . . . 168Parameters . . . . . . . . . . . . . 168

CANCEL command . . . . . . . . . . . 172Syntax. . . . . . . . . . . . . . . 173Parameters . . . . . . . . . . . . . 173

CHNGDUMP command. . . . . . . . . . 177Dump options and modes . . . . . . . . 177Changing the dump mode and options . . . . 178Scope in a sysplex . . . . . . . . . . . 178Syntax variations for CHNGDUMP . . . . . 178

Removing options from or resetting the systemdump options lists . . . . . . . . . . 179Parameters . . . . . . . . . . . . . 179Options for SDUMP, SYSABEND, SYSUDUMP,and SYSMDUMP . . . . . . . . . . . 181Resetting dump mode to add and the dumpoptions to initial values . . . . . . . . . 186Example: How CHNGDUMP commands affectdump modes and options . . . . . . . . 187Setting the dump modes and options . . . . 189

CMDS command . . . . . . . . . . . . 199Syntax. . . . . . . . . . . . . . . 200Parameters . . . . . . . . . . . . . 200

CONFIG command . . . . . . . . . . . 202Syntax. . . . . . . . . . . . . . . 203Reconfiguring the system directly . . . . . 203Reconfiguring the system with a CONFIGxxparmlib member . . . . . . . . . . . 215Reconfiguring the system in response to aconfiguration display . . . . . . . . . . 216

CONTROL command. . . . . . . . . . . 217Scope in a sysplex . . . . . . . . . . . 218Syntax. . . . . . . . . . . . . . . 218Changing out of line display area specifications 219Deleting retained action messages . . . . . 219Halting the printing or the display of a statusdisplay . . . . . . . . . . . . . . 221Controlling displays in areas . . . . . . . 221Removing information from the screen . . . . 222Activating, deactivating, or displaying the statusof the action message retention facility . . . . 224Changing or displaying the number of allowedWTL SYSLOG buffers . . . . . . . . . 224Changing or displaying the number of allowedWTO and WTOR message buffers . . . . . 225Changing the time the system waits for ROUTEcommand responses . . . . . . . . . . 226Increasing the maximum number of reply IDs 227Changing or displaying the status of WTOinstallation exit IEAVMXIT . . . . . . . . 227Displaying the SMCS APPLID of the currentsystem and VTAM generic resource name forSMCS . . . . . . . . . . . . . . . 228Setting the APPLID of the system . . . . . 229Setting or turning off the VTAM genericresource name for SMCS . . . . . . . . 229Changing a PFK definition . . . . . . . . 230Deleting message queues . . . . . . . . 232Changing or displayin