z/OS 

MVS System Commands

SA22-7627-13
z/OS 

MVS System Commands

SA22-7627-13
 Note
Before using this information and the product it supports, be sure to read the general information under Notices on page
B-1.

Fourteenth Edition, April 2006

This is a major revision of SA22-7627-12.
This edition applies to Version 1 Release 7 of z/OS (5694-A01), Version 1 Release 7 of z/OS.e (5655-G52), and to
all subsequent releases and modifications until otherwise indicated in new editions.
IBM welcomes your comments. A form for readers comments may be provided at the back of this document, or you
may address your comments to the following address:
International Business Machines Corporation
Department 55JA, Mail Station P384
2455 South Road
Poughkeepsie, NY 12601-5400
United States of America

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

FAX (Other Countries):
Your International Access Code +1+845+432-9405

IBMLink (United States customers only): IBMUSM10(MHVRCFS)

Internet e-mail: [email protected]
World Wide Web: 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 any
way it believes appropriate without incurring any obligation to you.
Copyright International Business Machines Corporation 1988, 2006. All rights reserved.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

About this document . . . . . . . . . . . . . . . . . . . . . xvii

Who should use this document . . . . . . . . . . . . . . . . . . . xvii
How to use this document . . . . . . . . . . . . . . . . . . . . xvii
Where to find more information . . . . . . . . . . . . . . . . . . xvii
Information updates on the web . . . . . . . . . . . . . . . . . xvii
Using LookAt to look up message explanations . . . . . . . . . . . xviii
Using IBM Health Checker for z/OS . . . . . . . . . . . . . . . . xviii

Summary of changes . . . . . . . . . . . . . . . . . . . . . . xix

Chapter 1. System Operations . . . . . . . . . . . . . . . . . . 1-1

Starting, Loading, and Initializing the System . . . . . . . . . . . . . 1-2
Starting the System . . . . . . . . . . . . . . . . . . . . . . 1-2
Preparing the System Hardware . . . . . . . . . . . . . . . . . 1-2
Loading the System Software . . . . . . . . . . . . . . . . . . 1-3
Logging On to the System . . . . . . . . . . . . . . . . . . . 1-6
Initializing the System Software . . . . . . . . . . . . . . . . . 1-7
Starting and Specifying Parameters for the Job Entry Subsystem . . . . . 1-9
Controlling the System . . . . . . . . . . . . . . . . . . . . . . 1-9
Displaying Current System Status . . . . . . . . . . . . . . . . 1-10
Displaying the Status of Devices and Availability of Paths . . . . . . . 1-10
Communicating Among Several Consoles . . . . . . . . . . . . . 1-11
Sending Commands to Systems in a Sysplex . . . . . . . . . . . . 1-11
Using Commands That Have Sysplex Scope . . . . . . . . . . . . 1-11
Sharing System Commands . . . . . . . . . . . . . . . . . . 1-14
Setting the Time and Changing the System Parameters . . . . . . . . 1-18
Using the System Restart Function . . . . . . . . . . . . . . . . 1-18
Responding To IEA502A . . . . . . . . . . . . . . . . . . . 1-19
Responding To BLW004A . . . . . . . . . . . . . . . . . . . 1-20
Activating a Workload Management Service Policy . . . . . . . . . . 1-20
Switching Workload Management Modes . . . . . . . . . . . . . 1-21
Controlling Time-Sharing . . . . . . . . . . . . . . . . . . . . 1-21
Controlling Jobs . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Starting a Job . . . . . . . . . . . . . . . . . . . . . . . 1-22
Stopping a Job . . . . . . . . . . . . . . . . . . . . . . . 1-22
Cancelling a Job . . . . . . . . . . . . . . . . . . . . . . 1-22
Passing Information to a Job . . . . . . . . . . . . . . . . . . 1-22
Restarting a Job . . . . . . . . . . . . . . . . . . . . . . 1-22
Deferred Restart . . . . . . . . . . . . . . . . . . . . . . 1-23
Controlling Started Tasks . . . . . . . . . . . . . . . . . . . . 1-24
Controlling System Information Recording . . . . . . . . . . . . . . 1-25
System Management Facilities . . . . . . . . . . . . . . . . . 1-25
System Trace . . . . . . . . . . . . . . . . . . . . . . . 1-26
The Generalized Trace Facility . . . . . . . . . . . . . . . . . 1-26
Master Trace . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Component Trace . . . . . . . . . . . . . . . . . . . . . . 1-27
Logrec Recording Medium . . . . . . . . . . . . . . . . . . . 1-27
Controlling Automatic Tape Switching . . . . . . . . . . . . . . . . 1-27
Defining Automatically Switchable Devices . . . . . . . . . . . . . 1-29

Copyright IBM Corp. 1988, 2006 iii

 Displaying Information About Automatically Switchable Devices . . . . . 1-29
Interacting with System Functions . . . . . . . . . . . . . . . . . 1-30
Device Allocation . . . . . . . . . . . . . . . . . . . . . . 1-30
Hot I/O Detection . . . . . . . . . . . . . . . . . . . . . . 1-32
Device Boxing . . . . . . . . . . . . . . . . . . . . . . . 1-33
Command Flooding . . . . . . . . . . . . . . . . . . . . . . 1-33
Class M1 Commands . . . . . . . . . . . . . . . . . . . . . 1-34
Class M2 Commands . . . . . . . . . . . . . . . . . . . . . 1-34
| Class M3 Commands . . . . . . . . . . . . . . . . . . . . . 1-36
Class C1 Commands . . . . . . . . . . . . . . . . . . . . . 1-36
Class C2 Commands . . . . . . . . . . . . . . . . . . . . . 1-36
| Class C3 Commands . . . . . . . . . . . . . . . . . . . . . 1-36
Inline Commands . . . . . . . . . . . . . . . . . . . . . . 1-36
Responding to Failing Devices . . . . . . . . . . . . . . . . . . 1-37
Quiescing the System . . . . . . . . . . . . . . . . . . . . . 1-38
Stopping the System . . . . . . . . . . . . . . . . . . . . . . 1-38

Chapter 2. Console Characteristics and Operations . . . . . . . . . . 2-1

General Characteristics of Display Consoles . . . . . . . . . . . . . . 2-1
Subsystem Use of Consoles. . . . . . . . . . . . . . . . . . . 2-1
Multiple-Console Configuration . . . . . . . . . . . . . . . . . . 2-2
Features on Display Consoles . . . . . . . . . . . . . . . . . . 2-3
Display Screen Areas . . . . . . . . . . . . . . . . . . . . . 2-4
L= Operand . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Special Screen Characters . . . . . . . . . . . . . . . . . . . 2-6
Messages Sent to Display Consoles . . . . . . . . . . . . . . . . 2-6
Operations on Display Consoles in Full-Capability Mode . . . . . . . . . 2-7
Performing Basic Keyboard Actions . . . . . . . . . . . . . . . . 2-7
How to Enter Commands . . . . . . . . . . . . . . . . . . . . 2-7
Entering Commands with the Keyboard . . . . . . . . . . . . . . 2-7
Entering Commands with Program Function Keys . . . . . . . . . . . 2-9
Entering Commands with the Selector Pen . . . . . . . . . . . . . 2-12
Changing Information in the Entry Area . . . . . . . . . . . . . . 2-13
Blanking the Entry Area . . . . . . . . . . . . . . . . . . . . 2-14
Handling Consoles in Error Conditions . . . . . . . . . . . . . . . 2-15
System Errors . . . . . . . . . . . . . . . . . . . . . . . 2-15
Console Hardware Errors . . . . . . . . . . . . . . . . . . . 2-15
Responding to a Master Console Failure. . . . . . . . . . . . . . 2-16
Responding to a No-Consoles Condition . . . . . . . . . . . . . . 2-17
Responding to Console Message Backups . . . . . . . . . . . . . 2-18
Processing MVS Messages at the System Console During System
Recovery . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Placing a Console in Offline Status . . . . . . . . . . . . . . . . . 2-22
Interchanging Your Consoles on a Control Unit . . . . . . . . . . . . 2-22

Chapter 3. Defining and Changing Console Characteristics . . . . . . 3-1 .

Using Operator Commands to Change CONSOLxx Statements . . . . . . 3-1 .
Potential Effects of Altering Console Attributes . . . . . . . . . . . 3-1 .
The CONSOLE Statement of CONSOLxx . . . . . . . . . . . . . 3-1 .
The INIT Statement in the CONSOLxx Member . . . . . . . . . . 3-2 .
The HARDCOPY Statement in the CONSOLxx Member . . . . . . . 3-3 .
Displaying Information About Console Characteristics . . . . . . . . 3-4 .
Changing Console Characteristics . . . . . . . . . . . . . . . . 3-5 .
System Commands Grouped According to System Command Authority 3-5
Changing the Authorization of a Console . . . . . . . . . . . . . . 3-7
Changing the Master Console in a System or Sysplex . . . . . . . . . 3-7

iv z/OS V1R7.0 MVS System Commands

 Console Groups . . . . . . . . . . . . . . . . . . . . . . . 3-8
Switching Console Attributes from One Console to Another . . . . . . . 3-8
Defining Console Use . . . . . . . . . . . . . . . . . . . . . 3-9
Using a Full-Capability Console . . . . . . . . . . . . . . . . . 3-10
Controlling System Messages and Commands . . . . . . . . . . . . 3-12
Defining Routing Codes for a Console . . . . . . . . . . . . . . 3-13
Defining Message Levels for a Console . . . . . . . . . . . . . . 3-14
Controlling the Format of Messages . . . . . . . . . . . . . . . 3-15
Controlling the Message Processing Facility (MPF) . . . . . . . . . . 3-15
Controlling the Action Message Retention Facility . . . . . . . . . . 3-16
Activating WTO and WTOR Installation Exit Routines . . . . . . . . . 3-17
Checking Message Processing, Retention, and Presentation Options 3-17
Defining Program Function Keys (PFKs) . . . . . . . . . . . . . . . 3-18
Defining PFKs Using PFK Tables . . . . . . . . . . . . . . . . 3-18
Defining PFKs Using the CONTROL Command . . . . . . . . . . . 3-19
The PFKTABxx and PFKs . . . . . . . . . . . . . . . . . . . 3-20
Processing Hardcopy . . . . . . . . . . . . . . . . . . . . . . 3-21
The Hardcopy Message Set . . . . . . . . . . . . . . . . . . 3-21
The Hardcopy Medium . . . . . . . . . . . . . . . . . . . . 3-22

Chapter 4. MVS System Commands Reference . . . . . . . . . . . . 4-1

Command Syntax Notation . . . . . . . . . . . . . . . . . . . . 4-12
How to read syntax conventions . . . . . . . . . . . . . . . . . 4-12
System Command Formats . . . . . . . . . . . . . . . . . . . 4-13
Typical Format . . . . . . . . . . . . . . . . . . . . . . . 4-13
A Second Format . . . . . . . . . . . . . . . . . . . . . . 4-14
ACTIVATE Command . . . . . . . . . . . . . . . . . . . . . . 4-15
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-15
CANCEL Command . . . . . . . . . . . . . . . . . . . . . . 4-19
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-20
CHNGDUMP Command . . . . . . . . . . . . . . . . . . . . . 4-25
Dump Options and Modes . . . . . . . . . . . . . . . . . . . 4-25
Changing the Dump Mode and Options . . . . . . . . . . . . . . 4-26
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-26
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Removing Options from or Resetting the System Dump Options Lists 4-26
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Options for SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP . . . . 4-29
Resetting Dump Mode to ADD and the Dump Options to Initial Values 4-32
Example: How CHNGDUMP Commands Affect Dump Modes and Options 4-32
Setting the Dump Modes and Options. . . . . . . . . . . . . . . 4-34
CMDS Command . . . . . . . . . . . . . . . . . . . . . . . 4-44
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-44
CONFIG Command . . . . . . . . . . . . . . . . . . . . . . 4-46
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Reconfiguring the System Directly . . . . . . . . . . . . . . . . 4-46
Reconfiguring the System with a CONFIGxx Parmlib Member . . . . . . 4-55
Reconfiguring the System in Response to a Configuration Display . . . . 4-56
CONTROL Command . . . . . . . . . . . . . . . . . . . . . 4-58
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-59
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
Changing Out Of Line Display Area Specifications . . . . . . . . . . 4-59

Contents v
 Deleting Retained Action Messages . . . . . . . . . . . . . . . 4-60
Halting the Printing or the Display of a Status Display . . . . . . . . . 4-62
Controlling Displays in Areas . . . . . . . . . . . . . . . . . . 4-62
Removing Information From the Screen . . . . . . . . . . . . . . 4-64
Activating, Deactivating, or Displaying the Status of the Action Message
Retention Facility . . . . . . . . . . . . . . . . . . . . . 4-65
Changing or Displaying the Number of Allowed WTL SYSLOG Buffers 4-66
Changing or Displaying the Number of Allowed WTO and WTOR Message
Buffers . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
Changing the Time the System Waits for ROUTE Command Responses 4-67
Increasing the Maximum Number of Reply IDs . . . . . . . . . . . 4-68
Changing or Displaying the Status of WTO Installation Exit IEAVMXIT 4-69
Displaying the SMCS APPLID of the current system and VTAM generic
resource name for SMCS . . . . . . . . . . . . . . . . . . 4-70
Setting the APPLID of the System . . . . . . . . . . . . . . . . 4-70
Setting or Turning Off the VTAM Generic Resource Name for SMCS 4-71
Changing a PFK Definition . . . . . . . . . . . . . . . . . . . 4-72
Deleting Message Queues . . . . . . . . . . . . . . . . . . . 4-74
Changing or Displaying Message Deletion and Format Specifications 4-74
Changing or Displaying Time Intervals for Dynamic Displays . . . . . . 4-78
Changing the Operating Mode of a Console . . . . . . . . . . . . 4-79
Selecting the Message Levels for a Console . . . . . . . . . . . . 4-80
DEVSERV Command . . . . . . . . . . . . . . . . . . . . . . 4-82
Using the DEVSERV QDASD option . . . . . . . . . . . . . . . 4-83
Using the DEVSERV QTAPE option . . . . . . . . . . . . . . . 4-83
| Using the DEVSERV QLIB option . . . . . . . . . . . . . . . . 4-83
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-84
DISPLAY Command . . . . . . . . . . . . . . . . . . . . . . 4-99
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-101
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102
Displaying APPC/MVS Information . . . . . . . . . . . . . . . 4-102
Displaying ASCH Configuration Information . . . . . . . . . . . . 4-108
Displaying Page Data Set Information . . . . . . . . . . . . . . 4-110
| Displaying the current system level Language Environment run-time
| options . . . . . . . . . . . . . . . . . . . . . . . . . 4-112
Displaying CONTROL Command Functions . . . . . . . . . . . . 4-112
Displaying Attached Coupling Facility Information . . . . . . . . . . 4-113
Displaying Console Group Definitions . . . . . . . . . . . . . . 4-113
Displaying Console Status Information . . . . . . . . . . . . . . 4-114
Displaying DIAG Parmlib Information . . . . . . . . . . . . . . . 4-118
Displaying Data Lookaside Facility Information . . . . . . . . . . . 4-119
Displaying Dump Options or Dump Data Set Status . . . . . . . . . 4-121
Displaying Extended MCS Information . . . . . . . . . . . . . . 4-125
Displaying the Timer Synchronization Mode and ETR Ports . . . . . . 4-129
Displaying Global Resource Serialization Information . . . . . . . . . 4-130
Displaying TSO/E Parmlib Information . . . . . . . . . . . . . . 4-141
Displaying I/O Configuration Information . . . . . . . . . . . . . 4-142
| Displaying Captured UCB Information . . . . . . . . . . . . . . 4-142
Displaying Dynamic Channel Path Management Information . . . . . . 4-143
| Displaying FICON Switch Data Information . . . . . . . . . . . . 4-143
Displaying IOS Group Information . . . . . . . . . . . . . . . . 4-144
| Displaying MIDAW Facility Status . . . . . . . . . . . . . . . . 4-144
Displaying MIH and I/O Timing Limits . . . . . . . . . . . . . . 4-144
| Displaying IOS Storage Residency Information . . . . . . . . . . . 4-148
Displaying the Devices Stopped by the IOACTION Command . . . . . 4-148

vi z/OS V1R7.0 MVS System Commands

 Displaying IPL Information . . . . . . . . . . . . . . . . . . 4-149
Displaying System Activity . . . . . . . . . . . . . . . . . . 4-150
Displaying Started Task Status . . . . . . . . . . . . . . . . . 4-159
Displaying Library Lookaside Information . . . . . . . . . . . . . 4-161
Displaying the System Logger and its Log Streams . . . . . . . . . 4-162
Displaying the Logrec Recording Medium . . . . . . . . . . . . . 4-165
Displaying System Configuration Information . . . . . . . . . . . . 4-166
Displaying MVS Message Service Status and Languages . . . . . . . 4-172
Displaying Message Suppression, Retention, Color, Intensity, and
Highlighting Options . . . . . . . . . . . . . . . . . . . . 4-173
Displaying z/OS UNIX System Services Status . . . . . . . . . . . 4-174
Displaying Operator Information (OPDATA) . . . . . . . . . . . . 4-190
Displaying PARMLIB Information . . . . . . . . . . . . . . . . 4-191
Displaying Commands Defined for PFKs . . . . . . . . . . . . . 4-194
Displaying Registered Products . . . . . . . . . . . . . . . . 4-195
Displaying Entries in the List of APF-Authorized Libraries . . . . . . . 4-196
Displaying Dynamic Exits . . . . . . . . . . . . . . . . . . . 4-197
Displaying LNKLST Information . . . . . . . . . . . . . . . . 4-199
Displaying LPA Information . . . . . . . . . . . . . . . . . . 4-201
Displaying System Requests . . . . . . . . . . . . . . . . . 4-201
Displaying RTLS Information . . . . . . . . . . . . . . . . . 4-207
Displaying SLIP Trap Information . . . . . . . . . . . . . . . . 4-211
Displaying SMF Data . . . . . . . . . . . . . . . . . . . . 4-211
Displaying Storage Management Subsystem Information . . . . . . . 4-212
Displaying Information about All Subsystems . . . . . . . . . . . . 4-229
Displaying Static System Symbols . . . . . . . . . . . . . . . 4-232
Displaying the Local and Greenwich Mean Time and Date . . . . . . . 4-232
Displaying Component or Transaction Trace Status . . . . . . . . . 4-233
Displaying Device Status and Allocation . . . . . . . . . . . . . 4-236
Displaying Virtual Storage Information . . . . . . . . . . . . . . 4-239
Displaying Workload Manager Information . . . . . . . . . . . . . 4-240
Displaying Cross System Coupling Facility (XCF) Information . . . . . 4-245
DUMP Command . . . . . . . . . . . . . . . . . . . . . . . 4-255
Wildcards. . . . . . . . . . . . . . . . . . . . . . . . . 4-255
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-255
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-256
Specifying Dump Options . . . . . . . . . . . . . . . . . . . 4-257
DUMPDS Command . . . . . . . . . . . . . . . . . . . . . 4-274
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274
Adding System Dump Resources . . . . . . . . . . . . . . . . 4-275
Enabling and Disabling Automatic Dump Data Set Allocation . . . . . . 4-278
Making Dump Data Sets Ready To Receive Dumps . . . . . . . . . 4-279
Deleting System Dump Resources . . . . . . . . . . . . . . . 4-279
Setting the Name-Pattern for Dump Data Sets . . . . . . . . . . . 4-281
FORCE Command . . . . . . . . . . . . . . . . . . . . . . 4-284
Considerations . . . . . . . . . . . . . . . . . . . . . . . 4-284
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-285
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-285
HALT Command . . . . . . . . . . . . . . . . . . . . . . . 4-289
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-289
IOACTION Command . . . . . . . . . . . . . . . . . . . . . 4-290
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-290
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-290
LIBRARY Command. . . . . . . . . . . . . . . . . . . . . . 4-292
LOG Command . . . . . . . . . . . . . . . . . . . . . . . 4-293
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-293

Contents vii
 Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-293
LOGOFF Command . . . . . . . . . . . . . . . . . . . . . . 4-294
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-294
LOGON Command . . . . . . . . . . . . . . . . . . . . . . 4-295
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-295
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-295
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-295
MODE Command . . . . . . . . . . . . . . . . . . . . . . . 4-297
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-297
Controlling the Recording of Hard Machine Check Interruptions . . . . . 4-298
Controlling the Recording of System Recovery and Degradation Machine
Check Interruptions . . . . . . . . . . . . . . . . . . . . 4-301
Displaying Recording and Monitoring Status . . . . . . . . . . . . 4-302
MODIFY Command . . . . . . . . . . . . . . . . . . . . . . 4-303
Summary of MODIFY . . . . . . . . . . . . . . . . . . . . 4-303
Using Asterisks in MODIFY Commands . . . . . . . . . . . . . 4-304
MODIFY Command Syntax . . . . . . . . . . . . . . . . . . 4-305
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-305
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-306
Passing Information to a z/OS UNIX System Services Application . . . . 4-307
Modifying TSO/VTAM Time Sharing . . . . . . . . . . . . . . . 4-308
Controlling z/OS UNIX System Services (z/OS UNIX) . . . . . . . . 4-308
Communicating with the Catalog Address Space . . . . . . . . . . 4-315
Changing the DLF Processing Mode . . . . . . . . . . . . . . . 4-324
Changing the DLF parameters . . . . . . . . . . . . . . . . . 4-324
Displaying DLF Status . . . . . . . . . . . . . . . . . . . . 4-325
Building and Replacing Library Lookaside Directories . . . . . . . . 4-325
Operating with the Network File System Server . . . . . . . . . . . 4-326
Collecting Problem Information for the Network File System Server 4-328
Managing the Object Access Method (OAM) . . . . . . . . . . . . 4-329
Recycling z/OS UNIX System Services (z/OS UNIX) . . . . . . . . . 4-329
| Dynamically activating maintenance for z/OS UNIX System Services
| (z/OS UNIX) . . . . . . . . . . . . . . . . . . . . . . . 4-331
Stopping a Temporary File System (TFS) . . . . . . . . . . . . . 4-332
| Enabling and Disabling the Application Response Measurement (ARM)
| Agent and Enterprise Workload Manager (EWLM) platform services . . 4-332
Changing Workload Manager Resource States . . . . . . . . . . . 4-333
Specifying Data Set Selection Criteria for an External Writer . . . . . . 4-334
Causing an External Writer to Pause . . . . . . . . . . . . . . 4-336
MONITOR Command . . . . . . . . . . . . . . . . . . . . . 4-338
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-338
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-338
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-338
MOUNT Command . . . . . . . . . . . . . . . . . . . . . . 4-340
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-340
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-340
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-340
Tape Library Dataserver Considerations . . . . . . . . . . . . . 4-341
MSGRT Command . . . . . . . . . . . . . . . . . . . . . . 4-342
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-342
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-342
Stopping Message Routing . . . . . . . . . . . . . . . . . . 4-344
PAGEADD Command . . . . . . . . . . . . . . . . . . . . . 4-345
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-346
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-346
PAGEDEL Command . . . . . . . . . . . . . . . . . . . . . 4-347

viii z/OS V1R7.0 MVS System Commands

 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-348
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-348
QUIESCE Command . . . . . . . . . . . . . . . . . . . . . 4-350
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-350
REPLY Command . . . . . . . . . . . . . . . . . . . . . . 4-351
Using System Symbols in REPLY Commands . . . . . . . . . . . 4-351
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-352
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-352
Replying to System Information Requests . . . . . . . . . . . . . 4-352
Replying to System Requests During Recovery Processing . . . . . . 4-353
Replying to System Security WTORs . . . . . . . . . . . . . . 4-353
Setting the Time-of-Day Clock . . . . . . . . . . . . . . . . . 4-353
Specifying Component Trace Options . . . . . . . . . . . . . . 4-355
Specifying Dump Options . . . . . . . . . . . . . . . . . . . 4-355
Specifying SMF Options . . . . . . . . . . . . . . . . . . . 4-356
Specifying System Parameters . . . . . . . . . . . . . . . . . 4-356
RESET Command . . . . . . . . . . . . . . . . . . . . . . 4-358
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-358
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-358
Forcing a Hung MCS or SMCS Console Offline . . . . . . . . . . . 4-358
Changing Service Classes or Quiescing Work . . . . . . . . . . . 4-359
ROUTE Command . . . . . . . . . . . . . . . . . . . . . . 4-363
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . 4-363
How MVS Displays Aggregated Response from ROUTE . . . . . . . 4-364
Using System Symbols in ROUTE Commands . . . . . . . . . . . 4-365
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-366
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-366
SEND Command . . . . . . . . . . . . . . . . . . . . . . . 4-371
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-371
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-371
Communicating with Other Operators . . . . . . . . . . . . . . 4-371
Communicating with Specified Users . . . . . . . . . . . . . . 4-372
Communicating with All Logged-On Terminal Users . . . . . . . . . 4-373
Saving Messages in the Broadcast Data Set . . . . . . . . . . . . 4-375
Listing the Notices Section of the Broadcast Data Set . . . . . . . . 4-375
Deleting a Message from the Broadcast Data Set (Notices Section) 4-377
SET Command . . . . . . . . . . . . . . . . . . . . . . . 4-378
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-379
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-380
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-380
| SETAPPC Command . . . . . . . . . . . . . . . . . . . . . 4-392
| Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-392
| Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-392
| SETCEE Command . . . . . . . . . . . . . . . . . . . . . . 4-398
| Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-398
| Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-398
SETCON Command . . . . . . . . . . . . . . . . . . . . . . 4-399
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-399
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-399
SETDMN Command . . . . . . . . . . . . . . . . . . . . . . 4-401
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-401
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . 4-401
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-402
SETETR Command . . . . . . . . . . . . . . . . . . . . . . 4-403
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-403
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-403

Contents ix
 SETGRS Command . . . . . . . . . . . . . . . . . . . . . . 4-404
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-404
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-404
SETIOS Command . . . . . . . . . . . . . . . . . . . . . . 4-406
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-406
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-407
SETLOAD Command . . . . . . . . . . . . . . . . . . . . . 4-412
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-412
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-412
| SETLOGR Command . . . . . . . . . . . . . . . . . . . . . 4-414
| Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-414
| Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-414
| SETLOGR FORCE Command . . . . . . . . . . . . . . . . . 4-414
SETLOGRC Command . . . . . . . . . . . . . . . . . . . . 4-417
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-417
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-417
SETOMVS Command . . . . . . . . . . . . . . . . . . . . . 4-419
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-419
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-420
SETPROG Command . . . . . . . . . . . . . . . . . . . . . 4-431
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-431
Updating the APF List . . . . . . . . . . . . . . . . . . . . 4-431
Updating Dynamic Exits . . . . . . . . . . . . . . . . . . . 4-433
Updating LNKLST Concatenations . . . . . . . . . . . . . . . 4-436
Managing Dynamic LPA Content . . . . . . . . . . . . . . . . 4-441
SETRRS CANCEL Command . . . . . . . . . . . . . . . . . . 4-444
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-444
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-444
SETSMF Command . . . . . . . . . . . . . . . . . . . . . . 4-445
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-445
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-445
SETSMS Command . . . . . . . . . . . . . . . . . . . . . . 4-446
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-447
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-447
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-448
SETSSI Command . . . . . . . . . . . . . . . . . . . . . . 4-459
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-459
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-459
| SETUNI Command . . . . . . . . . . . . . . . . . . . . . . 4-462
| Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-462
| Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-462
SETXCF Command . . . . . . . . . . . . . . . . . . . . . . 4-468
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-468
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-468
SETXCF COUPLE Command . . . . . . . . . . . . . . . . . 4-468
SETXCF FORCE Command . . . . . . . . . . . . . . . . . . 4-472
SETXCF MODIFY Command . . . . . . . . . . . . . . . . . 4-474
SETXCF PRSMPOLICY Command . . . . . . . . . . . . . . . 4-476
SETXCF START Command . . . . . . . . . . . . . . . . . . 4-477
SETXCF STOP Command . . . . . . . . . . . . . . . . . . 4-485
SLIP Command . . . . . . . . . . . . . . . . . . . . . . . 4-490
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-490
Using SLIP Commands . . . . . . . . . . . . . . . . . . . 4-490
Processing of SLIP Commands . . . . . . . . . . . . . . . . 4-491
Coding SLIP Command Parameters . . . . . . . . . . . . . . . 4-492
Setting a SLIP Trap . . . . . . . . . . . . . . . . . . . . . 4-497

x z/OS V1R7.0 MVS System Commands

 Modifying an Existing SLIP Trap . . . . . . . . . . . . . . . . 4-555
Deleting an Existing SLIP Trap . . . . . . . . . . . . . . . . . 4-556
START Command . . . . . . . . . . . . . . . . . . . . . . 4-558
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-558
Starting a System Task from a Console. . . . . . . . . . . . . . 4-558
Starting the APPC/MVS Address Space . . . . . . . . . . . . . 4-562
Starting the APPC/MVS Transaction Scheduler Address Space . . . . . 4-563
Starting the Generalized Trace Facility . . . . . . . . . . . . . . 4-564
Starting the Library Lookaside (LLA) Address Space . . . . . . . . . 4-566
Starting the Object Access Method (OAM) . . . . . . . . . . . . 4-566
Starting Resource Recovery Services (RRS) . . . . . . . . . . . . 4-567
Starting the System Object Model (SOM) Subsystem . . . . . . . . 4-568
Starting TSO/VTAM Time-Sharing . . . . . . . . . . . . . . . . 4-569
Starting the Virtual Lookaside Facility or Data Lookaside Facility . . . . 4-570
Starting an External Writer . . . . . . . . . . . . . . . . . . 4-571
STOP Command . . . . . . . . . . . . . . . . . . . . . . . 4-573
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-573
| Stopping a Running Program . . . . . . . . . . . . . . . . . 4-573
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-573
Stopping an ASCH Initiator . . . . . . . . . . . . . . . . . . 4-576
Stopping the Data Lookaside Facility (DLF) . . . . . . . . . . . . 4-576
Stopping the Library Lookaside (LLA) Address Space . . . . . . . . 4-576
Stopping the Object Access Method (OAM) Address Space . . . . . . 4-577
Stopping a System Object Model (SOM) . . . . . . . . . . . . . 4-577
Stopping a Temporary File System (TFS) . . . . . . . . . . . . . 4-578
Stopping the Virtual Lookaside Facility (VLF) . . . . . . . . . . . . 4-578
STOPMN Command. . . . . . . . . . . . . . . . . . . . . . 4-579
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-579
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-579
STOPTR Command . . . . . . . . . . . . . . . . . . . . . . 4-580
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-580
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-580
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-580
SWAP Command . . . . . . . . . . . . . . . . . . . . . . . 4-582
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-582
Operator-Requested DDR. . . . . . . . . . . . . . . . . . . 4-582
System-Initiated DDR . . . . . . . . . . . . . . . . . . . . 4-583
SWITCH Command . . . . . . . . . . . . . . . . . . . . . . 4-584
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-584
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-584
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-584
TRACE Command . . . . . . . . . . . . . . . . . . . . . . 4-587
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-587
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-588
Specifying TRACE CT Options . . . . . . . . . . . . . . . . . 4-591
Specifying TRACE TT Options . . . . . . . . . . . . . . . . . 4-593
TRACK Command . . . . . . . . . . . . . . . . . . . . . . 4-597
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-597
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-597
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-597
UNLOAD Command . . . . . . . . . . . . . . . . . . . . . . 4-599
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-599
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-599
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-599
VARY Command . . . . . . . . . . . . . . . . . . . . . . . 4-600
Scope in a Sysplex . . . . . . . . . . . . . . . . . . . . . 4-601

Contents xi
 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-602
Controlling Problem Determination Mode for the System Console . . . . 4-602
Controlling MCS and SMCS Consoles . . . . . . . . . . . . . . 4-605
Changing the Master Console . . . . . . . . . . . . . . . . . 4-613
Controlling Hardcopy Processing . . . . . . . . . . . . . . . . 4-614
Placing a Secondary Console Online or Offline . . . . . . . . . . . 4-617
Defining a Tape Device as Automatically Switchable . . . . . . . . . 4-618
Placing an I/O Device or a Range of I/O Devices Online or Offline 4-619
Controlling a Global Resource Serialization Complex . . . . . . . . . 4-623
Placing an I/O Path or Paths Online or Offline . . . . . . . . . . . 4-625
Changing the state of coupling facility cache structures and volumes 4-627
Placing an Optical Drive or Library Online or Offline . . . . . . . . . 4-630
Placing a System-Managed Tape Library Online or Offline . . . . . . . 4-630
Analyzing the State of the PDSE Subsystem . . . . . . . . . . . . 4-630
Releasing PDSE Latches . . . . . . . . . . . . . . . . . . . 4-630
| Modifying processing of PDSE monitor . . . . . . . . . . . . . . 4-631
| Display current state of the PDSE monitor . . . . . . . . . . . . 4-631
Changing the SMS Status of a Storage Group or Volume . . . . . . . 4-631
Controlling DFSMStvs processing . . . . . . . . . . . . . . . . 4-634
Controlling CICSVR processing . . . . . . . . . . . . . . . . 4-643
Placing a Switch Port Online or Offline . . . . . . . . . . . . . . 4-643
Controlling an Application Environment . . . . . . . . . . . . . . 4-645
Activating a Service Policy . . . . . . . . . . . . . . . . . . 4-647
Removing a System from the XCF Sysplex . . . . . . . . . . . . 4-649
WRITELOG Command . . . . . . . . . . . . . . . . . . . . . 4-651
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4-651
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-651

Appendix. Accessibility . . . . . . . . . . . . . . . . . . . . . A-1

Using assistive technologies . . . . . . . . . . . . . . . . . . . A-1
Keyboard navigation of the user interface . . . . . . . . . . . . . . . A-1
z/OS information . . . . . . . . . . . . . . . . . . . . . . . . A-1

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

xii z/OS V1R7.0 MVS System Commands

 Figures
| 1-1. Format of the LOAD Parameter . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1-2. Example of a Successful Response to a DISPLAY AUTOSWITCH Command . . . . . . 1-30
1-3. Example of an Unsuccessful Response to a DISPLAY AUTOSWITCH Command 1-30
2-1. Comparison of the Display Screens of Full-Capability and Output-Only Display Consoles 2-5
2-2. Example of DISPLAY CONSOLES,BACKLOG Command Output . . . . . . . . . . . 2-20
3-1. Example of DISPLAY CONSOLES,A Command Output . . . . . . . . . . . . . . . 3-5
3-2. Format of a Console Screen in Message Stream Mode . . . . . . . . . . . . . . . 3-11
4-1. One System Command Format . . . . . . . . . . . . . . . . . . . . . . . 4-13
4-2. A Second System Command Format . . . . . . . . . . . . . . . . . . . . . 4-14
4-3. Display Output Illustration (Column Descriptions) . . . . . . . . . . . . . . . . . 4-159
4-4. Display Output from D A,WTOR (Membername) . . . . . . . . . . . . . . . . . 4-160
4-5. Display Output for D A,WTOR (Membername and Identifier) . . . . . . . . . . . . 4-160
4-6. Display Output for D A,WTOR (Membername and JOBNAME) . . . . . . . . . . . . 4-160
4-7. Display Output from D A,SYM1 . . . . . . . . . . . . . . . . . . . . . . . 4-160
4-8. Display Output from D A,SYMTEST . . . . . . . . . . . . . . . . . . . . . 4-161
4-9. Display Output from D A,SYMBOLS . . . . . . . . . . . . . . . . . . . . . 4-161

Copyright IBM Corp. 1988, 2006 xiii

xiv z/OS V1R7.0 MVS System Commands
 Tables
| 1-1. Possible Values IMSI Characters . . . . . . . . . . . . . . . . . . . . . . . 1-5
1-2. MVS System Commands With Sysplex Scope . . . . . . . . . . . . . . . . . . 1-12
2-1. Checking the Commands Defined for Each PFK . . . . . . . . . . . . . . . . . 2-10
3-1. Comparison of System Commands and CONSOLE Parameters in CONSOLxx . . . . . . 3-1
3-2. Comparison of System Commands and INIT Statements in CONSOLxx . . . . . . . . . 3-2
3-3. Comparison of VARY HARDCPY Commands and HARDCOPY Statements in CONSOLxx 3-3
3-4. Command Groups Used to Determine Command Authority . . . . . . . . . . . . . . 3-6
3-5. Message Routing Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
4-1. System Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4-2. Syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4-3. Specifying FORCE with EMIF . . . . . . . . . . . . . . . . . . . . . . . . 4-17
4-4. CANCEL Command Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4-5. Summary of the CHNGDUMP Command . . . . . . . . . . . . . . . . . . . . 4-25
4-6. Example of How CHNGDUMP Commands Affect Dump Modes and Options . . . . . . . 4-32
4-7. Summary of the CONFIG Command . . . . . . . . . . . . . . . . . . . . . . 4-46
4-8. Summary of the CONTROL Command . . . . . . . . . . . . . . . . . . . . . 4-58
4-9. Sysplex Scope for CONTROL Command . . . . . . . . . . . . . . . . . . . . 4-59
4-10. Summary of the DISPLAY Command . . . . . . . . . . . . . . . . . . . . . 4-99
4-11. Sysplex Scope for DISPLAY Command . . . . . . . . . . . . . . . . . . . . 4-101
4-12. Displaying System Activity: Information for the LIST Operand . . . . . . . . . . . . 4-152
4-13. Displaying System Activity: Information for the ALL Operand . . . . . . . . . . . . 4-153
4-14. Displaying System Activity: Information for a Specific Name . . . . . . . . . . . . . 4-154
4-15. Examples of START Commands to Start Jobs . . . . . . . . . . . . . . . . . . 4-156
4-16. Examples of DISPLAY Commands . . . . . . . . . . . . . . . . . . . . . . 4-156
4-17. Denomination (multiplier) character used for various OMVS commands . . . . . . . . 4-177
4-18. Summary of the DUMPDS Command . . . . . . . . . . . . . . . . . . . . . 4-274
4-19. FORCE Command Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 4-284
4-20. Summary of the MODE Command . . . . . . . . . . . . . . . . . . . . . . 4-297
4-21. MODE Parameters Allowed for Machine Check Interruptions . . . . . . . . . . . . 4-298
4-22. Summary of the MODIFY Command . . . . . . . . . . . . . . . . . . . . . 4-303
4-23. Examples of START Commands to Start Jobs . . . . . . . . . . . . . . . . . . 4-305
4-24. Examples of MODIFY Commands . . . . . . . . . . . . . . . . . . . . . . 4-305
4-25. Possible Volume and Device Combinations on MOUNT Command . . . . . . . . . . 4-341
4-26. Summary of the REPLY Command . . . . . . . . . . . . . . . . . . . . . . 4-351
4-27. Summary of the RESET Command . . . . . . . . . . . . . . . . . . . . . . 4-358
4-28. Summary of the SEND Command . . . . . . . . . . . . . . . . . . . . . . 4-371
4-29. Sysplex Scope for SET Command . . . . . . . . . . . . . . . . . . . . . . 4-379
| 4-30. Summary of the SETLOGR Command . . . . . . . . . . . . . . . . . . . . 4-414
| 4-31. Sysplex Scope for the SETLOGR Command . . . . . . . . . . . . . . . . . . 4-414
| 4-32. 1Character Parameter Limit Multipliers . . . . . . . . . . . . . . . . . . . . 4-420
4-33. Acceptable Parameter Statements and Their Applicability . . . . . . . . . . . . . 4-427
4-34. Comparison of SET SMS with SETSMS . . . . . . . . . . . . . . . . . . . . 4-447
4-35. Incorrect Combinations of SETSMS Parameters . . . . . . . . . . . . . . . . . 4-447
4-36. Summary of the SETXCF Command . . . . . . . . . . . . . . . . . . . . . 4-468
4-37. Sysplex Scope for the SETXCF Command . . . . . . . . . . . . . . . . . . . 4-468
4-38. Summary of the SLIP Command. . . . . . . . . . . . . . . . . . . . . . . 4-490
4-39. Summary of the SLIP SET parameters . . . . . . . . . . . . . . . . . . . . 4-499
4-40. Summary of the START Command . . . . . . . . . . . . . . . . . . . . . . 4-558
4-41. Summary of the STOP Command . . . . . . . . . . . . . . . . . . . . . . 4-573
4-42. Summary of the SWAP Command . . . . . . . . . . . . . . . . . . . . . . 4-582
4-43. Summary of the VARY Command . . . . . . . . . . . . . . . . . . . . . . 4-600
4-44. Sysplex Scope for VARY Command . . . . . . . . . . . . . . . . . . . . . 4-601
4-45. Goal Mode and Compatibility Mode Actions for VARY WLM,APPLENV. . . . . . . . . 4-646
Copyright IBM Corp. 1988, 2006 xv
xvi z/OS V1R7.0 MVS System Commands
About this document
This document describes how to use MVS system operator commands for the z/OS
(5694-A01) and z/OS.e (5655-G52) operating systems. Although you can also
perform many of the tasks described in this book using JES2 or JES3 commands,
this book describes only the MVS (base control program) system commands. For
information about commands for other z/OS elements, such as communications
server (IP and SNA), DFSMS, JES2, JES3, and RACF, see z/OS Information
Roadmap. For information about commands for other software products that run on
z/OS, see z/OS Software Products Collection, SK3T-4270.

Who should use this document

This document is intended for anyone using a console and system commands to
control the operating system. This document assumes that the user understands
the hardware controls and features of the installation. It also assumes that the user
understands the general organization and functions of a z/OS operating system.

How to use this document

To describe the basic tasks within these general tasks and to provide a convenient
system commands reference, this document is organized as follows:
v Chapter 1, System Operations, on page 1-1, describes the tasks of running the
system from the time the system comes up to the time the system goes down for
a normal or abnormal reason.
v Chapter 2, Console Characteristics and Operations, on page 2-1, describes the
consoles that MVS supports as operators consoles. It describes the operations
and characteristics that you cannot define, including the operations that are
common on all operators consoles.
v Chapter 3, Defining and Changing Console Characteristics, on page 3-1,
continues the console descriptions of Chapter 2 by describing the console
characteristics that you can define. It describes the commands that operators and
system programmers can use to tailor the consoles and console operations to
the installations requirements. Chapter 3 also describes how to restrict the use of
system commands based on which operator issues the command and/or which
MCS or SMCS console the operator uses.
v Chapter 4, MVS System Commands Reference, on page 4-1, summarizes the
function, syntax, and parameters of all the MVS system commands that you can
use to control both the system and the MCS and SMCS consoles.

Where to find more information

Where necessary, this document references information in other documents, using
shortened versions of the document title. For complete titles and order numbers of
the documents for all products that are part of z/OS, see z/OS Information
Roadmap.

Information updates on the web

For the latest information updates that have been provided in PTF cover letters and
Documentation APARs for z/OS and z/OS.e, see the online document at:

http://www.s390.ibm.com:80/bookmgr-cgi/bookmgr.cmd/BOOKS/ZIDOCMST/CCONTENTS

Copyright IBM Corp. 1988, 2006 xvii

 This document is updated weekly and lists documentation changes before they are
incorporated into z/OS publications.

Using LookAt to look up message explanations

LookAt 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. Using
LookAt to find information is faster than a conventional search because in most
cases LookAt goes directly to the message explanation.

You can use LookAt from these locations to find IBM message explanations for
z/OS elements and features, z/VM, VSE/ESA, and Clusters for AIX and
Linux:
v The Internet. You can access IBM message explanations directly from the LookAt
Web site at http://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 or z/OS.e
systems to access 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 the
z/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) version
can still be used from the directory in which you install the Windows version of
LookAt.
v Your wireless handheld device. You can use the LookAt Mobile Edition from
http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookatm.html with a
handheld device that has wireless access and an Internet browser (for example:
Internet Explorer for Pocket PCs, Blazer or Eudora for Palm OS, or Opera for
Linux handheld devices).

You can obtain code to install LookAt on your host system or Microsoft Windows
workstation 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 the
LOOKAT.ME files available during the download process.

Using IBM Health Checker for z/OS

IBM Health Checker for z/OS is a z/OS component that installations can use to
gather information about their system environment and system parameters to help
identify potential configuration problems before they impact availability or cause
outages. Individual products, z/OS components, or ISV software can provide checks
that take advantage of the IBM Health Checker for z/OS framework. This book
refers 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. z/OS V1R4, V1R5, and V1R6
users can obtain the IBM Health Checker for z/OS from the z/OS Downloads page
at http://www.ibm.com/servers/eserver/zseries/zos/downloads/.

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

xviii z/OS V1R7.0 MVS System Commands

Summary of changes
Summary of changes
for SA22-7627-13
z/OS Version 1 Release 7
as updated April 2006

This document contains information previously presented in z/OS MVS System

Commands, SA22-7627-12, which supports z/OS Version 1 Release 7.

New information:
v Displaying MIDAW Facility Status on page 4-144 contains information about a
new parameter MIDAW on the DISPLAY IOS command.
v SETIOS Command on page 4-406 contains a new parameter, MIDAW.

This document has been enabled for the following types of advanced searches in
the online z/OS Library Center: commands, examples, tasks, concepts, reference,
parmlib members.

You may notice changes in the style and structure of some content in this
documentfor example, headings that use uppercase for the first letter of initial
words only, and procedures that have a different look and format. The changes are
ongoing improvements to the consistency and retrievability of information in our
documents.

This document contains terminology, maintenance, and editorial changes. Technical

changes or additions to the text and illustrations are indicated by a vertical line to
the left of the change.

Summary of changes
for SA22-7627-12
z/OS Version 1 Release 7

This document contains information previously presented in z/OS MVS System

Commands, SA22-7627-11, which supports z/OS Version 1 Release 6.

New information:
v Displaying z/OS UNIX System Services Status on page 4-174 contains
information about a new parameter ACTIVATE=SERVICE on the DISPLAY OMVS
command.
v Displaying Operator Information (OPDATA) on page 4-190 contains a new
parameter, MONITOR.
v Recycling z/OS UNIX System Services (z/OS UNIX) on page 4-329 contains
information about new parameters ACTIVATE=SERVICE and
DEACTIVATE=SERVICE on the MODIFY OMVS command.
v SETAPPC Command on page 4-392 is a new command to dynamically modify
or define the APPC/MVS configuration.
v SETCON Command on page 4-399 contains a new parameter, MONITOR.
v TRACE Command on page 4-587 contains a new parameter.
v SETLOGR Command on page 4-414 is a new command to control MVS logger
resources.

Copyright IBM Corp. 1988, 2006 xix

 v SETUNI Command on page 4-462 is a new command that provides control of
the Unicode tables in a conversion image.

Changed information:
v SLIP Command on page 4-490 contains changed parameter information.
v Many commands no longer support the command response routing externals
L=cc, L=cca, and CN=cc. This change aligns with the requirement that two-digit
console ID values are no longer allowed.
v Displaying z/OS UNIX System Services Status on page 4-174 contains
information about new output for the DISPLAY OMVS,O command. See
Example 6 on page 4-180.
v You cannot issue the following commands on systems at z/OS V1R7 and above:
CONTROL D,H
CONTROL D,U
CONTROL T,REF
CONTROL T,UTME=nnn
MSGRT TR=
TRACK
STOPTR
v References to OpenEdition have been replaced with z/OS UNIX System Services
or z/OS UNIX.

Deleted information:
v The START DFSMSPKG command is no longer supported and its corresponding
information is deleted from this edition.

This document contains terminology, maintenance, and editorial changes, including

changes to improve consistency and retrievability.

Summary of changes
SA22-7627-11
z/OS Version 1 Release 6
as updated March 2005

This document contains information previously presented in z/OS MVS System

Commands, SA22-7627-10, which supports z/OS Version 1 Release 6.

New information
v The DISPLAY WLM,AM command displays whether the EWLM ARM services are
{ENABLED|DISABLED. See Displaying Workload Manager Information on page
4-240 for more information.
v The MODIFY WLM,AM command enables or disables Application Response
Measurement (ARM) services and Enterprise Workload Manager (EWLM)
platform services. See Enabling and Disabling the Application Response
Measurement (ARM) Agent and Enterprise Workload Manager (EWLM) platform
services on page 4-332 for more information.

This document contains terminology, maintenance, and editorial changes, including

changes to improve consistency and retrievability.

Summary of changes
for SA22-7627-10
z/OS Version 1 Release 6

xx z/OS V1R7.0 MVS System Commands

This document contains information previously presented in z/OS MVS System
Commands, SA22-7627-09, which supports z/OS Version 1 Release 5.

New information
v CHNGDUMP Command on page 4-25 contains a new parameter
ABDUMP,TIMEENQ=yyyy.
v MODIFY Command on page 4-303 contains a new parameter WLM.
v SET Command on page 4-378 contains new parameters TIMEZONE and IOS.
v SETIOS Command on page 4-406 contains a new parameter
FICON,STATS=YES|NO.
v SETSMS Command on page 4-446 contains a new parameter DSSTIMEOUT.

This document contains terminology, maintenance, and editorial changes, including

changes to improve consistency and retrievability.

Summary of changes
for SA22-7627-09
z/OS Version 1 Release 5

This document contains information previously presented in z/OS MVS System

Commands, SA22-7627-08, which supports z/OS Version 1 Release 4.

Changed information
v The SETGRS Command on page 4-404 command contains a new default for
the SYNCHRES parameter.

Starting with z/OS V1R3, WLM compatibility mode is no longer available. This
affects the descriptions of the following system commands: DISPLAY DMN,
DISPLAY OMVS, MODIFY WLM, RESET, SET, SETDMN, and SETOMVS.

This document contains terminology, maintenance, and editorial changes, including

changes to improve consistency and retrievability.

Summary of changes
for SA22-7627-07
z/OS Version 1 Release 4
as updated December 2003

This document contains information previously presented in z/OS MVS System

Commands, SA22-7627-06, which supports z/OS Version 1 Release 4.

This document includes information in support of the Consoles Enhancements, an

unpriced feature, which will be generally available in 1Q2004.

New information
v The SETCON command added to activate functions pertaining to the console
environment and the Console ID Tracking facility.
v The DISPLAY OPDATA,TRACKING parameter added to display the status of the
Console ID Tracking facility.
v The SET CNIDTR=xx parameter added to specify the exclusion list used by the
Console ID Tracking facility.
v The VARY CN,AUTOACT= parameter added to enable the system console to
automatically receive messages when no other consoles are available.

Summary of changes xxi

 Changed information
v The CONTROL Q command no longer supports the R= parameter. Issue the
CONTROL Q command to remove a message queue from the target console
only. You cannot redirect messages to another console.

This document contains terminology, maintenance, and editorial changes, including

changes to improve consistency and retrievability.

Summary of changes
for SA22-7627-06
z/OS Version 1 Release 4
as updated October 2003

This document contains information previously presented in z/OS MVS System

Commands, SA22-7627-05, which supports z/OS Version 1 Release 4.

New information
v New information added for the DCM=OFFLINE option on the VARY SWITCH
command to support the z/OS z990 exploitation support.

This document contains terminology, maintenance, and editorial changes, including

changes to improve consistency and retrievability.

Summary of changes
for SA22-7627-05
z/OS Version 1 Release 4
as updated June 2003

This document contains information previously presented in z/OS MVS System

Commands, SA22-7627-04, which supports z/OS Version 1 Release 4.

New information
v Information is added in support of DFSMStvs. The following commands are
updated: DISPLAY, SET SMS, SETSMS, VARY.

This document also includes terminology, maintenance, and editorial changes,

including changes to improve consistency and retrievability.

Summary of changes
for SA22-7627-04
z/OS Version 1 Release 4

This document contains information previously presented in z/OS MVS System

Commands, SA22-7627-03, which supports z/OS Version 1 Release 3.

New information
v Information is added to indicate this document supports z/OS.e.
v Text has been added for the VARY CN and VARY CONSOLE commands
indicating the need for UPDATE authority in their corresponding profiles. See
VARY Command on page 4-600.
v Two new parameters, AUTHPGMLIST and AUTOMOVE, have been added for
the SETOMVS command. See SETOMVS Command on page 4-419.

xxii z/OS V1R7.0 MVS System Commands

v Output examples for the DISPLAY OMVS command are updated to include IPv6
addresses, zFS file system data, and AUTHPGMLIST paths. See Displaying
z/OS UNIX System Services Status on page 4-174.
v MODIFY CATALOG,NOTIFYEXTENT(xxx) is a new command that allows you to
specify the maximum extents possible for a catalog that are currently allocated.
The system monitors the allocated threshold.

Changed information
v The procedure for loading the system software has been updated to use the
Hardware Management Console. See Loading the System Software on page
1-3.
v The description of how a started task is assigned a job name has been clarified
for the START, CANCEL, MODIFY and STOP commands.
v Two new command classes are added for improved control of command flooding:
class C3 for ROUTE and class M3 for SEND. Both new classes have the same
maximum of 50 commands executing per class, however, SEND and ROUTE do
not impact other commands classes in execution. See CMDS Command on
page 4-44.

This document also includes terminology, maintenance, and editorial changes,

including changes to improve consistency and retrievability.

Summary of changes xxiii

xxiv z/OS V1R7.0 MVS System Commands
Chapter 1. System Operations
The tasks of starting, running, and stopping the MVS operating system involve
controlling the MVS system software and most of the installations hardware,
including processors, channel paths, and I/O devices. This book is for people who
need reference information about these tasks and the MVS system commands.
They include:
v Those who develop procedures for the daily operations, including system
programmers and lead operators
v Operators who want to learn how to use a console to control MVS and how to
change some of the consoles characteristics

System planners and system programmers should refer to the z/OS MVS Planning:
Operations for information on planning:
v System and sysplex operation management
v MCS consoles
v SMCS consoles
v Extended MCS consoles

This chapter describes how to operate an MVS system using MVS system
commands. Subsystem (JES2 or JES3) commands can perform many of the same
functions as MVS system commands but are described in z/OS JES2 Commands
and z/OS JES3 Commands.

The tasks of operating the MVS system that are described in this chapter include:
v Starting, Loading, and Initializing the System on page 1-2
v Controlling the System on page 1-9
v Controlling Time-Sharing on page 1-21
v Controlling Jobs on page 1-22
v Controlling Started Tasks on page 1-24
v Controlling System Information Recording on page 1-25
v Controlling Automatic Tape Switching on page 1-27
v Interacting with System Functions on page 1-30
v Responding to Failing Devices on page 1-37
v Quiescing the System on page 1-38
v Stopping the System on page 1-38

Controlling MVS involves issuing commands on a console and responding to

messages that appear on the console screen. Other books that describe controlling
MVS include:
v z/OS MVS JCL Reference, which documents two job control language
statements (the COMMAND statement and the JCL command statement) that
you can use to enter system commands through the input job stream.
v z/OS MVS Planning: Operations, which contains information about using MCS
and extended MCS consoles as well as MVS message and command
processing.
v z/OS MVS Planning: Global Resource Serialization, which contains information
about controlling a global resource serialization (GRS) ring.
v z/OS MVS Recovery and Reconfiguration Guide, which contains information
about handling recovery and reconfiguration in a system or sysplex.

Copyright IBM Corp. 1988, 2006 1-1

Starting, Loading, and Initializing the System
Before the system can do work, you must:
1. Start the system.
2. Prepare the system hardware.
3. Load the system software.
4. Initialize the system software. At this point, your installation might require you to
logon to the console. See Logging On to the System on page 1-6.
5. Set the time and date, as required.
6. Start the job entry subsystem (JES2 or JES3).
7. Specify all job entry subsystem parameters.

The following sections describe in detail how to start, load, and initialize the system.

Starting the System

Your installation may choose to use the system console as the only console
required to initialize the system. This console is connected to the processor
controller. From here, you load the system software and specify the load parameter.
Then you use this console to initialize the system. The initialization programs may
require initial values, specify an alternate master catalog, and, perhaps, set the time
and date.

If your installation uses MCS consoles, then you may use two separate consoles to
initialize the system. The first device is the system console, which is connected to
the processor controller. From this console, you load the system software and
specify the LOAD parameter. Later, during normal operations, this console is used
to monitor and service the hardware.

The second device is called the NIP (nucleus initialization program) console. In
HCD, you can specify a list of device numbers to use as NIP consoles. The
initialization programs use the first online and ready device in the list. NIP consoles
must be devices that are locally connected to the system using control units that do
not support systems network architecture (SNA) protocols. This means that SMCS
consoles cannot be used as NIP consoles. If that device is also specified on a
CONSOLE statement in CONSOLxx, it is initialized as an MCS console and
appears to change to an MCS console when console initialization is complete. If
no NIP consoles are defined, or no NIP consoles are online when MVS is loaded,
MVS tries to use the system console during initialization.

Preparing the System Hardware

To prepare the system hardware for work:
1. Turn on power for the processor.
2. Perform the initial microprogram load (IML) function for the processor.
3. Specify the central storage configuration.
4. Ensure that all volumes required by the system are online.
5. Turn on power for all devices you plan to use as multiple-console support
(MCS) consoles.
6. Switch into the configuration all control units for devices that the system needs.

For more information on these procedures, see the processor operators guide or
your installations operations procedures.

1-2 z/OS V1R7.0 MVS System Commands

 Loading the System Software
| Once the system hardware is ready, you can use the hardware management
| console (HMC) to load the system software. Consider the following information for
| loading system software through the HMC:
| 1. This task is available in Operator, Advanced Operator, System Programmer, or
| Service Representative mode.
| 2. Other products and documentation may refer to this operation as an initial
| program load (IPL).
| 3. For daily or routine loading of images, you can customize activation profiles to
| specify how you want to load images, then use a profile with the Activate task to
| perform all the operations necessary to make an image operational, including
| loading it with a control program.

| Load (except for a coupling facility image) causes a program to be read from a
| designated device and initiates the execution of that program. If the CPC is
| operating in logically partitioned (LPAR) mode, the logical partition is the target of
| the load. Otherwise, if the CPC is operating in basic mode, the CPC is the target of
| the load.

| To perform a load, do the following:

| 1. Open the Task List from the Views area.
| 2. Open CPC Recovery from the Task List Work Area.
| 3. Open Groups from the Views area.
| 4. Open the group that contains the CPC image that you want to load.
| 5. Select one object.
| Load is considered a disruptive task. If the object is locked, you must unlock it
| before continuing.
| 6. Drag and drop the selected object on Load in the CPC Recovery tasks area.
| The Load window is displayed with the information that was last used when the
| CPC image was loaded.
| 7. Review the information on the window to verify that the object you will load is
| the correct one. If the information is correct, select the OK push button. The
| Load Task Confirmation window is displayed.
| 8. Review the information on the window to verify that the object you will load is
| the correct one. If the information is correct, select the Yes push button. The
| Load Progress window displays indicating the progress of the load and the
| outcome.
| 9. Select the OK push button to close the window when the load completes
| successfully. Otherwise, if the load does not complete successfully, follow the
| directions on the window to determine the problem and how to correct it.
| Use the online Help to get additional information for loading a CPC image.

| Once the system hardware is ready, you can use the system console to load the
| system software. Load the system as follows, using the following fields on the
| system control (SYSCTL) frame. (This example uses the IBM 3090 for illustration.)
| 1. T=TARGET CP: Specifies the target processor for initialization.
| 2. A=INITIALIZE SYSTEM CONTROL PROGRAM, A1: Specifies the device
| number that contains the system residence volume (IPL volume).
| 3. A=INITIALIZE SYSTEM CONTROL PROGRAM, A2: Specifies the LOAD
| parameter. For more information, see Explanation of the A=INITIALIZE
| SYSTEM CONTROL PROGRAM, A2 Field on page 1-4.

Chapter 1. System Operations 1-3

| 4. A=INITIALIZE SYSTEM CONTROL PROGRAM, A3: Specifies the operator
| load function to IPL the MVS operating system. For more information, see
| Explanation of the A=INITIALIZE SYSTEM CONTROL PROGRAM, A3 Field on
| page 1-6.

| Explanation of the A=INITIALIZE SYSTEM CONTROL PROGRAM,

| A2 Field
| This field specifies the LOAD parameter. The format of the LOAD parameter is:
|
|
1 45 67 8

IODF DASD LOADxx PROMPT FEAT. ALT NUCx

IODF LOADxx prompt nucleus
device suffix feature suffix
number
|
| Figure 1-1. Format of the LOAD Parameter
|
| The LOAD parameter is eight characters long and contains the following
| information:
| 1. The first four characters (characters 1 through 4 of the LOAD parameter)
| specify the hexadecimal device number for the device that contains the I/O
| definition file (IODF) VSAM data set. This is also the device on which the
| search for the LOADxx member of SYSn.IPLPARM or SYS1.PARMLIB begins.
| The device number can be in the range X'0000' to X'FFFF'. If the number is
| less than 4 digits, specify leading zeroes before the device number. If you do
| not specify the device number, the system uses the device number of the
| system residence (SYSRES) volume.
| 2. The next two characters (characters 5 and 6 of the LOAD parameter) specify
| the suffix of the LOADxx parmlib member that the system is to use. The
| LOADxx member contains information about the name of the IODF data set,
| which master catalog to use, and which IEASYSxx members of SYS1.PARMLIB
| to use.
| The default for the LOADxx suffix is zeros. The system reads the LOADxx and
| NUCLSTxx members from SYSn.IPLPARM or SYS1.PARMLIB on the volume
| specified on the LOAD parameter (or the SYSRES volume, if a volume is not
| specified). Once the system opens the master catalog, the system reads all
| other members from the SYS1.PARMLIB data set that is pointed to by the
| master catalog. This SYS1.PARMLIB might be different from the
| SYS1.PARMLIB data set to which the LOAD parameter points.
| For more information about LOADxx, see the description of LOADxx in z/OS
| MVS Initialization and Tuning Reference.
| 3. The next character (character 7 of the LOAD parameter) specifies the prompting
| and message suppression characteristics that the system is to use at IPL. This
| character is commonly known as an initialization message suppression indicator
| (IMSI).
| Suppressing Informational Messages: Some IMSI characters suppress
| informational messages from the system console, which can speed up the
| initialization process and reduce message traffic to the console. It can also
| cause you to miss some critical messages, so you should always review the
| hardcopy log after initialization is complete.
| When the system suppresses informational messages, it displays the following
| messages:
| v Messages with descriptor codes 1, 2, 3, 11, or 12

1-4 z/OS V1R7.0 MVS System Commands

| v Write-to-operator with reply (WTOR) messages
| v Command responses
| v Synchronous messages that can indicate problems during initialization.
| It does not display the contents of a parmlib member, even if the L option has
| been specified.
| Prompting for Operator Responses: You can specify an IMSI character that
| tells the system to issue a MASTER CATALOG prompt, a SYSTEM
| PARAMETERS prompt, both, or none:
| v If the system issues a MASTER CATALOG prompt, the operator response
| overrides the values that are specified on the SYSCAT parameter in the
| LOADxx parmlib member.
| v If the system issues a SYSTEM PARAMETERS prompt, the operator
| response overrides the values that are specified on the SYSPARM parameter
| in LOADxx. Also, if LOADxx specifies the IEASYMxx parameter which in turn
| specifies a SYSPARM parameter for IEASYSxx, then the operator response
| also overrides the values that the SYSPARM parameter in IEASYMxx
| specifies.
| v If the system does not prompt the operator, the system uses the values
| specified in LOADxx. If the SYSCAT and SYSPARM statements are not
| specified in LOADxx, the system issues one or both prompts to obtain the
| missing information.
| Prompting for the Name of the Master Catalog: If you choose an IMSI
| character that tells the system not to prompt for the master catalog name, the
| system uses the name specified on the SYSCAT parameter in the LOADxx
| parmlib member.
| The default for the system parameter prompt is to use IEASYS00 in
| SYS1.PARMLIB, and the default for the master catalog prompt is to use
| SYSCATLG in SYS1.NUCLEUS.
| The following table shows the possible values for the IMSI character. The
| default value is period (.).
| Table 1-1. Possible Values IMSI Characters
| IMSI Display Informational Prompt for Master Prompt for System
| Character Messages Catalog Response Parameters Response
| period (.) or No No No
| blank
| A Yes Yes Yes
| C No Yes No
| D Yes Yes No
| M Yes No No
| P No Yes Yes
| S No No Yes
| T Yes No Yes
|
| 4. The last character (character 8 of the LOAD parameter) specifies the alternate
| nucleus identifier (0-9). Use this character at the system programmers direction.
| If you do not specify an alternate nucleus identifier, the system loads the
| standard (or primary) nucleus (IEANUC01) and an architectural extension of the
| nucleus (IEANUC11 or IEANUC21), unless the NUCLEUS statement is specified
| in the LOADxx member. For more information, see z/OS MVS Initialization and
| Tuning Reference.

Chapter 1. System Operations 1-5

| Also consider the following:
| 1. Decide whether to accept the system prompt indicator default. The default
| causes the system to suppress messages and not prompt the operator. You
| might miss critical messages during initialization, so you should review the
| hardcopy log.
| New installations might want to select prompt feature A (display all messages
| and prompt the operator) or M (display all messages but do not prompt
| operator) on the system control frame while validating changes and analyzing
| system errors during the initialization process. Specifying either A or M might
| increase message traffic.
| 2. Omit the LOAD parameter when you accept all the IBM-supplied defaults.
| 3. Each character in the LOAD parameter is positional. If you change any of the
| defaults you must retype the characters or use periods (....) to hold the
| positions.
| 4. You cannot leave any leading spaces blank, unless the defaults are accepted
| for the rest of the LOAD parameter.

| Explanation of the A=INITIALIZE SYSTEM CONTROL PROGRAM,

| A3 Field
| This field specifies the operator load function to IPL the MVS operating system.

| Selecting the operator load function causes the hardware to read an IPL (initial
| program loader) program into storage from the system residence volume. For this
| reason, loading and initializing the system is often called the IPL procedure or just
| IPL. Likewise, IPLing the system means loading and initializing the system.

| The IPL program is what actually loads the system software; if the IPL program
| does not get into storage or does not receive control properly, the entire load
| process stops and the processor pauses. If the IPL program does not finish
| properly, it puts the system into a disabled wait state with an error code in the
| low-order 12 bits of the program status word (PSW). To continue loading the
| system, display the PSW, note the error code, and follow the instructions for that
| code given in z/OS MVS System Codes. The processor operations manual tells you
| how to display the PSW.

Logging On to the System

Your installation can control the use of the system commands and access to the
MCS and SMCS consoles through the security authorization facility (SAF) and the
Resource Access Control Facility (RACF). Your installation can require operators to
use the LOGON command to log on to the system and identify themselves.

Your installation can specify the LOGON attribute for MCS and SMCS consoles in
two ways. First, a default LOGON attribute can be specified for all consoles active
on a system by specifying the LOGON keyword on the DEFAULT statement in the
CONSOLxx parmlib member. Second, individual consoles can override the default
LOGON attribute by specifying the LOGON keyword on the CONSOLE statement in
the CONSOLxx parmlib member. For more information on specifying LOGON
consult z/OS MVS Planning: Operations and z/OS MVS Initialization and Tuning
Reference.

Your installation can specify that LOGON is required by specifying

LOGON(REQUIRED) on the DEFAULT statement (for all consoles on the system)
or on the CONSOLE statement (for a single console). When LOGON is a system
requirement, you can issue commands only through the master console until RACF

1-6 z/OS V1R7.0 MVS System Commands

 is fully initialized and able to process logon requests. Until RACF is initialized, you
cannot issue any commands from any secondary console, with one exception. You
can issue the VARY MSTCONS command from a secondary console to establish
an alternate master console if you need operator intervention to complete RACF
initialization.

Once RACF is fully initialized, all operators are required to logon. The message
IEE187I prompts you for a userid and password. Optionally, you might enter a
group id and a security label. See LOGON Command on page 4-295 for more
information.

IBM recommends that SMCS consoles be LOGON(REQUIRED), either using the

system-wide DEFAULT(LOGON) specification or the CONSOLE LOGON
specification of the console.

Your installation can specify that LOGON is automatic by specifying LOGON(AUTO)

on the DEFAULT statement (for all consoles on the system) or on the CONSOLE
statement (for a single console). When LOGON is not a system requirement, after
the security product is fully initialized, the system will automatically issue an MCS
LOGON command to each active MCS or SMCS console; system operators may
log on to these consoles but are not required to do so. Automatic logon affects only
full capability consoles.

Your RACF administrator creates RACF user profiles for each operator. Each
operator can have access to different commands, consoles, data sets, and other
RACF-protected resources, according to the persons responsibilities. The RACF
administrator also creates RACF resource profiles that protect all operator
commands. If you need more information on creating profiles for operators,
consoles, MVS commands, and other resources, see the z/OS Security Server
RACF Security Administrators Guide.

Your installation can specify that LOGON is optional by specifying

LOGON(OPTIONAL) on the DEFAULT statement (for all consoles on the system) or
on the CONSOLE statement (for a single console). Code the OPTIONAL parameter
when your installation has selected consoles defined in RACF to require the
operator to log on.

z/OS MVS Planning: Operations has more information about controlling system
commands and consoles in a secure environment.

Initializing the System Software

Once the software is loaded into storage, it must be given specific starting values
before it can do work. These values are supplied through a LOADxx parmlib
member specified by the LOAD parameter on the system control (SYSCTL)
frame, or, depending on the installation hardware level, through the system console
or the NIP console during the initialization process.

In certain situations, the system prompts you to specify an alternate master catalog;
then it prompts for system parameters that are not specified in LOADxx. The
following two sections explain how to respond to those prompts.

Specifying an Alternate Master Catalog

During system initialization, unless the SYSCAT parameter is specified in the LOAD
parameter, the system issues the following message:
IEA347A SPECIFY MASTER CATALOG PARAMETER

Chapter 1. System Operations 1-7

 You must respond to this message. You can respond in one of two ways:
v If your installation uses the default member of SYS1.NUCLEUS, SYSCATLG, to
find the master catalog, press the ENTER key.
v If your installation uses an alternate member of SYS1.NUCLEUS, SYSCATnn, to
find an alternate master catalog, enter two characters for nn.

Specifying System Parameters Not Defined in LOADxx

The LOAD parameter can supply values not defined at system installation time. If
this is not done, you must supply them as system parameters in response to the
following system message:
IEA101A SPECIFY SYSTEM PARAMETERS FOR product-name

You must respond to this message. You can respond with specific system
parameters, such as
REPLY 00,CLPA,SYSP=83,LNK=(04,05,PQ),SYSNAME=AQ

However, a typographical error made in this response can lead to undesirable

system operation. To help avoid this situation, the system programmer can specify
system parameters in IEASYSxx parmlib members. If this has been done, you can
respond to message IEA101A in one of the following ways:
v To use the system parameters specified in the IEASYS00 parmlib member, press
the ENTER key.
v To use system parameters specified by IEASYSxx parmlib members along with
IEASYS00, use the SYSP operand on the REPLY command to specify the
2-character suffixes that identify the IEASYSxx parmlib members.
For example, to use the parameters specified in parmlib members IEASYSAA
and IEASYSBB along with IEASYS00, enter:
REPLY 00,SYSP=(AA,BB)
Note: Depending on the specific system parameter, a parameter value specified
in the alternate parmlib members supplements or overrides the value specified in
IEASYS00.
If the reply is longer than one line (there are 80 characters per line), you can follow
the last parameter with a comma or a blank and CONT. For details on how to
continue system parameters, see Specifying System Parameters on page 4-356 in
the description of the REPLY command in this book.

For details about parmlib members, see z/OS MVS Initialization and Tuning
Reference.

Setting the Time and Date

If the time-of-day (TOD) clock on the target processor is not set or if your
installation specifies the OPERATOR PROMPT parameter in the CLOCKxx member
of SYS1.PARMLIB that the system uses for initialization, the system prompts you
during initialization to set the correct time and date with message IEA886A and/or
message IEA888A. Message IEA886A asks you to specify values for the time and
date. Message IEA888A displays the time and date and lets you accept or change
these values. In response to either message, set an accurate time and date
according to your installations requirements.

For example, suppose the system issues:

IEA888A GMT DATE=1991.301,CLOCK=22.31.53
*00 IEA888A LOCAL DATE=1991.301,CLOCK=17.31.53 REPLY U, OR GMT/LOCAL TIME

1-8 z/OS V1R7.0 MVS System Commands

 The values in this message indicate that the local time is 5:31:53 P.M. on October
28, 1991 and that Greenwich mean time (GMT) is five hours later than local time in
your time zone. If the local time at your installation is really 8:00:00 A.M. on October
29, 1991, reply as follows:
R 00,DATE=1991.302,CLOCK=13.00.00,GMT

The system responds with:

IEA888A GMT DATE=1991.302,CLOCK=13.00.00
*00 IEA888A LOCAL DATE=1991.301,CLOCK=08.00.00 REPLY U, OR GMT/LOCAL TIME

Note that the system sets the local time but not the local date from the time and
date you specify. To set the local date, reply as follows:
R 00,DATE=1991.302

If the new GMT and local time values are still not accurate enough, you can reply
with new GMT time values now (and as many times as you need) to bring the
systems values closer to what your installation requires. When you are satisfied
with the systems values, reply as follows:
R 00,U

See REPLY Command on page 4-351.

Initializing MCS and SMCS Consoles

Message IEE612I appears on an MCS and SMCS console when it completes
initialization.

If you enter the command DISPLAY C,K (or D C,K), the system displays a summary
of the CONTROL commands. You can use these commands to change the
characteristics of the console. See Displaying CONTROL Command Functions on
page 4-112 for information about the DISPLAY C,K command.

Starting and Specifying Parameters for the Job Entry Subsystem

Even after the system is initialized, it cannot accept work until the job entry
subsystem (JES2 or JES3) is started. The system automatically starts JES2 or
JES3 if your installation provides this capability. Otherwise, you must issue the
START command. For further information about starting JES, see either z/OS JES2
Commands or z/OS JES3 Commands. See START Command on page 4-558.

Controlling the System

Controlling the operating system effectively, includes the following tasks:
v Display current system status, such as the number of active jobs and
teleprocessing functions, so you can take appropriate actions to operate the
system efficiently and to correct potential problems
v Display the status of devices and availability of paths.
v Communicate among several consoles.
v Communicate within a sysplex. In a sysplex, several MVS systems function
together to process work, and you might need to know about the operations of
more than one system in a sysplex.
v Set the time and change the system parameters.
v Use the system restart function to control certain system functions.
v Respond to message IEA502A.
v Respond to message BLW004A.

Chapter 1. System Operations 1-9

 v Activate a workload management service policy for a sysplex.

MVS provides system and subsystem commands that display job and system status
either when requested or continually at a regular interval. Other commands route
status information to one or more consoles and provide communication among
operators in a multiple-console environment, as well as communication with
time-sharing users. Many commands let you display information about all the
systems in a sysplex, and some commands allow you to control any target system
in the sysplex.

The following sections describe in detail how to control the system.

Displaying Current System Status

Using the DISPLAY command, you can display overview information about all
current system activity and detailed information about active batch jobs, started
tasks, system address spaces, and/or logged-on time-sharing users. (The DISPLAY
command in Chapter 4 describes the overview and detailed information you can
display.) The command produces a one-time display of status as it is at the time
you enter the command.

To help you keep up with the systems needs, you can enter the DISPLAY R
command to display system requests waiting for replies or actions, mount requests
not yet fulfilled, and devices waiting for operator intervention. You can use the
information in the display to take any necessary actions. See Displaying System
Requests on page 4-201 for information about the DISPLAY R command.

Using the MONITOR command, you can keep track of jobs starting and stopping. In
response to the MONITOR command, the system displays the job identification
whenever a job starts or stops. Using this command, you can also request that the
system notify you of TSO logons, JCL failures, and data set allocations. See
| MONITOR Command on page 4-338. You can also use the SETCON MONITOR
| command to enable or disable monitoring messages for jobs, TSO/E sessions, and
| data set allocations. See SETCON Command on page 4-399.

Displaying the Status of Devices and Availability of Paths

There are three commands that you can use to display the status of devices and
the availability of the paths these devices are on.

The DISPLAY U command allows you to keep track of the availability for allocation
of the following devices attached to the system:
v Channel-to-channel (CTC) links
v Direct access storage devices (DASDs)
v Graphic devices
v Magnetic tape units
v Communication equipment
v Unit record devices

This command displays device status and the job names and ASIDs of device
users. Knowing what jobs and ASIDs are using a particular device allows you to
determine whether you can take the device offline. See Displaying Device Status
and Allocation on page 4-236 for information about the DISPLAY U command.

The DISPLAY M command allows you to keep track of the availability of channel
paths and devices on these paths. See Displaying System Configuration
Information on page 4-166 for information about the DISPLAY M command.

1-10 z/OS V1R7.0 MVS System Commands

 The DEVSERV PATHS command can help you solve hardware or configuration
problems. The display includes the status of paths, the channel path ids, the logical
mode of devices, the number of data sets allocated on volumes, and volume serial
labels. Because the DEVSERV command causes the system to issue an I/O
request on paths to a device or devices, the resulting display reflects the current
physical state of the path. Comparable displays from the DISPLAY M command
reflect less recent information from the last use of MVS control blocks. For example,
assume that an I/O device is performing below normal and you suspect that some
paths to the device are offline. The DISPLAY M command might tell you that there
are four paths online to the device. The DEVSERV PATHS command might tell you
that there is actually only one online path. The DEVSERV command is more current
and thus more accurate. See DEVSERV Command on page 4-82 for information
about the DEVSERV command.

Communicating Among Several Consoles

The MSGRT command directs the output of displays to one or more consoles in the
system. You can route any display or message produced by the CONFIG, DISPLAY,
or MONITOR commands. You can also route the action of many CONTROL
commands. See MSGRT Command on page 4-342.

Using the SEND command, you can communicate with operators of other consoles
in your system, and you can send messages to remote terminals. See SEND
Command on page 4-371.

Sending Commands to Systems in a Sysplex

You can use the CONTROL V command to direct commands from a console to a
specific system in a sysplex. The CMDSYS parameter on the CONTROL V
command specifies which system receives all commands (not specifically routed
elsewhere by the ROUTE command) entered from a particular console. See
CONTROL Command on page 4-58.

You can use the ROUTE command to send commands to be processed on other
systems in the sysplex. See ROUTE Command on page 4-363.

You can use the VARY CN command to specify from what systems in a sysplex a
specified console receives unsolicited messages. Use the MSCOPE, AMSCOPE,
and DMSCOPE parameters for purposes of control. See VARY CN command on
page 4-605.

Some commands have an L=name parameter. You can use this parameter to
specify the name of a console on a different system in the sysplex. These
commands can communicate with the named console and receive messages from
that system.

Using Commands That Have Sysplex Scope

Commands that have sysplex scope have the following characteristics:
v They affect resources that are shared throughout the sysplex. Examples of such
resources include the Sysplex Timer, the coupling facility, couple data sets, and
certain DASD volumes.
v You can issue them from any system in the sysplex; the results are identical.
v The results of issuing them are sysplex wide without the need to use ROUTE
*ALL. You should not use any form of the ROUTE command to issue a
command with sysplex scope because doing so is redundant. Heres why:

Chapter 1. System Operations 1-11

 You use ROUTE to have a command issued on a particular system, group of
systems, or all systems in the sysplex. Using the ROUTE command is the
logical equivalent of walking up to a console attached to each system you
route to, and issuing the command from that console.
You do not need to issue a command with sysplex scope on a particular
system, group of systems, or all systems in the sysplex. You issue the
command once from any system.

Note that a command can have sysplex scope when you use particular parameters,
and not have sysplex scope when you use other parameters.

Commands that have sysplex scope are so noted in the documentation for that
command, and include those in the following table. If a command has All under
Conditions, then the command has sysplex scope under all circumstances and for
all variations.
Table 1-2. MVS System Commands With Sysplex Scope
Command Conditions
CHNGDUMP Has sysplex scope only when all systems are connected to
the same coupling facilities, and you specify
,SDUMP,SYSFAIL,STRLIST=.
CONTROL C,A All
CONTROL C,D Has sysplex scope only when you specify L=.
CONTROL M Has sysplex scope only when you do not specify MLIM,
UEXIT, LOGLIM, or APPLID.
CONTROL other Other parameters of CONTROL have sysplex scope only
when you specify L=.
DISPLAY CF Has sysplex scope only when displaying information about
the coupling facility and only for those systems connected to
the coupling facility. Does not have sysplex scope when
displaying an individual systems coupling facility
configuration information (coupling facility channels and
paths).
DISPLAY CNGRP All
DISPLAY CONSOLES Has sysplex scope unless you specify DISPLAY C,B or
DISPLAY C,U.
DISPLAY DUMP Has sysplex scope only when you issue the OPTIONS
parameter to display the results of a CHNGDUMP
...SDUMP,SYSFAIL,STRLIST= command.
DISPLAY EMCS Has sysplex scope, except when you specify STATUS=B or
STATUS=ERR. When you specify STATUS=FULL, consoles
from all systems will be displayed (for consoles that are not
active on the system where this command is processed,
some information will not be displayed).
DISPLAY GRS Has sysplex scope unless you specify SUSPEND. Also,
note the following about DISPLAY GRS,C and DISPLAY
GRS,RES: the output generated by these commands
includes both system-specific information (S=SYSTEM) and
sysplex information (S=SYSTEMS). The S=SYSTEM
information is valid only for the system on which you issue
the command. The S=SYSTEMS information is identical
regardless of the system on which you issue the command.

1-12 z/OS V1R7.0 MVS System Commands

 Table 1-2. MVS System Commands With Sysplex Scope (continued)
Command Conditions
| DISPLAY LOGGER Has sysplex scope when you use either L or C,SYSPLEX
| options.
DISPLAY OPDATA Has sysplex scope for the PREFIX operand and the
MONITOR operand (except for SPACE and DSNAME).
DISPLAY PFK Has sysplex scope only when you specify CN=.
DISPLAY R Has sysplex scope, but the output might be different on
different consoles, because the output of DISPLAY R is
dependent on the routing criteria for the console specified
by CN=. If you do not specify CN=, the routing criteria of the
console issuing the command is used. If you issue the
command in a program (by using the MGCRE macro) the
console you specify in the macro is used. If you specify a
console ID of 0, all retained messages are included in the
command response.
DISPLAY WLM All
DISPLAY XCF,ARMSTATUS Has sysplex scope provided all systems are using the same
ARM couple data set.
DISPLAY XCF,CF Has sysplex scope provided all systems in the sysplex are
connected to the same coupling facilities.
DISPLAY XCF,COUPLE Has sysplex scope as long as all systems are using the
same types of couple data sets, as specified on the TYPE
parameter (SYSPLEX, ARM, CFRM, SFM, LOGR, and
WLM.) If you do not specify the TYPE parameter, only
system-specific data is displayed.
DISPLAY XCF,GROUP All
DISPLAY XCF,POLICY Has sysplex scope as long as all systems are using the
same types of couple data sets, as specified on the TYPE
parameter (ARM, CFRM, SFM, and LOGR.)
DISPLAY XCF,STRUCTURE Has sysplex scope provided all systems in the sysplex are
connected to the same coupling facilities.
DISPLAY XCF,SYSPLEX All
MONITOR Has sysplex scope only when you specify L=.
MOUNT Has sysplex scope only when you issue the command
against an automatically switchable tape device.
REPLY All
RESET CN Issue the command from the system where the console was
active to avoid inconsistent sysplex results.
SEND Has sysplex scope only when sending to consoles; does not
have sysplex scope when sending to TSO users.
SET CNGRP Has sysplex scope provided all systems are sharing the
same parmlib data set.
SET DAE Has sysplex scope only when all systems are sharing the
same DAE data set and the same parmlib data set.
| SETLOGR FORCE Has sysplex scope when you use DELETE,LSName
| options.
SET GRSRNL Has sysplex scope only when all systems are sharing the
same parmlib data set.

Chapter 1. System Operations 1-13

 Table 1-2. MVS System Commands With Sysplex Scope (continued)
Command Conditions
SET SMS Has sysplex scope when you are issuing the command to
change the name of the ACDS or COMMDS. All systems in
the sysplex must be in the same SMS complex, and using
the same parmlib data set. If you are issuing the command
to start or restart SMS on a system, only the system on
which you issue the command is affected.
SETSMS Has sysplex scope only if you are changing the SCDS,
ACDS, or COMMDS, and only if all systems in the sysplex
are in the same SMS complex.
SETXCF FORCE Has sysplex scope only when all systems are connected to
the same coupling facility.
SETXCF COUPLE Has sysplex scope only when you specify PSWITCH,
ACOUPLE, or PCOUPLE, and all systems have access to
the specified couple data set.
SETXCF START|STOP Have sysplex scope only when you specify POLICY or
REBUILD.
STOPMN Has sysplex scope only when you specify L=.
SWITCH CN All
UNLOAD Has sysplex scope only when you issue the command
against an automatically switchable tape device.
VARY CN Has sysplex scope unless all of the following are true:
v You issue VARY CN(conspec),ONLINE without specifying
SYSTEM=.
v You do not specify SYSTEM= in the CONSOLxx parmlib
member that defines this console.
v The console has never been active in the sysplex.
VARY ...,MSTCONS Has sysplex scope when you issue VARY
conname,MSTCONS. Also has sysplex scope when you
issue VARY devnum,MSTCONS, but only if you use a
common IODF for the specified device across the sysplex.
VARY SMS, Has sysplex scope under these conditions only:
STORGRP|VOLUME v You specify (storgrp|volume,ALL) and all systems in the
sysplex are in the same SMS complex.
v You specify (storgrp|volume system) where system is a
system group, and the system group exactly matches the
sysplex (that is, none of the systems in the sysplex is
explicitly defined to SMS).
VARY XCF All
VARY WLM All

Sharing System Commands

MVS allows two or more systems in a multisystem environment to share commands
while retaining unique values in those commands. When two or more systems
share commands, you can view a multisystem environment as a single system
image from which you can perform operations for several different systems.

This section explains how to share system commands in a multisystem

environment, using:
v System symbols, which represent unique values in shared commands

1-14 z/OS V1R7.0 MVS System Commands

v Wildcards, which identify multiple resource names in commands.

Using System Symbols in Commands

System symbols represent the values in shared commands that are unique on
different systems. Each system defines its own values to system symbols, and
replaces the system symbols with those values when processing shared
commands.

To use system symbols in system commands, first see the section that describes
system symbols in z/OS MVS Initialization and Tuning Reference to understand the
types of system symbols, the elements that comprise them, and the general rules
for using them. Second, see the section on sharing system commands in z/OS
MVS Planning: Operations for information about planning to share commands. Then
read the rest of this section.

Display Static System Symbols: You can enter the DISPLAY SYMBOLS
command to display the static system symbols and associated substitution texts
that are in effect for a system. See Displaying Static System Symbols on page
4-232 for more information.

Know the Rules for Using System Symbols: The system enforces the following
rules when you use system symbols in system commands. They apply in addition to
the general rules for system symbols that are described in z/OS MVS Initialization
and Tuning Reference.
1. Substitution in a command begins after the command name. This means that
you cannot use symbolic variables to resolve to a command prefix or to a
command name. The command &Asyspref &mycmd would result in an error
message, for example.
2. If the issuing console has command association (CMDSYS) to another system,
the issuing system first transports the command to the associated system.
Substitution of any symbolic variables takes place on the receiving system.
3. If a command has a prefix defined with the command prefix facility (CPF), the
issuing system first transports the command to the system defined for that
prefix. Substitution of any symbolic variables takes place on the receiving
system.
4. After echoing and logging a command, the system examines the command
name. Certain commands receive special treatment:
v The system will not perform substitution for symbolics in a VARY
CN(*),ACTIVATE command.
v A DUMPDS command will not undergo substitution. The DUMPDS command
processor handles its own substitutions, at the time when it actually takes a
dump.
v For security reasons, the LOGON command does not support symbolic
substitution.
v For a REPLY command, substitution of any symbolic variables in the reply
text takes place on the system originally issuing the WTOR.
However, if the WTOR is synchronous (SYNCH = YES was specified, and the
synchronous WTO/R service displays the WTOR), the system does not
perform substitution of the reply text.
But, if the system issues the WTOR early during the initial program load
(IPL), that is, while the nucleus initialization program (NIP) is still in use:
The system performs substitution after it processes the requested
symbolics it reads from the parmlib. This means that the system will

Chapter 1. System Operations 1-15

 substitute symbolic variables in replies to WTORs it issues after issuing
the IEA347A SPECIFY MASTER CATALOG PARAMETER message.
The system will not issue message IEE295I for NIP-time replies that are
changed by symbolic substitution. Message IEE600I will reflect the
changed text.
v For a ROUTE command, the system issuing the command performs the
substitutions up through the specification of the destination system(s). Each
destination system completes the substitution of the text for the command.
For example, if you code the command
RO T=&T1,&SYSGRP1,F JOB&SYSCLONE,parms

the system issuing that ROUTE command will substitute the variables
&T1 and &SYSGRP1

and each system in the system group that &SYSGRP1 names will issue the
command
F JOB&SYSCLONE,parms

and each of those receiving systems will substitute its own value for
&SYSCLONE. See Using System Symbols in ROUTE Commands.
v You cannot use symbolic variables on an L= operand to aggregate the
command response when sending a command to more than one system. The
system will not substitute for the L= operand.
v For commands other than REPLY and ROUTE, the system issuing the
command performs the substitution for the text after the command name,
including comments.
5. You cannot use system symbols in commands that control batch jobs. Consider
converting batch jobs to started tasks, which can specify system symbols.
6. If substitution results in changing any command text, the system logs the new
text again and issues message IEE295I.
The system makes the original (pre-substitution) command text available to the
command installation exits and the subsystem interface (SSI). However, current
programs, if not modified, will see the substituted text.
When the system calls the command installation exits or SSI, if those exits
make any change to the command text, the system logs them again and issues
message IEE295I. However, it does not perform substitution again. It frees the
original command text, which means that it is no longer available in the system.

Cautions in Using System Symbols: The preceding rules mean that some forms
of command input will probably not produce the results you want:
1. Symbolic variables before or in a command name remain unsubstituted. The
system will process the command with the &variable; in the text, and probably
generate a COMMAND INVALID error message.
2. If a command exit changes the text and adds a new symbolic variable, the
system executes the command before substituting for the variable.
3. The following considerations apply when a command affects systems other than
the one issuing it:
v Except for REPLY, the substitution will reflect the issuing system. For
example, if
SYSVAR1 = (1,2)

on the system issuing the following VARY command, but

1-16 z/OS V1R7.0 MVS System Commands

 SYSVAR1 = (3,4)

on a system with the console consname attached, the command

VARY CN(consname),ROUT=&SYSVAR1

would result in the console consname receiving codes 1 and 2. If this

(unlikely) command is what you want, you should ROUTE it to the system
with consname attached.
| v The same logic applies to commands that accept the L=name-a parameter,
| that is, where you want the command output messages directed to a console
| (and display area) other than the one issuing the commands. Substitution of
| symbolic variables in commands occur on the systems where the commands
| are issued, not where the L= console is attached.
v Do not use symbolic variables in the L= parameter on the ROUTE
command. See the ROUTE command description in this manual.
v Understand the implications of using system symbols in commands that flow
through several systems in a multisystem environment. See Sharing
Commands That Flow Through Multiple Systems in OS/390 MVS Planning:
Operations for more information.

Determine Where to Use System Symbols: System symbols offer the greatest
advantage when two or more systems require different resources. This section
provides examples of how to specify system symbols when naming resources in
system commands.

Data Sets:

Assume that you want to display, on all systems in a sysplex, the local page data
sets that fit the following naming convention:
SY&SYSCLONE..PAGE.LOCAL

Instead of entering a different command to display the unique page data sets on
each system, you could enter the following command to display all the data sets
that fit the naming convention:
ROUTE *ALL,D ASM,PAGE=SY&SYSCLONE..PAGE.LOCAL

When each system processes the command, it substitutes the text that it has
defined for the &SYSCLONE system symbol. For example, if a sysplex consists of
two systems named SYS1 and SYS2, accepting the default value for &SYSCLONE
produces the following data sets:
D ASM,PAGE=SYS1.PAGE.LOCAL on system SYS1
D ASM,PAGE=SYS2.PAGE.LOCAL on system SYS2

Jobs:

When specifying system symbols in the source JCL for job names, first determine if
the jobs run as batch jobs or started tasks. If a job is a started task, you can specify
system symbols in the source JCL. If a job runs in batch, you cannot specify
system symbols in the source JCL; consider changing the job to run as a started
task.

Then, if a started task is to have multiple instances, determine if you want the
started task to have a different name for each instance. If each instance of a task
has a different name, your installation can easily identify the system on which each
instance runs.

Chapter 1. System Operations 1-17

 For started tasks, you can also specify system symbols on the JOBNAME
parameter on the START command that starts the task. For more information about
using system symbols in START commands, see the description of the START
command in z/OS MVS System Commands.

Using Wildcards in Commands

Wildcards allow you to use a single specification to indicate a number of resources
whose names match the wildcard pattern.

System commands use three kinds of wildcards:

v Multiple-character trailing asterisk (*): The * indicates zero, one, or more
characters, up to the maximum length of the string. This * must be at the end
and cannot appear alone. For example, ABC* matches ABC or ABCVWXYZ or
ABC1 or ABCZZZ. Use this wildcard in:
CANCEL
DISPLAY
MODIFY
SETPROG
SLIP parameters, as indicated in their descriptions
STOP
v Multiple-character asterisk (*) within the value: The * indicates zero, one, or
more characters, up to the maximum length of the string. This * can be in any
position and can appear alone to indicate all values. For example:
A*BC matches ABC or ACBC or AWXYZBC or A3BC
* matches all values
*BC matches BC or WXYZBC or ZZZBC
Use this wildcard in the JOBLIST and DSPNAME parameters of the SLIP
command.
v Single-character question mark (?): The ? indicates any single character. The
? can be in any position. For example:
A?C matches ABC or A1C
ABC?E?? matches ABCXEYZ or ABC1E23
?BC matches ABC and ZBC
Use this wildcard in SLIP parameters, as indicated in their descriptions.

In some SLIP command parameters, you can use more than one type of wildcard.
For example:
v A?C* matches ABC or AXCYZ or A5CZ2
v A*C? matches ABCD or AZZZZC1 or A123CZ or ACD

You can use wild cards to reduce the number of system commands needed for a
task. For example, you can enter one command to display information about all jobs
and started tasks beginning with the characters XYZ:
DISPLAY A,XYZ*

Setting the Time and Changing the System Parameters

Using the SET command, you can set the local time and date and change some
system parameters. See SET Command on page 4-378.

Using the System Restart Function

You can use the system restart function to:
v Restart the system after you have entered a QUIESCE command. (See
Quiescing the System on page 1-38.)

1-18 z/OS V1R7.0 MVS System Commands

 v Restart the system from a restartable wait state that is specified in z/OS MVS
System Codes.
v Restart the system when it behaves abnormally and you cannot terminate the
suspected unit of work with the CANCEL or FORCE commands. A system
behaving abnormally may be one that enters a nonvalid wait state or a disabled
loop. A nonvalid wait state exists when the wait state code in the PSW (IC) is not
listed in z/OS MVS System Codes and is not in the range of wait state codes
(FF0-FFE) reserved for other authorized applications. Symptoms of a disabled
loop are:
Nonproductive processing occurs and the PSW (IC) frequently displays the
same addresses.
All I/O and external interrupts are masked off for the system.

System Restart Procedure

To initiate the system restart function press the RESTART key on the hardware
operators console or specify one of several restart actions on an operator frame.
Refer to the hardware manual for your system for more detailed information about
your configuration. If the system has been quiesced or is in a valid restartable wait
state, the system restarts and continues processing the interrupted unit of work. If
the system had not been quiesced or is not in a valid restartable wait state then,
depending upon your system configuration, the system displays either message
IEA502A or BLW004A.

If the system does not recover as a result of your restart actions, follow your
installations procedures for recording system problems. When you have recorded
the system information, consult with your system programmer before taking further
action.

Responding To IEA502A
Reply reason code 0 when you suspect that a unit of work is causing a wait state
that is not valid or a disabled loop and you cannot terminate the suspected unit of
work by using the CANCEL or FORCE commands.
1. The system displays message IEA500A and waits for operator response.
IEA500A supplies information about the unit of work in progress.
2. Reply ABEND to abnormally terminate the interrupted program and invoke the
necessary recovery routines if the information describes the unit of work you
suspect has a problem.
3. Reply RESUME to end further restart processing and allow the interrupted work
to continue if the information does not describe the unit of work that you suspect
has a problem.

Repeat this process of invoking restart with REASON 0 until you interrupt the work
you suspect. Only then should you reply ABEND to abnormally terminate the
current work.

Note: The system terminates the work in progress without displaying any
information about it if you request the restart function with REASON 0:
v On a processor that cannot communicate with the master console or its
first designated alternate
v When the master console and its first designated alternate are not display
consoles

Chapter 1. System Operations 1-19

 Reply reason code 1 when you suspect a system problem that is not related to the
work currently in progress. The system diagnoses and repairs some problems that
might be causing it to behave abnormally. Among its actions, the system:
v Makes itself dispatchable.
v Checks the number of message buffers. The system notifies you if the maximum
number of buffers has been exceeded.
v Checks system activity. The system notifies you if there are no batch jobs or
time-sharing users.
v Restarts I/O on all channel paths.
v Checks and repairs critical data areas.

Note: Using reason code 1 might cause the system to immediately terminate
some address spaces. Use reason code 1 only under the direction of a
system programmer.

Normally, the system notifies you of anything it diagnoses or repairs when you
request the restart function with reason code 1. You only get this information on a
processor that can communicate with the master console or its first designated
alternate.

Responding To BLW004A
The system displays message BLW004A and waits for operator response.
BLW004A supplies information about the unit of work in progress.
1. Reply ABEND to abnormally terminate the interrupted program and invoke the
necessary recovery routines if the information describes the unit of work you
suspect has a problem.
Repeat this process of invoking restart procedure replying to BLW004A until you
interrupt the work that has the problem.
2. Reply RESUME to end further restart processing and allow the interrupted work
to continue if the message indicates that there are no batch jobs or time-sharing
users.
3. Reply RESUME to end further restart processing and allow the interrupted work
to continue if the message indicates that the WTO buffer limit has been
exceeded.
4. Reply REPAIR if you suspect a system problem that is not related to the work
currently in progress. The system diagnoses and repairs some problems that
might be causing the abnormal behavior.

Note: Replying REPAIR might cause the system to immediately terminate some
address spaces. Reply REPAIR only at the direction of the system
programmer.

Activating a Workload Management Service Policy

Important
Beginning with z/OS V1R3, WLM compatibility mode is no longer available.
Accordingly, the information below that pertains specifically to WLM
compatibility mode is no longer valid. It has been left here for reference
purposes, and for use on backlevel systems.

1-20 z/OS V1R7.0 MVS System Commands

 You can use the VARY WLM command to activate a named service policy for a
sysplex. The service policy must be defined in the workload management service
definition and must have been previously installed on the WLM couple data set.

You can also activate a workload management service policy by using the online
ISPF administrative application. Refer to z/OS MVS Planning: Workload
Management for more information or see your service administrator.

This command activates the named service policy on all systems in the sysplex,
regardless of the workload management mode in effect. However, only systems
operating in workload management goal mode will manage towards that service
policy. If there is an active service policy on a system running in compatibility mode,
and you use the MODIFY command to switch that system into goal mode, workload
management uses the service policy you activated.

For complete information on how to use the VARY command to activate a workload
management service policy, see Activating a Service Policy on page 4-647.

Switching Workload Management Modes

Important
Beginning with z/OS V1R3, WLM compatibility mode is no longer available.
Accordingly, you can no longer switch from one mode to another, as described
below. The information has been left here for reference purposes, and for use
on backlevel systems.

You can use the MODIFY WLM command to switch the workload management
mode in effect on a system. This command switches the mode of the system where
you issue the command.

Before switching into goal mode on any system in the sysplex, your service
definition should be complete and installed in the workload management couple
data set, and a service policy should have been activated.

For complete information on how to use the VARY command to activate a workload
management service policy, see Activating a Service Policy on page 4-647.

Controlling Time-Sharing
Time-sharing allows programmers at remote terminals to develop, test, and execute
programs without the turnaround delays that occur when they submit jobs to a
computer center. With time-sharing, a large number of jobs can share the resources
of a system concurrently, and remote terminal users can exercise primary control
over the execution of their jobs. Therefore, we can define time-sharing as the
shared, conversational, and concurrent use of a computing system by a number of
users at remote terminals.

Time-sharing in z/OS is provided by TSO/E. For more information about TSO/E see
z/OS TSO/E Users Guide.

You can display information about logged-on time-sharing users by using the
DISPLAY command. You can keep track of terminal users logging on and off the
system by using the MONITOR command. In response to the MONITOR command,

Chapter 1. System Operations 1-21

 the system displays the user id for each LOGON and LOGOFF. To stop the
systems monitoring of terminal use, issue the STOPMN command.

To communicate with time-sharing users you can use the SEND command to:
v Send messages to specific users or all users who are receiving messages
v Send messages to specific users or to all users logging on to the system
v Save messages in the broadcast data set
v List messages in the broadcast data set
v Delete messages from the broadcast data set

The broadcast data set, SYS1.BRODCAST, has mail and notices sections.

Controlling Jobs
A job is the basic unit of work for the system. Job control language (JCL) identifies
a job to an operating system and describes the jobs resource requirements. The
JOB JCL statement identifies a jobs beginning and contains such information as:
v Job name
v Job account number
v Job class
v Job priority.
Using job-related commands, you can start, stop, or cancel a job. You can also
modify a jobs parameters and performance group and restart a job that has failed.
There are two kinds of jobs in the system: queued jobs and jobs that are selected
on demand. Queued jobs are managed by JES. Jobs that are selected on demand
(referred to as demand-selected) are created as the result of START, MOUNT, and
LOGON commands.

Starting a Job
Using the START command, you can start jobs from the console. You can also use
the START command to cause the JES internal reader facility to read a job from a
tape or direct access volume.

Stopping a Job
Using the STOP command, you can stop a job if the programmer has coded a stop
routine in the program.

Cancelling a Job
Using the CANCEL and FORCE commands, you can cancel a job that is executing.
If the job is not currently executing, use a subsystem command to cancel it.

Passing Information to a Job

Use the MODIFY command to pass information to a job. This information may be
used by the currently running program. Note that you can only pass information that
is already defined in the currently running program.

Note to Programmers: For more information, see the section on communicating

with a program using EXTRACT or QEDIT in z/OS MVS Programming: Authorized
Assembler Services Guide.

Restarting a Job
Once a job is executing, it might end abnormally because of a hardware,
programming, or system error. This might happen any time during program

1-22 z/OS V1R7.0 MVS System Commands

 execution. Valuable machine time would be lost if an abnormal end occurred during
one of the last job steps of a multistep program or in the middle of a long job step,
and execution had to start again at the first job step. There are two ways of
avoiding this problem: automatic restart and deferred restart.

For JES2 jobs and JES3 jobs, the checkpoint/restart feature of the system allows a
job that ends abnormally to restart either at the beginning of a job step or at a
checkpoint within the current step. The programmer submitting the job provides for
an automatic restart or a deferred restart.

Automatic Restart
If the programmer submitting the job has provided for an automatic restart and the
job ends abnormally, you receive the following system message:
* id IEF225D SHOULD jobname.stepname.procedure checkid RESTART

This message allows you to prevent repeated restarts at the same checkpoint or job
step.

When this message appears, use the REPLY command to respond YES, HOLD, or
NO, as follows:
v Reply YES if the restart is to be performed at a specific checkpoint or job step for
the first time. (If it is a job step restart and the step to be restarted used a card
input data set that was not part of the SYSIN stream, you must return to the
appropriate hoppers all cards read by the job step before it ended abnormally. If
it is a checkpoint restart, follow the programmers instructions for replacing the
input cards.)
v Reply HOLD if you want to defer the restart: for example, to permit another job to
run first. You must issue the appropriate subsystem command when you are
ready to restart the job. Also, if you want, you can cancel the job. However,
cancelling the job can cause unrecoverable paging space or the failure of certain
data sets to be deleted if the job was using virtual I/O.
v Reply NO if a restart at a specific checkpoint or job step has been requested
repeatedly. When your reply is NO, and the programmer wants a restart to be
performed, he must resubmit the job for a deferred restart.

If the programmer specifies VIRTUAL=REAL (V=R), the job is processed entirely in

central storage; it is not paged out. For a V=R job, the restart might be delayed
while the system waits for the allocation of storage. If another job is using the
required storage, you get no message, only a delay. Enter the DISPLAY A,L
command to see if a system task or another job is using the storage required by the
job with a V=R region. You can then stop or cancel the conflicting task or job.

Note: Any operator commands in the input stream of the job step being restarted
are not executed.

Deferred Restart
If the programmer submitting the job has provided for a deferred restart and the job
ends abnormally, the programmer must resubmit the job for the deferred restart. To
restart the job, the programmer must provide a restart deck for submission to the
system through the system input reader. The JCL statements to be included in the
restart deck are described in detail in z/OS MVS JCL Users Guide.

If you change the device configuration of your system after a job ends abnormally,
restart the job carefully. For example, enough devices must be available to satisfy
the needs of the job step being restarted. The system under which a step restart is

Chapter 1. System Operations 1-23

 run need not be the same as it was for the jobs original execution. However, a
checkpoint restart should be run under the original system unless the alternate
system can meet the following restrictions:
v The job entry subsystem is the same.
v The release number is the same.
v The link pack area modules in use at the checkpoint reside in the same storage
locations.
v An area of storage identical to the original area is available to a V=R job.

If the required storage is not available, the system cancels the restart and you
receive the following message:
IEF209I VIRTUAL STORAGE UNAVAILABLE FOR jobname.stepname.procedure

Required storage might not be available for one of the following reasons:
v The link pack area expands into the required storage. This expansion can occur
if an IPL has been performed between the original execution of the job and the
restart. If it does occur, contact your system programmer for a respecification of
the system parameters and reIPL using the new values.
v The system storage area expands into the required storage. When this
expansion occurs, contact your system programmer for a respecification of the
SQA and CSA system parameter and reIPL using the new values.

When a job restarts correctly, you receive two messages: IEF006I JOB
RESTARTING and IEF008I JOB RESTARTED. If, for V=R jobs, these messages do
not appear, enter DISPLAY A,L to see if a system task or other job is using the
required storage. You can then stop or cancel the conflicting job. The system might
ask you to mount data volumes other than those required at the beginning of the
job. In addition, any card input data sets that have been used by the failing job step
must again be made available to the system.

For more information on deferred restart, see z/OS DFSMSdfp Checkpoint/Restart.

Controlling Started Tasks

A started task, like a job, is a basic unit of work for the system. However, started
tasks differ from jobs in that started tasks are always demand-selected; that is, the
operator or a program must take action to initiate a started task.

There are several ways to initiate started tasks:

v With a START command, described in Chapter 4 of this book.
v Via TSO/E logons. For information on using TSO/E logons, refer to the TSO/E
publications.
v With ASCRE (address space create) macros in programs. For information on
how to use the ASCRE macro, refer to z/OS MVS Programming: Extended
Addressability Guide.

Both the START command and the ASCRE macro create an address space. A
START command and an ASCRE macro started via a START command each will
look for a program that has a procedure in SYS1.PROCLIB; that program will be
the first to run in the ASCRE-created address space. Essentially, using ASCRE is
similar to a started task.

For a started task, the system:

1-24 z/OS V1R7.0 MVS System Commands

 v Locates the JCL that starts the task
v Defines the tasks address space
v Processes the JCL.

For a started task, operators can do the following:

Task For information, refer to:

Cancel the started task CANCEL Command on page 4-19
Display status about the started task DISPLAY Command on page 4-99
Force the started task FORCE Command on page 4-284
Modify the started task MODIFY Command on page 4-303
Name the started task START Command Starting a System Task
from a Console on page 4-558 (JOBNAME=
parameter)
Start the started task START Command Starting a System Task
from a Console on page 4-558
Stop the started task STOP Command on page 4-573

Controlling System Information Recording

The system records information that is later used for billing, accounting, or
diagnostics. Among the facilities that record system information are:
v System management facilities (SMF)
v System trace
v The generalized trace facility (GTF)
v Master trace
v Component trace
v The logrec recording medium

The system also records information in the system log and/or the operations log.
See z/OS MVS Planning: Operations for more information.

In addition to these facilities, JES2 and JES3 have their own event trace facilities.
These trace facilities are described in detail in z/OS JES2 Commands and z/OS
JES3 Commands.

System Management Facilities

System management facilities (SMF) consists of system routines and optional
user-written exit routines that collect, format, and record system and job-related
information.

The information gathered by SMF and user-written exit routines is recorded on

direct access volumes in one of the SMF data sets. These data sets, called primary
and secondary data sets, must be online at system initialization. At that time, SMF
uses the primary data set as the active recording data set unless it is full. If the
primary data set is full, SMF checks each data set in the order it is listed until it
finds one that is not full. SMF then uses this data set as the active recording data
set and requests that the operator dump all data sets that are not empty.

When the active recording data set becomes full, SMF automatically switches
recording from the active SMF data set to an empty secondary SMF data set,
passes control to the SMF dump exit, IEFU29, and issues a message to indicate

Chapter 1. System Operations 1-25

 that the data set needs to be dumped. Use the SMF dump program, IFASMFDP, to
dump the full SMF data set and to reset the status of the dumped data set to empty
so that it can be used again for recording.

Error Recovery

If an I/O error occurs while SMF is writing to one of the SMF data sets, you receive
a message and SMF switches to one of the empty secondary data sets.

Switching the SMF Data Sets

To prepare an SMF data set for dumping before it becomes full, the operator
normally uses the SWITCH SMF command to switch from the current data set to
another data set. For the switch to be successful, there must be an inactive data
set that is empty. Therefore, use the DISPLAY SMF command to verify that there is
at least one alternate data set before issuing the SWITCH or HALT command.

The HALT EOD command also prepares an SMF data set for dumping, but use it
only when you intend to quiesce the system in preparation to shut down. Do not
use HALT when you intend to keep the system running. HALT EOD will close the
system log and stop SMF recording.

Restarting SMF

Because SMF runs in its own address space, you can restart SMF with the SET
SMF command. When you enter that command, this message appears:
IEE980I SMF IS BEING RESTARTED

When the restart is complete and recording starts, the following message appears:
IEE360I SMF NOW RECORDING ON SYS1.MANx

If the SET SMF command abends while updating the SMF parameters, it might be
necessary to terminate the SMF address space and restart SMF. If the system
programmer determines that it is necessary to terminate the address space, issue:
FORCE SMF,ARM

To restart SMF after the SMF address space terminates, issue the SET SMF
command again, specifying a SMFPRMxx parmlib member containing different
parameters.

System Trace
System trace is a part of the operating system that records, for diagnostic purposes,
events that occur during system initialization and operation. To record events,
system trace provides three types of tracing: address space, branch, and explicit
tracing. System trace can be used between subsystem initialization and the start of
the generalized trace facility (GTF). For information on controlling system trace, see
TRACE Command on page 4-587.

The Generalized Trace Facility

The generalized trace facility (GTF), like system trace, gathers information used to
determine and diagnose problems that occur during system operation. Unlike
system trace, however, GTF can be tailored to record very specific system and user
program events. For information about starting and stopping GTF, see START

1-26 z/OS V1R7.0 MVS System Commands

 Command on page 4-558 and STOP Command on page 4-573. For information
about using GTF, see z/OS MVS Diagnosis: Tools and Service Aids.

Master Trace
Master trace is a diagnostic aid that maintains a trace table of console messages in
virtual storage. When master trace is active, the master trace table is embedded in
dumps that have the TRT option or contain the master schedulers private address
space. Master trace can eliminate the need to submit a portion of the system log to
IBM if there are problems in message processing. It also can ensure that the
messages accompanying a dump are the ones that correspond to the problem. The
TRACE command controls master trace. For a more detailed description of master
trace, see z/OS MVS Diagnosis: Tools and Service Aids.

Component Trace
Component trace is a diagnostic aid that system programmers can use to trace the
action of certain system components. Component trace enables the programmer to
use the TRACE command to start and stop component trace. The components that
use the component trace command must first invoke the define component trace
service and define the name of the component requesting the service and the name
of the start/stop routine that will get control when the TRACE operator command is
issued.

Logrec Recording Medium

When an error occurs, the system records information about the error in either the
logrec data set or a sysplex-wide logrec log stream. The diagnostic information
provides a history of all hardware failures, selected software errors, and selected
system conditions.

Use the records in the logrec data set or the logrec log stream as a companion to
dump data. The information in the records will point the system programmer in the
right direction while supplying symptom data about the failure.

For more information about log streams, see z/OS MVS Programming: Assembler
Services Guide. For more information about initializing a logrec data set or setting
up a logrec log stream, see z/OS MVS Diagnosis: Tools and Service Aids.

Controlling Automatic Tape Switching

In a sysplex, there are MVS operational considerations for two types of tape
devices:
v A dedicated tape device is varied online to one system at a time. For a second
system to use that same device, an operator issues VARY commands (first VARY
OFFLINE, then VARY ONLINE) to make the device available to the second
system.
v An automatically switchable tape device can be online to more than one
system at a time. For one system to use an automatically switchable tape device,
then another system to use the same device, an operator does not have to issue
any VARY commands. In many ways, automatically switchable tape devices are
similar to JES3-managed devices. They require that the systems in the sysplex
communicate with each other.

Chapter 1. System Operations 1-27

 Through system commands, the operations staff plays a key role in setting up and
maintaining automatic tape switching (that is, using automatically switchable tape
devices). For example, a device is automatically switchable after the following
operational actions are taken:
1. The device is defined as automatically switchable.
The VARY AUTOSWITCH command, as described in Defining Automatically
Switchable Devices on page 1-29, turns the AUTOSWITCH attribute on and off.
2. The device is varied online through the VARY ONLINE command.
3. Prior to z/OS Release 2, the connection between participating systems and the
coupling facility is active and an IEFAUTOS structure is defined in the active
coupling facility resource management (CFRM) policy.
Automatically switchable devices are managed using information stored in a list
structure named IEFAUTOS, which resides on the coupling facility. Through this
structure, the systems track the availability of automatically switchable tape
devices, select appropriate tape devices to satisfy requests, and control their
use. The structure is defined in the CFRM policy and the SETXCF
START,POLICY command makes the policy active.
For systems at z/OS Release 2, with APARs OW51103 and OW50900 installed,
and higher, the ATS STAR function uses global resource serialization and XCF
services to maintain serialization when allocating shared tape devices instead of
the IEFAUTOS structure. The system maintains information about the use of an
autoswitchable device in the Allocation address space (ALLOCAS).

The following section describes the coexistence behavior when some systems are
at z/OS R2 (with the appropriate PTFs) or higher and are using ATS STAR to
manage autoswitchable devices and other systems are at a level lower than z/OS
R2 and are using the IEFAUTOS coupling facility structure for autoswitchable
device management. Throughout this section, the term participating systems refers
| to systems using the same tape sharing method. The term nonparticipating
| system refers either to systems that use tape sharing methods (IEFAUTOS vs. ATS
| STAR) that are different from the participating systems , or systems that have
| devices dedicated (that is, not defined as autoswitchable).

Participating and nonparticipating systems take turns using the automatically

switchable devices:
v If a participating system requests an automatically switchable device that is
| allocated on another participating system, the system issues message IEF238D.
| Message IEF238D prompts the operator to reply with a device name, wait, or
| cancel.
| v If a nonparticipating system successfully assigns an autoswitchable device, the
| device becomes assigned to a foreign host to the participating system. The
| participating system issues message IEF292I to indicate this state when it tries to
| assign the device and finds it is already assigned to a foreign host. If
| participating systems try to allocate the device during this time, the system issues
| message IEF284I and the job step or dynamic allocation request is failed. The
| autoswitchable device remains assigned to a foreign host until the participating
| system reclaims it by successfully assigning it and issues message IEF294I.
| Some automatic tape switching messages use the term foreign host to describe
| a nonparticipating system. The messages appear when a system using the
| device is not connected to the same IEFAUTOS structure or is connected to the
| structure but is using the device as a dedicated device.
| Information in IEFAUTOS and ATS STAR is not updated when a nonparticipating
| system allocates a device that is defined as automatically switchable. You cannot

1-28 z/OS V1R7.0 MVS System Commands

| obtain this information with the DISPLAY U,,AS command. Participating systems
| are unaware that the device is not available to them until an attempt is made to
| assign the device, such as when the device is allocated. At this point, the
| information is updated and can be displayed using the DISPLAY U,,AS
| command.

Defining Automatically Switchable Devices

To define a device as automatically switchable, the device must be in a
varied-offline state. Use the following command:
VARY device,AUTOSWITCH,ON

The detailed description of this command is in Defining a Tape Device as

Automatically Switchable on page 4-618.

The AUTOSWITCH definition lasts for the duration of the IPL. Only if the device has
been defined through HCD does the definition persist longer than the duration of
the IPL. If HCD turns the attribute on, and the VARY AS command turns the
attribute off, the attribute will be on again at the next reIPL.

The ESCON manager and the IEEVARYD programmable interface can also set the
AUTOSWITCH attribute on and off.

Displaying Information About Automatically Switchable Devices

The DISPLAY U,,AUTOSWITCH command summarizes the status of automatically
switchable devices about which the coupling facility (that is, the IEFAUTOS
structure) has information. The display includes the following information:
v The name of the system to which the device is allocated
v The name of the job
v Volume serial number, if one is mounted and the device is allocated.

If a device is offline to the issuing system, the display shows OFFLINE in the
status field and the display provides no other information about the device.

The following example shows information that appears in response to DISPLAY

U,,AUTOSWITCH. Ten devices are defined automatically switchable in the sysplex.
Four of those devices (identified by A in STATUS column) are allocated to jobs
running on SYS5 and SYS6; two of the devices (identified by OFFLINE in the
STATUS column) are varied offline to the issuing system; and the status of the
other four devices is not known.

Chapter 1. System Operations 1-29

 - d u,,as
IEE343I 12.24.59 UNIT STATUS FRAME LAST F *E SYS=ALLOC5
UNIT TYPE STATUS SYSTEM JOBNAME ASID VOLSER VOLSTATE
05A8 348S A SYS5 TAPE02 0012 PUB/REMOV
05A9 348S A SYS5 TAPE02 0012 PUB/REMOV
05AA 3480 OFFLINE
05AB 3480 /REMOV
05AC 3480 /REMOV
05B8 349S A -CA SYS6 TAPE01 012E PUB/REMOV
05B9 349S A SYS6 TAPE01 012E PUB/REMOV
05BA 3490 OFFLINE
05BB 3490 /REMOV
05BC 3490 /REMOV

Figure 1-2. Example of a Successful Response to a DISPLAY AUTOSWITCH Command

The syntax of the DISPLAY AUTOSWITCH command is in Displaying Device

Status and Allocation on page 4-236.

If you issue DISPLAY U,,AUTOSWITCH and the system-to-IEFAUTOS connection

is broken, you receive the following message:

- d u,,as
IEE343I 15.09.07 UNIT STATUS 990
UNIT TYPE STATUS SYSTEM JOBNAME ASID VOLSER VOLSTATE
AUTOSWITCH STATUS UNAVAILABLE - ALLOCATION COUPLING
FACILITY STRUCTURE NOT AVAILABLE

Figure 1-3. Example of an Unsuccessful Response to a DISPLAY AUTOSWITCH Command

If you want to find out the status of a device that is assigned to a nonparticipating
system, issue the DISPLAY U,,, command on each system that could have varied
the device online, including the participating systems.

Interacting with System Functions

Most resource allocation, error recovery, and system monitoring functions in MVS
are automatic. Sometimes, however, the system requests your assistance, takes
certain actions that you must understand and/or correct, or issues messages that
make you aware of internal processing. So that you can plan your actions carefully
and respond appropriately to system messages, you need to know how to interact
with the following system functions:
v Device allocation
v Hot I/O detection
v Device boxing

Device Allocation
Device allocation is the assignment of input/output devices and volumes to job
steps. Requests for device allocation come from data definition (DD) statements
and dynamic device allocation requests.

Data definition (DD) statements can be entered into the system by:
v Job input to the JES reader
v Jobs submitted through the TSO SUBMIT command
v Started tasks

1-30 z/OS V1R7.0 MVS System Commands

v The MOUNT command
v TSO LOGONs
v APPC transactions

Dynamic device allocation/unallocation requests, in contrast, originate within

executing programs.

While performing device allocations, the system might ask you to:
v Mount or dismount volumes
v Make decisions (for example, to bring a device online immediately or to wait)

To control the amount of work you have to do related to device allocation, you might
want to restrict device allocation requests.

To control device allocation requests from data definition (DD) statements, you
might restrict each of the forms of input for these statements (for example, by
holding the reader, or by setting a maximum LOGON count). Because they originate
within executing programs, however, you cannot control dynamic device
allocation/unallocation requests.

Device Assignment
Operationally, the assignment of devices is influenced by:
v The online/offline status of the device. Generally, to be allocated to job steps,
devices must be online. Exceptions are (1) when the online test executive
program (OLTEP) or a similar testing program is running and (2) when
teleprocessing devices are allocated. You can bring offline devices online with the
VARY command or in response to the allocation recovery message, IEF238D.
v The MOUNT attribute. The MOUNT attribute, which applies only to tape or DASD
devices, is influenced by the MOUNT and UNLOAD system commands, and,
during initialization, by entries in the VATLSTxx parmlib member. Allocation
requests that can be satisfied by mounted devices are processed quickly and
without your intervention.
v The USE attribute. A parameter of the MOUNT command, the USE attribute
affects the type of data sets that can be allocated on a tape or DASD volume.
The USE attribute can also be set during initialization by entries in the VATLSTxx
member of parmlib. Having a proper mix of volumes with various USE attributes
reduces the amount of volume mounting.

The information from data definition (DD) statements determines the input/output
resources to assign to a job or job step and the volumes that are required. If a
requested volume is not mounted, the system issues a mount message asking you
to mount a specific volume or scratch volume. If you mount the wrong volume, the
system finds out as soon as it reads the volume label. The system unloads the
volume and repeats the mount message.

When you know that several jobs are going to need a volume, use the MOUNT
command to reserve that volume on a device. Allocation processing is faster when
the required volume is reserved rather than removable. The system does not
demount volumes reserved by a MOUNT command until you issue an UNLOAD
command.

Note: Do not use the MOUNT command for devices managed by JES3. See z/OS
JES3 Commands.

Chapter 1. System Operations 1-31

 Never mount a blank tape volume unless specifically directed to do so because the
system scans the entire volume for a tape label and this scanning wastes time. If
an unlabeled tape is needed, write a tapemark to avoid unnecessary scanning. After
you mount the tape volume and ready the drive, the system reads the volume label.
If an incorrect volume is mounted, the system unloads the incorrect volume and
repeats the mounting message.
Notes:
1. Occasionally, you receive two mount messages for the same volume, one
starting with IEF and the other with IEC. Treat the two messages as though they
were one. The second is a reminder.
2. When referring to I/O devices in the devnum parameter of system commands,
use the unique 3-digit or 4-digit device number for each device. You can
precede the device number with a slash (/). The slash is optional on many
commands, but required for 4-digit device numbers on some commands, such
as MOUNT and START.
3. Your installation can define symbolic group names of one to eight characters to
be used by programmers in data definition (DD) statements. The number of
devices associated with a symbolic name can range from one to the total
number of devices in your installation. The symbolic name allows the devices to
be grouped according to the attributes your installation considers significant. Do
not use these symbolic names in system commands.
4. Make sure there are sufficient work volumes available to satisfy requests for
temporary data sets at peak loads. A shortage of work volumes can cause the
system to request additional scratch volumes. Balance work volumes across
channel paths to increase system efficiency.

Automatic Volume Recognition

Automatic volume recognition (AVR) allows you to mount labeled volumes on
unused drives not managed by JES3. The system recognizes and remembers these
volumes, and assigns the drives to later job steps as required.

Hot I/O Detection

Hot I/O refers to the repeated I/O interruptions that result from hardware
malfunctions. Because it can cause the system to loop or to fill the system queue
area with I/O control blocks, hot I/O needs to be detected quickly and corrected.

When the number of repeated interruptions exceeds an installation-defined

threshold value, the system assumes there is a hot I/O condition. If your installation
has set up hot I/O recovery defaults that the system can use, the system issues
message IOS109E and attempts to recover from the hot I/O condition. (See z/OS
MVS Initialization and Tuning Guide and z/OS MVS Recovery and Reconfiguration
Guide for information on setting up hot I/O recovery defaults.) If your installation has
not set up hot I/O recovery defaults, the system issues one of the following
messages, if possible, or loads one of the following restartable wait states and
prompts you to take action:
IOS118A or IOS111D HOT NON-RESERVED DIRECT ACCESS DEVICE
(Wait state 111)
IOS119A or IOS112D HOT RESERVED DIRECT ACCESS DEVICE
(Wait state 112)
IOS117A or IOS110D HOT NON-DIRECT ACCESS DEVICE
(Wait state 110)

When you take action, try to solve the problem at the lowest possible level. That is,
try to correct the problem at the device first and then at the control unit. You could
power the device off and on. If that does not help, you could reset the control unit if

1-32 z/OS V1R7.0 MVS System Commands

 the affected device is not a direct access device. If these actions do not correct the
problem, you might have to physically disconnect the device or control unit.

Whatever action you take, tell the system what you are doing by responding to the
prompting message or restartable wait state. Use LookAt (see Using LookAt to
look up message explanations on page xviii) or use the MVS System Messages
books for information about IOS messages, and z/OS MVS System Codes for a
detailed explanation of the restartable wait states and your response to them.

Device Boxing
In certain error recovery situations and in response to certain commands, the MVS
system can box an I/O device. Once a device enters a boxed state, the system:
v Immediately terminates I/O in progress on the device
v Rejects future I/O requests (by a user or by the system) to the device as
permanent I/O errors
v Rejects any attempts to allocate the device
v Puts the device in pending-offline status

The system boxes a device:

v When it detects hot I/O on the device and the device cannot be recovered
v When, because of a channel path error, it takes the last path to the device offline
v When, because of a channel path error, it releases a reserve or assign on the
device
v When it releases an unconditional reserve for the device
v When you issue a VARY OFFLINE command with the FORCE option for the
device
v When you issue a CONFIG OFFLINE command with the FORCE option for a
channel path, and the command releases a hardware reserve or assign, or
removes the last path to the device
Notes:
1. Because you might release a reserve or assign on a device and cause a data
integrity exposure, be sure to use the VARY OFFLINE and CONFIG OFFLINE
commands with FORCE only in emergency situations.
2. When you fix whatever caused the system to box a device, you can take the
device out of the boxed state at any time by issuing VARY device ONLINE.
Once the VARY command takes effect, the device is again available for IOS
and any subsequent allocations (i.e., an allocation done in another step or job,
or another dynamic allocation). Note that after the VARY command takes effect,
the device is not considered for the current allocation.
You can make a boxed alias unit control block (UCB) of a parallel access
volume available using the DEVSERV, QPAVS command.
3. You cannot take a boxed device out of the boxed state by replying with the
device name to the allocation recovery message, IEF238D.

Command Flooding
| Starting with APAR OW45398, commands that run in the *MASTER* or CONSOLE
| address space are divided into six command classes. In each class, only 50
commands can execute at one time. Any additional commands in that class must
wait for execution.

Chapter 1. System Operations 1-33

 To manage the number of commands that are awaiting execution, the system
operator can issue the CMDS command to display the status of commands, remove
selected commands that are awaiting execution, or cancel commands that are
executing. When a command is removed before execution, the command issuer
receives message IEE065I COMMAND NOT EXECUTED, CMD=command instead
of the usual command response message. When a command is cancelled, the
command is terminated with an ABEND code 422, reason code 00010301.

Class M1 Commands
Class M1 commands are commands that are attached in the *MASTER* address
space, and are considered essential to clearing a backlog of other commands:
v DISPLAY GRS
v DISPLAY MPF
v DISPLAY SLIP
v DISPLAY XCF
v DUMP
v DUMPDS
v QUIESCE
v SET
v SETXCF
v SLIP
v VARY XCF

Class M2 Commands
Class M2 commands are ordinary attached commands that run in the *MASTER*
address space:
v ACTIVATE
v CONFIG
v DEVSERV
v DISPLAY APPC
v DISPLAY ASCH
v DISPLAY ASM
| v DISPLAY CEE
v DISPLAY CF
v DISPLAY CNGRP
v DISPLAY DLF
v DISPLAY DUMP
v DISPLAY ETR
v DISPLAY IOS
v DISPLAY IPLINFO
v DISPLAY LLA
v DISPLAY LOGGER
v DISPLAY LOGREC
v DISPLAY MATRIX
v DISPLAY MMS
v DISPLAY OMVS
v DISPLAY PARMLIB

1-34 z/OS V1R7.0 MVS System Commands

 v DISPLAY PROD
v DISPLAY PROG
v DISPLAY RTLS
v DISPLAY SMF
v DISPLAY SMS
v DISPLAY SSI
v DISPLAY SYMBOLS
v DISPLAY TCPIP
v DISPLAY TRACE
v DISPLAY U
v DISPLAY UNI
v DISPLAY WLM
v HALT EOD
v IOACTION
v LIBRARY
v LOGON (not MCS)
v MOUNT
v PAGEADD
v PAGEDEL
v RESET jobname
v SET UNI
| v SETAPPC
v SETETR
v SETGRS
v SETIOS
| v SETLOGR
v SETLOAD
v SETLOGRC
v SETOMVS
v SETPROG
v SETSMF
v SETSMS
v SETSSI
v START
v SWAP
v SWITCH SMF
v TRACE
v UNLOAD
v VARY GRS
v VARY ONLINE / OFFLINE
v VARY PATH
v VARY SMS
v VARY SWITCH
v VARY TCPIP
v VARY WLM

Chapter 1. System Operations 1-35

| Class M3 Commands
| Class M3 commands are ordinary attached commands that run in the *MASTER*
| address space. These commands can take a long time to execute, thus they
| require a command class different from Class M2:
| v SEND

Class C1 Commands
Class C1 commands are those that are attached in the CONSOLE address space,
and are considered essential to clearing a backlog of other commands:
v DISPLAY CONSOLES
v DISPLAY EMCS
v DISPLAY R
v LOGOFF
v LOGON (MCS)
v REPLY
v VARY CN
v VARY CONSOLE

Class C2 Commands
Class C2 commands are ordinary attached commands that run in the CONSOLE
address space:
v CHNGDUMP
v CONTROL M
v DISPLAY A
v DISPLAY C,K
v DISPLAY JOBS
v DISPLAY OPDATA
v DISPLAY PFK
v DISPLAY TS
v RESET CN
v SETCON
v SWITCH CN

| Class C3 Commands
| Class C3 commands are ordinary attached commands that run in the CONSOLE
| address space. These commands can take a long time to execute, thus they
| require a different command class than Class C2:
| v ROUTE

Inline Commands
Inline commands are not attached, but execute under the SVC 34 issuers task.
These are not subject to the limits, and cannot be displayed, removed, or canceled,
using the CMDS command:
v CANCEL
v CMDS
v CONTROL (except K M)
v DISPLAY NET

1-36 z/OS V1R7.0 MVS System Commands

 v DISPLAY T
v DISPLAY TP
v FORCE
v HALT NET
v HOLD TP
v LOG
v MODE
v MODIFY
v MONITOR
v MSGRT
v RELEASE TP
v STOP
v STOPMN
v VARY NET
v WRITELOG

Responding to Failing Devices

Whenever a device fails, you can use the SWAP command to invoke dynamic
device reconfiguration (DDR), which allows you to move or swap a demountable
volume from the device.

Using the SWAP command, you can also turn on or off system-initiated swapping
requests. When DDR is on, the system dynamically performs the swapping function
whenever the originally-allocated device encounters device errors. DDR tells you to
mount the volume on another available device. When the swapping function is
turned off, you can invoke operator-initiated DDR by issuing the SWAP command
and specifying the from and to device numbers. (See the SWAP command in
Chapter 4.)

When swapping tape devices, the from and to devices should have the same
density whenever possible. Swapping devices of unlike but compatible densities (for
example, 1600 and 1600/6250) can cause the failure of jobs that are in device
allocation at the time of the swap.

On JES3 systems, DDR interfaces with JES3 to ensure that the to device has not
been assigned to another job or function. When the swap is complete, DDR notifies
JES3.

The following devices are supported by DDR:

v 3400 series tape drives.
v 2501, 2540, 3505, 3525, 1403, and 3211 unit record devices. These devices are
not swapped by system-initiated DDR; you must issue the SWAP command to
swap these devices.
v 3330/3333 and 3340/3344 direct access devices. If you are using a 3348 Model
70F Data Module, make sure that the to 3340 device has the fixed-head feature
installed. When swapping a 3340/3344 device with the fixed-head feature, be
sure that the to device also has the fixed-head feature installed.

The following devices are not supported by DDR:

v Graphic or teleprocessing devices.

Chapter 1. System Operations 1-37

 v Shared DASD devices, unless the device is swapped to itself.
v 3344 and 3350 fixed-head DASD devices (not supported by system-requested
DDR).
v Any device holding a permanently-resident volume, such as a system residence
or page data set volume.
v 3375 direct access storage device.
v 3380 direct access storage device.

Quiescing the System

Issuing the QUIESCE command causes the system to suspend the processing of
all active jobs and to prevent the starting of any new ones. The system enters the
MANUAL state, the MANUAL indicator is on, and no processing is being done.
Quiescing the system does not affect any job step timings (for accounting
purposes). Issue the QUIESCE command from any console with MASTER authority.
You can continue processing by performing the restart function.

Do not issue a SYSTEM RESET after quiescing the system if you intend to issue a
RESTART after the quiesce. Issuing a SYSTEM RESET will cause the system to
enter an enabled wait state.

Stopping the System

When all processing (including subsystem processing) has finished, use the HALT
command to ensure that all system statistics and data records in storage are
collected for system recording facilities.

1-38 z/OS V1R7.0 MVS System Commands

Chapter 2. Console Characteristics and Operations
The tasks of starting, running, and stopping an MVS system involve:
1. Operating the system itselfthat is, controlling the system software and most
installation hardware (including processors, channel paths, and I/O devices)
2. Operating the MCS (multiple-console support) and SMCS (SNA multiple-console
support) consoles

Chapter 2 describes the physical characteristics and techniques for operating the
various consoles that MVS supports as operators consoles. It describes the
characteristics and operations that you cannot control, including those operations
that are common to all operators consoles.

Chapter 3 continues the console descriptions of Chapter 2 by describing the

console characteristics that you can control. It describes the commands that
operators and system programmers can use to tailor the consoles and console
operations to the installations requirements.

General Characteristics of Display Consoles

Many different input and output (I/O) devices can function as consoles in an MVS
system. Three logical conditions determine how or if the devices function. A device
can be:
1. Online: If allocated, the system assigns functions with these two limitations:
v The device must be capable of performing the function.
v The device cannot be assigned as a console because it is allocated to some
other function.
If unallocated, the device can be assigned as a console.
2. Offline: The device is generally unavailable for the system to use.
3. Console: The system can use the device to send messages to you, and you
can use the device to issue system commands (if the device has input
capability), but you cannot use the device for other input/output purposes.

You can use a device as a multiple console support (MCS) if the device number for
the console on a CONSOLE statement, in the CONSOLxx parmlib member, is the
same as the device number specified in the IODF. If you use MVSCP, the device
number specified for each console in CONSOLxx the CONSOLE
DEVNUM(devnum) statement must correspond to a device number specified on
an IODEVICE statement. SMCS consoles are also defined in CONSOLxx, but are
not specified in HCD.

Subsystem Use of Consoles

Many different devices can function as consoles in an MVS system if they are
specified as consoles in a CONSOLxx parmlib member. If the console is allocated
to a subsystem CONSOLE DEVNUM(SUBSYSTEM) there is no
corresponding device definition in the IODF. You should familiarize yourself with
subsystem consoles if your configuration includes them; some of them can affect
MVS operations in important ways. It is called a subsystem-allocatable console and
is defined to the subsystem.

For a subsystem-allocatable console, the definition

CONSOLE DEVNUM(SUBSYSTEM)

Copyright IBM Corp. 1988, 2006 2-1

 must appear in the CONSOLxx parmlib member.

Multiple-Console Configuration
You can divide the functions and message traffic of the system among a number of
consoles. These consoles make up a multiple-console configuration controlled
and serviced by MCS.

A multiple-console configuration for a system or sysplex consists of up to 99

consoles; one console is the master console. The other consoles can be active
(being used) or inactive. They can also have different levels of authority, for more
information see z/OS MVS Planning: Operations.

The master console is your principal means of communicating with the system. The
master console, along with any console with master console authority allows you to:
v Enter all operator commands
v Change the definition of the hardcopy message set or assign the hardcopy
medium
v Switch to a new master console

Other MCS and SMCS consoles are used for specific types of operator-system
communication when it is more convenient to have a console located away from the
processor. An MCS or SMCS console might, for example, be located close to tape
or disk drives or remote teleprocessing devices to make it easier for the operator in
that area to see which magnetic tapes or disk packs to mount. An MCS or SMCS
console without master authority cannot enter all commands (see System
Commands Grouped According to System Command Authority on page 3-5), and
can receive only those messages that are specifically routed to that console.

Your installation might further limit how you can use a console by assigning an
operating use that prevents the console from accepting commands.

A console you use both to issue commands and receive messages is in

full-capability operating mode. A console that only receives status displays is in
status display mode. A console that only monitors system activities and assists in
system security is in message stream mode. Both message stream and status
display consoles do not accept commands.

The different console modes help limit the number of consoles that operators can
use to issue commands, and yet provide operators the information that they need to
do their work.

At IPL, the system looks to the CONSOLxx member of parmlib to find which
console is the master console, and what the operating modes of the consoles are. It
also looks for other attributes, such as:
v System command groups the categories of commands that the system
accepts from that console
v Message routing codes the messages the console receives, determined by
routing code
v Message levels the messages the console receives, determined by message
level
v Alternate console groups the backup consoles assigned in case of a
malfunction or a console switch

2-2 z/OS V1R7.0 MVS System Commands

 v Hardcopy medium the system log (SYSLOG) or operations log (OPERLOG)
that receives the hardcopy message set
v PFK definitions the commands that consoles PFKs issue

Features on Display Consoles

MCS display consoles can operate in full-capability, status display, or message
stream mode. SMCS only operate in full-capability mode. Each one has a keyboard
to enter commands and responses to messages and to signal the system that you
are entering information. Each one also has a cursor, which appears on the screen
as a movable point of light (either an underscore, a horizontal bar, or a vertical bar).
The cursor points out the position on the screen that the system will examine for
your next action. This action might be positioning a typed character, entering a
command, requesting message deletion, or requesting a display. Special keys
located on the console keyboard control cursor movement.

A display console can also have some or all of the following features:

Selector Pen

The selector pen is a light-sensitive device that is available on some display

consoles. When you put the pen over specific areas of the display console screen,
it senses the light from the screen and signals the system. The system then
determines the screen location over which you have put the pen and takes
appropriate action. The action the system takes might involve entering operator
commands, deleting messages from the screen, canceling processes, or presenting
displays.

Audible Alarm

An audible alarm is available on display consoles. The system sounds this alarm
when certain changes in conditions occur, such as when you enter an invalid
CONTROL command. WTO macros with descriptor codes of 1, 2, or 11, and all
WTOR macros will cause the audible alarm to sound on operator consoles
so-equipped.

Program Function Keyboard

The program function keyboard is an input device that is available on some display
consoles. You can define each key on the program function keyboard to enter one
or more operator commands; you can enter a command or a group of commands
by pressing one key.

Extended Highlighting

Extended highlighting refers to blinking, reverse video, and underscored

presentation of messages that require operator action.

Color

Four or more colors are available on some devices, with certain colors identifying
certain kinds of messages that require action.

Intensity

Some messages that require operator action appear brighter.

Chapter 2. Console Characteristics and Operations 2-3

Display Screen Areas
The operating mode of the console controls the appearance of a display screen.
Figure 2-1 on page 2-5 illustrates the differences among the three different kinds of
consoles. The display screens can have these functional areas:

Message Area

This area contains system and problem program messages and copies of certain
operator commands. The size of the message area depends on the console.

Display Areas

These areas contain formatted, multiple-line displays of information about some part
of the system. The displays are written to the console in response to certain
commands, such as the DISPLAY command. The default on consoles in
full-capability mode is one display area, the default on consoles in status display
mode is two display areas. For consoles operating in full-capability mode, unless a
status display is requested, the display area is used for general messages.

PFK Display Line

This line contains a display of program function key (PFK) numbers that you use
when entering commands with the selector pen. This line is available on a 3277
model 2.

Instruction Line

This line contains console control messages. For example, if you make an error
entering a CONTROL command, an error message appears in the instruction line.

Entry Area

This area contains one or two lines that you use to enter commands and reply to
messages.

Warning Line

This line warns you of conditions that could require action. For example, a warning
message appears in this line when the message area is full and one or more
messages are waiting to appear. The warning line is not available on output-only
consoles in status display operating mode.

Operator Information Area

This line, the bottom-most line on the screen, is separated from the rest of the
screen by a horizontal line. The operator information area, which is not controlled
by MCS or SMCS, contains messages and symbols that keep you informed of the
operational status of the terminal. It is not available on some terminals.

Figure 2-1 shows the screens on consoles in the three different operating modes.
You can change the display areas on the consoles in full-capability mode and status
display mode. The screen on the console in message stream mode always appears
as in the figure.

2-4 z/OS V1R7.0 MVS System Commands

Figure 2-1. Comparison of the Display Screens of Full-Capability and Output-Only Display Consoles

L= Operand
Commands that manage consoles and console traffic use the L= operand to modify
the screen area. For example, use the L= operand to delete messages or to delete
lines from the screen area.

Commands that direct output use the L= operand to direct the output to an
out-of-line area that is defined to the console. If there is no out-of-line area defined
to the console, or if the area ID specified is z, the message is displayed inline.

For more information on the syntax and use of the L= operand for specific
commands, see the description of the specific command in this book.

For a discussion of the L= operand in a sysplex, see z/OS MVS Planning:

Operations.

Chapter 2. Console Characteristics and Operations 2-5

Special Screen Characters
The system uses five special screen characters to indicate the status of certain
screen messages. These special characters appear in position three, four, or five of
the lines in the message area:
v A vertical line (|) in position three indicates that required action has been taken
for the message and the system has deleted the message.
v A horizontal bar (-) in position three indicates that the message is for information
only and requires no action from you.
v An asterisk (*) in position four indicates that the message is a system message
that requires action from you.
v An at sign (@) in position four indicates that the message is a problem program
message that requires action from you.
v A plus sign (+) in position five indicates that the message is a problem program
message that requires no action from you.

Messages Sent to Display Consoles

The MVS system and any program running under the MVS system can issue
messages. A displayed message can appear by itself or with information about the
message. Each message consists of:
v An identifier, which is a three-letter prefix to identify the system component that
produced the message and a message serial number to identify the individual
message. The identifier may contain other information.
v A message text to provide information, describe an error, or request an operator
action.

Messages sent to your consoles can appear in one of the following formats:

f message

or

hh.mm.ss sysname jobident f message

Fields that are always present in a message are:

f A blank, which means that no action is required, or a special screen
character. See Special Screen Characters on page 2-6.
message Message identifier and text

Fields that you might chose to add to a message are:

jobident Job name or job id for the task that issued the message.
sysname Name of the system that issued the message
hh.mm.ss Time stamp, given as the hour (00-23), minute (00-59), second
(00-59)

To add any combination of job identification, system name, and time stamp to all
console messages, see Controlling the Format of Messages on page 3-15. For
more information about console messages, use LookAt (see Using LookAt to look
up message explanations on page xviii) or use the MVS System Messages books.

2-6 z/OS V1R7.0 MVS System Commands

Operations on Display Consoles in Full-Capability Mode
Although some of the procedures for operating and controlling display consoles
involve special functions and conditions, most console procedures are quite
general. These general procedures are described in this topic and include:
v How to perform basic keyboard actions
v How to enter commands with the keyboard
v How to enter commands with program function keyboard
v How to enter commands with the selector pen
v How to change information in the entry area

Performing Basic Keyboard Actions

While the basic operating procedures are similar for all types of display consoles,
the physical characteristics of each console require you to perform certain actions
(such as, the ENTER, CANCEL, cursor detect, and selector pen detect actions) in
different ways. The descriptions of operating procedures later in this section refer to
these actions.

To perform the ENTER action, press the ENTER key.

To perform the CANCEL action, on a 3278 or 3279 display console, hold down
the ALT key and press the PA2 key. On all other display consoles, press the
CANCEL (PA2) key.

The cancel action:

v Erases the entry area
v Moves the cursor to the first position in the entry area
v Rewrites the message area and the instruction line
v Removes deletable-message indicators (if any are displayed)
v Removes message line numbers (if line numbers are displayed)

To perform a CURSOR DETECT action, position the cursor under the desired
character and press the ENTER key.

To perform a SELECTOR PEN DETECT action, on 3277, 3278, or 3279 display

consoles, any of which has a selector pen, place the selector pen over the desired
indicator. Then, press the pen against the screen.

To retrieve the previous command, press the PA1 key.

How to Enter Commands

You can enter commands with the keyboard, the program function keys, or the
selector pen (together with the PFK display line).

Entering Commands with the Keyboard

To enter commands with the keyboard through display consoles, use the following
procedures. Use the same procedures to reply to WTOR messages:
1. Move the cursor to the first position in the entry area.
2. Type in the command.
3. Enter the command by performing the ENTER action.

Moving the Cursor

Move the cursor to the first position in the entry area by one of the following
methods:

Chapter 2. Console Characteristics and Operations 2-7

 v Press the cursor control keys.
v Press the tab key, the back-tab key, or the new line key.
v Press the ENTER key when the cursor is in the entry area or under the ENTER
indicator in the instruction line. Pressing the ENTER key passes any data in the
entry area to the system.
v Perform a cancel action. This action might also change the display.

Typing the Command

Type in the command just as you would on a typewriter. As you type each
character, the corresponding character appears in the entry area, and the cursor
advances to the next character position. When you reach the end of the first line of
a two-line entry area, the cursor advances automatically to the first character
position of the next line, so that you can continue the command. The maximum
number of characters that you can enter is 126.

You have the option of entering one command or several commands. When you
wish to enter more than one command, use the MVS command delimiter. The MVS
command delimiter is defined during system initialization. When the MVS command
delimiter has not been defined during system initialization, you cannot enter more
than one command at a time.

Most commands can be entered in either lowercase or uppercase. The system

converts the commands to uppercase, if required. However, information within a
command that is contained within single quotes (for example, a reply to a WTOR
message) is not converted to uppercase by the system. If the system requires the
information within the single quotes in uppercase, be sure to type it in uppercase
when you enter the command. When an MVS command delimiter has been defined
during system initialization, you cannot use the defined delimiter within single
quotes.

Entering the Command

When you enter the command, the cursor must be in the entry area or under the
ENTER indicator in the instruction line, but it need not be at the end of the
command. Pressing the ENTER key or selecting the ENTER indicator causes the
command to be read and processed by the system. Commands other than the
CONTROL command disappear from the entry area and reappear in the message
area. If the message area is full, the command may not appear immediately; to
have it displayed, you may have to delete some messages.

The PA1 Key

Each time you press the PA1 key, you see a command that you entered previously.
The maximum number of times you can press the PA1 key to see previous
commands is specified by your installation with the RBUF option on the CONSOLxx
parmlib member. If you exceed this maximum, you see the same commands again.

Correcting Command Entry Errors

If you make errors entering a CONTROL or MSGRT command, the audible alarm
sounds, and the command appears in the entry area. The location of the cursor
indicates the error:
v If the error is an invalid operand, the cursor appears under the invalid operand:
CONTROL X,N
v If the error is an invalid erase request, the cursor appears under the first invalid
request.
CONTROL E,31,19

2-8 z/OS V1R7.0 MVS System Commands

 v If the CONTROL command exceeds 126 characters, the cursor appears at
location 127 in the entry area.

To correct any of these errors, use the procedures described under Changing
Information in the Entry Area on page 2-13.

If the system detects an error in a command other than a CONTROL or MSGRT

command, it writes the command in the message area with an error message.
Follow the procedures indicated for the error message in the MVS System
Messages books.

Entering Commands with Program Function Keys

The program function keyboard is a group of keys called PFKs. They are located on
or near the operator console keyboard. PFKs are used as a shortcut for entering
commands. Some PFKs have commands defined for them at IPL. The definitions
might be those in a PFK table that your system programmer assigned to the
console, or the PFKs might have the defaults assigned by IBM. You can redefine
the PFK commands; see Defining PFKs using PFK Tables and Defining PFKs
Using the CONTROL Command on page 3-19 in Chapter 3.

Each PFK can be either conversational or nonconversational. The commands

associated with a conversational PFK appear in the entry area one at a time when
you press the key. You can change them before entering them. Commands
associated with a nonconversational PFK are entered immediately when you press
the key.

| If your system programmer does not define and activate a PFK table for your PFKs,
| IBM supplies default definitions in sample IEESPFK.

Identifying PFK Definition Errors

When the system tries to execute an invalid CONTROL N,PFK command, the
audible alarm sounds, and the command appears in the entry area. The location of
the cursor indicates the error:
v If the cursor is positioned under the first letter of a keyword (CMD, KEY, PFK, or
CON), that keyword or its trailing equal sign is incorrect.
v If the cursor is positioned under the number of the PFK being defined, that
number is either not a numeric character or not the number of a PFK that was
designated for command entry in the PFK table, or it is the number of a PFK you
are trying to associate with a list of key numbers when it is already part of a list
of key numbers.
v If the cursor is positioned under a number following the KEY operand, the key
number indicated is either a non-numeric character, the number of the PFK that
is being defined, the number of a PFK that has already been defined as a list of
key numbers, or the number of a PFK that has no command associated with it in
a PFK table.

To correct these errors, follow the procedures described under Changing

Information in the Entry Area on page 2-13.

Checking the Commands Defined for Each PFK

Use the DISPLAY PFK command to determine the commands defined for a
consoles PFKs, the PFK definitions in a specific PFK table, or the PFKs in effect
for a specific console. The display can appear in the message area or can be
routed to a display area or to another console. Unless you specify another console,
the definitions always refer to the console on which you issue the command.

Chapter 2. Console Characteristics and Operations 2-9

 Table 2-1. Checking the Commands Defined for Each PFK
If you want to know Use this command
The names of all available PFK tables DISPLAY PFK,TABLE
The PFKs in effect at your console DISPLAY PFK
The definitions in a specific PFK table DISPLAY PFK,TABLE=nnnnnnnn, where
nnnnnnnn is the name of the table
The PFK definitions in effect for a specific DISPLAY PFK,CN=cc, where cc is the
console consoles id

Summary of the PFK Definitions for the Cluster later in this chapter shows the
complete output of the DISPLAY PFK,TABLE=nnnnnnnn command.

Example 1

To display the commands associated with the PFKs on the console on which you
issue the command, enter:
DISPLAY PFK

In response to this command, the following message usually appears in the

message area:
IEE235I hh.mm.ss PFK DISPLAY
PFK DEFINITIONS FOR CONSOLE nnnnnnnn TABLE - MASTCMDS IN PFKTAB02
KEY# CON ------------DEFINITION-----------------------

The definitions for each key appear under the headings; nnnnnnnn identifies the
console on which the command is issued.

If no PFKs are defined for the console named CON04, the following message
appears in the message area instead:
IEE235I hh:mm:ss PFK DISPLAY
NO PFK DEFINITIONS FOR CON04

Example 2

To determine the definitions in effect for the PFKs on CON04, enter:

DISPLAY PFK,CN=CON04

In response to this command, a message such as the following might appear in the
message area:
IEE235I hh:mm:ss PFK DISPLAY
PFK DEFINITIONS FOR CON04 TABLE - MASTCMDS IN PFKTABJC

where the PFK table in effect for console 4 is MASTCMDS in the PFKTABJC
parmlib member.

The definition for each key appears under the headings. If, however, no PFKs are
defined for the console, the following message appears:
IEE235I hh:mm:ss PFK DISPLAY
NO PFK DEFINITIONS FOR CONSOLE 04

Entering Commands Assigned to PFKs in Conversational Mode

In conversational mode, the system causes commands assigned to PFKs to appear
in the entry area. You can change and then enter them, enter them unchanged, or

2-10 z/OS V1R7.0 MVS System Commands

cancel them. The cursor appears under the third character of the command or
where designated with an underscore when the PFK was assigned a command.
You can change or complete the command by positioning the cursor under the first
character you want to change, typing in the change, and performing an ENTER
action.

To enter commands in conversational mode,

1. Press the PFK associated with the command that you want to enter, causing the
first command associated with the key to appear in the entry area.
2. According to your requirements:
v Enter the command by performing an ENTER action. The next command
associated with the PFK (if any) then appears in the entry area.
v Change the command from the keyboard, then enter the command. (See
Changing Information in the Entry Area on page 2-13.)
v Cancel the command that appears in the entry area by performing a
CANCEL action. The next command associated with the PFK (if any) then
appears in the entry area.
v Cancel the request initiated by the first press of the PFK by pressing any
PFK while the command is still in the entry area.
The result of cancelling a request in this way is shown in the following
example. In the example, PFK 1 is assigned the commands START PGM1
and START PGM2.

PFK pressed Result

PFK 1 START PGM1 command is displayed
Any PFK START PGM1 command is cancelled, and a blank line is displayed
PFK1 START PGM2 command is displayed

Altering a command in the entry area works only for the command entry in
progress; the system retains the original definition for future use of the PFK. To
redefine a PFK, use the procedures described in Chapter 3 under Defining
Commands Using the CONTROL Command.

Entering Commands Assigned to PFKs in Nonconversational

Mode
Press the PFK associated with the commands that you want to enter. All of the
commands are entered in the order in which they were associated with the key, just
as if you had typed each command and performed the ENTER action.
Notes:
1. PFKs that are defined as conversational function in the conversational mode
even though the console is in nonconversational mode. Use these keys as if
you were in conversational mode, as described earlier under Entering
Commands Assigned to PFKs in Conversational Mode on page 2-10.
2. Although the commands are entered in order, their execution may overlap.
Therefore, assign commands requiring sequential execution in conversational
mode.

Responses to PFK Errors

If you press a PFK that is not designated for command entry, the following message
appears in the instruction line:
IEE721I PFK nn NOT SUPPORTED

Chapter 2. Console Characteristics and Operations 2-11

 If you press a PFK that has been designated for command entry but for which no
command has been defined, the following message appears in the instruction line:
IEE722I PFK nn NOT DEFINED

Displaying the PFK Numbers on 3277 Model 2 Consoles

You can display the PFK numbers on 3277-2 consoles and then point to them with
the selector pen. Pointing to a number has the same effect as pressing that key. To
display the PFK numbers, use the CONTROL D,PFK command. To erase the
numbers in the PFK line, use the CONTROL E,PFK command.

Example

To request a display in the PFK display line (this line is located immediately above
the instruction line), enter:
CONTROL D,PFK

In response to this command, a display similar to the following appears in the PFK
display line:
1 2 3 4 5 6 7 8 9 10 11 12

Only those numbers that have been designated for PFK command entry appear in
the display. Once you have requested this display, you can leave it on the screen;
the PFK display line is not used for any other purpose, even when the key numbers
are not displayed. To erase the display, enter:
CONTROL E,PFK

Entering Commands with the Selector Pen

Use the selector pen to enter commands that appear in the entry area. The
commands can be in the entry area either because you typed them there or
because you pressed a PFK that is in conversational mode. The PFK numbers
available for selector pen command entry are defined in the active PFK table or are
IBM defaults.

On a 3277 model 2, the selector pen can be used with the PFK display line to enter
commands. The numbers appearing in the display line represent PFK numbers, and
selecting a number with the selector pen has the same effect as pressing a PFK.

In nonconversational mode, all of the commands associated with a PFK are

entered in the order in which they were associated with the key number. All
commands (except CONTROL commands) appear in the message area when
screen space is available. No commands appear in the entry area.

To enter commands on the 3277 model 2 in nonconversational mode:

1. Display the PFK numbers in the PFK display line by entering the CONTROL
D,PFK command.
2. Select the PFK number associated with the command(s) you want to enter.
3. Press the selector pen against the screen over the selected number. The
command is automatically entered.

To select commands on the 3277 model 2 in conversational mode, follow the same
three steps. The system does not automatically enter the command; rather, the first
command associated with the PFK number appears in the entry area. To enter the
command, follow the steps described in the next section.

2-12 z/OS V1R7.0 MVS System Commands

 Entering Commands with the Selector Pen in Conversational
Mode
In conversational mode, each command associated with a PFK number is
presented in the entry area, one command at a time, where you can enter it as is,
change it and enter it, or cancel it. Changing a command in the entry area works
only for the command entry in progress; the system retains the original definition for
that PFK.

To enter commands with the selector pen in conversational mode:

1. Enter the command by performing the ENTER action or by selecting ENTER.
The next command associated with the PFK (if any) then appears in the entry
area.
2. Change the command from the keyboard before entering it as described later in
this chapter under Changing Information in the Entry Area on page 2-13.
3. Cancel the command in the entry area by performing a CANCEL action. The
next command (if any) then appears in the entry area.
4. Cancel the request initiated by the first selection of the PFK number by pressing
the selector pen against the screen over any other PFK number while a
command associated with the first key number is still in the entry area.

Changing Information in the Entry Area

You can change information in the entry area to correct a typing error or to change
a command during conversational command entry or message deletion. You might
not need to completely retype a command to correct or change it. (Both
conversational command entry and message deletion are described in this section.)
You can blank out the entry area without entering a command to the system.

Pressing the PA1 key displays a command that you entered previously. When you
see that command, you can make corrections or changes (as described in this
section) and press the Enter key to issue the command.

Substituting Characters
If you make a mistake when typing in the entry area move the cursor to the first
character you want to change and type the correct characters.

Example

If you type in the following reply to a WTOR message:

R 22,DISLAY REQUESTED_

and then note (before performing the enter action) that you have typed the word
DISPLAY incorrectly, you can move the cursor under the L, and type PL. The reply
then reads:
R 22,DISPLAY REQUESTED

In the same example, if you decide that the correct response is NO, moving the
cursor under the D in DISPLAY and typing NO leaves the following in the entry
area:
R 22,NOPLAY REQUESTED

To correct this situation, move the cursor under the P and press the ERASE EOF
key. This key erases the remainder of the entry area (from the cursor to the last
character position), leaving the following in the entry area:
R 22,NO_

Chapter 2. Console Characteristics and Operations 2-13

 Inserting Characters
To insert one or more characters within data in the entry area:
1. Position the cursor at the character position following the point where the
missing data should appear.
2. Press the INS MODE key (the insert mode marker appears on the console).
3. Type in the missing data.
4. On some consoles, you must press the RESET key to return the keyboard to its
normal input mode.

| Example

To insert the console identifier 10 in the following command:

DISPLAY JOBS,L=CONSOLEC

Move the cursor back to the C, press the INS MODE key, type in 10, and press the
RESET key. The command then reads:
DISPLAY JOBS,L=CONSOLE10C

Note that the characters to the right of the inserted characters shift to make room
for the inserted characters. If required, characters shift to the second line of the
entry area.

Deleting Characters
To delete a character, position the cursor at the character to be deleted and press
the DEL key.

All characters that follow the deleted one shift to the left to fill the space formerly
occupied by the deleted character. Delete one character at a time.

| Example

To delete the extra S from the following command:

DISPLAY JOBS,L=CONSSOLEC

Position the cursor at either S and press the DEL key. The command then reads:
DISPLAY JOBS,L=CONSOLEC

Blanking the Entry Area

The ERASE INPUT Key

To remove all of the data that you have typed in the entry area without causing it to
be passed to the system, press the ERASE INPUT key. This key erases the entry
area and moves the cursor to the first position in the entry area.

Note: Do not use the ERASE INPUT key on the 3279 models 2A, 2C, and 3A. On
these devices, the ERASE INPUT key blanks out the entry areas and all
fields with data displayed in red.

The PA2(CANCEL) Key

To clear the entry area and restore the screen, press the PA2 key.

2-14 z/OS V1R7.0 MVS System Commands

Handling Consoles in Error Conditions
Several types of errors can occur that directly affect the operation of display
consoles. In some cases, the error becomes apparent by a sudden screen failure,
the appearance of error messages, or the locking of the keyboard. In other cases,
the error might not be immediately apparent. Errors can be caused by a
programming problem (system error), a console malfunction (hardware error), or a
hardware error not related to the console.

System Errors
When a system error occurs, one or more of the following can happen:
v The screen is blanked out, and then an error message appears in the message
area
v An error message appears in the WARNING line.
v There is an abnormal lack of console activity.

Responding to an Error Message in the Message Area

An error message at the bottom of the message area indicates that a recoverable
system error has occurred. Perform the action specified by the error message, and
then perform a CANCEL action. This should restore the screen. It is good practice
to review the messages at this time to make sure that no messages were lost
during error recovery.

Responding to an Error Message in the WARNING Line

An error message in the WARNING line might indicate that an unrecoverable
system error has occurred and that the system needs to be loaded again. If so,
follow normal procedures for IPL, and notify your system programmer.

Responding to an Inactive Console

An inactive console condition is characterized by a lack of message traffic or a lack
of system response to commands. The inactivity could be caused simply by a low
level of system activity, or it could be the result of a problem in the message
handling portion of the control program.

If an MCS or SMCS console appears inactive, check the system response by

requesting a display of the time:
DISPLAY T

The system should respond within a few seconds with the time and date. If it does
not, perform one of the following actions:
v Issue the CONTROL C,D command to cancel any status displays being
presented on the inactive console.

If neither of these procedures returns the console to normal activity, assume that
there is some other problem related to the console. Check for a console hardware
error. Also, if possible, switch control to another console. If the system must be
loaded again, follow normal procedures for IPL. Report the occurrence of this
problem to your system programmer.

Console Hardware Errors

When a console hardware error occurs, one or more of the following can happen:
v Error messages are centered on the screen (the remainder of the screen is
blank).

Chapter 2. Console Characteristics and Operations 2-15

 v The screen is blank (and no error message appears).
v The screen appears normal, but the keyboard is locked and you cannot enter
commands.

Responding to Error Messages Centered on the Screen

If a console hardware error occurs, one of the following sets of messages can
appear centered on the screen:
IEE170E RETRYABLE ERROR. RECENT ACTION MAY NEED TO BE REPEATED
IEE170E PRESS THE CANCEL KEY TO RESTORE THE SCREEN
-- or --
IEE171E CONDITIONAL ERROR. RECENT ACTION MAY NEED TO BE REPEATED
IEE171E PRESS CANCEL TO CONTINUE OR SWITCH CONSOLES

Perform a CANCEL action. The CANCEL action should restore most of the screen,
including messages displayed inline in the message area, the instruction line, and
the warning line. The entry area and the PFK line, however, are blanked out, any
out-of-line displays are erased, and the cursor is positioned to the first data entry
position. Also, message numbering (if active) is terminated.

Note: If you do not perform a CANCEL action, the system rewrites the screen
(same effect as CANCEL) after about 30 seconds. If a console hardware
error results from keyboard input when you perform the CANCEL action, the
system sees the error as a permanent I/O error and automatically switches
consoles. All messages (except status displays) are moved to the new
console. (See Console Groups on page 3-8 for a description of console
switching.)

Responding to a Blank Screen

If the console screen goes blank, the system is probably switching to the consoles
alternate. When the switch is done, the following message should appear on the
alternate console:
IEE870I CONSOLE SWITCH. OLD=(dev,system) NEW=(dev,system) REASON=reason

Appropriate values and system symbols appear in the actual message. Use the
alternate console to continue operating the system, and have the old console
checked for the source of the error.

Note: It is normal for the screen of a 3277 to go blank for a few seconds if the
back-tab key is pressed when the cursor is not in the entry area.

Responding to a Locked Keyboard

Sometimes the system is unable to blank out the screen. If you find that you cannot
enter commands through a console that otherwise appears normal, try to restore
the screen by performing a CANCEL action.

If the system has switched to the consoles alternate, operate the system from the
alternate console, and have the old console examined for the source of the error.

Note: Inhibited input, with or without keyboard locking, can also occur when the
system abends or goes into a wait state, or when a problem occurs in the
message handling portion of the control program. See the procedures
described for an inactive console under System Errors on page 2-15.

Responding to a Master Console Failure

Normally, MVS detects a failing master console and automatically switches to the
alternate of the master console. A message is sent to the new master console to

2-16 z/OS V1R7.0 MVS System Commands

 inform the operator that his console is now the master console. The message also
informs the operator of the device number of the old master console so that it can
be repaired.

Occasionally, the system does not detect a failure. In this case, you should press
the external interrupt key to switch to the alternate.

When no alternate consoles are active, console switching cannot take place. If the
master console fails, and the master console function cannot be switched to
another console, all active MCS and SMCS consoles receive message IEE141A,
which indicates that there is no master console. There are several ways to resolve
a no-master-console condition:
v Issue VARY CN(),ONLINE to activate an MCS console and make it the master
console.
v Issue CONTROL V,USE=FC to change an active MCS output-only console to a
full-capability console, and make that console the master console.
v Issue the VARY MSTCONS command to make an active MCS or SMCS console
the master console.
v Activate a master-authority SMCS console to make that console the master
console.

Note: In a no-master-consoles condition, any MCS or SMCS console will accept

the VARY MSTCONS command to make that console the master console,
unless the installation has configured the security product to only allow
certain operators to issue the command. See z/OS MVS Planning:
Operations for more information on a no-master-consoles condition and
protecting the VARY MSTCONS command.

If no secondary consoles are active when a master console failure occurs, a

no-consoles condition occurs. See the next topic, Responding to a No-Consoles
Condition.

Responding to a No-Consoles Condition

A no-consoles condition occurs when no full-capability consoles (consoles capable
of input and output functions) are available to the system. When the system enters
a no-consoles condition, WTO message buffers are not freed and, when the
IPL-specified limit of buffers is reached, non-privileged tasks wait until WTO
message buffers become available. See Responding to Console Message
Backups on page 2-18.

Note: Output-only consoles can continue to function during a no-consoles

condition.

The system tries to notify you of a no-consoles condition in one or more of the
following ways:
v Issuing message IEA546E to any active output-only console.
v Sounding an alarm on a device. The system can sound a device alarm only if:
The device was specified as a console at system installation
The device has an alarm feature
The device is online or in console status
The device is unallocated
v Sounding the processor controller alarm.
v Stopping message traffic on full-capability consoles. A lack of message traffic
could be the only indication of a no-consoles condition because the system might

Chapter 2. Console Characteristics and Operations 2-17

 not find a console on which message IEA546E can appear and might not find
any devices on which to sound an alarm.
v Rejecting any VARY CONSOLE commands

Before trying to recover from a no-consoles condition, understand that:

v You cannot attempt recovery until all alarms have sounded and message
IEA546E has been issued.
v Recovering the master console should be your first priority.

To recover the master console, the operator can perform one of the following
actions:
v Issue VARY CN(),ONLINE (from an extended MCS or subsystem console) to
activate a full-capability console that is offline and make it the master.
v Issue CONTROL V,USE=FC (from an extended MCS or subystem console) to
change an active message stream or status display MCS console to a
full-capability MCS console and make it the master.
v Press the attention interrupt key on an MCS console device that is to become the
master console, then press the external interrupt key on the system console to
activate the device as the master console.
v In a sysplex, an operator can use the system console to IPL a system with a
full-capability console (defined with AUTH=MASTER) into the sysplex.
v Activate an SMCS console to relieve the no-consoles condition. If the console
was defined AUTH=MASTER, it will become the master console. Otherwise, it
will not become the master console, and the system or sysplex will enter a
no-master-console condition as described in No-Master-Console Condition in
z/OS MVS Planning: Operations. In a no-master-console condition, the operator
using the console can make the console the master console using the VARY
MSTCONS command, unless the installation takes steps to prevent it as
described in No-Master-Console Condition in z/OS MVS Planning: Operations.

If the recovery attempt is successful, the device that generated the attention
interrupt becomes the master console and message IEE870I appears on it.

This message indicates that the failing master consoles functions have been
switched to the new master console, messages queued to appear on the failing
master console now appear on the new master console, and the no-consoles
condition is resolved.

Responding to Console Message Backups

The MVS system keeps some WTO and WTOR messages in buffers in virtual
storage. The WTO buffers hold the messages that the system has not yet displayed
at the eligible consoles; the WTOR buffers each hold one WTOR message that the
system has already displayed but that an operator has not responded to. The
maximum number of WTO and WTOR buffers are determined by the MLIM and
RLIM parameters on the INIT statement in the CONSOLxx parmlib member. If these
parameters are not coded, the system defaults (as described in z/OS MVS
Initialization and Tuning Reference) are in effect.

To avoid WTO message buffer shortages, you can raise your WTO buffer limit
(MLIM) and adjust message deletion specifications on your consoles. To avoid
WTOR message buffer shortage, raise your WTOR buffer limit (RLIM) and reply to
WTORs more frequently. Procedures for responding to WTO and WTOR buffers
shortages follow in this section.

2-18 z/OS V1R7.0 MVS System Commands

 Responding to WTO Buffer Shortages
When WTO message buffer use reaches 80 percent of the limit specified at IPL, the
system issues the following message:
IEA405E WTO BUFFER SHORTAGE - 80% FULL

The system also issues a DISPLAY CONSOLES,BACKLOG (D C,B) command to

provide information helpful in determining the cause of the buffer shortage.

If the problem continues and WTO buffer use reaches its limit, the system issues
the following action message:
IEA404A SEVERE WTO BUFFER SHORTAGE - 100% FULL

When MLIM is reached, the system obtains buffers in backup storage. When this
backup storage is exhausted, the system issue the following message:
IEA652A WTO STORAGE EXHAUSTED - WTOS WILL BE DISCARDED

At this point, any new WTOs will be thrown away.

When the system notifies you that the WTO buffers are 80% full, determine the
reason for the buffer shortage and correct the problem. Possible reasons are:
v A console is not ready and WTO messages are filling the console message
buffers because:
An intervention required condition exists.
The console has been powered off.
Some part of the path to the device is not working; for example, an I/O
interface is disabled.
One or more consoles may have their displays held.
v A console is not in roll mode, and messages are filling the console message
buffers.
v A console is in roll or wrap mode but the update time is too long, and messages
are filling the console message buffers.
v A buffer limit specified at IPL is too low to handle the message traffic in the
system. (Either the value on the MLIM parameter in the CONSOLxx member is
too low, or the system default for RLIM is too low.)
| v A program is issuing messages at too rapid a rateand might be in a loop. When
| a job uses a high percentage of the WTO buffers, the system issues message
| CNZ3011I which identifies the jobname and the address space.

To determine the extent of the problem and the responsible console or consoles,
examine the output from the DISPLAY CONSOLES,BACKLOG (D C,B) command.
When messages are backed up for a console, it might be necessary to delete the
queue of messages for the console using a CONTROL Q command. You might
need to issue CONTROL Q several times to clear the console completely.

When there are too many messages from one job/address space, consider
| cancelling the job or jobs specified in message CNZ3011I. If cancelling a job would
cause a serious impact, look at the messages the job is issuing. If the job seems to
be in a loop, then activate an MPF member to suppress or delete the repeating
message. Another option is to temporarily remove the messages routing code from
all the consoles.

When a high number of buffers is in use for messages from another system in the
sysplex, you can route a D C,B command to the other system to determine if a job

Chapter 2. Console Characteristics and Operations 2-19

 on the other system is generating too many messages. You can protect your
system from a runaway job on another system in the sysplex by using the V
CN,DMSCOPE= command.

Figure 2-2 shows an example of the DISPLAY CONSOLES,BACKLOG output. The

system displays information about all consoles, on this system only, that have any
outstanding WTO messages. The output in the figure includes the following line:
MSG: CURR=1356 LIM=1500 RPLY:CURR=1 LIM=10 SYS=1 PFK=NONE

In this line, MSG: CURR=1356 LIM=1500 tells you the current use of WTO buffers and
the specified limit. RPLY: CURR=1 LIM=1500 tells you the number of WTOR
messages that have been displayed and are awaiting operator reply, and the
specified limit. The line confirms that more than 80% of the specified WTO buffer
limit is reached; 1356 WTO buffers are full and the specified limit is 1500. The
display in Figure 2-2 on page 2-20 indicates, through NBUF, the number of buffers
queued to each console. In this example, console 12, with 1217 message buffers
filled, is the source of the problem. The buffer limit of 1500 seems adequate, so
console 12 is probably failing and causing undisplayed messages to fill the
message buffers.

SY2 IEE889I 15.03.36 CONSOLE DISPLAY 198

MSG: CURR=1356 LIM=1500 RPLY:CURR=1 LIM=10 SYS=1 PFK=NONE
CONSOLE ID --------------- SPECIFICATIONS ---------------
12/CON2 12 COND=M AUTH=MASTER NBUF=1217
03E0 AREA=Z,A MFORM=S
SY2 DEL=RD RTME=2 RNUM=5 SEG=10 CON=N
USE=FC LEVEL=ALL PFKTAB=*DEFAULT
ROUTCDE=ALL
CMDSYS=1
MSCOPE=*ALL
MONITOR=JOBNAMES
WTO BUFFERS IN CONSOLE BACKUP STORAGE = 0
ADDRESS SPACE WTO BUFFER USAGE
ASID - 0019 JOBNAME = FLOODNUM NBUF = 520
MESSAGES COMING FROM OTHER SYSTEMS - WTO BUFFER USAGE
SYSTEM = 2 NBUF= 4

Figure 2-2. Example of DISPLAY CONSOLES,BACKLOG Command Output

If the buffer limit is not adequate, issue the CONTROL M,MLIM= command to
increase the WTO buffer limit for the duration of the IPL. Your system programmer
might code the MLIM parameter on the INIT statement in the CONSOLxx member
to raise the WTO buffer limit for the next IPL.

When the number of buffers in use drops below 60% of the limit specified at IPL
time, the system issues the following message:
IEA406I WTO BUFFER SHORTAGE RELIEVED
Notes:
1. All lines of an out-of-line multi-line status display that have not been presented
occupy message buffers. Therefore, you should erase these displays when they
are no longer needed.
2. The current buffer count can be larger than the specified limit. Even though the
buffer count is greater than or equal to the limit, the system always gives a
privileged task a buffer unless the storage available for buffers is exhausted.
3. The system does not use the MLIM and RLIM parameter values specified in the
CONSOLxx parmlib member until either the hardcopy medium (SYSLOG or

2-20 z/OS V1R7.0 MVS System Commands

 OPERLOG) becomes active or NIP processing is complete. After NIP
processing, consoles other than the master console become active and buffer
space becomes important.

Responding to WTOR Buffer Shortages

When WTOR message buffer use reaches 80 percent of the limit specified at IPL,
the system issues the following message:
IEA230E WTOR BUFFER SHORTAGE - 80% FULL

If the problem continues and WTO buffer use reaches its limit, the system issues
the following action message:
IEA231A WTOR BUFFER SHORTAGE CRITICAL - 100% FULL

When the system notifies you that the WTOR buffers are 80% full, you should reply
to the WTOR messages that are outstanding. If any of the WTORs have rolled off
the screen (console roll mode is DEL=R), use the DISPLAY R,R command to
retrieve the text of the outstanding requests.

To raise the limit of WTOR buffers for the duration of the IPL, issue the CONTROL
M,RLIM command. If WTOR buffer use often reaches 80 percent of the limit, the
limit for WTOR messages specified at IPL might be too low to handle the WTOR
message traffic in the system. Your system programmer should code the RLIM
parameter on the INIT statement in the CONSOLxx member to raise the WTOR
buffer limit for the next IPL.

Processing MVS Messages at the System Console During System

Recovery
During system recovery, MVS might try to communicate with you. Your installation
may have defined the master console, the system console, or any other MCS
console as members of an alternate console group in CNGRPxx to receive
synchronous messages. Synchronous messages are WTO or WTOR messages that
can be issued during initialization or recovery situations. The operator must respond
to the WTOR messages before the system will continue. In a sysplex, a console
can display synchronous messages only if it is attached to the system that issues
the message. If your installation has not specified an alternate console group or a
console is not active, the system that issues the message tries to select a console
in the following order:
v The master console, if it is active and physically attached to the system that
issues the message.
v The system console on the system that issues the message:
If the system hardware level supports the OPRMSG system console, MVS will
display the message on the OPRMSG priority frame.
Otherwise, MVS displays a WTOR message on the SCPMSG or SYSMSG
system console. When this action is successful, the alarm on the processor
controller rings, and a message replaces the screen image on the system
console. The message tells you that an MVS message is pending. To display
this MVS message, enter one of the following commands on the system
console:
F OPRMSG (on an ES/9000 processor)
or
F SCPMSF (on an ES/3090 processor)
or
F SYSMSG (on a 308x processor)

Chapter 2. Console Characteristics and Operations 2-21

 The MVS message on the system console does not time out; the message remains
on the screen until you enter a reply. See z/OS MVS Planning: Operations for more
information about consoles and console recovery.

Placing a Console in Offline Status

When an MCS or SMCS console or the system log must be bypassed for any
reason, you must enter a VARY command to place the console offline. Command
activity from the console is immediately suspended. If the console is a printer,
messages continue to be displayed until all waiting messages have been issued.

The VARY command does not cause the functions of the bypassed console to be
assigned to another console.

Before using the VARY command to bypass the master console, you must assign
the master consoles functions to another console.

| Before you use the VARY command to bypass the hardcopy medium, you must
| change the hardcopy medium to the system log.

Interchanging Your Consoles on a Control Unit

If a device has been specified as a 3270 model X to hardware configuration
definition (HCD), you can replace it with another device and redefine it through the
HCD panels. For information about using HCD, see z/OS HCD Users Guide.

2-22 z/OS V1R7.0 MVS System Commands

Chapter 3. Defining and Changing Console Characteristics
This chapter describes:
v Using Operator Commands to Change CONSOLxx Statements
v Changing Console Characteristics
v Controlling System Messages and Commands
v Defining Program Function Keys (PFKs)
v Processing Hardcopy

When your system comes up, the definitions in certain members of SYS1.PARMLIB
are in effect. After IPL, you can use CONTROL, MONITOR, MSGRT, SET, and
VARY commands to change some of the definitions; however, the effect of the
command lasts only for the duration of the IPL.

Using Operator Commands to Change CONSOLxx Statements

Several operator commands are available to modify the statements in the
CONSOLxx parmlib member.

Potential Effects of Altering Console Attributes

Altering some console attributes might cause a message loss or SYNCHDEST loss.
If a loss occurs, MVS issues a DISPLAY CONSOLE,HCONLY command and
message IEE889I. You need to understand that this can happen and can affect
automation.

The potential for this situation to occur comes from using these commands:
VARY CN
VARY CONSOLE
CONTROL V,LEVEL
SWITCH CN

The CONSOLE Statement of CONSOLxx

A CONSOLE statement in the CONSOLxx parmlib member establishes the device
as an MCS or SMCS console and defines certain console values or attributes.
These values are specified by system programmers or are IBM defaults. After IPL,
operators can use certain commands to change these attributes. The effects of
these commands last only for the duration of the IPL; at the next IPL, the values will
be those in the parmlib members or the IBM defaults.

CONSOLxx contains console definitions for the system or sysplex.

Table 3-1. Comparison of System Commands and CONSOLE Parameters in CONSOLxx
MVS Commands CONSOLE Characteristic that the Parameter
Parameters with Affects
DEFAULT
CONTROL A AREA Size of the out-of-line display areas
CONTROL N,PFK PFKTAB PFK table
CONTROL S,CON CON(N) Conversational or nonconversational
mode
CONTROL S,DEL DEL(RD) Message deletion mode
CONTROL S,MFORM MFORM(M) Format in which the messages appear

Copyright IBM Corp. 1988, 2006 3-1

 Table 3-1. Comparison of System Commands and CONSOLE Parameters in
CONSOLxx (continued)
MVS Commands CONSOLE Characteristic that the Parameter
Parameters with Affects
DEFAULT
CONTROL S,RNUM RNUM(5) Number of message lines included in
one message roll
CONTROL S,RTME RTME(2) Number of seconds between message
roll/wrap
CONTROL S,SEG SEG Number of lines in the message area
that can be deleted by a CONTROL
E,SEG command
CONTROL V,CMDSYS CMDSYS Systems where commands on a console
can be directed for processing
CONTROL V,LEVEL LEVEL Message levels for the console
CONTROL V,USE USE(FC) Console operating mode
MONITOR MONITOR Monitoring of certain events
MSGRT MSGRT Routing of system commands to a
specified console and message area
VARY CN,ALTGRP ALTGRP Alternate group for the console
VARY CN,AMSCOPE MSCOPE Systems that direct messages to a
console
VARY CN,DMSCOPE

VARY CN,MSCOPE
VARY CN,AUTH AUTH(INFO) Command groups
VARY CN,LOGON LOGON Defines the LOGON attribute
VARY CN,LU LU Defines the predefined LU for an SMCS
console only
VARY CN,ROUT ROUTCODE Routing codes for the console
VARY CN,AROUT
VARY CN,DROUT

The INIT Statement in the CONSOLxx Member

The INIT statement contains initialization values for the system. You code only one
INIT statement in the CONSOLxx member for all the consoles.

Table 3-2 describes each MVS command that has a corresponding parameter on
the INIT statement in CONSOLxx, the parameter, and the characteristic that the
command and parameter affect. The value in parentheses indicates the default.
Table 3-2. Comparison of System Commands and INIT Statements in CONSOLxx
MVS Command Parameter on INIT Characteristic that the Parameter
Statement with default Affects
value
CONTROL M,AMRF AMRF(Y) Establishes whether the action
message retention facility is to be
active
CONTROL M,APPLID APPLID Sets the APPLID used by SMCS
on this system

3-2 z/OS V1R7.0 MVS System Commands

 Table 3-2. Comparison of System Commands and INIT Statements in
CONSOLxx (continued)
MVS Command Parameter on INIT Characteristic that the Parameter
Statement with default Affects
value
CONTROL M,GENERIC GENERIC Sets the GENERIC used by SMCS
for the entire sysplex
CONTROL M,MLIM MLIM(1500) Limits the number of buffers for
WTO messages that the system
has not yet displayed
CONTROL M,LOGLIM LOGLIM(1000) Limits the number of buffers for
messages that the system sends to
the system log
CONTROL M,RLIM RLIM(10) Limits the number of WTOR
messages that the system has
displayed but that the operator has
not replied to
CONTROL M,UEXIT UEXIT(Y) Establishes whether the installation
exit IEAVMXIT is to be active
MONITOR MONITOR Establishes how the system
displays mount and demount
messages in response to the
MONITOR command
SET CNGRP CNGRP(NO) Specifies the CNGRPxx parmlib
members that the system is to use
SET MMS MMS(NO) Specifies the MMSLSTxx parmlib
member that holds the translation
tables that are available for your
system
SET MPF MPF(NO) Specifies the MPFLSTxx parmlib
members that the system is to use
SET PFK PFK(NONE) Specifies the PFKTABxx parmlib
member that holds the PFK tables
that are available for your consoles
TRACE CT,PARM= CTRACE(CTIOPS00) Specifies the CTnOPSxx parmlib
member that contains tracing
options for the operations services
(OPS) component

The HARDCOPY Statement in the CONSOLxx Member

Table 3-3 describes each VARY HARDCPY command operand, the corresponding
parameter in CONSOLxx parmlib member, and the task the command and
parameter performs. The value in parentheses indicates the default.
Table 3-3. Comparison of VARY HARDCPY Commands and HARDCOPY Statements in
CONSOLxx
VARY HARDCPY Parameters on Description
Command Parameters HARDCOPY Statement
devnum, SYSLOG, or DEVNUM Establishes whether the hardcopy
OPERLOG medium is a device, SYSLOG, or
OPERLOG

Chapter 3. Defining and Changing Console Characteristics 3-3

 Table 3-3. Comparison of VARY HARDCPY Commands and HARDCOPY Statements in
CONSOLxx (continued)
VARY HARDCPY Parameters on Description
Command Parameters HARDCOPY Statement
ROUT ROUTCODE Establishes the routing codes for
messages included in the hardcopy
message set
NOCMDS, INCMDS, CMDLEVEL Establishes whether the hardcopy
STCMDS, or CMDS message set includes operator
commands, responses, or status
displays

The HARDCOPY statement is optional; CONSOLxx contains only one statement for
each system. If the HARDCOPY default is used, the system uses the following
defaults:
v The hardcopy medium is SYSLOG.
v The system uses a minimum set of routing codes (1, 2, 3, 4, 7, 8, 10, and 42) to
select messages for the hardcopy message set.
v CMDLEVEL(CMDS) is used to select the level of commands included in the
hardcopy message set.

The DEFAULT statement in CONSOLxx

The system programmer uses the DEFAULT statement to control certain default
values for MCS and SMCS consoles in the configuration. DEFAULT lets the system
programmer specify console attributes that control the following for console
configuration:
v Console security by specifying operator logon options
v Certain console screen functions for all consoles (ability for operators to hold
moving or wrapping messages on the screen)
v Routing for messages without routing codes or other message queuing
information, and routing for synchronous messages that bypass normal message
queuing
v Determining the maximum value for operator REPLY ids.

Unlike values in CONSOLE and INIT, operators cannot change individual DEFAULT
statement values. Operators must re-IPL the system with the CONSOLxx member
that contains the new DEFAULT statement.

Displaying Information About Console Characteristics

To learn the current characteristics of the console, use the DISPLAY CONSOLES,A
command. The output is message IEE889I, which contains information about the
systems use of consoles as well as information about each consoles
characteristics. Figure 3-1 shows the output of the command. For a complete
description of message IEE889I, use LookAt (see Using LookAt to look up
message explanations on page xviii) or use the MVS System Messages books.

3-4 z/OS V1R7.0 MVS System Commands

 SY2 IEE889I 14.51.23 CONSOLE DISPLAY 636 C
MSG: CURR=1 LIM=1500 RPLY:CURR=0 LIM=99 SYS=SY2 PFK=NONE
CONSOLE ID --------------- SPECIFICATIONS ---------------
SYSLOG COND=H AUTH=CMDS NBUF=N/A
ROUTCDE=ALL
C3E0SY1 01 COND=M AUTH=MASTER NBUF=N/A
03E0 AREA=Z MFORM=S
SY1 DEL=RD RTME=1 RNUM=19 SEG=9 CON=N
USE=FC LEVEL=ALL PFKTAB=*DEFAULT
ROUTCDE=ALL
CMDSYS=SY1
MSCOPE=*ALL
MONITOR=JOBNAMES,SESS
C3E0SY2 21 COND=A AUTH=MASTER NBUF=1
03E0 AREA=Z MFORM=S
SY2 DEL=RD RTME=1 RNUM=19 SEG=19 CON=N
USE=FC LEVEL=ALL PFKTAB=*DEFAULT
ROUTCDE=ALL
CMDSYS=SY2
MSCOPE=*ALL

Figure 3-1. Example of DISPLAY CONSOLES,A Command Output

Changing Console Characteristics

You can change the characteristics of MCS and SMCS consoles dynamically
through MVS commands.

System Commands Grouped According to System Command Authority

If an MVS operator command is not RACF-protected (for example, if the RACF
OPERCMDS class is not active, or if no OPERCMDS profile covers the command),
the authority to issue the MVS command is granted based on the command group.
There are five command groups:
v Informational commands (INFO)
v System control commands (SYS)
v I/O control commands (IO)
v Console control commands (CONS)
v Master level authority commands (MASTER)

| If RACF is used to control who can issue commands, the RACF OPERCMDS
settings override the command group (AUTH) settings. For example, if the user has
access to the correct OPERCMDS profile, a job submitted in a class with
AUTH(INFO) will issue a MODIFY command. Similarly, if the user does not have
access to the proper OPERCMDS profile, a job submitted in an AUTH(ALL)
jobclass will be unable to issue a MODIFY command.

The commands in each group are shown in Table 3-4. The command groups are
ordered from the lowest to the highest JES authority level, as described in z/OS
JES2 Commands or z/OS JES3 Commands.

You can enter informational commands from any full-capability console. However, to
enter system control, I/O control, or console control commands from a secondary
console, that particular command group must be assigned to that console. If you
enter a command at a console where it is not authorized, MVS rejects the
command and sends an error message to the issuing console.

At the master console, you can enter all operator commands. Any console with
AUTH(MASTER) in the CONSOLxx parmlib member has master console authority.

Chapter 3. Defining and Changing Console Characteristics 3-5

 In a sysplex, the first system that IPLs and has a MCS console statement with
AUTH(MASTER) in the CONSOLxx parmlib member defines the master console for
the sysplex.

Using RACF, the installation can allow the operators to log on to any MCS or SMCS
console. IBM recommends logon for SMCS. The operators RACF profile and group
authority determines what commands can be issued from the console. For a list of
MVS commands and their profile names, see z/OS MVS Planning: Operations.
Table 3-4. Command Groups Used to Determine Command Authority
Command Group Commands
INFO CMDS DISPLAY REPLY (See Note 4 on page 3-7)
CMDS SHOW ROUTE
CONTROL (See Note 3 on page 3-7) SEND
DEVSERV STOPMN
DISPLAY (See Note 1 on page 3-7)
LOG
LOGOFF
LOGON
MONITOR
MSGRT (See Note 1 on page 3-7)
| SYS (system ACTIVATE SETAPPC
| control) CANCEL SET GRSRNL
| CHNGDUMP SETETR
| DUMPDS SETIOS
| HALT (See Note 2 on page 3-7) SETLOAD
| HOLD SETOMVS
| LIBRARY SETPROG
| MODE SETSMF
| MODIFY SETSMS
| PAGEADD SLIP
| PAGEDEL START
| RELEASE STOP
| RESET SWITCH SMF
| SET TRACE (with CT, ST, or STATUS)
| WRITELOG
IO (I/O control) ASSIGN VARY {NET } (See Note 2 on page 3-7)
MOUNT {OFFLINE} (See Note 5 on page 3-7)
SWAP {ONLINE } (See Note 5 on page 3-7)
UNLOAD {PATH }
{name or [/]devnum}
CONS (console CONTROL (See Note 3 on page 3-7) VARY {CN{...}[,ALTGRP=...] }
control) {OFFLINE} (See Note 5 on page 3-7)
{ONLINE } (See Note 5 on page 3-7)
{PATH }
{name or [/]devnum }
MASTER (master CMDS ABEND SWITCH CN
console control) CMDS REMOVE TRACE (with MT)
CONFIG VARY {CN(...)[,AUTH=...]}
CONTROL (See Note 3 on page 3-7) {CN(...)[,LOGON=...]}
DUMP {CN(...)[,LU=...]}
FORCE {CONSOLE[,AUTH=...]}
IOACTION {GRS }
QUIESCE {HARDCPY }
RESET CN {MSTCONS }
SETCON {OFFLINE,FORCE }
SETGRS {XCF }
| SETLOGR
| SETLOGRC
SETSSI
SETXCF

3-6 z/OS V1R7.0 MVS System Commands

 Table 3-4. Command Groups Used to Determine Command Authority (continued)
Command Group Commands

Notes:
1. CONS command group when message routing is specified.
2. HALT NET and VARY NET are related to the Virtual Telecommunications Access Method (VTAM)
3. CONTROL is in the INFO command group except when
| v Purging the message queues of any other full-capability MCS or SMCS console MASTER.
v Message routing is specified CONS.
v Changing or displaying the status of the action message retention facility MASTER.
v Changing or displaying the number of allowed message buffers MASTER.
v Changing or displaying the status of WTO user exit IEAVMXIT MASTER.
v In a sysplex, changing the maximum time to wait for aggregated command responses MASTER.
v Increasing the number of reply IDs MASTER.
4. An operator can reply to any message that the console is eligible to receive. Any console with master authority
can reply to any message.
5. VARY CN,OFFLINE and VARY CN,ONLINE require CONS. Without the CN keyword, VARY OFFLINE and VARY
ONLINE require IO authority.

Changing the Authorization of a Console

You can change the system command groups that a console is authorized to enter.

You change the authorization of consoles by:

v Using the VARY Command:
The VARY CN,AUTH= command defines which system command groups may be
entered through the consoles specified on the AUTH= keyword.
Example
To assign master level authority to a console named REMOTE, enter:
VARY CN(REMOTE),AUTH=MASTER
Enter this command through any console that has master console authority. If
you try to enter this command from a console without master console authority,
the command is rejected and a message appears to indicate that the switch did
not take place.
The effect of this command lasts only for the duration of the IPL.

Changing the Master Console in a System or Sysplex

By assigning the system command groups for a console, you establish the master
console and the command level for other consoles. In a sysplex, the first system
that IPLs and has a MCS console statement with AUTH(MASTER) in the
CONSOLxx parmlib member defines the master console for the sysplex.

You assign the master console by:

v Using the VARY Command:
The VARY device,MSTCONS command defines the master console.
Example
To reassign the console named CON31E as a console with master console
authority, enter:
VARY CON31E,MSTCONS

Chapter 3. Defining and Changing Console Characteristics 3-7

 Enter this command through any console that has master console authority. If
you try to enter this command from a console without master console authority,
the command is rejected and a message appears to indicate that the switch did
not take place.
The effect of this command lasts only for the duration of the IPL.

See Selecting a Master Console Using Alternate Console Groups to define a

master console when no full-capability consoles are available.

Console Groups
Each MCS, SMCS or extended MCS console can be assigned a console group to
be used as a backup if a console fails. An extended MCS console (1) increases the
number of consoles by using TSO/E terminals on MVS systems or (2) allows
applications and programs to access MVS messages and send commands. See
z/OS MVS Planning: Operations for information about extended MCS consoles.

The console group is a list of other functioning consoles in the system configuration,
with the same or greater capability (that is, a full-capability console can be the
alternate for a status display console, but an output-only console cannot back up a
full-capability console). When the system detects that the console is failing, it
automatically switches to the first available console in the failing consoles alternate
console group. If the system cannot find an active alternate, the system does not
switch the failing console. See z/OS MVS Planning: Operations for more information
about the arrangement of console groups.

To determine the alternate console group for your consoles, use the DISPLAY
CONSOLES command. Figure 3-1 on page 3-5 shows the display that appears in
response to this command.

You assign an alternate console group by:

v Issuing the VARY Command:
Use the ALTGRP operand on the VARY command to assign an alternate console
group. Console groups and their members are defined in CNGRPxx.
Example
To assign the console group group9 as the alternate console group for the
console TAPECN, enter:
VARY CN(TAPECN),ALTGRP=GROUP9
The effect of this command lasts only for the duration of the IPL. The system
programmer can specify ALTGRP on the CONSOLE statement in CONSOLxx to
make a permanent change.

Selecting a Master Console Using Alternate Console Groups

When no full-capability consoles are available in a system or a sysplex, you can
select a console from an alternate console group specified on the INIT NOCCGRP
statement and activate it as the master console. When the operator presses the
attention interrupt key on any console device that is a member of the alternate
console group and then presses the external interrupt key of the system console,
MVS can activate the console as the master console.

Switching Console Attributes from One Console to Another

Operators can use the SWITCH command to switch console attributes between
consoles. Using SWITCH might help to
v Handle message traffic during operator shifts

3-8 z/OS V1R7.0 MVS System Commands

 v Redistribute operator workload by rerouting messages.

Consoles can be MCS, SMCS or extended MCS consoles. Operators can use
SWITCH to do the following:
v Switch the console attributes of an active or inactive console to another console.
| v Switch the console attributes of an active or inactive console to its first available
| alternate in the alternate console group.
v Restore the console attributes of an inactive console that has switched to an
active alternate.

| When an operator uses the SWITCH command to switch from a console to another
| console, MVS first appends the console attributes with the other console and then
| deactivates the switched console.

Defining Console Use

MCS consoles can operate in one of the following ways:
v Status Display Console
v Message Stream Console
v Full-capability Console

Note: In this book, the term output-only mode refers to status display mode and
message stream mode.

Note: SMCS consoles are not permitted to be status display or message stream
consoles. SMCS consoles may only be full-capability consoles.

Using a Status Display Console

A status display console has output capability only; it cannot be used to enter
commands. The system uses the screen to receive status displays.

A console in status display mode provides a convenient area for displaying system
status information and frees the master console for use by other system messages.

You can divide the screen of the status display console into display areas,
according to your needs.

Controlling Displays on Status Display Consoles: Because a status display

console has no input capability, you must enter each request concerning the
console on a separate full-capability console. Use the routing location operand with
each command to designate the console and display area at which an action is to
take place, or define routing defaults with the MSGRT command.

The routing location operand can be entered only from a console with CONS
(console control) command group authority. Command group authority is described
under System Commands Grouped According to System Command Authority on
page 3-5.

Using a Message Stream Console

A message stream console has output capability only; it cannot be used to enter
commands. The system uses the screen to present general messages.

A console in message stream mode provides an area for presentation of messages

away from the master console. The messages sent to a message stream console

Chapter 3. Defining and Changing Console Characteristics 3-9

 depend on the routing codes or message levels assigned to that console. Message
stream consoles can provide system monitoring capabilities in tape or disk libraries,
or can assist in system security.

Deleting Messages from Message Stream Consoles

When a console enters message stream mode, roll-deletable message deletion

goes into effect automatically. (See Defining Automatic Message Deletion later in
this section.) All messages except action messages are automatically removed from
the screen.

Using a Full-Capability Console

A full-capability console has both input and output capability; the console can be
used both to enter commands and to receive status displays and messages. One
full-capability console is the master console; there can be many full-capability
consoles in the system or sysplex.

You can divide the screen on a full-capability console so that part of the screen
receives general messages and the other part receives status displays. When a
status display is not on the screen, MCS uses the status display area for general
messages.

Changing Full-Capability to Message Stream or Status Display Mode

The screens of the message stream console and the status display console appear
identical; they do not have any entry area. However, the screens of the consoles in
message stream mode receive general messages and the screens of the status
display consoles receive formatted status displays.

When you change a full-capability console to message stream or status display

mode, the PFK display line, the instruction line, and the entry area are incorporated
into the message area or the display area. Figure 3-2 shows the 3277 model 2, in
message stream mode. Once a display console enters message stream or status
display mode, it can accept no more input; you must use another console to enter
commands. Examples at the end of this section illustrate how the display on a
full-capability console changes to the display on a status display or message stream
console.

3-10 z/OS V1R7.0 MVS System Commands

 1
2

Message Area

nn Warning Line

Figure 3-2. Format of a Console Screen in Message Stream Mode

The system gives you the following choices for operating mode for MCS consoles:
FC Full-capability
MS Message stream
SD Status display

SMCS consoles may only be FC (full-capability) mode consoles. The operating

mode of an SMCS console cannot be changed.

If a console is an input/output device, the default operating mode is full-capability

mode.

You can check the console operating mode by entering the CONTROL V,REF
command. In response to this command, the specifications appear in the entry
area. You can change the specifications using the procedures described under
Changing Information in the Entry Area on page 2-13.

You define the operating mode of a console by:

v Using the CONTROL Command:
Use the USE operand on the CONTROL V command to change the operating
mode of a console. You cannot change a console to message stream or status
display if it is the master console; you must first designate another console to
take over the master console function.

Example 1

To define the console with a console name of CON8 as a full-capability console,

enter:
CONTROL V,USE=FC,L=CON8

The effect of this command lasts only for the duration of the IPL.

Note: When you use the CONTROL command to change the console operating
mode, you might also have to change other console characteristics. If the

Chapter 3. Defining and Changing Console Characteristics 3-11

 new definition for the console operating mode is incompatible with other
characteristics, the system rejects the CONTROL command.

Example 2

To change the console in Example 1 from full-capability mode to status display

mode, enter:
CONTROL V,USE=SD,L=CON8

In response to this command, any information on the screen disappears, and the
system reestablishes the display area specifications that were defined in the
CONSOLxx parmlib member. If you were changing the console from full-capability
mode to message stream mode, information on the screen would disappear and the
message area would expand, as in Figure 3-2 on page 3-11.

Example 3

To return CON8 to full-capability mode, enter the following command from a

full-capability console:
CONTROL V,USE=FC,L=CON8

| In response to this command, the message area of the console with a console
| name of CON8 returns to its full-capability size, and the console specifications
return to those established the last time the console was in full-capability mode for
this IPL or those established in the CONSOLxx member.

The display area specifications also return to the specifications established the last
time the console was in full-capability mode.

Controlling System Messages and Commands

Messages are the systems chief means of communication with you. Messages
range from informational, which are important but do not require a response, to
immediate action, which are not only important but require that you perform the
requested action at once. The action might be required because the message
issuer waits until the action is performed, or because taking the action as soon as
possible can improve system performance. Less urgent, but still important, are the
eventual action and critical eventual action messages. The message issuer is
not waiting for you to perform the action, but a number of unanswered requests
might degrade system performance.

The size of the screens message area varies, depending on the type of display
console. When the message area becomes full, you need to delete messages to
make room for new ones. You can delete messages, or have the system do it for
you automatically. (See Deleting Messages from the Console Screen later in this
chapter.) Once an action message is deleted from the screen, you cannot see the
entire message again unless the action message retention facility is active and you
have issued a DISPLAY R command.

So that you do not have to delete messages too often, make sure that you manage
message traffic carefully on all consoles. For example, if you find that the master
console screen fills often with action messages, think about:
v Adjusting routing codes and assigning message levels. Any console should
receive only messages for which the operator of that console is directly
responsible.

3-12 z/OS V1R7.0 MVS System Commands

 v Activating the action message retention facility so you can put the console in roll
mode without losing action messages.

Defining Routing Codes for a Console

Most messages have one or more routing codes. The system uses these codes,
decimal numbers from 1 to 128, to determine which console or consoles should
receive a message. The system programmer assigns routing codes to the consoles
attached to your system so that a specific message type is routed to the proper
console. Table 3-5 lists the routing codes.

Routing codes do not appear with a message at a console; routing codes 1 through
28 do, however, appear on the system log. To determine the routing codes each
console receives, use the DISPLAY CONSOLES,A command. Figure 3-1 on page
3-5 shows the display that appears in response to this command.
Table 3-5. Message Routing Codes
Code Definition

1 Master console action

2 Master console information
3 Tape pool
4 Direct access pool
5 Tape library
6 Disk library
7 Unit record pool
8 Teleprocessing control
9 System security
10 System error/maintenance/system programmer information
11 Programmer information
12 Emulators
13-20 Reserved for customer use
21-28 Reserved for subsystem use
29 Disaster Recovery
30-40 Reserved for IBM
41 Information about JES3 job status
42 General information about JES2 or JES3
43-64 Reserved for JES2 or JES3
65-96 Messages associated with particular processors
97-128 Messages associated with particular devices

One way to limit the messages that arrive at a console is to assign a routing code
or codes to a console. The console then receives only the messages that are
appropriate. You might want to direct only messages with routing codes 1, 2, 9, and
10 to the master console. The master console does not have to receive tape,
DASD, or teleprocessing messages.

To learn what the routing codes for a console are, enter the DISPLAY CONSOLES
command. Figure 3-1 on page 3-5 shows the display that appears in response to
this command.

You define routing codes for a console by:

v Using the VARY Command:

Chapter 3. Defining and Changing Console Characteristics 3-13

 Use operands on the VARY command to add to the existing set (AROUT
operand), subtract from the existing set (DROUT), or redefine the set (ROUT).
Example
To assign the routing codes 1, 2, 9, and 10 for a console named CON81D, enter:
VARY CN(CON81D),CONSOLE,ROUT=(1,2,9,10)
The effect of this command lasts only for the duration of the IPL.

Defining Message Levels for a Console

Assigning routing codes is one way to limit message traffic to a console. You can
further reduce the number of messages that appear on a console by directing
certain messages to consoles by message levels. The system differentiates among
these kinds of message levels:
v Write-to-operator with reply (WTOR) messages, which demand an immediate
reply.
v System failure and immediate action messages (descriptor codes 1 and 2), which
indicate that a task is awaiting your action.
v Critical eventual action messages (descriptor code 11), which indicate a potential
system problem.
v Eventual action messages (descriptor code 3), which do not require immediate
attention.
v Broadcast messages, which are normally sent to every active console regardless
of the routing code you assigned to the console.
v Informational messages, which generally indicate system status. (Most messages
are informational.)

Assignment by message level means that a console can accept combinations of

action, broadcast, and informational messages that the system sends to a console.
You can choose among the following message level options:
R Write to operator (WTOR) messages are to appear
I Immediate action messages (descriptor codes 1 and 2) are to appear
CE Critical eventual action messages (descriptor code 11) are to appear
E Eventual action messages (descriptor code 3) are to appear
IN Informational messages are to appear
NB Broadcast messages are not to appear
ALL All messages, including broadcast messages, are to appear.

If the LEVEL parameter in the CONSOLxx member is not coded, the system sends
all messages, including broadcast messages, to the console.

To display the routing codes and message levels for a console, issue the DISPLAY
CONSOLES command. Figure 3-1 on page 3-5 shows the display that appears in
response to this command.

To display the routing codes and message levels that appear only on the system
log and not on any console, issue the DISPLAY CONSOLES,HCONLY command.

You define the level of messages for a console by:

v Using the CONTROL Command:
Use the LEVEL operand on the CONTROL V command to assign message
levels to a console.
Example 1

3-14 z/OS V1R7.0 MVS System Commands

| To direct only WTOR messages and immediate action messages to the console
| with console name CON06, enter:
| CONTROL V,LEVEL(R,I),L=CON06
| When you change message levels so that some informational or broadcast
messages will not appear at any console, the system rejects the CONTROL V
command. If you want to override this rejection, use the UNCOND operand.
These messages then appear only on the system log, the hardcopy console, and
any extended MCS consoles that are receiving the hardcopy message set. The
system displays this message to warn you of the message loss:
IEE828E SOME MESSAGES NOW SENT TO HARDCOPY ONLY
Example 2
| To assign to the console with console name CON12 (and device number 81D)
| the informational messages directed to the tape libraries (routing code 5) and
| disk libraries (routing code 6), enter:
| VARY 81D,CONSOLE,ROUT=(5,6)
| CONTROL V,LEVEL=IN,L=CON12

| Controlling the Format of Messages

On a display console, a message can appear by itself or with information about the
message, such as job and system identification and the time the message was
issued. Messages Sent to Display Consoles on page 2-6 describes the format of
messages and describes the optional information that the system can include with
each message:
J The jobname/job id of its issuer
S The name of the system that issued the message
T A time stamp
M Only the message text displays
X Suppress system and job name of its issuer when S and/or J are specified

You request that additional information precede each message the system
sends a console by:
v Using the CONTROL Command:
Use the MFORM operand on the CONTROL S command to change the format of
messages.
Example
| To request that the system add to all messages that appear at console CON2 a
| time stamp, the name of the system that issued the message, and the jobname
| or ID of its issuer, enter:
| CONTROL S,MFORM=(J,T,S),L=CON2
| The effect of this command lasts only for the duration of the IPL.

Controlling the Message Processing Facility (MPF)

The message processing facility (MPF) controls message processing. It controls the
suppression and retention of messages, the installation exits that gain control when
certain messages are issued, and message presentation (that is, the color, intensity
and highlighting of messages) at certain consoles.

The operator can:

v See what MPF member or members are active with the DISPLAY command
v Change the active MPF member or members with the SET command.

Chapter 3. Defining and Changing Console Characteristics 3-15

 For MPF to suppress messages, hardcopy processing must be active. The
suppressed messages do not appear on any console; they do appear on the
system log, the hardcopy console, and any extended MCS consoles that are
receiving the hardcopy message set.

Message Presentation

Message presentation refers to the way the system uses color, intensity, and
highlighting (including blinking, reverse-video, and underscoring) to identify
messages that require action. The presentation depends on the type of device you
are using.

Using the SET Command:

Enter the SET MPF command to change the MPFLSTxx member or members that
the system is to use.

Example

To specify MPFLST03 and MPFLST06 as the MPF members for the system to use,
enter:
SET MPF=(03,06)

The effect of this command lasts only for the duration of the IPL.

Displaying Information About Messages Awaiting Action

Many systems now handle so much work so quickly that you cannot always keep
up with the messages that demand operator response. These messages roll off the
screen before you can respond. The action message retention facility keeps these
messages, including the WTORs and JES3 messages, so that you can see them at
a later time. (While you are examining the messages that you missed, you might, of
course, miss more messages. Experience with your system will help you determine
how frequently you need to check for retained action messages.)

The DISPLAY R command allows you to display all outstanding action messages or
a subset of these messages. For example, to display all outstanding action
messages at your console, enter DISPLAY R,M. To display all the outstanding
critical eventual-action messages (descriptor code 11), enter DISPLAY R,CE. See
z/OS MVS Planning: Operations for use of the DISPLAY R command.

Controlling the Action Message Retention Facility

During its initialization, the system can start the action message retention facility
(AMRF). When active, the facility retains in a buffer area all action messages (those
messages with descriptor codes 1, 2, 3, and 11) except those specified by the
installation in the active MPFLSTxx member.

If the first system IPLs and AMRF is active, then AMRF is active on every system
that you subsequently IPL into the sysplex.

When you have performed the action required by a message displayed on the
screen, the system deletes the message; or you can use the CONTROL C
command to delete the message. You can remove action messages from the
screen that require later action, then retrieve them in their entirety later by using the

3-16 z/OS V1R7.0 MVS System Commands

 DISPLAY R command. Periodically, you should display the retained messages and
delete the ones for which action has been taken so that the action message
retention buffer does not fill up.

To change the messages that the action message retention facility is to retain,
activate an MPFLSTxx member that contains the message retention options you
want. The system default is to have the action message retention facility on.

To learn the status of the action message retention facility, issue the CONTROL
M,REF command.

You change the status of the action message retention facility by:
v Using the CONTROL Command
Use the CONTROL M,AMRF command to turn the action message retention
facility on or off.
Example
To deactivate the action message retention facility, enter:
CONTROL M,AMRF=N

Activating WTO and WTOR Installation Exit Routines

The system programmer at your installation codes installation exit routines that gain
control when the system issues certain messages. A WTO installation exit can
change routing codes, descriptor codes, and message texts, as well as perform
other message processing; it can override MPF processing. Information about
coding these installation exits appears in z/OS MVS Installation Exits.

The most effective message control involves coding and installing the installation
exit IEAVMXIT, which can gain control when any WTO or WTOR message is
issued.

To learn whether IEAVMXIT is active or not, issue the CONTROL M,REF command.
The system displays (in the entry area) the status of the action message retention
facility, the status of installation exit IEAVMXIT, and the limit of the number of WTO
and WTOR buffers.

Your installation might have other exit routines to process messages. MPFLSTxx
parmlib members contain the IDs of messages and the installation exits that
process these messages. To activate processing by these installation exits, see
Controlling the Message Processing Facility (MPF) on page 3-15.

You can activate the installation exit IEAVMXIT, if it is installed, by:

v Using the CONTROL Command:
From the master console, use the UEXIT operand on the CONTROL command
to control whether the installation exit IEAVMXIT is active.
Example
To deactivate IEAVMXIT, enter:
CONTROL M,UEXIT=N
The effect of the command lasts only for the duration of the IPL.

Checking Message Processing, Retention, and Presentation Options

Issue the DISPLAY MPF,MSG command to see:
v Which messages are being suppressed by MPF

Chapter 3. Defining and Changing Console Characteristics 3-17

 v Which action messages are not being retained by the action message retention
facility
v Which installation exits receive control for selected messages
v The status of the general WTO installation exit IEAVMXIT
v Whether this message is automated by MPF
v The MPFLSTxx member that identifies the message ID, color attribute, or
command installation exit definition
| v A list of the subsystems receiving foreign messages and DOMs

Issue the DISPLAY MPF,COLOR command to see:

v What color, intensity, and highlighting capabilities are in effect

Issue the DISPLAY MPF command to see all of this information for the messages
that are defined in the MPFLSTxx parmlib member.

Defining Program Function Keys (PFKs)

You can define program function keys for a console by activating a PFK table or by
using the CONTROL N,PFK= command.

Defining PFKs Using PFK Tables

You define a consoles PFKs by activating a PFK table a table that your
installation has defined. The PFK table resides, optionally with other PFK tables, in
a PFKTABxx parmlib member. The entries in this table:
v Assign one or more commands to a PFK
The text of one or more commands are to be associated with a PFK. Later, when
you press this PFK, the commands are entered into the system.
v Assign one or more other PFKs to a PFK
The commands associated with other PFKs are to be associated with one PFK.

Entries in the PFK table also determine whether conversational or

nonconversational mode is to be in effect for a command defined to a PFK. In
nonconversational mode, the commands associated with a key are entered
immediately when you press the key. In conversational mode, pressing a PFK
causes the command to appear in the entry area, but no enter action takes place.
You can change, enter, or cancel the command according to your requirements.

In conversational mode, the cursor normally appears under the third non-blank
character when the command is in the entry area. If you want the cursor to appear
in a different location, when you define the command, type an underscore before
the character under which the cursor is to appear. The system deletes the space
occupied by the underscore in the actual command. For example, if you add the
following entry to a PFK table:
PFK(5) CMD(D U,L=_XXX) CON(Y)

pressing PFK 5 causes the following to appear in the entry area:

D U,L=XXX

If you want an underscore to appear in the command, code two consecutive

underscores. The system will treat them as a single underscore, and will not use
them for cursor placement. Example:

If the PRKTAB table contains:

3-18 z/OS V1R7.0 MVS System Commands
 PFK(17) CMD(E _XXXXXXXX,SRVCLASS=BAT__HI),CON(Y)

when you press PFK17, the entry area will contain:

E XXXXXXXX,SRVCLASS=BAT_HI

with the cursor under the first X.

Selector pens also use the definitions in PFK tables.

You can use some MVS commands to display information about the PFKs at your
console, or to change the PFKs that are available for your consoles. The following
commands relate to the previous example:
v Display the PFK definitions in the PFK table named MVSCMDS.
DISPLAY PFK,TABLE=MVSCMDS
v List the names of all PFK tables in the active PFKTABxx member.
DISPLAY PFK,TABLE
v Assign the commands in the PFK table named JES2CMDS to the PFKs on your
console.
CONTROL N,PFK=JES2CMDS
v Activate another PFKTABxx member, in this case PFKTAB02.
SET PFK=02
This command assumes that you have a PFK table in PFKTAB02 and that you
want to replace MVSCMDS with another PFK table. (Other consoles might be
using tables in the former PFKTABxx member. PFK definitions for these consoles
are not affected by the action of this SET command.)

Defining PFKs Using the CONTROL Command

Use the CONTROL N,PFK= command to change the definition for PFKs. This
command performs three tasks:
v Assigns one or more commands to a PFK
v Assigns one or more other PFKs to a PFK
v Assigns a PFK table to your console.

With the CONTROL N,PFK= command you can also determine whether
conversational or nonconversational mode is to be in effect for the commands
defined to the PFK. Nonconversational mode is the default. For example, if you
define PFK 5 as follows:
| CONTROL N,PFK=(5,CMD=D U,L=CON9A),CON=N

| pressing PFK 5 has the same effect as typing DISPLAY U,L=CON9A and pressing
| the ENTER key.

On the other hand, if you specify conversational mode by entering:

| CONTROL N,PFK=(5,CMD=D U,L=CON9A),CON=Y

pressing PFK 5 causes the command D U,L=CON9A to appear in the entry area
but no enter action takes place. You can change, enter, or cancel the command
according to your requirements.

The system does not accept PFK assignments that may result in an endless loop.
Examples of commands that the system will not accept are:
v You cannot assign a PFK to itself. For example, the system does not accept
CONTROL N,PFK=(9,KEY=9).
Chapter 3. Defining and Changing Console Characteristics 3-19
 v If a PFK is being assigned a list of PFKs (that is, a key list), that PFK cannot
appear in the key list for another PFK. For example, if PFK 5 is already
associated with keys 3 and 4, the system does not accept CONTROL
N,PFK=(6,KEY=5,8).
v If a PFK is already in a key list, you cannot assign a key list to that PFK. For
example, if key 4 is associated with keys 5 and 6, the system does not accept
CONTROL N,PFK=(5,KEY=7,8).

Remember that the assignment of the command to the PFK through the CONTROL
command lasts only for the duration of the IPL.

Example 1

If PFK 3 is associated with commands SET OPT=PM and SEND 14,BRDCST, and
PFK 4 is associated with the command START
GTF,MODE=INT,BUF=387,TIME=YES,DEBUG=YES, you can associate all three of
these commands with PFK 5 by entering:
CONTROL N,PFK=(5,KEY=3,4),CON=Y

The commands associated with PFK 5 are now:

SET OPT=PM
SEND 14,BRDCST
START GTF,MODE=INT,BUF=387,TIME=YES,DEBUG=YES

The system schedules the commands in that order, but might not execute them in
that order.

Example 2

To remove a definition previously set for PFK 5, leaving PFK 5 undefined, enter:
CONTROL N,PFK=(5,CMD=)

The PFKTABxx and PFKs

The PFKTABxx parmlib members contain the PFK tables that have the definitions
your installation has assigned to PFKs. To associate your consoles PFKs with the
definitions in a particular PFK table:
v The PFK parameter on the INIT statement in the active CONSOLxx member
must identify the PFKTABxx member that contains the table.
v The PFKTAB parameter on the CONSOLE statement in CONSOLxx must identify
the name of the PFK table.
v The particular table must contain entries; each entry supplies a command or
commands associated with a PFK.

You use CONSOLxx and PFKTABxx members to set the PFK definitions at IPL. You
can also change the PFK definitions for the duration of the IPL:

To change a PFK table:

1. Enter SET PFK=xx, if necessary, to change the PFKTABxx member in effect for
the console. Other consoles using the former PFKTABxx member are not
affected by the SET command you issue for your console.
2. Enter CONTROL N,PFK=nnnnnnnn to assign the PFK table that contains the
PFK definitions you want to use for the console.

To change a PFK key:

3-20 z/OS V1R7.0 MVS System Commands

 v Enter CONTROL N,PFK=(nn1,CMD=...) to change a specific PFK key definition
for the console where the command is entered.

During IPL, the system looks for the PFK parameter in CONSOLxx member. If the
system does not find the PFK parameter, it issues the message:
IEA180I USING IBM DEFAULT DEFINITIONS. NO PFK TABLES REQUESTED

| In this case, PFKs 1 through 8 have the defaults that IBM supplies. These defaults
| are shipped in sample IEESPFK.

To define PFKs for your consoles, see Defining PFKs Using PFK Tables on page
3-18.

Processing Hardcopy
Logging provides a permanent record of system activity. Your installation can record
system messages and, optionally, commands and command responses, by using
either the system log (SYSLOG) or the operations log (OPERLOG). Your installation
can also allow an extended MCS console to receive the same set of messages as
SYSLOG and OPERLOG. The log that receives messages is called the hardcopy
medium. The group of messages that is recorded is called the hardcopy message
set.

The hardcopy message set is defined at system initialization and persists for the life
of the system. See z/OS MVS Planning: Operations for the characteristics of the
hardcopy message set.

The Hardcopy Message Set

Unless you specify otherwise, the hardcopy message set includes all messages,
except those that are explicitly omitted through the WTO macro or installation exits.
You can request that the hardcopy message set not include messages with certain
routing codes. The minimum set of routing codes is 1, 2, 3, 4, 7, 8, 10, and 42. If
you attempt to eliminate any of these, the system includes messages with these
routing codes in the hardcopy message set anyway.

To see information about the kinds of messages that the system includes in the
hardcopy message set, but does not send to any console, issue the DISPLAY
CONSOLES,HCONLY command.

Selecting Messages for the Hardcopy Message Set

You control which messages are included in the hardcopy message set by:
v Using the VARY Command:
Use the VARY,HARDCPY command to specify the routing codes of messages
that are included in the hardcopy message set. You can add to the existing set
(AROUT operand), subtract from the existing set (DROUT), or redefine the set
(ROUT).
Example
To stop including all routing codes except the minimum set, enter:
VARY ,HARDCPY,DROUT(5,6,9,11-41,43-128)
The system would give the same response if you entered the
VARY,HARDCOPY,ROUT=NONE command.
The effect of this command lasts only for the duration of the IPL.

Chapter 3. Defining and Changing Console Characteristics 3-21

 Selecting Commands and Command Responses for the
Hardcopy Message Set
Unless you specify otherwise, the system includes all operator and system
commands, responses, and status displays (including static and time-interval
updated status displays) in the hardcopy message set. To request that some
commands and command responses not be included in the hardcopy message set,
the system gives you the following choices on the VARY ,HARDCPY command:
NOCMDS The system does not include operator commands or their
responses in the hardcopy message set.
INCMDS The system includes all operator commands and their responses,
excluding any status displays, in the hardcopy message set.
| STCMDS The system includes all operator commands and their responses in
| the hardcopy message set.
| CMDS The system includes all operator commands and their responses,
| including all status displays, in the hardcopy message set.

To see which commands and command responses the system includes in the
hardcopy message set, issue the DISPLAY CONSOLES command. Figure 3-1 on
page 3-5 shows the display that appears in response to this command.

Use of the TRACK command in z/OS releases

| Because dynamic displays dealt exclusively with the TRACK command that
| has been removed from z/OS V1R7 and later, dynamic displays are no longer
| issued by z/OS. Multiline messages with descriptor codes 8, 9, 10 appear in
| the log with a hardcopy message of CMDS.

| Note:

You control which commands and command responses are included in the
hardcopy message set by:
v Using the VARY Command:
Use the VARY ,HARDCPY command to change the commands or the command
responses that are included in the hardcopy message set.
Example
To request that the hardcopy message set include all operator commands and
responses except status displays, enter:
VARY ,HARDCPY,INCMDS
The effect of this command lasts only for the duration of the IPL.

The Hardcopy Medium

You can specify whether the hardcopy medium is the system log (SYSLOG) or the
operations log (OPERLOG). If you use SYSLOG as the hardcopy medium, start a
writer that includes the system log message class (A for MVS, unless otherwise
specified in your installation). The SYSLOG spool file is managed by JES and
cannot be browsed or edited using normal means. The external writer will write it to
an SMF-managed file.

The System Log

The system log (SYSLOG) is a direct access data set that stores messages and
commands. It resides in the primary job entry subsystems spool space. It can be

3-22 z/OS V1R7.0 MVS System Commands

 used by application and system programmers (through the WTL macro) to record
communications about programs and system functions. You can use the LOG
command to add an entry to the system log.

Several kinds of information can appear in the system log:

v Job time, step time, and data from the JOB and EXEC statements of completed
jobs entered by user-written routines
v Operating data entered by programs using a write to log (WTL) macro instruction
v Descriptions of unusual events that you enter using the LOG command
v The hardcopy message set

When MVS has JES3 as its job entry subsystem, the system log can record
console activity. If used to record console activity, the system log is referred to in
JES3 messages as DLOG.

In CONSOLxx, you can use the HCFORMAT keyword on the HARDCOPY

statement to specify whether hardcopy records should have a 2-digit or 4-digit year.

The system log is queued for printing when the number of messages recorded
reaches a threshold specified at system initialization. You can force the system log
data set to be queued for printing before the threshold is reached by issuing the
WRITELOG command.

| If the system log is defined as the hardcopy medium and SYSLOG fails, the system
| attempts to switch hardcopy processing. If OPERLOG is not active at the time of
| failure, hardcopy processing is suspended and you are notified through the master
| console.

The Operations Log

The operations log (OPERLOG) is an MVS system logger application that records
and merges the hardcopy message set from each system in a sysplex that
activates OPERLOG. Use OPERLOG rather than the system log (SYSLOG) as your
hardcopy medium when you need a permanent log about operating conditions and
maintenance for all systems in a sysplex.

For more information on OPERLOG, see z/OS MVS Setting Up a Sysplex.

Assigning the Hardcopy Medium

You assign the hardcopy medium by using the VARY command.

Use the HARDCPY operand on the VARY command to assign SYSLOG or

OPERLOG as the hardcopy medium.

Example:

To specify the hardcopy medium as SYSLOG, issue:

VARY SYSLOG,HARDCPY

The effect of this command lasts only for the duration of the IPL.

To display information about the hardcopy medium, enter:

DISPLAY CONSOLES,HARDCOPY

Chapter 3. Defining and Changing Console Characteristics 3-23

 The resulting display tells you whether the hardcopy medium is SYSLOG or
OPERLOG, the criteria that have been defined by the installation for selecting
messages for the hardcopy message set, and the number of messages waiting to
be placed on the hardcopy medium.

3-24 z/OS V1R7.0 MVS System Commands

Chapter 4. MVS System Commands Reference
This chapter describes the functions, syntax, and parameters of all the MVS base
control program (BCP) system commands. You can use these commands to control
both the system itself and multiple console support (MCS) or SNA multiple console
support (SMCS) consoles.

Table 4-1 on page 4-2 sums up the MVS BCP system commands and their
functions. The figure shows the operator command groups for each command and
tells whether you can enter the command from the job stream, an MCS or SMCS
console, or an extended MCS console session. An extended MCS console session
is established either by the TSO/E CONSOLE command as an interactive TSO/E
session or by a program issuing the MCSOPER macro so the program can receive
messages and issue commands. See z/OS TSO/E System Programming Command
Reference for information about the TSO/E CONSOLE command. See z/OS MVS
Programming: Authorized Assembler Services Reference LLA-SDU for information
about the MCSOPER macro.

An installation can use RACF to control which consoles and commands operators
can use. For more information, see z/OS MVS Planning: Operations.

Operator commands may contain the following characters:

v A to Z
v 0 to 9
v #$&()*+,./<|!;%_>?:@=
The system translates characters that are not valid into null characters (X'00').

You can enter operator commands in uppercase or lowercase. Unless enclosed in

apostrophes, lowercase letters are converted to uppercase. Therefore, when a
lowercase response is required, you must enclose the text in apostrophes. Also,
when an apostrophe appears in the text of a command and the text is enclosed in
apostrophes, you must enter two apostrophes in the text. For example, you would
enter:
SEND Your jobs done

You can enter system commands through a multiple console support (MCS)
console, an SNA multiple console support (SMCS) console, an extended MCS
(EMCS) console, or through the input stream (card reader). Table 4-1 on page 4-2
indicates from which types of consoles a command is accepted. Superscripts
denote footnotes that can be found on the last page of the table. All examples in
this book show the format for MCS and SMCS console entry.
Notes:
1. If you enter a system command through a card reader in a JES2 system, enter
$VS,system command when you enter the command between jobs, and enter
//b system command when you enter the command within a job.
2. Do not use the JES backspace character within a system command.

Following the summary figure is a section on command syntax and format. The
syntax rules are shown in How to read syntax conventions on page 4-12.

The rest of this chapter consists of a description of each command in more detail.
The descriptions are in alphabetical order by command name. Each description lists
the functions that the command performs followed by the commands syntax and

Copyright IBM Corp. 1988, 2006 4-1

 parameters. The syntax and parameters of complex commands follow subsets of
the listed functions. Descriptions of the parameters and keywords appear in the
order in which they appear in the syntax.
Table 4-1. System Command Summary
Command Function Acceptable Command
(Abbr) From Group
ACTIVATE Build the interface to and invoke the hardware MCS, SMCS or SYS
configuration definition (HCD) application program extended MCS
interface. console 5
CANCEL (C) Cancel a MOUNT command MCS, SMCS or SYS
extended MCS
Cancel a time-sharing user consoles or job
stream 5
Cancel a cataloged procedure

Cancel a job in execution

Cancel a started catalog procedure

Cancel an external writer allocation

Cancel the writing of a SYSOUT data set by an

external writer session

Cancel a running APPC/MVS transaction program

Cancel a z/OS UNIX System Services process

CHNGDUMP Override dump options specified in parmlib, on the MCS, SMCS or SYS
(CD) ABEND, CALLRTM, and SETRP macros, and in extended MCS
the SDUMP parameter list consoles or job
stream 5
CMDS DISPLAY or SHOW information about commands MCS, SMCS or INFO
that are executing or waiting for execution extended MCS
consoles or job
ABEND or REMOVE executing commands or stream 5
commands waiting for execution MASTER
CONFIG (CF) Place processors online or offline MCS, SMCS or MASTER
extended MCS
Place central storage elements online or offline consoles

Place amounts of central storage online or offline

Place ranges of central storage online or offline

Place expanded storage elements online or offline

Place channel paths online or offline

Place Vector Facilities online or offline MCS, SMCS

or extended MCS console 5

4-2 z/OS V1R7.0 MVS System Commands

 Table 4-1. System Command Summary (continued)
Command Function Acceptable Command
(Abbr) From Group
CONTROL (K) Change display area specifications MCS and SMCS INFO
consoles
Delete certain messages INFO

Halt printing of a status display INFO

Control area displays INFO

Remove information from the screens INFO

Activate, deactivate, or display the status of the MASTER

action message retention facility

Change or display the number of allowed message

and reply buffers MASTER

Change or display message deletion or format INFO

specifications

Change or display the status of WTO user exit

IEAVMXIT MASTER

Define commands for PFKs INFO

| Purge message queue of a console. INFO or

MASTER

Change operating mode of console

INFO
Select the message levels for a console
INFO
Increase the RMAX value
INFO
In a sysplex, change the maximum time MVS waits
before aggregating messages from routed MASTER
commands

MASTER
DEVSERV Display current status of devices and MCS, SMCS or INFO
(DS) corresponding channel paths extended MCS
consoles or job
stream 5

Chapter 4. MVS System Commands Reference 4-3

 Table 4-1. System Command Summary (continued)
Command Function Acceptable Command
(Abbr) From Group
DISPLAY (D) Display APPC/MVS configuration information MCS, SMCS INFO
Console or
Display ASCH configuration information extended MCS
consoles or job
Display IOS configuration stream 5

Display console configuration information

Display z/OS UNIX System Services information

Display MVS message service and current

available languages

Display status of external time reference (ETR)

ports

Display status information for trace

Display system requests and status of the AMRF

Display CONTROL command functions

Display configuration information

Display device allocation

Display current system status

Display system information requests

Display local and Greenwich mean time and date

Display status or contents of SYS1.DUMP data

sets and captured data sets

Display dump options in effect

Display SMF options in effect or SMF data sets

Display information about the cross system

coupling facility information (XCF)

Display information about operation information

(OPDATA) in a sysplex, or display the status of the
Console ID Tracking facility

Display information about the SMS configuration or

the status of SMS volumes or storage groups or
SMS trace options

Display information about all subsystems defined to

MVS.

4-4 z/OS V1R7.0 MVS System Commands

 Table 4-1. System Command Summary (continued)
Command Function Acceptable Command
(Abbr) From Group
DISPLAY (D) Display page data set information MCS, SMCS or INFO
(continued) extended MCS
Display current MIH time intervals for individual consoles or job
devices, or for device classes stream 5

Display SLIP trap information

Display commands defined for PFKs

Display the messages MPF is processing and

color, intensity, and highlighting display options in
effect

Display entries in the list of APF-authorized

program libraries

Display dynamic exits

Display information about the LNKLST set

Display information about modules dynamically

added to the LPA.

Display state of the systems, a particular systems

CTCs, the status of an RNL change, or the
contents of RNLs in the global resource
serialization complex

Display the status of the active workload

management service policy for systems or
application environments

Display information about registered products and

the product enablement policy.

| Display information about system logger and log

| stream resources.
DUMP Request a dump of virtual storage to be stored in a MCS, SMCS or MASTER
SYS1.DUMP data set extended MCS
console 5
DUMPDS Change the systems list of SYS1.DUMP data sets MCS, SMCS or SYS
(DD) extended MCS
Clear full SYS1.DUMP data sets and make them console 5
available for dumps
FORCE Force termination of: MCS, SMCS or MASTER
v A MOUNT command extended MCS
v A job in execution console 5
v An external writer allocation
v The writing of a SYSOUT data set by an
external writer
v A non-cancellable job, time-sharing user, or
started task
v A running APPC/MVS transaction program
HALT (Z) Record statistics before stopping the system (Must MCS, SMCS or SYS
first stop subsystem processing with a subsystem extended MCS
command) console 5
IOACTION Stop or resume I/O activity to DASD MCS, SMCS or MASTER
(IO) extended MCS
console 5

Chapter 4. MVS System Commands Reference 4-5

 Table 4-1. System Command Summary (continued)
Command Function Acceptable Command
(Abbr) From Group
LIBRARY (LI) Eject a volume from a library of removable storage MCS and SMCS SYS
media. consoles

Reactivate processing for certain installation exits

without stopping or restarting the object access
method (OAM).

Set or display the media type of scratch volumes

that the system places into the cartridge loader of
a device within a tape library.

Display tape drive status.

LOG (L) Enter comments in the system log MCS, SMCS or INFO
extended MCS
consoles or job
stream 5
LOGOFF To log off MCS and SMCS consoles MCS and SMCS INFO
consoles
LOGON To access the MCS and SMCS consoles MCS and SMCS INFO
console
MODE Control recording of or suppress system recovery MCS, SMCS or SYS
and degradation machine check interruptions on extended MCS
the logrec data set console 5

Control the monitoring of hard machine check

interruptions
MODIFY (F) Change characteristics of a job by modifying the MCS, SMCS or SYS
job parameters extended MCS
consoles or job
Specify criteria an external writer uses to select stream 5
data sets for processing

Cause an external writer to pause for operator

intervention

Build a new LLA directory

Display information about the catalog address

space or request the catalog address space to
perform a specified service.

Modify TSO/VTAM time-sharing Rebuild a new

LNKLST directory

Display the status of the DLF, or change DLF

parameters or processing mode
MONITOR Continuously display data set status MCS, SMCS or INFO
(MN) extended MCS
Continuously display job status consoles or job
stream 5
Monitor time-sharing users logging on and off the
system
MOUNT (M) Mount volumes MCS, SMCS or I/O
extended MCS
consoles or job
stream 5

4-6 z/OS V1R7.0 MVS System Commands

 Table 4-1. System Command Summary (continued)
Command Function Acceptable Command
(Abbr) From Group
| MSGRT (MR) Establish message routing instructions for certain MCS and SMCS INFO
| options of DISPLAY, MONITOR, STOPMN, Consoles
| CONFIG, and CONTROL commands

| Stop message routing

| Establish message routing for z/OS UNIX System

| Services information
PAGEADD Add local page data sets MCS, SMCS or SYS
(PA) extended MCS
Specify data sets as non-VIO page data sets console 5
PAGEDEL Delete, replace, or drain a local page data set MCS, SMCS or SYS
(PD) extended MCS
(PLPA, common page data sets, and the last local console 5
page data set cannot be deleted, replaced or
drained)
QUIESCE Put system in MANUAL state without affecting step MCS, SMCS or MASTER
timing extended MCS
console 5
REPLY (R) Reply to system information requests MCS, SMCS or INFO
extended MCS
Reply to system requests during recovery consoles or job
processing stream 5

Specify component trace options after issuing

TRACE CT

Specify system parameters

Set the time-of-day clock and specify the

installation performance specification

Specify SMF options

Specify DUMP options

RESET (E) Change performance group of a job currently in MCS, SMCS or SYS
execution extended MCS
consoles or job MASTER
Assign work to a new workload management stream 5
service class. Also, quiesce and resume executing
work.

Force a hung console device offline.

ROUTE (RO) Direct a command to another system, to all MCS, SMCS or INFO
systems, or to a subset of systems in the sysplex extended MCS
consoles or job
stream 5
SEND (SE) Communicate with other operators MCS, SMCS or INFO
extended MCS
Communicate with specific time-sharing users consoles or job
stream 5
Communicate with all time-sharing users

Save messages in the broadcast data set for

issuance at TSO LOGON time or when requested

List messages accumulated in the notices section

of the broadcast data set

Delete a message from the notices section of the

broadcast data set

Chapter 4. MVS System Commands Reference 4-7

 Table 4-1. System Command Summary (continued)
Command Function Acceptable Command
(Abbr) From Group
SET (T) Add modules to, or delete modules from, the LPA MCS, SMCS or SYS
dynamically. Change: extended MCS
v the local time and date consoles or job
stream 5
v the system resources manager (SRM)
parameters
v the MPF parameters
v the dump analysis and elimination (DAE)
parameters
v SLIP processing by changing the active
IEASLPxx parmlib member
v SMS parameters by selecting member
IGDSMSxx in , start SMS if not started at IPL, or
restart SMS if it cannot be restarted
automatically
v available PFK tables
v MIH time intervals by changing the active
IECSIOSxx parmlib member
v excessive spin-loop timeout interval recovery
actions
v RNLs by selecting new GRSRNLxx parmlib
members
v the APPC/MVS address space information
v the APPC/MVS transaction scheduler
information
v the PPT information
v the active console group definitions in the
sysplex
v the MMS parameters
v the command installation exits the system is to
use
v the product enablement policy the system is to
use
v the exclusion list that the Console Id Tracking
facility will use

Restart SMF or change SMF parameters by

changing the active SMFPRMxx parmlib member

Start or stop the common storage and tracking

functions

Start, refresh, or stop MMS. Update:

v the APF list and dynamic exits
v the format or contents of the APF list
v the LNLKST set for LNKLST concatenation
SETCON Activate console environment functions MCS, SMCS or MASTER
extended MCS
console 5
SETETR Enable external time reference (ETR) ports that MCS, SMCS or SYS
have been disabled extended MCS
console 5
SETGRS Migrate a currently active global resource MCS, SMCS or MASTER
serialization ring complex to a global resource extended MCS
serialization star complex console 5

4-8 z/OS V1R7.0 MVS System Commands

 Table 4-1. System Command Summary (continued)
Command Function Acceptable Command
(Abbr) From Group
| SETIOS Respecify, add, or delete MIH time intervals, MCS, SMCS or SYS
| update DCM, enable/disable FICON statistics, and extended MCS
| enable/disable the MIDAW facility, all without console 5
changing the active IECIOSxx parmlib member
SETLOAD Switch dynamically from one parmlib concatenation MCS, SMCS or SYS
to another without having to initiate an IPL extended MCS
console 5
| SETLOGR Take action on system logger log stream MVS, SMCS or MASTER
| resources. extended MVS
| console 5
SETLOGRC Change the logrec recording medium MCS, SMCS or MASTER
extended MCS
console 5
SETOMVS Change the options that OS/390 UNIX System MCS, SMCS or SYS
Services uses. extended MCS
console 5
SETPROG Update APF list MCS, SMCS or SYS
extended MCS
Update dynamic exits console 5

Update the LNKLST set

Dynamically add modules to, or delete modules

from, the LPA.
SETRRS End RRS processing MCS, SMCS or SYS
CANCEL extended MCS
console 5
SETSMF (SS) Change SMF parameters without changing the MCS, SMCS or SYS
active SMFPRMxx parmlib member extended MCS
consoles or job
stream 5
SETSMS Change SMS parameters without changing the MCS, SMCS or SYS
active IGDSMSxx parmlib member extended MCS
console 5
SETSSI Dynamically add, activate or deactivate a MCS, SMCS or MASTER
subsystem. extended MCS
console 5
| SETUNI Control the Unicode environment. MCS, SMCS or SYS
extended MCS
console.5
SETXCF Control the cross-system coupling facility (XCF) MCS, SMCS or MASTER
extended MCS
console 5
SLIP (SL) Set SLIP traps MCS, SMCS or SYS
extended MCS
Modify SLIP traps consoles or job
stream 5
Delete SLIP traps

Chapter 4. MVS System Commands Reference 4-9

 Table 4-1. System Command Summary (continued)
Command Function Acceptable Command
(Abbr) From Group
START (S) Start a job from a console MCS, SMCS or SYS
extended MCS
Start the advanced program-to-program consoles or job
communication (APPC/MVS) address space stream 5

Start the APPC/MVS scheduler (ASCH) address

space

Start the data facility storage management

subsystem (DFSMS/MVS) license compliance
facility

Start the generalized trace facility (GTF)

Start the library lookaside (LLA) address space

Start the object access method (OAM)

Start resource recovery services (RRS)

Start the system object model (SOM)

Start TSO/VTAM time-sharing

Start the virtual lookaside facility (VLF) or the data

lookaside facility (DLF)

Start an external writer

STOP (P) Stop a job in execution MCS, SMCS or SYS
extended MCS
Stop an address space consoles or job
stream 5
Stop an ASCH initiator

Stop an initiator

Stop the data lookaside facility (DLF)

Stop the generalized trace facility (GTF)

Stop the library lookaside (LLA) address space

Stop the object access method (OAM)

Stop the system object model (SOM)

Stop TSO/VTAM time-sharing

Stop the virtual lookaside facility (VLF)

Stop an external writer

STOPMN Stop continual display of data set status MCS, SMCS or INFO
(PM) extended MCS
Stop continual display of job status consoles or job
stream 5
Stop monitoring the activity of time-sharing users.
SWAP (G) Move a volume from one device to another MCS, SMCS or I/O
extended MCS
consoles 5
SWITCH (I) Manually switch recording of SMF data from one MCS, SMCS or SYS
data set to another extended MCS
console 5 MASTER
Switch a consoles attributes to another console

4-10 z/OS V1R7.0 MVS System Commands

Table 4-1. System Command Summary (continued)
Command Function Acceptable Command
(Abbr) From Group
TRACE Start, stop, or modify system trace MCS, SMCS or SYS
extended MCS
Start, stop, or modify master trace console 5 MASTER

Start, stop, or modify component trace MASTER

Display the status of system trace, master trace, or SYS

component trace
UNLOAD (U) Remove a volume from system use MCS, SMCS or I/O
extended MCS
consoles or job
stream 5
VARY (V) Change the master console MCS, SMCS, or MASTER, I/O,
extended MCS or CONS
Control the hardcopy message set and the consoles or job
hardcopy medium. stream (Note 4)

Change the status of a secondary console

Change the consoles alternate console group

Change the SMS status of a storage group or

volume for one or more MVS systems in the SMS
complex

Place I/O devices online or offline

Assign and control consoles

Place I/O paths online or offline

Remove a system from a sysplex

Place I/O paths online after C.U.I.R service

Change a systems participation in a global

resource serialization complex

Change routing codes for a console

Activate a workload management service policy for

a sysplex

Control an application environment

WRITELOG Schedule printing of system log MCS, SMCS or SYS
(W) extended MCS
Change system log output class consoles or job
stream 5
Close the system log and discontinue the log
function

Restart system log after closing

Notes:
1. CONS command group when message routing is specified.
2. For information about VTAM commands, see VTAM Operation.
3. This command is in a different command authority group depending on the parameters specified on
the command. See Table 3-4 on page 3-6 for more information.
4. An extended MCS console can be either an interactive TSO/E session or a program that issues the
MCSOPER macro.

Chapter 4. MVS System Commands Reference 4-11

 Command Syntax Notation
You must follow certain syntactical rules when you code the MVS commands
described in this chapter. Use How to read syntax conventions to help you with
the syntax.

How to read syntax conventions

This section describes how to read syntax conventions. It defines syntax notations
and provides syntax examples that contain these items.
Table 4-2. Syntax conventions
Notation Meaning Example
Book syntax Sample entry
Apostrophes Apostrophes indicate a SEND message,NOW SEND listings ready,NOW
parameter string and must
be entered as shown.
Comma Commas must be entered DISPLAY C,K DISPLAY C,K
as shown.
Ellipsis ... Ellipsis indicates that the VARY (devspec[,devspec]...),ONLINE VARY (282,283,287),ONLINE
preceding item or group
of items can be repeated
one or more times. Do not
enter the ellipsis.
Parentheses Parentheses and special DUMP COMM=(text) DUMP COMM=(PAYROLL)
and special characters must be
characters entered as shown.
| Underline Underline indicates a K M[,AMRF={Y | N}] |,REF K M
| default option. If you
| select an underlined
| alternative, you do not
| have to specify it when
| you enter the command.
Lowercase Lowercase indicates a MOUNT devnum MOUNT A30
parameter variable term. Substitute
your own value for the or
item. mount a30
Uppercase Uppercase indicates the DISPLAY SMF DISPLAY SMF
parameter item must be entered
using the characters or
shown. Enter the item in display smf
either upper or lowercase.
Single Single brackets represent DISPLAY DMN[=domainum] DISPLAY DMN=5
brackets single or group-related
items that are optional.
Enter one or none of
these items.
Stacked Stacked brackets [TERMINAL] NOTERMINAL
brackets represent group-related [NOTERMINAL]
items that are optional.
Enter one or none of
these items.

4-12 z/OS V1R7.0 MVS System Commands

Table 4-2. Syntax conventions (continued)
Notation Meaning Example
Book syntax Sample entry
Single braces Single braces represent {COMCHECK | COMK} COMK
group-related items that
are alternatives. You must
enter one of the items.
You cannot enter more
than one.
Stacked Stacked braces represent MN {DSNAME} MN SPACE
braces group related items that {SPACE }
are alternatives. You must {STATUS}
enter one of the items.
You cannot enter more
than one.
Or-bar (|) An or-bar indicates a ACTIVATE|RECOVER=SOURCE RECOVER=SOURCE
mutually exclusive choice.
When used with brackets,
enter one or none of the
items. When used with
braces, you must enter
one of the items.
Stacked items Stacked items with CD RESET [ ,SDUMP ] CD RESET,SYSUDUMP
with or-bars (|) or-bars indicates a |,SYSABEND
and brackets mutually-exclusive choice. |,SYSUDUMP
Enter one or none of |,SYSMDUMP
these items. |,ALL

System Command Formats

Two system command formats are defined.

Typical Format
Most system commands can use the format shown in Figure 4-1.

COMMAND [operand [,operand] ] [comments]

optional 1 or no embedded 1 or embedded

command more blanks more blanks
prefixes blanks blanks allowed
or blanks

Figure 4-1. One System Command Format

The following restrictions apply to commands using this format:

1. Enter only one command per line. Use a maximum of 126 characters from a
console, or 80 characters through a card reader.
2. To include a comment on a command when you have specified no operands,
insert the following after the command: a blank, then a comma, then another
blank, and then the comment. The comment may contain embedded blanks.

Chapter 4. MVS System Commands Reference 4-13

A Second Format
Figure 4-2 shows a format required by some system commands including DISPLAY
PROD, DISPLAY PROG, DISPLAY RTLS, and SETPROG.

COMMAND [operand [comments] ] [comments]

optional 1 or Optional comments, optional embedded

command more and optional commas blank blanks
prefixes blanks between operands allowed
or blanks
Figure 4-2. A Second System Command Format

This second format provides the opportunity to include a comment after the
command and each operand within the command. These restrictions apply:
1. You may, but do not have to use a comma between operands. Examples:
D PROG APF
D PROG,APF
2. This format requires that each comment be contained between a slash-asterisk
and asterisk-slash pair. Comments may contain embedded blanks. Examples:
D PROG APF /* comments */
D PROG /*comment */ APF /* comment */

4-14 z/OS V1R7.0 MVS System Commands

 ACTIVATE Command

ACTIVATE Command
Use the ACTIVATE command to activate or test a new I/O configuration definition
dynamically.

Restrictions
For a list of restrictions on the ACTIVATE command, see z/OS HCD Planning.

Attention: An ACTIVATE command may still be active as a task in IOSAS after

the command task has been abended with a CMDS ABEND.

Syntax
The complete syntax for the ACTIVATE command is:

ACTIVATE {[,IODF=xx][,EDT=xx][,PROC=procname][,CFID=id] }
[,RECOVER=SOURCE|TARGET][,ACTIOCDS=xx]

{[ ,SOFT[=VALIDATE|=NOVALIDATE] ] }
|,TEST
|,FORCE
|,FORCE={DEVICE }
{CANDIDATE }
{(DEVICE,CANDIDATE)}
{(CANDIDATE,DEVICE)}

Note: Do not specify a comma before the first parameter following ACTIVATE.

Parameters
IODF=xx
Specifies the two-character suffix of the target IODF data set name (IODFxx)
that contains the configuration definition the system is to activate. When this
keyword is omitted, the system defaults to the active IODF data set name.
EDT=xx
Specifies the eligible devices table (EDT) that the system is to construct from
the target IODF. If you omit this keyword, the system uses the active EDT
identifier.
PROC=procname
Indicates the eight-byte name of the processor definition in the target IODF. If
you omit this keyword, the system will use the active processor name.
CFID=id
Specifies the eight-byte configuration identifier that indicates the operating
system definition in the target IODF. If you omit this keyword, the system
defaults the configuration identifier as follows:
v When the target IODF has only one configuration identifier, it becomes the
default, otherwise, the current configuration identifier is the default.
RECOVER=
Allows the installation to continue a dynamic change that did not complete due
to a hardware, software, or PR/SM failure. You can specify:
v SOURCE to retry the original I/O configuration
v TARGET to retry the new I/O configuration
v default:
Retry TARGET IODF if ACTIVATE failed during advance

Chapter 4. MVS System Commands Reference 4-15

ACTIVATE Command

Retry SOURCE IODF if ACTIVATE failed while backing out.

ACTIOCDS=xx
Specifies the two-character IOCDS name that the system is to activate. Upon
successful completion of the ACTIVATE command, the default IOCDS for the
next power-on-reset will be xx. It does not make the I/O configuration definition
stored in the IOCDS the active one.
For the IOCDS activate process to be successful, the processor token in the
target IOCDS must match the current processor token in the Hardware System
Area (HSA). This means that the IOCDS that is being activated has an I/O
configuration definition that matches the I/O configuration currently active in the
channel subsystem.
When you specify ACTIOCDS, you cannot specify TEST.
SOFT
Specifies a dynamic change to the software I/O configuration, which updates
the I/O configuration only to the operating system. To change a software and
hardware I/O configuration dynamically, omit the SOFT keyword.
When you specify SOFT, you cannot specify FORCE.
When you specify SOFT without any parameters, it is the same as specifying
SOFT=VALIDATE.
=VALIDATE or =NOVALIDATE
Allows you to specify whether or not the system is to validate that any specified
hardware elements to be deleted are offline and available, and that there is
sufficient HSA space available to accommodate the hardware changes.
When a dynamic change is made to the I/O configuration for a processor
complex running in LPAR mode, a change to the software I/O configuration is
performed for the first N-1 logical partitions, followed by a hardware and
software change for the Nth logical partition. By specifying the SOFT keyword
(or SOFT=VALIDATE) when changing the I/O configuration on the N-1 logical
partitions, you can determine early on whether there will be sufficient HSA
space available for the subsequent software and hardware I/O configuration
changes on the Nth logical partition.
TEST
Specifies test mode to check, but not to change, the configuration. The system
checks include whether:
v The dynamic change will fit into the current HSA
v The target IODF exists
v The target IODF contains the target EDT
v The target IOCDS is a valid data set
v The device support code supports devices being dynamically added or
deleted
v The devices to be deleted are offline
v The paths to be deleted are offline
If you are performing a full dynamic activate, the system provides a list showing
which channels and devices will be added, deleted, or changed during
activation.
Warning If you run the ACTIVATE command with the TEST option and
the system detects no errors, there is still no guarantee that
ACTIVATE will work without TEST.

4-16 z/OS V1R7.0 MVS System Commands

 ACTIVATE Command

When you specify TEST, you cannot specify ACTIOCDS or FORCE.

FORCE
Specify that the system makes it possible to delete hardware resources that
might offset other partitions.
You must specify FORCE if your processor complex is running in LPAR mode,
and you want to activate a target IODF to delete one or more I/O components.
You can also specify FORCE to activate a target IODF to delete a logical
partition from a device candidate list. These deletions may be explicit or implicit
due to changes in the definitions for some I/O components. When you specify
FORCE, you cannot specify SOFT or TEST.
If your processor complex has Enterprise Systems Connection (ESCON)
Multiple Image Facility (EMIF) capability, you can specify FORCE to get the
results described in Table 4-3.
For information about ESCON Multiple Image Facility (EMIF), see z/OS HCD
Planning. For information about access lists and candidate lists, see z/OS HCD
Users Guide.
Table 4-3. Specifying FORCE with EMIF
To do the following: Specify FORCE as follows:
Delete no I/O components, and do either of the Do not specify FORCE.
following:
v Delete no logical partitions from the access or
candidate list of a channel path.
v Delete one or more logical partitions from the
access or candidate list of a channel path
offline to all of those logical partitions. IBM
recommends that you take the channel path
offline before issuing the command.
Delete no I/O components, and delete one or FORCE=CANDIDATE
more logical partitions from the access or
candidate list of a channel path online to any of
those logical partitions. IBM does not recommend
this action.
Delete one or more I/O components, and do FORCE or FORCE=DEVICE
either of the following:
v Delete no logical partitions from the access or
candidate list of a channel path.
v Delete one or more logical partitions from the
access or candidate list of a channel path
offline to all of those logical partitions. IBM
recommends that you take the channel path
offline before issuing the command.
Delete one or more I/O components, and delete FORCE=(DEVICE,CANDIDATE) or
one or more logical partitions from the access or FORCE=(CANDIDATE,DEVICE)
candidate list of a channel path online to any of
those logical partitions. IBM does not recommend
this action.
Delete one or more logical partitions from the FORCE or FORCE=DEVICE
device candidate list and delete no other I/O
components.

Chapter 4. MVS System Commands Reference 4-17

ACTIVATE Command

Note: Before activating the new configuration, you may have to configure offline
affected channel paths or vary offline affected devices. See z/OS HCD
Planning for details about avoiding disruptions to I/O operations during
dynamic changes.

Example 1

To ACTIVATE the A0 IOCDS, enter:

ACTIVATE ACTIOCDS=A0

Example 2

To ACTIVATE the configuration definition COMPUT22, contained in the IODF with

suffix 03, enter:
ACTIVATE IODF=03,CFID=COMPUT22

Example 3

To perform a test ACTIVATE to processor definition PROC1001 contained in the

currently active IODF, enter:
ACTIVATE PROC=PROC1001,TEST

Example 4

To ACTIVATE an IODF with suffix 04, which deletes one or more I/O components
from the I/O configuration, enter:
ACTIVATE IODF=04,FORCE
or
ACTIVATE IODF=04,FORCE=DEVICE

4-18 z/OS V1R7.0 MVS System Commands

 CANCEL Command

CANCEL Command
Use the CANCEL command to end an active job, started task, or time-sharing user
immediately. The table that follows summarizes the tasks that the CANCEL
command can perform. Following the table are usage notes, the complete
command syntax, definition of parameters, and examples of use.

If the program that supports the job or started task was designed to recognize the
STOP command, use the STOP command before using the CANCEL command. If
the CANCEL command fails several times, consider using the FORCE command.
Table 4-4. CANCEL Command Tasks
Task - Immediately Terminate: Syntax
v A job in execution CANCEL jobname
v A running Advanced Program-to-Program Communication/MVS
(APPC/MVS) transaction program
v A started task
v A time-sharing user CANCEL U=userid
v A started task CANCEL identifier
v A MOUNT command
v An external writer allocation
v The output processing for a job
v A z/OS UNIX process

Notes:
1. If your system was part of a global resource serialization ring (GRS=START,
GRS=JOIN or GRS=TRYJOIN was specified at IPL) and the system is either
inactive or quiesced (by entering the VARY GRS(system name),QUIESCE
command), the CANCEL command might not work for jobs that own any global
resources. Use DISPLAY GRS to determine GRS status.
2. If a job is running, you can end it using either the CANCEL system command or
the appropriate subsystem command. However, if the job is not running, you
must CANCEL the job using the subsystem command.
3. The CANCEL command issues an ABEND with either code 122 or 222 to
abnormally end a job step or time-sharing user. The ABEND is asynchronous
and might result in additional errors, depending on which programs were active
at the time of the request. You might need to issue additional CANCEL
commands to completely end the job.
4. Entering the CANCEL command during device allocation terminates the external
writer as well as the unit of work. Entering this command when the external
writer is processing output for a job terminates the output processing but leaves
the external writer to process other data sets.
5. When you cancel a MOUNT command for a tape unit, the MOUNT command
can end before the volume has been mounted. If the MOUNT command has
ended and the mount request is not satisfied, issue the UNLOAD command to
free the tape unit.

Chapter 4. MVS System Commands Reference 4-19

 CANCEL Command

Syntax
The complete syntax for the CANCEL command is:

C {jobname }[,DUMP][,A=asid][,ARMRESTART]
{U=userid }
{[jobname.]identifier}

Parameters
jobname
The name of the batch job, started task, or APPC/MVS transaction program to
be canceled.
| The job name for a given started task can be assigned based on a variety of
| inputs. These inputs are examined in the following order, so that if item #1 is
| not specified, item #2 is used. If neither #1 nor #2 is specified, then #3 is used,
| and so on.
| 1. The jobname specified in the JOBNAME= parameter of the START
| command
| or
| The identifier specified on the START command.
| 2. The jobname specified on the JOB JCL statement within the member.
| 3. The device number specified on the START command, or the device
| number associated with the device type specified on the START command
| or
| The device number associated with the device type specified on the START
| command.
| 4. The device number associated with the IEFRDER DD statement within the
| member.
| 5. The member name.
U=userid
The user ID of the time-sharing user you want to cancel.
If the user is just logging on and does not yet have a unique name, you must
find out the address space identifier for the user (see the explanation under
A=asid) and use the following version of the command:
CANCEL U=*LOGON*,A=asid
[jobname.]identifier
The identifier for the unit of work that you want to cancel, optionally preceded
by the job name.
The following types of identifiers can be used:
v The identifier that was specified on the START command.
v [/]devnum, the device number specified when the START or MOUNT
command was entered. The device number is 3 or 4 hexadecimal digits,
optionally preceded by a slash (/). You can precede the device number with a
slash to prevent ambiguity between the device number and a device type or
identifier.
v devicetype, the type of device specified when the START or MOUNT
command was issued.

4-20 z/OS V1R7.0 MVS System Commands

 CANCEL Command

If no identifier was specified on the START command, the system assigns

temporary identifier STARTING to the unit of work, until the system can assign
an identifier according to the following order of precedence:
1. If an identifier was not specified on the START command, the identifier is
the device type (for example, 3410) or device number (for example, X0000)
specified on the START or MOUNT command.
2. If an identifier, a device type, or a device number was not specified on the
START or MOUNT command, the identifier is the device type specified on
an IEFRDER DD statement (invoking a cataloged procedure) in the JCL.
3. If none of the above was specified, the identifier defaults to the job name.

When you specify jobname.identifier, then identifier can be represented by any

of the following:
v An asterisk
v One or more characters from the beginning of the identifier, followed by an
asterisk
v The entire identifier

When you specify an asterisk, the system responds with message IEE422I.

Attention: When you use the asterisk format, the command affects all started
tasks that begin with the specified characters. Device numbers are assumed to
be four-digit numbers; for example, /13* would match on 1301, 1302, and so
on, but would not match on 13C, because 13C is interpreted as 013C.

Specifying both the job name and the entire identifier causes the command to
take effect if one and only one work unit with that combination of job name
and identifier is running. For the case where more than one work units with the
same combination of job name and identifier are running, see A=asid below.
DUMP
A dump is to be taken. The type of dump (SYSABEND, SYSUDUMP, or
SYSMDUMP) depends on the JCL for the job. A dump request is only valid
when made while the job is running. Dumps are not taken during job allocation
or deallocation.
Note: You can use DUMP with any of the other CANCEL parameters.
A=asid
The hexadecimal address space identifier of the work unit you want to cancel.
If more than one work unit is running with the same job name, identifier,
combination of job name and identifier, or user ID that you specified on the
CANCEL command, the system rejects the command because it does not know
which work unit to cancel. To avoid this, you must add the parameter A=asid to
your original CANCEL command in order to specify the address space identifier
of the work unit.

Note: If the asterisk format is used, you will not be prompted for A=asid.
Rather, all work units meeting the specified criteria will be canceled.
You can use the CANCEL operator command to cancel z/OS UNIX address
spaces. Each address space is equivalent to a z/OS UNIX process.
To find out the address space identifier for a unit of work, you can use the
DISPLAY command as follows:

Chapter 4. MVS System Commands Reference 4-21

CANCEL Command

DISPLAY JOBS,ALL
Lists the address space identifiers for all batch jobs and started tasks.
DISPLAY ASCH,ALL
Lists the address space identifiers for all APPC/MVS transaction programs.
DISPLAY TS,ALL
Lists the address space identifiers for all logged-on time-sharing users.
DISPLAY OMVS,ASID=ALL or DISPLAY OMVS,A=ALL
Lists the address space identifiers for all z/OS UNIX processes.

Note: A=asid can be used with any of the other CANCEL parameters except if
you specify jobname.identifier with an asterisk (for example, CANCEL
aor2.tl*).
ARMRESTART
Indicates that the batch job or started task should be automatically restarted
after the cancel completes, if it is registered as an element of the automatic
restart manager. If the job or task is not registered or if you do not specify this
parameter, MVS will not automatically restart the job or task.

Example 1

Cancel the job named EXAMPLE and take a dump.

c example,dump

Example 2

Cancel the job named EXAMPLE. Whether you get a dump or not depends on the
system routine in control when you enter the command.
c example

Example 3

Of all jobs named EXAMPLE in the system, cancel only the one whose address
space identifier is 7F.
c example,a=7F

Example 4

Log off the system the user just logging on who has an address space identifier of
3D but does not yet have a unique user identifier.
c u=*logon*,a=3d

Example 5

Log user A237 off the system.

c u=a237

Example 6

Log user A237 off the system and take a dump.

c u=a237,dump

Example 7

4-22 z/OS V1R7.0 MVS System Commands

 CANCEL Command

Cancel the MOUNT command that requests a volume to be mounted on device

number 232, enter:
c 232

Example 8

Cancel the MOUNT command that requests a volume to be mounted on a 3330

device type.
c 3330

Example 9

End the device allocation for a writer with device number 00E.
c 00e

Example 10

End the output processing being done for device number 00E and cause another
output data set to be processed.
c 00e

Example 11

End the output processing being done for device number 3480 and cause another
output data set to be processed.
c /3480

Example 12

Of all the transaction programs running with the job name MAIL, end only the one
whose address space identifier is 2C, which is the APPC/MVS scheduler (ASCH)
initiator ASID.
C mail,a=2c

Example 13

End the device allocation for a writer on device number F00E.

c /f00e

Example 14

There are several tasks running with jobname AOR2. End all of those tasks.
c aor2.*

Example 15

There are several tasks running with jobname AOR2. Some of those tasks have
identifiers beginning T1. End only those specific tasks.
c aor2.t1*

Example 16

The following example shows an operator session that cancels a process that is
running the shell command sleep 6000 for the TSO/E user CHAD.

Chapter 4. MVS System Commands Reference 4-23

CANCEL Command

DISPLAY OMVS,U=CHAD

BPXO001I 17.12.23 DISPLAY OMVS 700 C

OMVS ACTIVE BPXPRMHF
USER JOBNAME ASID PID PPID STATE START CT_SECS
CHAD CHAD 001D 262147 1 RI 17.00.10 1.203
CHAD CHAD 001B 131076 5 SI 17.00.10 .111
LATCHWAITPID= 0 CMD=sleep 6000
CHAD CHAD 0041 5 262147 IW 17.00.10 .596
LATCHWAITPID= 0 CMD=-sh
CHAD CHAD3 001B 131076 5 SI 17.00.10 .111
LATCHWAITPID= 0 CMD=sleep 6000

If you want to cancel only the process that is running the shell command sleep
6000, enter:
CANCEL CHAD3

If you want to cancel the TSO/E user CHAD altogether, enter:

CANCEL U=CHAD

4-24 z/OS V1R7.0 MVS System Commands

 CHNGDUMP Command

CHNGDUMP Command
Use the CHNGDUMP command to change the mode and system dump options list
for any dump type, or to request structures to be dumped when one or more
systems connected to a coupling facility fail. The dump types are SDUMP,
SYSABEND, SYSUDUMP, and SYSMDUMP. If you issue multiple CHNGDUMP
commands, the changes to the system dump options are cumulative. Table 4-5
summarizes the information that the CHNGDUMP command provides. Use it to
access the pages on which you can find details about a particular use of the
CHNGDUMP command.
Table 4-5. Summary of the CHNGDUMP Command
Command Topic
CHNGDUMP DEL Removing Options from or Resetting the System Dump Options
Lists on page 4-26
CHNGDUMP RESET Resetting Dump Mode to ADD and the Dump Options to Initial
Values on page 4-32
CHNGDUMP SET Setting the Dump Modes and Options on page 4-34

Dump Options and Modes

The system checks the dump mode and dump options each time the system or a
user requests a dump. The dump mode determines whether the system accepts
either a dump request or the options a dump request specifies. The starting dump
mode for all four dump types is ADD.

The dump options, whether taken from a system dump options list or from a dump
request, specify, for each dump type, the data areas to dump. MVS sets up system
dump options lists each time you initialize the system. These lists specify the dump
mode and dump options in effect for each dump type. The system finds the starting
dump options lists for the SYSABEND, SYSUDUMP, and SYSMDUMP dump types
in parmlib members IEAABD00, IEADMP00, and IEADMR00 respectively. Because
the SDUMP dump type has no corresponding parmlib member, it starts with an
empty dump options list.

Dump Modes
In addition to ADD, other possible dump modes are OVER and NODUMP. The
meaning of each mode is:
v ADD When a dump is requested for a dump type that is in ADD mode, the
system merges the options specified on the dump request with the options
specified in the system dump options list for that dump type. The merged options
determine the data areas to dump. If an option specified on the dump request
conflicts with an option in the options list, the system uses the option in the
options list.
v OVER When a dump is requested for a dump type that is in OVER (override)
mode, the system ignores the options specified on the dump request and uses
only the options specified in the system dump options list for that dump type
combined with the override options to determine the data areas to dump.
v NODUMP When a dump is requested for a dump type that is in NODUMP
mode, the system ignores the request and does not take a dump.

Chapter 4. MVS System Commands Reference 4-25

CHNGDUMP Command

Changing the Dump Mode and Options

You can change the dump mode or options for a dump type. Before making a
change, however, issue DISPLAY DUMP,OPTIONS to see the current mode and
options.

Changing the mode of a dump type can also affect its system dump options list as
follows:
v If you change the mode for a dump type from OVER to ADD, the system adds
the dump types parmlib options to the dump types system dump options list.
The dump types system dump options list then contains both the dump types
parmlib options and any options set by previous CHNGDUMP commands.
v If you change the mode for a dump type from ADD to OVER, the system
removes the dump types parmlib options from the dump types system dump
options list. The dump types system dump options list then contains only the
options set by previous CHNGDUMP commands.
v If you change the mode for a dump type to NODUMP, the system empties the
dump types system dump options list.

If you make an error entering a CHNGDUMP command, the system rejects the
entire command and issues an error message.

Scope in a Sysplex
The CHNGDUMP command has sysplex scope only when all systems are
connected to the same coupling facilities, and you specify
,SDUMP,SYSFAIL,STRLIST=. See Using Commands That Have Sysplex Scope
on page 1-11 for an explanation of sysplex scope.

Syntax
The syntax for each variation of the CHNGDUMP command (CD DEL, CD RESET,
and CD SET) is shown immediately preceding its respective parameter list.

CHNGDUMP or CD

Removing Options from or Resetting the System Dump Options Lists

Use the CHNGDUMP DEL command to remove specified options from a dump
options list or to reset all dump options lists to values specified at system
initialization.

CD DEL[,SDUMP[=(option[,option]...)] ]
[,Q={YES|NO}]
[,TYPE={XMEM|XMEME}]
[,ALL]
[,SYSFAIL,STRLIST={ALL|(STRNAME=strname[,STRNAME=strname]...)}]
[{,SYSABEND}[,SDATA=(option[,option]...) ] ]

[{,SYSUDUMP} |,PDATA=(option[,option]...) ]
|,ALL

[,SYSMDUMP[=(option[,option]...)] ]
|,ALL

[,ALL ]

4-26 z/OS V1R7.0 MVS System Commands

 CHNGDUMP Command

Parameters
DEL
Set the dump mode for each dump type to ADD and reset all system dump
options lists to the values established during system initialization. (The system
gets the initial dump options for SYSABEND, SYSUDUMP, and SYSMDUMP
from parmlib members IEAABD00, IEADMP00, and IEADMR00 respectively.
The system empties the SDUMP dump options list.)
SDUMP
Set the dump mode for the SDUMP dump type to ADD, and empty the
SDUMP system dump options list.
SDUMP,SYSFAIL,STRLIST={ALL or STRNAME=strname,...}
To delete STRNAME specifications from the dump options list. You can
delete any or all structure name specifications from the dump options list.
For a complete description of the keyword specifications see the
SET,SDUMP parameter on page 4-37.
SDUMP=(options)
Remove the specified options from the SDUMP system dump options list. If
the SDUMP dump mode is OVER, and previous CHNGDUMP commands
have removed all dump options from the SDUMP dump options list, this
command has no effect and leaves the SDUMP dump options list empty.
See Options for SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP on
page 4-29 for SDUMP options you can specify.
SDUMP,Q=YES or NO
Specifies whether or not SDUMP is to quiesce the systemset it to
nondispatchable (Q=YES) or leave the system dispatchable (Q=NO)while
dumping the contents of the SQA or CSA. For further information, see
Setting the Dump Modes and Options on page 4-34.
SDUMP,TYPE=XMEM
Turn off cross memory in the SDUMP system dump options list.
SDUMP,TYPE=XMEME
Turn off cross memory at the time of the error in the SDUMP system
dump options list.
SDUMP,ALL
Same as DEL,SDUMP.
SYSABEND
Set the dump mode for the SYSABEND dump type to ADD, and reset the
SYSABEND system dump options list to the values established during
system initialization. (The system gets the initial dump options for
SYSABEND from the IEAABD00 parmlib member.)
SYSABEND,SDATA=(options)
Remove any of the specified SDATA options that previous CHNGDUMP
commands put in the SYSABEND system dump options list. Parmlib
options do not change. If the SYSABEND dump mode is OVER and
previous CHNGDUMP commands have removed all SDATA and PDATA
dump options from the SYSABEND dump options list, reset the list to the
parmlib options. See Options for SDUMP, SYSABEND, SYSUDUMP, and
SYSMDUMP on page 4-29 for SYSABEND options you can specify.
SYSABEND,PDATA=(options)
Remove any of the specified PDATA options that previous CHNGDUMP
commands put in the SYSABEND system dump options list. Parmlib

Chapter 4. MVS System Commands Reference 4-27

CHNGDUMP Command

options do not change. If the SYSABEND dump mode is OVER and

previous CHNGDUMP commands have removed all SDATA and PDATA
dump options from the SYSABEND dump options list, reset the list to the
parmlib options. See Options for SDUMP, SYSABEND, SYSUDUMP, and
SYSMDUMP on page 4-29 for SYSABEND options you can specify.
SYSABEND,ALL
Same as DEL,SYSABEND.
SYSUDUMP
Set the dump mode for the SYSUDUMP dump type to ADD, and reset the
SYSUDUMP system dump options list to the values established during
system initialization. (The system gets the initial dump options for
SYSUDUMP from the IEADMP00 parmlib member.)
SYSUDUMP,SDATA=(options)
Remove any of the specified SDATA options that previous CHNGDUMP
commands put in the SYSUDUMP system dump options list. Parmlib
options do not change. If the SYSUDUMP dump mode is OVER and
previous CHNGDUMP commands have removed all SDATA and PDATA
dump options from the SYSUDUMP dump options list, reset the list to the
parmlib options. See Options for SDUMP, SYSABEND, SYSUDUMP, and
SYSMDUMP on page 4-29 for SYSUDUMP options you can specify.
SYSUDUMP,PDATA=(options)
Remove any of the specified PDATA options that previous CHNGDUMP
commands put in the SYSUDUMP system dump options list. Parmlib
options do not change. If the SYSUDUMP dump mode is OVER and
previous CHNGDUMP commands have removed all SDATA and PDATA
dump options from the SYSUDUMP dump options list, reset the list to the
parmlib options. See Options for SDUMP, SYSABEND, SYSUDUMP, and
SYSMDUMP on page 4-29 for SYSUDUMP options you can specify.
SYSUDUMP,ALL
Same as DEL,SYSUDUMP.
SYSMDUMP
Set the dump mode for the SYSMDUMP dump type to ADD, and reset the
SYSMDUMP system dump options list to the values established during
system initialization. (The system gets the initial dump options for
SYSMDUMP from the IEADMR00 parmlib member.)
SYSMDUMP=(options)
Remove any of the specified options that previous CHNGDUMP commands
put in the SYSMDUMP system dump options list. Parmlib options do not
change. If the SYSMDUMP dump mode is OVER and previous
CHNGDUMP commands have removed all dump options from the
SYSMDUMP dump options list, reset the list to the parmlib options. See
Options for SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP on page
4-29 for SYSMDUMP options you can specify.
SYSMDUMP,ALL
Same as DEL,SYSMDUMP.
ALL
Same as DEL.

4-28 z/OS V1R7.0 MVS System Commands

 CHNGDUMP Command

Options for SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP

The options that you can specify on the CHNGDUMP command follow. The default
options for the IEAABD00, IEADMP00, and IEADMR00 parmlib members are CB,
DM, ENQ, ERR, IO, JPA, LPA, LSQA, NUC, PSW, REGS, RGN, SA, SPLS, SQA,
SUM, SWA, and TRT:

SDUMP options:
ALLNUC All of the DAT-on nucleus, including page-protected areas, and all
of the DAT-off nucleus.
ALLPSA or NOALLPSA or NOALL
Prefix storage area for all processors. NOALLPSA or NOALL
specifies that these areas are not to be dumped.
COUPLE XCF related information in the sysplex.
CSA Common storage area.
GRSQ Global resource serialization (ENQ/DEQ/RESERVE) queues.
LPA Link pack area.
LSQA Local system queue area.
NUC Non-page-protected areas of the DAT-on nucleus.
PSA Prefix storage area of the dumping processor.
RGN Entire private area.
SERVERS Requests that the registered IEASDUMP.SERVER dynamic exits
receive control.
SQA or NOSQA
System queue area. NOSQA specifies that this data not be
dumped.
SUMDUMP or SUM
Requests the summary dump function. For a description of NOSUM
the summary dump function, see z/OS MVS Programming:
Authorized Assembler Services Reference LLA-SDU.
NOSUM or NOSUMDUMP
Requests that the function not be performed.
SWA Scheduler work area.
TRT GTF, system trace, and master trace data.
WLM Workload management related information in the sysplex.
XESDATA XES-Related information in the sysplex.

SDATA options for SYSABEND dump type:

ALLSDATA Sets all of the other SDATA options except NOSYM and ALLVNUC.
ALLVNUC All of the DAT-on nucleus, including page-protected areas.
CB Format of task-related control blocks.
DM Data management control blocks.
ENQ Global resource serialization control blocks for the current task.
ERR RTM control blocks.

Chapter 4. MVS System Commands Reference 4-29

CHNGDUMP Command

IO I/O supervisor control blocks.

LSQA Local system queue area.
NOSYM Symptom dump is not to be produced.
NUC Non-page-protected areas of the DAT-on nucleus.
PCDATA Program call data for the current task.
SQA System queue area.
SUM Summary dump data.
SWA Scheduler work area.
TRT GTF and system trace data. (For an authorized user, system trace
data is for all address spaces in the system. For an unauthorized
user, system trace data is for the users address space only. The
GTF data is for the users address space only.)

SDATA options for SYSUDUMP dump type:

ALLSDATA Sets all of the other SDATA options except NOSYM and ALLVNUC.
ALLVNUC All of the DAT-on nucleus, including page-protected areas.
CB Format of task-related control blocks.
DM Data management control blocks.
ENQ Global resource serialization control blocks for the current task.
ERR RTM control blocks.
IO I/O supervisor control blocks.
LSQA Local system queue area.
NOSYM Symptom dump is not to be produced.
NUC Non-page-protected areas of the DAT-on nucleus.
PCDATA Program call data for the current task.
SQA System queue area.
SUM Summary dump data.
SWA Scheduler work area.
TRT GTF and system trace data. (For an authorized user, system trace
data is for all address spaces in the system. For an unauthorized
user, system trace data is for the users address space only. The
GTF data is for the users address space only.)

PDATA options for SYSABEND dump type:

ALLPDATA Sets all of the PDATA options.
ALLPA Sets both the LPA and JPA options.
JPA job pack area.
LPA Link pack area for this job.
PSW Program status word.
REGS General registers.
SA Save area trace (long form).

4-30 z/OS V1R7.0 MVS System Commands

 CHNGDUMP Command

SAH Save area trace (short form).

SPLS Allocated storage subpools.
SUBTASKS Program data for the main task and all subtasks of this job.
(SUBTASKS is always included for abends with a system
completion code of X'22'.)

PDATA options for SYSUDUMP dump type:

ALLPDATA Sets all of the PDATA options.
ALLPA Sets both the LPA and JPA options.
JPA Job pack area.
LPA Link pack area for this job.
PSW Program status word.
REGS General registers.
SA Save area trace (long form).
SAH Save area trace (short form).
SPLS Allocated storage subpools.
SUBTASKS Program data for the main task and all subtasks of this job.
(SUBTASKS is always included for abends with a system
completion code of X'22'.)

SYSMDUMP options:
ALL Sets all of the other SYSMDUMP options except NOSYM and
ALLNUC.
ALLNUC All of DAT-on nucleus, including page-protected areas, and all of
the DAT-off nucleus.
CSA The portions of the common storage area that are not
fetch-protected.
GRSQ Global resource serialization (ENQ/DEQ/RESERVE) queues.
LPA Link pack area for this job.
LSQA Local system queue area.
NOSYM Symptom dump is not to be produced.
NUC Non-page-protected areas of the DAT-on nucleus.
RGN Entire private area.
SQA System queue area.
SUM Requests the summary dump function. For a description of the
summary dump function, see z/OS MVS Programming: Authorized
Assembler Services Reference LLA-SDU.
SWA Scheduler work area.
TRT System trace data. (For an authorized user, system trace data is for
all address spaces in the system. For an unauthorized user, system
trace data is for the users address space only.)

Chapter 4. MVS System Commands Reference 4-31

CHNGDUMP Command

Resetting Dump Mode to ADD and the Dump Options to Initial Values
Use the CHNGDUMP RESET command to reset the dump mode to ADD and the
dump options list to values established during system initialization.

CD RESET[,SDUMP ]
|,SYSABEND
|,SYSUDUMP
|,SYSMDUMP
|,ALL

RESET
Set the dump mode for each dump type to ADD, and reset the system dump
options list for each type to the values established during system initialization.
(The system gets the initial dump options for SYSABEND, SYSUDUMP, and
SYSMDUMP from parmlib members IEAABD00, IEADMP00, and IEADMR00
respectively. The system empties the SDUMP dump options list.)
RESET,SDUMP or SYSABEND or SYSUDUMP or SYSMDUMP
Set the dump mode for the specified dump type to ADD, and reset the dump
types system dump options list to the values established during system
initialization. (The system gets the initial dump options for SYSABEND,
SYSUDUMP, and SYSMDUMP from parmlib members IEAABD00, IEADMP00,
and IEADMR00 respectively. The system empties the SDUMP dump options
list.)
RESET,ALL
Same as RESET.

Example: How CHNGDUMP Commands Affect Dump Modes and

Options
Table 4-6 (using SYSABEND) shows how dump modes and system dump options
are set during system initialization and then changed by CHNGDUMP commands or
options specified on ABEND macro dump requests. The figure assumes that
parmlib member IEAABD00 specifies dump options CB, DM, ENQ, ERR, IO, LSQA,
SUM, and TRT. The figure lists system and operator actions and explains each
action the system takes.
v The FUNCTION column lists the IPL process, CHNGDUMP commands, and
dump requests (from the ABEND macro instruction) as they occur.
v The OPTIONS column identifies the SYSABEND dump options in effect at each
point in the example.
v The MODE column identifies the dump mode in effect at each point in the
example.
Table 4-6. Example of How CHNGDUMP Commands Affect Dump Modes and Options
FUNCTION (* indicates operator commands/actions) OPTIONS MODE
CB IO ADD
* IPL DM LSQA
During IPL, parmlib options are set on, and mode is set ENQ SUM
to ADD. ERR TRT

4-32 z/OS V1R7.0 MVS System Commands

 CHNGDUMP Command

Table 4-6. Example of How CHNGDUMP Commands Affect Dump Modes and Options (continued)
FUNCTION (* indicates operator commands/actions) OPTIONS MODE
CB LSQA ADD
ABEND SDATA=(NUC,SWA) DM NUC
Because mode is ADD, options specified on dump ENQ SUM
request are added to options set on in options list to ERR SWA
IO TRT
determine areas to dump.
CB LSQA ADD
* CD SET,SYSABEND,SDATA=PCDATA DM PCDATA
An additional option is set on in options list. ENQ SUM
ERR TRT
IO
CB LSQA ADD
ABEND DM PCDATA
Because dump request specified no additional options, ENQ SUM
only options set on in options list determine areas to ERR TRT
IO
dump.
CB NUC ADD
ABEND SDATA=(NUC,SWA) DM PCDATA
Because mode is ADD, options specified on dump ENQ SUM
request are added to options set on in options list to ERR SWA
IO TRT
determine areas to dump.
LSQA
CB OVER
* CD SET,SYSABEND,OVER,SDATA=(CB,IO) IO
Mode is changed to OVER and parmlib options are PCDATA
deleted from options lists. Only options set by previous
CD commands remain on in options list; CD commands
are cumulative. Options in options list are combined with
override options to determine areas to dump.
CB OVER
ABEND SDATA=(SWA,TRT) IO
Because mode is OVER, options specified on dump PCDATA
request are ignored. Options set on in options list
determine areas to dump.
CB LSQA OVER
* CD SET,SYSABEND,SDATA=(ENQ, LSQA),OVER ENQ PCDATA
Two more options are set on in options list, and mode is IO
unchanged.
CB LSQA ADD
* CD SET,SYSABEND,SDATA=NUC DM NUC
Mode is changed to ADD (the default) for SYSABEND, ENQ PCDATA
parmlib options are set on, and CD command options ERR SUM
IO TRT
are set on. Previous CD command options remain on.
CB NUC ADD
ABEND SDATA=(CB,SWA,NUC) DM PCDATA
Because mode is ADD, options specified on dump ENQ SUM
request are added to options set on in options list to ERR SWA
IO TRT
determine areas to dump.
LSQA
NODUMP
* CD SET,SYSABEND,NODUMP
Mode is changed to NODUMP. All options in options list
are set off.

Chapter 4. MVS System Commands Reference 4-33

CHNGDUMP Command

Table 4-6. Example of How CHNGDUMP Commands Affect Dump Modes and Options (continued)
FUNCTION (* indicates operator commands/actions) OPTIONS MODE
NODUMP
ABEND SDATA=(CB,SWA,NUC)
Because mode is NODUMP, request is ignored.
CB LSQA ADD
* CD SET,SYSABEND,SDATA=SQA DM SQA
Mode is changed to ADD. Parmlib options on this CD ENQ SUM
command are set. ERR TRT
IO
CB SQA ADD
* CD DEL,SYSABEND,SDATA=(DM,IO) ENQ SUM
Because DEL is specified, specified options in options ERR TRT
list are set off. LSQA

ADD
* CD DEL,SYSABEND,SDATA=(SQA, LSQA,TRT,
CB,ENQ,ERR,SUM)
Specified options are set off in options list.
SQA ADD
ABEND SDATA=(SQA)
The option specified in the dump request determines the
area to dump. There are no options on in the options
list.
CB IO ADD
* CD RESET,SYSABEND DM LSQA
Mode and options list are reset to values established at ENQ SUM
system initialization. ERR TRT

Setting the Dump Modes and Options

Use the following form of the CHNGDUMP command to set the dump modes and
put specified options in the dump options lists.

4-34 z/OS V1R7.0 MVS System Commands

 CHNGDUMP Command

CD SET,{NODUMP }

{OVER }

{ADD }

{SDUMP[=(option[,option]...)] }
[,Q={YES|NO}]
[,TYPE={XMEM|XMEME}]
[,BUFFERS={nnnnK|nnnM}]
[,MAXSPACE=xxxxxxxxM]
[,MSGTIME=yyyyy]
[,SYSFAIL,STRLIST=(s-option[,s-option]...)]
[,NODUMP]
|,OVER
|,ADD

{{SYSABEND}[,SDATA=(option[,option]...) ][,NODUMP] }
{{SYSUDUMP} |,PDATA=(option[,option]...) |,OVER }
|,ADD

{SYSMDUMP[=(option[,option]...)][,NODUMP] }
|,OVER
|,ADD
| {ABDUMP,TIMENQ=yyyy}

Where s-option represents:

STRNAME=strname
[,CONNAME=conname ]

[,ACCESSTIME={ENFORCE|NOLIMIT|NOLIM} ]

[,LOCKENTRIES ]

[,USERCNTLS ]

[,EVENTQS ]

[,(EMCONTROLS={ALL|(list))} ]

[,({COCLASS|STGCLASS|LISTNUM}={ALL|(list)} ]
[ {[,ADJUNCT={CAPTURE|DIRECTIO}][,ENTRYDATA={UNSERIALIZE|SERIALIZE}]} ]
[ {[,SUMMARY] }) ]

SET
Set the dump mode and put specified options in the system dump options list.
NODUMP
Set the SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP dump modes
to NODUMP, and remove all options from the system dump options lists for
these dump types.
ADD
Set the SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP dump modes
to ADD. If any of these dump types were previously in OVER mode, add its
parmlib dump options to its system dump options list.
OVER
Set the SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP dump modes

Chapter 4. MVS System Commands Reference 4-35

CHNGDUMP Command

to OVER. If any of these dump types were previously in ADD mode,

remove its parmlib options from its system dump options list.
SDUMP
Set the SDUMP dump mode to ADD.
SDUMP,NODUMP
Set the SDUMP dump mode to NODUMP.
You cannot specify other parameters when specifying NODUMP. For
example, you can specify CD SDUMP,NODUMP, but not CD
SDUMP,Q=YES,NODUMP.
SDUMP,OVER or ADD
Set the SDUMP dump mode to the specified mode.
SDUMP,SYSFAIL,STRLIST=(structure names and options)
Set structures to be dumped when a single system fails or when all the
systems connected to a coupling facility fail. SYSFAIL may not be specified
with other dump options, and must be specified with STRLIST. The syntax
for the STRLIST specification is identical to the DUMP command. SYSFAIL
and STRLIST may be specified in ADD or OVER mode. In either mode, the
STRLIST parameter list is saved and when a system fails or when all the
systems fail, a dump is requested that includes the specified structures.
SDUMP=(options)
Put the specified options in the SDUMP system dump options list. See
Options for SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP on page
4-29 for SDUMP options you can specify.
SDUMP,TYPE=XMEM
Set the SDUMP system dump options list to cross memory. Specifying
TYPE=XMEM causes SVC dump to dump the cross memory address
spaces that the caller has when SVC dump gets control.
SDUMP,TYPE=XMEME
Set the SDUMP system dump options list to cross memory at the time of
the error. Specifying TYPE=XMEME causes SVC dump to dump cross
memory address spaces that the caller has when the error causing the
dump occurs.
SDUMP,Q=YES or NO
Specifies whether or not SDUMP is to quiesce the systemset it to
nondispatchable (Q=YES) or leave the system dispatchable (Q=NO)while
dumping the contents of the SQA or CSA.
Quiescing the system increases the ability to capture SQA and/or CSA data
when a failure occurs. However, the system can appear hung when
collecting large amounts of data. When the system is not quiesced, users
are more likely to receive uninterrupted system service.
If the operator issuing the CHNGDUMP command specifies Q=YES,
SDUMP will always quiesce the system, whether or not it dumps the SQA
or CSA. That is, the command will override the specification in the program.
If the operator specifies Q=NO, SDUMP will not quiesce the system. An
exception to this is that SDUMP will quiesce the system if the program
specified to dump the SQA or CSA and it included the QUIESCE parameter
on the SDUMP macro.

4-36 z/OS V1R7.0 MVS System Commands

 CHNGDUMP Command

If the operator issuing the CHNGDUMP command specifies neither Q=YES

nor Q=NO, the system will use the value the program specified for the
QUIESCE parameter on the SDUMP macro.
SDUMP,BUFFERS=nnnnK or nnnM
Reserves storage for exclusive use by SVC dump. SVC dump can use this
storage while it captures the contents of common area storage. The amount
of storage that is set aside is expressed in kilobytes (0K to 9999K) or in
megabytes (0M to 999M). The default is 0.
You can enter the BUFFERS option at any time to change the amount of
storage reserved for use by SVC dump only. You should decide how much
storage the installation needs to set aside for use by SVC dump, without
seriously impacting system performance. Specifying a large BUFFERS
value may degrade performance because the system reserves a large
amount of storage for use by SVC dump.
SDUMP,MAXSPACE=xxxxxxxxM
Specifies the maximum amount of virtual storage that SVC dump can use
to capture volatile virtual storage data, summary dump data, and
component-specific data before writing the dump to DASD. The default
value is 500 megabytes. The value that can be specified may range from 1
to 99999999 (with, or without, an M suffix). The new value takes effect
immediately. If the value specified is lower than the space used, SVC dump
will not continue to capture data.
The CHNGDUMP command only provides two ways to change the
MAXSPACE value: by using the SET,SDUMP invocation as described here;
or by using the RESET,SDUMP invocation that resets all initial SDUMP
parameters, including setting the MAXSPACE value to 500M.
SDUMP,MSGTIME=yyyyy
Specifies how long message IEA793A appears on the console, where yyyyy
is a number of minutes from 0 99999. The default is 99999. When the
system deletes the message, it also deletes the captured dump.
You cannot delete this option with CHNGDUMP DEL. To change the value
of MSGTIME, issue the CHNGDUMP command in the SET mode with a
new value. If you change the MSGTIME value after the message IEA793A
appears, the new value will be in affect immediately. If you set the
MSGTIME value to 0, the system will not issue the message and it deletes
the captured dump.
STRLIST= or STL=(STRNAME=strname...)
Used to include in the dump a list of coupling facility structures. Following
are the structure-related keywords:
STRNAME= or STRNM=strname
Designates a particular coupling facility list or cache structure. strname
is the name of the coupling facility structure to be included in the dump.
Any dump options for this structure are replaced when you issue this
command. If strname does not begin with a letter or is longer than 16
characters the system issues syntax error message IEE866I. If a
structure does not exist, or the update fails for any reason, the system
issues message IEE816I. You may include more than one
STRNAME=strname within the parentheses, separated by commas.
CONNAME= or CONNM=conname
When specified for a coupling facility cache structure, requests the user
registry information for this user be included in the dump. conname is

Chapter 4. MVS System Commands Reference 4-37

CHNGDUMP Command

the name of a connected user. If the connected user represented by the

conname does not exist, the dump will not contain user registry
information.
ACCESSTIME= or ACC={ENFORCE or ENF or NOLIMIT or NOLIM}
Indicates whether the dump time limit specified on the ACCESSTIME
parameter of the IXLCONN macro is in effect. When
ACCESSTIME=ENFORCE is specified, the system holds structure
dump serialization no longer than the time interval specified on the
IXLCONN macro. This is the default. If ACCESSTIME=0 is specified on
the IXLCONN macro and ACCESSTIME=ENFORCE is specified on the
dump request, the structure will not be included in the dump.
When ACCESSTIME=NOLIMIT is specified, the dump time limit is not in
effect and the system will hold structure dump serialization until
processing is completed.
LOCKENTRIES or LOCKE
When specified for a coupling facility list structure, the system includes
in the dump the lock table entries for the requested structure. Since
lock table entries do not exist for coupling facility cache structures, this
keyword is ignored when specified for a coupling facility cache
structure.
USERCNTLS or UC
Requests that the user attach controls be included in the dump.
(list)
Represents a list of values, ranges of values, or values and ranges of
values.
(start1-end1,value2,start3-end3, ...)
COCLASS= or COC=ALL or (list)
Specifies which cast-out classes are included in the dump. For each
cast-out class, the cast-out class controls are dumped and the directory
information for each of the entries within the requested cast-out classes
are dumped (if SUMMARY is not specified).
COCLASS is valid only for a coupling facility cache structure. If
specified for a coupling facility list structure, the structure is not included
in the dump.
When COCLASS=ALL is specified, the cast-out class controls for all
cast-out classes are dumped along with the directory information for all
entries within the classes (if SUMMARY is not specified).
When COCLASS=(list) is specified, the cast-out class controls for (list)
are dumped along with the directory information for the entries in the
requested cast-out classes (if SUMMARY is not specified). The values
specified in a range are the decimal cast-out class values in the range
065535. When a requested class does not exist, it is not dumped.
STGCLASS= or SC=ALL or (list)
Specifies which storage classes are included in the dump. For each
storage class, the storage class controls are dumped and the directory
information for each of the entries within the requested storage classes
are dumped (if SUMMARY was not specified).
STGCLASS is valid only for a coupling facility cache structure. If
specified for a coupling facility list structure, the structure will not be
included in the dump.

4-38 z/OS V1R7.0 MVS System Commands

 CHNGDUMP Command

When STGCLASS=ALL is specified, the storage class controls for all

storage classes are dumped along with the directory information for all
entries within the classes (if SUMMARY is not specified).
When STGCLASS=(list) is specified, the storage class controls for (list)
are dumped along with the directory information for the entries in the
requested storage classes (if SUMMARY is not specified). The values
specified are the decimal storage class values, 0255. When a
requested class does not exist, it is not dumped.
LISTNUM= or LNUM=ALL or (list)
Specifies which lists are included in the dump. The list controls are
dumped along with the entry controls for the entries on each requested
list (if SUMMARY is not specified).
LISTNUM is only valid for a coupling facility list structure. If specified for
a coupling facility cache structure, the structure is not included in the
dump.
When LISTNUM=ALL is specified, the list controls for all lists in the
coupling facility list structure are dumped along with the entry controls
(if SUMMARY is not specified).
When LISTNUM=(list) is specified, the list controls for (list) are included
in the dump along with the entry controls for those lists. The values
specified are the decimal list values, 04294967295. The system
ignores a zero in the case of LISTNUM. No error results. When a
requested list does not exist, it is not dumped.

You may use the following keyword to further modify the STGCLASS,
COCLASS and LISTNUM keywords:
ADJUNCT= or ADJ={CAPTURE or CAP or DIRECTIO or DIO}
Indicates that the adjunct data for each entry specified by the range is
included in the dump. When you do not specify this keyword, or when
adjunct data does not exist for this structure, the dump does not include
the adjunct data.
ADJUNCT may not be specified with SUMMARY. If they are both
specified, a syntax error is issued.
When ADJUNCT=CAPTURE is specified, the adjunct data is captured
in the facility dump space along with the directory information while
dumping serialization is held.
When ADJUNCT=DIRECTIO is specified, the adjunct data is written
directly to the dump data set after the directory information is captured.
The adjunct data is not captured in the structure dump table. The
adjunct data may be changing as dumping proceeds.
ENTRYDATA= or EDATA={UNSERIALIZE or UNSER or SERIALIZE or
SER}
Indicates that the entry data for each entry within the requested range
is included in the dump. When this keyword is not specified or when
entry data does not exist for the structure, entry data is not included in
the dump.
ENTRYDATA may not be specified with SUMMARY. If they are both
specified, a syntax error is issued.
When ENTRYDATA=UNSERIALIZE is specified, the entry data is
dumped after structure dump serialization is released. The entry data

Chapter 4. MVS System Commands Reference 4-39

CHNGDUMP Command

may be changing relative to the entry controls that were captured while
structure dump serialization was held.
When ENTRYDATA=SERIALIZE is specified, the entry data is dumped
while serialization is held. If ACCESSTIME=ENFORCE is specified and
the dump time limit expires before the entry data is written to the dump
data set, the system continues to write the entry data to the dump data
set even though serialization is not held.
SUMMARY or SUM
Indicates that a summary of the range of classes or lists is dumped.
The directory information for the entries is excluded from the dump.
SUMMARY may not be specified with ADJUNCT or ENTRYDATA. If it
specified with either of these keywords, a syntax error is issued.
Notes:
1. A syntax error is issued if STRNAME is not the first keyword.
2. If CONNAME and ACCESSTIME are specified more than one time for a
structure, the first CONNAME and the last ACCESSTIME are used.
3. When a list number, a storage class, a cast-out class, or an entry is
specified in the STRLIST more than once, it will be dumped more than
once. An example of this is when STGCLASS=ALL is specified with
COCLASS=ALL. All entries in the coupling facility cache structure are
dumped twice. Once grouped by storage class and again grouped by
cast-out class.
4. When neither LISTNUM, STGCLASS, or COCLASS is specified, no list
or class controls are dumped and no entries are dumped.
5. If you request a large amount of dump data, the system may not be
able completely to dump all the data. You can expect to successfully
dump up to a maximum of 47 structures if you specify no more than a
total of 6 ranges. If you must specify more than 6 ranges, you must
specify fewer structures. For each structure less than 47 that you
specify, you can specify another 10 ranges, as follows:

Number of Structures Number of Ranges

47 6
46 16
45 26
44 36
. .
. .
. .

If the system cannot dump all the data you requested, it prioritizes the
data according to your specifications on the command in the following
manner:
a. The system will attempt to dump the first requested structure first.
1) Within that structure, the system processes the LOCKENTRIES,
USERCNTLS, COCLASS, STGCLASS, and LISTNUM
parameters in the order that they are specified. COCLASS,
STGCLASS, and LISTNUM may be specified more than once
for a single structure.

4-40 z/OS V1R7.0 MVS System Commands

 CHNGDUMP Command

2) The system dumps requested serialized data before requested

unserialized data starting with the first requested data in the
structure and proceeding through the last data that was
requested as serialized.
b. The system then dumps the next-requested structure data starting
with the first requested data in the structure and proceeding through
the last data that was requested as serialized.
c. The system continues in this manner until all serialized data in all
requested structures has been prioritized for dumping.
d. The system then dumps any remaining data that was requested as
unserialized that may not have been dumped beginning with the
first-requested structure.

Structure 1
Range 1 Serialized Data as
Range 2 specified on
Range 3 Serialized Priority 1 the command
Range 4
Range 5 Serialized
Range 6 Priority 3

Structure 2
Range 1 Serialized
Range 2 Priority 2
Range 3 Serialized
Range 4 Priority 4

Structure 1 Range 1 Data as

Range 2 prioritized
Range 3 Priority 1 for dumping
Range 4
Range 5
Structure 2 Range 1
Range 2 Priority 2
Range 3
Structure 1 Range 6 Priority 3
Structure 2 Range 4 Priority 4

6. The CONT parameter allows the operator to provide input to the

CHNGDUMP command that spans more than one line of input. You can
specify the CONT parameter after any comma within the STRLIST
parameter list. If a line of input ends with a comma and any closing
parentheses are missing, the system assumes the CONT parameter.
SYSABEND
Set the SYSABEND dump mode to ADD.
SYSABEND,NODUMP
Set the SYSABEND dump mode to NODUMP.

Chapter 4. MVS System Commands Reference 4-41

 CHNGDUMP Command

You cannot specify other parameters when specifying NODUMP. For

example, you can specify CD SYSABEND,NODUMP, but not CD
SYSABEND,PDATA=option,NODUMP.
SYSABEND,OVER or ADD
Set the SYSABEND dump mode to the specified mode.
SYSABEND,SDATA=(option[,option]...)
Put the specified SDATA options in the SYSABEND system dump options
list. See Options for SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP
on page 4-29 for SYSABEND options you can specify.
SYSABEND,PDATA=(option[,option]...)
Put the specified PDATA options in the SYSABEND system dump options
list. See Options for SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP
on page 4-29 for SYSABEND options you can specify.
SYSUDUMP
Set the SYSUDUMP dump mode to ADD.
SYSUDUMP,NODUMP
Set the SYSUDUMP dump mode to NODUMP.
You cannot specify other parameters when specifying NODUMP. For
example, you can specify CD SYSUDUMP,NODUMP, but not CD
SYSUDUMP,PDATA=option,NODUMP.
SYSUDUMP,OVER or ADD
Set the SYSUDUMP dump mode to the specified mode.
SYSUDUMP,SDATA=(option[,option]...)
Put the specified SDATA options in the SYSUDUMP system dump options
list. See Options for SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP
on page 4-29 for SYSUDUMP options you can specify.
SYSUDUMP,PDATA=(option[,option]...)
Put the specified PDATA options in the SYSUDUMP system dump options
list. See Options for SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP
on page 4-29 for SYSUDUMP options you can specify.
SYSMDUMP
Set the SYSMDUMP dump mode to ADD.
SYSMDUMP,NODUMP
Set the SYSMDUMP dump mode to NODUMP.
You cannot specify other parameters when specifying NODUMP. For
example, you can specify CD SYSMDUMP,NODUMP, but not CD
SYSMDUMP=option,NODUMP.
SYSMDUMP,OVER or ADD
Set the SYSMDUMP dump mode to the specified mode.
SYSMDUMP=(option[,option]...)
Put the specified options in the SYSMDUMP system dump options list. See
Options for SDUMP, SYSABEND, SYSUDUMP, and SYSMDUMP on page
4-29 for SYSMDUMP options you can specify.
| ABDUMP,TIMEENQ=yyyy
| Sets the approximate number of seconds that ABDUMP processing waits
| for obtaining required resources. The value may be changed up to the
| maximum of 9999. If this command is used to change the value from the
| IBM default interval of 240 seconds, place the command into a COMMNDxx

4-42 z/OS V1R7.0 MVS System Commands

 CHNGDUMP Command

| member of PARMLIB. That establishes the setting as the installation default

| when the system is IPLed. See z/OS MVS System Messages, Vol 6
| (GOS-IEA) for the discussion in message IEA848I, DEADLOCK AVOIDED
| to find more information.
| Whenever the TIMEENQ value is changed, the new value takes effect
| immediately. A value of 0 does not force an SVC dump to occur, because
| the resources required might be immediately available. You can not use
| CHNGDUMP DEL to delete this option.

Chapter 4. MVS System Commands Reference 4-43

CMDS Command

CMDS Command
Use the CMDS command to display executing and waiting MVS commands, to
delete commands that are waiting for execution, or to cancel commands that are
executing.

Syntax
The complete syntax for the CMDS command is:

CMDS {ABEND,CMD=cccccccc,ID=nnnn[,CLASS=classname][,JOB=jobname]}

{DISPLAY|D[,CLASS=classname][,CMD=cccccccc][,ID=nnnn][,JOB=jobname]}

{REMOVE|R[,CLASS=classname][,CMD=cccccccc][,ID=nnnn][,JOB=jobname]}

{SHOW|S[,CLASS=classname][,CMD=cccccccc][,ID=nnnn][,JOB=jobname]}
Notes:
1. The ABEND parameter requires that you specify the CMD= and ID= subparameters.
2. The REMOVE parameter requires that you specify at least one subparameter.
3. You may specify the optional subparameters of the default or specified parameter in any
order.

Parameters
CMDS
v ABEND abnormally end a command that is currently executing.
This parameter requires subparameters CMD= and ID=.
The system terminates, with ABEND code 422, reason code 00010301, the
command that CMD=cccccccc and ID=nnnn identifies.
Use the ABEND option with extreme caution, being careful to avoid leaving the
system in an inconsistent state. Use this parameter only as a last resort, such as
when a command is hanging in execution.
The system issues message IEE064I in response to this command. It does not
send any response message to the console that issued the abended command.
Attention: An ACTIVATE command may still be active as a task in IOSAS after
the command task has been abended with a CMDS ABEND.
v DISPLAY | D display the numbers and brief information about the commands
that are currently executing and those that are waiting for execution.
The system issues message IEE062I in response to this command.
v REMOVE | R remove commands that are waiting for execution, as specified
by the subparameters. You cannot use this option to cancel any commands that
are executing.
The REMOVE parameter requires you specify at least one of the keyword
subparameters CLASS=, CMD=, ID=, or JOB=.
The system issues message IEE064I in response to this command, and sends
message IEE065I to the console that issued the removed command.
v SHOW | S display full information about the specific command(s) specified by
the subparameters.
The system issues message IEE063I in response to this command.

4-44 z/OS V1R7.0 MVS System Commands

 CMDS Command

The CMDS command uses the following keyword subparameters to limit the
number of commands to show or remove:
v CLASS= classname
The command class in which the commands belong.
If you do not specify this parameter, commands in all classes will be displayed or
removed.
The classes are:
1. Class M1 commands may be essential to clearing a backlog of Class M2
commands.
2. Class M2 commands are ordinary attached commands that run in the
MASTER address space.
| 3. Class M3 is only for SEND commands executed in the MASTER address
| space.
4. Class C1 commands might be needed to clear a backlog of Class C2
commands.
5. Class C2 commands are ordinary attached commands that run in the
CONSOLE address space.
| 6. Class C3 is only for the ROUTE command executed in the CONSOLE
| address space.
For a list of the commands by class, see Command Flooding on page 1-33.
v CMD= command verb
The name of the command, as displayed by the SHOW option. For example,
CMDS REMOVE,CMD=CONFIG

will delete all CONFIG commands that are waiting for execution.
You can use command abbreviations instead of full command names.
v ID= number
The commands sequence number, which appears in the output from a CMDS
DISPLAY or CMDS SHOW command (messages IEE062I or IEE063I).
v JOB= jobname of the command issuer, as displayed by the SHOW option. For
example,
CMDS REMOVE,JOB=JOB1111

will remove all commands issued by JOB1111.

If you specify more than one of the keyword parameters, the command must
meet all specified criteria. For example,
CMDS REMOVE,CMD=VARY,JOB=JOB1111

will remove waiting VARY commands that job JOB1111 issued.

Note: Some commands remain active indefinitely, so the system will display them
whenever CMDS is issued. For example, if any SLIP commands have been
issued and SLIP traps are in effect, one SLIP command will be executing
| until all traps are deleted. This is also true for many SET commands, such
| as SET SLIP and SET MPF.

Chapter 4. MVS System Commands Reference 4-45

CONFIG Command

CONFIG Command
Use the CONFIG command to change or check the configuration of the system.
You can use the CONFIG command to change the online or offline status of
available processors, Vector Facilities attached to online processors, storage
amounts, storage ranges, central and expanded storage elements, and channel
paths:
1. Directly
2. In response to a configuration display
3. With the options in a CONFIGxx parmlib member that you specify

Table 4-7 summarizes the information that the CONFIG command provides. Use it
to access the pages on which you can find details about a particular use of the
CONFIG command.
Table 4-7. Summary of the CONFIG Command
Command: Topic:
CONFIG CHP Reconfiguring the System Directly
CONFIG CPUAD
CONFIG ESTOR
CONFIG STORAGE
CONFIG VF
CONFIG MEMBER Reconfiguring the System with a CONFIGxx Parmlib
Member on page 4-55
CONFIG OFFLINE Reconfiguring the System in Response to a Configuration
CONFIG ONLINE Display on page 4-56

The CONFIG command reconfigures (both logically and physically) available

processors, Vector Facilities attached to online processors, central storage ranges,
amounts, and elements, and expanded storage elements, and channel paths.

Note: To configure an Integrated Cryptographic Facility (ICRF) online or offline, you

have to configure online or offline the processor to which the ICRF is
attached and, when configuring an ICRF online, Integrated Cryptographic
Service Facility/MVS (ICSF/MVS) must be active. You can enter the CONFIG
command only from a console with master authority.

Syntax
The syntax for each variation of the CONFIG command is shown immediately
preceding its respective parameter list.

CONFIG or CF

Reconfiguring the System Directly

Use the CONFIG command to change the online or offline status of any of the
following, directly, that is, without invoking a configuration display or a CONFIGxx
parmlib member: available processors, Vector Facilities, and Integrated
Cryptographic Facilities (ICRFs), attached to online processors, storage amounts,
storage ranges, central and expanded storage elements, logical partitions, or
channel paths.

See z/OS MVS Recovery and Reconfiguration Guide for more information about
how to reconfigure the resources associated with a processor or a processor

4-46 z/OS V1R7.0 MVS System Commands

 CONFIG Command

complex. See PR/SM Planning Guide for more information about logical partitions.

CF {{CPUAD|CPU}(x[,x]...)[,{ONLINE|ON}[,VFON ]|,{OFFLINE|OFF}] }
|,VFOFF

{VF(x[,x]...)[,{ONLINE|ON}|,{OFFLINE|OFF}] }

| {{STORAGE|STOR}{(ddddddddM) }[,{ONLINE|ON}|,{OFFLINE|OFF}] }
| {(ddddddddM-ddddddddM)}
{(E=id) }

{ESTOR(E=id)[,{ONLINE|ON}|,{OFFLINE|OFF}] }

{CHP{(xx) }[,{ONLINE|ON}[NOVARY]|,{OFFLINE|OFF}[,UNCOND]] }
{(aa-bb) } |,FORCE
{(list) }
{(ALL,id)}

The parameters are:

CPUAD or CPU
The system is to reconfigure one or more processors. The system is also to
reconfigure one or more Vector Facilities and ICRFs attached to specified online
processors.
(x[,x]...)
| One or more processors identified by x in hexadecimal format.
ONLINE or ON
The system is to bring the specified processor(s) online. If necessary, the
system synchronizes the processors TOD clocks. Each processors Vector
Facility remains in the state it was in when the system last varied the
processor offline. If Integrated Cryptographic Service Facility/MVS
(ICSF/MVS) is active, the system brings online any ICRF attached to each
processor.
ONLINE,VFON
The system is to bring online the specified processor(s), and bring online
the Vector Facility attached to each specified processor. If ICSF/MVS is
active, the system brings online any ICRF attached to each processor.
ONLINE,VFOFF
The system is to bring online the specified processor(s), but keep offline the
Vector Facility attached to each processor. If ICSF/MVS is active, the
system brings online any ICRF attached to each processor.
OFFLINE or OFF
The system is to take offline the specified processor(s) and any ICRF
attached to the processor(s).
VF
The system is to reconfigure, both logically and physically, one or more Vector
Facilities attached to online processors.
(x[,x]...)
One or more online processors identified by x (0 through F) that have
Vector Facilities attached.
ONLINE or ON
The system is to bring online each specified Vector Facility.

Chapter 4. MVS System Commands Reference 4-47

 CONFIG Command

OFFLINE or OFF
The system is to take offline each specified Vector Facility.
STORAGE or STOR
The system is to reconfigure central storage, both logically and physically. Note
that storage reconfiguration is not supported on all processors and that central
storage reconfiguration in a PR/SM environment without enhanced dynamic
storage reconfiguration must be specified by storage element ID. The starting
and ending addresses of the central storage for which you want the status
display.
| ddddddddX
| The amount of central storage to be reconfigured. Specify up to eight
decimal digits followed by a multiplier (M-megabytes, G-gigabytes,
T-terabytes, P-petabytes) for this amount. Check the configuration of your
processor to see which size storage increments are supported. The value
| for dddddddd must be a multiple of the storage increment size (usually 2, 4,
or 8), and cannot exceed 16383P.
Instead of specifying a decimal amount, you may specify a hexadecimal
amount, with or without a multiplier, in the format X'xxxxxx'. For example:
v X'123456789A00000'
v X'123'M
You may use underscores in any hexadecimal specification for better clarity.
Underscores in the specification are ignored during processing.
| ddddddddX-ddddddddX
The starting and ending addresses of the central storage section to be
| reconfigured. Specify up to eight decimal digits followed by a multiplier
(M-megabytes, G-gigabytes, T-terabytes, P-petabytes) for each address.
| The value for each dddddddd must be a multiple of the storage increment
size (usually 2, 4, or 8), and cannot exceed 16383P. The starting and
ending addresses must not be the same.
Instead of specifying the range using decimal numbers, you may specify it
in hexadecimal, with or without a multiplier, in the format
X'xxxxxx'-X'xxxxxx'. For example:
v X'123456789A00000'-X'123456789B00000'
v X'123'M-X'124'M
You may use underscores in any hexadecimal specification for better clarity.
Underscores in the specification are ignored during processing.
E=id
The storage element to be reconfigured, identified by the storage element
id. Use this parameter only under the direction of a system programmer to
take a storage element offline or online.
ONLINE or ON
The system is to bring the specified storage range or storage element
online. The system rejects the command if you specify:
v An address higher than the storage limit set at system initialization
v An address or an element id for storage that is not available to the
system
OFFLINE or OFF
The system is to take the specified storage range or storage element
offline.

4-48 z/OS V1R7.0 MVS System Commands

 CONFIG Command

Notes:
1. There can be a delay between the time you enter CONFIG STOR ...
OFFLINE and the time the system issues a message indicating the
storage is offline. This delay occurs when there is activity in the
specified storage; all activity in the storage must stop before the
command can take effect. If the storage does not go offline within a
short time, a message appears that lets you cancel the command.
2. When you issue CONFIG STOR ... OFFLINE without E=id, the system
rejects the command if you specify storage that is either part of the
hardware system area (HSA) or assigned permanently to the system.
Generally, you can take non-preferred (reconfigurable) storage offline,
but, you cannot take preferred (non-reconfigurable) storage offline.
3. When you issue CONFIG STOR ... OFFLINE with E=id, the system
moves any storage associated with the HSA or permanently assigned to
the system to another storage element. The system saves the
addresses of the former storage and displays their address ranges.
| 4. In order to configure a range of storage online through the CONFIG
| STOR(xx-xx),ONLINE command, the subject storage must be in a
| storage element that is online. If a storage element is offline, the only
| way to bring online any storage within that element is to configure the
| entire element online, through CONFIG STOR(E=id),ONLINE.
ESTOR
The system is to reconfigure expanded storage elements.
(E=id)
The expanded storage element to be reconfigured, identified by its storage
element id.
The expanded storage element to be reconfigured, identified by its storage
element id. If you specify E=0 in LPAR mode, the system is to reconfigure
the initial allocation of the expanded storage element (as defined in the
activation profile), unless the initial allocation is zero, in which case E=0 will
reconfigure the reserved allocation. If you specify E=1, the system is to
reconfigure the reserved allocation of the expanded storage element (as
defined in the activation profile), unless the initial allocation is zero, in which
case no storage will be reconfigured.
ONLINE or ON
The system is to bring the specified expanded storage element online. The
system issues message IEE524I to display the ranges of expanded storage
that come online. The system rejects the command if you specify an id for
an expanded storage element that is not available to the system.
If the system cannot bring some of the requested storage online, message
IEE578I displays the total amount of requested storage that is left offline.
OFFLINE or OFF
The system is to take the specified expanded storage element offline. The
system issues message IEE510I to display the ranges of expanded storage
that went offline with the expanded storage element. If the system cannot
reconfigure the expanded storage element physically offline, the system
rejects the command and issues message IEE148I.
Notes:
1. There can be a delay between the time you enter CONFIG ESTOR...
OFFLINE and the time the system issues a message indicating the
expanded storage is offline. This delay occurs when there is activity in

Chapter 4. MVS System Commands Reference 4-49

CONFIG Command

the specified storage; all activity in the storage must stop before the
command can take effect. If the storage does not go offline within a
short time, a message appears that lets you cancel the command.
2. When you issue CONFIG ESTOR...OFFLINE to take an expanded
storage element offline, the system issues a display that tells what
address ranges have been removed.
3. ESTOR processing is not applicable to the z/Architecture environment.
CHP
The system is to reconfigure one or more channel paths.
Note that if you have systems running on a processor at the z990 level or
higher, you can automatically reconfigure channel paths on and offline using the
hardware management console (HMC) instead of issuing the CONFIG
command. On a z990, you may have multiple logical channel subsystems,
which means that if an ESCON card fails, you need to reconfigure 15 channels
being used across 30 different partitions in each logical channel subsystem.
Automatic CHPID reconfiguration lets you issue a reconfiguration request
centrally from HMC, which in turn triggers the z/OS systems in each partition to
issue the CONFIG command. Then only those partitions that cannot process
the request or are not running on a z990 level processor or higher need to be
individually reconfigured with the CONFIG command.
(xx)
A single channel path identified by xx. The channel path identifier may have
a value from 0 to FF.
(aa-bb)
A range of channel paths. The starting and ending channel path identifiers
may have values from 0 to FF.
(list)
One or more single channel paths, ranges of channel paths, or a
combination of single channel paths and ranges of channel paths. ALL,id
cannot be included in the list.
(ALL,id)
All of the channel paths associated with one side of a partitioned processor
complex are to be placed online or offline, where id is the identifier (0 or 1)
of the side. Use ALL,id only when your processor complex is one that can
be partitioned (such as a 3090 Model 400 Processor Complex). Message
IEE172I indicates that all channel paths on a side have been brought online
or taken offline.

Note: If you configure a partitionable processor from single image to

partitioned mode, and a tape mount is pending, the tape drive(s)
might not start after you mount them. You can avoid the problem by
mounting the tape before you issue the CONFIG
CHP(ALL,id),OFFLINE command to perform the partitioning or, after
partitioning, you can issue the VARY device,ONLINE command to
start the tape drive(s).
ONLINE or ON
The system is to bring the specified channel path(s) online.
ONLINE,NOVARY
The system is to bring the specified channel paths online without bringing
online the paths to the associated devices. Use this command when you

4-50 z/OS V1R7.0 MVS System Commands

 CONFIG Command

want to configure online a channel path that does not currently have a
device connected. Example 10 shows the operator commands and system
responses.
OFFLINE or OFF
The system is to take the specified channel path(s) offline. The system
rejects this command if it would remove the last path to a device that is:
v In use by a system function
v Online
v Allocated
v A TP device
v The only active console in the system
v A coupling facility.
To remove the last path to all other devices, use the CONFIG command
without the UNCOND or FORCE parameters.
OFFLINE
The command processor determines if taking the CHPID offline will
cause a loss of consoles that should not be lost, for example, the MCS
master console. If the MCS master console could be lost, the CONFIG
command processor rejects the command. With SMCS consoles, there
is no way to associate the CHPID to an LU so the command cannot
detect if an SMCS console will be lost.
OFFLINE,UNCOND
The system is to take the specified channel path(s) offline, even if it is the
last path to a device. The system rejects this command if it would remove
the last path to a device that is:
v In use by a system function
v Allocated
v A TP device
v The only active console in the system
v A coupling facility in use by an active XES connection on the system
from which the CONFIG command is issued. (Structures in the coupling
facility can be in use, persistent, or have failed-persistent connectors.)
Use OFFLINE,UNCOND to remove the last path to an unallocated online
device. You cannot do this by specifying OFFLINE alone.
OFFLINE,FORCE
CAUTION: FORCE is a very powerful option. Never specify FORCE
unless you understand all its consequences for your system.
The system is to take the specified channel path(s) offline, even if it is the
last path to a device. The system rejects this command if it would remove
the last path to a device that is:
v The only active console in the system

The last path to all other devices listed in the OFFLINE,UNCOND option
can be removed by the OFFLINE,FORCE option.

Responding to the FORCE Option

Message IEE100E lists any devices that are affected by the

OFFLINE,FORCE options. The following message then asks you to confirm
the FORCE option:
IEE131D REPLY CANCEL OR CONTINUE

Chapter 4. MVS System Commands Reference 4-51

CONFIG Command

Reply CANCEL to leave the channel path and devices online. Reply
CONTINUE if you want to remove the channel path. After you reply
CONTINUE, the following message appears:
IEE507D SHOULD ACTIVE DEVICES HAVE I/O TERMINATED?
REPLY NO OR YES

Reply NO to leave the affected devices online and allocated.

If you specify NO to message IEE507D, the channel path will NOT be

configured offline.

Reply YES to have the system stop all I/O in progress on the affected
devices, permanently reject all future I/O requests to the devices, and mark
the affected devices pending-offline.

If you specify YES to message IEE507D, further system action depends on

whether or not there are reserved devices on the channel path you want to
take offline:
v If there are no reserved devices on the channel path, the system takes
the channel path offline when it stops I/O on the devices.
v If there are reserved devices on the channel path for which there are no
alternate paths, you get the following messages after you reply YES to
message IEE507D:
IEE508E NO ALTERNATE PATHS TO RESERVED
DEVICES ddd [,ddd]...
IEE131D REPLY CANCEL OR CONTINUE
If you dont want to lose I/O on reserved devices, reply CANCEL to
terminate the CONFIG command and leave the channel path and
devices online. Reply CONTINUE to have the system continue to remove
the channel path. After you reply CONTINUE, message IOS062E is
issued. All the processors for this image enter a restartable disabled wait
(WAIT062) state.
The IOS062E message asks you to stop all systems sharing the
reserved devices so the system can reserve the devices again, if
possible, through alternate paths. If the system cannot find alternate
paths, it stops I/O in progress on the devices, rejects any future I/O
requests to the devices as permanent I/O errors, and marks the devices
pending-offline.
Once the system has been restarted from the wait state, recovery for the
channel path will be started and completed. Then, message IOS201E will
inform you to start the processors stopped when message IOS062E was
issued.

Generally, when CONFIG CHP OFFLINE,FORCE causes the system to

take a device offline, you can bring the device back online by bringing
online a channel path that provides a path to the device. Once it is back
online, the device is again available for allocation. However, if the device
was reserved when the system took it offline with the channel path, to bring
the device back online and make it again available for allocation, you must
provide a path to the device with a CONFIG CHP command and issue a
VARY device ONLINE command.

Specifically, when the master console goes offline because of a CONFIG

CHP OFFLINE command, a CONFIG CHP ONLINE command for the same
channel path brings the device back online. The master console, however,

4-52 z/OS V1R7.0 MVS System Commands

 CONFIG Command

remains the alternate console assigned when the master console went
offline. The original master console remains an alternate console unless you
again make it the master console by issuing the VARY CONSOLE and
VARY MSTCONS commands.

Responding to the FORCE Option for a Coupling Facility

Message IXL126I identifies the coupling facility that is affected by the

OFFLINE,FORCE option. The following message then asks you to confirm
the FORCE option:
IXL127A REPLY CANCEL OR
CONTINUE

Reply CANCEL to leave the coupling facility online. Reply CONTINUE if you
want to remove the coupling facility.

Example 1

To take processor 2 offline, enter:

cf cpu(2),offline

Example 2

To bring online a storage range from real addressses four to eight megabytes,
enter:
cf stor(4m-8m),on

Example 3

To take storage element 0 offline, enter:

cf stor(e=0),offline

Example 4

To bring channel paths 4-9 and 12 online, enter:

cf chp(4-9,12),online

Example 5

To take channel paths 0-6 offline, even though one might be the last path to an
unallocated online device, enter:
cf chp(00-06),offline,uncond

Example 6

To bring all channel paths associated with side 1 online, enter:

cf chp(all,1),online

Example 7

To bring processor 1 online with its Vector Facility, enter:

cf cpu(1),online,vfon

If the Vector Facility was online when the system last varied processor 1 offline, the
following command would produce the same result:

Chapter 4. MVS System Commands Reference 4-53

CONFIG Command

cf cpu(1)

Example 8

To bring processor 2 online but keep offline the attached Vector Facility, issue:
cf cpu(2),online,vfoff

Example 9

To bring the Vector Facility attached to processor 3 online, issue:

cf vf(3),online or cf vf(3)

Example 10

CHP(01) is associated with devices 223 and 224. To correct an error condition,
CHP(01) was configured offline to the system. Problem analysis determined that
device 224 has a hardware problem that cannot be immediately corrected. This
example shows how to configure CHP(01) online without bringing the path to device
224 online.

To display status for devices 223 and 224 before configuring CHP(01) online, issue
the following commands:
d m=dev(223)
d m=dev(224)

The output, which shows that the paths to the devices are not online and not
operational, appears as follows:
IEE174I 09.05.00 DISPLAY M 197
DEVICE 0223 STATUS=OFFLINE
CHP 01
PATH ONLINE N
CHP PHYSICALLY ONLINE N
PATH OPERATIONAL N
IEE174I 09.05.30 DISPLAY M 200
DEVICE 0224 STATUS=OFFLINE
CHP 01
PATH ONLINE N
CHP PHYSICALLY ONLINE N
PATH OPERATIONAL N

To configure channel path 01 online without bringing online the paths to devices
223 and 224, issue the following command:
cf chp(1),online,novary

The system issues the following messages to indicate that not all paths were
brought online:
IEE754I NOT ALL PATHS BROUGHT ONLINE WITH CHP(01)
IEE502I CHP(1),ONLINE
IEE712I CONFIG PROCESSING COMPLETE

To display the status of each device after configuring the channel path online, issue
the following commands:
d m=dev(223)
d m=dev(224)

4-54 z/OS V1R7.0 MVS System Commands

 CONFIG Command

The output, which shows that the paths to the devices are not online but are
operational, appears as follows:
IEE174I 09.05.40 DISPLAY M 200
DEVICE 0223 STATUS=OFFLINE
CHP 01
PATH ONLINE N
CHP PHYSICALLY ONLINE Y
PATH OPERATIONAL Y
IEE174I 09.05.50 DISPLAY M 200
DEVICE 0224 STATUS=OFFLINE
CHP 01
PATH ONLINE N
CHP PHYSICALLY ONLINE Y
PATH OPERATIONAL Y

To vary the path online for device 223, issue the following command:
vary path(223,01),online

To display the status of devices 223 and 224 after varying the channel path online,
issue the following commands:
d m=dev(223)
d m=dev(224)

The output, which shows that only the path to device 223 is online and operational,
appears as follows:
IEE174I 09.05.55 DISPLAY M 200
DEVICE 0223 STATUS=ONLINE
CHP 01
PATH ONLINE Y
CHP PHYSICALLY ONLINE Y
PATH OPERATIONAL Y
IEE174I 09.05.59 DISPLAY M 200
DEVICE 0224 STATUS=OFFLINE
CHP 01
PATH ONLINE N
CHP PHYSICALLY ONLINE Y
PATH OPERATIONAL Y

Reconfiguring the System with a CONFIGxx Parmlib Member

Use the CONFIG MEMBER command when you want the system to use options in
a CONFIGxx parmlib member to change the online or offline status of available
processors, storage sections, and channel paths. See z/OS MVS Initialization and
Tuning Reference for detailed information on the syntax and contents of the
CONFIGxx parmlib member.

CF MEMBER[(member-id)]

The parameters are:

MEMBER
The system is to use a CONFIGxx parmlib member to reconfigure available
processors, storage sections, and channel paths.
member-id
The identifier (xx) of the CONFIGxx member you want the system to use to
reconfigure the available processors, storage sections, and channel paths.

Chapter 4. MVS System Commands Reference 4-55

 CONFIG Command

This identifier may be any two alphanumeric characters. If you do not

specify member-id, the default member is CONFIG00.

Example

To reconfigure available processors, central and expanded storage, and channel

paths in the system to match the options in the CONFIGT3 parmlib member, enter:
cf member(t3)

Reconfiguring the System in Response to a Configuration Display

Use the following form of the CONFIG command before making any changes to the
system configuration, or to display the processors, Vector Facilities and Integrated
Cryptographic Features (ICRFs) attached to the processors, total amount of
storage, channel paths available to the system, and the online or offline status of
each channel path. (To obtain more information on storage, use the DISPLAY M
command.)

In response to this command, the system issues messages IEE521I and IEE522D.
Message IEE521I displays the reconfigurable resources available to the system,
including processors, Vector Facilities and ICRFs attached to the processors, total
amount of central storage, central storage elements, expanded storage elements,
and channel paths. If your processor complex is partitioned, message IEE521I
contains this information for one side. Respond to message IEE522D with the
processors, total amount of central and expanded storage, as well as channel paths
you want to bring online or take offline.

If the system is unable to display the resources available to the system, message
IEE521I indicates that the command was unsuccessful.

|
| CF {ONLINE|ON }[,L={a|name|name-a}]
| {OFFLINE|OFF}
|

ONLINE or ON
The system is to display the system configuration so that you can decide which
processors, Vector Facilities and ICRFs attached to the processors, central and
expanded storage elements, and channel paths you want to bring online. The
system brings online the processors, Vector Facilities and ICRFs attached to
the processors, storage elements, and channel paths you specify in response to
message IEE522D. If an ICRF is attached to a processor that is being brought
online and the Integrated Cryptographic Service Facility/MVS (ICSF/MVS) is
active, the system brings the ICRF online.
OFFLINE or OFF
The system is to display the system configuration so that you can decide which
processors, Vector Facilities and ICRFs attached to the processors, central and
expanded storage elements, and channel paths you want to take offline. The
system takes offline the processors, Vector Facilities and ICRFs attached to the
processors, storage elements, and channel paths you specify in response to
message IEE522D. If an ICRF is attached to a processor that is being taken
offline and the ICSF/MVS is active, the system takes the ICRF offline.
| L=a, name or name-a
The display area where the system is to display the system configuration. You
can specify the display area (a), console name (name), or both (name-a). If you
do not specify this option, the system displays the system configuration in the

4-56 z/OS V1R7.0 MVS System Commands

 CONFIG Command

first available display or message area of the console on which you entered the
command (unless you specify routing instructions for messages IEE521I and
IEE522D with the MSGRT command, as described later in this chapter).

Example 1

To check the channel paths available to the system before bringing any online,
enter:
cf online

When message IEE522D appears after the configuration display message, IEE521I,
reply with the channel paths you want to bring online.

Example 2

To check the available processors, central and expanded storage elements, and
channel paths in the system and the online or offline status of each, enter:
cf offline or cf online

When message IEE522D appears after the configuration display message, IEE521I,
reply with NONE.

Chapter 4. MVS System Commands Reference 4-57

CONTROL Command

CONTROL Command
Use the CONTROL command to control the screen display of MCS and SMCS
consoles. Table 4-8 summarizes the information that the CONTROL command
provides. Use it to access the pages on which you can find details about a
particular use of the CONTROL command.
Table 4-8. Summary of the CONTROL Command
Command: Topic:
CONTROL A Changing Out Of Line Display Area Specifications on page
4-59
CONTROL C Deleting Retained Action Messages on page 4-60
CONTROL C,D Halting the Printing or the Display of a Status Display on
page 4-62
CONTROL D Controlling Displays in Areas on page 4-62
CONTROL E Removing Information From the Screen on page 4-64
CONTROL M,AMRF Activating, Deactivating, or Displaying the Status of the
Action Message Retention Facility on page 4-65
CONTROL M,APPLID Setting the APPLID of the System on page 4-70
CONTROL M,GENERIC Setting or Turning Off the VTAM Generic Resource Name
for SMCS on page 4-71
CONTROL M,LOGLIM Changing or Displaying the Number of Allowed WTL
SYSLOG Buffers on page 4-66
CONTROL M,MLIM Changing or Displaying the Number of Allowed WTO and
WTOR Message Buffers on page 4-66
CONTROL M,ROUTTIME Changing the Time the System Waits for ROUTE
Command Responses on page 4-67
CONTROL M,RMAX Increasing the Maximum Number of Reply IDs on page
4-68
CONTROL M,UEXIT Changing or Displaying the Status of WTO Installation Exit
IEAVMXIT on page 4-69
CONTROL N,PFK Changing a PFK Definition on page 4-72
CONTROL Q Deleting Message Queues on page 4-74
CONTROL S Changing or Displaying Message Deletion and Format
Specifications on page 4-74
CONTROL T Changing or Displaying Time Intervals for Dynamic
Displays on page 4-78
CONTROL V,USE Changing the Operating Mode of a Console on page 4-79
CONTROL V,LEVEL Selecting the Message Levels for a Console on page 4-80

The following CONTROL commands have no effect on extended MCS consoles or

on system consoles, and are not valid for managing these consoles:
v KA
v K C,D
v KD
v KE
v K N,PFK
v KQ
v KS
CON=

4-58 z/OS V1R7.0 MVS System Commands

 CONTROL Command

SEG=
DEL=
RNUM=
RTME=
v K T
v K V,USE

| The system does not support the following variants of the CONTROL command at
| z/OS V1R7 and above:
| v KT
| v K D,H
| v K D,U

Many of the functions of the CONTROL command are controlled at IPL by

parameters in the CONSOLxx parmlib member. Accompanying the descriptions of
some operands on the CONTROL command are the corresponding parameters in
CONSOLxx. If you need more information about the parameters in CONSOLxx, see
z/OS MVS Planning: Operations and z/OS MVS Initialization and Tuning Reference.
See Chapter 3, Defining and Changing Console Characteristics, on page 3-1 for
more information about using the CONTROL command.

Scope in a Sysplex
The following table describes the conditions under which the CONTROL command
has sysplex scope. See Using Commands That Have Sysplex Scope on page
1-11 for an explanation of sysplex scope. If a command has All under Conditions,
then the command has sysplex scope under all circumstances and for all variations.
Table 4-9. Sysplex Scope for CONTROL Command
Command Conditions
CONTROL C,A All
CONTROL C,D Has sysplex scope only when you specify L=.
CONTROL M Has sysplex scope only when you do not specify MLIM,
UEXIT, LOGLIM, or APPLID.
CONTROL other Other parameters of CONTROL have sysplex scope only
when you specify L=.

Syntax
The syntax for each of the many variations of the CONTROL command is shown
immediately preceding its respective parameter list.

CONTROL or K

Changing Out Of Line Display Area Specifications

Use the CONTROL A command to change, remove, or examine out of line display
area specifications for any MCS or SMCS console in the system.

The AREA parameter on the CONSOLE statement in the CONSOLxx parmlib

member controls the display area specifications at IPL. z/OS MVS Planning:
Operations shows the maximum message area sizes for all devices that MVS
supports as consoles and the defaults for the AREA parameter.

Chapter 4. MVS System Commands Reference 4-59

 CONTROL Command

|
| K A[,nn[,nn]...][,L={name }]
| |,NONE
| |,REF
|

A The display area specifications are to be altered or referenced.

nn[,nn]...
The number of message lines in each display area. The first number (nn)
defines the bottom area of the screen; additional numbers (,nn) define
areas working toward the top of the screen. The minimum number of lines
in one display area is 4, the maximum is 99. The total number of all
specified lines cannot exceed the number of lines in the message area of
the screen. The maximum number of display areas that you can define is
11.
NONE
All out-of-line display area specifications will be removed for the specified
console.
REF
Displays, in the command input area, the size of out-of-line display areas
for the specified console. For example, if you enter K A,REF in the
command input area, and the size of the display area is 14, the system
displays K A,14 in the command input area.
| L= name
| The MCS or SMCS console whose display area is to be changed or
| referenced. If this operand is omitted, the console on which K A is entered
| is assumed.

Example

To define two display areas of 4 and 6 lines respectively, enter:

K A,4,6

Note: The CONTROL A command has no effect on extended MCS consoles or on

system consoles and is not valid for managing these consoles.

Deleting Retained Action Messages

Use the CONTROL C command to delete the outstanding action messages that the
action message retention facility (AMRF) has retained.

K C,{A|I|E|CE},{id|id-id[,id|id-id]...}

The parameters are:

C The system is to delete one or more action messages that AMRF has retained.
A The system is to delete one or more outstanding retained action messages
in any of the following categories:
v immediate action (descriptor code 1 or 2)
v eventual action (descriptor code 3)
v critical eventual action (descriptor code 11).

4-60 z/OS V1R7.0 MVS System Commands

 CONTROL Command

These messages are identified by number in response to the DISPLAY

R,LIST command.
I The system is to delete one or more outstanding immediate action
messages (descriptor code 1 or 2). These messages are identified by
number in response to the DISPLAY R,I command.
E The system is to delete one or more outstanding eventual action messages
(descriptor code 3). These messages are identified by number in response
to the DISPLAY R,E command.
CE
The system is to delete one or more outstanding critical eventual action
messages (descriptor code 11). These messages are identified by number
in response to the DISPLAY R,CE command.
id The one-to-ten-digit decimal message identification number of the message
to be deleted. This number is listed in response to the DISPLAY R
command (message IEE112I).
id-id
The one-to-ten-digit decimal message identification numbers of the
beginning and end of a range of messages to be deleted. The ending
number must be greater than or equal to the beginning number.
When a range of numbers is specified, all retained immediate action,
eventual action and/or critical eventual action messages with identification
numbers in the specified range are deleted.

Example 1

To delete a range of immediate action, eventual action, and critical eventual action
messages that have been retained with identification numbers from 0 to 110, enter:
CONTROL C,A,0-110

Example 2

Assume you have completed the requested action for three eventual action
messages, but the messages remain marked as outstanding. Use the DISPLAY R,E
command to get the identification numbers of the three messages (id1, id2, and id3)
and then use K C,E to delete the three messages.
DISPLAY R,E K C,E,id1,id2,id3

Example 3

Assume you have performed the requested immediate action, but the message is
still marked as outstanding. Use the DISPLAY R,I command to obtain the message
identification number and then issue CONTROL C,I to delete the message.
DISPLAY R,I
CONTROL C,I,id
Notes:
1. Specifying a large range of message identification numbers (more than 1000)
can result in system resources being held and performance being impaired.
2. When you delete retained messages, the requests relating to them may still be
outstanding.
3. When you specify a range, certain conditions are not flagged as errors that
would be errors if individual identification numbers were specified. For example,

Chapter 4. MVS System Commands Reference 4-61

 CONTROL Command

nonexistent message identification numbers that fall within the range do not
cause an error message. If you specify a nonexistent identification number by
itself, you receive an error message.

Halting the Printing or the Display of a Status Display

Use the CONTROL C,D command to halt the printing or display of the status:
v On a printer console that is not the hardcopy medium
v On a display console that does not have display areas

The CONTROL C,D command must be entered while the system is displaying or
printing the display.

|
| K C,D,id[,L={a|name|name-a}]
|

The parameters are:

C,D
The inline display, indicated by the id operand, is to be stopped. This command
is only valid on an MCS or SMCS console.
id The three-digit identification number of the status display you want to stop.
The identification number appears in the first line of the display.
| L=a, name, or name-a
| The name of the active MCS or SMCS (printer or display) console where
| the status display is to be stopped. If you do not specify the L= operand,
| then the K C,D,id command applies to the console from which the
| command is issued.

Example 1

To stop the status display, identification number 121, which is in progress in the
general message area of console CON21, enter:
k c,d,121,L=CON21

Note: The CONTROL C,D command has no effect on extended MCS consoles or
on system consoles and is not valid for managing these consoles.

Controlling Displays in Areas

CONTROL D,H and CONTROL D,U OPTIONS

| The CONTROL D,H and CONTROL D,U options of this command are not
| supported on systems at z/OS V1R7 and higher.

Use the CONTROL D command to control displays, message numbering, and the
PFK display line.

|
| K D[,N[,HOLD] ]
| |{,F|,H|,U}[,L={a|name-a}]
| |,PFK
|

4-62 z/OS V1R7.0 MVS System Commands

 CONTROL Command

The parameters are:

D Control what or how information is to be displayed on the screen. This
command is only valid for MCS and SMCS display consoles.
N Messages on the screen are to be consecutively numbered. The operator
uses these numbers as references to delete messages from the screen
using the K E,nn command. (For very large screen sizes the K D,N
command will only number the first 99 rows on the screen. All subsequent
lines will contain AA in the number field.) The numbers are removed from
the screen when the operator deletes a message or performs a cancel
action. (The K E,nn command cannot delete messages after line 99 on the
screen.) This option is not valid when:
v The console is in wrap mode; the system issues message IEE290I.
v The console is in roll or roll-deletable mode; the system issues message
IEE158I.
HOLD
In conjunction with the N operand, HOLD specifies that the system
display consecutive numbers for each message on the screen and
renumber messages after each message deletion that the operator
performs.
F The next frame of a status display is to be displayed. When you do not
specify an area, the oldest area on the screen is scrolled. This option is not
valid when there is no status display on the console; the system issues
message IEE158I.
H The updating of a dynamic status display is to be suppressed. This option
is not valid when there is no dynamic status display on the console; the
| system issues message IEE158I. The H option is not supported on
| systems at z/OS V1R7 and higher.
U The updating of a dynamic status display is to be resumed. This option is
not valid when there is no dynamic status display on the console; the
| system issues message IEE158I. The U option is not supported on
| systems at z/OS V1R7 and higher.
| L=a or name-a
Specifies the display area (a), console name (name), or both (name-a)
where the display will appear.

The L= operand only applies to the F, H, and U parameters.

PFK
Specifies that the numbers of the program function keys (PFKs) designated
for command entry are to be displayed in the PFK display line. This
operand applies only to display consoles that have the PFK function and
support the PFK display line (for example, 32772).

Example

To display the next frame of a status display, enter:

k d,f

Note: The CONTROL D command has no effect on extended MCS consoles or on

system consoles and is not valid for managing these consoles.

Chapter 4. MVS System Commands Reference 4-63

 CONTROL Command

Removing Information From the Screen

Use the CONTROL E command to remove various types of messages from the
screen or to cause message numbers to be deleted.

|
| K E[,nn ]
| |,nn,nn
| |,SEG
| |,F
| |,N
| |,PFK
| |,D[,L={a|name|name-a}]
|

The parameters are:

E Messages are to be removed from the screen.
nn The system is to remove a single (nn) message or a range (nn,nn) of
deletable messages from the screen. The value of nn must be a decimal
number from 01 to 99. The K E,nn command cannot delete messages after
line 99 on very large screen sizes. A deletable message is any message
that is either a WTOR or a WTO message issued without descriptor code 1,
2, 3, or 11.

Note: Do not use this command to try to remove a range of non-deletable

messages; you can remove only one non-deletable message at a
time.
SEG
Deletable messages in the predefined message segment are to be removed
from the screen. A deletable message is any message that is either a
WTOR or a WTO message issued with descriptor code 1,2,3, or 11.
F All flagged messages (messages marked with a vertical or horizontal bar in
position 3) are to be removed from the screen.
N Removes the numbers preceding the messages displayed on the screen.
The messages on the screen were consecutively numbered by the K D
command.
D Specifies that a status display is to be deleted.
| L=a, name, or name-a
For the D operand, specifies where the specified action is to take place.
You can specify the display area by area (a), console name (name), or
both (name-a). When this keyword is not specified, the oldest area on
the screen is deleted.
PFK
Specifies that the numbers are to be erased from the program function key
(PFK) display line. This operand applies only to display consoles that have
the PFK function and support the PFK display line (for example, 32772);
the system issues message IEE158I for all other consoles.

Example 1

To delete the message at line 10, which appears on the screen as follows:
10 IEE334I HALT EOD SUCCESSFUL

4-64 z/OS V1R7.0 MVS System Commands

 CONTROL Command

enter:
K E,10

Example 2

To delete the non-action messages from a segment of messages, enter:

K E,SEG or K E

Example 3

To delete the non-action messages on lines 4-10, enter:

K E,4,10

Example 4

To delete all flagged messages (messages marked with a vertical or horizontal bar
in position 3), enter:
K E,F

Note: The CONTROL E command has no effect on extended MCS consoles or on

system consoles and is not valid for managing these consoles.

Activating, Deactivating, or Displaying the Status of the Action

Message Retention Facility
Use the CONTROL M,AMRF command to change or display the status of the action
message retention facility. You can enter the command from the master console, or
from a console with master authority.

The AMRF parameter on the INIT statement in the CONSOLxx parmlib member
controls whether or not the system starts the action message retention facility at
IPL. If the AMRF parameter is not coded, the action message retention facility is
active. Use the CONTROL M command to stop or restart the facility once the
system is active.

The syntax of the command is as follows:

K M[,AMRF={Y|N}]
|,REF

The parameters are:

M Indicates message processing by the message retention facility.
AMRF=
The status of the action message retention facility is to be modified for all
systems in the sysplex.
Y The action message retention facility is to become active.
N The action message retention facility is to be deactivated.
REF
Displays the current values of all the operands on the K M command.

Example

Chapter 4. MVS System Commands Reference 4-65

 CONTROL Command

To activate the action message retention facility, enter:

K M,AMRF=Y

Changing or Displaying the Number of Allowed WTL SYSLOG Buffers

Use the CONTROL M,LOGLIM command to change or display the number of
allowed WTL (write-to-log) SYSLOG buffers. You can enter the command from
consoles with master authority.

The LOGLIM parameter on the INIT statement in the CONSOLxx parmlib member
controls the number of WTL buffers. If the LOGLIM parameter is not coded, the
number of WTL buffers is 1000.

The syntax for the command is:

K M[,LOGLIM={nnnnnn|0}]
|,REF

The parameters are:

M Indicates message processing by the message retention facility.
LOGLIM=nnnnnn
| The maximum number of outstanding WTL requests that the system can hold in
| buffers on the system, where nnnnnn can be a decimal number from 1000 to
| 999999. In a sysplex, the WTL SYSLOG buffers hold messages that the system
| has not yet presented to the hard-copy medium in the sysplex.

| Note: When you set LOGLIM=999999 you allocate over 100 megabytes of
| CSA storage for WTL SYSLOG buffer storage. Be careful that WTL
| SYSLOG buffer storage does not hamper your systems performance.
LOGLIM=0
All outstanding WTL buffer storage is freed by the system log task.

Note: Use this command value only at the direction of the system programmer.
It results in the potential loss of messages sent to hard-copy.
REF
Displays the current values of all the operands on the K M command. Unless
you specifically change it, the LOGLIM value that the system displays is the
value that was specified on the INIT statement in CONSOLxx parmlib member.

Example

To allow 4000 WTL message buffers, enter:

K M,LOGLIM=4000

Changing or Displaying the Number of Allowed WTO and WTOR

Message Buffers
Use the CONTROL M,MLIM command to change or display the number of allowed
WTO (write-to-operator) or WTOR (write-to-operator-with-reply) message buffers.
You can enter the command from consoles with master authority.

4-66 z/OS V1R7.0 MVS System Commands

 CONTROL Command

The MLIM and RLIM parameters on the INIT statement in the CONSOLxx parmlib
member control the number of WTO and WTOR buffers. If the MLIM or RLIM
parameters are not coded, the number of WTO buffers is 1500, and the number of
WTOR buffers is 10.

The syntax for the command is:

K M[,REF|[,MLIM=nnnn][,RLIM=mmmm]]

The parameters are:

M Indicates message processing by the message retention facility.
MLIM=nnnn
The maximum number of WTO message buffers to be allowed in the system,
where nnnn can be a decimal number from 20 to 9999. The WTO buffers hold
the WTO messages that the system has not yet displayed at the eligible MCS
and SMCS consoles in the sysplex.
RLIM=mmmm
The maximum number of outstanding WTOR messages that the system or
sysplex can hold in buffers, where mmmm can be a decimal number from 5 to
9999. Each WTOR buffer holds a WTOR message that the system or sysplex
has displayed and has not received a response to. The maximum upper limit is
set by the RMAX keyword on the DEFAULT statement in CONSOLExx.
REF
Displays the current values of all the operands on the K M command.

Example

Assuming RMAX is set to 9999: To allow the maximum number of WTO message
buffers and WTOR message buffers, enter:
K M,MLIM=9999,RLIM=9999

Changing the Time the System Waits for ROUTE Command Responses
Use the CONTROL M,ROUTTIME command to display or change the maximum
amount of time the ROUTE *ALL, ROUTE systemgroupname, or ROUTE *OTHER
command waits for a response from each system in the sysplex before aggregating
the responses. ROUTTIME applies to any ROUTE command with the *ALL or
systemgroupname operand when issued from any system in a sysplex.

The syntax of the command is as follows:

K M[,ROUTTIME=nnn ]
|,REF

The parameters are:

ROUTTIME=nnn
Dynamically changes the maximum number of seconds the ROUTE *ALL or
ROUTE systemgroupname command waits for command responses from each

Chapter 4. MVS System Commands Reference 4-67

CONTROL Command

system before aggregating the responses. (If not specified in CONSOLxx, the
IBM-supplied default value is 30 seconds.) The nnn value is a decimal number
from 0-999.
If nnn is zero, command responses are not aggregated. The change applies
across the sysplex, and affects ROUTE commands issued after the CONTROL
command is processed.
If the timeout value (T= operand) is specified on a ROUTE *ALL or ROUTE
systemgroupname command, the value of the T= operand overrides the value
then in effect on the system.
REF
Displays the current values of all the operands on the K M command.

Example 1

To change the maximum amount of time ROUTE *ALL or ROUTE

systemgroupname waits for command responses to 45 seconds, enter:
K M,ROUTTIME=45

Example 2

To display the maximum amount of time ROUTE *ALL or ROUTE

systemgroupname waits for command responses, enter:
K M

Increasing the Maximum Number of Reply IDs

Use the CONTROL M,RMAX command to display or dynamically increase the
maximum number of reply IDs.

The syntax of the command is as follows:

K M[,RMAX=nnnn ]
|,REF

The parameter is:

RMAX=nnnn
Dynamically increase the maximum number of reply IDs, where nnnn is a
decimal number from 99 to 9999.

Note: The value for RMAX also determines the size of the reply ID displayed in
the message text. For example, specifying an RMAX of 999 means that
all WTOR messages have a 3-character reply ID.
You can increase the value of RMAX only in a system running in local mode or
in a sysplex whose couple data set supports more than eight systems.
The new value of RMAX must be greater than the previous value of RMAX.
REF
Displays the current values of all the operands on the K M command.

Example

To increase the maximum number of reply IDs to 200, enter:

4-68 z/OS V1R7.0 MVS System Commands

 CONTROL Command

K M,RMAX=200

Changing or Displaying the Status of WTO Installation Exit IEAVMXIT

Use the CONTROL M,UEXIT command to change or display the status of the WTO
installation exit IEAVMXIT. This exit receives control when the system issues a
WTO message unless your installation names another WTO installation exit routine
for the message. To learn what messages are currently processed by IEAVMXIT,
issue the DISPLAY MPF command.

The UEXIT parameter on the INIT statement in the CONSOLxx parmlib member
controls whether IEAVMXIT is active at IPL. If the UEXIT parameter is not coded,
IEAVMXIT will be activated, if it is installed. If IEAVMXIT is not installed, the system
will IPL with UEXIT=N.

The syntax of the command is:

K M[,UEXIT={Y|N}]
|,REF

The parameters are:

UEXIT=
The status of the general WTO installation exit IEAVMXIT is to be changed.
Y The general user exit routine IEAVMXIT is to become active. If IEAVMXIT is
already active and you want a new copy, deactivate IEAVMXIT, refresh the
library lookaside (LLA), and then reactivate IEAVMXIT.
N The general user exit routine IEAVMXIT is to become inactive.
REF
Displays the current values of all the operands on the K M command.

Example 1

To activate the general WTO installation exit routine IEAVMXIT, enter:

K M,UEXIT=Y

Example 2

To load a new copy of the general WTO installation-exit routine IEAVMXIT, first
enter:
K M,UEXIT=N

to deactivate the current copy. Then enter:

MODIFY LLA,REFRESH

After you receive notification that the library lookaside (LLA) is refreshed, enter:
K M,UEXIT=Y

to activate the new copy.

Chapter 4. MVS System Commands Reference 4-69

CONTROL Command

Displaying the SMCS APPLID of the current system and VTAM generic
resource name for SMCS
Use the CONTROL M,REF command to display the SMCS APPLID of the current
system and VTAM generic resource name for SMCS.

If either of these values has been changed by a prior CONTROL M command, but
SMCS has not yet been recycled using the VARY NET,INACT and VARY NET,ACT
commands to deactivate and restart the SMCS application, CONTROL M will show
the new APPLID and GENERIC, even though SMCS will be using the old APPLID
and GENERIC. The DISPLAY CONSOLES,SMCS command can be used to display
the APPLID and GENERIC in use on each system in the sysplex, as well as the
APPLID and GENERIC set by the CONTROL M command.

If the system is in XCFLOCAL or MONOPLEX mode, the GENERIC keyword will

not be displayed. If the system does not have an APPLID in effect, the APPLID
keyword will not be displayed.

The syntax of the command is:

K M[,REF]

The parameters are:

REF
Displays the current values of all the operands on the K M command.

Setting the APPLID of the System

Use the CONTROL M,APPLID command to set the APPLID of the system where it
is issued. If there is not an APPLID in effect on the system, either because an
APPLID was not specified in CONSOLxx, or because the APPLID was invalid or in
use by another system during this systems IPL, this command is rejected.

For the new APPLID to take effect, after issuing the CONTROL M command to
change it, the VARY NET,INACT,ID=oldapplid[,I or ,F] command must be issued to
deactivate SMCS, followed by the VARY NET,ACT,ID=newapplid command to
activate SMCS using the new APPLID. This is sometimes referred to as recycling
the APPLID or recycling SMCS. Until SMCS is recycled, the old APPLID value is
still in use. Message IEE821E is issued to reflect the need to recycle SMCS.

The syntax of the command is:

K M,APPLID=aaaaaaaa

The parameters are:

APPLID=aaaaaaaa
Sets the APPLID of the system where it is issued.
Value Range: Is from 2 to 8 characters. The first character must begin with the
letters A through Z or with a #, $, or @; the remaining characters can be A
through Z, 0 through 9, or #, $, or @.

4-70 z/OS V1R7.0 MVS System Commands

 CONTROL Command

Example:
Systems SY1 and SY2 are in a sysplex. System SY1 is using APPLID SMCS1,
and SY2 is using APPLID SMCS2. To change SY1s APPLID to SMCSA, enter:
K M,APPLID=SMCSA

to change the APPLID. However, SY1 will continue to use SMCS1 as its
APPLID until SMCS is recycled with the following commands:
VARY NET,INACT,ID=SMCS1,I
VARY NET,ACT,ID=SMCSA

Setting or Turning Off the VTAM Generic Resource Name for SMCS
Use the CONTROL M,GENERIC command to set or turn off the VTAM generic
resource name for SMCS in the sysplex.

If the system is in XCFLOCAL or MONOPLEX mode, this command is rejected.

For the updated GENERIC value to take effect, after issuing the CONTROL M
command to change it, the VARY NET,INACT,ID=applid[,I or ,F] command must be
issued to deactivate SMCS, followed by the VARY NET,ACT,ID=applid command to
reactivate SMCS using the new GENERIC value. This is sometimes referred to as
recycling the APPLID or recycling SMCS. Each SMCS application in the sysplex
will continue to use the old GENERIC value until it is recycled. It is not necessary to
recycle all of the SMCS applications at the same time, however, this may result in
some systems using the old value of GENERIC and others using the new value of
GENERIC until all SMCS applications in the sysplex are recycled.

The syntax of the command is:

K M[,GENERIC={aaaaaaaa}]
|{*NONE*}

The parameters are:

GENERIC=
aaaaaaaa
Sets the VTAM generic resource name for SMCS in the sysplex.
*NONE*
Turns off the VTAM generic resource name for SMCS in the sysplex.

Example:

Systems SY1 and SY2 are in a sysplex. System SY1 is using APPLID SMCS1,
and SY2 is using APPLID SMCS2, and the current GENERIC is SMCSX. To
change the GENERIC to ANYSMCS, on either SY1 or SY2, enter:
K M,GENERIC=ANYSMCS

SY1 and SY2 will continue to use SMCSX as the GENERIC until SMCS is
recycled on each system. To recycle SMCS on SY1, issue the following
commands:
VARY NET,INACT,ID=SMCS1,I
VARY NET,ACT,ID=SMCS1

Chapter 4. MVS System Commands Reference 4-71

 CONTROL Command

To recycle SMCS on SY2, issue the following commands:

VARY NET,INACT,ID=SMCS2,I
VARY NET,ACT,ID=SMCS2

Changing a PFK Definition

Use the CONTROL N,PFK command to change the definition of a PFK on a
particular console or to assign a PFK table to a particular console. The set of
commands associated with the PFKs on your console resides in a PFK table in a
PFKTABxx parmlib member.

A PFK command that you assign to a PFK by using the CONTROL N,PFK
command is not associated with the PFK when you bring the console online again.
To have a command associated with a PFK when you bring a console online, it
must be defined in the appropriate PFK table in PFKTABxx. See Defining PFKs
Using the CONTROL Command on page 3-19.

Use the following form of the CONTROL command to define commands for
program function keys (PFKs) or assign a PFK table.

|
| K N,PFK={(nn1{,CMD=text[;text]...})[,CON={Y|N}] }
| { {,KEY=nn2[,nn2]... } }
| { }
| {nnnnnnnn[,L=name] }
|

The parameters are:

N,PFK
A PFK command definition is to be altered.
nn1
The number of the PFK being defined. The nn1 value must be the number of a
PFK designated for command entry at system installation
CMD
The text of one or more commands is to be associated with PFK nn1.
text[;text]...
The text of the operators commands to be associated with PFK nn1. Up to
110 characters can be included within the quotes. If more than one
command is to be associated with a PFK, the commands must be
separated by a semicolon. Do not put a semicolon after the last command.
Text characters can be entered in upper or lower case; the system converts
all characters to uppercase. A command that must be entered lowercase,
such as a reply to a WTOR, cannot be entered using the PFK command
entry function.

Note: Text characters should not contain sensitive or secure data (such as
passwords).
KEY
The commands associated with other PFKs are to be associated with nn1.
nn2[,nn2]...
The number(s) of the PFK whose commands are to be associated with PFK
nn1. Up to 54 key numbers (numbers can be repeated) can be included in
the list. Separate key numbers with a comma.

4-72 z/OS V1R7.0 MVS System Commands

 CONTROL Command

Note: You cannot nest the lists of keys. That is, a PFK defined as a list of
PFKs cannot be included in a list of keys assigned to another PFK.
For example, if PFK 5 is associated with a list of keys (such as
KEY=3,4), and you attempt to associate PFK 6 with a list of keys
that includes PFK 5 (such as KEY=1,2,5), the system rejects the
request.
CON
Specifies whether conversational mode of command entry is in effect.
Y Conversational mode of command entry is to be in effect.
N Conversational mode of command entry is not to be in effect
(non-conversational mode of command entry is to be in effect). If CON
is not specified, CON=N is assumed.
nnnnnnnn
The name of the PFK table that contains the commands that define the
PFKs for a console.
| L=name
The console whose PFKs are to be defined by the PFK table you
specify. The issuing console is the default.

Example 1

To associate a START GTF command with PFK 5, enter:

K N,PFK=(5,CMD=S GTF,285),CON=N

Example 2

To associate a START READER and a START WRITER command with PFK 5,

enter:
K N,PFK=(5,CMD=S RDR,001;S XWTR,292),CON=N

Example 3

If PFK 3 is associated with commands S RDR,001 and S XWTR,292, and PFK 4 is

associated with the command S
GTF,MODE=INT,BUF=387,TIME=YES,DEBUG=YES, you can associate all three of
these commands with PFK 5 by entering:
K N,PFK=(5,KEY=3,4),CON=Y

The commands associated with PFK 5 are now S RDR,001; S XWTR,292, and S
GTF,MODE=INT,BUF=387,TIME=YES,DEBUG=YES, in that order.

Example 4

To remove a definition previously set for PFK 5, leaving PFK 5 undefined, enter:
K N,PFK=(5,CMD=)

Example 5

To assign the commands in the table PFK22 to cons8, enter:

K N,PFK=PFK22,L=CONS8

Note: The CONTROL N,PFK command has no effect on extended MCS consoles
or on system consoles and is not valid for managing these consoles.

Chapter 4. MVS System Commands Reference 4-73

 CONTROL Command

Deleting Message Queues

Use this command to delete messages that are queued to an MCS or SMCS
console. It affects only messages currently on the consoles queue. Subsequent
messages are queued as usual. This command is generally, though not exclusively,
for use in error situations.

The command gives you more control over MCS and SMCS console message
queues. If there is a WTO buffer shortage, you can delete the messages to speed
up console processing or alleviate storage problems. You might need to issue the
command several times to clear the console of messages.

Note: This CONTROL command is not valid for extended MCS consoles or
extended MCS console message queues.

The kinds of messages that are deleted are:

v Action messages.
v All in-line messages queued for a particular console.
v WTOR messages and unconditional messages.

The kinds of messages that are not deleted are:

v Out-of-line messages. You can delete these with K E,D.
v Messages queued to SYSLOG.

The syntax is:

|
| K Q[,L=name]
|

Q The CONTROL command is to delete a consoles message queue.

| L=name
The name of the console whose message queue is to be deleted. If this
operand is omitted, the message queue of the console from which the K Q
command is entered is deleted.

Example 1

To delete any messages on the issuing full-capability consoles queue, enter:

K Q

Example 2

To delete messages queued on console CON2, enter:

K Q,L=CON2

Changing or Displaying Message Deletion and Format Specifications

Use the CONTROL S command to change console specifications or to display the
console specifications currently in effect. Any changes you make with the
CONTROL S command do not exist when you IPL the system the next time.

The following parameters on the CONSOLE statement in the CONSOLxx parmlib

member control, at IPL, the same console specifications as the CONTROL S
command. The system defaults are:

4-74 z/OS V1R7.0 MVS System Commands

 CONTROL Command

CON(N) Conversational or nonconversational mode

DEL(RD) Message deletion mode
MFORM(M) Format of messages
RNUM(5) Maximum number of messages included in one message roll
RTME(2) Number of seconds between message rolls
SEG Number of lines in the message area that the CONTROL E,SEG
command deletes.

The complete syntax for the CONTROL S command is:

|
| K S[,REF ]
| |
| |[,CON={Y|N}][,SEG=nn][,DEL={Y|N|R|RD|W}]
| [,RNUM=nn][,RTME=nnn][,MFORM=(option[,option]...)]
|
| [,L=name]
|

S The current console specifications are to be temporarily altered or referenced.

CON=
Conversational message deletion is requested or cancelled.
Y Requests conversational message deletion.
N Cancels conversational message deletion. (non-conversational message
deletion is to go into effect).

Note: The CONTROL S,CON= command has no effect on extended MCS

consoles or on system consoles and is not valid for managing these
consoles.
REF
The current console specification values are to be displayed in the entry area in
CONTROL command form.
SEG=nn
The size of the message segment is to be altered, where nn specifies the
number of lines to include in the segment of messages deleted when a
CONTROL E,SEG command is entered. The CONTROL S,SEG= command can
accept a maximum value of 99 or the number of lines on the screen, whichever
is smaller.

Note: The CONTROL S,SEG= command has no effect on extended MCS

consoles or on system consoles and is not valid for managing these
consoles.
DEL=
The message deletion mode is to be changed.
Y Automatic mode of message deletion is to go into effect. That is, all flagged
messages are removed from the screen whenever the screen becomes full.
N Automatic mode of message deletion is cancelled. Messages must be
removed manually.

Chapter 4. MVS System Commands Reference 4-75

CONTROL Command

R Roll mode is to go into effect. That is, a specified number of messages

(determined by RNUM) roll off the screen each specified interval
(determined by RTME).
RD
Roll-deletable mode of message deletion is to go into effect. That is,
messages roll off as with roll mode, except that the action messages
accumulate at the top of the screen.
W Wrap mode is to go into effect. When the screen is full, the next message
overlays the message at the top of the screen and subsequent messages
continue overlaying older messages down the screen. The separator line,
with the same highlighting attribute as the warning line, moves with the new
messages and includes the count of the undisplayed messages. WTORs
and action messages are also overlaid.

Note: The CONTROL S,DEL= command has no effect on extended MCS

consoles or on system consoles and is not valid for managing these
consoles.
RNUM=nn
The number of lines in the message roll. The CONTROL S,RNUM=nn
command can accept a value of nn from 1 to 99 (decimal) or the number of
lines on the screen, whichever is smaller, as the number of lines in the
message area.

Note: The CONTROL S,RNUM=nn command has no effect on extended MCS

consoles or on system consoles and is not valid for managing these
consoles.
RTME=nnn
The time interval in seconds between message rolls. The nnn value can be any
decimal number from 1 to 999, 1/2, or 1/4. This time interval sets the MCS and
SMCS screen refresh rate. Messages will be displayed each nnn seconds in R,
RD, and W modes.
Notes:
1. The value for 3290 consoles should be 1 or higher.
2. The CONTROL S,RTME=nnn command has no effect on, and is not valid
for managing, extended MCS consoles or system consoles.
MFORM=(option[,option]...)
The format of messages sent to a console is to be changed. You can control
whether the text of each message (including those from JES2 and JES3) is
accompanied by:
v a time stamp
v the name of the system that issues the message
v the jobname or job id of the issuer of the message
The format of a message that includes all MFORM options is:
Time stamp System name Jobname/id Message text

You can enter more than one of the options. If you do, place parentheses
around the list of options and separate them with commas. The system displays
the information that accompanies the message text in the order described,
regardless of the order of the options you specify on the MFORM operand.
option can be any of the following:
T Requests that each message appear with a time stamp.

4-76 z/OS V1R7.0 MVS System Commands

 CONTROL Command

S Requests that each message appear with the name of the system that
sent the message.
J Requests that each message appear with the job name or job ID
associated with this message.

Note: This value is initially the job name or ID of the issuer of the
message, but either the issuer or subsystem code can change
the value. For example, messages that JES issues often change
the initial value from the JES name/id to that of the job the
message is describing.
M Requests that the text of each message appear without a time stamp,
the job name/job ID of its issuer, or the name of the system that sent
the message. The text of the message is displayed whether or not you
use this operand. At IPL, if the MFORM operand in the CONSOLxx
parmlib member is not coded, the system displays the message text
without time stamp, system name, or job name/ job id.

Note: M is the default MFORM option for extended MCS consoles. To

change the default value for the extended MCS consoles use the
RACF command, ALTUSER userid
OPERPARM(MFORM(T,S,J,M,X)). See z/OS Security Server
RACF Command Language Reference for more information. The
default for MCS and SMCS consoles can be changed with the
CONTROL command.
X Requests not to prefix messages flagged as exempt from sysname and
jobname formatting with a sysname and jobname field when the S
and/or J operands are specified. X does not affect the T operand.
| L= name
The console this command is to affect. Before using the L operand, realize:
v You can specify this operand to change the specifications of another console
only from a console with at least CONS command group authority.
| v For name, you can specify the name of a full-capability console only from a
| console with master authority or a pseudo-master console.
| v For name, You cannot specify the name of a status display console.
| v If you specify the name of a message stream console, you cannot specify
| DEL=Y or DEL=N, CON=N; if the name is for a non-display console, you
| cannot specify any operand other than MFORM.

Example 1

To set SEG equal to 10 lines, enter:

K S,SEG=10

Example 2

To cancel roll mode on console CON4, enter:

CONTROL S,DEL=N,L=CON4

In this case, you must delete messages manually.

Example 3

To determine the current value of SEG, enter:

Chapter 4. MVS System Commands Reference 4-77

 CONTROL Command

K S,REF or K S

Example 4

To place a console in wrap mode, enter:

K S,DEL=W

Example 5

To display all messages on the full-capability console named CON5 with time
stamps and the job names/job IDs of their issuers, enter the following command
from the master console:
K S,MFORM=(M,T,J),L=CON5
Notes:
1. The system displays the time stamps and the job names/job IDs in the order
described earlier.
2. Whether or not you specify the option M, the system displays the text of the
message.

Changing or Displaying Time Intervals for Dynamic Displays

CONTROL T NO LONGER SUPPORTED

| The CONTROL T command is not supported on systems at z/OS V1R7 and
| higher.

Use the CONTROL T command to change the time interval or to see the current
time interval used for updating dynamic displays on a console.

The UTME parameter on the CONSOLE statement in the CONSOLxx parmlib

member controls the time interval value at IPL. If the UTME parameter is not coded,
the time interval is 30 seconds. The CONTROL T command is not valid for
extended MCS consoles.

The syntax for the CONTROL T command is:

K T[,REF ][,L=name ]
|,UTME=nnn

The parameters are:

T The time interval for updating status displays is to be changed or displayed.
REF
Displays the current value of the CONTROL K T,UTME operand.
UTME=nnn
The time interval for updating status displays in seconds, where nnn can be
any decimal number from 10 to 999.
L= name
The console where the time interval updating or change is to occur.

4-78 z/OS V1R7.0 MVS System Commands

 CONTROL Command

Notes:
1. If the issuing console is not a display console, the system responds to the
CONTROL T,REF command with the following:
IEE922I K T,UTME=nnn
The current time interval is indicated by nnn. You can change the time interval
by entering another CONTROL T,UTME command.
2. In general, if there is a dynamic display in progress when you change the time
interval, the new interval does not take effect until the interval in progress
elapses. If a K D,U command is directed to the display area, however, the new
interval takes effect immediately.
3. The CONTROL T command has no effect on extended MCS consoles or on
system consoles and is not valid for managing these consoles.

Changing the Operating Mode of a Console

Use the CONTROL V,USE command to change the operating mode of a console.

The USE parameter on the CONSOLE statement in the CONSOLxx parmlib

member controls the operating mode of a console at IPL. If the USE parameter is
not coded and the console is a display console, the consoles operating mode is
full-capability. Use the K V,USE command to change the operating mode for MCS
consoles. You cannot change the operating mode for SMCS or extended MCS
consoles.

The syntax for the CONTROL V command is:

|
| K V[,REF ][,L=name ]
| |
| |,USE={FC|SD|MS}[,CMDSYS={sysname|*}]
|

The parameters are:

USE=
The operating mode of a console is to be changed.
FC
The console is to be changed to full-capability mode (input/output
capability).
SD
The console is to be changed to output-only for presentation of status
displays.
MS
The console is to be changed to output-only for presentation of messages
other than status displays.

Note:
1. If you issue the VARY command to take the console offline and then
bring the console online, the console will resume the operating mode
in effect when the console was taken offline.
2. K V USE=SD and K V USE=MS operating modes are not valid for
SMCS consoles.

Chapter 4. MVS System Commands Reference 4-79

 CONTROL Command

REF
Displays the current value of the CONTROL V,USE operand.
CMDSYS
Indicates the system where all commands will be sent for processing.
sysname
The system where all commands are to be sent. If this keyword is not
specified or is incorrect, the commands are processed on the system where
you issue the command.
* The system where you issue the command.
| L= name
The name of the console where the specified action is to take place.

Note: The CONTROL V,USE command has no effect on extended MCS consoles
or on system consoles and is not valid for managing these consoles.

Example

To direct all commands issued from this console to processor SY2, enter:
K V,CMDSYS=SY2

Selecting the Message Levels for a Console

Use the CONTROL V,LEVEL command to specify the message levels for messages
that are to be displayed at a console.

The LEVEL parameter on the CONSOLE statement in the CONSOLxx parmlib

member controls the message levels for the console at IPL. If the LEVEL parameter
is not coded, the system sends all messages, including broadcast messages, to the
console.

The syntax for the command is:

|
| K V[,REF ][,L=name ]
| |
| |,LEVEL=(type[,type]...)
|

The parameters are:

LEVEL=(type[,type]...)
The message levels for a console are to be changed. The following operands
specify which messages are to be displayed at the console. You can enter more
than one of the following operands. If you do, place parentheses around the list
of operands and separate them with commas. type can be any of the following:
ALL The system is to display all messages routed to the console,
including broadcast messages.
ALL,NB The system is to display all messages routed to the console,
except for broadcast messages.
CE Critical eventual action messages (descriptor code 11) are to be
displayed
E Eventual action messages (descriptor code 3) are to be
displayed

4-80 z/OS V1R7.0 MVS System Commands

 CONTROL Command

I Immediate action messages (descriptor codes 1 and 2) are to

be displayed
IN Informational messages are to be displayed
NB Broadcast messages are not to be displayed.
R Write-to-operator with reply (WTOR) messages are to be
displayed.
UNCOND The system is to execute this command even though it means
broadcast and informational messages with certain routing
codes will not be assigned to any console. Use this operand if
you want broadcast and certain informational messages to be
sent only to the hardcopy medium.
Notes:
1. If you dont specify NB, your console receives broadcast messages.
2. If a WTOR or action message is not directed to any console, the message
is logged. It can be retrieved and displayed at a console using the DISPLAY
REQUESTS command.
3. If a message is directed to a specific console, it appears there regardless of
the message level of the console.
4. If you specify a second K V,LEVEL command, the K V,LEVEL command in
effect is cancelled.
5. If you specify only one message type on the LEVEL operand, you can omit
the parentheses.
REF
Displays the current value of the CONTROL V,LEVEL operand.
| L= name
The name of the console where the specified action is to take place. The
issuing console is the default.

Example 1

To route only informational and broadcast messages to console CON20, enter:

K V,LEVEL=IN,L=CON20

Example 2

To route WTOR, immediate action, and broadcast messages to the issuing console,
enter:
K V,LEVEL=(R,I)

Example 3

To route all messages except broadcast messages to the issuing console, enter:
K V,LEVEL=(ALL,NB)

To suppress all broadcast and informational messages destined for the issuing
console, enter:
K V,LEVEL=(NB,UNCOND)

Chapter 4. MVS System Commands Reference 4-81

DEVSERV Command

DEVSERV Command
Use the DEVSERV command to request a display of the status of DASD and tape
devices. The response is a display of basic status information about a device, a
group of devices, or storage control units, and optionally can include a broad range
of additional information. You can display:
v Device number
v Device type
v Logical mode of the device
v Number of data sets allocated on the volume
v Volume serial label
v Channel path ID
v Status of the path
v Status of an SMS-managed device
Volume status
Storage group name
Storage group status
v Control unit type and model
v Control unit serial number
v Device capacity, in cylinders
v Device extended function status
v Unit control block (UCB) device type information
v Help text, when you request it
v The following, if the device belongs to the DASD storage subsystem:
Real device type (if what is shown is an emulated device type)
Control unit type and model (or emulated control unit type and model if the
real and emulated control units are not the same)
Subsystem ID for this storage subsystem
Cache fast write state
Track caching state
DASD fast write state
State of pinned data
State of dual copy, PPRC, or SPARing -- if there is any
Address of the other device in a dual copy pair
Channel subsystem device address
Subsystem internal logical device address
An indication if the device extended function status information is inconsistent
between MVS control blocks and the storage subsystem
An indication if the defined (UCB) device type is inconsistent with the real
device type
Optionally, the total number of cylinders for each unique track format (3380,
3390, and 9345) for all of the devices within the scope of the request
v The following, if the device belongs to a tape library:
Device type equivalent to DTYPE from the DS P command
Device status indicating online / offline and ready / not ready
Device type and model
Device serial number
Library identification number
An indication if the defined (UCB) device type is inconsistent with the real
device type
You can also use several options of the DEVSERV command:

4-82 z/OS V1R7.0 MVS System Commands

 DEVSERV Command

| v You can compare the DEVSERV PATHS command with the DISPLAY U and
| DISPLAY M commands by referring to Displaying the Status of Devices and
| Availability of Paths on page 1-10.
| v Using the DEVSERV QDASD option
| v Using the DEVSERV QTAPE option
| v Using the DEVSERV QLIB option

Using the DEVSERV QDASD option

Use the QDASD option of the DEVSERV command to validate MVS storage
resident control blocks for extended function status with data acquired directly from
the storage subsystem. Optionally, you can obtain a hexadecimal display of:
v the following device-related MVS system control blocks:
Unit control block (UCB), UCB prefix, and UCB common extension
Device class extension (DCE)
Storage subsystem control block (SSSCB)
Device performance characteristics table (DPCT)
v and the following data buffers acquired directly from the device:
Read device characteristics (RDC) data
Read configuration data (RCD) data
Sense subsystem status (SNSS) data

Using the DEVSERV QTAPE option

Use the QTAPE option of the DEVSERV command to request a hexadecimal
display of:
v the following device-related MVS system control blocks:
Unit control block (UCB), UCB prefix, and UCB common extension
Device class extension (DCE)
v and the following data buffers acquired directly from the device:
Read device characteristics (RDC) data
Read configuration data (RCD) data

| Using the DEVSERV QLIB option

| Use the QLIB option of the DEVSERV command to:
| v Request a list of tape library subsytems that are defined to the host. Libraries are
| listed by serial number (library-id)
| v Request a list of devices within a library. Devices are listed by device number
| and displays the library port for each device
| v Validate the connection status of devices in a library, for example, devices that
| are connected to the host.
| v Delete an improperly defined library control block in preparation for an IODF
| activate.
| v Issue a diagnostic state save order to a library when requested by the IBM
| Support Center.

Chapter 4. MVS System Commands Reference 4-83

 DEVSERV Command

Syntax
The syntax for the DEVSERV command is:

DS {PATHS|P},[/]devnum[,nn][,ONLINE|,ON ][,NOSYM|,NOS][,DUMP]
{SMS|S } |,OFFLINE|,OFF
| [,L=a,name,name-a]

{QDASD | QD}[,? |

[ [ [,ccuu [,1] | ,VOL=volser ] [ [,UCB] [,DCE][,SSSCB] [,DPCT]

[ [,NOIO] | [,RDC] [,RCD] [,SNSS] ] ] ] | ,ccuu,nnn |
[,ccuu,nnn] ,VOL=volser |
,MACH=[mmpp-sssss | XXXX-sssss] |
,SSID=[ssid | ALL] |
,TYPE=[type | ALL] ]
[,ONLINE] [,OFFLINE] [,DEFINED] [,CHKFAIL] [,VALIDATE] [,TOTALCYL]

{QTAPE | QT}[,? |

[ [ [,ccuu [,1] ] [ [,UCB] [,DCE][ [,NOIO] | [,RDC]

[,RCD] ] ] ] | ,ccuu,nnn |
[,ccuu,nnn] ,LIB=libid | ALL |
,MACH=[mmpp-sssss | XXXX-sssss] |
,TYPE=[type | ALL] ]
[,ONLINE] [,OFFLINE] [,DEFINED]

{QPAVS | QP},{dddd}
{dddd,nn}
{SSID=ssid}
| {dddd,{VOLUME | UCB | DCE | UNBOX}}

| [QLIB | QL],
| [LIST] {ACTIVE|INACTIVE|QUEUE}
| [LISTALL] {ACTIVE|INACTIVE}
| [LIBID] {ACTIVE|INACTIVE|VALIDATE|QUEUE|DELETE}
| [DDDD] {SS}
| [?]

Parameters
The basic status parameters are:
PATHS or P
Displays (in message IEE459I) the status of specified devices. The display
includes any device(s) the Storage Management Subsystem (SMS) manages,
but does not show any SMS information such as the status of any volume or
storage group associated with the device(s).
SMS or S
Displays (in message IGD001I) the volume and storage group status for nn
devices that SMS manages, starting with the specified device number.
[/]devnum
The device number for which the system is to display information. The number
consists of three or four hexadecimal digits, optionally preceded by a slash (/).
You can specify any device that the operating system supports, except that with
the SMS operand, the system displays the status of the volume and the storage
group only for devices that SMS manages.

4-84 z/OS V1R7.0 MVS System Commands

 DEVSERV Command

nn The number, from 1 to 32, of devices for which the system is to display the
information, in ascending order beginning with the device you specify. If you do
not code nn, the default is 1, and the system displays information only about
the device you specify.
ONLINE or ON
Directs the system to display information about only those specified devices that
are online to this MVS host. If you do not specify ONLINE or OFFLINE, the
system displays information about both online and offline devices.
OFFLINE or OFF
Directs the system to display information about only those specified devices that
are offline to this MVS host. If you do not specify ONLINE or OFFLINE, the
system displays information about both online and offline devices.
NOSYM or NOS
Directs the system not to display (with message IEE459I) the definitions of
symbols. If you omit NOSYM, the system displays the definition of all the
symbols. You may use this parameter with PATHS, but not with SMS.
DUMP
Requests an SVC dump after execution of the DEVSERV PATHS command. If
you specify both DUMP and a value for nn, the system ignores the value for nn.
The SVC dump will cause an 0C1X abend. You may use this parameter with
PATHS, but not with SMS.
| L=a , name, or name-a
The display area (a), console name (name), or both (name-a) where the display
will appear. If you omit this operand, the display appears in the first available
display area or in the message area of the console at which you entered the
command.
QDASD or QD
Displays (in message IEE459I) diagnostic information about the status of direct
access storage devices and storage control units. You use two classes of
QDASD parameters to control the scope of the display: unit selection
parameters and dump selection parameters.
v Use unit selection parameters to identify the units whose information you
want to see. These parameters include ccuu and nnn, VOL, MACH, SSID,
TYPE, ONLINE, OFFLINE, DEFINED, and CHKFAIL.
v Use the dump selection parameters, to define the contents of the display.
Beyond the basic status information, you can specify which of the following
MVS system control blocks, and/or what information acquired directly from
the following device information buffers, to display in hexadecimal format.
The system control blocks are UCB, DCE, SSSCB, and DPCT.
If you specify the parameter NOIO, the display will show only the storage
resident information in the MVS control blocks; the command will not
issue any I/O to the selected devices.
The device information buffers are RDC, RCD, and SNSS.
Any hexadecimal information you request appears following the basic status
information.
In addition, there is one action parameter, VALIDATE, and one display request
parameter, TOTALCYL.
QDASD-specific Unit Selection Parameters
? Enter the command DEVSERV QDASD,? to view online help text.

Chapter 4. MVS System Commands Reference 4-85

DEVSERV Command

ccuu
The number of the DASD device you are querying.
nnn
The number of DASD devices or units to query. Valid values are from 1 to 256.
The default is 1.
VOL=volser
The serial number of the volume whose information DEVSERV will display. The
volume must be online to the system where you issue the DEVSERV
command.
MACH=mmpp-sssss | XXXX-sssss
A ten-character serial number specifying either the storage control unit or DASD
device about which DEVSERV will display information. If you specify
XXXX-sssss, the search will be done only on the sssss portion of the number.
MACH= will cause an I/O operation for each DASD in the system. To limit the
number of I/O operations, specify ccuu and nnn.
SSID=ssid | ALL
Specifies the identification number of the subsystem whose information
DEVSERV will display. Valid ssid numbers are from 1 to FFFF.
SSID=ssid will cause an I/O operation for each DASD in the system. To limit the
number of I/O operations, specify ccuu and nnn.
SSID=ALL requests a display of information for all DASD devices that support
the RCD (Read Configuration Data) command.
TYPE=type | ALL
Specifies the type of DASD or storage control unit about which DEVSERV will
display information. Valid type values are 3380, 3390, and 9345. TYPE=ALL
causes the system to display information for all DASD devices that meet all
other selection criteria. TYPE= will cause an I/O operation for each DASD in the
system. To limit the number of I/O operations, specify ccuu and nnn.
ONLINE or ON and OFFLINE or OFF
See the basic status parameters, above.
DEFINED
Displays information about all DASD units defined in the current I/O
configuration that meet all other selection criteria. The display contains
information based on the existence of unit addresses (UCBs) for DASD type
devices, and not on the existence of physical devices. Therefore, the display
may contain information even for unit addresses that have no accessible
physical devices, or for which an accessible physical device type is inconsistent
with the defined device type.
CHKFAIL
Directs the system to display information about a device with a status that is
inconsistent between the MVS control blocks and the device. This parameter
requires a unit address with a physical device attached to it. CHKFAIL will
cause an I/O operation for each DASD in the system. To limit the number of I/O
operations, specify ccuu and nnn.
VALIDATE
Uses status information acquired directly from a device to correct inconsistent
extended function status information maintained in host processor storage.
VALIDATE has no effect if the unit address has no physical device attached.
TOTALCYL
Accumulates device capacities during the scan. Valid track formats are 3380,

4-86 z/OS V1R7.0 MVS System Commands

 DEVSERV Command

3390, and 9345. For each valid track format, the total capacity for all accessible
devices will appear at the end of the DEVSERV QDASD display.
QDASD Dump Selection Parameters
Parameters that are only valid when (a) specifying ccuu, and nnn has a value of
1, or (b) when specifying the VOL=volser parameter. Dump selection parameter
information appears in hexadecimal format. The parameters are:
UCB unit control block
DCE device class extension block (of the UCB)
SSSCB storage subsystem control block
DPCT device performance characteristics table
RDC read device characteristics
RCD read configuration data
SNSS sense subsystem status
NOIO no input/output requests

NOIO prevents I/O requests and allows a display only of storage resident
information. All other dump selection parameters cause I/O operations.
QTAPE or QT
Displays identification, status, and diagnostic information about tape devices in
MVS/390 configurations. You can request information about a specific tape
device or multiple tape devices. The DEVSERV QTAPE command can obtain
information from any tape device that is responsive to the SENSEID command.
You use two classes of QTAPE parameters to control the scope of the display:
unit selection parameters and diagnostic information selection parameters.
v Use unit selection parameters to identify the units whose information you
want to see. These parameters include ccuu and nnn, LIB, MACH, TYPE,
ONLINE, OFFLINE, and DEFINED.
v Use diagnostic information selection parameters to define the contents of the
display. Beyond the basic status information, you can select which of the
following MVS system control blocks, and/or what information acquired
directly from the following device information buffers, to display in
hexadecimal format.
The system control blocks are UCB and DCE.
If you specify the parameter NOIO, the display will show only the storage
resident information in the requested MVS control blocks; the system will
not issue an I/O to the selected device.
The device information buffers are RDC and RCD.
Any hexadecimal information you request appears in the display following the
basic status information.
QTAPE-specific Unit Selection Parameters
? Enter the command DEVSERV QTAPE,? to view online help text.
ccuu
The number of the starting, or only, tape device you are querying.
nnn
A decimal value indicating the number of sequential device numbers, starting
with ccuu, for which to display information.
Valid values for nnn are from 1 to 256. The default is 1. The value must be
defaulted (unspecified), or specified with a value of 1, if you are specifying any
diagnostic information selection parameters. nnn is valid only when you also
specify ccuu.

Chapter 4. MVS System Commands Reference 4-87

DEVSERV Command

nnn has a different meaning for DEVSERV QTAPE than for DEVSERV PATHS
or DISPLAY UNITS. For those commands, nnn indicates the number of device
numbers to display, ignoring gaps in the device number sequence. For the
DEVSERV QTAPE command, if gaps exist in the sequence of tape device
numbers defined to the operating system, and DEFINED is not specified, the
missing tape device numbers are listed in the form ...nnnn(01)... where nnnn is
the device number and 01 is the reason code indicating that no unit control
block was found for that device number. If DEFINED is specified, the display
contains no information for missing device numbers.
LIB=libid | ALL
Requests information about the devices having the specified libid. If you specify
LIB=ALL, the display will show information for all library tape devices. LIB= is
mutually exclusive with MACH= and TYPE=.
MACH=mmpp-sssss
A ten-character serial number of either a tape control unit or a tape device. The
display will show information for the specific device, or for all devices on the
tape control unit having the serial number mmpp-sssss. If you specify the
mmpp portion as XXXX, the command processor will ignore the manufacturer
and plant of manufacture fields of the serial number, and will search only on
sssss, the sequence number portion. MACH= is mutually exclusive with LIB=
and TYPE=.
TYPE=type | ALL
Specifies the type of tape device or control unit about which DEVSERV will
display information. Valid values for type include any valid four character tape
device or tape control unit number.
TYPE=ALL causes the system to display information for all tape devices that
meet all other selection criteria, such as ONLINE, OFFLINE, and DEFINED.
TYPE= is mutually exclusive with LIB= and MACH=.
ONLINE or ON and OFFLINE or OFF
See the basic status parameters, above.
DEFINED
Displays information about all tape units defined in the current I/O configuration
that meet all other selection criteria.
The display contains information based on the existence of unit addresses
(UCBs) for tape type devices and not on the existence of physical devices.
Therefore, the display may contain information even for unit addresses that
have no accessible physical devices, or for which an accessible physical device
type is inconsistent with the defined device type.
The system ignores DEFINED if you also specify LIB= or MACH=, as these
options require the existence of a physical device.
If you specify both DEFINED and TYPE=ALL, the display will include
information for all tape units defined in the configuration.
If you specify both DEFINED and TYPE=type, where type is other than ALL,
the display will include information only for units of the type type. Valid type
values are 3400, 3480, 3490, and 3590.
For the 3400 device type, QTAPE supports only the devices that are responsive
to the SENSEID command. For other tape devices, QTAPE annotates the
display with reason code 9: QTAPE is not supported.

4-88 z/OS V1R7.0 MVS System Commands

 DEVSERV Command

QTAPE Diagnostic Information Selection Parameters

Parameters that are only valid when you specify ccuu and nnn, with nnn having
a value of 1. The data appears in hexadecimal format. The parameters are:
UCB unit control block
DCE device class extension block
RDC read device characteristics block
RCD read configuration data block
NOIO no input/output requests

NOIO calls for a display of processor storage resident information only. The
command processor issues no I/O requests to the device(s). The display will
contain only unit numbers and device types defined in MVS. NOIO is valid only
when specified in combination with UCB and DCE. NOIO is mutually exclusive
with RDC and RCD, because those parameters can be acquired only via an I/O
operation with the device.
QPAVS or QP
Displays the logical subsystem configuration as defined to the host software,
and highlights any inconsistencies between the host configuration definition and
the subsystem configuration for parallel access volumes (PAVs).
dddd
Specifies a three- or four-digit device number.
nn Specifies the number of devices, a decimal number from 1 to 256.
ssid
Specifies the subsystem identification number (SSID) of the subsystem whose
information DEVSERV will display.
VOLUME
Displays the parallel access volume (PAV) relationship information for the
logical volume, including the PAV base device number and all PAV alias device
numbers bound to that base.
UCB
Displays the unit control block (UCB) information associated with the device.
| DCE
| Displays the device class extension block (DCE) of the BASE UCB.
UNBOX
Causes QPAVS to unbox the unbound alias device if it is in a BOX state.
| QLIB or QL
| Displays (in message IEE459I) the requested DEVSERV library information.
| You use two classes of QLIB parameters to control the scope of the display:
| parameters and sub-parameters.
| QLIB Parameters
| LIST
| Indicates that QLIB should display a list of the ACTIVE library-ids (the default).
| You can optionally generate a list of INACTIVE library-ids or QUEUEd library
| orders. LIST uses the sub-parameters ACTIVE, INACTIVE, and QUEUE.
| LISTALL
| Produces a detailed list of all libraries, including the devices and port-ids within
| each library. LISTALL uses the sub-parameters ACTIVE and INACTIVE.
| LIBID
| Indicates that the request is for a specific library. LIBID uses the
| sub-parameters ACTIVE, INACTIVE, VALIDATE, QUEUE, and DELETE.

Chapter 4. MVS System Commands Reference 4-89

 DEVSERV Command

| DDDD
| Indicates that the request is either for the library that contains device dddd, or is
| for the device dddd itself. A sub-parameter is required when DDDD is specified.
| DDDD uses the sub-parameter SS.
| ? Causes QLIB to display the command syntax.
| QLIB Sub-parameters
| ACTIVE
| Displays information about the library configuration that is currently in use by
| the system.
| INACTIVE
| Displays information about the library configuration that becomes active
| following the next IODF activate. The INACTIVE configuration is similar to
| ACTIVE, but may contain additional devices or libraries.
| VALIDATE
| Displays the same information as the INACTIVE configuration. However, before
| the configuration is displayed, I/O is issued to each device in the configuration
| to validate connectivity to the host.
| DELETE
| Indicates that QLIB should delete the INACTIVE control blocks for library LIBID
| and not affect the existing ACTIVE library definition. The DELETE command is
| used to remove incorrectly defined library control blocks so that they can be
| rebuilt. DEVSERV DELETE provides an alternative to the method described in
| information APAR II09065, which requires two IODF activates.
| The DEVSERV QLIB method is as follows:
| 1. Use QLIB DELETE to delete all of the devices from the incorrect control
| blocks.
| 2. Choose one action depending on whether you have LIBID and LIBPORT
| coded in the IODF:
| v If LIBID and LIBPORT are coded, use QLIB LIST to display that the
| INACTIVE control blocks have been deleted.
| v If LIBID and LIBPORT are not coded, use the VARY command to vary
| online the devices in the library. This will create control blocks. The
| system issues message IEA437I, for example:
| IEA437I TAPE LIBRARY DEVICE(dev), ACTIVATE IODF=XX, IS REQUIRED
| 3. Use ACTIVATE IODF to redefine the devices.
| 4. Use QLIB LIST to display that the ACTIVE control blocks are properly
| defined.
| QUEUE
| Lists the library orders that are waiting to be completed. Such orders include:
| v MOUNT
| v DEMOUNT
| v EJECT
| v AUDIT
| When an order completes, the library notifies the host and the order is removed
| from the queue. This QLIB display can list orders for all libraries, or be limited
| for a single library.
| SS
| Indicates that QLIB should issue a diagnostic state save to the library

4-90 z/OS V1R7.0 MVS System Commands

 DEVSERV Command

| containing device DDDD. This command is intended to be used at the request

| of IBM Support Center. For example, SS can be used to diagnose a hardware
| error that results in a mount failure message. Automated Operator code can
| extract the failing device number from the failure message, then insert the
| device in a QLIB SS command.

QPAVS Output Formats

When UNBOX is not specified (see Example 13) the format is:

IEE459I DEVSERV QPAVS

HOST SUBSYSTEM
CONFIGURATION CONFIGURATION
------------- ----------------------
UNIT UNIT UA
NUM. UA TYPE STATUS SSID ADDR. TYPE
---- -- ---- ------ ---- ---- --------
dddd aa BASE INV-ALIAS ssss uu BASE
ALIAS-bbbb NOT-BASE ALIAS-bb
NON-PAV NOT-ALIAS NC
NON-NPAV
UCB AT V.....
U.....
UCB PREFIX AT V.....
U.....
UCB COMMON EXTENSION AT V.....
U.....
**** UNLISTED DEVICES AND REASON CODES
dddd(rc) dddd(rc) dddd(rc) ...
**** n DEVICE(S) MET THE SELECTION CRITERIA

where:
v Host Configuration
dddd = the device number
aa = the unit address from the host configuration
BASE = dddd is a BASE device
ALIAS-bbbb = the dddd is an ALIAS device, the BASE is at address bbbb
NON-PAV = the unit is neither a BASE nor an ALIAS
v Status
INV-ALIAS = on the host side, the unit is defined as an ALIAS whose BASE is
different from the one on the subsystem side
NOT-BASE = on the host side, the unit is a BASE, while on the subsystem
side it is not
NOT-ALIAS = on the host side, the unit is an ALIAS, while on the subsystem
side it is not
NON-NPAV = on the host side, the unit is not a BASE nor an ALIAS, while on
the subsystem side it is an ALIAS
v Subsystem Configuration
ssss = the SSID of the subsystem where device dddd belongs
uu = the unit address from the subsystem configuration
BASE = the unit is a BASE
ALIAS-bb = the unit is an ALIAS device and the BASE is at unit address bb
NC = the unit is neither a BASE nor an ALIAS

If optional keyword UCB is specified:

V..... = virtual address

Chapter 4. MVS System Commands Reference 4-91

 DEVSERV Command

U..... = UCB content in HEX digits

For unlisted devices the reason codes are:

01 = Device not configured, UCB not found
02 = UCB not connected
03 = Device unavailable, SCP routine in control
04 = Subchannel error
05 = Device boxed
06 = UCB not a DASD
07 = Device I/O error
08 = Device is not a DASD
09 = DSE-1 CCW build failed
0A = Device is an unbound PAV-ALIAS
| 0B = Device is a secondary of a PPRC pair

When UNBOX is specified (see Example 14), the format is:

IEE459I DEVSERV QPAVS
e.....

where:
v e..... = The DEVSERV QPAV UNBOX command has been executed successfully.
v e..... = The DEVSERV QPAV UNBOX command has been executed with a return
code of yy and a reason code of zz.
v e..... = dddd is not an unbound PAV-ALIAS device. The DEVSERV QPAV
UNBOX command is not executed.
v e..... = dddd is not in BOX state. The DEVSERV QPAV UNBOX command is not
executed.

Examples

Example 1

To display the status of a DASD with device number 380, enter:

DS P,380

Example 2

To display the status of a DASD with device number 3480, enter:

DS P,/3480

Example 3

To display the status of all online devices with device numbers 380 through 38F,
enter:
DS P,380,16,ON

Example 4

To display the status of SMS-controlled device 430 and the seven devices whose
addresses follow it, enter:
ds s,430,8

4-92 z/OS V1R7.0 MVS System Commands

 DEVSERV Command

This command would produce the following display:

11.49.20 IGD001I 11:49:20 DEVSERV SMS 455

UNIT,TYPE ,M,VOLUME,VOLSTAT STORGRP, SGSTAT

430 ,3380 ,O,XP0101,ENABLED SXP01 ,ENABLED
431 ,3380 ,A,XP0201,ENABLED SXP02 ,ENABLED
432 ,3380 ,A,XP0202,ENABLED SXP02 ,ENABLED
433 ,3380 ,O,XP0301,ENABLED SXP03 ,ENABLED
434 ,3380 ,O,XP0302,ENABLED SXP03 ,ENABLED
435 ,3380 ,O,XP0303,ENABLED SXP03 ,ENABLED
436 ,3380 ,O,338001,STRG/RSDNT, VOLUME NOT MANAGED BY SMS
437 ,3380 ,A,SMSPCK,STRG/RSDNT, VOLUME NOT MANAGED BY SMS

Note: Indications in the M column are: O=online, A=allocated, F=offline.

Example 5

The following two sample displays compare the response to DEVSERV P with the
response to DEVSERV S. Note that DEVSERV P provides volser and CHPID
information, while DEVSERV S provides SMS volume and storage group status.

Issuing DEVSERV P,430 produces this display:

00- 16.24.41 devserv p,430

16.24.41 IEE459I 16.24.41 DEVSERV PATHS 572

UNIT DTYPE M CNT VOLSER CHPID= PATH STATUS
430, 3380D, O, 000, XP0101, 25=+ 2E=+

************************ SYMBOL DEFINITIONS ************************

O = ONLINE + = PATH AVAILABLE

Issuing DEVSERV S,430 produces this display:

16.24.26 devserv s,430

16.24.26 IGD001I 16:24:26 DEVSERV SMS 569

UNIT, TYPE ,M, VOLUME, VOLSTAT STORGRP, SGSTAT
430, 3380 ,O, XP0101, ENABLED SXP01, QUIESCED
*************************** SYMBOL DEFINITIONS *********************
O = ONLINE + = PATH AVAILABLE

Example 6

The extra header line and data line appear in the response only when there are
3990 Model 3 Storage Controls in the system. If record caching has not been
installed, the RC column in the third header line is left blank.

Issuing DEVSERV P,430,2 produces this display:

00- 16.24.41 devserv p,430,2

16.24.41 IEE459I 16.24.41 DEVSERV PATHS 572

UNIT DTYPE M CNT VOLSER CHPID= PATH STATUS
RC TC DFW PIN DC-STATE CCA DDC ALT CU-TYPE
430, 3380D, O, 000, XP0101, 25=+ 2E=+
IE YY NN N SIMPLEX C0 01 3990-3
431, 3380E, O, 000, XP0101, 25=+ 2E=+
IE YY NN N SIMPLEX C1 01 3990-3

************************ SYMBOL DEFINITIONS **************************

O = ONLINE + = PATH AVAILABLE

Example 7

Chapter 4. MVS System Commands Reference 4-93

DEVSERV Command

This example shows the dual copy status.

Issuing DS P,D2A,2 produces this display:

IEE459I 10.06.45 DEVSERV PATHS 297
UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS
RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC ALT CU-TYPE
0D2A,3380D ,O,000,DSFXA0,1B=+ 9B=+ 1C=+ 9C=+
00AB Y NY. NY. N PRIMARY 20 20 0D2B 3990-3
0D2B,3380D ,F,000, ,1B=+ 9B=+ 1C=+ 9C=+
00AB Y NY. NY. N SECONDARY 21 21 0D2A 3990-3

********************** SYMBOL DEFINITIONS ****************************

F = OFFLINE O = ONLINE
+ = PATH AVAILABLE

Example 8

This example shows the sparing status.

Issuing DS P,F7E produces this display:

IEE459I 16.02.11 DEVSERV PATHS 389
UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS
RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC ALT CU-TYPE
0F7E,33903 ,F,000, ,B5=X B6=X B9=X BA=X
9392-2 00FD Y NY. NN. N SPARE 2E 00 3990-3

************************ SYMBOL DEFINITIONS **************************

F = OFFLINE X = INDETERMINATE FAILING UNIT

Example 9

This example shows the PPRC status.

Issuing DS P,F7C produces this display:

IEE459I 15.14.12 DEVSERV PATHS 113
UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS
RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC ALT CU-TYPE
0F7C,33903 ,F,000, ,B1=X B7=X C1=X C7=X
053F Y YY. YY. N PSECONDRY 0C 0C 3990-6

************************ SYMBOL DEFINITIONS ***************************

F = OFFLINE X = INDETERMINATE FAILING UNIT

Example 10

This example uses the DEVSERV QTAPE command to diagnose an error, namely
an inconsistent device definition.
a. VARY ONLINE fails.

V 931,ONLINE

IEE103I UNIT 0931 NOT BROUGHT ONLINE

IEE763I NAME- IECDINIT CODE= 0000000800000000
IEA435I PHYSICAL DEVICE INCONSISTENT WITH LOGICAL DEFINITION
IEE764I END OF IEE103I RELATED MESSAGES

b. DEVSERV QTAPE shows inconsistent device definition.

DS QT,931,1

IEE459I 15.28.22 DEVSERV QTAPE

4-94 z/OS V1R7.0 MVS System Commands

 DEVSERV Command

UNIT DTYPE DSTATUS CUTYPE DEVTYPE CU-SERIAL DEV-SERIAL ACL LIBID

0931 3480X OFFLINE 3490A20 3490B40? 0113-97231 0113-97231 I
**** 1 DEVICE(S) MET THE SELECTION CRITERIA

Example 11

This example illustrates the help text provided when you issue the command:
DS QT,?

IEE459I 15.27.49 DEVSERV QTAPE

DEVSERV QTAPE COMMAND SYNTAX:
DS QT,ccuu,n,filter1,filter2,diagnostic info
ccuu -- device number, n -- number of devices (1-256)
filter1 -- LIB=ALL or library id, or
MACH=ALL or cu or device serial, or
TYPE=ALL or device type or defined device type
filter2 -- DEFINED, ONLINE, OFFLINE
DEFINED is valid only if TYPE= is selected
diagnostic info -- UCB, DCE, RDC, RCD, NOIO
valid only if n=1 is specified
DS QT,LIB=libid,filter
libid -- ALL or library id
filter -- ONLINE, OFFLINE
DS QT,MACH=serialnmbr,filter
serialnmbr -- control unit or device serial
filter -- ONLINE, OFFLINE
DS QT,TYPE=type,filter
type -- ALL or defined device type
filter -- DEFINED, ONLINE, OFFLINE

Example 12

This example illustrates the basic DEVSERV QTAPE display without hexadecimal
data.
DS QT,TYPE=ALL

IEE459I 12.57.36 DEVSERV QTAPE

UNIT DTYPE DSTATUS CUTYPE DEVTYPE CU-SERIAL DEV-SERIAL ACL LIBID
0930 3480SX ON-NRD 3490A02 3490B04 0112-47671 0112-47671 I
093F 3480SX OFFLINE 3490A02 3490B04 0112-47671 0112-47671 I
0990 3490 ON-RDY 3490A20 3490B40 0113-97231 0113-97231 I-A
09A0 3490 OFFLINE 3490C2A 3490C2A 0113-55565 0113-55565 I 10382
**** UNLISTED DEVICE(S) AND REASON CODES :
093E(05) 093F(05)
**** 4 DEVICE(S) MET THE SELECTION CRITERIA
**** (05) - DEVICE BOXED

Example 13

These three variations illustrate the DEVSERV QPAVS command when the UNBOX
parameter is not specified.
DS QP,D2FF,VOLUME

IEE459I 08.20.32 DEVSERV QPAVS 591

HOST SUBSYSTEM
CONFIGURATION CONFIGURATION
------------- ----------------------
UNIT UNIT UA
NUM. UA TYPE STATUS SSID ADDR. TYPE
---- -- ---- ------ ---- ---- --------
D222 22 BASE 0102 22 BASE

Chapter 4. MVS System Commands Reference 4-95

 DEVSERV Command

D2FE FE ALIAS-D222 0102 FE ALIAS-22

D2FF FF ALIAS-D222 0102 FF ALIAS-22
**** 3 DEVICE(S) MET THE SELECTION CRITERIA
DS QP,E27B,UCB

IEE459I 08.03.55 DEVSERV QPAVS 920

HOST SUBSYSTEM
CONFIGURATION CONFIGURATION
------------- ----------------------
UNIT UNIT UA
NUM. UA TYPE STATUS SSID ADDR. TYPE
---- -- ---- ------ ---- ---- --------
E27B 7B ALIAS-E200 3205 7B ALIAS-00
UCB AT V02336568
0088FF04E27B0000 0000000008E4C3C2 3010200F00336541 0000000000000000
0000000000100000 00F451F0023362A8 0080000000000000
UCB PREFIX AT V023BF6E0
0004004000000000 0000000000013920 289C0DB2B00080F0 0A0B1213FFFFFFFF
0108000000000001
UCB COMMON EXTENSION AT V02336540
00000900202A0000 023BF6E000000000 0000000000FCD31C 00F4539000000000
**** 1 DEVICE(S) MET THE SELECTION CRITERIA
DS QP,E279,2

IEE459I 08.23.08 DEVSERV QPAVS 952

HOST SUBSYSTEM
CONFIGURATION CONFIGURATION
------------- ----------------------
UNIT UNIT UA
NUM. UA TYPE STATUS SSID ADDR. TYPE
---- -- ---- ------ ---- ---- --------
E279 79 ALIAS-E200 3205 79 ALIAS-00
**** UNLISTED DEVICE(S) AND REASON CODES :
E27A(0A)
**** (0A) - DEVICE IS AN UNBOUND PAV-ALIAS
**** 1 DEVICE(S) MET THE SELECTION CRITERIA

Example 14

This command illustrates the DEVSERV QPAVS command when the UNBOX
parameter IS specified.
DS QP,E200,UNBOX

IEE459I 08.12.53 DEVSERV QPAVS 935

E200 IS NOT AN UNBOUND PAV-ALIAS DEVICE.
THE DEVSERV QPAV UNBOX COMMAND IS NOT EXECUTED.

| Example 15

| This example illustrates the use of DEVSERV QLIB to delete the INACTIVE control
| blocks for library 10382.
| DS QL,10382,DELETE
|
|