z/OS IBM

MVS Interactive Problem Control System

(IPCS) Commands
Version 2 Release 3

SA23-1382-30
 Note
Before using this information and the product it supports, read the information in “Notices” on page 473.

This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modifications
until otherwise indicated in new editions.
Last updated: July 17, 2017
© Copyright IBM Corporation 1988, 2017.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . vii ALTLIB command — identify libraries of CLISTs
and REXX EXECs . . . . . . . . . . . . 37
Tables . . . . . . . . . . . . . . . ix BLS9 command — session of TSO commands . . . 38
BLS9CALL command — call a program . . . . . 39
IPCS command — start an IPCS session . . . . . 41
About this information . . . . . . . . xi IPCSDDIR command — initialize a user or sysplex
Who should use this information . . . . . . . xi dump directory . . . . . . . . . . . . . 42
z/OS information . . . . . . . . . . . . xi SYSDSCAN command — display titles in dump
data sets . . . . . . . . . . . . . . . 43
How to send your comments to IBM xiii
If you have a technical problem . . . . . . . xiii Chapter 5. IPCS subcommands . . . . 45
Entering subcommands . . . . . . . . . . 45
Summary of changes . . . . . . . . xv Abbreviating subcommands and parameter
Summary of changes for z/OS MVS IPCS operands . . . . . . . . . . . . . . . 45
Commands for Version 2 Release 3 (V2R3) . . . . xv Overriding defaults. . . . . . . . . . . . 45
Summary of changes for z/OS MVS IPCS Online help . . . . . . . . . . . . . . 46
Commands for Version 2 Release 2 (V2R2) as Standard subcommand return codes . . . . . . 46
updated September 2016 . . . . . . . . . . xv Task directory for subcommands . . . . . . . 46
Summary of changes for z/OS MVS IPCS Analyze a dump. . . . . . . . . . . . 46
Commands for Version 2 Release 2 . . . . . . xvi View dump storage. . . . . . . . . . . 47
z/OS Version 2 Release 1 summary of changes . . xvi View trace information . . . . . . . . . 47
Check system components and key system areas 48
Chapter 1. Introduction . . . . . . . . 1 Retrieve information in variables . . . . . . 50
IPCS processing sources facilities, and modes . . . 1 Maintain the user dump directory or sysplex
Starting IPCS . . . . . . . . . . . . . . 2 dump directory . . . . . . . . . . . . 50
Starting IPCS with customized access . . . . . 2 Perform utility functions . . . . . . . . . 50
Starting IPCS without customized access . . . . 2 Debug a dump exit program . . . . . . . 51
Directing IPCS output . . . . . . . . . . . 2 ADDDUMP subcommand — add a source
Attention processing in IPCS . . . . . . . . . 3 description to a dump directory . . . . . . . 52
Attention processing for IPCS subcommands and ALTER subcommand — change a name in the IPCS
CLISTs . . . . . . . . . . . . . . . 3 inventory . . . . . . . . . . . . . . . 53
Attention processing for IPCS REXX Execs . . . 4 ANALYZE subcommand — perform contention
Messages and user completion codes . . . . . . 4 analysis. . . . . . . . . . . . . . . . 54
Using IPCS parameters . . . . . . . . . . . 5 APPCDATA subcommand — analyze APPC/MVS
Syntax conventions . . . . . . . . . . . . 6 component data . . . . . . . . . . . . . 62
ARCHECK subcommand — format access register
data . . . . . . . . . . . . . . . . . 66
Chapter 2. Literal values. . . . . . . . 9
ASCBEXIT subcommand — run an ASCB exit
Positive integers . . . . . . . . . . . . . 10
routine . . . . . . . . . . . . . . . . 69
Signed integers . . . . . . . . . . . . . 10
ASCHDATA subcommand — analyze APPC/MVS
General values . . . . . . . . . . . . . 10
transaction scheduler data . . . . . . . . . 70
Symbols . . . . . . . . . . . . . . . 15
ASMCHECK subcommand — analyze auxiliary
storage manager data . . . . . . . . . . . 72
Chapter 3. Data description parameter 17 CBFORMAT subcommand — format a control block 72
Parts of the data description parameter . . . . . 17 CBSTAT subcommand — obtain control block status 78
Address, LENGTH, and POSITIONS parameters . . 18 CLOSE subcommand — release resources in use by
Address processing parameters . . . . . . . . 23 IPCS. . . . . . . . . . . . . . . . . 81
Attribute parameters . . . . . . . . . . . 29 COMCHECK subcommand — analyze
Array parameters . . . . . . . . . . . . 34 communications task data . . . . . . . . . 83
Remark parameters . . . . . . . . . . . . 35 COMPARE subcommand — compare dump data. . 87
COPYCAPD subcommand — copy captured dump
Chapter 4. TSO/E commands . . . . . 37 data . . . . . . . . . . . . . . . . . 89
Entering TSO/E commands . . . . . . . . . 37 COPYDDIR subcommand — copy source
Task directory of TSO/E commands for IPCS . . . 37 description from dump directory . . . . . . . 92
COPYDUMP subcommand — copy dump data . . 94

© Copyright IBM Corp. 1988, 2017 iii

COPYTRC subcommand — copy trace entries or LISTSYM subcommand — list symbol table entries 199
records . . . . . . . . . . . . . . . 101 LISTTOD subcommand — list TOD clock image 201
COUPLE subcommand — analyze cross-system LISTUCB subcommand — list UCBs. . . . . . 203
coupling data . . . . . . . . . . . . . 105 LITERAL subcommand — assign a value to a
CTRACE subcommand — format component trace literal . . . . . . . . . . . . . . . . 205
entries . . . . . . . . . . . . . . . . 108 LOGGER subcommand — format system logger
DOCPU subcommand — obtain stand-alone dump address space data . . . . . . . . . . . 207
data for multiple processors . . . . . . . . 118 LPAMAP subcommand — list link pack area entry
DIVDATA subcommand — analyze data-in-virtual points . . . . . . . . . . . . . . . . 207
data . . . . . . . . . . . . . . . . 120 MERGE and MERGEEND subcommands — merge
DLFDATA subcommand — format data lookaside multiple traces . . . . . . . . . . . . . 209
facility data . . . . . . . . . . . . . . 123 NAME subcommand — translate an STOKEN . . 212
DROPDUMP subcommand — delete source NAMETOKN subcommand — display the token
description data . . . . . . . . . . . . 125 from a name/token pair . . . . . . . . . . 213
DROPMAP subcommand — delete storage map NOTE subcommand — generate a message . . . 216
records . . . . . . . . . . . . . . . 127 OMVSDATA subcommand — format z/OS UNIX
DROPSYM subcommand — delete symbols . . . 129 data . . . . . . . . . . . . . . . . 218
END subcommand — end an IPCS session . . . 130 OPCODE subcommand — retrieve operation code 220
EPTRACE subcommand — using 72-byte save OPEN subcommand — prepare resources for use
areas . . . . . . . . . . . . . . . . 131 by IPCS . . . . . . . . . . . . . . . 222
EQUATE subcommand — create a symbol . . . 132 PATCH subcommand. . . . . . . . . . . 225
EVALDEF subcommand — format defaults . . . 135 Adding or replacing a patch . . . . . . . 226
EVALDUMP subcommand — format dump Deleting patches . . . . . . . . . . . 227
attributes . . . . . . . . . . . . . . . 137 Listing patches . . . . . . . . . . . . 227
EVALMAP subcommand — format a storage map Return codes . . . . . . . . . . . . 228
entry . . . . . . . . . . . . . . . . 140 PROFILE subcommand — set preferred line and
EVALPROF subcommand — format PROFILE page size defaults . . . . . . . . . . . . 228
subcommand options. . . . . . . . . . . 144 RENUM subcommand — renumber symbol table
EVALSYM subcommand — format the definition entries . . . . . . . . . . . . . . . . 232
of a symbol . . . . . . . . . . . . . . 145 RSMDATA subcommand — analyze real storage
EVALUATE subcommand — retrieve dump data manager data . . . . . . . . . . . . . 233
for a variable . . . . . . . . . . . . . 149 RUNARRAY subcommand — process an array of
CLIST, REXX, or DIALOG option. . . . . . 151 control blocks . . . . . . . . . . . . . 248
Default option . . . . . . . . . . . . 152 RUNCHAIN subcommand — process a chain of
CHECK option . . . . . . . . . . . . 153 control blocks . . . . . . . . . . . . . 249
FIND subcommand — locate data in a dump . . 153 RUNCPOOL subcommand — process a CPOOL 254
FINDMOD subcommand — locate a module name 158 Examples . . . . . . . . . . . . . . 256
FINDSWA subcommand — locate a scheduler SCAN subcommand — validate system data areas 257
work area (SWA) block . . . . . . . . . . 159 SELECT subcommand — generate address space
FINDUCB subcommand — locate a UCB . . . . 160 storage map entries . . . . . . . . . . . 259
GO subcommand — resume IPCS trap processing 161 SETDEF subcommand — set defaults . . . . . 262
GRSDATA subcommand — format Global Resource SMFDATA subcommand — obtain system
Serialization data . . . . . . . . . . . . 161 management facilities records . . . . . . . . 271
GTFTRACE subcommand — format GTF trace SSIDATA subcommand — display subsystem
records . . . . . . . . . . . . . . . 165 information . . . . . . . . . . . . . . 272
HELP subcommand — get information about STACK subcommand — create a symbol in the
subcommands . . . . . . . . . . . . . 171 stack . . . . . . . . . . . . . . . . 272
INTEGER subcommand — format or list a number 172 STATUS subcommand — describe system status 273
IOSCHECK subcommand — format I/O STRDATA subcommand — format coupling facility
supervisor data. . . . . . . . . . . . . 173 structure data . . . . . . . . . . . . . 283
IPCSDATA subcommand — request a report about SUMMARY subcommand — summarize control
IPCS activity . . . . . . . . . . . . . 179 block fields . . . . . . . . . . . . . . 293
IPLDATA subcommand — request IPL reports . . 185 SYMDEF subcommand — display an entry in the
ISPEXEC subcommand — request an ISPF dialog system symbol table . . . . . . . . . . . 303
service. . . . . . . . . . . . . . . . 186 SYSTRACE subcommand — format system trace
LIST subcommand — display storage . . . . . 186 entries . . . . . . . . . . . . . . . . 303
LISTDUMP subcommand — list dumps in dump TCBEXIT subcommand — run a TCB exit routine 312
directory . . . . . . . . . . . . . . . 189 TRAPLIST subcommand — list the status of IPCS
LISTEDT subcommand — format the eligible traps . . . . . . . . . . . . . . . . 314
device table (EDT). . . . . . . . . . . . 194 TRAPOFF subcommand — deactivate IPCS traps 316
LISTMAP subcommand — list storage map entries 197 TRAPON subcommand — activate IPCS traps . . 318

iv z/OS MVS IPCS Commands

 TSO subcommand — run a TSO/E command . . 322 Commands, PF keys, and codes for panels . . . 383
VERBEXIT subcommand — run an Selection and data entry panels . . . . . . 383
installation-supplied or an IBM-supplied verb exit Pointer and storage panels . . . . . . . . 384
routine . . . . . . . . . . . . . . . 324 Dump display reporter panels . . . . . . . 385
VERBEXIT ALCWAIT subcommand — list jobs IPCS inventory panel . . . . . . . . . . 386
waiting for devices . . . . . . . . . . . 328 Storage panel . . . . . . . . . . . . 386
VERBEXIT ASMDATA subcommand — format IPCS dialog primary commands . . . . . . . 387
auxiliary storage manager data . . . . . . . 328 ALIGN primary command - display data on a
VERBEXIT AVMDATA subcommand — format X'10' or X'20' boundary . . . . . . . . . 387
availability manager data . . . . . . . . . 328 ASCII primary command — display characters
VERBEXIT BLSAIPST subcommand — format as ASCII . . . . . . . . . . . . . . 388
system initialization data . . . . . . . . . 328 CANCEL primary command — end the
VERBEXIT CBDATA subcommand — format BROWSE option . . . . . . . . . . . 388
component broker data . . . . . . . . . . 329 CBFORMAT primary command — format a
VERBEXIT DAEDATA subcommand — format control block . . . . . . . . . . . . 388
dump analysis and elimination data . . . . . . 330 CONDENSE primary command - display data
VERBEXIT GRSTRACE subcommand — format using condensing technique . . . . . . . 389
Global Resource Serialization data . . . . . . 331 DOWN primary command — scroll data
| VERBEXIT IEAVTFCB subcommand — format SVC forward . . . . . . . . . . . . . . 390
| dump system-scope statistics . . . . . . . . 334 EBCDIC primary command — display
VERBEXIT IEAVTSFS subcommand — format SVC characters as EBCDIC . . . . . . . . . 390
dump measurements and statistics report . . . . 335 END primary command — end a subcommand
VERBEXIT IEFENFVX subcommand — list ENF or panel . . . . . . . . . . . . . . 391
listeners . . . . . . . . . . . . . . . 340 EQUATE primary command — create a
VERBEXIT IEFIVAWT subcommand — list pending user-defined symbol . . . . . . . . . . 391
XCF work for tape allocation . . . . . . . . 340 EXCLUDE primary command — exclude lines
VERBEXIT IEFIVIGD subcommand — list global from display. . . . . . . . . . . . . 392
tape device information . . . . . . . . . . 341 FIND primary command — search for a
VERBEXIT JESXCF subcommand — format data specified value . . . . . . . . . . . . 393
for JES XCF component . . . . . . . . . . 342 IPCS primary command — invoke an IPCS
VERBEXIT LEDATA subcommand — format subcommand, CLIST, or REXX exec . . . . . 397
Language Environment data . . . . . . . . 342 LEFT primary command — scroll data left . . 399
VERBEXIT LOGDATA subcommand — format LOCATE primary command — scroll the
logrec buffer records . . . . . . . . . . . 345 display to show specific data . . . . . . . 400
VERBEXIT MMSDATA subcommand — format MORE primary command — scroll data . . . 402
MVS message service data . . . . . . . . . 348 OPCODE primary command — display
VERBEXIT MTRACE subcommand — format operation code . . . . . . . . . . . . 402
master trace entries . . . . . . . . . . . 348 NOALIGN primary command — display data
VERBEXIT NUCMAP subcommand — map without aligning . . . . . . . . . . . 403
modules in the nucleus . . . . . . . . . . 349 RENUM primary command — renumber
VERBEXIT SADMPMSG subcommand — format symbol entries . . . . . . . . . . . . 403
stand-alone dump message log . . . . . . . 353 REPORT primary command — process IPCS
VERBEXIT SRMDATA subcommand — format output streams . . . . . . . . . . . . 404
System Resource Manager data . . . . . . . 353 RESET primary command — remove pending
VERBEXIT SUMDUMP subcommand — format commands . . . . . . . . . . . . . 407
SVC summary dump data . . . . . . . . . 354 RETURN primary command — display the
VERBEXIT SYMPTOM subcommand — format IPCS primary option menu . . . . . . . . 408
symptom string . . . . . . . . . . . . 355 RFIND primary command — repeat the FIND
VERBEXIT VSMDATA subcommand — format command . . . . . . . . . . . . . 408
virtual storage management data . . . . . . . 356 RIGHT primary command — scroll data right 408
VLFDATA subcommand — format virtual SELECT primary command — select a pointer
lookaside facility data . . . . . . . . . . 359 to display storage . . . . . . . . . . . 409
WHERE subcommand — identify an area at a SORT primary command — sort an IPCS report 410
given address . . . . . . . . . . . . . 361 STACK primary command — create an
WLMDATA subcommand — analyze workload IPCS-defined symbol . . . . . . . . . . 411
manager data . . . . . . . . . . . . . 368 UP primary command — scroll data backward 412
XESDATA subcommand — format cross system VERBOSE primary command — display all data
extended services data . . . . . . . . . . 370 without condensing . . . . . . . . . . 413
WHERE primary command — identify an area
Chapter 6. IPCS dialog controls . . . 381 at a given address . . . . . . . . . . . 413
Using dialog controls . . . . . . . . . . . 381 IPCS dialog line commands . . . . . . . . 415

Contents v
 D line command — delete screen output . . . 415 BLSXWHER REXX EXEC — find all modules with
E line command — edit a pointer . . . . . 417 the same entry point name . . . . . . . . . 440
F line command — format a defined control
block . . . . . . . . . . . . . . . 418 Chapter 8. IPCS batch mode . . . . . 443
I line command — insert a pointer . . . . . 419 JCL needed to run IPCS in batch mode . . . . . 443
R line command — repeat a pointer . . . . . 420 IPCS cataloged procedure . . . . . . . . . 444
S line command — select a pointer to display Running CLISTs with BLSJIPCS . . . . . . 444
storage . . . . . . . . . . . . . . 421
S, F, and L line commands — show excluded
Appendix A. IPCS symbols . . . . . 445
screen output . . . . . . . . . . . . 422
Defining symbols . . . . . . . . . . . . 445
X line command — exclude screen output . . . 424
Creating symbols . . . . . . . . . . . . 445
IPCS symbol definitions . . . . . . . . . . 445
Chapter 7. IPCS CLISTs and REXX
EXECs . . . . . . . . . . . . . . 427 Appendix B. IPCS special symbols for
Task Directory for IPCS CLISTs and REXX EXECs 427
system control blocks . . . . . . . 453
BLSCBSAA CLIST — print a stand-alone dump
screening report . . . . . . . . . . . . 429
BLSCBSAP CLIST — print a stand-alone dump Appendix C. Control blocks and data
detailed report . . . . . . . . . . . . . 429 areas scanned, mapped, and
BLSCBSVA CLIST — print an SVC dump screening formatted . . . . . . . . . . . . . 455
report . . . . . . . . . . . . . . . . 430
BLSCBSVB CLIST — obtain an SVC dump Appendix D. Print dump to IPCS
screening report . . . . . . . . . . . . 431
BLSCBSVP CLIST — print an SVC dump detailed
conversion summary . . . . . . . . 463
report . . . . . . . . . . . . . . . . 431
BLSCBSYA CLIST — print a SYSMDUMP dump Appendix E. Accessibility . . . . . . 469
screening report . . . . . . . . . . . . 432 Accessibility features . . . . . . . . . . . 469
BLSCBSYB CLIST — obtain a SYSMDUMP dump Consult assistive technologies . . . . . . . . 469
screening report . . . . . . . . . . . . 433 Keyboard navigation of the user interface . . . . 469
BLSCBSYP CLIST — print a SYSMDUMP dump Dotted decimal syntax diagrams . . . . . . . 469
detailed report . . . . . . . . . . . . . 433
BLSCDDIR CLIST — create a dump directory . . 434 Notices . . . . . . . . . . . . . . 473
BLSCDROP CLIST — issue IPCS DROPDUMP for Terms and conditions for product documentation 475
uncataloged DSNAME entries . . . . . . . . 435 IBM Online Privacy Statement. . . . . . . . 476
BLSCEPTR CLIST — run a save area chain . . . 436 Policy for unsupported hardware. . . . . . . 476
BLSCPCSA CLIST — print common storage areas 436 Minimum supported hardware . . . . . . . 476
BLSCPNUC CLIST — print nucleus storage areas 437 Programming interface information . . . . . . 477
BLSCPRIV CLIST — print private storage areas 437 Trademarks . . . . . . . . . . . . . . 477
BLSCPRNT CLIST — print a dump . . . . . . 437
BLSCPSQA CLIST — print global system queue Index . . . . . . . . . . . . . . . 479
areas . . . . . . . . . . . . . . . . 439
BLSCSCAN CLIST — obtain a stand-alone dump
screening report . . . . . . . . . . . . 439

vi z/OS MVS IPCS Commands

Figures
1. Example output from LIST subcommand 31 22. PROFILE-Defined Defaults . . . . . . . 229
2. Example output from LIST subcommand 23. Example: SELECT output . . . . . . . 262
(using EP parameter) . . . . . . . . . 32 24. Example: SELECT output (storage map
3. Example output from ANALYZE command entries) . . . . . . . . . . . . . 262
(ASID contention) . . . . . . . . . . 56 25. IBM-supplied values for global
4. Example output from ANALYZE command SETDEF-defined defaults. . . . . . . . 263
(resource contention) . . . . . . . . . 57 26. Example: results of changing IPCS-defined
5. Example output from ANALYZE command values . . . . . . . . . . . . . . 271
(exception contention) . . . . . . . . . 59 27. Example output from STATUS SYSTEM
6. Example output from ANALYZE command command . . . . . . . . . . . . . 277
(lockout) . . . . . . . . . . . . . 61 28. Example output from STATUS CPU
7. Example output from ARCHECK command command . . . . . . . . . . . . . 278
(specific central processor) . . . . . . . 68 29. Example output from STATUS WORKSHEET
8. Example output from ARCHECK command command . . . . . . . . . . . . . 280
(specific access register) . . . . . . . . 69 30. Example of an SDUMP parameter list for an
9. Example CBFORMAT command output SVC dump . . . . . . . . . . . . 281
(formatting CSD). . . . . . . . . . . 75 31. Example output from STATUS FAILDATA
10. Example CBFORMAT command output command . . . . . . . . . . . . . 282
(formatting captured UCB) . . . . . . . 76 32. Sample output from SUMMARY KEYFIELD
11. Example CBFORMAT command output CURRENT command . . . . . . . . . 299
(formatting base UCB) . . . . . . . . . 77 33. Sample output from SUMMARY FORMAT
12. Example CBFORMAT command output CURRENT command . . . . . . . . . 300
(formatting alias UCB) . . . . . . . . . 78 34. Example output from SUMMARY
13. Example CBSTAT command output . . . . 80 TCBSUMMARY CURRENT . . . . . . . 301
14. Example CBSTAT command output (analyze a 35. Example output from SUMMARY
TCB) . . . . . . . . . . . . . . . 80 JOBSUMMARY CURRENT . . . . . . . 302
15. Example CBSTAT command output (analyze 36. Example output from SYSTRACE STATUS 309
an ASCB) . . . . . . . . . . . . . 81 37. Example of trace table snapshots . . . . . 311
16. Example CBSTAT command output (view data 38. Using FIND on the Dump Display Reporter
about NIP RIMs) . . . . . . . . . . . 81 Panel . . . . . . . . . . . . . . 396
17. Example COMCHECK command output 39. Result of Using FIND . . . . . . . . . 397
(obtain UCME addresses) . . . . . . . . 86 40. Result of Using PF5/RFIND . . . . . . 397
18. Example output CTRACE COMP command 115 41. Using E on the Pointer Panel . . . . . . 418
19. Example output CTRACE COMP command 116 42. Pointer Editing Panel . . . . . . . . . 418
20. Example output CTRACE TALLY command 118 43. Result of Using Edit . . . . . . . . . 418
21. LISTUCB command report for device 0410 205 44. JCL required to run IPCS in batch mode 443

© Copyright IBM Corp. 1988, 2017 vii

viii z/OS MVS IPCS Commands
Tables
1. Sources from which IPCS processes contents 1 18. Example of entries considered as a separate
2. Destination of IPCS Output . . . . . . . 3 queue . . . . . . . . . . . . . . 293
3. Additional types of messages that may appear 19. ASCB, TCB, RB key fields associated with
in an IPCS session. . . . . . . . . . . 4 specified address spaces . . . . . . . . 294
4. Summary of IPCS syntax conventions . . . . 6 20. Examples of valid date and time formats 307
5. Summary of TSO/E commands and tasks 37 21. Summary of processor status information 310
6. Standard subcommand return codes and 22. Verb name summary . . . . . . . . . 325
explanations . . . . . . . . . . . . 46 23. Selection and Data Entry Panels - Commands
7. Examples of valid date and time formats 104 and PF Keys . . . . . . . . . . . . 383
8. Structures recognized by EPTRACE . . . . 132 24. Pointer and Storage Panels - Commands and
9. Effect of DECIMAL and HEXADECIMAL on PF Keys . . . . . . . . . . . . . 384
the other parameters . . . . . . . . . 142 25. Dump display reporter panel - commands
10. Return codes for the CLIST, REXX, or and PF keys . . . . . . . . . . . . 385
DIALOG option. . . . . . . . . . . 152 26. Command codes to manage inventory panel 386
11. Return codes for the Default option . . . . 153 27. IPCS selection codes . . . . . . . . . 386
12. Return codes for the CHECK option . . . . 153 28. Summary of IPCS symbol definitions 445
13. GRS resource status values . . . . . . . 164 29. IPCS special symbols . . . . . . . . . 453
14. EXCLUDE parameter naming conventions 230 30. Control blocks and data areas that
15. Address space parameter and AREA(name) 261 CBFORMAT can scan . . . . . . . . . 455
16. Defaults for the STATUS report type . . . . 276 31. AMDPRDMP - IPCS conversion summary 463
17. Example of queue and entry postions 292

© Copyright IBM Corp. 1988, 2017 ix

x z/OS MVS IPCS Commands
About this information
The interactive problem control system (IPCS) is a tool provided to aid in
diagnosing software failures. IPCS provides formatting and analysis support for
dumps and traces produced by MVS™ and other program products and
applications that run on z/OS.

The following reference information about using IPCS is presented, in alphabetic

order:
v TSO/E commands for IPCS
v IPCS subcommands
v IPCS primary commands
v IPCS line commands
v IPCS CLISTs and REXX execs
It also gives examples of output generated by subcommands.

Who should use this information

This document is for anyone who analyzes unformatted dumps and traces on an
MVS system.

z/OS information
This information explains how z/OS references information in other documents
and on the web.

When possible, this information uses cross document links that go directly to the
topic in reference 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.

To find the complete z/OS® library, go to IBM Knowledge Center

(www.ibm.com/support/knowledgecenter/SSLTBW/welcome).

© Copyright IBM Corp. 1988, 2017 xi

xii z/OS MVS IPCS Commands
How to send your comments to IBM
We appreciate your input on this documentation. Please provide us with any
feedback that you have, including comments on the clarity, accuracy, or
completeness of the information.

Use one of the following methods to send your comments:

Important: If your comment regards a technical problem, see instead “If you have
a technical problem.”
v Send an email to [email protected].
v Send an email from the Contact z/OS web page (www.ibm.com/systems/z/os/
zos/webqs.html).

Include the following information:

v Your name and address
v Your email address
v Your phone or fax number
v The publication title and order number:
z/OS MVS IPCS Commands
SA23-1382-30
v The topic and page number or URL of the specific information to which your
comment relates
v The text of your comment.
When you send comments to IBM®, you grant IBM a nonexclusive right to use or
distribute the comments in any way appropriate without incurring any obligation
to you.

IBM or any other organizations use the personal information that you supply to
contact you only about the issues that you submit.

If you have a technical problem

Do not use the feedback methods that are listed for sending comments. Instead,
take one or more of the following actions:
v Visit the IBM Support Portal (support.ibm.com).
v Contact your IBM service representative.
v Call IBM technical support.

© Copyright IBM Corp. 1988, 2017 xiii

xiv z/OS MVS IPCS Commands
Summary of changes
This information includes terminology, maintenance, and editorial changes.
Technical changes or additions to the text and illustrations for the current edition
are indicated by a vertical line to the left of the change.

Summary of changes for z/OS MVS IPCS Commands for Version 2

Release 3 (V2R3)
The following changes are made for z/OS Version 2 Release 3 (V2R3).

New
v The VERBEXIT IEAVTFCB subcommand was added to format SVC dump
system-scope statistics. For more information, see “VERBEXIT IEAVTFCB
subcommand — format SVC dump system-scope statistics” on page 334.
v New symbols for Guarded-Storage Facility added in “IPCS symbol definitions”
on page 445 and Appendix B, “IPCS special symbols for system control blocks,”
on page 453.
v New GSCB control block for Guarded-Storage Facility added in Appendix C,
“Control blocks and data areas scanned, mapped, and formatted,” on page 455
to the list of control blocks and data areas in system dumps that the
CBFORMAT subcommand can scan, create a storage map entry for, or format.

Changed
v The VERBEXIT IEAVTSFS subcommand was updated to add parameters that
indicate which statistics are displayed. For more information, see “VERBEXIT
IEAVTSFS subcommand — format SVC dump measurements and statistics
report” on page 335.
v The SYSTRACE subcommand was updated to add parameters for specific
message suppression. For more information, see “SYSTRACE subcommand —
format system trace entries” on page 303.

Summary of changes for z/OS MVS IPCS Commands for Version 2

Release 2 (V2R2) as updated September 2016
The following changes are made for z/OS Version 2 Release 2 (V2R2) as updated
September 2016.

New
v The REGVEC and REGVECnnn symbols were added. For more information, see
“IPCS symbol definitions” on page 445, Appendix B, “IPCS special symbols for
system control blocks,” on page 453, and Appendix C, “Control blocks and data
areas scanned, mapped, and formatted,” on page 455.
v Information about system symbols was added. For more information, see
“Symbols” on page 15.

Changed
v Return codes were added to the EVALSYM subcommand. For more information,
see “EVALSYM subcommand — format the definition of a symbol” on page 145.

© Copyright IBM Corp. 1988, 2017 xv

Summary of changes for z/OS MVS IPCS Commands for Version 2
Release 2
The following changes are made for z/OS Version 2 Release 2 (V2R2).

Changed
v The address space selection parameters of the IPCS SELECT subcommand were
updated for ACTIVE storage. For more information, see “SELECT subcommand
— generate address space storage map entries” on page 259.
v The XESDATA subcommand is updated to add the TRACE parameter and the
TROPTS additional data selection parameter. For more information, see
“XESDATA subcommand — format cross system extended services data” on
page 370.

z/OS Version 2 Release 1 summary of changes

See the Version 2 Release 1 (V2R1) versions of the following publications for all
enhancements related to z/OS V2R1:
v z/OS Migration
v z/OS Planning for Installation
v z/OS Summary of Message and Interface Changes
v z/OS Introduction and Release Guide

xvi z/OS MVS IPCS Commands

Chapter 1. Introduction
This book describes the functions and facilities of the interactive problem control
system (IPCS). IPCS provides an interactive, online facility for diagnosing software
failures. Using data sets and active system storage, IPCS analyzes information and
produces reports that can be viewed at a Time Sharing Option Extensions (TSO/E)
terminal or can be printed.

IPCS processing sources facilities, and modes

v Sources for IPCS processing
As Table 1 shows, IPCS processes the contents of the following sources.
Table 1. Sources from which IPCS processes contents
Source Explanation
SVC dump data set Dump written to a data set on DASD or tape
SYSMDUMP dump data set ABEND dump written to data sets defined by SYSMDUMP
DD statements
Stand-alone dump Dump written by the stand-alone service aid
Trace data set Data set created by the generalized tracing facility (GTF) or
by component trace
Active system storage The following in central storage:
v Storage for the address space in which IPCS is currently
running
v Private storage
v Any common storage accessible by an unauthorized
problem-state program
Data sets Virtual storage access method (VSAM) data sets and other
data sets for browsing
Note: For information about how to reference VSAM
objects, see “Address processing parameters” on page 23.

v IPCS processing facilities

IPCS can browse and analyze the records in any of these data sets using general
purpose facilities. Special purpose facilities are also included to process two
groups of these data sets:
– The dump data sets and active system storage — for these sources, you can:
- Browse virtual and other system storage, and control information placed in
dumps by the dump-writing program.
- Request various types of dump data reports.
- Selectively format trace records found in the dump.
- Run your own special purpose analysis and reporting CLISTs, REXX execs,
Interactive System Productivity Facility (ISPF) dialogs, and exit routines.
– Trace data sets — IPCS provides specialized processing to facilitate formatting
trace data sets. See the z/OS MVS IPCS User's Guide for further information.
v IPCS processing modes
Using IPCS, you can process dumps in:

© Copyright IBM Corp. 1988, 2017 1

 – Full screen mode during an interactive TSO/E session, a session during
which line mode messages are shown immediately when written, where
interactive ISPF services are also available.
– Line mode from any terminal supported by TSO/E. See “Starting IPCS.”
– Batch mode using TSO/E commands, IPCS subcommands, CLISTs, and REXX
execs. See Chapter 8, “IPCS batch mode,” on page 443.

Recommendations

The information in this section is intended as a ‘quick path’ into IPCS. The z/OS MVS
IPCS User's Guide provides more detailed usage information. It is recommended as an
introduction and refresher to using IPCS as your installation's dump analysis tool.

Starting IPCS
The procedure you follow to start IPCS depends on the specific customization, if
any, that you or your installation have provided. z/OS MVS IPCS User's Guide
contains a more detailed description of procedures for starting IPCS, and z/OS
MVS IPCS Customization explains how to customize access to IPCS.

Starting IPCS with customized access

There should be an option on an ISPF selection panel for starting the IPCS dialog.
To start the IPCS dialog, select the appropriate option.

Starting IPCS without customized access

If access to IPCS has not been customized, you can use the following procedure:
1. Logon to TSO/E.
2. (Optional) — Unless you want to use IPCS in line mode, you can skip this step.
To start IPCS in line mode, do the following:
a. Add SYS1.SBLSCLI0 to the SYSPROC concatenation:
ALTLIB ACTIVATE APPLICATION(CLIST) DA(’SYS1.SBLSCLI0’)
b. Enter the IPCS command:
IPCS
At this point, you can enter IPCS commands in line mode. You do not need
to proceed to the next step unless you want to start the IPCS dialog from
IPCS line mode.
3. Start the ISPF dialog:
ISPF
4. Choose the TSO/E commands option from the ISPF menu.
5. Start the IPCS dialog by entering the following at the prompt:
EX ’SYS1.SBLSCLI0(BLSCLIBD)’

Directing IPCS output

Depending on which message routing parameters are in effect (PRINT, NOPRINT,
PDS, NOPDS, TERMINAL, NOTERMINAL) and depending in which mode
(full-screen, line, batch) you are using IPCS, the output can be directed to different
mediums. Note that certain non-report type messages are always routed to the
terminal or the SYSTSPRT data set.

2 z/OS MVS IPCS Commands

 Directing Output

Table 2 provides a summary of the output destination possibilities.

Table 2. Destination of IPCS Output
Message routing Using IPCS in line or Using IPCS in batch mode,
parameters full-screen mode, the output is the output is directed to:
directed to:
PRINT, PDS, and IPCSPRNT data set, IPCSPDS IPCSPRNT, IPCSPDS, and
TERMINAL data set, and Terminal SYSTSPRT data sets
PRINT, PDS, and IPCSPRNT and IPCSPDS data IPCSPRNT and IPCSPDS
NOTERMINAL sets data sets
PRINT, NOPDS, and IPCSPRNT data set and Terminal IPCSPRNT and SYSTSPRT
TERMINAL data sets
PRINT, NOPDS, and IPCSPRNT data set IPCSPRNT data set
NOTERMINAL
NOPRINT, PDS, and IPCSPDS data set and Terminal IPCSPDS and SYSTSPRT
TERMINAL data sets
NOPRINT, PDS, and IPCSPDS data set IPCSPDS data set
NOTERMINAL
NOPRINT, NOPDS, and Terminal SYSTSPRT data set
TERMINAL
NOPRINT, NOPDS, and Terminal SYSTSPRT data set
NOTERMINAL

Note: Unless a different ddname is used on the OPEN subcommand, IPCS

associates PRINT with the IPCSPRNT data set.

Attention processing in IPCS

To cancel any IPCS processing, use the attention interrupt key. When you press the
attention interrupt key during an IPCS session, IPCS indicates that you have
suspended mainline IPCS processing and have initiated an attention interrupt by
displaying a message.

Attention processing for IPCS subcommands and CLISTs

v For subcommands and CLISTs running in IPCS line mode, IPCS displays the
following message:
IPCS*
v For subcommands and CLISTs running in the IPCS dialog, IPCS displays the
following message:
Processing suspended--Enter a null line, TIME, END, or ABEND

You can do the following in response to either attention message:

v Resume processing by entering a null line after the attention interrupt. If you are
using session manager support at your terminal, press the ERASE EOF key and
then press Enter to enter a null line.
v Enter the TSO/E TIME command. The command runs without ending the
interrupted processing and the attention interrupt remains in effect.
v Enter the TSO/E ABEND command. The IPCS session abnormally ends with an
IPCS user code of X'072' (decimal 114). The abend produces a dump if you have
a SYSABEND, SYSUDUMP, or SYSMDUMP data set allocated to your session.
v Enter the TSO/E END command. IPCS ends the interrupted processing.

Chapter 1. Introduction 3
Attention processing

v Perform other processing by entering any other TSO/E command or an IPCS

subcommand or CLIST. This causes IPCS to end the interrupted processing and
run the new command, subcommand, or CLIST.

If you interrupt and end a subcommand that modifies the problem directory or the
data set directory, the modification to the directory might be incomplete.

The ATTN statement of CLIST processing is not supported under IPCS. The
scheduling of the attention interrupt causes the IPCS attention exit to be bypassed
and control reverts to the terminal monitor program (TMP) level.

Attention processing for IPCS REXX Execs

For REXX execs running in IPCS line mode, the system displays message IRX0920I:
ENTER HI TO END, A NULL LINE TO CONTINUE, OR AN IMMEDIATE COMMAND

You can do the following in response to this message:

v Enter the HI command to end the exec. If the system was processing an IPCS
subcommand from the exec at the time of the interrupt, the system allows the
subcommand to run to completion before ending the exec.
v Enter a null line after the attention interrupt to resume processing.
v Enter an immediate command. If the system was processing an IPCS
subcommand from the exec at the time of the interrupt, the system allows the
subcommand to run to completion before processing the immediate command.
See z/OS TSO/E REXX Reference for information about immediate commands.

For REXX execs running in the IPCS dialog, IPCS displays the following message:
Enter HI to end, a null line, TIME, or an immediate command

You can do the following in response to this message:

v Enter the HI command to end the exec. If the system was processing an IPCS
subcommand from the exec at the time of the interrupt, the system also ends the
subcommand.
v Enter a null line after the attention interrupt to resume processing.
v Enter the TSO/E TIME command. The command runs without ending the
interrupted processing and the attention interrupt remains in effect.
v Enter an immediate command. If the system was processing an IPCS
subcommand from the exec at the time of the interrupt, the system allows the
subcommand to run to completion before processing the immediate command.
See z/OS TSO/E REXX Reference for information about immediate commands.

Messages and user completion codes

Messages that appear during an IPCS session can come from many sources. Table 3
identifies the three major types of messages that appear during an IPCS session
and the information units where you will find explanations for those messages:
Table 3. Additional types of messages that may appear in an IPCS session
Message type Information units
IPCS z/OS MVS Dump Output Messages
TSO/E z/OS TSO/E Messages

4 z/OS MVS IPCS Commands

 Attention processing

Table 3. Additional types of messages that may appear in an IPCS session (continued)
Message type Information units
MVS BCP z/OS MVS System Messages, Vol 1 (ABA-AOM)
z/OS MVS System Messages, Vol 2 (ARC-ASA)
z/OS MVS System Messages, Vol 3 (ASB-BPX)
z/OS MVS System Messages, Vol 4 (CBD-DMO)
z/OS MVS System Messages, Vol 5 (EDG-GFS)
z/OS MVS System Messages, Vol 6 (GOS-IEA)
z/OS MVS System Messages, Vol 7 (IEB-IEE)
z/OS MVS System Messages, Vol 8 (IEF-IGD)
z/OS MVS System Messages, Vol 9 (IGF-IWM)
z/OS MVS System Messages, Vol 10 (IXC-IZP)

User completion codes indicate a problem with IPCS processing. See the IPCS topic
in z/OS MVS Diagnosis: Reference for explanations of the codes.

Using IPCS parameters

A typical IPCS function invocation is divided into two parts: the operation, or
command or subcommand name, followed by the operand, which consists of
parameters. The operation can be a TSO/E command, IPCS subcommand, IPCS
primary command, or IPCS line command.

The parameters that are used with the TSO/E commands, IPCS subcommands, and
IPCS primary commands are of two types: positional and keyword.
v Positional parameters
Positional parameters follow the command name in a certain order. In the
command descriptions within this book, the positional parameters are shown in
lowercase characters. In the following example, iosvirba is a positional parameter
on the FINDMOD subcommand:
FINDMOD iosvirba
v Keyword parameters
Keyword parameters are specific names or symbols that have a particular
meaning to IPCS. You can include these parameters in any order following the
positional parameters. In the command descriptions, the keywords are shown in
uppercase characters and any variables associated with them are shown in
lowercase characters. However, the keywords may be entered in either
uppercase or lowercase:
TERMINAL | NOTERMINAL
FILE(ddname)

Long keywords such as TERMINAL and NOTERMINAL might make syntax easier
to read, but it might be a burden to type long keywords. IPCS primary commands,
IPCS subcommands and TSO/E commands that are supplied with IPCS provide
two ways to allow abbreviating long keywords:
v Some keywords that you tend to use often support explicit, short aliases. For
example, you can type C for CHARACTER.
v All keywords support unambiguous truncations. For example, you can enter
LEN for LENGTH, because this truncated form is currently unambiguous on all
the subcommands that support the LENGTH keyword.
If you are composing a command procedure that you hope will remain useful for a
long time, do not truncate keywords in it. As IPCS responds to new demands, new
keywords are introduced that might make the previous acceptable truncations

Chapter 1. Introduction 5
IPCS parameters

ambiguous. Use truncations only when you type commands manually, or when
you compose command procedures for short-term use.

Many parameters are unique to an IPCS subcommand. However, two different sets
of parameters are used by many subcommands:
v Parameters in the Chapter 3, “Data description parameter,” on page 17
v Parameters defined through “SETDEF subcommand — set defaults” on page 262

Syntax conventions
For IPCS subcommands, IPCS primary commands, IPCS line commands, and
TSO/E commands, the syntax in this book uses the conventions shown in Table 4.

Note: The defaults for the SETDEF-defined parameters are not shown in each
subcommand syntax diagram because they are individually set by each IPCS user.
Unless a special situation is noted for a particular subcommand, see “SETDEF
subcommand — set defaults” on page 262 for an explanation of each
SETDEF-defined parameter.
Table 4. Summary of IPCS syntax conventions
Notation Meaning Syntax example Sample entry
UPPERCASE Uppercase indicates the item must be SUMMARY KEYFIELD summary keyfield
entered using the characters shown.
Enter the item in either uppercase or
lowercase.
lowercase Lowercase indicates a variable item. LENGTH(length) length(24)
Substitute your own value for the item.
‘ ’ Apostrophes indicate a parameter string. VERBX VSMDATA verbx vsmdata
Enter the apostrophes as shown. ’parameter,parameter’ ’error,global’
( ) Parentheses must be entered as shown. FLAG(severity) flag(info)
{ } Single braces represent group-related { COMCHECK | COMK } comcheck
items that are alternatives. You must
enter exactly one of the items.
[ ] Single brackets represent single or GTFTRACE [DEBUG] gtftrace
group-related items that are optional.
Enter one or none of the items.
{ } Stacked braces represent group-related { ASCBEXIT } { pgmname } ascbx *
{ } items that are alternatives. You must { ASCBX } { * }
{ } enter exactly one of the items.
[ ] Stacked brackets represent group-related [ TERMINAL ] terminal
[ ] items that are optional. Enter one or none [ NOTERMINAL ]
[ ] of the items.
____ Underscore indicates a default option. If SCAN [ SUMMARY ] scan
you select an underscored alternative, [ NOSUMMARY ]
you need not specify it when you enter
the command.
| Or-sign indicates a mutually-exclusive RDCM[(ALL | LIST | address)] rdcm(all)
choice. When used with brackets, enter
one or none of the items. When used
with braces, you must enter one of the
items.

6 z/OS MVS IPCS Commands

 Syntax conventions

Table 4. Summary of IPCS syntax conventions (continued)

Notation Meaning Syntax example Sample entry
... Ellipsis indicates that the preceding item SUB((subname[.subname]...)) sub((sub1.
or group of items can be repeated one or func2.svc3))
more times.

Chapter 1. Introduction 7
Syntax conventions

8 z/OS MVS IPCS Commands

Chapter 2. Literal values
This section describes the following types of literal values that can be used with
IPCS subcommands and primary commands.
v “Positive integers” on page 10.

To describe Specify
Positive binary numbers B‘bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb’
Positive decimal numbers nnnnnnnnnn
Positive hexadecimal X‘xxxxxxxx’ or X‘xxxxxxxx_xxxxxxxx’
numbers
An underscore (_) might be used between hexadecimal
digits to improve legibility for values greater than 32 bits.

v “Signed integers” on page 10.

To describe Specify
Signed binary numbers B‘[+|-]bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb’
Signed decimal numbers [+|-]nnnnnnnnnn or F‘[+|-]nnnnnnnnnn’
Signed hexadecimal X‘[+|-]xxxxxxxx’ or X‘[+|-]xxxxxxxx_xxxxxxxx’
numbers
An underscore (_) might be used between hexadecimal
digits to improve legibility for values greater than 32 bits.

v “General values” on page 10.

To describe Specify Restriction

Fullword pointers A‘xxxxxxxx’ or none
A‘(Ln)xxxxxxxx_xxxxxxxx’
EBCDIC character strings C‘c...’ none
Signed binary fullwords F‘[+|-]nnnnnnnnnn’ or none
F‘(Ln)[+|-]nnnnnnnn’
Signed binary halfwords H‘[+|-]nnnnn’ or none
H‘(Ln)[+|-]nnnnn’
Picture strings P‘p...’ none
ASCII character strings Q‘q...’ none
Any string of characters ‘...’ or “...” valid only for the FIND
primary command
ASCII text strings S‘s...’ none
EBCDIC text strings T‘t...’ none
Uppercase or lowercase blank, | sign, or comma before valid only for the FIND
letters or numbers and after the value primary command
Hexadecimal strings X‘xx...’ none
Previously entered search valid only for the FIND
value primary command

v “Symbols” on page 15.

© Copyright IBM Corp. 1988, 2017 9

Literal Values

Positive integers
Whenever an IPCS subcommand requires a number between 0 and 231, that
number can be entered in any of the following ways:
nnnnnnnnnn
This notation describes a decimal number. The value, nnnnnnnnnn, is a positive
1- to 10-digit decimal number.

Note: The maximum value that can be entered using decimal notation is
2147843647 (231-1), one less than the maximum positive integer that IPCS can
process (for example, as a data length or a page size). In order to designate the
maximum value to IPCS, hexadecimal or binary notation must be used.
X‘xxxxxxxx’ or X‘xxxxxxxx_xxxxxxxx’
This notation describes a hexadecimal number. The value, xxxxxxxx, is a
positive 1- to 8-digit hexadecimal number, preceded by X. Hexadecimal digits
A through F can be entered using either uppercase or lowercase letters.
An underscore (_) might be used between hexadecimal digits to improve
legibility for values greater than 32 bits.
B‘bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb’
This notation describes a binary number. The value,
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb, is a positive 1- to 31-digit binary number
preceded by B.

Signed integers
When an IPCS subcommand requires a number between -231 and 231-1, you can
specify the number using any of the following notations:
[+]nnnnnnnnnn
-nnnnnnnnnn
This notation describes a decimal number. The value, nnnnnnnnnn, is a 1- to
10-digit decimal number preceded by an optional plus (the default) or minus
sign.
F‘[+]nnnnnnnnnn’
F‘-nnnnnnnnnn’
This notation describes a 1- to 10-digit decimal number preceded by an F and
an optional plus (the default) or minus sign.
X‘[+]xxxxxxxx’
X‘-xxxxxxxx’
This notation describes a hexadecimal number. The value, xxxxxxxx, is a 1- to
8-digit hexadecimal number preceded by X and an optional plus (the default)
or minus sign. Hexadecimal digits A through F can be entered in either
uppercase or lowercase.
B‘[+]bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb’
B‘-bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb’
This notation describes a binary number. The value,
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb, is a 1- to 31-digit binary number preceded by
B and an optional plus (the default) or minus sign.

General values
When an IPCS subcommand accepts a literal value that can describe a string and a
number, that value can be expressed as follows:

10 z/OS MVS IPCS Commands

 Literal Values

v Preceded by a letter indicating the type of literal and an apostrophe. The letter
can be entered in uppercase or lowercase.
v Followed by an apostrophe.

When the primary commands in the IPCS dialog accept a literal value that can
describe a string and a number, that value can be expressed in the same manner as
described for the IPCS subcommands and as follows:
v Preceded or succeeded by a letter indicating the type of literal value. The letter
can be entered in uppercase or lowercase.
v The literal value can be delimited by either quotation marks or by apostrophes.
If the delimiter character is used as part of the value, then each delimiter that is
represented in the value must be doubled.
For example, if you want to find the EBCDIC character string dump’s, enter:
FIND C’dump’’s’ or FIND C"dump’s"

IPCS accepts 64-bit addresses and signed binary values. The explicit length
notation is indicated by an expression within parentheses beginning with the letter
“..L” in upper or lower case and followed by a length expressed in decimal.
Standard TSO/E separator characters may be used between parts of the expression.
The total length of the expression may not exceed 256 characters. See type codes A,
F, and H for examples.

IPCS supports the following types of values:

A‘[(Ln)]xxxxxxxx_xxxxxxxx’
This notation describes a fullword pointer. The value, xxxxxxxx_xxxxxxxx, is a
1- to 16-digit hexadecimal expression. IPCS provides leading zeros if you enter
fewer than 16 digits.
The length may be explicitly specified as 1-8 bytes or will default to 4 bytes.
Example:
A'(L8) F4'
A'(L8) 00000000_000000F4'
C‘c...’
This notation describes an EBCDIC character string containing one to 256
characters. The value, c..., is subjected to editing as follows:
v Data entered manually from a terminal may be translated by the TSO/E
Terminal I/O Controller.
v IPCS translates each pair of adjacent apostrophes into a single apostrophe.
v The FIND primary command accepts either ‘ABC’C or C‘ABC’ as the same
search value.

Note: Lowercase letters are not translated to uppercase when the search
argument is formed.
Example:
find C’aBc’
Result: IPCS finds the first occurrence of aBc.
F‘[(Ln)][+]nnnnnnnnnn’
F‘[(Ln)]-nnnnnnnnnn’
This notation describes a signed binary fullword. The value, [+|-]nnnnnnnnnn,
is a 1- to 10-decimal digit number preceded by an optional plus (the default) or
minus sign. IPCS provides leading zeros if you enter fewer than ten digits.

Chapter 2. Literal values 11

Literal Values

Example:
F'(L8) 124'
H‘[(Ln)][+]nnnnn’
H‘[(Ln)]-nnnnn’
This notation describes a signed binary halfword. The value, [+|-]nnnnn, is a
1- to 5-decimal digit number, preceded by an optional plus (the default) or
minus sign. IPCS provides leading zeros if you enter fewer than 5 digits.
Example:
H'(L8) 75'
P‘p...’
This notation describes a picture string containing one to 256 characters. With
picture strings you can enter the type of string to be found instead of the exact
characters to be found. Each character p can be any of the following:
v Blank
v Alphabetic character
v Decimal digit
or it can be a symbol used to represent a class of characters, as follows:
Symbol
Description of Class
= Any character
@ Alphabetic characters
# Numeric characters
$ Special characters
¬ Non-blank characters
. Invalid characters
- Non-numeric characters
< Lowercase alphabetics
> Uppercase alphabetics
Use of picture strings results in either an equal or an unequal condition.

Note: Picture strings can be used only in a search argument or in a

comparison. They cannot be used to specify:
v A PAD value on a COMPARE subcommand
v A MASK value on a COMPARE, EVALUATE, or FIND subcommand or on a
FIND primary command
v A symbolic literal on a LITERAL subcommand
Example 1:
find p’aBc’
Result: IPCS finds the first occurrence of string aBc.
Example 2:
FIND P’¬>’
Result: IPCS finds the first occurrence of a string consisting of a non-blank
character followed by an uppercase letter.
Q‘Q...’

12 z/OS MVS IPCS Commands

 Literal Values

This notation describes an ASCII character string containing one to 256

characters. The value, Q..., is subjected to editing as follows:
v Data entered manually from a terminal may be translated by the TSO/E
Terminal I/O Controller.
v IPCS translates each pair of adjacent apostrophes into a single apostrophe.
v The FIND primary command accepts either ‘ABC’Q or Q‘ABC’ as the same
search value.
v The characters entered are interpreted as ISO-8 ASCII characters and are
limited to those characters for which corresponding EBCDIC graphics are
supported.

Note: Lowercase letters are not translated to uppercase when the search
argument is formed.
Example:
find Q’aBc’

Result: IPCS finds the first occurrence of aBc.

quoted-string
When the FIND primary command is used from the storage panel of IPCS
browse, the character translation currently being employed determines how a
quoted string is interpreted:
v If characters are being shown in EBCDIC, the quoted string is interpreted as
a text string T‘t...’.
v If characters are being shown in ASCII, the quoted string is interpreted as an
ASCII text string S‘...’.
S‘S...’
This notation describes ASCII text strings containing one to 256 characters.
ASCII text strings are phrases without regard to case. Either uppercase or
lowercase is processed. Use of ASCII text strings results in either an equal or
unequal condition.

Note: ASCII text strings may only be used in a search argument or a

comparison. They CANNOT be used to specify:
v A pad value on a COMPARE subcommand.
v A MASK value on a COMPARE, EVALUATE, or FIND subcommand or an a
FIND primary command.
v A symbolic literal on a LITERAL subcommand.
Example:
find s’ABC’
Result: IPCS finds the first occurrence of any of the following possibilities:
v abc
v Abc
v ABc
v ABC
v aBC
v abC
v aBc
v AbC

Chapter 2. Literal values 13

Literal Values

T‘t...’
This notation describes text strings containing one to 256 characters. Text
strings are phrases without regard to case. Either uppercase or lowercase is
processed. Use of text strings results in either an equal or an unequal
condition.

Note: Text strings can be used only in a search argument or in a comparison.

They cannot be used to specify:
v A PAD value on a COMPARE subcommand
v A MASK value on a COMPARE, EVALUATE, or FIND subcommand or on a
FIND primary command
v A symbolic literal on a LITERAL subcommand
Example:
find t’ABC’
Result: IPCS finds the first occurrence of any one of the following possibilities:
v abc
v Abc
v ABc
v ABC
v aBC
v abC
v aBc
v AbC
word
When the FIND primary command is used from the storage panel of IPCS
browse, the character translation currently being employed determines how a
word is interpreted:
v If characters are being shown in EBCDIC, the quoted string is interpreted as
a text string T‘t...’.
v If characters are being shown in ASCII, the quoted string is interpreted as an
ASCII text string S‘...’.
You determine whether characters are shown in EBCDIC or ASCII by using the
EBCDIC and ASCII primary commands.
X‘xx...’
This notation describes a hexadecimal string containing one to 256 characters.
The value, xx..., must contain two hexadecimal digits for each byte described.
For legibility, you can place one or more TSO/E separator characters between
groups of hexadecimal digits, such as:
v Blanks (X‘40’)
v Commas (X‘6B’)
v Tabs (X‘05’)
Each group divided in this manner must describe one or more complete bytes.
*
This notation (the asterisk), which is accepted only by the FIND primary
command in the IPCS dialog, specifies the repetition of the same search value
that was used on the preceding FIND primary command.

14 z/OS MVS IPCS Commands

 Literal Values

Symbols
When an IPCS subcommand accepts a literal value, the value can be entered as a
symbol. The definition of the symbol and the data associated with the symbol are
contained in the dump directory. You can use symbolic literals so that IPCS can
manage many dumps and traces without having to allocate and open the dump
and trace data sets frequently.
v Defining a Symbol
Define a symbol using a LITERAL subcommand. For example:
literal a c’ABCDE’
If the EVALUATE subcommand requests a storage key for a symbolic literal,
IPCS returns the FF value used when the storage key is not available.

Note: IBM does not recommend using a symbolic literal as the basis for indirect
addressing. IPCS will accept such an indirect address and try to resolve it to the
appropriate dumped central storage, but may not be able to resolve it depending
on the dump and the local and global defaults in effect.
If you define a symbol based on a literal symbol, the resulting definition is an
independent copy of the literal data. For instance:
literal a c’X’
equate b a
literal a c’Y’
This sequence leaves symbol A associated with C'Y' and symbol B associated
with C'X', rather than C'Y'. This sequence is consistent with the following
EQUATE subcommands, which leave symbol F with the same definition as
symbol ASVT and symbol G with the same definition as symbol CVT.
equate f cvt
equate g f
equate f asvt
v Referring to a Symbolic Literal
An IPCS command or subcommand refers to the name of the address space
containing the literal as LITERAL and refers to the literal by its symbol. For
example:
literal(a)
v Location of a Symbol
IPCS treats each literal value as residing in the first 1 through 256 bytes of an
address space that it shares with no other literals. Because an address space
contains 231 bytes, most or all bytes in the address space for a symbolic literal
are not available. The following sequence of subcommands associates symbol Y
with an address space in which no bytes are available:
literal x c’Q’
equate y x position(10) length(10) character
Only the first byte of the address space was populated by the LITERAL
subcommand. The EQUATE subcommand tries to define symbol Y with 10 bytes
of storage that are not available.
v System Symbols
System symbols can be used in IPCS command processing. When IPCS sees an
'&' character, it checks the system symbol service to see if there are any symbolic
substitutions to perform.
See What are system symbols? in z/OS MVS Initialization and Tuning Reference for
more information on system symbols.

Chapter 2. Literal values 15

Literal Values

16 z/OS MVS IPCS Commands

Chapter 3. Data description parameter
You describe storage in a dump by using the data description (data-descr)
parameter.

Parts of the data description parameter

The parts of the data-descr parameter are:
v An address (required when data-descr is explicitly specified on a subcommand)
Types of addresses are:
– Symbolic address
– Relative address
– Literal address
– General-purpose register
– Floating-point register
– Indirect address
v Address processing parameters (optional)

To describe an address in: Specify the parameter:

Absolute storage ABSOLUTE
Virtual storage ASID(asid) [CPU(cpu)|NOCPU] [SUMDUMP]
A data space ASID(asid) DSPNAME(dspname) [SUMDUMP]
Physical block number BLOCK(block-number)
Component data COMPDATA(component-id)
Supplementary dump data DOMAIN(domain-id)
The header record HEADER
Relative byte address group RBA
number
Central storage REAL [CPU(cpu)]
One of the CPU status records STATUS [CPU(cpu)]
The physical block TTR(ttr)
A dump source ACTIVE, MAIN, STORAGE, DSNAME(dsname),
DATASET(dsname), FILE(ddname),
DDNAME(ddname), or PATH(hfspath)

v An attribute parameter (optional)

To describe an address in: Specify the parameter

An area AREA
A bit string BIT or HEXADECIMAL
A character string CHARACTER
A signed binary number SIGNED
An unsigned binary number UNSIGNED
A pointer POINTER

© Copyright IBM Corp. 1988, 2017 17

Data Description Parameter

To describe an address in: Specify the parameter

A module MODULE
A control block STRUCTURE
A floating point number FLOAT
An instruction stream INSTRUCTION EP(hexadecimal address)
A packed decimal number PACKED
A zoned decimal number ZONED

v Array parameters (optional)

To provide Specify the parameter

An array ENTRIES(xx [:yy])
An array of dimension DIMENSION(nnn) [ENTRY(xx)]
A single entity SCALAR

v A remark parameter (optional)

To provide Specify the parameter

A comment about an address REMARK(‘text’)
No comment NOREMARK

Address, LENGTH, and POSITIONS parameters

An address, which is required, and LENGTH and POSITIONS parameters, which
are optional, specify the three properties of the data:
v An address is the logical origin of the data, the address passed between
programs to indicate where it is and thus, the location at which the data is said
to reside.
Depending on the subcommand's syntax, address can be a positional or
keyword parameter.
An example of specifying address as a positional parameter is:
list 54.%% length(9) asid(22)
An example of address as a keyword parameter is:
find address(54.%%) length(9) asid(22)
Address may be expressed as a single address, an address expression, or a range
of addresses.

Note: The DROPMAP, LISTMAP, and SCAN subcommands are exceptions to

the rule that an address is required in a data description. These subcommands
accept address processing parameters without an address and interpret that to
mean all addresses contained within an address space.
v LENGTH is the number of bytes spanned by the data (or a single entry in an
array); its size in IPCS terms.
v POSITIONS is the signed offset between the logical origin of the data and its
physical origin.
Where the offset is negative (as it is with system CVTs, RBs, TCBs, and UCBs),
the data is said to have a prefix.

18 z/OS MVS IPCS Commands

 Data Description Parameter

If the address is a positional parameter, the syntax is as follows:

address[:address] [LENGTH(length)] [POSITIONS(position[:position])]

If the address is a keyword parameter, the syntax is as follows:

{ ADDRESS(address[:address]) }
{ RANGE(address[:address]) }
[ LENGTH(length) ]
[ POSITIONS(position [:position ] ) ]

address [: address]
ADDRESS(address : address )
RANGE(address : address )
address expression
Specify the address as:
v A single address
v A range of addresses
v An address expression
A single address is a symbolic address, relative address, literal address,
general-purpose register, floating-point register, or indirect address.
Example:
list +73
Result: LIST displays a relative address, X‘73’ bytes beyond X, the current
address.
A range of addresses is any pair of addresses, address expressions, and
registers (general-purpose and floating-point), separated with a colon. A range
of addresses includes both end-points of the range. If you specify a range of
addresses and LENGTH, the length of the range overrides the LENGTH value.
Example:
scan range(7819b.:8019b.) asid(6)
Result: SCAN processes only the storage map entries for ASID 6 that originate
between X‘7819B’ and X‘8019B’ inclusive.
An address expression is an address followed by any number of expression
values. An address expression has the format:
address[{%|?}...]±value[{%|?}...]&cont;
[±value[{%|?}...]]
address
A symbolic address, relative address, literal address, indirect address, or
general-purpose register. You cannot use floating-point registers (and it is
not advisable to use general-purpose registers) in an address expression.
For any symbol that has a positive or negative origin point, be sure to use
the +0 displacement for indirect addressing.
value
An address modifier that is either:
v A 1- to 19-digit decimal number followed by the letter N. The N may be
in uppercase or lowercase.

Chapter 3. Data description parameter 19

Data Description Parameter

v A 1- to 16-digit hexadecimal number that is not followed by a period.

Underscores may be used between pairs of hexadecimal digits to
improve legibility.
Value must be preceded by a plus (+) or a minus (-) sign and cannot be the
first value in an address expression. You can use address modifiers with
general-purpose registers but you cannot use address modifiers with
floating-point registers.
Types of addresses
An address can be any one of the following types:
Symbolic address
A symbolic address is a symbol consisting of at least one and no more than
31 characters. The first character must be a letter or the following
characters:
$ (X’5B’)
# (X’7B’)
@ (X’7C’)

The same characters plus the decimal digits, 0 through 9, may be used for
any of the remaining characters.

Note:
1. A symbolic address provides a complete description of a block of
storage to IPCS:
v Address, LENGTH, and POSITIONS parameters
v Address processing parameters
v An attribute parameter
v Array parameters
v A remark parameter
2. A symbolic address can be defined and used by the same IPCS
subcommand if the following conditions are met:
v The symbolic address conforms to IPCS naming conventions. See
Appendix A, “IPCS symbols,” on page 445 for a list of the IPCS
naming conventions supported. The diagnostic guides for other
products that you have installed may supplement this list.
v IPCS is able to associate the symbolic address with the type of
AREA, MODULE, or STRUCTURE required by IPCS naming
conventions. This will occur if, for example, you enter
list ascb1

or you enter
list ascb1 structure(ascb)

It will not occur if you enter

list ascb1 structure
Example:
list x

Result: LIST displays X, the current address.

20 z/OS MVS IPCS Commands

 Data Description Parameter

Relative address
A relative address value can designate a maximum of 16 hexadecimal
digits. Underscores (_) can be used as separators when the value is
entered.
Literal address
Before OS/390® Release 10, a literal address is a maximum of eight
hexadecimal digits. If the initial digit is a letter A through F, the literal
address must end with a period. Otherwise, the period can be omitted.
The maximum address is ‘7FFFFFFF’.
The following list explains valid literal address ranges.
v If the address is absolute, real, or virtual, the address can range from 0
through 264-1.
v If the address is in the status record, the address can range from 0
through 4095.
v If the address is in the dump header record, the address can range from
0 through 4159.
Example:
where fe2b8.
Result: WHERE identifies the area in storage in which the address resides.
Underscores (_) can be used as separators when the value is entered. IPCS
accepts literal addresses beginning with a decimal digit without regard to
the presence of a trailing period.
General-purpose register
A general-purpose register is designated as a decimal integer followed by
an R. The decimal integer can range from 0 through 15.
With OS/390 Release 10 and higher, 64-bits of general-purpose registers are
recorded as part of an unformatted dump. When dumps are produced on
OS/390 Release 10 on processors lacking support for the z/Architecture®
instruction set and 64-bit registers, the fullword values actually available
are prefixed with 32 bits of binary zeros.
Example:
list 0r:15r terminal
Result: LIST displays the contents of all 16 general-purpose registers as
they were at the time of the dump to the terminal.
Floating-point register
A floating-point register is designated as a decimal integer followed by a D
for double precision. The decimal integer can be 0 through 15.
Example:
list 0d:6d
Result: LIST displays the seven floating-point double precision registers in
hexadecimal.

Note:
1. Single precision floating point register notation, a decimal integer
followed by an E, is accepted but interpreted as a reference to the
corresponding double precision floating point register.

Chapter 3. Data description parameter 21

Data Description Parameter

2. Two or three decimal digit values ending in D or E are going to be

interpreted as precise instances of floating point registers, so it is very
important that you end an address with a period if you want it to be
literal.
Indirect address
An indirect address is a symbolic, relative, or literal address, or a
general-purpose register followed by a maximum of 255 percent signs (%)
or question marks (?). The address may include up to a maximum of 255
exclamation points (!) to indicate a 64-bit address value.
Each percent sign, question mark, or exclamation point indicates one level
of indirect addressing. Indirect addressing is a method of addressing in
which one area of dump data is used as the address of other dump data.
The address preceding the percent sign, question mark, or exclamation
point is used to locate a pointer in the dump as follows:
v If the address preceding the percent sign, question mark, or exclamation
point is a symbolic address that describes a pointer, the contents of the
pointer are retrieved from the dump.
v If the address preceding the percent sign, question mark, or exclamation
point is not a symbolic address that describes a pointer, IPCS verifies
that the addressed storage is acceptable for indirect addressing:
– If the addressed storage begins on a fullword or doubleword
boundary, IPCS accepts the fullword or doubleword pointer.
– If not, IPCS checks the data type of the address storage. if the
addressed storage has a data type of POINTER, IPCS accepts the
pointer, even though it does not begin on a fullword or doubleword
boundary.
Once IPCS accepts a pointer, it retrieves the contents of that pointer from
the dump. The pointer is interpreted to form an address as follows:
v If the address is followed by a percent sign, the pointer is interpreted as
a 24-bit address. If a fullword pointer was retrieved from the dump,
nonzero bits in the first byte are set to zeros to form the address.
v If the address is followed by a question mark, the pointer is interpreted
as a 31-bit address. If a fullword pointer was retrieved from the dump,
the initial bit is set to zero to form the address.
v If the address is followed by an exclamation point, the pointer is
interpreted as a 64-bit address.
It is not recommended that you use registers in indirect addresses. For
compatibility with TSO/E TEST, general-purpose registers will be accepted
in an address expression, but the resolution of the expression by IPCS will
generally prove unsatisfactory. You cannot use floating-point registers in an
address expression.
LENGTH(length)
The length of the area beginning at the specified address. The length can be
specified in decimal (nnn), hexadecimal (X‘xxx’), or binary (B‘bbb’) notation.
The following list explains valid address length ranges.
v If the address is absolute, real, or virtual, the length can range from 1
through 264-1.
v If the address is in the status record, the length can range from 1 through
4096.

22 z/OS MVS IPCS Commands

 Data Description Parameter

v If the address is in the dump header record, the length can range from 1
through 4160.
If you specify the LENGTH parameter and a range of addresses, the length of
the range overrides the LENGTH value. If the length exceeds the upper limit
for an addressing mode, the length is adjusted to include the last valid address
for that addressing mode.
If you omit the LENGTH parameter, the subcommand uses the default length.

Note: When STRUCTURE(cbname) attribute parameter is specified, IPCS can

supply a preferred length that overrides the default length. See “Attribute
parameters” on page 29 for more details.
Example:
equate abc a72f4. length(80) area
Result: EQUATE creates a symbol table entry for symbol ABC associating it
with an 80-byte area beginning at X‘A72F4’.
POSITIONS(position[:position])
The offset of the initial and, optionally, the final byte of the area. The offsets
can be specified in signed decimal ([+ | -]nnn or F‘[+ | -]nnn’), signed
hexadecimal (X‘[+ | -]xxx’), signed binary (B‘[+ | -]bbb’).
Example 1:
list 400. position(30) length(10) structure
Result: LIST displays locations X‘41E’ (decimal 1054) through X‘427’. IPCS uses
offset caption +0000001E for the line of storage displayed.
Example 2:
list asvt positions(512:519)
Result: LIST displays the cross section of the ASVT containing fields
ASVTASVT and ASVTMAXU. The ending position is an alternate means to
designate the length of the storage.
Example 3:
list +5 position(0) length(5)
Result: LIST performs the following steps:
1. The definition of the current symbol, X, is retrieved.
2. The POSITION(0) specification in conjunction with the explicit offset
specification, +5, causes 5 to be added to the address of X before 0 is stored
as a new offset.
3. The LENGTH(5) specification causes the updated definition of X to be
stored with a length of 5 bytes.
4. The 5 bytes of storage are displayed.
This combination of explicit offset and the POSITION parameter can be used to
move down (or up) within storage, in increments.

Address processing parameters

Address processing parameters are optional. They describe an address space within
which the data to be processed resides.

Chapter 3. Data description parameter 23

Data Description Parameter

Note: Address processing parameters DSNAME, FILE, BLOCK, and RBA are the
only address processing parameters you can use when referencing VSAM data sets.

[ ABSOLUTE ]
[ ASID(asid) [CPU(cpu)|NOCPU] [SUMDUMP] ]
[ ASID(asid) DSPNAME(dspname) [SUMDUMP] ]
[ BLOCK(block-number) ]
[ COMPDATA(component-id) ]
[ DOMAIN(domain-id) [CPU(cpu)] ]
[ HEADER ]
[ RBA [(0|rba-group)] ]
[ REAL [CPU(cpu)] ]
[ STATUS [CPU(cpu)] ]
[ TTR(ttr) ]
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(hfspath) ]

ABSOLUTE
The storage at the address or address range is in absolute storage in a system
dump or ACTIVE storage (that is, the LPAR in which IPCS is running).
Access to the absolute storage in ACTIVE requires READ authority to
FACILITY class resource BLSACTV.SYSTEM. Without such authority, all
ABSOLUTE storage are treated as inaccessible.
ASID(asid)
The storage at the address or address range is in an address space or a data
space. IPCS accesses the storage differently, depending on the type of
information source:
v For dumps, IPCS accesses address spaces using a valid ASID.
v For ACTIVE storage, IPCS accesses storage from the system where it is
executing on demand as an enabled application. Access to sensitive storage
is restricted by proper authority to FACILITY class resources
BLSACTV.ADDRSPAC or BLSACTV.SYSTEM. See supported keywords for
more discussions about the FACILITY class authority.
v For stand-alone dumps, IPCS simulates dynamic address translation or
central storage prefixing, depending on the parameter you specify. (See the
descriptions for the CPU and NOCPU parameters.)
The ASID can range from 1 through 65,535. You can specify the ASID in
decimal, hexadecimal (X'xxx'...), or binary (B'bbb'...).
Example:
equate abc a72f4. asid(1) length(80) area
Result: EQUATE creates a symbol table entry for symbol ABC, associating it
with an 80-byte area beginning at X‘A72F4’. ASID(1) indicates that this address
is in virtual storage and IPCS simulates dynamic address translation.
BLOCK(block-number)
The storage at the address or address range is in physical block number
“block-number” as follows:
BLOCK(0) is the first physical block.
BLOCK(1) is the second physical block.
BLOCK(2) is the third physical block.

24 z/OS MVS IPCS Commands

 Data Description Parameter

BLOCK(3)
. is the fourth physical block.
.
.

The block number can range from 0 through 224-1. You can specify the block
number in decimal, hexadecimal (X'xxx...'), or binary (B‘bbb...’).
For VSAM data sets, BLOCK(0) is the first control interval, BLOCK(1) is the
second, and so on.
COMPDATA(component-id)
The storage supplied as part of a dump to facilitate analysis of a specific
component. Use the LISTDUMP subcommand to find the COMPDATA records
available in a dump. For example, the stand-alone dump program can produce
the following COMPDATA records:
AMDSAMSG
Requests display of messages displayed at the operator's console during
the dumping process.
AMDSA001 - AMDSA005
Request display of self-dump information from stand-alone dump when it
detects errors in its own processing.
AMDSA009
Request display of internal control blocks used by stand-alone dump
during its processing.

See z/OS MVS Diagnosis: Tools and Service Aids for more information about
stand-alone dump COMPDATA records.

Records written by a stand-alone dump use component-ids that begin with the
same prefix characters as that component's module names (“AMDSA”). This is
true for all IBM-supplied components.
CPU(cpu)
The storage within the CPU address that provides the context for the ASID,
DOMAIN, REAL, or STATUS parameter. The CPU parameter applies only to
stand-alone dumps.
v For the ASID and REAL parameters, this is the processor whose prefix
register is used when IPCS simulates prefixing.
v For the STATUS parameter, this is the processor whose registers were saved
by a store-status operation during the dumping of the operating system.
The CPU address can range from 0 to 63 and may be specified in decimal,
hexadecimal (X‘xxx...’), or binary (B‘bbb...’). If you specify this parameter and
omit ASID, REAL, and STATUS, the subcommand uses the default ASID. See
supported keywords for more details.
DOMAIN(identifier)
The dump storage that supplements the storage pages that record system
status. The valid domain-ids are:
DOMAIN(VECTOR)
The vector registers recorded by stand-alone dump. Stand-alone dumps
might contain vector registers that are for each processor in the
configuration. If you do not use the CPU parameter to specify the address
of the CPU containing vector records you want, IPCS uses a default CPU
address.

Chapter 3. Data description parameter 25

Data Description Parameter

DOMAIN(SDUMPBUFFER)
The diagnostic data in the SDUMP buffer. The requester of a
system-initiated dump puts the data in the SDUMP buffer.
DOMAIN(SUMDUMP)
The highly volatile diagnostic data that is useful for problem
determination.
DSPNAME(dspname)
The data space dspname that is associated with the specified ASID. If the dump
is not a stand-alone dump, and the DSPNAME and SUMDUMP parameters are
specified or are the default, IPCS accesses only that data space information
which was collected in DOMAIN(SUMDUMP) records.
As of z/OS V1R9, IPCS users can access data spaces via ACTIVE storage:
v Without special authority, the data spaces that are visible to an authorized
application can be accessed.
v Authority to the FACILITY class resources BLSACTV.ADDRSPAC and
BLSACTV.SYSTEM can provide access to the data spaces that are not
directly accessible by an authorized application.
HEADER
The storage at the address or address range is in the header record for a
system dump or ACTIVE storage. When you use this parameter, the
subcommand accesses data in the header record from offset 0. That is, the
subcommand processes data in the header record at the address you specify.
NOCPU
The storage at the address or address range is in virtual storage in a system
stand-alone dump. IPCS is to simulate dynamic address translation and use the
results to directly access absolute storage without the use of prefix registers. If
you specify the NOCPU parameter and omit ASID, the subcommand uses the
default ASID.
RBA[(0|rba-group)]
The storage at the address or address range is in relative byte address group
number “rba-group.” Each relative byte address group consists of up to 231
bytes from a data set as follows:
v RBA(0) contains the first 231 bytes.
v RBA(1) contains the second 231 bytes.
v RBA(2) contains the third 231 bytes.
v RBA(3) contains the fourth 231 bytes.
.
.
.

Note: IPCS interprets RBA(0) (or just RBA) as the first 264 bytes of a data set.
The group number can range from 0 through 224-1 If the group number is
omitted, it defaults to 0. You can specify the group number in decimal,
hexadecimal (X‘xxx...’), or binary (B‘bbb...’).
For VSAM data sets, IPCS masks the boundaries between control intervals,
allowing them to be referenced as part of a single address space.
REAL
The storage at the address or address range is in central storage in a system
stand-alone dump. IPCS is to simulate prefixing for the specified or current
default CPU. If you specify the REAL parameter and omit the CPU parameter,
the subcommand uses the default CPU.

26 z/OS MVS IPCS Commands

 Data Description Parameter

STATUS
The storage at the address or address range is in one of the CPU status records
in a system stand-alone dump. Stand-alone dumps contain a CPU status record
for each CPU that was active on the system at the time of the dump. The CPU
status record for a particular CPU contains an image of a 4096-byte prefixed
save area (PSA) just after a STORE STATUS operation was performed from the
CPU to the PSA. The status information stored by the STORE STATUS
operation includes the current PSW and the general registers. IPCS supports
access to each CPU's status as a 4096-byte CPU status address space.
When you use STATUS, the parameter accesses data in the status records from
offset eight. That is, the parameter processes data in the status record eight
bytes beyond the address you specify. See the AMDDATA mapping macro for
more information.
If you specify this parameter and omit CPU, the subcommand uses the default
CPU.
Example:
list 100 status cpu(0) length(8)
Result: LIST displays the PSW that is placed in the store status record at X‘100’
of a stand-alone dump.
SUMDUMP
The dump storage containing the DOMAIN(SUMDUMP) records, provided
that the dump is not a stand-alone dump. For dumps other than stand-alone
dumps, the SUMDUMP parameter can be specified or may be the default.

Note: The SUMDUMP parameter does not apply to stand-alone dumps.

TTR(ttr)
The storage at the address or address range is in the physical block that has
the relative track and record address of “ttr”. The value of ttr can range from 0
through 224-1. You can specify the ttr in decimal, hexadecimal (X‘xxx...’), or
binary (B‘bbb...’).
ACTIVE or MAIN or STORAGE
DSNAME(dsname) or DATASET(dsname)
FILE(ddname) or DDNAME(ddname)
Specifies the source that contains the address space or address range. If one of
these parameters is not specified, IPCS uses your current source.

Note: Do not use these parameters for:

v Volatile common or private storage
v Prefixed storage
ACTIVE or MAIN or STORAGE specifies that the address or address range is
in the central storage in which IPCS is currently running.
A header record similar to those used for system dumps is supplied by IPCS to
enable common dump analysis programs to function.
Storage is accessed incrementally on demand, and IPCS generally remains
enabled. As a result, ACTIVE storage might be subject to frequent changes,
which can prevent the analysis programs from producing useful results.
ABSOLUTE, ASID, DSPNAME, and HEADER keywords are supported. Access
to sensitive storage areas, such as ABSOLUTE, is limited using facility classes.
When the user does not have the authority, the access attempts are handled as
though the storage in question was not included in a dump.

Chapter 3. Data description parameter 27

Data Description Parameter

With no special authority, IPCS can access the following storage:

v The common and private storage in its own ASID visible to a key 8
application
v The data spaces owned by its own ASID and visible to a key 8 application
Before z/OS V1R9, no data space access was supported.
With read authority to facility class BLSACTV.ADDRSPAC, IPCS can look at
the following storage (in addition to those storage areas it can access with no
special authority) :
v The common and private storage visible to a key 0 application
v All data spaces owned by its own ASID
Before z/OS V1R9, no data space access was supported.
With read authority to facility class BLSACTV.SYSTEM, IPCS can look at the
following storage (in addition to those storage areas it can access with no
special authority) :
v The ABSOLUTE storage
v Other ASIDs
v The data spaces owned by other ASIDs
BLSACTV.SYSTEM support was added in z/OS V1R9.

Note: IPCS artificially attributes CADS ownerships to ASID(1) as it also does

for the page frame table space, ASID(1) DSPNAME(IARPFT). Consistent with
this perspective BLSACTV.SYSTEM authority is required to access these data
spaces.
DSNAME or DATASET specifies that the address or address range is in the
cataloged data set dsname.
For VSAM data sets, you can:
v Access the data portion of the cluster by:
– Specifying the cluster data set name for dsname
– Specifying the optional data portion data set name for dsname
– Specifying dsname in pseudo-PDS notation, providing a member name of
“data”, as in
DSNAME(vsam.cluster.dsname(data))
v Access the index portion of the cluster by:
– Specifying the optional index portion data set name for dsname
– Specifying dsname in pseudo-PDS notation, providing a member name of
“index”, as in
DSNAME(vsam.cluster.dsname(index))
FILE or DDNAME specifies that the address or address range is in the data set
ddname.
z/OS UNIX files can be referenced with this notation.
v Those z/OS UNIX files whose size is a multiple of 4160 bytes will be treated
as z/OS unformatted dumps.
v No trace formatting support is provided for GTF or component traces that
have been copied into z/OS UNIX files.
v RBA access is supported for any z/OS UNIX file.

28 z/OS MVS IPCS Commands

 Data Description Parameter

For VSAM data sets, allocate the data or index portions of the VSAM cluster to
use the FILE parameter in pseudo-PDS notation. For example, specify
FILE(vsam.cluster.dsname(data)) or FILE(vsam.cluster.dsname(index)).
Specifying the name of the required portion with the DSNAME parameter
instead avoids allocating the portions.
PATH(hfspath)
Specifies a valid path name.
v You can reference path names directly. There is no need to associate a path
with a ddname before asking IPCS to process a z/OS UNIX file path.
v Fully qualified path names are limited to 44 characters. Enclosing
apostrophes or quotation marks are not counted toward the limit.
v You can use partially-qualified path names. IPCS will determine the
fully-qualified names.
You can enter PATH as follows:
PATH(‘/pathname’)
PATH(“/pathname used in IPCS dialog”)
You can always enter path names within apostrophes. Quotation marks can
be used as an alternative to apostrophes when supplying a source name to
the defaults or browse options of the IPCS dialog. The rules for entering a
path name within quotation marks are standard:
v If the path name contains an apostrophe and you used that punctuation
to delimit the name, two adjacent apostrophes need to be entered.
v If the path name contains a quotation mark and you used that
punctuation to delimit the name, two adjacent quotation marks need to
be entered.
Always use quoted string notation when your path name contains blanks,
commas, horizontal tabulation characters (EBCDIC X'05'), apostrophes
(single quotation marks), or quotation marks.
PATH(/x/y/z)
Quoted string notation is not always required. You can enter most path
names without enclosing them with punctuations.
PATH(partially-qualified-name)
IPCS accepts existing z/OS UNIX file paths that can be qualified when
they are entered, as if the fully-qualified name had been entered.

Note: Path names are case-sensitive. Path names “/ABC”, “Abc”, and “abc”
refer to three different paths.

Attribute parameters
Attribute parameters are optional. They designate the type of data and thus, the
way IPCS should format the storage in which the data resides. If you omit all
attribute parameters, the default is AREA.

Chapter 3. Data description parameter 29

Data Description Parameter

[ AREA[(name)] ]
[ BIT | B | HEXADECIMAL | X ]
[ CHARACTER | C ]
[ FLOAT ]
[ INSTRUCTION [EP(hex address)] ]
[ MODULE[(name)] ]
[ PACKED ]
[ POINTER | PTR ]
[ SIGNED | F ]
[ STRUCTURE[(cbname)] ]
[ UNSIGNED ]
[ ZONED ]

AREA[(name)]
The storage indicated by the address or in the range is an area of storage (a
subpool, a buffer, and so on.) that is not a module or control block.
If you display or print the area, each line contains four or eight words,
depending on line width, in hexadecimal format followed by their character
equivalent. This parameter is frequently used when creating a symbol table
entry for the storage at the address or in the address range. The symbol table
entry is created with the specified length parameter.
If you specify a name, IPCS automatically creates a storage map entry for it.
The name can be a maximum of 31 alphanumeric characters and the first
character must be alphabetic. To determine the length of the storage map entry,
IPCS will first check a list of known lengths from parmlib and other sources. If
the Area name is unknown to IPCS, IPCS will use the session default length
established by SETDEF. The storage map entry is used by IPCS for WHERE
processing.
Example 1:
equate abc a72f4. asid(1) length(80) area
Result: EQUATE creates a symbol table entry for symbol ABC associating it
with an 80-byte area beginning at X‘A72F4’. ASID(1) indicates that this address
is in virtual storage. No storage map entry is created for symbol ABC.
Example 2:
setdef length(x’100’)
equate abc a72f4. asid(1) length(80) area(ABC)

ABC is not a recognized structure by IPCS.

Result: EQUATE creates a symbol table entry for symbol ABC associating it
with an 80-byte area beginning at X'A72F4'. ASID(1) indicates that this address
is in virtual storage. A storage map entry is created beginning at address
X'A72F4' for length x'100' because ABC is not recognized by IPCS.
BIT or HEXADECIMAL
The storage indicated by the address or in the address range is bit string data.
If you display or print the data, it is shown in hexadecimal format. B or X is
the abbreviation.
CHARACTER
The storage indicated by the address or in the address range is character string
data. If you display or print the data, it is shown in character format. C is the
abbreviation.
Example:
list abc+80n length(20) c

30 z/OS MVS IPCS Commands

 Data Description Parameter

Result: LIST displays a 20-byte field following a symbolic address in character

format.
FLOAT
The storage indicated by the address or in the address range is a floating point
number or numbers. If you display or print the data, it is shown as a string of
hexadecimal digits.
If you specify LENGTH, it must be 4, 8 or 16. If you specify any other value,
the subcommand changes the attribute to AREA. If you omit the length
parameter, the subcommand uses the length associated with the symbol, if you
used one, or the default length. If this length is not 4, 8 or 16, the subcommand
changes the length to the nearest shorter length, if possible, or to 4 otherwise.
INSTRUCTION [EP(hex address)]
The storage indicated by the address or in the address range is an instruction
stream. If you display or print the data, the output format depends on HLASM
services that provide formatting support. Only contiguous streams of
instructions guarantee correct formatting.
Example: Use the LIST subcommand to display the instruction stream at the
given address EP9:
list ep9 instr
Result: Figure 1 shows the output of the LIST subcommand.

EP9
LIST 02CC48. ASID(X’01AA’) LENGTH(X’69’) INSTRUCTION
0002CC48 | 90EC D00C | STM R14,R12,X’C’(R13)
0002CC4C | 18CF | LR R12,R15
0002CC4E | 41F0 0000 | LA R15,X’0’
0002CC52 | 5800 C19C | L R0,X’19C’(,R12)
0002CC56 | 5890 1000 | L R9,X’0’(,R1)
0002CC5A | 58F0 93E4 | L R15,X’3E4’(,R9)
0002CC5E | 0DEF | BASR R14,R15
0002CC60 | 18FD | LR R15,R13
0002CC62 | 18D1 | LR R13,R1
0002CC64 | 50F0 D004 | ST R15,X’4’(,R13)
0002CC68 | 50D0 F008 | ST R13,X’8’(,R15)
0002CC6C | 98F1 F010 | LM R15,R1,X’10’(R15)
0002CC70 | D207 D048 1000 | MVC X’48’(X’8’,R13),X’0’(R1)
0002CC76 | 58B0 94F0 | L R11,X’4F0’(,R9)
0002CC7A | 58A0 D04C | L R10,X’4C’(,R13)
0002CC7E | 5860 B01C | L R6,X’1C’(,R11)
0002CC82 | 5850 A018 | L R5,X’18’(,R10)
0002CC86 | 1556 | CLR R5,R6

Figure 1. Example output from LIST subcommand

You can use the optional EP(hex address) parameter to give IPCS an address
of the beginning of a module. In this case, an additional column containing the
relative address of every instruction from the beginning of the module will be
displayed.
Example: Use the LIST subcommand to display the instruction stream at the
given address 000007AE and the address of the beginning of the module
000007B8:
list 000007AE length(x’64’) instr EP(000007B8)
Result: Figure 2 on page 32 shows the output of the preceding LIST
subcommand.

Chapter 3. Data description parameter 31

Data Description Parameter

LIST 07AE. ASID(X’0005’) LENGTH(X’64’) INSTRUCTION

000007AE | ____ | 1B50 | SR R5,R0
000007B0 | ____ | 55F0 07E4 | CL R15,X’7E4’
000007B4 | ____ | 4740 07BC | BC X’4’,X’7BC’
000007B8 | 0000 | 41F0 0030 | LA R15,X’30’
000007BC | 0004 | 5EF0 07E0 | AL R15,X’7E0’
000007C0 | 0008 | ACFB 04A3 | STNSM X’4A3’,X’FB’
000007C4 | 000C | 58F0 F000 | L R15,X’0’(,R15)
000007C8 | 0010 | 0CEF | BASSM R14,R15
000007CA | 0012 | AD04 04A3 | STOSM X’4A3’,X’04’
000007CE | 0016 | 18E0 | LR R14,R0
000007D0 | 0018 | 0B0E | BSM 0,R14
000007D2 | 001A LENGTH(X’40’)==>Displayed as AREA
000007D2 LENGTH(X’0E’)==>All bytes contain X’00’

Figure 2. Example output from LIST subcommand (using EP parameter)

MODULE[(name)]
The storage indicated by the address or in the address range is a module. If
you display or print the data, each line contains four or eight words,
depending on line width, in hexadecimal format followed by their character
format. This parameter is frequently used when creating a symbol table entry
for the storage indicated by the address or in the address range.
If you omit the name, the storage is given the attribute of MODULE to
distinguish it from AREA and STRUCTURE.
If you specify a name, IPCS automatically creates a storage map entry for it.
The name can be a maximum of 31 alphanumeric characters and the first
character must be alphabetic.
PACKED
The storage indicated by the address or in the address range is a signed
packed decimal number or numbers. If you display or print the data, it is
shown as a string of hexadecimal digits.
If you specify LENGTH, it must be 1 through 16. If you specify any other
value, the subcommand changes the attribute to AREA. If you omit the length
parameter, the subcommand uses the length associated with the symbol, if you
used one, or the default length. If this length is greater than 16, the
subcommand changes the length to 16.
POINTER
The storage indicated by the address or in the address range is a pointer or
pointers. If you display or print the data, it is shown in hexadecimal format.
If you specify LENGTH, it can range from 1 through 4. If you specify any
other length, the subcommand changes the attribute to AREA.
If you omit the length, the subcommand uses the length associated with the
symbol, if you used one, or the default length. If this length exceeds four, the
subcommand uses a length of four. PTR is the abbreviation.
SIGNED or F
The storage indicated by the address or in the address range is a signed binary
number or numbers. If you display or print the data, it is shown as a signed
number or numbers translated to decimal.
If you specify LENGTH, the length must be two or four. If you specify any
other value, the subcommand changes the attribute to AREA.
If you omit the length parameter, the subcommand uses the length associated
with the symbol, if you used one, or the default length. If this length is not

32 z/OS MVS IPCS Commands

 Data Description Parameter

two or four, the subcommand changes lengths of one or three to two and
changes lengths greater than four to four. F is the alias.
STRUCTURE[(cbname)]
The storage indicated by the address or in the address range is a control block.
If you display or print the data, each line contains four or eight words,
depending on line width, in hexadecimal format followed by their character
format. This parameter is frequently used when creating a symbol table entry
for the storage indicated by the address or in the address range.
If you omit cbname, the storage is given the attribute STRUCTURE to
distinguish it from AREA and MODULE. No storage map entry is created.
If you specify a cbname, IPCS automatically creates a storage map entry for it
to assess whether the instance of STRUCTURE(cbname) that you have
identified is a usable one, and to supply a preferred length that overrides the
default length. (An explicit LENGTH or range supplied in the data description
can, in turn, override the preferred length for the symbol entry but not the
storage map entry.) The following sources of this information are consulted,
selecting the first one listed.
1. A scan exit routine is used.
2. A model is used if one is available and the model has described a control
block identifier and a control block length.
3. A table of z/OS data area lengths is consulted regarding a default data
length.
4. The default data length established by SETDEF is used.
5. Storage map entries are used in WHERE processing.
The CBFORMAT subcommand requires specification of the STRUCTURE
parameter, except with its own MODEL and FORMAT parameters. The
CBSTAT subcommand always requires the STRUCTURE(cbname) parameter.
The parameter may be omitted for either, however, if the referenced symbol
already exists in the symbol table and if the referenced symbol contains the
attribute STRUCTURE(cbname).
The CBSTAT subcommand can use another value, STORESTATUS, in place of
cbname. See “CBSTAT subcommand — obtain control block status” on page 78
for a description and an example.
Example 1:
cbstat 7fa030. structure(tcb)
Result: CBSTAT displays the status for the TCB control block at the given
address.
Example 2:
equate mytcb 522c0. structure(tcb)
Result: EQUATE explicitly verifies that the storage at X‘522C0’ is a TCB and
makes a symbol table entry for MYTCB and a storage map entry for location
X‘522C0’. The storage map entry and symbol table entry use the length from
the IBM supplied TCB formatter. In verifying the TCB, IPCS checks various
pointers in the TCB to other control blocks, such as RBs, CDEs, an so on. In the
process, these control blocks may also be validated and entered in the storage
map but not in the symbol table.
Example 3:
setdef length(x’0F00’)
equate nick 10000. structure(nick) length(x’1000’)

Chapter 3. Data description parameter 33

Data Description Parameter

NICK is not a recognized structure by IPCS.

Result: EQUATE creates a storage map entry at x'10000' but is unable to locate
a formatter for NICK. The entry is created with the SETDEF length of X'0F00'.
A symbol table entry is then created for symbol nick at X'10000' using the
defined length parameter x'1000'.
UNSIGNED
The storage indicated by the address or in the address range is an unsigned
binary number or numbers. If you display or print the data, it is shown as an
unsigned number or numbers translated to decimal.
If you specify LENGTH, it can range from one through four. If you specify any
other length, the subcommand changes the attribute to AREA.
If you omit the length, the subcommand uses the length associated with the
symbol, if you used one, or the default length. If this length exceeds four, the
subcommand uses a length of four.
ZONED
The storage indicated by the address or in the address range is signed zoned
decimal number or numbers. If you display or print the data, it is shown as a
string of hexadecimal digits.
If you specify LENGTH, the length must be 1 through 31. If you specify any
other value, the subcommand changes the attribute to AREA. If you omit the
length parameter, the subcommand uses the length associated with the symbol,
if you used one, or the default length. If this length is greater than 31, the
subcommand changes the length to 31.

Array parameters
Array parameters are optional. They indicate whether the data consists of a single
item (SCALAR) or consists of adjacent, similar items (ENTRIES).

[ ENTRIES(xx[:yy]) ]
[ [DIMENSION(nnn) | MULTIPLE(nnn)] [ENTRY(xx)] ]
[ SCALAR ]

ENTRY(xx[:yy]) or ENTRIES(xx[:yy])
The storage indicated by the address or in the address range is an array. You
specify the number of elements in the array with the values xx and yy. The
value xx must be less than or equal to yy. These values can range from -231 to
231-1 and can be specified using signed decimal ([+|-]nnn), hexadecimal
(X‘[+|-]xxx’, or binary (B‘[+|-]bbb’). (Plus is the default.) The size of the total
array is the length of storage in the specified address range or specified with
the LENGTH parameter, multiplied by the number of array elements.
The number of elements in the array can range from -263 to 263-1. The
difference between the lower and the upper values can be no more than 15
decimal digits.
If you specify an array whose size exceeds the upper limit for the addressing
mode, the subcommand changes the array to a scalar and adjusts its length to
include the last valid address for that addressing mode. If you specify ENTRY
or ENTRIES and SCALAR, the subcommand uses the SCALAR parameter and
ignores ENTRY or ENTRIES.
Example:

34 z/OS MVS IPCS Commands

 Data Description Parameter

list 7FFFD018. length(4) entries(6:10)

Result: Assuming that you have located a segment table at X‘7FFFD000’, LIST
displays five segment table entries beginning at X‘7FFFD018’ (each segment
table entry is four bytes). The total length of the five entries is 20 bytes.
DIMENSION(nnn) or MULTIPLE(nnn)
The storage indicated by the address or in the address range is an array of
dimension nnn. The number nnn can be a maximum of 231 and can be
specified in decimal, hexadecimal (X‘xxx...’), or binary (B‘bbb...’). Each array
element occupies the length of storage in the specified address range or the
length specified with the LENGTH parameter. The total size of the array is the
size of an element, multiplied by nnn. The dimension may be no longer than
15 decimal digits.
If you specify an array whose size exceeds the upper limit for the addressing
mode, the subcommand changes the array to a scalar and adjusts its length to
include the last valid address for that addressing mode.
Example:
equate sgt001 5d7c00. absolute length(4) dimension(256)
Result: Assuming that the master segment table is located at X‘5D7C00’ in
absolute storage with a length of 4 and a dimension of 256, EQUATE defines
the master segment in the symbol table with these attributes.
SCALAR
The storage indicated by the address or in the address range is a single entity
with non-repeating fields. If you omit all array and scalar parameters, the
default is SCALAR.
If you specify SCALAR and either ENTRY or ENTRIES, the subcommand uses
the SCALAR parameter and ignores ENTRY or ENTRIES.
Example:
list a72f4. asid(1) length(x’50’) area scalar
Result: LIST displays the storage as a single entity of non-repeating fields,
beginning at the absolute address X‘A72F4’ for a length of 80 (X‘50’) bytes.

Remark parameters
Remark parameters are optional. They associate a description with the data
consisting of up to 512 characters of text.

[ REMARK(’text’) | NOREMARK ]

REMARK(text)
A textual description of the storage indicated by the address or in the address
range. The description must be entered within apostrophes, and any
apostrophes which appear within the description must be paired. The text can
be a maximum of 512 characters. The remark is stored in the symbol table.
Example:
equate abc a72f4. asid(1) length(80) area scalar +
remark(’input params from EXEC statement’)
Result: IPCS creates a symbol table entry for the symbol ABC. EQUATE
associates the entry with an 80-byte area beginning at the absolute address,
X‘A72F4’. The ASID(1) indicates that this address is in virtual storage and IPCS

Chapter 3. Data description parameter 35

Data Description Parameter

simulates dynamic address translation for ASID(1). AREA indicates that the
symbol is neither a module nor a control block. SCALAR indicates that the
symbol is a single block of storage, not an array. REMARK is your description
of the 80-byte area.
NOREMARK
No textual description is to be associated with the storage. This parameter may
be used when equating a new symbol to one previously defined. It will
prevent IPCS from copying the remark text stored with the existing symbol.
Example:
equate abc+73 asid(1) length(80) area scalar +
noremark
Result: Assuming symbol, ABC, already exists in the symbol table, EQUATE
overlays the new address and attributes for ABC but does not delete the
existing remark.

36 z/OS MVS IPCS Commands

Chapter 4. TSO/E commands
This chapter describes the TSO/E commands that perform IPCS functions. It also
describes those TSO/E commands that have special considerations when they are
entered from an IPCS session.

Entering TSO/E commands

The following TSO/E commands can be processed at any time during a TSO/E
session. Except for the IPCS command, which starts an IPCS session, you can also
run TSO/E commands during an IPCS session.

To run a TSO/E command whose name does match an IPCS subcommand, use the
IPCS subcommand named TSO (see “TSO subcommand — run a TSO/E
command” on page 322). To run a TSO/E command whose name does not match
an IPCS subcommand, type the command and press ENTER.

Task directory of TSO/E commands for IPCS

Table 5 identifies the TSO/E commands by the tasks they perform.
Table 5. Summary of TSO/E commands and tasks
When you want to Use
Begin an IPCS session “IPCS command — start an IPCS session” on
page 41
Identify libraries of CLISTs and REXX “ALTLIB command — identify libraries of CLISTs
EXECs and REXX EXECs”
Initialize a dump directory “IPCSDDIR command — initialize a user or
sysplex dump directory” on page 42
View dump titles “SYSDSCAN command — display titles in dump
data sets” on page 43
Pass control to TSO command “BLS9 command — session of TSO commands”
processors on page 38
Pass control for a System/370 interface “BLS9CALL command — call a program” on
page 39

ALTLIB command — identify libraries of CLISTs and REXX EXECs

Use the ALTLIB command to identify libraries of CLISTs or REXX EXECs. The
function, operands, and syntax of the ALTLIB command are the same as those
documented in z/OS TSO/E Command Reference. However, the following special
considerations apply for using ALTLIB in an IPCS session.
v Using ALTLIB in the IPCS Dialog
When you activate the IPCS dialog for an ISPF logical screen, the system creates
an ALTLIB environment for IPCS that will be used whenever you ask IPCS to
process a CLIST or REXX EXEC. This ALTLIB environment is separate from the
following ALTLIB environments:
– The ALTLIB environment maintained by ISPF
– The ALTLIB environment maintained by another IPCS dialog logical screen

© Copyright IBM Corp. 1988, 2017 37

TSO/E command ALTLIB

– The ALTLIB environment used in IPCS line mode

To display or update the ALTLIB environment for the IPCS dialog logical screen,
use the following command with appropriate operands:
IPCS ALTLIB
You can also enter ALTLIB without the IPCS prefix from option 4 of the IPCS
dialog. You cannot use the QUIET option of the ALTLIB command. The QUIET
option requires ISPF services, which are not made available to TSO/E
commands by IPCS.
Changes that you make to the ALTLIB environment for that logical screen will
remain in effect until the next ALTLIB command is entered or until you exit the
IPCS dialog.

Note: The following command is a request to display or update the separate

ALTLIB environment maintained by ISPF, not the ALTLIB environment
maintained by the IPCS dialog:
TSO ALTLIB
v Using ALTLIB in IPCS line mode or batch mode
When you use IPCS in line mode or batch mode, IPCS continues to use the same
ALTLIB environment in effect when it received control. ALTLIB commands
entered before the use of IPCS remain in effect. ALTLIB commands entered
during the IPCS session will display or update this environment. This ALTLIB
environment is not affected by ending IPCS.

BLS9 command — session of TSO commands

Use the BLS9 command to pass control to a succession of unauthorized TSO
command processors. A “temporary steplib” can be specified for the duration of
the BLS9 command session.

Authorized TSO commands are supported through linkage that ignores any
TASKLIB data sets in effect for unauthorized commands.
v Related subcommand
– END
v Syntax

BLS9
[ TASKLIB(dsname ...) ]
[ TEST | NOTEST ]

v Operands
TASKLIB(dsname ...)
TASKLIB(dsname) specifies a list of load module libraries to be searched for
unauthorized command processors invoked during the BLS9 session and for
any modules the unauthorized command processors invoke using
system-aided linkages.
TEST
NOTEST
TEST specifies than any ABEND that occurs during a BLS9 session is to be
permitted to continue so that the TSO TEST command can be used.

38 z/OS MVS IPCS Commands

 TSO/E command BLS9

Note: TSO TEST and TSO TMP will describe the situation as “BLS9 ENDED
DUE TO ERROR+” whether the ABEND occurred in BLS9 command
processing or in the processing of a command invoked by the BLS9
command.
NOTEST specifies that the BLS9 command is to intercept and briefly
diagnose any ABEND that occurs during a BLS9 session, allowing a
SYSABEND, SYSMDUMP, or SYSUDUMP data set to be produced to
document the error but blocking the use of TSO TEST.

BLS9CALL command — call a program

Use the BLS9CALL command to pass control to a processing program that expects
the interface established by the IBM System/370 standard linkage conventions.
Such processing programs include assemblers, compilers, and data set utilities
among others.
v Related commands
– ATTCHMVS REXX host command environment
– CALL command of the z/OS TSO/E element
– CALLMVS REXX host command environment
– JCL EXEC PGM=program
v Syntax

BLS9CALL program [ parm ]

[ HEADING(heading) | TITLE(title) | NOHEADING | NOTITLE ]
[ LIBRARY(library ...) | NOLIBRARY ]
[ MEMBER(member) ]
[ PAGE(page) ]
[ STATUS | NOSTATUS ]
[ SYSIN(sysin) ]
[ SYSLIB(syslib) ]
[ SYSLIN(syslin) ]
[ SYSLMOD(syslmod) ]
[ SYSPRINT(sysprint) ]
[ SYSPUNCH(syspunch) ]
[ SYSTERM(systerm) ]
[ SYSUT1(sysut1) ]
[ SYSUT2(sysut2) ]
[ SYSUT3(sysut3) ]
[ SYSUT4(sysut4) ]

v Operands
program
program specifies the 1-8 character name of the command processor to be
given control. The program can reside in a library specified on the
BLS9CALL command, the job pack area, the logon procedure steplib, the
link pack area, or the system link library.
parm
Specifies a character string to be passed to the processing program. Enclose
the character string with apostrophes. If not specified, the default is a null
string.
HEADING(heading)
TITLE(title)
NOHEADING

Chapter 4. TSO/E commands 39

TSO/E command BLS9CALL

NOTITLE
Specifies the heading or title to be passed to the processing program. Enclose
the heading or the title in apostrophes.
LIBRARY(library ...)
NOLIBRARY
Specifies the libraries to be searched before the logon procedure steblib and
the system link library when searching for an unauthorized program and
any modules it invokes using system-aided linkages.

Note: These libraries are not searched when an authorized program is

invoked.
MEMBER(member)
Specifies a member of the SYSLMOD library. The member is typically an
argument passed as a parameter to a linkage editor.
PAGE(page)
Specifies a page number to be passed to the processing program.
STATUS
NOSTATUS
Specifies whether the completion status of the processing program is to be
displayed if the program terminates without an abend. (On abend, the status
always is displayed.)
SYSIN(sysin)
Specifies the file name to be passed to the processing program and used
instead of SYSIN.
SYSLIB(syslib)
Specifies the file name to be passed to the processing program and used
instead of SYSLIB.
SYSLIN(syslin)
Specifies the file name to be passed to the processing program and used
instead of SYSLIN.
SYSLMOD(syslmod)
Specifies the file name to be passed to the processing program and used
instead of SYSLMOD.
SYSPRINT(sysprint)
Specifies the file name to be passed to the processing program and used
instead of SYSPRINT.
SYSPUNCH(syspunch)
Specifies the file name to be passed to the processing program and used
instead of SYSPUNCH.
SYSTERM(systerm)
Specifies the file name to be passed to the processing program and used
instead of SYSTERM.
SYSUT1(sysut1)
Specifies the file name to be passed to the processing program and used
instead of SYSUT1.
SYSUT2(sysut2)
Specifies the file name to be passed to the processing program and used
instead of SYSUT2.

40 z/OS MVS IPCS Commands

 TSO/E command BLS9CALL

SYSUT3(sysut3)
Specifies the file name to be passed to the processing program and used
instead of SYSUT3.
SYSUT4(sysut4)
Specifies the file name to be passed to the processing program and used
instead of SYSUT4.

IPCS command — start an IPCS session

Use the IPCS command to start an IPCS session. IPCS is a TSO/E command that
initializes the IPCS environment. Once the IPCS command is processed, you may
use the IPCS subcommands. Before running the IPCS command, you must allocate
a dump directory.
v Related subcommands
– END
– SETDEF
v Syntax

IPCS
[ PARM(nn|00) | NOPARM ]
[ TASKLIB(dsname) | NOTASKLIB ]

v Operands
PARM(nn|00)
NOPARM
PARM(nn) specifies the member of parmlib that IPCS uses as its
initialization parameters for this session. The first six characters of the
member name are “IPCSPR” and nn is the 2-digit decimal number that is
appended to it. When specifying the number, a leading zero is optional.
The IPCSPRnn member specifies parameters for problem management and
data set management facilities. See z/OS MVS Initialization and Tuning
Reference for the syntax of the IPCSPRnn parmlib member.
NOPARM specifies that no IPCSPRnn member of parmlib should be
accessed for this IPCS session. If NOPARM is specified, IPCS facilities for
problem analysis may be used during the session, but those for problem
management and data set management may not be used.
The default is PARM(00), which causes IPCSPR00 to be used.
TASKLIB(dsname)
NOTASKLIB
TASKLIB(dsname) specifies a list of load module libraries to be searched for
analysis programs. The libraries must be cataloged and will be searched in
the order entered.
NOTASKLIB specifies that only the standard load module libraries should
be searched for analysis programs during the IPCS session.
For example, request that IPCS search the load libraries
IPCSU1.DEBUG.LOAD and IPCSU1.DIAGNOS.LOAD, enter:
ipcs tasklib(’ipcsu1.debug.load’ ’ipcsu1.diagnos.load’)

IPCSU1.DEBUG.LOAD will be searched for programs before data set

IPCSU1.DIAGNOS.LOAD.

Chapter 4. TSO/E commands 41

TSO/E command IPCS

You may enter each data set name using one of the following notations:
– Enter a fully-qualified data set name within apostrophes. For example, to
specify data set IPCSU1.DEBUG.LOAD, enter:
ipcs tasklib(’ipcsu1.debug.load’)
– A data set name beginning with your TSO/E prefix qualifier and ending
with the qualifier “LOAD” may be designated by entering the qualifiers
between them. If your TSO/E prefix is IPCSU1 and you want to specify
data set IPCSU1.DEBUG.LOAD, enter:
ipcs tasklib(debug)
The data set name entered is edited in three ways:
- Lowercase letters are changed to uppercase.
- The TSO/E prefix qualifier is added before the entered name.
- The final qualifier “LOAD” is appended to the name.
– A data set name beginning with your TSO/E prefix qualifier and ending
with the qualifier “LOAD” may also be designated by entering the
qualifiers including the final qualifier. For example, if your TSO/E prefix
is IPCSU1, the following command specifies data set
IPCSU1.DEBUG.LOAD:
ipcs tasklib(debug.load)
The following command specifies data set IPCSU1.LOAD:
ipcs tasklib(load)
The data set name entered is edited in two ways:
- Lowercase letters are changed to uppercase.
- The TSO/E prefix qualifier is added before the name.

IPCSDDIR command — initialize a user or sysplex dump directory

Use the IPCSDDIR command to:
v Initialize a user dump directory or a sysplex dump directory
v Reset a directory to contain only initialization records

To initialize the directory, the IPCSDDIR command writes two records to it: one
with a key of binary zeros (0) and the other with a key of binary ones (1). Once the
directory is initialized, you do not need to reinitialize it.

Initialization of the directory is required before IPCS subcommands can use it.
v Syntax

IPCSDDIR dsname
[REUSE | NOREUSE ]
[CONFIRM | NOCONFIRM ]
[ENQ | NOENQ ]

v Operands
dsname
The name of the data set for the dump directory.
REUSE
NOREUSE
REUSE requests that the system delete all records from the data set and

42 z/OS MVS IPCS Commands

 TSO/E command IPCSDDIR

write the initialization records to the data set. The directory must have the
VSAM REUSE attribute to use this option.
NOREUSE requests that the system write the initialization records to the
data set. When using IPCSDDIR NOREUSE, the data set should contain no
records; if the initialization records are already present, the command will
fail.
CONFIRM
NOCONFIRM
CONFIRM causes the IPCS user to be prompted before IPCS runs a
IPCSDDIR REUSE command.
NOCONFIRM authorizes immediate processing of an IPCSDDIR REUSE
command.
ENQ
NOENQ
ENQ causes IPCSDDIR to serialize access to the dump directory during its
initialization. This is the default and the recommended option.
NOENQ suppresses ENQ processing that is intended to block other
instances of IPCS from using the directory being prepared for use by
IPCSDDIR. IPCS itself uses this option when it has already established the
needed serialization. Manual use of this option is not recommended.
v Return Codes

Code Explanation
00 Successful completion.
04 Attention, command completed with a condition that might be of interest to
the user.
08 Error, command encountered an error condition that might be of interest to
the user.
12 Severe, an error condition or user request forced early end to the command
processing.
16 Ending, an error condition from a called service routine forced an early end
to the processing.

SYSDSCAN command — display titles in dump data sets

Use the SYSDSCAN command to display the titles of the dumps in dump data
sets. The date and time when each dump was produced is included in the display.
v Syntax

SYSDSCAN [ xx [:yy] | 00:09 ]

v Operands
xx[:yy]
Specifies one or a range of SYS1.DUMPnn data sets. xx and yy can be any
positive decimal numbers from 00 through 99. A leading zero is optional and
xx must be less than or equal to yy. If you omit this operand, the default
range is 00:09.
v Return Codes

Chapter 4. TSO/E commands 43

TSO/E command SYSDSCAN

Code Explanation
00 Successful completion.
other Either a nonzero return code from IKJPARS or a nonzero return code from
dynamic allocation.

44 z/OS MVS IPCS Commands

Chapter 5. IPCS subcommands
This topic presents a task directory for and descriptions of the individual IPCS
subcommands.

Entering subcommands
Enter a subcommand as directed by the syntax diagrams. See “Syntax conventions”
on page 6 for more information.
v Entering subcommands in IPCS line mode
Enter a subcommand at the IPCS prompt. For example:
IPCS
ANALYZE CONTENTION
v Entering subcommands from an IPCS batch job
After the batch job has established an IPCS session, you can enter subcommands
as you do from IPCS line mode. The following example shows how to enter a
subcommand from the JCL or TSO/E job stream:
//SYSTSIN DD *
IPCS
ANALYZE CONTENTION
/*
v Entering subcommands from the IPCS dialog
There are two ways to enter subcommands from the IPCS dialog:
– Choose option 4 (COMMAND) and enter the subcommand on the command
line:
===> ANALYZE CONTENTION
– Use the IPCS primary command to prefix the subcommand invocation from
any command or option line of the IPCS dialog. For example:
COMMAND ===> IPCS ANALYZE CONTENTION

Abbreviating subcommands and parameter operands

You can enter subcommands and parameter operands spelled exactly as they are
shown or you can use an acceptable abbreviation (also referred to as an alias).
When abbreviating enter only the significant characters; that is, you must type as
much of the parameter as is necessary to distinguish it from the other parameters.
Most minimal abbreviations are indicated.

Overriding defaults
Some subcommands allow you to override the SETDEF-defined defaults for the
processing of that single subcommand. Once the subcommand completes
processing, the original defaults are in effect.

The syntax diagram will indicate what, if any, SETDEF-defined parameters are
allowed for that subcommand. For an explanation of those parameters, see
“SETDEF subcommand — set defaults” on page 262.

© Copyright IBM Corp. 1988, 2017 45

Online help
During an IPCS line mode or dialog session, you can use the HELP subcommand
to obtain information about any IPCS subcommand. This information includes the
function, syntax, and operands of a subcommand. For example, to get the syntax
and operands of the ANALYZE subcommand, enter:
HELP ANALYZE

Standard subcommand return codes

Most IPCS subcommands use the return codes listed in Table 6. Additional return
codes or special reasons for using the defined return codes are presented with the
description of each subcommand.
Table 6. Standard subcommand return codes and explanations
Code Explanation
00 Successful completion.
04 Attention, subcommand completed with a condition that may be of interest to
you.
08 Error, subcommand encountered an error condition that may be of interest to
you.
12 Severe error, an error condition or user request forced an early end to the
subcommand processing.
16 Ending error, an error condition from a called service routine forced an early
ending of subcommand processing.

Task directory for subcommands

The following tables organize the IPCS subcommands by the tasks they perform.
These tasks are grouped into the following areas:
v “Analyze a dump”
v “View dump storage” on page 47
v “View trace information” on page 47
v “Check system components and key system areas” on page 48
v “Retrieve information in variables” on page 50
v “Maintain the user dump directory or sysplex dump directory” on page 50
v “Perform utility functions” on page 50
v “Debug a dump exit program” on page 51

Analyze a dump
When you want to Use
Check resource contention “ANALYZE subcommand — perform
contention analysis” on page 54
Display access register data “ARCHECK subcommand — format access
register data” on page 66
Display ASCB-related data areas “ASCBEXIT subcommand — run an ASCB
exit routine” on page 69
Display z/OS UNIX System Services (z/OS “OMVSDATA subcommand — format z/OS
UNIX) address spaces and tasks UNIX data” on page 218

46 z/OS MVS IPCS Commands

 When you want to Use
Format selected control blocks “CBFORMAT subcommand — format a
control block” on page 72
Check the status of a control block or unit of “CBSTAT subcommand — obtain control
work block status” on page 78
Search for a module by name “FINDMOD subcommand — locate a
module name” on page 158
Search for a UCB “FINDUCB subcommand — locate a UCB”
on page 160
Display a map of the link pack area “LPAMAP subcommand — list link pack
area entry points” on page 207
Translate an STOKEN “NAME subcommand — translate an
STOKEN” on page 212
Display the token from a name/token pair. “NAMETOKN subcommand — display the
token from a name/token pair” on page 213
Repair data residing in a dump or manage “PATCH subcommand” on page 225
the list of patches in effect for a dump.
Identify address spaces satisfying specified “SELECT subcommand — generate address
selection criteria. space storage map entries” on page 259
Display system status at the time of the “STATUS subcommand — describe system
dump status” on page 273
Display formatted control blocks “SUMMARY subcommand — summarize
control block fields” on page 293
Display TCB-related data areas “TCBEXIT subcommand — run a TCB exit
routine” on page 312
Identify area(s) containing a given address “WHERE subcommand — identify an area
at a given address” on page 361

View dump storage

When you want to Use
Locate data in a dump “FIND subcommand — locate data in a
dump” on page 153
Display storage “LIST subcommand — display storage” on
page 186
Display the eligible device table (EDT) “LISTEDT subcommand — format the
eligible device table (EDT)” on page 194
Display one or more UCBs “LISTUCB subcommand — list UCBs” on
page 203
Search through a chain of control blocks “RUNCHAIN subcommand — process a
chain of control blocks” on page 249

View trace information

When you want to Use
Display component trace data “CTRACE subcommand — format
component trace entries” on page 108

Chapter 5. IPCS subcommands 47

 When you want to Use
Display data-in-virtual trace data “DIVDATA subcommand — analyze
data-in-virtual data” on page 120
Display program control flow “EPTRACE subcommand — using 72-byte
save areas” on page 131
Display GTF trace data “GTFTRACE subcommand — format GTF
trace records” on page 165
Merge several trace data reports “MERGE and MERGEEND subcommands —
merge multiple traces” on page 209
Display trace data in the master trace table “VERBEXIT MTRACE subcommand —
format master trace entries” on page 348
Display system trace entries “SYSTRACE subcommand — format system
trace entries” on page 303

Check system components and key system areas

To obtain a diagnostic report for Use
Advanced Program-to-Program “APPCDATA subcommand — analyze
Communication (APPC) component APPC/MVS component data” on page 62
APPC/MVS transaction scheduler “ASCHDATA subcommand — analyze
APPC/MVS transaction scheduler data” on
page 70
Auxiliary storage manager (ASM) “ASMCHECK subcommand — analyze
component auxiliary storage manager data” on page 72
“VERBEXIT ASMDATA subcommand —
format auxiliary storage manager data” on
page 328
Availability management component “VERBEXIT AVMDATA subcommand —
format availability manager data” on page
328
Communications task component “COMCHECK subcommand — analyze
communications task data” on page 83
Cross-system coupling facility (XCF) “COUPLE subcommand — analyze
cross-system coupling data” on page 105
Cross system extended services (XES) “XESDATA subcommand — format cross
system extended services data” on page 370
Data-in-virtual component “DIVDATA subcommand — analyze
data-in-virtual data” on page 120
Data lookaside facility (DLF) component “DLFDATA subcommand — format data
lookaside facility data” on page 123
Dump analysis and elimination (DAE) “VERBEXIT DAEDATA subcommand —
component format dump analysis and elimination data”
on page 330
Global resource serialization component “VERBEXIT GRSTRACE subcommand —
format Global Resource Serialization data”
on page 331
Information Management System (IMS™) See IMS/ESA® Utilities Reference
product
IMS resource lock manager (IRLM) product See IMS/ESA Utilities Reference or

48 z/OS MVS IPCS Commands

To obtain a diagnostic report for Use
Input/output supervisor (IOS) component “IOSCHECK subcommand — format I/O
supervisor data” on page 173
Job entry subsystem 2 (JES2) component See z/OS JES2 Diagnosis
Job entry subsystem 3 (JES3) component See z/OS JES3 Diagnosis
LOGREC buffer records “VERBEXIT LOGDATA subcommand —
format logrec buffer records” on page 345
MVS message service (MMS) component “VERBEXIT MMSDATA subcommand —
format MVS message service data” on page
348
Modules in the nucleus “VERBEXIT NUCMAP subcommand — map
modules in the nucleus” on page 349
Real storage manager (RSM) component “RSMDATA subcommand — analyze real
storage manager data” on page 233
Stand-alone dump message log “VERBEXIT SADMPMSG subcommand —
format stand-alone dump message log” on
page 353
Storage management subsystem (SMS) See z/OS DFSMSdfp Diagnosis
component
System logger component “LOGGER subcommand — format system
logger address space data” on page 207
System resource manager (SRM) component “VERBEXIT SRMDATA subcommand —
format System Resource Manager data” on
page 353
System symbol table (which is different from “SYMDEF subcommand — display an entry
the IPCS symbol table - it contains system in the system symbol table” on page 303
symbols for general system use)
Subsystem Interface (SSI) component “SSIDATA subcommand — display
subsystem information” on page 272
Structures of the coupling facility “STRDATA subcommand — format coupling
facility structure data” on page 283
SVC summary dump data “VERBEXIT SUMDUMP subcommand —
format SVC summary dump data” on page
354
Symptom string “VERBEXIT SYMPTOM subcommand —
format symptom string” on page 355
Time Sharing Option Extensions (TSO/E) See TSO/E V2 Diagnosis: Guide and Index
product
Virtual lookaside facility (VLF) component “VLFDATA subcommand — format virtual
lookaside facility data” on page 359
Virtual storage manager (VSM) component “VERBEXIT VSMDATA subcommand —
format virtual storage management data” on
page 356
Virtual Telecommunication Access Method See VTAM Diagnosis
(VTAM®) product
Workload manager (WLM) “WLMDATA subcommand — analyze
workload manager data” on page 368

Chapter 5. IPCS subcommands 49

 Retrieve information in variables
When you want to Use
Format IPCS default values “EVALDEF subcommand — format
defaults” on page 135
Format a dump data set name or “EVALDUMP subcommand — format dump
information regarding a dump data set attributes” on page 137
Format information regarding an entry in “EVALMAP subcommand — format a
the storage map for a dump data set storage map entry” on page 140
Format information regarding an entry in “EVALSYM subcommand — format the
the symbol table for a dump data set definition of a symbol” on page 145
Format dump storage or protection keys “EVALUATE subcommand — retrieve dump
data for a variable” on page 149

Maintain the user dump directory or sysplex dump directory

When you want to Use
Add a source description to a dump “ADDDUMP subcommand — add a source
directory description to a dump directory” on page 52
Delete records in a source description from a “DROPDUMP subcommand — delete source
dump directory description data” on page 125
Delete records of control blocks that have “DROPMAP subcommand — delete storage
been located in a dump map records” on page 127
Delete IPCS symbols from the IPCS symbol “DROPSYM subcommand — delete
table symbols” on page 129
Create an IPCS symbol with a user-defined “EQUATE subcommand — create a symbol”
name on page 132
List dumps represented in a dump directory “LISTDUMP subcommand — list dumps in
dump directory” on page 189
List storage map entries “LISTMAP subcommand — list storage map
entries” on page 197
List attributes of symbols in the IPCS “LISTSYM subcommand — list symbol table
symbol table entries” on page 199
Assign a value to an IPCS symbol in the “LITERAL subcommand — assign a value to
symbol table a literal” on page 205
Renumber all stack symbols in the IPCS “RENUM subcommand — renumber symbol
symbol table table entries” on page 232
Validate control blocks “SCAN subcommand — validate system
data areas” on page 257
Create storage map entries for address “SELECT subcommand — generate address
spaces satisfying specified selection criteria space storage map entries” on page 259
Add an IPCS symbol (Znnnnn) to the IPCS “STACK subcommand — create a symbol in
pointer stack the stack” on page 272

Perform utility functions

When you want to Use
Change the dsname of a directory entry “ALTER subcommand — change a name in
the IPCS inventory” on page 53

50 z/OS MVS IPCS Commands

 When you want to Use
End the use of resources by IPCS “CLOSE subcommand — release resources
in use by IPCS” on page 81
Perform logical data comparisons “COMPARE subcommand — compare
dump data” on page 87
Copy records describing a dump data set “COPYDDIR subcommand — copy source
from one dump directory to another description from dump directory” on page
92
Copy dump data from one data set to “COPYDUMP subcommand — copy dump
another data” on page 94
Copy trace data to a data set from one or “COPYTRC subcommand — copy trace
more dump or trace data sets entries or records” on page 101
End an IPCS session “END subcommand — end an IPCS session”
on page 130
Obtain descriptive information about the “HELP subcommand — get information
IPCS command and its subcommands about subcommands” on page 171
Format an integer using decimal digits, “INTEGER subcommand — format or list a
hexadecimal digits, or four EBCDIC number” on page 172
characters
Request ISPF dialog services “ISPEXEC subcommand — request an ISPF
dialog service” on page 186
Produce messages and control spacing and “NOTE subcommand — generate a
pagination message” on page 216
Prepare resources for use by IPCS “OPEN subcommand — prepare resources
for use by IPCS” on page 222
Control session output format “PROFILE subcommand — set preferred line
and page size defaults” on page 228
Set, change, and display IPCS session “SETDEF subcommand — set defaults” on
defaults page 262
Transfer system management facility (SMF) “SMFDATA subcommand — obtain system
records to a preallocated SMF (VSAM) data management facilities records” on page 271
set or log stream
Invoke a non-IPCS TSO/E command or “TSO subcommand — run a TSO/E
subcommand function command” on page 322

Debug a dump exit program

When you want to Use
Resume trap processing from a STOP trap “GO subcommand — resume IPCS trap
processing” on page 161
Display the status of currently active traps “TRAPLIST subcommand — list the status
of IPCS traps” on page 314
Selectively disable traps “TRAPOFF subcommand — deactivate IPCS
traps” on page 316
Selectively enable traps “TRAPON subcommand — activate IPCS
traps” on page 318

Chapter 5. IPCS subcommands 51

ADDDUMP subcommand

ADDDUMP subcommand — add a source description to a dump

directory
Use the ADDDUMP subcommand to add a source description to a dump directory.
The description is for an unformatted source that IPCS can format, for example, an
SVC dump, a stand-alone dump, an SYSMDUMP dump, a trace data set, a data
set, or active storage. The directory is allocated with ddname IPCSDDIR and is
your current dump directory. The current dump directory is your user dump
directory or, for users with write access authority, might be the sysplex dump
directory.

If the source is a dump, IPCS does not initialize it, as this is a process that takes
time. If IPCS can access the dump and it is an unformatted dump from an z/OS
MVS system or an MVS/ESA SP 5.2 or 5.2.2 system, IPCS accesses it to define
symbols for the dump and place them in the symbol table in the record. For
information about the symbol table, see z/OS MVS IPCS User's Guide. IPCS defines
the following symbols, as appropriate; for information about these symbols, see
Appendix A, “IPCS symbols,” on page 445.
v DUMPINGPROGRAM
v DUMPORIGINALDSNAME
v DUMPREQUESTOR
v DUMPTIMESTAMP
v DUMPTOD
v ERRORID
v INCIDENTTOKEN
v PRIMARYSYMPTOMS
v REMOTEDUMP
v SECONDARYSYMPTOMS
v SLIPTRAP
v TITLE
v Related subcommands
– DROPDUMP
v Syntax

ADDDUMP

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE|MAIN|STORAGE ]
[ DSNAME(dsname)|DATASET(dsname) ]
[ FILE(ddname)|DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ TEST | NOTEST ]

v Parameters
ACTIVE or MAIN or STORAGE
DSNAME(dsname) or DATASET(dsname)
FILE(ddname) or DDNAME(ddname)

52 z/OS MVS IPCS Commands

 ADDDUMP subcommand

PATH(path-name)
Specifies the source storage or data set to be represented by the source
description. One of these parameters is required.
ACTIVE, MAIN, or STORAGE specifies central storage.
DSNAME or DATASET specifies a cataloged data set.
FILE or DDNAME specifies the ddname of a data set.
PATH specifies the path of a file or directory on a z/OS UNIX file.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the ADDDUMP subcommand.
v Example: Add a dump to your user dump directory.
– Action
adddump dsname(’sys1.dump.d930428.t110113.system1.s00001’)
– Result
IPCS creates in your user dump directory a source description for the dump
with the data set name of sys1.dump.d930428.t110113.system1.s00001. IPCS
accesses the dump but does not initialize it.

ALTER subcommand — change a name in the IPCS inventory

Use the ALTER subcommand to change the name of a dump or trace data set in an
IPCS dump directory.
v Syntax

ALTER

{DSNAME(dsname)|DATASET(dsname)|FILE(ddname)|DDNAME(ddname)}
NEWNAME({ DSNAME(dsname)|DATASET(dsname)|FILE(ddname)|DDNAME(ddname) }

-------- SETDEF-Defined Parameters -------------------------

Note: You must specify one of the following SETDEF parameters:
{ DSNAME(dsname) | DATASET(dsname) }
{ FILE(ddname) | DDNAME(ddname) }
[ PATH(path-name) ]

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.
[ TEST | NOTEST ]

v Parameters
DSNAME
Designates the current dsname or ddname of the dump or trace.
NEWNAME
Designates the new dsname or ddname of the dump or trace. The ALTER
subcommand does not actually change the name of any data sets, only the
association between dump directory data and a name.
For consistency with the TSO (and IDCAMS) ALTER command, you can use
NEWNM as an abbreviation of the NEWNAME keyword.
The ALTER subcommand requires that the dump whose description is to be
affected be explicitly specified.

Chapter 5. IPCS subcommands 53

ANALYZE subcommand

ANALYZE subcommand — perform contention analysis

Use the ANALYZE subcommand to gather contention information from component
analysis exits and format the data to show where contention exists in the dump.
ANALYZE obtains contention information for I/O, ENQs, suspend locks,
allocatable devices, real frames, global resource serialization latches, and other
resources.

ANALYZE produces different diagnostic reports depending on the report type

parameter or parameters. Specify one or more of these parameters to select the
information you want to see. If you do not specify a report type parameter, you
receive an EXCEPTION report.
v EXCEPTION displays contention information when a unit of work holds at least
one resource for which contention exists and that unit of work is not waiting for
another resource.
When applicable, ANALYZE displays a resource lockout report following the
EXCEPTION report when a unit of work holds a resource and is waiting for
another resource that cannot be obtained until the first resource is freed.
See Example 3 for an example of an EXCEPTION report and Example 4 for an
example of a lockout analysis report.
v RESOURCE displays contention information organized by resource name.
See the allocation/unallocation component in z/OS MVS Diagnosis: Reference for
an example of a RESOURCE report.
v ASID displays contention information organized by ASID. Parts of this report
are also produced by the STATUS CPU CONTENTION subcommand.
See Example 1 for an example of an ASID report.
v ALL displays all contention information.
v Obtaining contention information
IPCS gathers contention information once for each dump. ANALYZE invokes
each ANALYZE exit routine specified by parmlib members embedded in the
BLSCECT parmlib member. When contention information has not been
previously gathered, IPCS issues this message:
BLS01000I Contention data initialization is in progress
The amount of time required to gather contention information depends on the
size of the dump, how many address spaces it contains, the number of I/O
devices, and the amount of contention in the dump. IPCS recommends that you
run the ANALYZE subcommand in the background as part of a preliminary
screening report. (See z/OS MVS IPCS User's Guide for information about
running IPCS subcommands in the background.)
In the event that no contention information is detected, IPCS issues:
BLS01002I No resource contention detected. Undetected contention
is possible.
But if contention information is present, IPCS stores this data in the dump
directory. When the contention information in the dump directory is inconsistent
with the current exit routine list, this message is issued:
BLS01004I ANALYZE exit list in PARMLIB member BLSCECT has changed.
Correct BLSCECT member or issue DROPDUMP RECORDS TRANSLATION.
If the BLSCECT parmlib member is correct, enter:
COMMAND ===> DROPDUMP RECORDS(TRANSLATION)
This command deletes all contention information from the dump directory and
lets you reenter the ANALYZE subcommand to gather the contention data again.

54 z/OS MVS IPCS Commands

 ANALYZE subcommand

To perform its processing, the ANALYZE subcommand uses the contention

queue element (CQE) create service to obtain contention data. The CQE service
is IBM-supplied and can be used when writing your own dump exit. See z/OS
MVS IPCS Customization for information about these services and for
information about writing ANALYZE exits.
v Syntax

ANALYZE

-------- Report Type Parameters -----------------------------

[ EXCEPTION ]
[ RESOURCE ]
[ ASID ]
[ ALL ]
[ XREF | NOXREF ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ DSNAME(dsname)|DATASET(dsname) ]
[ FILE(ddname)|DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report type parameters

Use these parameters to select the type of report. If you omit a report type
parameter, the default is EXCEPTION.
EXCEPTION
Specifies that contention information is to be reported only for units of work
that have been determined to be “exceptions”. A unit of work is considered
an “exception” when all of the following conditions apply:
– The unit of work holds at least one resource for which contention exists
– The unit of work is not waiting for another resource
The EXCEPTION report, which is organized by ASID, identifies the units of
work that appear to be preventing work from being accomplished in the
system. A second section of the EXCEPTION report can be produced (when
applicable) indicating resource lockouts. The lockout analysis report lists all
units of work that are involved in a circular chain of resource ownership.
RESOURCE
Specifies that the contention analysis report is to be organized by resource
name. All resources are listed regardless of whether they are involved in
contention.
ASID
Specifies that the contention analysis report is to be organized by ASID. The
report uses the ASID number, the control block type and address, the CPU
address and the system name (SYSNAME) to identify a unit of work that
holds or is waiting for a resource. All units of work are listed regardless of
whether they are involved in contention.
ALL
Specifies that all contention-related information found for this dump is to be
reported. Noncontention information, such as all active I/O and all holders

Chapter 5. IPCS subcommands 55

ANALYZE subcommand

of LOCAL and CMS locks, is also included. The ALL parameter includes
EXCEPTION, RESOURCE and ASID. These other parameters can be
specified with ALL, but do not change the contents of the generated output.
XREF or NOXREF
XREF specifies that additional cross referencing information about resources
held and resources waited for are to be displayed. NOXREF specifies that
this additional information is to be suppressed, and is the default.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the ANALYZE subcommand.
v Example 1: Produce an ASID contention report.
– Action
COMMAND ===> analyze asid xref
– Result
Figure 3 shows the report that is produced.

▌1▐ CONTENTION REPORT BY UNIT OF WORK

▌2▐ JOBNAME=S1202 ASID=000E TCB=009FA950

JOBNAME=S1202 HOLDS THE FOLLOWING RESOURCE(S):

RESOURCE #0004:
NAME=Device Group 0015
DATA=(ALC) ASSOCIATED WITH 3330,DASD,SYSDA,SYSSQ,3330B,SYSALLDA

RESOURCE #0004 IS WAITED ON BY:

JOBNAME=S1203 ASID=000F TCB=009FA950

▌3▐ JOBNAME=S1203 ASID=000F TCB=009FA950

JOBNAME=S1203 IS WAITING FOR RESOURCE(S):

RESOURCE #0004:
NAME=Device Group 0015
DATA=(ALC) ASSOCIATED WITH 3330,DASD,SYSDA,SYSSQ,3330B,SYSALLDA

RESOURCE #0004 IS HELD BY:

JOBNAME=S1202 ASID=000E TCB=009FA950

▌4▐ JOBNAME=S1301 ASID=0011 TCB=009FA950

JOBNAME=S1301 HOLDS THE FOLLOWING RESOURCE(S):

RESOURCE #0003:
NAME=Device Group 0014
DATA=(ALC) ASSOCIATED WITH 3330,DASD,SYSDA,SYSSQ,3330A,SYSALLDA

RESOURCE #0003 IS WAITED ON BY:

JOBNAME=S1302 ASID=0012 TCB=009FA950

Figure 3. Example output from ANALYZE command (ASID contention)

▌1▐ Names the contention report type, ASID. The report is organized by
ASID.
▌2▐ Identifies the unit of work by jobname, and lists the resource(s) it
holds. If it holds more than one resource, they are displayed in the
order in which they were encountered. When XREF is specified the
report shows for each held resource:

56 z/OS MVS IPCS Commands

 ANALYZE subcommand

- Other units of work that share the resource.

- Units of work that are waiting for the resource.
Resources that the job is waiting for are listed. XREF was specified, so
the report identifies the unit of work that currently owns the resource.
▌3▐ and ▌4▐
Lists other units of work experiencing contention.
v Example 2: Produce a RESOURCE contention report.
– Action
COMMAND ===> analyze resource
– Result
Figure 4 shows the report that is produced.

▌1▐ CONTENTION REPORT BY RESOURCE NAME

▌2▐ RESOURCE #0003:

NAME=Device group 001B

RESOURCE #0003 IS HELD BY:

JOBNAME=S1400 ASID=0013 TCB=009FA490

DATA=(ALC) ASSOCIATED WITH 3800,SYSPR

RESOURCE #0003 IS REQUIRED BY:

JOBNAME=S1402 ASID=0014 TCB=009FA490

DATA=(ALC) ASSOCIATED WITH 3800,SYSPR

JOBNAME=S1403 ASID=0015 TCB=009FA490

DATA=(ALC) ASSOCIATED WITH 3800,SYSPR

▌3▐ RESOURCE #0004:

NAME=LOCAL LOCK FOR ASID 001A

RESOURCE #0002 IS HELD BY:

JOBNAME=DATJINT ASID=001A TCB=009FE240

DATA

=INTERRUPTED AND NOW DISPATCHABLE

▌4▐ RESOURCE #0009:

NAME=VAR1001#SET1 ASID=002A Latch#=0:GRJCTZ13_LATCH # 0_100 CHAR LID
STRING_123456789_123456789_123456789_123456789_123456789_123456789_1

RESOURCE #0009 IS HELD BY:

JOBNAME=GRACTZ13 ASID=002A TCB=004E6D90

DATA=EXCLUSIVE RETADDR=87BF8B86 REQID=D9C5D8F17BF0F0F1
REQUEST = 06/04/2009 16:00:42.101583
GRANT = 06/04/2009 16:00:42.101583

RESOURCE #0009 IS REQUIRED BY:

JOBNAME=GRACTZ13 ASID=002A TCB=004E6B70

DATA=EXCLUSIVE RETADDR=87BF8B86 REQID=C3D6D5E3E3C1E2D2
REQUEST = 06/04/2009 16:00:42.422416

Figure 4. Example output from ANALYZE command (resource contention)

▌1▐ Names the contention report type, RESOURCE. The report is

organized by resource name.
▌2▐ Identifies a resource experiencing contention. The report shows:

Chapter 5. IPCS subcommands 57

ANALYZE subcommand

- NAME - The name of the resource

- Information about each job that either owns or is waiting to obtain
the named resource:
v JOBNAME - The job name
v ASID - The associated home ASID
v TCB - The address of the task control block (TCB) for the task
that owns or is waiting to obtain the resource
v DATA - Additional information that describes the named
resource.
▌3▐ Identifies a resource experiencing contention. Because the resource
shown in the example report is associated with a lock, the report
shows:
- NAME - The name of the resource
- Information about each job that either owns or is waiting to obtain
the named resource:
v JOBNAME - The job name
v ASID - The associated home ASID
v TCB - The address of the task control block (TCB) for the task
that owns or is waiting to obtain the resource
v DATA - Additional information that describes the named
resource.
▌4▐ Identifies a resource experiencing contention. Because the resource
shown in the example report is associated with a latch, the report
shows:
- NAME - The latch set name
- ASID - The identifier of the primary address space at the time the
latch set was created
- LATCH# - The number of the latch that has contention. This is
followed by a ":" and the LATCHID String. Up to 255 characters of
the LATCHID string will be displayed. If more than 255 characters
exist, "T" will be appended after the 255th byte.
- Information about each job that either owns or is waiting to obtain
the latch:
v JOBNAME - The job name
v ASID - The associated home ASID
v TCB - The TCB address of the requester, if the requester is a task;
the value '00000000', if the requester is an SRB
v DATA - Indicates whether the job requested exclusive or shared
access to the resource
v RETADDR - The contents of general purpose register (GPR) 14 at
the time the requester called the Latch_Obtain service
v REQID - The requester ID (an 8-byte field that identifies the latch
requester) that was specified by the RequestId value on the
Latch_Obtain service.
v REQUEST - Time when the latch obtain was requested.
v GRANT - Time that the latch was granted ownership. This time
is in only provided for owners.

58 z/OS MVS IPCS Commands

 ANALYZE subcommand

Additional information about latch resource values; for example,

Latch#, REQID, and LATCHID, that are provided by the latch set
creator can be found in the z/OS MVS Diagnosis: Reference.
When XREF is specified:
- For each job that holds one or more resources, the report lists other
resources that are held. These other resource names are truncated to fit on a
single line. The full resource names are available in other sections of the
report.
- For each job that is waiting on one or more resources, the report gives the
name of the resources.
Resources that the job is waiting for are listed. XREF was specified, so the
report identifies the unit of work that currently owns the resource.
v Example 3: Produce an EXCEPTION contention report.
– Action
COMMAND ===> analyze exception
– Result
Figure 5 shows the report that is produced.

▌1▐ CONTENTION EXCEPTION REPORT

▌2▐ JOBNAME=S1202 ASID=000E TCB=009FA950

JOBNAME=S1202 HOLDS THE FOLLOWING RESOURCE(S):

▌3▐RESOURCE #0004: There are 0001 units of work waiting for this resource
NAME=Device Group 0015
DATA=(ALC) ASSOCIATED WITH 3330,DASD,SYSDA,SYSSQ,3330B,SYSALLDA

▌4▐ STATUS FOR THIS UNIT OF WORK:

IRA10102I This address space is on the SRM WAIT queue.
IRA10104I The reason for swap-out is long wait (3).

▌5▐ JOBNAME=S1301 ASID=0011 TCB=009FA950

JOBNAME=S1301 HOLDS THE FOLLOWING RESOURCE(S):

RESOURCE #0003: There are 0001 units of work waiting for this resource
NAME=Device Group 0014
DATA=(ALC) ASSOCIATED WITH 3330,DASD,SYSDA,SYSSQ,3330A,SYSALLDA

STATUS FOR THIS UNIT OF WORK:

IRA10102I This address space is on the SRM WAIT queue.
IRA10104I The reason for swap-out is long wait (3).

▌6▐ JOBNAME=MEGA ASID=0014 TCB=009C0E88

JOBNAME=MEGA HOLDS THE FOLLOWING RESOURCE(S):

RESOURCE #0006: There are 0002 units of work waiting for this resource
NAME=DB3.XMITDATA.LATCH.SET ASID=001D Latch#=1
DATA=EXCLUSIVE RETADDR=82C63F6E REQID=00AC41A000000000

STATUS FOR THIS UNIT OF WORK:

IRA10102I This address space is on the SRM IN queue.

▌7▐BLS01005I No resource lockouts were detected for this dump

Figure 5. Example output from ANALYZE command (exception contention)

▌1▐ Names the contention report type, EXCEPTION.

Chapter 5. IPCS subcommands 59

ANALYZE subcommand

▌2▐ Identifies the unit of work, by jobname, that holds a resource for
which contention exists.
▌3▐ Lists the resources held by this unit of work. If more than one
resource is held, the resources are displayed in the order in which
they were encountered.
▌4▐ Indicates the status of this unit of work.
▌5▐ and ▌6▐
Identify other units of work that hold resources for which contention
exists.
▌7▐ Indicates that no lockouts were detected. Therefore, a lockout analysis
report will not appear at the end of this EXCEPTION report.
v Example 4: Produce a lockout analysis report.
– Action
COMMAND ===> analyze exception
– Result
Figure 6 on page 61 shows the report that is produced.

60 z/OS MVS IPCS Commands

 ANALYZE subcommand

BLS01003I No units of work meet the exception criteria

▌1▐ A RESOURCE LOCKOUT WAS DETECTED FOR THE FOLLOWING JOBS

▌2▐ JOBNAME=S1301 ASID=0011 TCB=009FA950

JOBNAME=S1301 HOLDS:

RESOURCE #0003:
NAME=Device Group 0014
DATA=(ALC) ASSOCIATED WITH 3330,DASD,SYSDA,SYSSQ,3330A,SYSALLDA

AND IS WAITING FOR:

RESOURCE #0002:
NAME=Device Group 001C
DATA=(ALC) ASSOCIATED WITH 3800,SYSPR,SONORA

▌3▐ JOBNAME=S1400 ASID=0013 TCB=009FA490

JOBNAME=S1400 HOLDS:

RESOURCE #0002:
NAME=Device Group 001C
DATA=(ALC) ASSOCIATED WITH 3800,SYSPR,SONORA

AND IS WAITING FOR:

RESOURCE #0001:
NAME=Device Group 001B
DATA=(ALC) ASSOCIATED WITH 3800,SYSPR

▌4▐ JOBNAME=S1401 ASID=0014 TCB=009FA490

JOBNAME=S1400 HOLDS:

RESOURCE #0001:
NAME=Device Group 001B
DATA=(ALC) ASSOCIATED WITH 3800,SYSPR

AND IS WAITING FOR:

RESOURCE #0003:
NAME=Device Group 0014
DATA=(ALC) ASSOCIATED WITH 3330,DASD,SYSDA,SYSSQ,3330A,SYSALLDA

Figure 6. Example output from ANALYZE command (lockout)

▌1▐ Indicates that this is a lockout analysis report, which is organized by

ASID. A lockout occurs when a unit of work holds a resource and is
waiting for another resource that cannot be obtained until the first
resource is freed. The lockout report follows the EXCEPTION report
with the lockout heading repeated for each unique set of resources
involved.
▌2▐ Identifies IPCSJOB as the unit of work that holds a resource for which
contention exists. The resources that are held and are waited for are
displayed.
▌3▐ and ▌4▐
List the two other units of work and the resources that are held and
are waited for. These resources caused IPCSJOB to become part of a
lockout condition.

Chapter 5. IPCS subcommands 61

APPCDATA subcommand

APPCDATA subcommand — analyze APPC/MVS component data

Use the APPCDATA subcommand to generate reports about the Advanced
Program-to-Program Communication (APPC) component of MVS. This
subcommand provides information about the following topics:
v Status of the APPC component
v Configuration of local logical units (LU)
v Local transaction programs (TPs) and their conversations
v Allocate queues and their associated APPC/MVS server address spaces.
v TP FMH-5 attach requests
v APPC component trace status

See the APPC/MVS component topic in z/OS MVS Diagnosis: Reference for
examples of APPCDATA output.
v Syntax

APPCDATA

--------- Report Type Parameters ---------------------------

[ ALL ]
[ CONFIGURATION ]
[ CONVERSATIONS[(asid|ALL)] ]
[ SERVERDATA ]
[ CTRACE ]
[ FMH5MANAGER ]
[ STATUS ]

--------- Data Selection Parameters ------------------------

[ DETAIL ]
[ EXCEPTION ]
[ SUMMARY ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE|MAIN|STORAGE ]
[ DSNAME(dsname)|DATASET(dsname) ]
[ FILE(ddname)|DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report type parameters

Use these parameters to select the type of report. You can specify as many
reports as you want. If you omit these parameters, the default is ALL.
ALL
Requests that information for all the APPCDATA options be presented.
CONFIGURATION
Requests information about the configuration of local LUs in terms of their
connections to partner LUs. The configuration summary report displays the
following information:
– Local LU name and its status
– Number of partner LUs with which the local LU had sessions

62 z/OS MVS IPCS Commands

 APPCDATA subcommand

– Number of partner/mode pairs for which sessions were established.

– VTAM generic resource name or *NONE*
– Local LU resource manager name and token
– Number of units of recovery (URs)
– Total expressions of interest
The configuration detail report includes information from the summary
report and adds the following information for each partner LU:
– Partner LU name
– Number of modes that defined session characteristics
– Logon name for each mode.
– URIDs and expressions of interest for each UR
– Diagnostic information
CONVERSATIONS[(asid|ALL)]
Requests information for each local TP and its conversations for either a
particular address space, specified as an address space identifier (ASID), or
all address spaces. For this parameter, asid is a 1- to 4-character hexadecimal
value. If no ASID is specified, information for all address spaces is
displayed.
The conversations summary report displays for each address space the
following information:
– A scheduler name
– Local TP name or *UNKNOWN*
– TP_ID
– Local LU name through which the session was established
– Work unit ID
– Number of conversations in which the TP was engaged
The conversations detail report includes information from the summary
report and adds the following information for each conversation:
– Conversation identifier
– Conversation correlator
– Partner TP name or *UNKNOWN*
– Attach user identifier
– Conversation type
– Sync level
– Unit of recovery identifier (URID)
– Logical unit of work identifier (LUWID)
– Resource manager name
– LU name of the partner TP
– Logon mode
– The current state
– Time of day (TOD)
SERVERDATA
Requests information about allocate queues and their associated APPC/MVS
server address spaces.
The SERVERDATA summary report displays the following information
about allocate queues and APPC/MVS server address spaces.

Chapter 5. IPCS subcommands 63

APPCDATA subcommand

– For each allocate queue:

- Name of the TP whose allocate requests are being queued
- Name of the LU at which the server resides
- Userid that was specified on the allocate request
- Profile of the security group to which the userid belongs
- Name of the LU at which the client TP resides
- Number of servers for the allocate queue
- Number of allocate requests (elements) on the allocate queue
- Total number of allocate requests that have been added to the allocate
queue (includes allocate requests that have been received from the
allocate queue)
- Number of pending calls to the Receive_Allocate service
- Keep time (the amount of time APPC/MVS is to maintain the allocate
queue in the absence of servers)
- Time at which the allocate queue was created
- Time at which an allocate request was last received from the allocate
queue
- Time at which a server last called the Unregister_For_Allocates service
to unregister from the allocate queue.
– For each APPC/MVS server:
- Address space identifier (ASID) of the server address space
- An indication of whether the server has an outstanding call to the
Get_Event service
- Number of events on the server's event queue
- Number of allocate queues for which the server is currently registered.
The SERVERDATA detail report includes information from the summary
report and adds the following information:
– For each APPC/MVS server for a given allocate queue:
- Address space identifier (ASID) of the server address space
- Time at which the server registered for each allocate queue
- Time at which the server last issued the Receive_Allocate service
- Time at which a Receive_Allocate request was last returned to the
server
- Total number of allocate requests returned to the server.
– For each pending Receive_Allocate request for a given allocate queue:
- The address space identifier (ASID) of the server with the pending
Receive_Allocate request.
– For each inbound allocate request for a given allocate queue:
- Conversation identifier
- Access method conversation identifier
- Conversation type (basic or mapped)
- Conversation correlator
- Logon mode
- Partner LU name
- Sync level (“none” or “confirm”)
- Userid

64 z/OS MVS IPCS Commands

 APPCDATA subcommand

- Security profile
- Time at which the system placed the request on the allocate queue
- Address of the access method control block (ACB) for the LU at which
the APPC/MVS server resides.
– For each server event for a given server:
- Event (“min” or “max”)
- Event object (the allocate queue token of the allocate queue to which
the event pertains)
- Event qualifier.
– For each allocate queue for a given server:
- Allocate queue token
- Minimum and maximum one-time event threshold
- Minimum and maximum continuous event threshold.
CTRACE
Displays the status of component trace for APPC, trace options, and other
trace-related information. The CTRACE summary report displays the
following information:
– Trace status
– Most recently specified trace options
– User IDs, ASIDs, and job names used as filters
The CTRACE detail report includes information from the summary report
and adds the following details:
– Console identifiers of the operator who most recently started or stopped
the trace
– Message-routing command and response token (CART)
– Information about the trace table
FMH5MANAGER
Requests information about the transaction program FMH-5 attach requests
that are either waiting to be processed or are currently being processed.
The summary report displays the number of TP FMH-5 attach requests that
are waiting to be processed and the number of requests currently being
processed.
The detail report lists, for both types of requests, the LU names and the total
number of requests they received. For each LU name, the requests are
broken down into the number of requests originating from a specific partner
LU name. If the request was being processed and dump data is available,
the report displays the data.
STATUS
Displays a message about the overall status of the APPC component at the
time of the dump.

Note: The reports generated by the APPCDATA subcommand contain

information for IBM diagnostic use. The IBM Support Center might ask for this
information for use in problem determination.
v Data Selection Parameters
Data selection parameters limit the scope of the data in the report. If no data
selection parameter is selected, the default is to present a summary report for all
of the following topics:

Chapter 5. IPCS subcommands 65

APPCDATA subcommand

DETAIL
Requests detailed information for each of the selected topics.
EXCEPTION
Requests a list of exceptional or unusual conditions for each topic. The list of
exceptions contains information for IBM diagnostic use.
SUMMARY
Requests summary information for each of the requested topics.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the APPCDATA subcommand.

ARCHECK subcommand — format access register data

Use the ARCHECK subcommand to format access register data associated with
system control blocks, the active processors described by a stand-alone dump, or
the processors described by an SVC dump.
v Syntax

ARCHECK { data-descr }
{ CPU(nn)STATUS }
{ HEADER }
[ AR(nn| ALL) ]
[ ALET(aletvalue) ]
[ TRANSLATE | ANALYZE ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
data-descr
Specifies the data description parameter, which supplies the location of the
control block or access list you want. The data description parameter
consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (see the following note)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.

Note: The STRUCTURE(cbname) attribute parameter is required; all other

attribute parameters are optional. Use one of the following values for
cbname:
– ACCESSLIST

66 z/OS MVS IPCS Commands

 ARCHECK subcommand

– RB
– SSRB
– TCB
When you specify STRUCTURE(ACCESSLIST), the ALET parameter is
required to associate access registers with the access list.
CPU(nn) STATUS
CPU(nn) STATUS is for stand-alone dumps and requests formatting of the
access registers in the STORE STATUS record associated with the specified
CPU. The display shows the access register information at the time of the
error.
HEADER
HEADER is for SVC dumps and produces the same output as CPU(nn)
STATUS.
AR(nn | ALL)
Requests processing of either a specific access register or all non-zero access
registers and is the default. The nn is a decimal number ranging from 0 to
15. If you do not supply a number, ALL is the default. When you specify
AR(ALL), the contents of the access registers appears first, followed by more
detailed information. The nature of the rest of the information you will see
depends on whether you specify TRANSLATE or ANALYZE.
ALET(alet value)
Specify an 8-character hexadecimal ALET value instead of one of the saved
access registers, to process a specific access list entry and control the use of
the PASN or work unit access list. ALET is required with
STRUCTURE(ACCESSLIST).
TRANSLATE
TRANSLATE identifies the target address space or data space for an ALET
or access register and is the default. TRANSLATE works for stand-alone
dumps only.
ANALYZE
ANALYZE formats the access list entry (ALE) and the address space second
table entry control blocks. The ARCHECK service uses these control blocks
to achieve access register addressability.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the ARCHECK subcommand.
v Example 1: Display the contents of access register 5 for the RB at AD8BE0, in
address space number 12 (X'000C').
– Action
COMMAND ===> archeck address(00ad8be0) asid(X’000C’) structure(rb) ar(5)
– Result
The display identifies the requested access register and the address space or
data space associated with it.
v Example 2: Get detailed information from a stand-alone dump about all the
access registers associated with a central processor.
– Action
COMMAND ===> archeck cpu(00) status ar(all) analyze
– Result

Chapter 5. IPCS subcommands 67

ARCHECK subcommand

IPCS produces the report shown in Figure 7 for the specified central
processor.

▌1▐ ACCESS REGISTER VALUES

0-3 00000000 00000000 00000000 00000000
4-7 FFFFFFFF 00010007 0101000B FFFFFFFF
8-11 00000000 00010006 DDDDDDDD 00000000
12-15 00000000 00000000 00000000 00000000

▌2▐ ALET TRANSLATION

------------------------------------------------------------------

▌3▐ AR 04 VALUE: FFFFFFFF

IEA11016I There are non-zero reserved bits in the ALET.

AR 04 Not translatable
------------------------------------------------------------------

▌4▐ AR 05 VALUE: 00010007

IEA11013I The WORKUNIT access list is being used for translation.

ALE: 7FFFD970
+0000 OPTB1... 00 SN...... 01 EAX..... 0001
+0008 ASTE.... 00D26140 ASTSN... 00000001
ASTE REAL ADDRESS: 00D26140
+0000 ATO..... 00C0F0B0 AX...... 0001 ATL..... 0030
+0008 STD..... 0040C07F LTD..... 80412000 PALD.... 00CA9F00

▌5▐ AR 05 addresses ASID (X’0004’)

Figure 7. Example output from ARCHECK command (specific central processor)

▌1▐ Shows the contents of the access registers.

▌2▐ Shows how the ALETs are translated and listed in numeric order with
information about the translation results (described in items ▌3▐
through ▌5▐).
▌3▐ Shows the output message indicating an untranslatable ALET. An
ALET is typically not translatable when errors are detected or dump
data is insufficient for translation.
▌4▐ Shows the translation results for a translatable ALET. Related
information might include the access list entry used for translation
processing and, if the ALET is addressing an address space, the
address space second table entry (ASTE) control block.
▌5▐ For translatable ALETs, a message indicates which space is accessible
using the related access register.
v Example 3: Obtain information about a particular access register using an access
list you supply.
– Action
Command:
===> archeck address(7fffd900) asid(12) str(accesslist)
alet(x’00010006’) analyze
– Result
IPCS produces the report shown in Figure 8 on page 69.

68 z/OS MVS IPCS Commands

 ARCHECK subcommand

ALET TRANSLATION
------------------------------------------------------------------

▌1▐ ALET VALUE: 00010006

▌2▐ IEA11013I The WORKUNIT access list is being used for translation.

▌3▐ ALE: 7FFFD960

+0000 OPTB1... 01 SN...... 01 EAX..... 0001
+0008 ASTE.... 00D26080 ASTSN... 00000001

▌4▐ ASTE REAL ADDRESS: 00D26080

+0000 ATO..... 00C0F0B0 AX...... 0001 ATL..... 0030
+0008 STD..... 0080B07F LTD..... 80412000 PALD.... 00CA9F00
+0014 SQN..... 00000001 PROG.... 00F37E00

▌5▐ ALET addresses ASID(X’0002’)

Figure 8. Example output from ARCHECK command (specific access register)

▌1▐ Identifies the ALET value used for translation.

▌2▐ The message that identifies the specified access list (address 7fffd900
in the command) as the WORKUNIT access list.
▌3▐ and ▌4▐
The formatted ALE and ASTE control blocks used for translation.

Note: The ASTE only appears of the ALET addresses an address

space.
▌5▐ Identifies the space that the translated ALET addresses.

ASCBEXIT subcommand — run an ASCB exit routine

Use the ASCBEXIT subcommand to run an installation-provided ASCB exit routine.
v Syntax

{ASCBEXIT } { pgmname | * }
{ASCBX }
asid
[ AMASK(mask) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE| MAIN | STORAGE ]
[ DSNAME(dsname)| DATASET(dsname) ]
[ FILE(ddname)| DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
pgmname or *
pgmname specifies the name of an installation-provided exit routine that
must reside in a library available to IPCS, such as a step library, job library,
or link library. For information about writing ASCB exit routines, see z/OS
MVS IPCS Customization.

Chapter 5. IPCS subcommands 69

ASCBEXIT subcommand

* specifies that the list of installation-provided ASCB exit routines (identified

in the BLSCUSER parmlib member) receives control.

Note: The z/OS MVS system does not supply any ASCB exit routines.
asid
Specifies the address space identifier (ASID) to be passed to the exit routine.
The ASID can range from 1 through 65535. You can specify the ASID in
decimal, hexadecimal (X‘xxx...’), or binary (B‘bbb...’).
AMASK(mask)
Specifies an integer mask that ASCBEXIT is to AND to the dump addresses
passed by the exit to the storage access and format service routines. Only
X‘7FFFFFFF’, X‘00FFFFFF’, or the corresponding decimal or binary values
will be accepted.
v Return codes

Code Explanation
12 Severe error; an error condition or user request forced early end to the
subcommand processing.
16 Ending error; an error condition from a called service routine forced an
early end to the subcommand processing.
other An exit-generated return code

v Example: Invoke an installation-provided ASCB exit.

– Action
COMMAND ===> ascbexit chekascb 7
– Result
This command runs the installation-provided routine, CHEKASCB, and
passes it ASID 7. Note that CHEKASCB must be identified in the BLSCUSER
parmlib member.

ASCHDATA subcommand — analyze APPC/MVS transaction scheduler

data
Use the ASCHDATA subcommand to generate reports about the APPC/MVS
transaction scheduler. This subcommand provides the following information:
v Status of the scheduler
v Subsystem name
v Default scheduler class
v Generic initiators, if any
v Summary information for each class

See the APPC/MVS component in z/OS MVS Diagnosis: Reference for examples of
ASCHDATA output.

Note: The reports generated by ASCHDATA contain information for IBM

diagnostic use. The IBM Support Center might ask you to provide this information
for use in problem determination.
v Syntax

70 z/OS MVS IPCS Commands

 ASCHDATA subcommand

ASCHDATA

--------- Report Type Parameters ---------------------------

[ CLASS[(classname|ALL)] ]

--------- Data Selection Parameters ------------------------

[ DETAIL ]
[ EXCEPTION ]
[ SUMMARY ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE|MAIN|STORAGE ]
[ DSNAME(dsname)|DATASET(dsname) ]
[ FILE(ddname)|DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report type parameters

Use these parameters to select the type of report. Specify only one; ASCHDATA
produces the report type for each topic specified by a data selection parameter.
If you omit a report type parameter, the default is ALL.
CLASS[(classname|ALL)]
Requests APPC transaction scheduler information for either a particular
scheduler class or all scheduler classes. For this parameter, classname is a
valid 1- to 8-character scheduler class name. If no class name is specified,
information for all scheduler classes is displayed.
The class summary report displays the following information for each
scheduler class:
– Class name and status of each class, including:
- Maximum and minimum number of initiators
- Expected response time
- Message limit
– Total number of jobs waiting for processing
– Total number of active initiators
– Total number of active waiting multi-trans initiators
– Total number of idle initiators
The class detail report includes information from the summary report and
adds the following information:
– For each job waiting to run, the job identifier, local LU name, partner LU
name, TP name, FMH5 userid, and time the job started waiting to run.
– For each active initiator, the address space identifier (ASID), TP start time,
TP name, current job identifier, local LU name, partner LU name, and
FMH5 userid.
– For each active waiting multi-trans initiators, the ASID and TP name.
– For each idle initiator, the ASID.
v Data selection parameters

Chapter 5. IPCS subcommands 71

ASCHDATA subcommand

Data selection parameters limit the scope of the data in the report. If no data
selection parameter is selected, the default is to present a summary report for all
of the following topics:
DETAIL
Requests detailed information for each of the selected topics.
EXCEPTION
Requests a list of exceptional or unusual conditions for each topic. The list of
exceptions contains information for IBM diagnostic use.
SUMMARY
Requests summary information for each of the requested topics.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the ASCHDATA subcommand.

ASMCHECK subcommand — analyze auxiliary storage manager data

Use the ASMCHECK subcommand to analyze and validate data associated with
the auxiliary storage manager (ASM) to produce a report.

See the ASM component in z/OS MVS Diagnosis: Reference for an example of the
ASMCHECK report and more information about diagnosing ASM problems.
v Syntax

{ASMCHECK | ASMK }

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE|MAIN|STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the ASMCHECK subcommand.

CBFORMAT subcommand — format a control block

Use the CBFORMAT subcommand to format and display a control block or data
area that is defined in the exit data table. CBFORMAT can also be used to test and
run user-written formatting routines and control block models. Appendix C,
“Control blocks and data areas scanned, mapped, and formatted,” on page 455 lists
the control blocks and data areas that CBFORMAT formats.

The maximum size of the control block or data area is 64 kilobytes.

After successful processing, CBFORMAT sets X, the current address, to the starting
address of the data area being formatted. If a data area has no IPCS formatting

72 z/OS MVS IPCS Commands

 CBFORMAT Subcommand

support, IPCS issues message BLS17004I, which identifies the requested control
block or data area name specified with the STRUCTURE parameter.

You can use the CBFORMAT subcommand to format literal data as if it was a valid
instance of a control block. IBM does not recommend this use unless:
v The control block involved remains valid when removed from its original
setting.
v You recognize that it is inappropriate, for example, to ask the service to format a
symbolic literal as a task control block (TCB) and then to use the formatted TCB
for diagnosis.
v Syntax

{ CBFORMAT | CBF }

data-descr
[ EXIT | NOEXIT ]
[ FORMAT(name [level]) ]
[ MODEL(name) ]
[ VIEW(fieldlist) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
data-descr
Specifies the data description parameter, which consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (see the following note)
– Array parameters (optional)
– A remark parameter (optional)
See Chapter 3, “Data description parameter,” on page 17 for the use and
syntax of the data description parameter.

Note: The STRUCTURE(cbname) attribute parameter is required, except

with FORMAT and MODEL. All other attribute parameters are optional.
EXIT or NOEXIT
EXIT processes all formatting exits defined in the exit data table for a given
control block, after the control block has formatted successfully. NOEXIT
requests no formatting exits, and is the default.
FORMAT(name[level])
FORMAT identifies the user-written formatter program to be used to format
the data. See z/OS MVS IPCS Customization for details about formatting exits.
The level option can be one of the following:
HBB3310
It causes a BLSRESSY to be passed in ABITS(31) format.

Chapter 5. IPCS subcommands 73

CBFORMAT Subcommand

HBB7703
It causes a BLSRESSY to be passed in ABITS(64) format. If level is
omitted, the default is HBB7703 for compatibility with CBFORMAT.

Note: FORMAT is intended for use during program development of new

formatter support. It does not require use of the STRUCTURE(cbname)
attribute parameter.
MODEL(name)
Identifies the user-written control block model to be used to format the data.
z/OS MVS IPCS Customization describes how to use formatting models.

Note:
1. MODEL is intended for use during control block model development of
new formatter support. It does not require use of the
STRUCTURE(cbname) attribute parameter.
2. MODEL does not influence how IPCS resolves the data description. If a
MODEL is used in resolution, it is the one that would have been used to
support formatting STRUCTURE(cbname) except for this override.
3. When MODEL(name) supplies a control block length, the length is
compared with the default length generated by the data-descr, and the
longer of the two lengths is used during formatting.
VIEW(fieldlist)
VIEW sets the view control field of the format parameter. Values for fieldlist
can be any combination of the following options:
hex value
A 4-digit hexadecimal value that displays a particular field you have
defined in your model.
ALL
Displays all the control block fields.
DEFINED
Displays only the defined control block fields and is the default.
FLAGS
Displays significant bits in the flag bytes with explanations.
KEYFIELDS
Displays the key fields of defined control blocks.
LINK
Displays the control block linkage field and uses it to display attached
blocks.

If VIEW is not specified, CBFORMAT uses a default of VIEW(DEFINED).

v Return codes

Code Explanation
00 Successful completion.
04 Attention, subcommand completed with a condition that may be of interest
to you.
08 Error, subcommand encountered an error condition that may be of interest
to you.
12 Severe error, an error condition or user request forced early end to the
subcommand processing.

74 z/OS MVS IPCS Commands

 CBFORMAT Subcommand

Code Explanation
16 Ending error, CBFORMAT did not recognize the control block type
specified with the STRUCTURE parameter.

v Example 1: Format the CVT.

– Action
COMMAND ===> cbformat cvt structure(cvt)
– Result
This example formats the CVT. (No display is shown here because of the
control block's size.) Note that the STRUCTURE parameter can be omitted
from this example because IPCS always defines the CVT as a symbol and has
STRUCTURE as part of its definition. If a symbol is defined in the IPCS
symbol table and if that symbol has the STRUCTURE attribute assigned, the
STRUCTURE parameter does not need to be specified.
v Example 2: Format the CSD.
– Action
COMMAND ===> cbformat f632d0. structure(csd)
– Result
CBFORMAT generates the formatted control block with offsets, as Figure 9
shows.

CSD: 00F632D0
+0000 CSD...... CSD CPUJS.... 8000 CHAD..... 0000
+0008 CPUAL.... 8000 CPUOL.... 0001 SCFL1.... 00
+000D SCFL2.... 00 SCFL3.... 00 SCFL4.... 00
+0010 AXPAL.... 0000 AXPOL.... 0000 MF1CP.... 0000
+0016 ACR...... 00 FLAGS.... 80 MAFF..... 00000000 0000000
+0020 00000000 00000000 00000000 00000000 00000000 0000000
+0038 00000000 00000000 00000000 00000000 00000000 0000000
+0050 00000000 00000000 00000000 00000000 00000000 0000000
+0068 RV044.... 0000 DDRCT.... 0000 GDCC..... 00000001
+0070 GDINT.... 00000001 GDTOD.... 00000001 TCNT..... 00000000
+007C UCNT..... 00000000 MASK..... 80004000 20001000 08000400 0200010
+0090 00800040 00200010 00080004 00020001
+00A0 IOSID.... 00 IOML..... 02 CPUVF.... 0000
+00A8 CMT...... 019C5708

Figure 9. Example CBFORMAT command output (formatting CSD)

v Example 3: Format a captured unit control block (UCB).

– Action
COMMAND ===> cbformat 006f8028. structure(ucb)
– Result
CBFORMAT generates the formatted UCB with offsets, as Figure 10 on page
76 shows. The actual UCB Common Segment Address field is useful when
you input a captured UCB address and want to learn the UCB's actual
address. In this example, the captured UCB provides a view of the actual
UCB at address 01D0E028.

Chapter 5. IPCS subcommands 75

CBFORMAT Subcommand

UCBPRFIX: 006F8020
-0008 LOCK..... 00000000 IOQ...... 00000000

UCBOB: 006F8028
+0000 JBNR..... 00 FL5...... 00 ID....... FF
+0003 STAT..... 00 CHAN..... 8000 FL1...... 00
+0007 FLB...... 20 NXUCB.... 00000000 WGT...... 06
+000D NAME..... UCB TBYT1.... 00 TBYT2.... 00
+0012 DVCLS.... 41 UNTYP.... 01 FLC...... 00
+0015 EXTP..... D0E001 CTCAL.... 00000000 CTCF1.... 00
+001D RV042.... 000000 CTCWA.... 00000000

UCBCMXT: 006F8000
+0000 ETI...... 19 STI...... 00 FL6...... 00
+0003 ATI...... 2C SNSCT.... 02 FLP1..... 00
+0006 STLI..... 00 FL7...... 00 IEXT..... 01D55B68
+000C CHPRM.... 00 SATI..... 00 ASID..... 0000
+0011 WTOID.... 000000 DDT...... 00FCCCC0 CLEXT.... 00000000
+001C DCTOF.... 0000

UCBXPX: 01D55B68
+0000 RSTEM.... 00 MIHKY.... 07 MIHTI.... 00
+0003 HOTIO.... 00 IOQF..... 00000000 IOQL..... 00000000
+000C SIDA..... 0000 SCHNO.... 0000 PMCW1.... 0000
+0012 MBI...... 0000 LPM...... 00 LPUM..... 00
+0017 PIM...... 00 CHPID.... 00000000 00000000
+0020 LEVEL.... 01 IOSF1.... 40 IOTKY.... 00
+0023 MIHFG.... 00 LVMSK.... 00000001

ACTUAL UCB COMMON SEGMENT ADDRESS 01D0E028

DEVICE IS DYNAMIC

Figure 10. Example CBFORMAT command output (formatting captured UCB)

v Example 4: Format a base UCB of a parallel access volume.

– Action
COMMAND ===> cbformat 00F0B808. structure(ucb)
– Result
CBFORMAT generates the formatted base UCB with offsets, as Figure 11 on
page 77 shows.. After the formatted base UCB, the report provides
information about each alias UCB associated with the base UCB. The
information includes the alias UCB's device number, address, and whether it
is available for I/O requests. In this example, the alias UCB with device
number 01BC at address 01D42448 is not available for I/O requests.

76 z/OS MVS IPCS Commands

 CBFORMAT Subcommand

UCBPRFIX: 00F0B800
-0008 LOCK..... 00000000 IOQ...... 00FC1800

UCBOB: 00F0B808
+0000 JBNR..... 00 FL5...... 88 ID....... FF
+0003 STAT..... 84 CHAN..... 01B0 FL1...... 40
+0007 FLB...... 00 NXUCB.... 00000000 WGT...... 08
+000D NAME..... 1B0 TBYT1.... 30 TBYT2.... 30
+0012 DVCLS.... 20 UNTYP.... 0E FLC...... 00
+0015 EXTP..... F0B7E0 VTOC..... 00010100 VOLI..... 3381B0
+0022 STAB..... 04 DMCT..... 00 SQC...... 00
+0025 FL4...... 00 USER..... 0000 BASE..... 00F0B608
+002C NEXP..... 01D41F88

UCBCMXT: 00F0B7E0
+0000 ETI...... 00 STI...... 00 FL6...... 09
+0003 ATI...... 40 SNSCT.... 20 FLP1..... 22
+0006 STLI..... 00 FL7...... 00 IEXT..... 01D54D38
+000C CHPRM.... 00 SATI..... 00 ASID..... 0000
+0011 WTOID.... 000000 DDT...... 00FCA728 CLEXT.... 00F0B7B0
+001C DCTOF.... 0000

UCBXPX: 01D54D38
+0000 RSTEM.... 00 MIHKY.... 04 MIHTI.... 00
+0003 HOTIO.... 40 IOQF..... 00000000 IOQL..... 00000000
+000C SIDA..... 0001 SCHNO.... 0029 PMCW1.... 289C
+0012 MBI...... 0049 LPM...... C0 LPUM..... 40
+0017 PIM...... C0 CHPID.... 60700000 00000000
+0020 LEVEL.... 01 IOSF1.... 08 IOTKY.... 00
+0023 MIHFG.... 00 LVMSK.... 00000001

Actual UCB Common segment address 00F0B808

Device is dynamic

Base UCB of a parallel access volume

Base UCB has usable alias UCB 01B4 at address 01D42188

Base UCB has usable alias UCB 01B8 at address 01D422E8

Base UCB has unusable alias UCB 01BC at address 01D42448

Figure 11. Example CBFORMAT command output (formatting base UCB)

v Example 5: Format an alias UCB of a parallel access volume.

– Action
COMMAND ===> cbformat 01d422e8. structure(ucb)
– Result
CBFORMAT generates the formatted alias UCB with offsets (Figure 12 on
page 78). After the formatted alias UCB, the report states whether the alias
UCB is available for I/O requests and provides information about the base
UCB.

Chapter 5. IPCS subcommands 77

CBSTAT Subcommand

UCBPRFIX: 01D422E0
-0008 LOCK..... 00000000 IOQ...... 00FC1980

UCBOB: 01D422E8
+0000 JBNR..... 00 FL5...... 88 ID....... FF
+0003 STAT..... 04 CHAN..... 01B8 FL1...... 00
+0007 FLB...... 00 NXUCB.... 00000000 WGT...... 08
+000D NAME..... 1B0 TBYT1.... 30 TBYT2.... 30
+0012 DVCLS.... 20 UNTYP.... 0E FLC...... 00
+0015 EXTP..... D422C1 VTOC..... 00000000 VOLI..... 00000000
+0022 STAB..... 00 DMCT..... 00 SQC...... 00
+0025 FL4...... 00 USER..... 0000 BASE..... 00F0B608
+002C NEXP..... 01D42248

UCBCMXT: 01D422C0
+0000 ETI...... 00 STI...... 00 FL6...... 09
+0003 ATI...... 40 SNSCT.... 18 FLP1..... 22
+0006 STLI..... 00 FL7...... 00 IEXT..... 01D550B8
+000C CHPRM.... 00 SATI..... 00 ASID..... 0000
+0011 WTOID.... 000000 DDT...... 00FCA728 CLEXT.... 00F0B7B0
+001C DCTOF.... 0000

UCBXPX: 01D550B8
+0000 RSTEM.... 00 MIHKY.... 00 MIHTI.... 00
+0003 HOTIO.... 40 IOQF..... 00000000 IOQL..... 00000000
+000C SIDA..... 0001 SCHNO.... 0034 PMCW1.... 289C
+0012 MBI...... 0051 LPM...... C0 LPUM..... 40
+0017 PIM...... C0 CHPID.... 60700000 00000000
+0020 LEVEL.... 01 IOSF1.... 08 IOTKY.... 00
+0023 MIHFG.... 00 LVMSK.... 00000001

Actual UCB Common segment address 01D422E8

Device is dynamic

Usable alias UCB of a parallel access volume

Base UCB 01B0 is at address 00F0B808

Figure 12. Example CBFORMAT command output (formatting alias UCB)

CBSTAT subcommand — obtain control block status

Use the CBSTAT subcommand to analyze a specific control block. IBM provides
exit routines that process ASCBs and TCBs; the exit routines are specified by
parmlib members embedded in the BLSCECT parmlib member. CBSTAT generates
a report for ASCBs that encompasses address space level information. Similarly,
CBSTAT generates a report for TCBs that contains task level information about
control blocks other than the TCB.

You can also use CBSTAT to get information about resource initialization modules
(RIMs) that fail during IPL/NIP processing. Specify the STRUCTURE attribute
parameter, but instead of a control block name, specify STORESTATUS. CBSTAT
returns the name of the failing RIM(s) with corresponding abend and reason codes.
(See the example on viewing data about failing NIP RIMs..)

IPCS may issue the accompanying messages when:

v No CBSTAT report is generated.
BLS01040I No errors were detected by the CBSTAT exits
v CBSTAT does not analyze a requested control block, where yyyyyyyy is the
name of the specified control block that CBSTAT does not analyze, such as the
ASXB.

78 z/OS MVS IPCS Commands

 CBSTAT Subcommand

BLS01041I The CBSTAT exits defined in BLSCECT do not process

STRUCTURE(yyyyyyyy)
v The CBSTAT subcommand syntax check fails. This may occur when the address
for the requested control block is not in virtual storage or when the
STRUCTURE parameter is omitted.
BLS01043I CBSTAT requires the specification of a STRUCTURE
in virtual storage
v The specified address cannot be accessed.
BLS18100I adr-space adr NOT AVAILABLE
v The control block identified in the STRUCTURE parameter fails the validity
check.
BLS18058I Errors detected in STRUCTURE(name) at ASID(n) address

To perform its processing, the CBSTAT subcommand uses the CBSTAT service. This
service is IBM-supplied and can be used when writing your own dump exit. See
z/OS MVS IPCS Customization for information about these services and for
information about writing CBSTAT exits.
v Syntax

CBSTAT data-descr

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
data-descr
Specifies the data description parameter, which consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (see the following note)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.

Note: The STRUCTURE(cbname) attribute parameter is required; all other

attribute parameters are optional. The following values are valid for cbname:
– ASCB
– CSRCPOOL
– SSRB
– STORESTATUS
– TCB
v Return codes

Chapter 5. IPCS subcommands 79

CBSTAT Subcommand

Code Explanation
00 Successful completion.
04 Attention, subcommand completed with a condition that may interest you.
08 Error, subcommand encountered an error condition that may interest you.
12 Severe error, no CBSTAT exits exist for the requested control block type or
user request forced early end to the subcommand processing.
16 Ending error, the identified control block failed the validity check.

v Example 1: Analyze the ASCB in the master scheduler address space.

– Action
COMMAND ===> cbstat ascb1 structure(ascb)
– Result
CBSTAT generates the output (see Figure 13) for the master scheduler address
space, after accessing and validity checking the ASCB. IPCS invokes the
CBSTAT exits for ASCBs. Note that if the symbol, ascb1, is defined in the
IPCS symbol table and if that symbol has the STRUCTURE attribute defined,
the STRUCTURE parameter can be omitted from the example.

STATUS FOR STRUCTURE(ASCB) AT 00FC8B00. NOCPU ASID(X’0001’)

IRA10102I This address space is on the SRM IN queue.

Figure 13. Example CBSTAT command output

v Example 2: Analyze a TCB at a specified address.

– Action
COMMAND ===> cbstat 7fa030. structure(tcb)
– Result
CBSTAT generates the output for the specified TCB (Figure 14) . IPCS invokes
the CBSTAT exits for TCBs.

STATUS FOR STRUCTURE(TCB) AT 007FA030. ASID(X’07D1’)

IEA21005I Task is in recovery processing, LIFO summary of active
recovery environments follows:
IEA21007I In ESTAE at IGC0006C+010D70 for S003F at IGC0006C+01045A,
SDWA at 007B0B40

Figure 14. Example CBSTAT command output (analyze a TCB)

v Example 3: Analyze an ASCB at a specified address.

– Action
COMMAND ===> cbstat f62180. structure(ascb)
– Result
CBSTAT generates the output for the ASCB (Figure 15 on page 81).

80 z/OS MVS IPCS Commands

 CBSTAT Subcommand

STATUS FOR STRUCTURE(ASCB) AT 00F62180. CPU(X’00’) ASID(X’0001’)

IRA10102I This address space is on the SRM WAIT queue.
IRA10104I The reason for swap-out is long wait (3).

Figure 15. Example CBSTAT command output (analyze an ASCB)

v Example 4: View data about failing NIP RIMs.

– Action
COMMAND ===> cbstat structure(storestatus)
– Result
CBSTAT generates the output shown in Figure 16.

STATUS FOR STRUCTURE(STORESTATUS) AT 00FD7100 NOCPU ASID(X’0001’)

IEA41001I NIP RIM IEAVNP11 has failed
IEA41002I ABEND=0C4 REASON=04

Figure 16. Example CBSTAT command output (view data about NIP RIMs)

CLOSE subcommand — release resources in use by IPCS

Use the CLOSE subcommand to end the use of a source or data set by IPCS.
CLOSE can end the use of the following:
v Dump data sets
v Trace data sets
v User dump directory
v Sysplex dump directory (for users with access authority)
v Central storage
v Print and table of contents (TOC) data sets

Note: When you end an IPCS session, IPCS automatically closes these data sets,
except the sysplex dump directory.

See z/OS MVS IPCS User's Guide for information about closing the print and TOC
data sets.
v Syntax

CLOSE { ALL }
{ ACTIVE|MAIN|STORAGE }
{ DSNAME(dslist)|DATASET(dslist) }
{ FILE(ddlist | IPCSDDIR)|DDNAME(ddlist) }
{ PATH(path-name ...) }
[ CONDITIONALLY | UNCONDITIONALLY ]
[ PRINT ]

-------- SETDEF-Defined Parameter -------------------------

Note: You can override the following SETDEF parameter.
See “SETDEF subcommand — set defaults” on page 262.
[ TEST | NOTEST ]

v Parameters
ALL
ACTIVE or MAIN or STORAGE

Chapter 5. IPCS subcommands 81

CLOSE Subcommand

DSNAME(dslist) or DATASET(dslist)
FILE(ddlist | IPCSDDIR) or DDNAME(ddlist)
PATH(pathname)
Specifies one or more source or print data sets to be closed. If you specify
ALL and other source parameters, IPCS processes CLOSE ALL and ignores
the other source parameters. If you omit these parameters, IPCS closes your
current source data set.
ALL directs IPCS to close all data sets it is using.
ACTIVE, MAIN, or STORAGE directs IPCS to release resources that were
needed to access the central storage that was specified as the source.
DSNAME or DATASET specifies one or more names of cataloged data sets
that IPCS is to close. The CLOSE subcommand closes the data sets in the
order in which they are specified.
FILE or DDNAME specifies one or more ddnames of data sets that IPCS is
to close. The CLOSE subcommand closes the data sets in the order in which
they are specified.
When specifying more than one data set name or ddname, separate the
names with a comma or a blank.
PATH specifies one or more paths of a file or directory on a z/OS UNIX file.
CLOSE FILE(IPCSDDIR) indicates that you want to close your current dump
directory. You have to specify its ddname; specifying a range for ddlist does
not include your dump directory.

Default Values: You can change your current dump directory by closing it
and opening another. This substitution has no effect on the local or global
default values. IPCS establishes the local and global defaults when a session
starts, using defaults from the dump directory available when the session
started.
If you update your local or global defaults, IPCS records the updated
defaults in your current dump directory. Depending on when you make the
update, the updated dump directory will be the original directory used
when the session started or the substitution dump directory.
CONDITIONALLY or UNCONDITIONALLY
Determines how IPCS should handle a data set that is already closed when
the CLOSE subcommand is processed. For CONDITIONALLY, IPCS does not
issue messages about the data set being closed. For UNCONDITIONALLY,
IPCS issues messages about the data set being closed. UNCONDITIONALLY
is the default.
PRINT
PRINT directs IPCS to close the print data set and the table of contents
(TOC) data set, if it is open. In the process of doing a CLOSE PRINT, the
default message routing parameter is set to NOPRINT so that subsequent
subcommands do not attempt to write to a closed data set.
v Support of dump directory substitution
– IPCS supports substitution when the change of dump directories is made
while you are not using the IPCS dialog.
– IPCS supports substitution while you are using the IPCS dialog when the
dialog activity is not using the original dump directory.
– IPCS does not allow substitution while you are using the IPCS dialog when
the dialog activity is using the original dump directory. The reason is that

82 z/OS MVS IPCS Commands

 CLOSE Subcommand

unpredictable errors can potentially damage the new directory, because IPCS
has data from the original directory and the data is not necessarily present in
the new directory.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the CLOSE subcommand.
v Example: Close the TOC data set.
– Action
COMMAND ===> close print
– Result
Both the TOC and print data sets are closed. Note that when you end an IPCS
session, IPCS closes both of these data sets automatically.

COMCHECK subcommand — analyze communications task data

Use the COMCHECK subcommand to generate reports about the attributes and
status of the communications task (COMMTASK) at the time of a dump. You can
request information for the following:
v MCS consoles
v Extended MCS consoles
v System console
v Subsystem console
v SMCS console
v Device independent display operator console support (DIDOCS) resident display
control modules (RDCM)
v DIDOCS pageable display control modules (TDCM)
v Message queues and console management

You can select information for one or all MCS consoles and RDCM, TDCM, and
UCME control blocks. You can request the addresses of control blocks or
formatting of the blocks.

See z/OS MVS Diagnosis: Reference for examples of COMCHECK reports and more
information about diagnosing problems with communications task.
v Syntax

Chapter 5. IPCS subcommands 83

COMCHECK Subcommand

{ COMCHECK | COMK }

-------- Report Type Parameters ----------------------------

[ MCSINFO ]
[ DATABLKS[( LIST | address )] ]
[ LISTNAMES(keyname) ]
[ NAME(nnnnnnnn) | ID(iiiiiiii) ]
[ NAMELIST ]
[ RDCM[( ALL | LIST | address )] ]
[ SBC ]
[ SYSCONS ]
[ SYSPLEX[( CNTRLMEM | SYSMEM )] ]
[ TDCM[( ALL | LIST | address )] ]
[ UCM ]
[ UCME[( ALL | LIST | address )] ]
[ UPDATES[( ALL | LIST | address )] ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report type parameters

Use these parameters to select the type of report. Specify only one. If you omit a
report type parameter, the default is MCSINFO.
MCSINFO
Requests summary communications task information for console activity.
MCSINFO analyzes the control blocks used to queue messages and manage
consoles. MCSINFO produces the following statistics:
– The number of queued messages in the system at the time of the dump.
– The WTO limit (MLIM) in the dumped system.
– The number of messages that are queued to each console.
– Pending WTOR messages.
MCSINFO is the default when COMCHECK is specified without any other
parameters.
DATABLKS[(LIST | address)]
Requests summary information that the IBM Support Center might request
for problem determination.
ID(iiiiiiii)
Requests summary information for a console. Specify the console's 4-byte ID
assigned by the system.
LISTNAMES(keyname)
Requests a list of extended MCS console names defined to a 1- to 8-character
keyname.
NAME(nnnnnnnn)
Requests summary information for a console. Specify the console's 2- to
8-character symbolic name.

84 z/OS MVS IPCS Commands

 COMCHECK Subcommand

NAMELIST
Requests a list of all console names defined in a sysplex.
RDCM[(ALL | LIST | address)]
Requests summary control block information for RDCMs.
ALL
Gives the status of all active and defined RDCMs.
LIST
Lists the address of each RDCM in the dump.
address
Gives the status of one RDCM at the specified address.
SBC
Requests information about the delayed issue queue and additional
information that the IBM Support Center might request for problem
determination. It formats the supplemental branch entry console control
block (SBC).
SYSCONS
Requests information about the status of the system console, including:
– The console name and ID
– The console's attributes
– The console's availability
– Message suppression for the console
SYSPLEX[(CNTRLMEM | SYSMEM)]
Requests summary information for the members of the sysplex. SYSPLEX
with no delimiter prints the current number of sysplex members, the
maximum number of members allowed in this sysplex, and additional
information the IBM Support Center might request for problem
determination.
CNTRLMEM
Requests information for each sysplex control member that the IBM
Support Center might request for problem determination.
SYSMEM
Requests the names of the systems defined to the sysplex and
additional information the IBM Support Center might request for
problem determination.
TDCM[(ALL | LIST | address)]
Requests summary control block information for TDCMs.
ALL
Gives the status of all active and defined TDCMs.
LIST
Lists the status of each TDCM in the dump.
address
Gives the status of one TDCM at the specified address.
UCM
Requests summary control block information for the unit control module
(UCM) base, prefix, and extension.

Chapter 5. IPCS subcommands 85

COMCHECK Subcommand

UCME[(ALL | LIST | address)]

Requests the status of an MCS, SMCS, or subsystem console at the time of
the dump. It formats the unit control module individual device entries
(UCMEs).
ALL
Gives the status of all active and defined MCS, SMCS, and subsystem
consoles. It formats all console information.
LIST
Lists the address of each UCME in the dump.
address
Gives the status of one MCS, SMCS, or subsystem console. It formats the
UCME at the specified address.
UPDATES[(ALL | LIST | address)]
Requests summary information that IBM might request for problem
determination.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the COMCHECK subcommand.
v Example: Find the status of an MCS console at the time of a dump.
– First Action
Obtain a list of UCME addresses by entering on the command line:
COMMAND ===> COMCHECK UCME
– Result
COMCHECK produces a list of UCME addresses, similar to the example in
Figure 17.

COMMUNICATION TASK ANALYSIS

ADDRESS OF ALL ACTIVE UCMES ON SY1

CONSOLE NAME ADDRESS TYPE

------------ ------- ----
MCSY13E0 00FD64C0 MCS
MCSY13D1 00FD6510 MCS
MCSY13D2 00FD6560 MCS
SUBSYS2 00FDFBEC SUBSYSTEM

Figure 17. Example COMCHECK command output (obtain UCME addresses)

– Second Action
To look at the UCME at address 00FD64C0, enter on the command line:
COMMAND ===> COMCHECK UCME(00FD64C0)
– Result
COMCHECK produces a report for the MCS console represented by that
UCME. z/OS MVS Diagnosis: Reference shows a sample UCME report and
explains the contents of the fields.

86 z/OS MVS IPCS Commands

 COMPARE subcommand

COMPARE subcommand — compare dump data

Use the COMPARE subcommand to compare two data items. COMPARE makes
the results of the comparison known to a CLIST or REXX exec by a return code
and, optionally, makes the results known to you by a message. Each data item can
be specified as a value or as the address of a data item.
v Numeric comparison
Numeric comparison is performed if the PAD parameter is specified and both
items to be compared have POINTER, SIGNED, or UNSIGNED data types.
– Numeric comparison between two unsigned (POINTER or UNSIGNED data
types) items is accomplished by providing leading zero bytes to pad both
items to a fullword (32-bit) precision and comparing the unsigned results.
– Numeric comparison between two SIGNED items is accomplished by
propagating the sign bit to pad both items to a fullword (31-bit) precision and
comparing the signed results.
– Numeric comparison between a SIGNED item and one that is unsigned is
reduced to the following cases:
- If the SIGNED value is negative, that number is less than any unsigned
value.
- Otherwise, a positive SIGNED value may be treated as unsigned, and the
comparison completed as though unsigned numeric comparison had been
requested.
v String comparison
String comparison is performed whenever numeric comparison is inappropriate.
Comparison of strings whose lengths differ may be performed in two ways:
– The longer string may be truncated to the length of the shorter before
comparison (TRUNCATE parameter).
– The shorter string may be padded to the length of the longer before
comparison (PAD parameter). The character used for padding may be
explicitly specified. If it is not, an EBCDIC blank (X'40') is used for data
described as CHARACTER data or data described using a general value of
types C or T. If the data was described using a general value associated with
ISO-8 ASCII CHARACTER data (types Q or S), padding is performed using
an ISO-8 ASCII blank (X'20'). Padding with a null character (X'00') is used for
all other types of data.
v Syntax

{COMPARE | COMP}

[ data-descr | ADDRESS(X) | (VALUE(value)) ]

[ WITH [(data-descr) | (ADDRESS(X)) | (VALUE(value))] ]
[ LIST | NOLIST ]
[ MASK(mask) | NOMASK ]
[ PAD[(value)] | TRUNCATE ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters

Chapter 5. IPCS subcommands 87

COMPARE subcommand

data-descr
ADDRESS(X)
VALUE(value)
Specifies the first operand for the comparison. The length of the comparison
is determined by the length of the data described by this parameter or by
the mask, if you specify one. The maximum length is 231 bytes or, if you use
a mask, 256 bytes.
The data-descr specifies the data description parameter, which designates
dump data as the first operand for the comparison. The data description
parameter consists of five parts:
– An address (required when data-descr is explicitly specified on the
subcommand)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.
VALUE(value) designates a literal value as the first operand; it may be
specified as a:
– Positive integer
– Signed integer
– General value
See Chapter 2, “Literal values,” on page 9 for more information, the syntax
and examples.
If you specify VALUE, you cannot specify data description parameters with
it. They will be ignored and processing will continue. IPCS issues the
following message, where n is either 1 or 2, to indicate which operand is in
error.
BLS18032I Operand n uses both the value parameter and data description
parameters. The data description parameters are ignored.
If you omit this parameter, the default is ADDRESS(X), the most recently
accessed address.
WITH [(data-descr) | (ADDRESS(X)) | (VALUE(value))]
Specifies the second operand for the comparison.

Note: The rules for specifying the VALUE parameter on this operand are the
same as those for specifying VALUE on the first operand.
LIST or NOLIST
LIST directs the subcommand to display the results of the comparison at
your terminal. NOLIST suppresses the display of the results of the
comparison at your terminal.
MASK(mask) or NOMASK
MASK(mask) defines a value that is logically ANDed with both compare
operands before performing the comparison. The mask must be the same
size as the data items being compared. The mask value must be a general
value. See Chapter 2, “Literal values,” on page 9 for information about
specifying a general value. NOMASK suppresses masking.

88 z/OS MVS IPCS Commands

 COMPARE subcommand

PAD[(value)] or TRUNCATE
PAD authorizes numeric comparison and comparison of operands of
differing lengths by padding the shorter compare operand before
comparison. PAD(value) specifies a 1-byte value to be used to pad data
before comparison. Either a character (C′c′) or a hexadecimal (X'xx') value
may be specified.
TRUNCATE specifies that a string comparison be performed and that
comparison of operands of differing length be performed by truncating the
longer compare operand to the length of the shorter before comparison.
v Return codes

Code Explanation
00 The operands are equal.
04 The first operand is low.
08 The first operand is high.
12 The comparison is incomplete.

v Example: In the BLSCCOMP CLIST, instructions find the address space vector
table (ASVT) from field CVTASVT in the communications vector table (CVT). A
COMPARE subcommand compares the ASVT identifier field, ASVTASVT, with
the character string ′ASVT′. If the comparison returns a nonzero completion
code, the CVTASVT field that points to the ASVT might be damaged. The
COMPARE subcommand is:
COMPARE ADDRESS(&ASVT+200) CHARACTER LENGTH(4)/* ASVTASVT */+
WITH(VALUE(C’ASVT’)) /* Expected, normal value */
See the BLSCCOMP member in the IBM-supplied SYS1.SBLSCLI0 library for the
complete listing.

COPYCAPD subcommand — copy captured dump data

Use the COPYCAPD subcommand to generate a report showing all captured
dumps present in a standalone dump and then copy the captured dump data to an
output data set. The generated report contains the following information:
v An ordinal number arbitrarily associated with the captured dump.
v The time when the dump capture process was started.
v The dump title.
v If present, the name of the dump data set to which part of the captured dump
was written.
v Syntax

Chapter 5. IPCS subcommands 89

COPYCAPD subcommand

COPYCAPD
{ captured-dump-number }
{ OUTDSNAME(dsname)|OUTDATASET(dsname)|ODS(dsname) }
{ OFILE(ddname)|OUTDDNAME(ddname) }
[ SPACE(nnnn[,mmmm]) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE|MAIN|STORAGE ]
[ DSNAME(dslist)|DATASET(dsname) ]
[ FILE(ddname)|DDNAME(ddname) ]
[ PATH(hfspath) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
captured-dump-number
Selects the captured dump to be copied. If this is omitted, COPYCAPD only
produces a report describing captured dumps.
OUTDSNAME(dsname) or OUTDATASET(dsname) or ODS(dsname)
OFILE(ddname) or OUTDDNAME(ddname)
Specifies the output data set into which the dump is to be copied. An output
data set must be specified. OUTDSNAME, OUTDATASET, or ODS specifies
the name of the output data set. After copying, IPCS closes and deallocates
the data set.
If the designated data set exists, it must be cataloged. It is dynamically
allocated and used by COPYCAPD. If the data set resides on a volume that
is not mounted as RESIDENT or RESERVED, MVS MOUNT authorization is
required.
If the designated data set does not exist, the system allocates a new data set
with the specified name and the defaults RECFM=FBS, LRECL=4160, and
system-determined BLKSIZE are used.
OFILE or OUTDDNAME specifies the ddname of the output data set. This
data set must be allocated by JCL or the TSO/E ALLOCATE command
before COPYCAPD is entered.
After copying, COPYCAPD closes the data set, but does not directly
deallocate it. You may use the JCL option FREE=CLOSE to release the data
set at the earliest possible moment.
SPACE(nnnn[,mmmm])
Specifies the primary space allocation, nnnn, and the secondary space
allocation, mmmm, if a new data set is created. Space is allocated in units of
4160-byte dump records. Excess space is released at the completion of
COPYCAPD processing.
If you omit this parameter, both the primary allocation and the secondary
allocation defaults are 1500 records. If only the primary allocation is
specified, the secondary allocation defaults to the primary allocation.
v Return codes

90 z/OS MVS IPCS Commands

 COPYCAPD subcommand

Code Explanation
00 End of file reached. The input data set has been closed and a dump has
been copied to the output data set.
16 Subcommand processing ended after detection of a problem in the IPCS
processing environment.
20 Subcommand processing ended as a result of an attention interruption you
generated. The input data set has been closed. The output data set has been
loaded with part of a dump.

v Example 1: Request a report only. Normally, an IPCS user will first request a
report to determine the available dump titles and time stamps. Once that
information has be evaluated, the user can request another COPYCAPD
subcommand to select a specific dump.
– Action
COMMAND ===> COPYCAPD
– Result:
When title text will not fit on the first line, it is broken at a blank or comma
and continued under the time stamp.

copycapd

Number Time stamp Title

------ ------------------- --------------------------------------------

1 09/19/2001 22:27:42 COMPON=GRS,COMPID=5752SCSDS,ISSUER=ISGREC,

MODULE=ISGWFP ,EP=ISGWFPR ,ABEND=S0602,REASON=00000000

1 captured dump processed

v Example 2: Request to report and copy the captured dump.

– Action
COMMAND ===> COPYCAPD 1 SPACE(5000) OUTDSN(my.captured.dump)
– Result

Chapter 5. IPCS subcommands 91

COPYDDIR subcommand

copycapd 1 space(5000) outdsn(my.captured.dump)

Number Time stamp Title

------ ------------------- --------------------------------------------

1 09/19/2001 22:27:42 COMPON=GRS,COMPID=5752SCSDS,ISSUER=ISGREC,

MODULE=ISGWFP ,EP=ISGWFPR ,ABEND=S0602,REASON=00000000

1 captured dump processed

BLS18169I Dump 1 is being copied

DATA SPACE ASID(X’0005’) DSPNAME(00003SDU) STOKEN(X’800027000000002E’)
DATA SPACE ASID(X’0005’) DSPNAME(00000SDU) STOKEN(X’800023000000002A’)
DATA SPACE ASID(X’0005’) DSPNAME(00001SDU) STOKEN(X’800025000000002B’)
DATA SPACE ASID(X’0005’) DSPNAME(00002SDU) STOKEN(X’800026000000002C’)
BLS18100I ASID(X’0005’) DSPNAME(00000SDU) 7EE73008 not available for PRDDATA

IEA11004I DAT-off nucleus could not be accessed.

IEA11005I 23 SUMDUMP pages were not accessible.
IEA11005I 1 first reference page was not accessible.
BLS18170I 57,669 records 239,903,040 bytes, copied

COPYDDIR subcommand — copy source description from dump

directory
Use the COPYDDIR subcommand to copy one or more source descriptions. A
description is a reference to a source of data, a dsname, ddname, or path.
Additional, optional records may also be present and copied:
v Some records may help you understand the significance of the source.
v Other records may enable IPCS to assist in analysis and formatting of its
contents.
v A few records may serve dual roles, symbols allowing you to refer to important
data by name and allowing IPCS to locate the same important data and check its
validity just once in the course of analyzing a dump.

COPYDDIR can perform three similar types of operations:

1. Copy operations transcribe records to the current session dump directory from
another dump directory. You designate the source directory via INDATASET,
INDDNAME, or aliases of those keywords. Multiple descriptions may be
selected for transcription in a single operation.
2. Import operations transcribe records to the current session dump directory
from a RECFM=VB data set. You designate the source RECFM=VB data via
INDATASET, INDDNAME, or aliases of those keywords. No selectivity is
supported. One description is copied.
3. Export operations transcribe records from either the current session dump
directory or another dump directory to a RECFM=VB data set.
v You imply the use of the current session dump directory by omitting
INDATASET, INDDNAME, and their aliases.
v You designate the source directory via INDATASET, INDDNAME, or aliases
of those keywords.
You designate the target RECFM=VB data set via the EXPORT keyword. The
same selection options supported for COPY may be used to select a single
description to be exported.

92 z/OS MVS IPCS Commands

 COPYDDIR subcommand

The main purpose of the COPYDDIR subcommand is to place the source

description of a dump or trace into your current user dump directory, so that you
can format and analyze the dump or trace.

See z/OS MVS IPCS User's Guide for information about dump directories.
v Syntax

COPYDDIR [ INDATASET(dsname)|INDSNAME(dsname) ]
[ INFILE(ddname)|INDDNAME(ddname) ]
[ EXPORT {(DSNAME(dsname))|(DATASET(dsname))} ]
{(FILE(ddname))|(DDNAME(ddname)) }
[ SUMMARY | NOSUMMARY ]
[ DSNAME(dslist)|DATASET(dslist) ]
[ FILE(ddname-range-list)|DDNAME(ddname-range-list) ]
[ PATH(path-name ...) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ TEST | NOTEST ]

v Parameters
Use a DSNAME, DATASET, FILE, DDNAME, or PATH parameter to specify the
source for the source description to be copied. You can request copying of more
than one source description. Note that you can also use a SCREEN keyword
with INDATASET or INFILE while the IPCS dialog is active in order to display
the COPYDDIR inventory panel for the input dump directory selected.
INDATASET(dsname) or INDSNAME(dsname)
INFILE(ddname) or INDDNAME(ddname)
Specifies the input for copy or import operations. One of these parameters is
required except when the EXPORT option is selected. EXPORT uses the
current session directory as a source of records when neither input dsname
nor input ddname are specified.

Note: Do not specify your current dump directory. Do not specify

IPCSDDIR as the ddname.
INDATASET or INDSNAME specifies the input directory by its data set
name.
INFILE or INDDNAME specifies the ddname of the input data set.
EXPORT(DSNAME(dsname)) or EXPORT(DATASET(dsname))
EXPORT(FILE(ddname)) or EXPORT(DDNAME(ddname))
Specifies a RECFM=VB data set to receive dump directory records pertaining
to one source. RECFM=VB data sets must have a LRECL of 3076 or larger.
SUMMARY or NOSUMMARY
SUMMARY indicates that a summary line containing the total number of
dump descriptions copied should be displayed and is the default.
NOSUMMARY suppresses the summary line unless one or more source
descriptions were not copied, for example, if error conditions exist, or if the
description already exists in the output directory. You might use
NOSUMMARY when running COPYDDIR within a CLIST or REXX exec.
DSNAME(dslist) or DATASET(dslist)

Chapter 5. IPCS subcommands 93

COPYDDIR subcommand

FILE(ddname-range-list) or DDNAME(ddname-range-list)
Specifies one or more data sets for the source descriptions to be copied. If
one of these parameters is not specified, the default is the SETDEF-defined
default source data set.
DSNAME or DATASET specifies the data set name or a list of data set
names of cataloged data sets. The dslist can include a wildcard character (*)
to represent any name. A data set name can contain a single asterisk in place
of any qualifier except the first. For example, DSNAME (A,*,C) specifies all
names with 3 qualifiers that have A as the first qualifier and C as the third
qualifier.
FILE or DDNAME specifies the ddname, a list of ddname, or a range of
ddnames for the data sets. For example, FILE(A:C) specifies all ddnames
from A to C, including A, AA, ABC, B, C, and so on.
When specifying more than one data set name or ddname, separate the
names with commas or blanks. When specifying a range of ddnames,
separate the first and last ddname with a colon.
PATH specifies the path-name or list of path-names of a file or directory on
a z/OS UNIX file.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the COPYDDIR subcommand.
v Example 1: Copy the source description for the dump data set MY.DUMP from
the sysplex dump directory, SYS1.DDIR, to your current user dump directory.
– Action
COMMAND ===> COPYDDIR INDSNAME(SYS1.DDIR) DSNAME(MY.DUMP)
– Result
COPYDDIR copies the source description for MY.DUMP from SYS1.DDIR into
your current user dump directory and displays a summary of the processing.
v Example 2: Copy source descriptions for multiple data sets to your current user
dump directory:
– Action
COMMAND ===> COPYDDIR FILE(W:X) DSNAME(MY.DUMP2) INDSNAME(DUMPDIR)
– Result
IPCS copies the source descriptions from the DUMPDIR directory for all data
sets beginning with W or X and data set MY.DUMP2 into your current user
dump directory. IPCS displays a summary of the processing.

COPYDUMP subcommand — copy dump data

Use the COPYDUMP subcommand to copy a single unformatted dump from one
data set to another. COPYDUMP also allows you to:
v Extract a single dump from a string of dumps in a data set
v Copy the records of multi-volume SADMP data sets, retaining the priority order
used during dumping.
v Reunite the portions of dump data that was previously split.
v Obtain a summary of all the dump titles in the data set
v Reduce the size of a dump by copying dump records from a specified list of
address spaces

94 z/OS MVS IPCS Commands

 COPYDUMP subcommand

Applications, such as IMS, can write several contiguous SYSMDUMPs in a single

data set. COPYDUMP can list the title of each dump in the data set and extract
one of the dumps from the data set.

SADMP to DASD uses the volumes of multi-volume data sets in parallel, writing
to each as rapidly as it is prepared to accept dump records. COPYDUMP
recognizes this and creates a copy in which the first data captured by SADMP
appears in the first records written without regard to which volume blocks were
written.

SADMP to DASD can exhaust the pre-allocated space associated with the initial
data set. You can designate second and subsequent data sets to cause a complete
SADMP to be written. COPYDUMP accepts a list of data set names and can create
a single dump data set for analysis from the several dump data sets to which
SADMP wrote.

You can use filtering options to produce a copy that has less records than the
original dump. This is particularly useful with a stand-alone dump. Specify
ASIDLIST, JOBLIST, or EASYCOPY to select ASIDs that are useful for your dump
analysis, leaving ASIDs that are usually not needed to analyze a problem. The
following types of copies may be produced:
v A primary copy, filtered if ASIDLIST, JOBLIST, or EASYCOPY options are
specified. (Note that these filtering options will remove available pages of the
system dumped by SADMP.)
v A FULL copy.
v A COMPLEMENT copy that contains those dump record removed from the
primary copy via filtering.
Each type of copy is optional. See the OUTDSNAME and OUTDDNAME options
for more information. See the specific filtering options regarding their use to
balance importance against size of the copy.

The output data set, into which the dump is copied, is closed after copying is
completed. The input data set, from which the dump was copied, is closed when
an end of file is encountered. If COPYDUMP completes without reaching an end of
file, an option determines whether the input data set is closed or remains open. If
it remains open, the input data set is positioned for another COPYDUMP
subcommand to resume processing with the next dump.
v Syntax

Chapter 5. IPCS subcommands 95

COPYDUMP subcommand

COPYDUMP
{ OUTDSNAME(outds-spec)|OUTDATASET(outds-spec)|ODS(outds-spec) }
{ OUTFILE(outdd-spec)|OFILE(outdd-spec)|OUTDDNAME(outdd-spec) }
[ INDSNAME(dsname_list)|INDATASET(dsname_list)|IDS(dsname_list) ]
[ INFILE(ddname_list|IPCSINDD)| IFILE(ddname_list|IPCSINDD)
| INDDNAME(ddname_list|IPCSINDD) ]
[ DEFAULT ]
[ SPACE(nnnn[,mmmm]|1500,1500) ]
[ CLOSE | LEAVE ]
[ ASIDLIST(ddddd[,ddddd]) ]
[ JOBLIST(j1[,j2][,j3]..[,jn]) ]
[ NOSKIP | SKIP[(nnn|1|EOF)] ]
[ NOCLEAR | CLEAR ]
[ EASYCOPY ]

where
outds-spec := dsname [ INITIALIZE | INITAPPEND] | NULLFILE
[ COMPLEMENT(dsname | NULLFILE) ]
[ FULL(dsname [INITIALIZE]) | NULLFILE]

outdd-spec := ddname [ INITIALIZE | INITAPPEND] [ COMPLEMENT(ddname) ]

[ FULL(ddname [INITIALIZE]) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ CONFIRM | NOCONFIRM ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
OUTDSNAME(outds-spec) or OUTDATASET(outds-spec) or ODS(outds-spec)
OUTFILE(outdd-spec) or OFILE(outdd-spec) or OUTDDNAME(outdd-spec)
Specifies the output data set into which the subset dump, complementary
dump and full dump are to be copied. At least one output data set must be
specified, unless SKIP(EOF) is specified; if SKIP(EOF) and any output data
set are both specified, IPCS ignores the output data set. If NULLFILE is
specified for any output dataset, then IPCS ignores that output dataset.
NULLFILE can be specified only for dsnames and not for ddnames.
OUTDSNAME, OUTDATASET, or ODS specifies the name of the output
data set. The COMPLEMENT and the FULL data sets can be specified only
if ASIDLIST or JOBLIST is specified. The COMPLEMENT data set contains
the complement of the subset dump. The FULL data set contains the input
dump specified. If a list of input data sets is specified, the input dump is
merged and written into the FULL data set. After copying, IPCS closes and
deallocates the data set.
If the designated data set exists, it must be cataloged. It is dynamically
allocated and used by COPYDUMP. If the data set resides on a volume that
is not mounted as RESIDENT or RESERVED, MVS MOUNT authorization is
required.
If the designated data set does not exist, the system allocates a new data set
with the specified name and the defaults RECFM=FBS, LRECL=4160, and
system-determined BLKSIZE are used. Use the SPACE parameter to indicate
the amount of space to be allocated. If the SPACE parameter is omitted,
COPYDUMP uses default amounts.
OUTFILE, OFILE or OUTDDNAME specifies the ddname of the output data
set. This data set must be allocated by JCL or the TSO/E ALLOCATE

96 z/OS MVS IPCS Commands

 COPYDUMP subcommand

command before COPYDUMP is entered. The COMPLEMENT and the

FULL data sets can be specified only if ASIDLIST or JOBLIST is specified.
The COMPLEMENT data set contains the complement of the subset dump.
The FULL data set contains the entire dump specified. If a list of input
dumps is specified, the input dump is merged and written into the FULL
data set.
After copying, COPYDUMP closes the data set, but does not directly
deallocate it. You must use the JCL option FREE=CLOSE to release the data
set at the earliest possible moment.
If the INITIALIZE option is specified with any of the output data sets or
ddnames, then IPCS will create the dump directory entries and perform
dump initialization for those output dump data sets. INITIALIZE cannot be
specified when NULLFILE is specified and is not used with COMPLEMENT
data sets.
If the INITAPPEND option is specified with output data sets or ddnames,
IPCS performs the following actions; these allow IPCS to avoid repeated
initialization in the future:
– create the dump directory entries
– perform dump initialization for those output dump data sets
– add the dump directory entries to the end of the output data set
INITIALIZE and INITAPPEND cannot be specified with the NULLFILE
| operand. If specified together, you will receive message BLS18159I or
| BLS18259I respectively. INITAPPEND is not used with COMPLEMENT data
sets. If both INITIALIZE and INITAPPEND options are specified, then
INITAPPEND is preferred. If the INITAPPEND option is specified for an
appended dump, the dump description will be refreshed using the current
DDIR.
The specified or resulting output data set should not match any specified or
resulting input data set or data sets. Trying to copy a dump to itself can
result in a loss of data.
INDSNAME(dsname_list) or INDATASET(dsname_list) or IDS(dsname_list)
INFILE(ddname_list|IPCSINDD) or IFILE(ddname_list|IPCSINDD) or INDDNAME
(ddname_list|IPCSINDD)
Specifies one or more input data sets from which the dump is copied. If one
of these parameters is not specified, IPCS takes the following actions:
– If an open data set is available, COPYDUMP resumes processing the open
data set.
– If no open data set is available, COPYDUMP opens the default input data
set, IPCSINDD, and begins processing with the first record.
INDSNAME, INDATASET, or IDS specifies the input data set or a list of
input data sets. The designated data sets must exist and must be cataloged.
After copying, COPYDUMP closes and deallocates the input data sets.
If a prior COPYDUMP subcommand left a designated data set open,
processing of the data set is resumed where it left off. Note that INDSNAME
or INDATASET cannot be used to resume processing of a data set initially
opened using INFILE or IFILE or INDDNAME.
If a designated data set is not open, it is dynamically allocated, opened, and
processed beginning with the first record,
If a designated data set resides on a volume that is not mounted as
RESIDENT or RESERVED, MVS MOUNT authorization is required.

Chapter 5. IPCS subcommands 97

COPYDUMP subcommand

INFILE, IFILE or INDDNAME specifies the ddname, or a list of ddname of

the input data sets. The designated data sets must be allocated by JCL or the
TSO/E ALLOCATE command before COPYDUMP is entered. After copying,
COPYDUMP closes the input data sets. but does not directly deallocate
them. You must use the JCL option FREE=CLOSE to release the data sets at
the earliest possible moment.
If a prior COPYDUMP subcommand left a designated data set open,
processing of the data set is resumed where it left off. Note that INFILE or
IFILE or INDDNAME may not be used to resume processing of a data set
initially opened using INDSNAME or INDATASET.
If a designated data set is not open, it is dynamically allocated, opened, and
processed beginning with the first record.

Note: You can specify the ddname_list option to combine STANDALONE or

TDUMP dumps that have been taken to more than one dataset.
The specified or resulting output data set should not match any specified or
resulting input data set or data sets. Trying to copy a dump to itself can
result in a loss of data.
PATH(path-name ...)
Specifies a path-name or list of path-names of a file or directory on a z/OS
UNIX file to be processed.
DEFAULT
Specifies that the output data set is to become the current source. If the
subcommand specifies a data set name with a password, the data set name
and password become the name of the current source.
IPCS changes the current source in both the local and global defaults. If you
omit this parameter, or if the subcommand fails, the current source is not
changed in the defaults.

Note: If the output data set is specified by OUTFILE or OFILE or

OUTDDNAME, the function of the DEFAULT parameter is nullified.
SPACE(nnnn[,mmmm])
Specifies the primary space allocation, nnnn, and the secondary space
allocation, mmmm, if a new data set is created. Space is allocated in units of
4160-byte dump records. Excess space is released at the completion of
COPYDUMP processing. If you omit this parameter, both the primary
allocation and the secondary allocation defaults are 1500 records. If only the
primary allocation is specified, the secondary allocation defaults to the
primary allocation.
CLOSE or LEAVE
CLOSE directs COPYDUMP to close the input data set immediately after the
dump has been copied. LEAVE directs COPYDUMP to allow the input data
set to remain open if processing of the subcommand completes before
reaching an end of file. The input data set is always closed if COPYDUMP
completes after reaching the end of file. If the IPCS session ends, the input
data set is automatically closed.
ASIDLIST(asid[:asid])
Specifies ASIDs for the address spaces and their associated data spaces to be
copied; dump records for other address spaces and their associated data
spaces are not copied.

98 z/OS MVS IPCS Commands

 COPYDUMP subcommand

The asid can be a single ASID or an ASID range. When you specify a range,
separate the first and last ASID in the range with a colon. An ASID can be 1
through 65535. An ASID can be expressed in the notation X'asid' or in
decimal. An unqualified number is assumed to be decimal.

Note: No matter what ASID you specify on this parameter, COPYDUMP

always copies the dump records for address spaces 1 through 4 to the
output data set. Correspondingly, when you analyze a copied dump, you
might see common storage for an ASID not specified on the ASIDLIST
parameter because common storage is stored in a dump with ASID(X'0001').
JOBLIST(j1[,j2][,j3]...[,jn])
Specifies job names for the address spaces and their associated data spaces
to be copied; dump records for other address spaces and their associated
data spaces are not copied. The JOBLIST can contain a single job name or a
list of job names. When you specify a list, separate the job names with a
comma. The job name can be 1 to 8 characters.

Note: No matter what job name you specify on this parameter, COPYDUMP
always copies the dump records for address spaces 1 through 4 to the
output data set. Correspondingly, when you analyze a copied dump, you
might see common storage for a job name not specified on the JOBLIST
parameter because common storage is stored in a dump with ASID(X'0001').
SKIP[(nnn | 1 | EOF)] or NOSKIP
SKIP(nnn) specifies the number of dumps, nnn, in the input data set to be
skipped before copying begins. Each dump title encountered in the input
data set is displayed when it is read.
If you enter SKIP but no number, one dump is skipped.
If you specify SKIP(EOF), COPYDUMP skips to the end of the data set,
displaying all dump titles that are encountered during that process; however,
no copying is performed. Also, the output data set is not needed if
SKIP(EOF) is specified.
NOSKIP specifies that no dumps are to be skipped before copying begins.
NOCLEAR or CLEAR
NOCLEAR specifies that the input data set should not be cleared after the
copy. CLEAR directs COPYDUMP to clear the input data set after the dump
has been copied.

Note: Because IPCS allocates the input data set with a disposition of SHR,
use caution if the input data set is being used by other users. Do not clear
the dump data set while other users are still using it.
EASYCOPY
If EASYCOPY is specified, one of following events will occur depending on
z/OS release, which produced selected source dump:
– For z/OS V1R10 dumps, the JOBLIST and ASID RANGE fields will be
ignored, and a JOBLIST entry created with a predefined list of system
address space names. The JOBLIST includes the following fourteen job
names: ALLOCAS, ANTAS000, ANTMAIN, CATALOG, CONSOLE,
DEVMAN, DUMPSRV, IEFSCHAS, IOSAS, IXGLOGR, JESXCF, JES2, JES3,
and OMVS.
– For z/OS V1R8 and V1R9 dumps, the JOBLIST and ASID RANGE fields
will be ignored, and an ASID entry created with a range of 1 to 20.

Chapter 5. IPCS subcommands 99

COPYDUMP subcommand

Note: COPYDUMP always copies the dump records for address spaces 1
through 4 to the output data set. Correspondingly, when you analyze a
copied dump, you might see common storage for an ASID not specified
because common storage is stored in a dump with ASID(X'0001').
CONFIRM or NOCONFIRM
CONFIRM specifies that the subcommand is to request your confirmation
before performing the copy operation. The subcommand displays the title of
the dump to be copied. It then requests your confirmation.
– If you enter Y, the subcommand copies the dump into the output data set
and drops any existing records in the dump directory associated with the
output data set.
– If you enter N, the subcommand ends without copying the dump into the
output data set, and ignores the DEFAULT parameter, if specified. The
LEAVE/CLOSE parameter determines if the input data set is left open.
NOCONFIRM specifies that the subcommand is not to request your
confirmation before copying the dump into the output data set and
dropping any entries in the dump directory that are associated with the
specified dump name.
If you omit both CONFIRM and NOCONFIRM, the subcommand uses the
default (established through SETDEF) for this parameter.
Restriction: When using IPCS in the background or while in the IPCS
full-screen dialog, you may not specify CONFIRM. Specify NOCONFIRM
either on this subcommand or on the SETDEF subcommand.
v Return codes

Code Explanation
00 End of file reached. The input data set has been closed and a dump has
been copied to the output data set.
04 End of dump reached. The input data set has been left open, positioned
immediately after the dump copied by this subcommand.
08 End of file reached before reaching the dump to be copied. (This return
code is always produced if SKIP(EOF) is specified and COPYDUMP
reaches end of file.)
12 Subcommand processing ended for one of the following reasons:
v COPYDUMP requested your confirmation and confirmation was not
received. The CLOSE option was in effect.
v The COPYDUMP subcommand cannot be interpreted. No input data
set was left open by a prior run of COPYDUMP.
v You generated an attention interrupt before any COPYDUMP
processing. No input data set was left open by a prior run of
COPYDUMP.
v COPYDUMP read an incorrect dump header record as the initial
record of the input data set. The CLOSE option was in effect. The
input data set has been closed, and the output data set (if any) has not
been altered.
16 Subcommand processing ended after detection of a problem in the IPCS
processing environment.
20 Subcommand processing ended as a result of an attention interruption
you generated. The input data set has been closed. The output data set
has been loaded with part of a dump.

100 z/OS MVS IPCS Commands

 COPYDUMP subcommand

Code Explanation
24 Subcommand processing ended for one of the following reasons:
v COPYDUMP requested your confirmation and confirmation was not
received. The LEAVE option was in effect.
v The COPYDUMP subcommand cannot be interpreted. An input data
set was left open by a prior run of COPYDUMP.
v An attention interruption was generated by you during COPYDUMP
skip processing. The LEAVE option was in effect.
v COPYDUMP read an incorrect dump header record as the initial
record of the input data set. The LEAVE option was in effect. The
input data set has been left open, and the output data set (if any) has
not been altered.
28 An error occurred when COPYDUMP attempted to open the input data
set for output with the CLEAR option in effect. The input data set was
copied to the output data set, but the input data set was not cleared.

COPYTRC subcommand — copy trace entries or records

Use the COPYTRC subcommand to copy GTF trace records to an output data set
from trace data sets or trace buffers in dump data sets. You can also use COPYTRC
to copy component trace entries to an output data set from trace data sets or trace
buffers in dump data sets. You can use COPYTRC to:
v Combine trace data sets, or trace entries or records in dump data sets, or both,
into a single data set.
v Extract trace entries or records from buffers in SVC and stand-alone dumps.
v Combine trace entries or records from multiple systems. When COPYTRC
combines trace entries or records from several systems into a single data set, it
marks the system of origin for each trace entry or record in the output data set.
v Extract trace entries or records for a specified list of systems from combined
trace entries or records.

You can run COPYTRC by entering the subcommand or using the panels on option
5.3 of the IPCS dialog.

The main function of the COPYTRC subcommand is to aid in processing multiple

trace sources. Suppose you have multiple GTF data sets from a run on a single
system. Before using GTFTRACE to process all of the trace data, you must
combine all GTF trace records into a single data set using COPYTRC.

Note:
1. To process multiple GTF data sets from multiple systems, you can either:
v Combine the trace records into a single data set with COPYTRC
v Keep the trace data sets separate and use the MERGE subcommand to
format the traces
2. COPYTRC cannot process GTF trace records and component trace entries at the
same time. So, for COPYTRC input sources, specify all GTF trace sources, or all
component trace sources, but not a mix of both traces. To see GTF trace records
and component trace entries chronologically in a single report, use the MERGE
subcommand.

COPYTRC does not have a default input or output data set name or ddname.

Chapter 5. IPCS subcommands 101

COPYTRC subcommand

After the entries or records are copied, COPYTRC closes both the input and output
data sets and displays a summary of the trace entries or records that were copied.
v Related subcommands
– CTRACE
– GTFTRACE
– MERGE
v Syntax

COPYTRC [ TYPE(GTF|CTRACE) ]
{ INDATASET(dslist)|INDSNAME(dslist)|IDS(dslist) }
{ INFILE(ddlist)|INDDNAME(ddlist) }
{ OUTDATASET(dsname)|OUTDSNAME(dsname)|ODS(dsname) }
{ OUTFILE(ddname)|OUTDDNAME(ddname) }
[ SPACE(pppp[,ssss]|50,50) ]

-------- Data Selection Parameters -------------------------

[ OPTIONS((ALL|filters)) ]
[ START(mm/dd/yy,hh.mm.ss.dddddd) ]
[ STOP(mm/dd/yy,hh.mm.ss.dddddd) ]
[ SYSNAME(sysname[,sysname]...) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
TYPE(GTF | CTRACE)
Specifies the type of trace data to be copied. COPYTRC will copy trace data
generated by either GTF or component traces. These two types of traces may
not be combined. If the TYPE parameter is omitted, COPYTRC tries to copy
GTF trace records.
INDATASET(dslist) or INDSNAME(dslist) or IDS(dslist)
INFILE(ddlist) or INDDNAME(ddlist)
Specifies the data sets containing the traces to be copied. Use these
parameters in any combination. All data sets should contain the same type
of trace. To specify multiple input data sets, use any combination of the
following data sets:
– Trace data sets created by GTF or CTRACE
– Trace data sets created by COPYTRC
– SVC, stand-alone dump, and SYSMDUMP dump data sets
An example of a combination of parameters follows:
COMMAND ===> COPYTRC INFILE(GTFDINDD) INDATASET(MY.GTFDATA1,MY.GTFDATA2) ...
INDATASET, INDSNAME, or IDS specifies the input data set or sets. When
specifying more than one data set name, separate the names with commas or
blanks. IPCS dynamically allocates each input data set. If a data set is not
open, COPYTRC opens the data set after it is dynamically allocated.
Each designated data set must exist and must be cataloged to allow the
system to locate it. If a data set resides on a volume that is not mounted as
RESIDENT, MVS MOUNT authorization is required.

102 z/OS MVS IPCS Commands

 COPYTRC subcommand

After copying, IPCS closes and deallocates each data set. When the
SETDEF-defined default source is specified as an input data set, IPCS does
not close or deallocate the data set.
INFILE or INDDNAME specifies the ddname of the input data set or sets.
Before using INFILE or INDDNAME, you must allocate each data set using
JCL or the TSO/E ALLOCATE command. IPCS opens the data sets.
When specifying more than one ddname, separate the names with commas
or blanks.
When IPCS finishes copying, it closes the data set, but does not directly
deallocate it. You can use the JCL FREE=CLOSE to release each data set.
When the SETDEF-defined default source is specified as an input data set,
IPCS does not close or deallocate it.
OUTDATASET(dsname) or OUTDSNAME(dsname) or ODS(dsname)
OUTFILE(ddname) or OUTDDNAME(ddname) or OFILE(ddname)
Specifies the output data set into which the traces are to be copied. The
COPYTRC subcommand must specify an output data set.
OUTDATASET, OUTDSNAME, or ODS specifies the output data set. If the
designated data set exists, it is dynamically allocated and used by
COPYTRC. The data set must be cataloged. If the data set resides on a
volume that is not mounted as RESIDENT or RESERVED, MVS MOUNT
authorization is required.
If the designated data set does not exist, the system allocates a new data set
with the specified name. Use the SPACE parameter to indicate the amount
of space to be allocated. If the SPACE parameter is omitted, COPYTRC uses
default amounts.
After the copying, IPCS closes and deallocates the data set.
OUTFILE or OUTDDNAME specifies the ddname of the output data set.
Before using COPYTRC, you must allocate this data set using JCL or the
TSO/E ALLOCATE command.
After the copying, IPCS closes the data set but does not directly deallocate it.
COPYTRC processing might open and close the output data set more than
once. Do not use options on the DD statement, such as RLSE or
FREE=CLOSE that conflict with the multiple open and close operations.
IBM recommends to use the same BLOCKSIZE for the output data set as for
the input data set. Using different BLOCKSIZE may cause some data not to
be captured when START or STOP times are specified.
SPACE(pppp[,ssss] | 50,50)
Specifies the number of tracks for the primary space allocation, pppp, and the
secondary space allocation, ssss for a new data set. The system releases
excess space at the completion of COPYTRC processing. If you omit this
parameter, both the primary allocation and the secondary allocation defaults
are 50 tracks. If only the primary allocation is specified, the secondary
allocation defaults to the primary allocation.
v Data Selection Parameters
All data selection parameters are optional. If specified, COPYTRC copies only
trace entries or records that meet the specified data selection requirement.
OPTIONS((ALL | filters))
Specifies filtering options for a particular component trace. ALL indicates

Chapter 5. IPCS subcommands 103

COPYTRC subcommand

that COPYTRC is to copy all component traces. filters lists the trace names to
be used as filters; filters has the following syntax:
COMP(name) [SUB(name[.name]...)][,...]

You may specify complete trace names or partial trace names. Separate each
partial or complete trace name by a comma. If you specify a partial trace
name, COPYTRC copies each trace that matches the partial trace name.
For example, if you specify OPTIONS((COMP(COMP1) SUB(ASID(200)))), the
following traces match this partial trace name:
– COMP1.ASID(0200).FUNC2.SVC3
– COMP1.ASID(0200).FUNC1.SVC3

Note: You must specify TYPE(CTRACE) to use the OPTIONS parameter.

START(mm/dd/yy,hh.mm.ss.dddddd)
Specifies the beginning date and time for the trace entries or records to be
copied. When you do not specify START, IPCS starts at the beginning of the
trace entries or records. Specify the date and time in mm/dd/
yy,hh.mm.ss.dddddd format.
mm represents months
dd represents days
yy represents years
hh represents hours
mm represents minutes
ss represents seconds
dddddd
represents decimal fractions of seconds
These rules apply to the date and time specifications:
– You must specify a date and time on the START parameter.
– The month and day can be specified in either single or double digits.
– Separate the date from the time with a comma.
– The time must be Greenwich mean time (GMT).
– Hours, minutes, and seconds can be specified in single or double digits.
– The time can be truncated anywhere on the right.
– The time can be left off completely, in which case, it will default to
00:00:00.000000 (midnight).
Table 7 shows examples of valid date and time formats.
Table 7. Examples of valid date and time formats
Valid date formats Valid time formats
m/dd/yy hh.mm.ss.dddddd
mm/d/yy hh.mm.ss.dd
m/d/yy hh.mm.ss
mm/dd/yy h.m.s
hh.mm
hh

STOP(mm/dd/yy,hh.mm.ss.ddddddd)
Specifies the ending date and time for the trace entries or records to be

104 z/OS MVS IPCS Commands

 COPYTRC subcommand

copied. When you do not specify STOP, IPCS stops copying after the last
trace entry or record. For guidelines on how to specify the date and time,
see the START parameter.
SYSNAME(sysname[,sysname]...)
Requests that the trace entries or records should be copied only if the trace's
system name matches one of the system names in the list. SYSNAME
accepts up to 16 system names in the list.
v Return codes

Code Explanation
00 End of file reached. The input data set has been closed and all trace
entries or records have been copied to the output data set.
04 No valid trace entries or records meeting the selection criteria were
found. No trace data was copied to the output data set.
08 A processing error occurred. Some, but not all trace entries or records
were copied to the output data set.
12 An error occurred in COPYTRC processing. No trace entries or records
were copied to the output data set.
16 Dynamic allocation of the output data set failed. No trace entries or
records were copied to the output data set.
20 The COPYTRC subcommand has a syntax error.
24 The COPYTRC subcommand has a semantic error.

COUPLE subcommand — analyze cross-system coupling data

Use the COUPLE subcommand to generate reports about the cross-system
coupling facility (XCF). This subcommand provides information about the
following:
v Groups and members in the sysplex
v Sysplex couple datasets
v XCF signaling service
v XCF storage use
v Status of systems in the sysplex
v XCF internal diagnostic information
v Coupling Facility Resource Management (CFRM)
v Automatic restart management

The COUPLE subcommand does not process active storage.

The reports generated by the COUPLE subcommand contain information for IBM
diagnostic use. IBM might ask you to report this information for use in problem
determination.

See the XCF component in z/OS MVS Diagnosis: Reference for COUPLE output.
v Syntax

Chapter 5. IPCS subcommands 105

COUPLE Subcommand

COUPLE

--------- Report Type Parameters ---------------------------

[ GROUP ]
[ SERIAL ]
[ SIGNAL ]
[ STORAGE ]
[ SYSPLEX ]
[ XCFSTACK ]
[ CFRM ]
[ ARM ]

--------- Data Selection Parameters ------------------------

[ DETAIL ]
[ EXCEPTION ]
[ SUMMARY ]

--------- Address Space Selection Parameters ---------------

[ ASID(asidlist) ]
[ JOBNAME(joblist) ]

--------- Additional Filter Parameters ---------------------

[ CFNAME(cfname) ]
[ STRNAME(strname) ]
[ SYSNAME(sysname) ]
[ GRPNAME(grpname) ]
[ DEVICE(device) ]
[ TYPE(type) ]
[ ELEMENT(element) ]
[ RSTGROUP(rstgroup) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report type parameters

Use these parameters to select the type of report. You may specify more than
one; COUPLE produces a report for each specified parameter. If you omit these
parameters, the default is to present a report for all of the following parameters:
GROUP
Requests information about the groups in the sysplex and the status of
members within each group.
SERIAL
Requests information about the XCF couple data sets.

106 z/OS MVS IPCS Commands

 COUPLE Subcommand

SIGNAL
Requests information about XCF signaling services. This report includes
information about signaling paths, transport classes, message buffers, list
structures, and devices in use.
STORAGE
Requests information about XCF storage use.
SYSPLEX
Requests information about the status of each system in the sysplex. This
includes sysplex failure management (SFM) information.
XCFSTACK
Requests internal diagnostic information. This information may be requested
by the IBM Support Center.
CFRM
Requests information about coupling facility resource management.
ARM
Requests information about elements and restart groups for the system
where the dump was taken.
v Data selection parameters
Data selection parameters limit the scope of the data in the report. The default is
to present a summary report.
SUMMARY
Requests summary information for each of the requested topics.
EXCEPTION
Requests a list of exceptional or unusual conditions for each topic. The list of
exceptions contains information for IBM diagnostic use.
DETAIL
Requests a report showing detailed information for each of the selected
topics.
v Address Space Selection Parameters
Use these parameters to obtain data from particular address spaces, which you
specify by their address space identifiers (ASIDs).
ASID(asidlist)
Specifies the ASID for the address space to be included in the report. The
asidlist can be a single ASID, a range of ASIDs, or a list of noncontiguous
ASIDs. When you specify a range, separate the first and last ASIDs in the
range with a colon. When you specify a list, separate the list members with
commas. The ASID can be 1 through 65535. An ASID can be expressed in
the notation X'nnn' or decimal, nnn.
JOBNAME(joblist)
Specifies a list of job names whose associated address spaces are to be
included in the report. Use commands to separate the job names in the list;
do not enclose job names in apostrophes; and do not specify a range of job
names. You may use an asterisk (*) at the end of a job name as a generic
character. That will result in a match for any value that begins with the
characters preceding the asterisk.
v Additional filter parameters
Use these parameters to select the information for the report.
CFNAME(cfname)
Requests that only information about the specified coupling facility be

Chapter 5. IPCS subcommands 107

COUPLE Subcommand

included in the report. cfname may also be a list of coupling facilities. You
may use an asterisk (*) at the end of cfname as a generic character. That will
result in a match for any value that begins with the characters preceding the
asterisk.
STRNAME(strname)
Requests that only information about the specified coupling facility structure
be included in the report. strname may also be a list of coupling facility
structures. You may use an asterisk (*) at the end of strname as a generic
character. That will result in a match for any value that begins with the
characters preceding the asterisk.
SYSNAME(sysname)
Requests that only information about the specified system be included in the
report. sysname may also be a list of systems. You may use an asterisk (*) at
the end of sysname as a generic character. That will result in a match for any
value that begins with the characters preceding the asterisk.
GRPNAME(grpname)
Requests that only information about the specified group be included in the
report. grpname may also be a list of groups. You may use an asterisk (*) at
the end of grpname as a generic character. That will result in a match for any
value that begins with the characters preceding the asterisk.
DEVICE(device)
Requests that only information about the specified device be included in the
report. device may be a list or range of devices. You must specify
hexadecimal values.
TYPE(type)
Requests that only information about the specified couple data set be
included in the report. type may also be a list of couple data sets.
ELEMENT(element)
Requests that only information about the specified element be included in
the report. element may also be a list of elements.
RSTGROUP(rstgroup)
Requests that only information about the specified restart group be included
in the report. rstgroup may also be a list of restart groups.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the COUPLE subcommand.

CTRACE subcommand — format component trace entries

Use the CTRACE subcommand to process component trace entries in a dump or
trace data set. CTRACE has two basic functions:
v Identify components and applications that have component trace entries in a
dump or trace data set. The QUERY parameter provides this function.
v Process the trace entries in a dump or trace data set.

To process trace entries, CTRACE allows you to:

v Select the traces to be processed
v View formatted trace entries
v Limit the information displayed for each formatted trace
v List entry identifiers for a trace

108 z/OS MVS IPCS Commands

 CTRACE subcommand

v Count the number of occurrences of each trace entry

Additional data selection can be done with a component-supplied or user-written

routine. You can use the OPTIONS parameter to pass parameters to data selection
and formatting routines.

The following books provide more information:

v z/OS MVS Diagnosis: Tools and Service Aids tells how to request and format
IBM-supplied component traces and shows trace output from IBM-supplied
traces.
v z/OS MVS IPCS Customization describes the steps needed to set up formatting for
your application's traces with CTRACE.
v Syntax

CTRACE

{ QUERY[(compname) [SUB((name[.name]...))]] }
{ }
{ [SYSNAME(name)] COMP(name) [SUB((name[.name]...))] }

-------- Report Type Parameters ----------------------------

[ SHORT ]
[ SUMMARY ]
[ FULL ]
[ TALLY ]

-------- Data Selection Parameters -------------------------

[ GMT|LOCAL ]
[ START(mm/dd/yy,hh.mm.ss.dddddd) ]
[ STOP(mm/dd/yy,hh.mm.ss.dddddd) ]
[ EXCEPTION ]
[ LIMIT(nnnnnnnn) ]
[ ENTIDLIST(entidlist) ]
[ USEREXIT(exitname) ]
[ OPTIONS((component routine parms)) ]

-------- Address Space Selection Parameters ----------------

[ ALL ]
[ CURRENT ]
[ ERROR ]
[ TCBERROR ]
[ ASIDLIST(asidlist) ]
[ JOBLIST(joblist)|JOBNAME(joblist) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

Note: The PATH keyword is only intended to refer to a dump data set, not an
external trace.
v Parameters

Chapter 5. IPCS subcommands 109

CTRACE subcommand

QUERY[(compname) [SUB((name[.name]...))]]
Requests component trace status information based on the level of the
request and the number of traces within an available component.
Specify QUERY with no component name to request a list of the names of
components or applications that have traces defined in a dump or trace data
set. For multiple-trace components, the report lists each SUB level trace
name for that component.
To request various summary trace reports for a component, do the following:
– For single-trace components, specify QUERY with a component name.
The output lists the date and time of the first and last entries for that
trace. If that trace is in a dump data set, specify FULL to list the trace
options that were active for the trace at the time of the dump.
– For multiple-trace components, you may request a list of traces defined
to a HEAD level or summary trace information for a single trace.
- For a list of traces defined to a HEAD level, specify QUERY either with
the HEAD level component name or with the component name and
HEAD name on the SUB parameter.
- For summary trace information for a single trace, specify QUERY with
the component name and complete SUB name of the trace. The report
lists the date and time of the first and last entries for that trace. If that
trace is in a dump data set, specify FULL to list the trace options that
were active for the trace at the time of the dump.
GMT, LOCAL and OPTIONS are the only data selection parameters that
may be specified with QUERY. GMT is the default.
QUERY is the default parameter on the CTRACE subcommand. If you
specify CTRACE with no additional parameters, IPCS will process a general
query request.
[SYSNAME(name)] COMP(name) [SUB((name[.name]...))]
Specifies the trace to be processed. If the trace to be processed comes from a
component or application that uses a single trace, use only the COMP
parameter to identify that trace. Use the SUB parameter with COMP to
identify a trace that is part of a multiple-trace component.
The SYSNAME parameter allows only trace entries from a particular system
to be processed for a particular trace.
Do not specify a partial trace name for formatting.
Report type parameters, data selection parameters, and address space
selection parameters control the output produced by this parameter.
To identify components for which you can view component trace entries, use
QUERY. z/OS MVS Diagnosis: Tools and Service Aids identifies the value for
the COMP parameter for each component that supports tracing.
v Report type parameters
Use these parameters to select the type of report. If you omit a report type
parameter, the default is SHORT.
SHORT
Requests that one line of output be produced for each requested trace entry.
The line includes the component mnemonic, entry identifier, date and time,
and a description of the entry.

110 z/OS MVS IPCS Commands

 CTRACE subcommand

SUMMARY
Requests that key fields from each qualifying trace entry be printed
following the date, time, and entry description.
FULL
Requests that all the data in each qualifying trace entry be formatted
following the date, time, and entry description line.
TALLY
Requests a list of trace entry definitions for the component and counts how
many times each trace entry occurred.
If you need only to format entry identifier definitions, specify a small
number in the LIMIT parameter to avoid reading all the trace entries.
Otherwise, if you do not place a limit on the number of trace entries
processed, TALLY finds the number of occurrences of each trace entry and
the average interval, in microseconds, between occurrences.
v Data selection parameters
Use these parameters to limit the number of trace entries. All data selection
parameters are optional.
GMT or LOCAL
GMT indicates that the time specified is Greenwich mean time. LOCAL
indicates that the time specified is local time.
START(mm/dd/yy,hh.mm.ss.dddddd)
Specifies the beginning date and time for the trace entries to be formatted.
When you do not specify START, IPCS starts at the beginning of the trace
entries. Specify the date and time in mm/dd/yy,hh.mm.ss.dddddd format
mm represents months
dd represents days
yy represents years
hh represents hours
mm represents minutes
ss represents seconds
dddddd
represents decimal fractions of seconds
These rules apply to the date and time specifications:
– The date section can be specified as an asterisk (*) to use the date from
the first trace entry in the dump or trace data set.
– The month and day can be specified in either single or double digits.
– Separate the date from the time with a comma.
– The time can be GMT, by default or specified in a GMT parameter, or
local, if specified in a LOCAL parameter.
– Hours, minutes, and seconds can be specified in single or double digits.
– The time can be truncated anywhere on the right.
– The time can be left off completely, in which case, it will default to
00:00:00.000000 (midnight).
Some examples of valid date formats are:

Chapter 5. IPCS subcommands 111

CTRACE subcommand

*
m/dd/yy
mm/d/yy
m/d/yy
mm/dd/yy
Some examples of valid time formats are:
hh.mm.ss.dddddd
hh.mm.ss.dd
hh.mm.ss
h.m.s
hh.mm
hh
STOP(mm/dd/yy,hh.mm.ss.ddddddd)
Specifies the ending date and time for the trace entries to be formatted.
When you do not specify STOP, IPCS stops formatting after the last trace
entry. For guidelines on how to specify the time and date, see the START
parameter.
EXCEPTION
Requests that qualifying exceptional trace entries be formatted.

Note: Not all components support EXCEPTION processing.

LIMIT(nnnnnnnnn)
Limits the number of trace entries that CTRACE will process. The specified
number (nnnnnnnn) can range from 1 to 999,999,999.
ENTIDLIST(entidlist)
Specifies a list of format entry identifiers to be used as filters for a trace.
Specify the list of entry identifiers using standard TSO/E notation. For
example:
ENTIDLIST(X’00800020’,3,X’12345678’:X’22000000’)

Note: To obtain a list of allowable entry identifiers for a component, enter

CTRACE TALLY LIMIT(1).
USEREXIT(exitname)
Specifies an optional user exit routine that gets control:
– When CTRACE begins to process each trace entry
– After CTRACE processes the last trace entry
This exit routine can select, gather, and format entries. See z/OS MVS IPCS
Customization for more information about user exits.
OPTIONS((component routine parms))
Identifies parameters to pass to the component-owned CTRACE filter
analysis routine or CTRACE buffer-find exit routine. These options are
shown in the heading of the report. To determine which parameters the
routine accepts, see z/OS MVS Diagnosis: Tools and Service Aids or the related
product documentation.
v Address space selection parameters
Use these parameters to obtain data from specific address spaces, which you
specify by their address space identifiers (ASIDs). If you omit these parameters,
the default is ALL. For more information, see the select ASID service in z/OS
MVS IPCS Customization.

Note:

112 z/OS MVS IPCS Commands

 CTRACE subcommand

1. If both ASIDLIST and JOBNAME or JOBLIST parameters are in effect, then a

match for either allows the trace entry to be processed.
2. Not all components support ASIDLIST processing.
3. Not all components support JOBNAME or JOBLIST processing.
ALL
Specifies processing of the applicable trace entries for all address spaces in
the dump.
CURRENT
Specifies processing of the trace entries for each address space that is active
when the dump is generated.
ERROR
Specifies formatting of trace entries for any address space with an error
indicator or containing a task with an error indicator.
TCBERROR
Specifies formatting of trace entries for any address space containing a task
with an error indicator. Entries for address spaces with an error indicator are
not formatted.
ASIDLIST(asidlist)
Specifies the list of ASIDs for which you want to process trace entries. The
asidlist can be a single ASID, a range of ASIDs, or a list of noncontiguous
ASIDs. When you specify a range, separate the first and last ASIDs in the
range with a colon. When you specify a list, separate the list members with
commas.
The ASID can be 1 through 65535. An ASID can be expressed in the notation
X'nnn', F'nnn', or B'nnn'. An unqualified number is assumed to be fixed.
JOBNAME(joblist) or JOBLIST(joblist)
Specifies the list of job names whose associated address spaces are to be
processed for trace entries. Use commas or spaces to separate the job names
in the list; do not enclose job names in apostrophes; and do not specify a
range of job names.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the CTRACE subcommand.
v Example 1: Request a list of traces defined in a dump.
– Action
COMMAND ===> ctrace query
– Result
CTRACE produces the following output. The report shows the complete
name of all traces defined in a dump, organized by component names. In this
example, COMP1 is a HEAD level component name for a multiple trace
component. Five traces are defined under COMP1.

Chapter 5. IPCS subcommands 113

CTRACE subcommand

COMPONENT TRACE QUERY SUMMARY

COMPONENT SUB NAME

0001 COMP1 ASID(0010).FUNC2.SVC2

0002 COMP1 ASID(0020).FUNC1.SVC3
0003 COMP1 ASID(0200).FUNC2.SVC3
0004 COMP1 ASID(0200).FUNC1.SVC3
0005 COMP1 ASID(0012).FUNC1.SVC1
0006 COMP2 FUNCA
0007 COMP2 FUNCB
0008 COMP3
0009 COMP4
.
.
.

v Example 2: Produce a QUERY report for the COMP1 multiple-trace component

trace in Example 1.
– Action
COMMAND ===> ctrace query(COMP1)
– Result
CTRACE produces the following output. The report is similar to the general
query report, listing only the traces from the COMP1 component name.

COMPONENT TRACE QUERY SUMMARY

COMPONENT SUB NAME

0001 COMP1 ASID(0010).FUNC2.SVC2

0002 COMP1 ASID(0020).FUNC1.SVC3
0003 COMP1 ASID(0200).FUNC2.SVC3
0004 COMP1 ASID(0200).FUNC1.SVC3
0005 COMP1 ASID(0012).FUNC1.SVC1

v Example 3: Produce a QUERY report for the COMP1.ASID(0200) HEAD level.

– Action
COMMAND ===> ctrace query(COMP1) sub((ASID(0200)))
– Result
CTRACE produces the following output.

COMPONENT TRACE QUERY SUMMARY

COMPONENT SUB NAME

0001 COMP1 ASID(0200).FUNC2.SVC3

0002 COMP1 ASID(0200).FUNC1.SVC3

v Example 4: Produce a QUERY report for the COMP1.ASID(0200).FUNC2.SVC3

trace.
– Action
COMMAND ===> ctrace query(COMP1) sub((ASID(0200).func2.svc3))
– Result
CTRACE produces the following output.

114 z/OS MVS IPCS Commands

 CTRACE subcommand

COMPONENT TRACE QUERY SUMMARY

COMP(COMP1) SUBNAME((ASID(0200).FUNC2.SVC.))

START = 01/05/90 14:37:48.963576 GMT

STOP = 01/05/90 14:39:21.354861 GMT

v Example 5: Produce a QUERY FULL report for the

COMP1.ASID(0200).FUNC2.SVC3 trace.
– Action
COMMAND ===> ctrace query(COMP1) sub((ASID(0200).func2.svc3)) full
– Result
CTRACE produces the following output.

COMPONENT TRACE QUERY SUMMARY

COMP(COMP1) SUBNAME((ASID(0200).FUNC2.SVC.))

START = 01/05/90 14:37:48.963576 GMT

STOP = 01/05/90 14:39:21.354861 GMT

OPTIONS: COMASID,DMPREC,BUFF=(7,50)

v Example 6: Produce a SHORT form report for RSM trace entries.

– Action
COMMAND ===> ctrace comp(sysrsm) lim(10)
– Result
CTRACE produces the following output.

COMPONENT TRACE SHORT FORMAT

COMP(SYSRSM)
**** 01/05/90

MNEMONIC ENTRY ID TIME STAMP DESCRIPTION

-------- -------- --------------- -----------

RSGSNG 00000006 14:37:48.926973 Get Single Frame

RSEPAG 00000008 14:37:48.927078 Enqueue Pageable Frame
XEPEXIT 00000002 14:37:48.927177 External Entry Point Exit
XEPENTRY 00000001 14:37:48.927734 External Entry Point Entry
RSGSNG 00000006 14:37:48.927853 Get Single Frame
RSEPAG 00000008 14:37:48.927953 Enqueue Pageable Frame
XEPEXIT 00000002 14:37:48.928052 External Entry Point Exit
XEPENTRY 00000001 14:37:48.928554 External Entry Point Entry
RSGSNG 00000006 14:37:48.928668 Get Single Frame
RSEPAG 00000008 14:37:48.928772 Enqueue Pageable Frame

Figure 18. Example output CTRACE COMP command

v Example 7: Produce a SUMMARY form report for RSM trace entries.

– Action
COMMAND ===> ctrace comp(sysrsm) lim(10) summary
– Result
CTRACE produces the following output.

Chapter 5. IPCS subcommands 115

CTRACE subcommand

COMPONENT TRACE SUMMARY FORMAT

COMP(SYSRSM)
**** 01/05/90

MNEMONIC ENTRY ID TIME STAMP DESCRIPTION

-------- -------- --------------- -----------

RSGSNG 00000006 14:37:48.926973 Get Single Frame

FUNC1... VSMGTMN VSM Getmain Service
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 88084001 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 88084000
RSEPAG 00000008 14:37:48.927078 Enqueue Pageable Frame
FUNC1... VSMGTMN VSM Getmain Service
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 88004001 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 88004000
XEPEXIT 00000002 14:37:48.927177 External Entry Point Exit
FUNC1... VSMGTMN VSM Getmain Service
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 80000001 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 80000000
XEPENTRY 00000001 14:37:48.927734 External Entry Point Entry
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 00000003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 00000000
RSGSNG 00000006 14:37:48.927853 Get Single Frame
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 08084003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 08084000
RSEPAG 00000008 14:37:48.927953 Enqueue Pageable Frame
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 08004003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 08004000
XEPEXIT 00000002 14:37:48.928052 External Entry Point Exit
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 00000003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 00000000
XEPENTRY 00000001 14:37:48.928554 External Entry Point Entry
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 00000003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 00000000
RSGSNG 00000006 14:37:48.928668 Get Single Frame
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 08084003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 08084000
RSEPAG 00000008 14:37:48.928772 Enqueue Pageable Frame
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 08004003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 08004000

Figure 19. Example output CTRACE COMP command

v Example 8: Produce a FULL form report for RSM trace entries.

– Action
COMMAND ===> ctrace comp(sysrsm) lim(10) full
– Result
CTRACE produces the following output.
COMPONENT TRACE FULL FORMAT
COMP(SYSRSM)
**** 01/05/90

MNEMONIC ENTRY ID TIME STAMP DESCRIPTION

-------- -------- --------------- -----------

RSGSNG 00000006 14:37:48.926973 Get Single Frame

FUNC1... VSMGTMN VSM Getmain Service
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 88084001 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 88084000
KEY..... 0036 ADDR.... 01B32DC0 ALET.... 00000000
19001200
KEY..... 0001 ADDR.... 012A6000 ALET.... 00000000
012A26A0 0125FBEC FFC00000 03000000 00000000 7FFE4000 01B77F00 00000000

116 z/OS MVS IPCS Commands

 CTRACE subcommand

RSEPAG 00000008 14:37:48.927078 Enqueue Pageable Frame

FUNC1... VSMGTMN VSM Getmain Service
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 88004001 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 88004000
KEY..... 0036 ADDR.... 01B32DC0 ALET.... 00000000
1900
KEY..... 0001 ADDR.... 012A6000 ALET.... 00000000
01A12AAC 0129A7E0 81C00000 03000000 0000000A 00989000 01B77F00 00000000
XEPEXIT 00000002 14:37:48.927177 External Entry Point Exit
FUNC1... VSMGTMN VSM Getmain Service
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 80000001 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 80000000
KEY..... 0036 ADDR.... 01B32DC0 ALET.... 00000000
1900
KEY..... 0016 ADDR.... 00000000 ALET.... 00000000
XEPENTRY 00000001 14:37:48.927734 External Entry Point Entry
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 00000003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 00000000
KEY..... 0036 ADDR.... 01B2FDC0 ALET.... 00000000
0400
KEY..... 002F ADDR.... 0098A000 ALET.... 00000000
KEY..... 0032 ADDR.... 00F2B088 ALET.... 00000000
070C2000 81ED81AE
RSEPAG 00000008 14:37:48.927953 Enqueue Pageable Frame
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 08004003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 08004000
KEY..... 0036 ADDR.... 01B2FDC0 ALET.... 00000000
0400
KEY..... 0001 ADDR.... 012A26A0 ALET.... 00000000
01A12AAC 012A6000 81C00000 03000000 0000000A 0098A000 01B14E80 00000000
XEPEXIT 00000002 14:37:48.928052 External Entry Point Exit
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 00000003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 00000000
KEY..... 0036 ADDR.... 01B2FDC0 ALET.... 00000000
0400
KEY..... 0016 ADDR.... 00000004 ALET.... 00000000
KEY..... 0017 ADDR.... 04000E00 ALET.... 00000000
KEY..... 0027 ADDR.... 7FF14228 ALET.... 00000000
KEY..... 0002 ADDR.... 012A26A0 ALET.... 00000000
XEPENTRY 00000001 14:37:48.928554 External Entry Point Entry
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 00000003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 00000000
KEY..... 0036 ADDR.... 01B2FDC0 ALET.... 00000000
0400
KEY..... 002F ADDR.... 0098B000 ALET.... 00000000
KEY..... 0032 ADDR.... 00F2B088 ALET.... 00000000
070C2000 8243D124
RSGSNG 00000006 14:37:48.928668 Get Single Frame
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 08084003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 08084000
KEY..... 0036 ADDR.... 01B2FDC0 ALET.... 00000000
04001200
KEY..... 0001 ADDR.... 0129E7E0 ALET.... 00000000
01292A80 0125FBEC FFC00000 03000000 00000000 02F1C000 01B77700 00000000
RSEPAG 00000008 14:37:48.928772 Enqueue Pageable Frame
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... CONSOLE ASID1... 000A PLOCKS.. 08004003 CPU..... 0001
JOBN2... CONSOLE ASID2... 000A RLOCKS.. 08004000
KEY..... 0036 ADDR.... 01B2FDC0 ALET.... 00000000
0400
KEY..... 0001 ADDR.... 0129E7E0 ALET.... 00000000
01A12AAC 012A26A0 81C00000 03000000 0000000A 0098B000 01B77700 00000000
v Example 9: Produce a TALLY form report.
– Action
COMMAND ===> ctrace tally comp(sysrsm) lim(22)

Chapter 5. IPCS subcommands 117

CTRACE subcommand

– Result
CTRACE produces the output shown in Figure 20.

Note: The trace record with mnemonic TRACEB has an average interval
greater than or equal to 1000 seconds. IPCS supplies the message ] 16 min.
for all trace entries with average intervals greater than or equal to 1000
seconds.

COMPONENT TRACE TALLY REPORT

COMP(SYSRSM)
TRACE ENTRY COUNTS AND AVERAGE INTERVALS (IN MICROSECONDS)

FMTID COUNT INTERVAL MNEMONIC DESCRIBE

-------- ----- ---------- -------- ----------------------------
00000001 4 855 XEPENTRY External Entry Point Entry
00000002 4 944 XEPEXIT External Entry Point Exit
00000003 0 FIX Page Being Fixed
00000004 0 FREE Page Being Freed
00000005 0 RSGDBL Get Double Frame
00000006 3 847 RSGSNG Get Single Frame
00000007 0 RSEFIX Enqueue Fixed Frame
00000008 3 847 RSEPAG Enqueue Pageable Frame
00000009 0 RSESQA Enqueue SQA Frame
0000000A 0 RSESBUF Enqueue Storage Buffer Frame
0000000B 0 RSEDEFER Enqueue Deferred Frame
0000000C 0 RSEVRW Enqueue V=R Waiting Frame
0000000D 0 RSDFIX Dequeue Fixed Frame
0000000E 3 170 RSDPAG Dequeue Pageable Frame
0000000F 0 RSDSQA Dequeue SQA Frame
00000010 0 RSDSBUF Dequeue Storage Buffer Frame
00000011 0 RSDDEFER Dequeue Deferred Frame
00000012 0 RSDVRW Dequeue V=R Waiting Frame
00000013 0 RSFDBL Free Double Frame
00000014 3 162 RSFSNG Free Single Frame
00000015 0 ESGET Get Expanded Storage
00000016 0 ESENQ Enqueue Expanded Storage
00000017 0 ESDEQ Dequeue Expanded Storage
00000018 0 ESFREE Free Expanded Storage
00000019 0 PAGER2A Page Request Real to Auxiliary
0000001A 0 PAGER2P Page Request Real to Permanent
0000001B 0 PAGER2E Page Request Real to Expanded
0000001C 0 PAGER2R Page Request Real to Real
0000001D 0 PAGEA2R Page Request Auxiliary to Real
0000001E 0 PAGEP2R Page Request Permanent to Real
0000001F 0 PAGEE2R Page Request Expanded to Real
00000020 0 PAGEREL Page Request Related
00000021 0 PAGEDEF Page Request Deferred
00000022 0 FUNCREQ Function Request
00000023 2 ] 16 min. TRACEB Trace Buffer

Total trace entries: 22

Figure 20. Example output CTRACE TALLY command

DOCPU subcommand — obtain stand-alone dump data for multiple

processors
Use the DOCPU subcommand to gather stand-alone dump data for tasks that need
to be repeated for each of the specified processors. For example, to display
contents of a processor-related control block for a group of processors. With this
command, you can obtain processor-related diagnostic data from a stand-alone
dump with one command rather than repeating the command for each processor.
v Syntax for DOCPU:

118 z/OS MVS IPCS Commands

 DOCPU subcommand

{ DOCPU }

-------- Data Selection Parameters -------------------------

[ ( CPU ( cpu-address-range-list ) ) |
CPUTYPE ( (ZAAP|ZA) | (ZIIP|ZI) | (STANDARD | CP | S) ) |
CPUMASK ( cpumask ) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Data Selection Parameters

Use these parameters to limit the scope of the data in the report. If you omit
these parameters (CPU, CPUTYPE, and CPUMASK), all processors are included
as the default.
CPU (cpu-address-range-list)
Specifies the processors (CPU) that are selected for to run the specified IPCS
subcommand. The cpu-address-range-list is a processor number, a range of
processor numbers, or a combination of both. You can specify the processor
number in either decimal or hexadecimal format (X'...'). You can use a colon
to indicate a range of processors, and use a space or comma as a delimiter.
For example:
CPU(0)
CPU(5:10)
CPU(0 5:10)
CPU(0,3,5:10)
CPU(X’A’)

Note: You can combine CPU, CPUTYPE, and CPUMASK as a union of sets.
CPUTYPE ((ZAAP|ZA) | (ZIIP|ZI) | (STANDARD|CP|S))
– Specifying ZAAP or ZA selects all ZAAP processors in the configuration.
– Specifying ZIIP or ZI selects all ZIIP processors in the configuration.
– Specifying STANDARD or CP or S selects all standard processors in the
configuration.
You can combine the ZAAP, ZIIP, and STANDARD options in any order to
select a combination of CPU types. For example, CPUTYPE(ZAAP
STANDARD). You can use spaces or commas as a delimiter.
CPUMASK(CPU hexadecimal mask)
Specifies processors in a string of hexadecimal characters. Each hexadecimal
character identifies four processors. The maximum number of processors
supported by z/OS defines the maximum length of this hexadecimal string.
Currently, the maximum number of processors supported by z/OS is 256, so
the maximum length of the hexadecimal mask is 64. The leftmost bit
designates the lower processor address starting from zero. For example:
– CPUMASK(FFF)
– CPUMASK(F0F0)
– CPUMASK(80) CPU

Chapter 5. IPCS subcommands 119

DOCPU subcommand

You can combine CPUTYPE and CPUMASK as a union of sets. If all of the
processors are omitted, the default is to include all processors.
EXEC((ipcs subcommand))
Runs the IPCS subcommand for each CPU you specify by appending
CPU(xxx) to the IPCS subcommand. The DOCPU subcommand generates a
return code that consists of its own return code plus the return code from
the IPCS subcommand designated on the EXEC parameter.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the DOCPU subcommand.
v Examples
– To display four bytes of storage at 414 in every PSA, enter the following
command:
DOCPU EXEC((L 414 LEN(4)))
– To format the PSA of processor 0,1,2,3,8,9,10,11, enter the following
commands:
DOCPU CPUMASK(F0F0) EXEC((CBF 0 STR(PSA)))

You can delete symbols when you want to free space in the dump directory.

DIVDATA subcommand — analyze data-in-virtual data

Use the DIVDATA subcommand to request:
v Validation, formatting, and display of the data-in-virtual control blocks
v Formatting and display of the data-in-virtual trace table

DIVDATA produces different diagnostic reports depending on the report type

parameters and the address space selection parameters specified. By specifying one
or more report type and address space selection parameters, you can selectively
display the information you want to see.
v Report Type Parameters
– DETAIL displays all data-in-virtual control blocks.
– SUMMARY displays a summary of the data-in-virtual control blocks.
– EXCEPTION displays diagnostic error messages for not valid data-in-virtual
control blocks.
– TRACE displays the data-in-virtual trace table by the specified address space
selection parameter(s).
– FULLTRACE displays the entire data-in-virtual trace table.
v Address Space Selection Parameters
– ALL processes all address spaces.
– CURRENT processes active address spaces of the dump.
– ERROR processes any address space with an error indicator or containing a
task with an error indicator.
– TCBERROR processes any address space containing a task with an error
indicator.
– ASIDLIST processes address spaces associated with ASID(s).
– JOBLIST or JOBNAME processes address spaces associated with job names.

120 z/OS MVS IPCS Commands

 DIVDATA subcommand

Several address space selection parameters can be specified and an address

space might meet more than one selection criterion. The selection criterion (or
criteria) that is met for each address space appears in the output. No address
space is processed more than once.
v Syntax

DIVDATA

-------- Report Type Parameters ----------------------------

[ DETAIL ]
[ SUMMARY ]
[ EXCEPTION ]
[ TRACE {OLDEST(n) } ]
[ FULLTRACE {NEWEST(n) } ]

-------- Address Space Selection Parameters ----------------

[ ALL ]
[ CURRENT ]
[ ERROR ]
[ TCBERROR ]
[ ASIDLIST(asidlist) ]
[ JOBLIST(joblist)|JOBNAME(joblist) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report Type Parameters

Use these parameters to select the type of report. If you omit a report type
parameter, the default is EXCEPTION.
DETAIL
Specifies the report type that:
– Validates and formats all of the data-in-virtual control blocks
– Produces a data-in-virtual trace table statistics report, which contains
information about the trace table and trace table entries
SUMMARY
Specifies the report type that validates certain control blocks and produces a
summary table showing the data-in-virtual object ranges that are mapped
and the virtual storage ranges they are mapped into.
If the DETAIL parameter is not also specified, SUMMARY also produces a
data-in-virtual trace table statistics report, which contains information about
the trace table and trace table entries. Additionally, IPCS validates, formats,
and displays certain control blocks.
EXCEPTION
Specifies the report type that validates all of data-in-virtual control blocks

Chapter 5. IPCS subcommands 121

DIVDATA subcommand

and displays diagnostic error messages for incorrect control blocks. A

condensed version of the data-in-virtual trace table statistics report is also
produced.
TRACE
FULLTRACE
Specifies the report type for formatting and displaying the data-in-virtual
trace table entries.
TRACE specifies formatting and displaying of trace entries based on the
address space selection parameters.
FULLTRACE specifies formatting and displaying the entire data-in-virtual
trace table entries regardless of any specified address space selection
parameter.
The trace table entries are processed based on the specified order
parameters, OLDEST or NEWEST.
OLDEST(n)
NEWEST(n)
Specifies the order in which the trace table entries are to be formatted and
displayed.
OLDEST specifies processing from the oldest entry toward the newest.
NEWEST specifies processing from the newest entry toward the oldest.
The n indicates the number of trace entries to be processed. The n can range
from 1 through 231 and can be specified in decimal, hexadecimal (X'xxx...'),
or binary (B'bbb...'). If n exceeds the total number of trace table entries or is
omitted, the entire trace table is formatted and displayed.
If you omit both OLDEST and NEWEST, the default is OLDEST.
v Address Space Selection Parameters
Use these parameters to obtain data from particular address spaces, which you
specify by the address spaces identifier (ASID). If you omit these parameters, the
default is CURRENT. For more information, see the select ASID service in z/OS
MVS IPCS Customization.
ALL
Specifies processing of data-in-virtual control blocks for all address spaces in
the system at the time the dump is generated.
CURRENT
Specifies processing of data-in-virtual control blocks for each address space
that is active (for example, dispatched on some central processor) when the
dump is generated.
ERROR
Specifies processing of data-in-virtual control blocks for any address space
with an MVS error indicator or containing a task with an error indicator.
TCBERROR
Specifies processing of data-in-virtual control blocks for any address space
containing a task with an error indicator. Blocks for address spaces with an
error indicator are not processed.
ASIDLIST(asidlist)
Specifies a list of ASIDs for the address spaces to be in the report.

122 z/OS MVS IPCS Commands

 DIVDATA subcommand

The asidlist can be a single ASID, a range of ASIDs, or a list of

noncontiguous ASIDs. When you specify a range, separate the first and last
ASIDs in the range with a colon. When you specify a list, separate the list
members with commas.
The ASID can be 1 through 65535. An ASID can be expressed using the
notation X'nnn', F‘nnn’, or B'nnn'. An unqualified number is assumed to be
fixed.
This subcommand does not process summary dump records (ASID X'FFFA').
JOBLIST(joblist) or JOBNAME(joblist)
Specifies a list of job names whose associated address spaces are to be in the
report. Use commas to separate the job names in the list; do not enclose job
names in apostrophes; and do not specify a range of job names.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the DIVDATA subcommand.
v Example
See the data-in-virtual component in z/OS MVS Diagnosis: Reference for examples
of the DIVDATA subcommand output.

DLFDATA subcommand — format data lookaside facility data

Use the DLFDATA subcommand to generate diagnostic reports about activity by
the data lookaside facility (DLF). Use the report type parameters to choose the
information you want to see.

DLFDATA

-------- Report Type Parameters -----------------------------

{ CLASS(classname)[OBJECT(objname)] }
{ EXCEPTION }
{ STATS(classname) }
{ STORAGE(classname) }
{ SUMMARY }
{ USER(classname) }

-------- Address Selection Parameters ----------------------

[ ASIDLIST(list) ]
[ CURRENT ]
[ ERROR ]
[ TCBERROR ]
[ JOBLIST(list)|JOBNAME(list) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

Chapter 5. IPCS subcommands 123

DLFDATA subcommand

v Report Type Parameters

Use these parameters to select the type of report. If you omit a report type
parameter, the default is SUMMARY.

Note: In the parameter values, classname is 1 through 7 characters, which are

alphanumeric or the following:
$ (X’5B’)
# (X’7B’)
@ (X’7C’)
CLASS(classname)
Produces a report with information pertaining to the DLF class specified by
classname.
OBJECT(objname)
Is an optional CLASS report parameter. Specify OBJECT to produce
information about an object stored in DLF.
EXCEPTION
Produces messages related to any inconsistencies IPCS finds in the DLF data.
STATS(classname)
Produces a report with statistics about DLF activity. If you specify classname,
only statistics for the specified class are produced.
STORAGE
Produces a report with information about the storage management of DLF
data spaces. If you specify a classname, only storage management
information for the specified class is produced.
SUMMARY
Produces a report with overall information for each of the classes known to
DLF. This is the default report.
USER(classname)
Produces a report with information relating to an address space that was
using DLF facilities. If you specify classname, only information related to the
specified class is produced.
v Address Space Selection Parameters
Use these parameters to obtain data from particular address spaces, which you
specify by their address space identifiers (ASIDs). If you omit these parameters,
the default is CURRENT. For more information, see the select ASID service in
z/OS MVS IPCS Customization.
ASIDLIST(asidlist)
Specifies a list of ASIDs for the address spaces to be included in the report.
The asidlist can be a single ASID or a list of noncontiguous ASIDs. When
you specify a list, separate the list members with commas.
CURRENT
Specifies that address spaces considered to be current by the select ASID exit
service are to be included in the report.
ERROR
Specifies processing for any address space with an error indicator or
containing a task with an error indicator.
TCBERROR
Specifies processing for any address space containing a task with an error
indicator. Entries for address spaces with an error indicator are not
formatted.

124 z/OS MVS IPCS Commands

 DLFDATA subcommand

JOBLIST(list) or JOBNAME(list)
Specifies a list of job names whose associated address spaces are to be
included in the report. Use commas to separate the job names in the list; do
not enclose job names in apostrophes; and do not specify a range of job
names.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the DLFDATA subcommand.
v Example
See the virtual lookaside component in z/OS MVS Diagnosis: Reference for
examples of the DLFDATA subcommand output.

DROPDUMP subcommand — delete source description data

Use the DROPDUMP subcommand to delete a source description or records in a
source description from a dump directory. The description is for an unformatted
source that IPCS can format, for example, an SVC dump, a stand-alone dump, an
SYSMDUMP dump, a trace data set, a data set, or active storage. The directory is
allocated with ddname IPCSDDIR and is your current dump directory. The current
dump directory is your user dump directory or, for users with write access
authority, might be the sysplex dump directory.

Some reasons for using DROPDUMP are to:

v Delete the description for a source that is no longer needed
v Delete the description for a partially initialized dump
v Delete source descriptions to free space in the directory
v Delete translation records from one or more source descriptions
v Related subcommands
– ADDDUMP
– LISTDUMP
v Syntax

{DROPDUMP } [RECORDS {( ALL | ANALYSIS | TRANSLATION } ]

{DROPD
[ SUMMARY | NOSUMMARY ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE|MAIN|STORAGE ]
[ DSNAME(dslist)|DATASET(dslist) ]
[ FILE(ddlist)|DDNAME(ddlist) ]
[ TEST | NOTEST ]

v Parameters
RECORDS(ALL)
RECORDS(ANALYSIS)
RECORDS(TRANSLATION)
Designates the type of records to be deleted from a source description.
RECORDS(ALL) directs IPCS to delete all of the records in a source
description.
RECORDS(ANALYSIS) directs IPCS to delete only analysis records.

Chapter 5. IPCS subcommands 125

DROPDUMP subcommand

RECORDS(TRANSLATION) directs IPCS to delete only records generated by

an IPCS translation process. Translation records are generated by, for
example, the simulation of System/390® prefixing or dynamic address
translation.
The following are ways to use RECORDS(TRANSLATION):
– When IPCS first processes storage for a central processor in a stand-alone
dump, IPCS locates the prefixed storage area (PSA) for the processor.
IPCS constructs a central storage map using the absolute storage record
map for the dump.
If IPCS used an incorrect PSA, you may correct the definition of the
PSAnn symbol in the symbol table. Then, you can run DROPDUMP
RECORDS(TRANSLATION) to delete the incorrect translation records
from your user dump directory. When IPCS next processes the storage in
the dump, IPCS uses the corrected symbol to build a correct record map.
– When IPCS first processes an address space in a stand-alone dump, IPCS
locates the segment table for the address space. IPCS constructs a virtual
storage record map for the referenced page using the absolute storage
record map or the central storage map for the dump.
If IPCS used an incorrect segment table, you may correct the definition of
the SGTnnnnn symbol in the symbol table. Then, you can run
DROPDUMP RECORDS(TRANSLATION) to delete the incorrect
translation records from your user dump directory. When IPCS next
processes the address space in the dump, IPCS uses the corrected symbol
to build a correct record map.
– When you first enter an ANALYZE or STATUS CPU CONTENTION
subcommand, IPCS places the following contention records in the source
description:
- The contention queue (CQ)
- The contention resource (CR)
- Program history (PH)
These records are incorrect if the symbols for the control blocks are
incorrect or if the ANALYZE exit routines specified by parmlib members
embedded in the BLSCECT parmlib member have been redefined. If you
determine that the contention records are incorrect, enter DROPDUMP
RECORDS(TRANSLATION) to delete all contention records. Then you
can run ANALYZE or STATUS CPU CONTENTION to have IPCS gather
the contention records again.
DROPDUMP RECORDS(TRANSLATION) does not edit the symbol table or
the storage map. For editing, use DROPMAP, DROPSYM, or EQUATE
subcommands.
SUMMARY or NOSUMMARY
SUMMARY indicates that a processing summary (a final total line) is to be
produced.
NOSUMMARY specifies that a processing summary is to be suppressed. The
NOSUMMARY parameter is useful to turn off summary messages when the
subcommand is invoked within a CLIST or a REXX exec.
ACTIVE or MAIN or STORAGE
DSNAME(dslist) or DATASET(dslist)
FILE(ddlist) or DDNAME(ddlist)
Specifies storage or one or more data sets. IPCS is to delete the source
description or records in the source description for the storage or data sets.

126 z/OS MVS IPCS Commands

 DROPDUMP subcommand

If one of these parameters is not specified, IPCS deletes the source

description or records from the source description for your current source
data set.
ACTIVE, MAIN, or STORAGE specifies that the source description is for the
active storage that was accessed.
DSNAME or DATASET specifies that the source description is for the
cataloged data set or sets named in dslist. When specifying more than one
data set name, separate the names with commas or blanks.
FILE or DDNAME specifies that the source description is for a data set or
sets with the ddname or ddnames in ddlist. When specifying more than one
ddname, separate the names with commas or blanks.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the DROPDUMP subcommand.
v Example 1: Delete a source description for a specific dump.
– Action
COMMAND ===> dropdump dsname(’sys1.dump.d930428.t110113.system1.s00000’)
– Result
IPCS deletes from your user dump directory the source description for the
dump in the data set named sys1.dump.d930428.t110113.system1.s00000.
IPCS issues the following summary output.
BLS18206I All records for 1 dump dropped
v Example 2: Delete records generated by translation processes,
– Action
COMMAND ===> dropdump records(translation)
– Result
The contention information from a STATUS CPU CONTENTION
subcommand for the current dump data set appears to be incorrect. IPCS
deletes this information, displays the following output, and permits the
STATUS subcommand to be entered again to obtain new contention data.
BLS18206I Translation records for 1 dump dropped

DROPMAP subcommand — delete storage map records

Use the DROPMAP subcommand to delete records from the storage map in a
source description for a dump. The source description is in the dump directory
allocated with ddname IPCSDDIR and is your current dump directory. The current
dump directory is your user dump directory or, for users with write access
authority, might be the sysplex dump directory.
v Related subcommands
– LISTMAP
– SCAN
v Syntax

Chapter 5. IPCS subcommands 127

DROPMAP subcommand

{DROPMAP } [RANGE (address:address)] [data-descr]

{DROPM }
[ SUMMARY | NOSUMMARY ]

-------- SETDEF-Defined Parameter --------------------------

Note: You can override the following SETDEF parameter.
See “SETDEF subcommand — set defaults” on page 262.
[ TEST | NOTEST ]

v Parameters
RANGE(address:address)
Specifies that the range of addresses in the dump for which map records
exist are to be deleted. The range can be specified as an address and a
length or as a range of addresses.
If you omit the range parameter, the subcommand deletes all map record s
for the dump.
If a map record describes an address within the range, the subcommand
deletes the map record.
data-descr
Specifies the data description parameter, which consists of five parts:
– An address (required with the RANGE parameter and when data-descr is
explicitly specified on the subcommand)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.

If you specify address processing parameters (which are optional) but omit
the address (which is required), the subcommand deletes all map records for
the address space.
SUMMARY or NOSUMMARY
SUMMARY indicates that a processing summary (a final total line) is to be
produced.
NOSUMMARY specifies that a processing summary is to be suppressed. The
NOSUMMARY parameter is useful to turn off summary messages when the
subcommand is invoked within a CLIST or a REXX exec.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the DROPMAP subcommand.
v Example 1: Delete all storage map records.
– Action
COMMAND ===> dropmap
– Result
DROPMAP produces the following summary output.
BLS18114I 42 RECORDS ERASED
v Example 2: Delete storage map records within an address range for the same
ASID.

128 z/OS MVS IPCS Commands

 DROPMAP subcommand

– Action
COMMAND ===> dropmap range(005d4980.:005d4c88.) asid(x’000b’)
– Result
DROPMAP produces the following summary output.
BLS18114I 7 RECORDS ERASED

DROPSYM subcommand — delete symbols

Use the DROPSYM subcommand to delete symbols from the symbol table in a
source description for a dump. The source description is in the dump directory
allocated with ddname IPCSDDIR and is your current dump directory. The current
dump directory is your user dump directory or, for users with write access
authority, might be the sysplex dump directory.

You can delete symbols when you want to free space in the dump directory.
v Related subcommands
– EQUATE
– LISTSYM
– RENUM
– STACK
v Syntax

{ DROPSYM } { (symbol-list) | * }
{ DROPS }
[ DROP|NOPURGE ]
[ NODROP ]
[ PURGE ]
[ SUMMARY | NOSUMMARY ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ TEST | NOTEST ]

v Parameters
symbol-list or *
Specifies the symbols to be deleted. You can specify one symbol, a range of
symbols, a list of symbols, a combination of these, or, with an asterisk (*), all
symbols in the symbol table. Enclose more than one symbol or range of
symbols in parentheses. The list can contain up to 31 symbols, ranges, or
both.
The symbols follow the IPCS naming conventions for symbols. See
Appendix A, “IPCS symbols,” on page 445.
If you specify a single symbol or a list of symbols, the subcommand deletes
only the specified symbol or symbols.
If you specify a range of symbols, the symbol name must follow the naming
conventions for symbols. See Appendix A, “IPCS symbols,” on page 445.
IPCS deletes all symbols whose names begin with the first character string

Chapter 5. IPCS subcommands 129

DROPSYM subcommand

through all symbols whose names begin with the second character string. A
range of symbols is inclusive: the subcommand deletes all the symbols in the
range and at both ends of the range.
DROP or NODROP
NOPURGE or PURGE
Defines which symbols are eligible for deletion. The default is NOPURGE.
DROP and NOPURGE specify that only symbols with the DROP attribute
are to be deleted.
NODROP specifies that only symbols with the NODROP attribute are to be
deleted.
PURGE specifies that the NODROP attribute is ignored and all specified
symbols are deleted.
SUMMARY or NOSUMMARY
SUMMARY indicates that a processing summary (a final total line) is to be
produced.
NOSUMMARY specifies that a processing summary is to be suppressed. The
NOSUMMARY parameter is useful to turn off summary messages when the
subcommand is invoked within a CLIST or a REXX exec.
ACTIVE or MAIN or STORAGE
DSNAME(dsname) or DATASET(dsname)
FILE(ddname) or DDNAME(ddname)
Specify the source of the source description containing the symbol. If one of
these parameters are not specified, the source is your current source.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the DROPSYM subcommand.
v Example 1: Delete a range of ASCB symbols.
– Action
COMMAND ===> dropsym (ascb00001 : ascb00050) nodrop
– Result
DROPSYM deletes the ASCB symbols for ASID 1 through 50.
v Example 2: Delete all symbols in the symbol table.
– Action
COMMAND ===> dropsym * purge
– Result
DROPSYM deletes every entry in the symbol table, including X, for the
current dump. If you omit the PURGE parameter, this example deletes all
symbols except those with the NODROP attribute.

END subcommand — end an IPCS session

Use the END subcommand to end:
v An IPCS session.
Any default values specified with the SETDEF subcommand are canceled. The
subcommand closes and deallocates the data set directory, problem directory,
and any dumps allocated to the user. The subcommand closes but does not
deallocate your user dump directory and the print output data set.
v A session initiated by entering the IPCS TSO subcommand with no operands.

130 z/OS MVS IPCS Commands

 END subcommand

During a TSO subcommand session, a command such as LIST causes the TSO/E
command associated with the command to be processed, not the IPCS
subcommand associated with it. When END is entered during a TSO
subcommand session, IPCS resumes its normal interpretation of commands.
v CLIST or REXX exec processing initiated with the EXEC parameter of the
RUNCHAIN subcommand.
v CLIST or REXX exec processing initiated with the IPCS primary command of the
IPCS dialog.
v CLIST or REXX exec processing initiated through option 4 of the IPCS dialog.
v Related subcommands
– IPCS
– SETDEF
v Syntax

END

v Return Codes
When the END subcommand ends an IPCS session, IPCS returns the highest
return code that was issued during the session.

EPTRACE subcommand — using 72-byte save areas

Use the EPTRACE subcommand to generate reports on the control flow between
programs as indicated by 72-byte save areas.
v Related subcommands
“SETDEF subcommand — set defaults” on page 262
v Syntax

EPTRACE

------- Report Selection Parameters ---------------------

[ KEYFIELD | SAVEAREA ]
[ ORDER(RETURN | ENTRY ) ]
[ DATA( TCBCURRENT | symbol ) ]

------- SETDEF-Defined Parameters -----------------------

Note: You can override the following SETDEF parameters

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]

[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(hfspath) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
KEYFIELD or SAVEAREA
Selects the report formatting to be performed for each entry point.
KEYFIELD is the default.

Chapter 5. IPCS subcommands 131

EPTRACE subcommand

Note: The KEYFIELD report of EPTRACE is enhanced in z/OS V1R8 IPCS

to consider additional linkage mechanisms:
– Linkages that employ the linkage stack to save status.
– Linkages that mark the initial word of caller’s save areas to indicate how
status is saved.
ORDER(RETURN) or ORDER(ENTRY)
Selects the order of processing. ORDER(RETURN) causes the GPR 13 current
GPR 13 value to be used to locate the active save area, and displays
information to be displayed for calling programs later. ORDER(RETURN) is
the default because it provides information needed for problem analysis
early in the report. ORDER(ENTRY) causes information about the first entry
point entered to be listed first.
DATA(symbol)
Specifies an IPCS symbol that is associated with one of the structures shown
in Table 8.
Table 8. Structures recognized by EPTRACE
Structure Use by EPTRACE
TCB The first program of interest is the highest one active for the
task.
IRB, SVRB, TIRB The first program of interest is the highest one active for the
RB.
REGSAVE The first program of interest is the one to which this 72-byte
save area was passed. Use of this data type limits EPTRACE
processing to 72-byte save areas. No attempt is made to
identify a related linkage stack.

The default, DATA(TCBCURRENT), is a symbol for which z/OS R5 support

is supplied. An IPCS find routine is supplied that will attempt to determine
whether an obvious current task can be identified within the dump. If it can
be determined, the symbol TCBCURRENT is defined and associated with
that TCB. Otherwise, the symbol is undefined. When the symbol explicitly or
implicitly cannot be defined or that symbol is defined but is not associated
with a supported data type, EPTRACE will generate an error message and
will terminate.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the EPTRACE subcommand.

EQUATE subcommand — create a symbol

The EQUATE subcommand allows you to:
v Create a symbol in the symbol table and to associate an address and storage
attributes with the symbol
v Change the attributes of a symbol that is already defined in the symbol table
v Create storage map entries
v Set X, the current address, to a specific address

The symbol is in a symbol table that is part of a source description. The source
description is in the dump directory allocated with ddname IPCSDDIR and is your
current dump directory. The current dump directory is your user dump directory
or, for users with write access authority, might be the sysplex dump directory.

132 z/OS MVS IPCS Commands

 EQUATE subcommand

On the EQUATE subcommand, specify the name of the symbol followed by any
address and other storage attributes that you want associated with the symbol. If
the specified symbol already exists in the symbol table, the new address and
storage attributes overlay the previous address and storage attributes.

Note: Because the EQUATE subcommand can be used either to create a new
symbol or redefine an existing symbol, it can be used to create a symbol for a
system control block that has failed the validity check during IPCS processing.

See the z/OS MVS IPCS User's Guide for information about maintaining symbol
tables and storage map entries and about creating and validating your own symbol
definitions.
v Related subcommands
– DROPSYM
– LISTSYM
– RENUM
– STACK
v Syntax

{ EQUATE } [ symbol | X ] [ data-descr | X ]

{ EQU }
{ EQ } [ DROP | NODROP ]

-------- SETDEF-Defined Parameter --------------------------

Note: You can override the following SETDEF parameter.
See
“SETDEF subcommand — set defaults” on page 262.
[ TEST | NOTEST ]

v Parameters
symbol or X
Specifies the symbol being defined. The symbol name is 1 through 31
alphanumeric characters; the first character must be a letter or one of the
following characters:
$ (X’5B’)
# (X’7B’)
@ (X’7C’)

If you omit this parameter, the default is X, which is the most recently
accessed address.
data-descr or X
Specifies the address and attributes to be associated with the symbol being
defined through the data description parameter. The data description
parameter consists of five parts:
– An address (required when data-descr is explicitly specified on the
subcommand)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.
Chapter 5. IPCS subcommands 133
EQUATE subcommand

If you omit this parameter, the default is X, which is the most recently
accessed address.
DROP or NODROP
Specifies how the DROPSYM subcommand can delete the symbol.
DROP specifies that the symbol can be deleted from the symbol table by the
DROPSYM subcommand without using the PURGE parameter.
NODROP specifies that the symbol not be deleted from the symbol table by
the DROPSYM subcommand. This can be overridden by the PURGE
parameter on the DROPSYM subcommand.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the EQUATE subcommand.
v Example 1: Define a symbol for a TCB that caused a dump.
– Action
equate failingtcb 51368. length(360) +
x remark(’tcb that caused the dump’)
– Result
This subcommand defines FAILINGTCB at address X'51368'. It is identified as
a TCB, and its size is 360 bytes (decimal). If the TCB is displayed or printed,
it is in hexadecimal format. Because the NODROP parameter is not specified,
this name can be deleted from the symbol table.
v Example 2: Define a symbol table entry at the current address.
– Action
equate jstcb
– Result
This subcommand creates a symbol table entry for JSTCB. By default, the
address and attributes associated with JSTCB are those associated with X,
which is the current address.
v Example 3: Set X to a specific address.
– Action
equate x 522836
– Result
This sets X to address X'522836'.
v Example 4: Define a symbol, then change its attributes.
– Action
equate buffer1 55280. length(80) asid(3) drop
equate buffer1 buffer1 nodrop cpu(2)
– Result
The first EQUATE creates the symbol BUFFER1 and gives it certain attributes.
The second EQUATE changes the DROP attribute to NODROP and specifies a
central processor in the CPU parameter. You can change the attributes of any
symbol in the symbol table whether you created it or whether IPCS
subcommands created it for you.
v Example 5:
– Action
setdef length(x’0F00’)
equate nick 10000. structure(nick) length(x’1000’

NICK is not a recognized structure by IPCS.

134 z/OS MVS IPCS Commands

 EQUATE subcommand

– Result
EQUATE creates a storage map entry at x'10000' but is unable to locate a
formatter for NICK. The entry is created with the SETDEF length of X'0F00'.
A symbol table entry is then created for symbol nick at X'10000' using the
defined length parameter x'1000'.

EVALDEF subcommand — format defaults

Use the EVALDEF subcommand to retrieve SETDEF-defined default values and
format the values in CLIST variables, REXX variables, or ISPF function pool dialog
variables. The default values can be for:
v Local defaults. These values are currently in use for an ISPF screen in the IPCS
dialog, for a batch IPCS session, or for an IPCS interactive line-mode session.
v Global defaults. These values are used to establish the local defaults when IPCS
processing starts in an ISPF screen, a batch IPCS session, or an IPCS interactive
line-mode session.

The default values are part of a source description. The source description is in the
dump directory allocated with ddname IPCSDDIR and is your current dump
directory. The current dump directory is your user dump directory or, for users
with write access authority, might be the sysplex dump directory.

Note: With TSO/E Release 2 installed, you can use this subcommand to update
GLOBAL CLIST variables. See z/OS TSO/E CLISTs for information.
v Related subcommands
– EQUATE
– EVALDUMP
– EVALMAP
– EVALSYM
v Syntax

EVALDEF { LOCAL | GLOBAL }

{ CLIST(var-list) }
{ DIALOG(var-list) }
{ REXX(var-list) }

-------- SETDEF-Defined Parameter --------------------------

Note: You can override the following SETDEF parameter.
See “SETDEF subcommand — set defaults” on page 262.
[ TEST | NOTEST ]

v Parameters
LOCAL or GLOBAL
Identifies the type of default values to be retrieved.
LOCAL requests the default values that are currently used.
GLOBAL requests the default values to be used when local values are not
specified.
CLIST(var-list)
DIALOG(var-list)
REXX(var-list)
Specifies how the default values are to be formatted.

Chapter 5. IPCS subcommands 135

EVALDEF subcommand

CLIST(var-list) designates that the values be formatted into CLIST variables.

DIALOG(var-list) designates that the values be formatted into ISPF function
pool dialog variables.
REXX(var-list) designates that the values be formatted into REXX variables.
The syntax for var-list is as follows:

[ DECIMAL | F ]
[ HEXADECIMAL | X ]
[ CONFIRM(confirm) ]
[ DISPLAY(display) ]
[ FLAG(flag) ]
[ LENGTH(length) ]
[ PRINT(print) ]
[ PROBLEM(problem) ]
[ QUALIFICATION(qualification) ]
[ SOURCE(var-name)|DATASET(var-name)|DSNAME(var-name) ]
[ TERMINAL(terminal) ]
[ TEST(test) ]
[ VERIFY(verify) ]

DECIMAL or F
HEXADECIMAL or X
Specifies the format of the default length.
DECIMAL or F designates that the default length be formatted using
decimal digits.
HEXADECIMAL or X designates that the default length be formatted using
hexadecimal digits.
CONFIRM(confirm)
Places the parameter CONFIRM or NOCONFIRM in the variable confirm.
DISPLAY(display)
Places one of each of the following options of the DISPLAY parameter in the
variable display:
– [NO]MACHINE
– [NO]REMARK
– [NO]REQUEST
– [NO]STORAGE
– [NO]SYMBOL
SOURCE(var-name) or DATASET(var-name) or DSNAME(var-name)
Places the parameter SOURCE, DATASET, or DSNAME and the default
dump source name or the parameter NODSNAME in the variable var-name.
FLAG(flag)
Places one of the following options of the FLAG parameter, in the variable
flag:
– INFORMATIONAL
– WARNING
– ERROR
– SERIOUS
– TERMINATING

136 z/OS MVS IPCS Commands

 EVALDEF subcommand

LENGTH(length)
Formats and places the default data length in the variable length. The length
is in DECIMAL unless HEXADECIMAL is specified.
PRINT(print)
Places the parameter PRINT or NOPRINT in the variable print.
PROBLEM(problem)
Places the PROBLEM parameter and the default problem number or the
parameter NOPROBLEM in the variable problem.
QUALIFICATION(qualification)
Places the default address qualifiers for the default data set in the variable
qualification.
TERMINAL(terminal)
Places the parameter TERMINAL or NOTERMINAL in the variable terminal.
TEST(test)
Places the parameter TEST or NOTEST in the variable test.
VERIFY(verify)
Places the parameter VERIFY or NOVERIFY in the variable verify.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the EVALDEF subcommand.
v Example: The BLSCSETD CLIST formats the current SETDEF-defined defaults
for display on an ISPF data entry panel. It supports option 0 (DEFAULTS) of the
IPCS dialog when TSO/E Release 2 (or a later release of that product) is
installed. The first part of the CLIST uses the EVALDEF subcommand to obtain
the SETDEF-defined defaults as follows. The defaults shown will, by default, be
the local defaults.
EVALDEF CLIST(SOURCE(SRC) CONFIRM(CON) DISPLAY(DSP) +
FLAG(FLG) PRINT(PRI) TERMINAL(TER) VERIFY(VER))
SET CONTROL=FLAG(&FLG) &CON &VER
SET ROUTE=&PRI &TER
IF &LASTCC=8 THEN EXIT
EVALDEF CLIST(QUALIFICATION(QUAL))
See the BLSCSETD member of SYS1.SBLSCLI0 for the complete listing.

EVALDUMP subcommand — format dump attributes

Use the EVALDUMP subcommand to retrieve information from a source
description and format that information in CLIST variables, REXX variables, or
ISPF function pool dialog variables.

The source description is for an unformatted source that IPCS can format, for
example, an SVC dump, a stand-alone dump, an SYSMDUMP dump, a trace data
set, a data set, or active storage. The source description is in a directory allocated
with ddname IPCSDDIR and is your current dump directory. The current dump
directory is your user dump directory or, for users with access authority, might be
the sysplex dump directory.

The source description is for a source that IPCS has initialized or for a source IPCS
accessed during processing of an ADDDUMP subcommand.

Note: With TSO/E Release 2 installed, you can use this subcommand to update
GLOBAL CLIST variables. See z/OS TSO/E CLISTs for additional information.

Chapter 5. IPCS subcommands 137

EVALDUMP subcommand

v Related subcommands
– EQUATE
– EVALDEF
– EVALMAP
– EVALSYM
v Syntax

EVALDUMP [ relational-operator ]

[ CLIST(var-list) ]
[ DIALOG(var-list) ]
[ REXX(var-list) ]
[ INDATASET(dsname) | INFILE(ddname) ]

-------- SETDEF-Defined Parameter --------------------------

Note: You can override the following SETDEF parameter.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ TEST | NOTEST ]

v Parameters
relational-operator
Specifies a symbolic or programming operators to be used with the source to
identify the source description to be retrieved from the dump directory. The
syntax for relational-operator is as follows:
[ < | LT ]
[ <= | LE ]
[ > | GT ]
[ >= | GE ]
[ ¬> | NG ]
[ ¬< | NL ]
[ = | EQ ]

For example, the less than (<|LT) relationship is satisfied by the

highest-collating source name that also collates lower than the source name
specified on the EVALDUMP subcommand.
CLIST(var-list)
DIALOG(var-list)
REXX(var-list)
Specifies how the default values are to be formatted.
CLIST(var-list) designates that the information be formatted into CLIST
variables.
DIALOG(var-list) designates that the information be formatted into ISPF
function pool dialog variables.
REXX(var-list) designates that the information be formatted into REXX
variables.
INDATASET(dsname)
INDSNAME(dsname)
Requests allocation of directory dsname and use of the contents of that
directory by the subcommand.

138 z/OS MVS IPCS Commands

 EVALDUMP subcommand

INFILE(ddname)
INDDNAME(ddname)
Requests use of a directory that the IPCS user has allocated to ddname and
use of the contents of that directory by the subcommand.
The syntax for var-list is as follows:

[ DECIMAL | F ]
[ HEXADECIMAL | X ]
[ BLOCKS(blocks) ]
[ BYTES(bytes) ]
[ QUALIFICATION(qualification) ]
[ SOURCE(var-name)|DATASET(var-name)|DSNAME(var-name) ]

DECIMAL or F
HEXADECIMAL or X
Specifies the format of the number of blocks.
DECIMAL or F designates that IPCS format the number of blocks using
decimal digits. The default is DECIMAL.
HEXADECIMAL or X designates that IPCS format the number of blocks
using hexadecimal digits.
BLOCKS(blocks)
Places the number of blocks contained in the dump to be formatted in the
variable blocks.
BYTES(bytes)
Formats and places the number of bytes contained in the dump in the
variable bytes. IPCS always uses decimal for the number of bytes.
QUALIFICATION(qualification)
Formats and places the address qualifiers that describe the default address
space for the dump in the variable qualification.
SOURCE(var-name) | DATASET(var-name) | DSNAME(var-name)
Places the name of the retrieved data set in the variable var-name.
v SETDEF-Defined Parameters
ACTIVE or MAIN or STORAGE
DSNAME(dsname) or DATASET(dsname)
FILE(ddname) or DDNAME(ddname)
Specifies the source of the source description from which you want to
retrieve information. If one of these parameters is not specified, IPCS uses
your current source.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the EVALDUMP subcommand.
v Example: The BLSCEDUM CLIST lists the number of blocks and bytes for each
source in the dump directory. It uses the EVALDUMP subcommand to retrieve
the information as follows:
EVALDUMP >= ACTIVE CLIST(SOURCE(SRC) BLOCKS(JL) BYTES(JY))
See the BLSCEDUM member of SYS1.SBLSCLI0 for the complete listing.

Chapter 5. IPCS subcommands 139

EVALMAP subcommand

EVALMAP subcommand — format a storage map entry

Use the EVALMAP subcommand to retrieve information associated with an entry
in the storage map and to format that information in CLIST variables, REXX
variables, or ISPF function pool dialog variables.

The storage map is part of a source description. The source description is for an
unformatted source that IPCS can format, for example, an SVC dump, a
stand-alone dump, an SYSMDUMP dump, a trace data set, a data set, or active
storage. The source description is in a directory allocated with ddname IPCSDDIR
and is your current dump directory. The current dump directory is your user
dump directory or, for users with access authority, might be the sysplex dump
directory.

Numeric information may be formatted in decimal or hexadecimal. Default

formatting for pointers and data used in conjunction with pointers is hexadecimal.
Default formatting for other numeric data is decimal.

Note: With TSO/E Release 2 installed, you can use this subcommand to update
global CLIST variables. For information about using global variables and writing
your own CLISTs, see z/OS TSO/E CLISTs and z/OS MVS IPCS User's Guide.
v Related subcommands
– EQUATE
– EVALDEF
– EVALDUMP
– EVALSYM
v Syntax

EVALMAP [ relational-operator ]

data-descr
[SELECT([AREA][MODULE][STRUCTURE])]
[ CLIST(var-list) ]
[ DIALOG(var-list) ]
[ REXX(var-list) ]

-------- SETDEF-Defined Parameter --------------------------

Note: You can override the following SETDEF parameter.
See “SETDEF subcommand — set defaults” on page 262.
[ TEST | NOTEST ]

v Parameters
The DIMENSION, ENTRY, HEXADECIMAL, LENGTH, MULTIPLE, POSITION,
and X parameters may appear in both the data-descr and var-list variables.
relational-operator
Specifies one of the following symbolic or programming operators to be
used in conjunction with the data description to identify which map entry is
to be retrieved. The syntax for relational-operator is as follows:
[ < | LT ]
[ <= | LE ]
[ > | GT ]
[ >= | GE ]
[ ¬> | NG ]
[ ¬< | NL ]
[ = | EQ ]

140 z/OS MVS IPCS Commands

 EVALMAP subcommand

For example, the less than(<|LT) relationship is satisfied by the

highest-collating map entry that collates lower than the byte addressed by
the data description.
data-descr
Specifies the data description parameter, which consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.

Note: The qualification, address, and data type are all part of the key of a
map entry. To write a CLIST or dialog that moves from one map entry to
another, you must specify all three arguments in your data description.
SELECT([AREA][MODULE][STRUCTURE])
Specifies the data types to be returned as results of the EVALMAP
command.
AREA
Allows EVALMAP to associate the location of interest with AREAs.
MODULE
Allows EVALMAP to associate the location of interest with MODULEs.
STRUCTURE
Allows EVALMAP to associate the location of interest with
STRUCTUREs.

When no selection is specified or all selections are chosen, EVALMAP can

associate the location of interest with AREAs, MODULEs, or STRUCTUREs.
CLIST(var-list)
DIALOG(var-list)
REXX(var-list)
Specifies how the information is to be formatted.
CLIST(var-list) designates that the information be formatted into CLIST
variables.
DIALOG(var-list) designates that the information be formatted into ISPF
function pool dialog variables.
REXX(var-list) designates that the information be formatted into REXX
variables.
The syntax for var-list is as follows:

Chapter 5. IPCS subcommands 141

EVALMAP subcommand

[ DECIMAL | F ]
[ HEXADECIMAL | X ]
[ ADDRESS(address) ]
[ ANALYSIS(analysis) ]
[ DATATYPE(type[,group]) ]
[ DIMENSION(dimension)|MULTIPLE(dimension) ]
[ ENTRY(entry) ]
[ FLAG(flag) ]
[ LENGTH(length) ]
[ POSITION(position) ]
[ QUALIFICATION(qualification) ]

DECIMAL or F
HEXADECIMAL or X
Specifies the format of the numeric information.
DECIMAL or F designates that the numeric information be formatted using
decimal digits.
HEXADECIMAL or X designates that the numeric information be formatted
using hexadecimal digits.
Table 9 summarizes the effect of specifying DECIMAL and HEXADECIMAL
on the other parameters.
Table 9. Effect of DECIMAL and HEXADECIMAL on the other parameters
Parameter Default DECIMAL changes HEXADECIMAL
the default? changes the default?
ADDRESS HEXADECIMAL yes
DIMENSION DECIMAL yes
ENTRY DECIMAL yes
LENGTH DECIMAL yes
POSITION HEXADECIMAL yes

ADDRESS(address)
Requests that the address associated with the map entry be formatted and
placed in the variable address. Unless DECIMAL is specified, the address is
formatted in hexadecimal; if DECIMAL is specified, decimal digits are used.
ANALYSIS(analysis)
The degree of validation completed for the block is placed in the variable
analysis:
– NOCHECKER
– NONE
– PARTIAL
– COMPLETE
DATATYPE(type[,group])
Requests that the data type associated with the map entry be formatted and
placed in the variable type.
If you specify group, EVALMAP formats the group data type and places it in
the variable group. For example, if type is set to STRUCTURE(UCBDA) for
an MVS dump, group is set to STRUCTURE(UCB).
DIMENSION(dimension) | MULTIPLE(dimension)
Requests that the dimension, or replication factor, for the map entry be

142 z/OS MVS IPCS Commands

 EVALMAP subcommand

formatted and placed in the variable dimension. Unless HEXADECIMAL is

specified, the dimension is formatted in decimal; if HEXADECIMAL is
specified, hexadecimal digits are used.
If the map entry is defined as a SCALAR, a zero dimension is supplied. The
return code is set to 4 unless a more serious condition is also detected.
ENTRY(entry)
Requests that the subscript associated with the initial array entry described
by the map entry be formatted and placed in the variable entry Unless
HEXADECIMAL is specified, the subscript is formatted in decimal; if
HEXADECIMAL is specified, hexadecimal digits are used.
If the map entry is defined as a SCALAR, a zero subscript is supplied. The
return code is set to 4 unless a more serious condition is also detected.
FLAG(flag)
Requests that the most severe condition detected when the validity of the
block was checked be placed in the variable flag:
– INFORMATIONAL
– WARNING
– ERROR
– SERIOUS
LENGTH(length)
Requests that the length associated with the map entry be formatted and
placed in the variable length. Unless HEXADECIMAL is specified, the length
is formatted in decimal; if HEXADECIMAL is specified, hexadecimal digits
are used.
If the data described is an array, length is for one entry in the array. To
calculate the length of the array, multiply the length by the dimension.
POSITION(position)
Requests that the signed offset associated with the map entry be formatted
and placed in the variable position. The offset is the number of bytes skipped
between the address of the data and the first physical byte described.
Unless DECIMAL is specified, the address is formatted in hexadecimal; if
DECIMAL is specified, decimal digits are used.
QUALIFICATION(qualification)
Requests that the address qualifiers be formatted and placed in the variable
qualification. The address qualifiers are for the address space described by the
map entry.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the EVALMAP subcommand.
v Example: The BLSCEMAP CLIST counts all the task control blocks (TCBs) in the
storage map for the default data set and displays the sum. It uses the EVALMAP
subcommand to retrieve the information as follows:
EVALMAP >= 0. ABSOLUTE STRUCTURE CLIST(QUALIFICATION(Q) +
ADDRESS(A) DATATYPE(T))
See the BLSCEMAP member of SYS1.SBLSCLI0 for the complete listing.

Chapter 5. IPCS subcommands 143

EVALPROF subcommand

EVALPROF subcommand — format PROFILE subcommand options

Use the EVALPROF subcommand values to format the values in CLIST variables,
REXX variables, or ISPF function pool dialog variables.

The default values are established from the dump directory during IPCS session
initialization. You can modify the defaults using the PROFILE subcommand during
the course of your session, which will cause the values to become effective
immediately and recorded as defaults for a subsequent session where the same
directory is used.
v Related subcommands
– EVALDEF
– EVALDUMP
– EVALMAP
– EVALSYM
– PROFILE
v Syntax

VERB OPERANDS

EVALPROF { CLIST(variable-list) }
{ DIALOG(variable-list) }
{ REXX(variable-list) )
-------- SETDEF-Defined Parameter --------------------------
Note: You can override the following SETDEF parameter. See “SETDEF subcommand —
set defaults” on page 262.

v Parameters
CLIST(var-list)
DIALOG(var-list)
REXX(var-list)
Specifies how the information is to be formatted.
CLIST(var-list) designates that the information be formatted into CLIST
variables.
DIALOG(var-list) designates that the information be formatted into ISPF
function pool dialog variables.
REXX(var-list) designates that the information be formatted into REXX
variables. The syntax for var-list is as follows:
EXCLUDE(variable-name)
LINESIZE(variable-name)
PAGESIZE(variable-name)
STACK(variable-name)
EXCLUDE(variable-name)
Places the list of exclusions in variable variable-name.
LINESIZE(variable-name)
Places the line size in variable variable-name.
PAGESIZE(variable-name)
Places the page size in variable variable-name.
STACK(variable-name)
Places DUPLICATES or NODUPLICATES in variable variable-name.
v Return Codes

144 z/OS MVS IPCS Commands

 EVALPROF subcommand

See “Standard subcommand return codes” on page 46 for a description of the

return codes produced by the EVALPROF subcommand.

EVALSYM subcommand — format the definition of a symbol

Use the EVALSYM subcommand to retrieve information associated with a symbol
and format that information in CLIST variables, REXX variables, or ISPF function
pool dialog variables.

The symbol is in a symbol table that is part of a source description. The source
description is in a directory allocated with ddname IPCSDDIR and is your current
dump directory. The current dump directory is your user dump directory or, for
users with access authority, might be the sysplex dump directory.

Numeric information can be formatted in decimal or hexadecimal. Default

formatting for pointers and data used in conjunction with pointers is hexadecimal.
Default formatting for other numeric data is decimal.

Note: With TSO/E Release 2 installed, you can use this subcommand to update
global CLIST variables. For information about using global variables and writing
your own CLISTs, see z/OS TSO/E CLISTs and z/OS MVS IPCS User's Guide.
v Related subcommands
– EQUATE
– EVALDEF
– EVALDUMP
– EVALMAP
– EVALUATE
Guideline: EVALUATE does not handle log streams nor does it deal with
dumps or traces in added status within the dump directory. The ability to
format the value of a literal symbol was added to EVALSYM to enable
command procedures to access such values in these circumstances.
v Syntax

EVALSYM [ relational-operator ]

symbol
[ CLIST(var-list) ]
[ DIALOG(var-list) ]
[ REXX(var-list) ]
[ INDATASET(dsname) | INFILE(ddname) ]

-------- SETDEF-Defined Parameter --------------------------

Note: You can override the following SETDEF parameter.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ TEST | NOTEST ]

v Parameters
relational-operator
Specifies one of the following symbolic or programming operators to be
used in conjunction with the data description to identify which map entry is
to be retrieved. The syntax for relational-operator is as follows:

Chapter 5. IPCS subcommands 145

EVALSYM subcommand

[ < | LT ]
[ <= | LE ]
[ > | GT ]
[ >= | GE ]
[ ¬> | NG ]
[ ¬< | NL ]
[ = | EQ ]

For example, the less than (<|LT) relationship is satisfied by the

highest-collating map entry that collates lower than the byte addressed by
the data description.
symbol
Specifies a symbol to be used with a relational operator. The definition of the
symbol is to be retrieved.
CLIST(var-list)
DIALOG(var-list)
REXX(var-list)
Specifies how the information is to be formatted.
CLIST(var-list) designates that the information be formatted into CLIST
variables.
DIALOG(var-list) designates that the information be formatted into ISPF
function pool dialog variables.
REXX(var-list) designates that the information be formatted into REXX
variables.
INDATASET(dsname)
INDSNAME(dsname)
Requests allocation of directory dsname and use of the contents of that
directory by the subcommand.
INFILE(ddname)
INDDNAME(ddname)
Requests use of a directory that the IPCS user has allocated to ddname and
use of the contents of that directory by the subcommand.
The syntax for var-list is as follows:

[ DECIMAL | F ]
[ HEXADECIMAL | X ]
[ ADDRESS(address) ]
[ DATATYPE(type[,group]) ]
[ DIMENSION(dimension)|MULTIPLE(dimension) ]
[ DROP(drop) ]
[ ENQUOTE|UNQUOTE|NOQUOTES ]
[ ENTRY(entry) ]
[ FLAG(flag) ]
[ LENGTH(length) ]
[ NOBLANKS ]
[ POSITION(position) ]
[ QUALIFICATION(qualification) ]
[ REMARK(remark) ]
[ SYMBOL(symbol) ]
[ VALUE(value) ]

DECIMAL or F
HEXADECIMAL or X
Specifies the format of the numeric information:
– DECIMAL or F for decimal

146 z/OS MVS IPCS Commands

 EVALSYM subcommand

– HEXADECIMAL or X for hexadecimal

ADDRESS(address)
Places in the variable address the address associated with the symbol. Unless
DECIMAL is specified, the address is formatted in hexadecimal; if
DECIMAL is specified, decimal is used.
DATATYPE(type)
Places in the variable type the data type for the symbol. The preferred
representations for the data type are:
– BIT (rather than HEXADECIMAL or X)
– CHARACTER (rather than C)
– SIGNED (rather than F)
– POINTER (rather than PTR)
DIMENSION(dimension) or MULTIPLE(dimension)
Places in the variable dimension the dimension, or replication factor,
associated with the symbol. Unless HEXADECIMAL is specified, the
dimension is in decimal; if HEXADECIMAL is specified, hexadecimal is
used.
If the symbol is defined as a SCALAR, a zero dimension is supplied. The
return code is set to 4 unless a more serious condition is also detected.
DROP(drop)
Places in the variable drop the value DROP or NODROP.
ENQUOTE | UNQUOTE | NOQUOTES
Specifies how REMARK text is to be formatted:
– ENQUOTE requests a quoted string.
– UNQUOTE and NOQUOTES request that apostrophes (X'7D') translated
to periods.
ENTRY(entry)
Places in the variable entry the subscript associated with the initial array
entry described by the symbol. Unless HEXADECIMAL is specified, the
subscript is in decimal; if HEXADECIMAL is specified, hexadecimal is used.
If the symbol is defined as a SCALAR, a zero subscript is supplied. The
return code is set to 4 unless a more serious condition is also detected.
FLAG(flag)
Places in the variable flag the most severe condition detected when the
validity of the block was checked:
– INFORMATIONAL
– WARNING
– ERROR
– SERIOUS
LENGTH(length)
Places in the variable length the length associated with the symbol. Unless
HEXADECIMAL is specified, the length is decimal; if HEXADECIMAL is
specified, hexadecimal is used.
If the data described is an array, the length describes one entry in the array.
The length of the array may be computed by multiplying the length of one
entry by the dimension.

Chapter 5. IPCS subcommands 147

EVALSYM subcommand

NOBLANKS
Requests that blanks (X'40') in REMARK text be translated to periods.
POSITION(position)
Places in the variable position the signed offset associated with the symbol.
The offset is the number of bytes skipped between the address of the data
and the first physical byte described. Unless DECIMAL is specified, the
address is in hexadecimal; if DECIMAL is specified, decimal is used.
QUALIFICATION(qualification)
Places in the variable qualification the address qualifiers for the address space
described by the symbol.
REMARK(remark)
Places in the variable remark the remark associated with the symbol. The
remark text is edited for use in CLISTs, REXX execs, or ISPF dialogs:
– EBCDIC lower case alphabetic characters (a-z) are always replaced by
uppercase characters (A-Z), and EBCDIC superscript decimal digits
(X'B0'-X'B9') are always replaced by common decimal digits (X'F0'-X'F9').
– Characters not present on either the IBM 1403 TN print chain or the IBM
3211 T11 print train are always replaced by periods.
– Ampersands are always replaced by periods.
– Blanks are replaced by periods if the NOBLANKS option is selected.
Otherwise, blanks are not edited.
– Apostrophes (X'7D') are left alone if you do not specify ENQUOTE,
UNQUOTE, or NOQUOTES. The string placed in the variable is the same
length as that of the string in the dump. However, the following
parameters affect this option:
ENQUOTE
One leading apostrophe and one trailing apostrophe are supplied.
Apostrophes found in dump data are paired.
UNQUOTE|NOQUOTES
Apostrophes found in dump data are replaced by periods. The string
placed in the variable is the same length as that of the string in the
dump.
SYMBOL(symbol)
Places in the variable symbol the name of the symbol retrieved.
VALUE(value)
Places in the literal value the value associated with a literal symbol. The
following formatting is performed:
1. If the symbol is not associated with a literal value, a single blank is
stored.
2. Unless HEXADECIMAL is specified, SIGNED and UNSIGNED data are
formatted using decimal digits. If HEXADECIMAL is specified,
hexadecimal digits are used.
3. Unless DECIMAL is specified, POINTER data is formatted using
hexadecimal digits. If DECIMAL is specified, decimal digits are used.
4. CHARACTER data is formatted subject to the same criteria used for
REMARK text.
5. All other types of data are formatted using hexadecimal digits.
v SETDEF-Defined Parameters
ACTIVE or MAIN or STORAGE

148 z/OS MVS IPCS Commands

 EVALSYM subcommand

DSNAME(dsname) or DATASET(dsname)
FILE(ddname) or DDNAME(ddname)
Specifies the source of the source description that contains the symbol. If one
of these parameters is not specified, IPCS uses your current source.
v Return Codes
0 The symbol is defined and all CLIST variables have been updated.
12 The symbol is not defined and no CLIST variables have been updated.
16 Environmental error is detected.
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the EVALSYM subcommand.
v Example: The BLSCESYM CLIST counts all the symbols representing task
control blocks (TCBs) in the symbol table for the default data set and displays
the sum. It uses the following EVALSYM subcommand to retrieve the
information:
EVALSYM >= $ CLIST(SYMBOL(SYM) DATATYPE(T))
See the BLSCESYM member of SYS1.SBLSCLI0 for the complete listing.

EVALUATE subcommand — retrieve dump data for a variable

Use the EVALUATE subcommand to retrieve information from a dump and format
that information in CLIST variables, REXX variables, or ISPF function pool dialog
variables.

“Default option” on page 152 discusses the processing of the EVALUATE

subcommand when the CHECK, CLIST, REXX, and DIALOG parameters are all
omitted. This is an archaic form of the EVALUATE subcommand that should not
be used in new CLISTs, REXX execs, or dialogs. When existing CLISTs and REXX
execs are updated, the old subcommand should be replaced with an EVALUATE
subcommand using a CLIST, REXX, or DIALOG parameter. See “CLIST, REXX, or
DIALOG option” on page 151.

Note:
1. EVALUATE might modify X, the current address.
2. With TSO/E Release 2 installed, you can use this subcommand to update
global CLIST variables. For information about using global variables and
writing your own CLISTs, see z/OS TSO/E CLISTs and z/OS MVS IPCS User's
Guide.
v Related subcommands
– EVALSYM
v Syntax

Chapter 5. IPCS subcommands 149

EVALUATE subcommand

{ EVALUATE } data-descr
{ EVAL }

[ CLIST(var-list) [ MASK(mask) ] ]
[ DIALOG(var-list) [ MASK(mask) ] ]
[ REXX(var-list) [ MASK(mask) ] ]
[ CHECK ]

-------- SETDEF-Defined Parameter --------------------------

Note: You can override the following SETDEF parameter.
See “SETDEF subcommand — set defaults” on page 262.
[ TEST | NOTEST ]

v Parameters
data-descr
Specifies the data description parameter, which consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.
MASK(mask)
Defines a value that is logically ANDed with the retrieved information. The
AND operation occurs before the retrieved information is formatted into a
variable. The mask must be the same length as the retrieved information.
The mask value must be a general value. See Chapter 2, “Literal values,” on
page 9 for more information about specifying a general value.
CHECK
Directs IPCS to inform a CLIST, REXX exec, or ISPF dialog whether 1 to 4
bytes of storage can be accessed in a dump. “CHECK option” on page 153
discusses this option further.
CLIST(var-list)
DIALOG(var-list)
REXX(var-list)
Specifies how to format the information.
CLIST(var-list) designates that the information be formatted into CLIST
variables.
DIALOG(var-list) designates that the information be formatted into ISPF
function pool dialog variables.
REXX(var-list) designates that the information be formatted into REXX
variables.
The syntax for var-list is as follows:

[ ENQUOTE|UNQUOTE|NOQUOTES ]
[ NOBLANKS ]
[ PROTECTION(protection) ]
[ STORAGE(storage) ]
[ FORMATTED|UNFORMATTED ]

150 z/OS MVS IPCS Commands

 EVALUATE subcommand

ENQUOTE or UNQUOTE or NOQUOTES

Specifies how CHARACTER data is to be formatted:
– ENQUOTE requests a quoted string.
– UNQUOTE and NOQUOTES request that apostrophes (X'7D') translated
to periods.
NOBLANKS
Requests that blanks (X'40') in CHARACTER data be translated to periods.
PROTECTION(protection)
Specifies the name of the CLIST, REXX, or ISPF dialog variable into which
IPCS places the formatted protection key.

Note: When no storage key is known for a block of storage, IPCS supplies
the value X'FF' This occurs when IPCS processes DOMAIN(SUMDUMP)
records and active storage. The following topic, “CLIST, REXX, or DIALOG
option,” discusses the processing performed.
STORAGE(storage)
Specifies the name of the variable into which IPCS places the formatted
storage.
FORMATTED or UNFORMATTED
Specifies how the information is to be returned:
– FORMATTED
Formatted data is returned. This is the default.
– UNFORMATTED
Unformatted data is returned. This option is mutually exclusive with the
following var-list keywords:
- ENQUOTE | UNQUOTE | NOQUOTES
- NOBLANKS
The UNFORMATTED keyword causes the storage variable, if specified, to
receive an image of the data requested. The storage that can be processed
is 32760 bytes.

CLIST, REXX, or DIALOG option

EVALUATE processing is divided into four parts:
1. The data description is edited, if necessary:
v If the length of data is more than 512 bytes, LENGTH(512) is substituted.
v If an array containing multiple entries is described, DIMENSION(1) is
substituted.
v If a data type other than bit, character, pointer, signed, or unsigned is
specified, BIT is substituted.
Return code 4 is set when editing occurs.
2. The storage described by the edited data description is retrieved.
If the storage is not available, EVALUATE processing ends with return code 12.
3. If storage formatting was requested, the data is formatted and stored in a
variable. Formatting is primarily controlled by the type of data retrieved:
v BIT|POINTER — Bit string and pointer data is formatted using 2
hexadecimal digits for each byte retrieved.
v CHARACTER — Character string data is edited for use in CLISTs, REXX
execs, or ISPF dialogs:

Chapter 5. IPCS subcommands 151

EVALUATE subcommand

– EBCDIC lower case alphabetic characters (a-z) are replaced by uppercase

characters (A-Z), and EBCDIC superscript decimal digits (X'B0'-X'B9') are
replaced by common decimal digits (X'F0'-X'F9').
– Characters not present on either the IBM 1403 TN print chain or the IBM
3211 T11 print train are replaced by periods.
– Ampersands are replaced by periods.
– Blanks are replaced by periods if the NOBLANKS option is selected.
Blanks are not changed otherwise.
– Editing of apostrophes (X'7D') is governed by the subcommand option
selected:
ENQUOTE
One leading and one trailing apostrophe are supplied. Apostrophes
found in dump data are paired.
UNQUOTE|NOQUOTES
Apostrophes found in dump data are replaced by periods. The string
placed in the variable is the same length as that of the string in the
dump.
If no subcommand option is specified, apostrophes are not edited. The
string placed in the variable is the same length as that of the string in the
dump.
v SIGNED — Signed binary integers are formatted using decimal digits.
Leading zeros are removed. A minus sign is supplied for negative integers.
v UNSIGNED — Unsigned binary integers are formatted using decimal digits.
Leading zeros are removed.
4. If the protection key was requested, it is formatted and stored in a variable.
The protection key is formatted using 2 hexadecimal digits.
v If no storage key was provided by the dumping program or multiple
inconsistent storage keys (different fetch-protection or reference key values)
apply to the storage, the value stored is X'FF'.
v Otherwise, the value is formatted using the fetch-protection and reference
key bits that apply to all storage described. The reference and change bits are
represented as on if they are on for any block of storage described.
5. If no storage formatting was requested with UNFORMATTED, the data
requested is returned in the area specified by STORAGE. The amount of data
retrieved can be up to 32760 bytes. When UNFORMATTED is specified, the use
of ENQUOTE | UNQUOTE | NOQUOTES and NOBLANKS is not allowed.

If the CLIST, REXX, or DIALOG option is specified, EVALUATE uses its return
code (see Table 10) to indicate whether the requested operation was successful.
Table 10. Return codes for the CLIST, REXX, or DIALOG option
Code Explanation
00 Successful completion
04 Description of data was edited.
12 Data not available or not defined. The variables are not changed.

Default option
The default option of the EVALUATE subcommand retrieves an unsigned binary
number from a dump and uses that number as its return code. The number in the
dump may span 1 to 4 bytes.

152 z/OS MVS IPCS Commands

 EVALUATE subcommand

Note: If a 4-byte number is used as a return code, EVALUATE translates the

high-order byte of the number to zeros after retrieving it from the dump and
before using it as a return code. This reduces the actual precision of the value from
32-bits (0 to 231-1) to 24-bits (0 to 223-1) because the latter is the precision used for
TSO command and subcommand return codes.

In a CLIST, the subcommand following EVALUATE can refer to the return code
with the CLIST variable &LASTCC. EVALUATE has little use other than in CLISTs
because the return code is made available by the CLIST variable &LASTCC.

Each subcommand in a CLIST resets &LASTCC. Thus, the data retrieved by

EVALUATE must be examined or moved from &LASTCC before another
subcommand in the CLIST overlays it.

Use caution in using the contents of &LASTCC after this subcommand. It may
contain data or a return code; however, there is no way of determining which. For
example, if the specified storage cannot be retrieved, EVALUATE generates return
code 12. This is, in fact, a return code indicating the failure to retrieve the data, but
it can be interpreted as data.
Table 11. Return codes for the Default option
Code Explanation
12 Severe, requested storage cannot be retrieved.
16 Terminating, an error condition from a called service routine forced an early
termination.
other Successful completion, uses the requested data as a return code.

CHECK option
If the CHECK option is specified, EVALUATE uses its return code (see Table 12) to
indicate whether diagnostic data can be retrieved. It is also used to indicate other
concerns if the same data description is used with the default form of EVALUATE.
Table 12. Return codes for the CHECK option
Code Explanation
00 Successful completion
04 Description of data was edited
v If the length is more than 4 bytes, LENGTH(4) is substituted.
v If an array containing multiple entries is described, DIMENSION(1) is
substituted.
v Only the UNSIGNED data type is supported. If another data type is
described, UNSIGNED is substituted.
08 Four bytes of data were retrieved but the initial byte does not contain X'00'.
Significance is lost if the first byte of a fullword is removed. That byte does
not contain X'00'.
12 Data not available or not defined.

FIND subcommand — locate data in a dump

Use the FIND subcommand to locate literal values in a dump.
v Search argument and options

Chapter 5. IPCS subcommands 153

FIND subcommand

You must specify a search argument the first time you use FIND. FIND saves
the search argument and any options you specify:
– The data type of the search argument allows you to request signed binary
comparisons or logical (bit by bit) comparisons.
– A relational operator allows you to indicate whether the data sought is less
than, equal to, or greater than the search argument, and so on.
– The BOUNDARY option allows you to search only for data aligned on
storage boundaries, such as doubleword boundaries.
– The BREAK option allows you to stop when storage is missing for a
comparison or continue the search beyond the missing storage.
– The MASK option allows you to ignore selected bits when the search
argument is compared with storage.
If you omit a search argument later, the subcommand uses the saved argument
and options. If you override options, the new options are merged with those
saved earlier and all options are saved.
If you respecify a search argument, the saved options are discarded.
v Storage searched
You can limit the search by specifying the range of addresses to be searched.
FIND uses the symbol FINDAREA (recorded in the symbol table) to describe the
beginning address and the length of the area.
The FIRST, LAST, NEXT, and PREVIOUS options allow you to control the
direction of a search and to force a search to be resumed at either end of
FINDAREA.
Before the search begins, FIND sets X to the first address to be searched. If it
locates a match, FIND sets X to the address of the match. Otherwise, FIND
leaves X set to the first address searched. If no range of addresses is explicitly
set on the initial invocation of the FIND subcommand, IPCS searches an entire
address space.
After the subcommand sets the search range (FINDAREA and its length), if you
request another search without specifying a new range and if X is outside the
current search range, FIND ends immediately, without modifying X. (X can be
outside the current search range only if you have modified FINDAREA, X, or
both between the two searches.)
If you do not specify a beginning address for the search range but you do
specify a search argument, FIND begins the search at X. If you do not specify a
beginning address for the search range or a search argument, FIND begins the
search at:
– X + 1 if FIND FIRST or FIND NEXT processing is being resumed.
– X - 1 if FIND LAST or FIND PREVIOUS processing is being resumed.
In either case, the end point of the search range remains the same.

Note: This subcommand may modify X, the current address.

v Related subcommands
– FINDMOD
– FINDUCB
v Syntax

154 z/OS MVS IPCS Commands

 FIND subcommand

{ FIND } [ relational-operator ]
{ F }
[ value ]
[ data-descr ]
[ BOUNDARY(bdy [,index-range]) ]
[ BREAK | NOBREAK ]
[ FIRST ]
[ LAST ]
[ NEXT ]
[ PREVIOUS ]
[ MASK(mask) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
[ VERIFY | NOVERIFY ]

v Parameters
relational-operator
Specifies one of the following symbolic or programming operators to be
used with the value parameter and the BOUNDARY, BREAK, and MASK
parameters to establish the search criterion:
[<|LT|<=|LE|¬>|NG|=|EQ|>=|GE|¬<|NL|>|GT|¬|NE]
value
Specifies a general value. See Chapter 2, “Literal values,” on page 9 for
information, syntax, and examples. If the BOUNDARY, BREAK, and MASK
parameters are not specified in the FIND subcommand, the default options
are:
– BOUNDARY(1,1)
– BREAK
– NOMASK
data-descr
Specifies the data description parameter, which consists of five parts:
– An address (required when data-descr is explicitly specified on the
subcommand)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter. However, the following exception
applies to the FIND subcommand only:
– The address is not a positional parameter. You must use the ADDRESS
parameter to specify an address.
BOUNDARY(bdy[,index-range])
Requests that storage be partitioned into strings bdy bytes in length. The
address of each string is divisible by bdy. FIND performs only one

Chapter 5. IPCS subcommands 155

FIND subcommand

comparison with data whose first byte lies within any string. The
abbreviation BDY is accepted for this parameter. The index value designates
which byte FIND is to select:
BDY(1) or BDY(1,1) or BDY(1,1:1)
FIND examines each byte.
BDY(2) or BDY(2,1) or BDY(2,1:1)
FIND performs comparisons with strings originating at even-numbered
addresses.
BDY(2,2) or BDY(2,2:2)
FIND performs comparisons with strings originating at odd-numbered
addresses.
BDY(5,5) or BDY(5,5:5)
FIND performs comparisons only with strings originating at addresses 4
bytes past an address divisible by 5.
BDY(7,6:7)
FIND performs comparisons only with strings originating at addresses 5
or 6 bytes past an address divisible by 7.
BDY(8) or BDY(8,1) or BDY(8,1:1)
FIND performs comparisons only with strings aligned on doubleword
boundaries.

Both bdy and index-range can be 1 through 231 and can be specified in
decimal, hexadecimal (X'xxx...'), or binary (B'bbb...').
When you specify this option, it remains in effect until you specify a new
search argument or override this option. The default, BDY(1,1), is used only
when a new search argument is entered and this option is omitted.
BREAK or NOBREAK
Indicates if FIND is to continue processing if IPCS cannot retrieve storage
from the dump.
BREAK specifies that FIND is to stop processing if it cannot retrieve storage
from the dump to continue the search. This happens if the required storage
was not obtained by IPCS or the required storage is not contained in the
dump.
NOBREAK specifies that FIND is to continue processing if it cannot retrieve
storage from the dump. FIND continues the search with the next available
address in the dump.
When you specify BREAK or NOBREAK, it remains in effect until you
specify a new search argument or you override this option. The default of
BREAK is used only when a new search argument is entered and this option
is omitted.
FIRST
LAST
NEXT
PREVIOUS
Specifies where the search is to begin.
FIRST specifies that the search is to begin at the lowest address in
FINDAREA and is to proceed from low-numbered addresses to higher
addresses.

156 z/OS MVS IPCS Commands

 FIND subcommand

LAST specifies that the search is to begin at the highest address in

FINDAREA and is to proceed from high-numbered addresses to lower
addresses.
NEXT specifies that the search is to proceed from low-numbered addresses
to higher addresses.
PREVIOUS specifies that the search is to proceed from high-numbered
addresses to lower addresses.
MASK(mask) | NOMASK
Requests or suppresses a mask. MASK defines a value that is logically
ANDed with both operands before performing the comparison. The mask
must be the same size as the data items being compared.
The mask value must be a general value. See “General values” on page 10
for more information.
NOMASK suppresses masking.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the FIND subcommand.
v Example 1: Search for a character string in the first 10 columns of an 80-byte
record in a buffer pool. The first 10 columns contain a character string.
– Action
COMMAND ===> find c’ABC’ addr(bufferpool) bdy(80,1:10)
– Result
X is set to describe the 3 bytes of storage in which the data was found. If the
VERIFY parameter is in effect, FIND displays where the match was found.
The actual content of the display is controlled by the DISPLAY parameters in
effect.
v Example 2: Search for a fullword pointer that is present in the storage searched.
– Action
COMMAND ===> find a’fdfd’ bdy(4)
– Result
X is set to describe the 4 bytes of storage in which the data was found. If the
VERIFY parameter is in effect, FIND displays where the match was found.
The actual content of the display is controlled by the DISPLAY parameters in
effect.
v Example 3: Search the NUCLEUS CSECT table for the entry containing a
requested address. The table is aligned on a page boundary and contains a series
of 16-byte entries. For example:
Offset Description
00 Name of NUCLEUS CSECT in EBCDIC
08 Address of NUCLEUS CSECT
0C Length of NUCLEUS CSECT
The entries in the table are sorted in ascending order by the address of the
NUCLEUS CSECT.
– Action
COMMAND ===> find [= a’requested-address’
address(table-origin :table-end)
bdy(16,9) last
– Result

Chapter 5. IPCS subcommands 157

FIND subcommand

This command updates X to describe the ninth through the twelfth bytes of
the table entry. That is, X describes the field that contains the address of the
NUCLEUS CSECT.
Here is a breakdown of each parameter's function in this example:
- The relational-operator, [=, causes the search to fail for all table entries
associated with CSECTs whose addresses are greater than the
requested-address.
- The fullword pointer, requested-address, is the value sought.
- ADDRESS(table-origin :table-end) limits the search within the bounds of
the table. No address processing parameters are included because it is
assumed that the table is visible from the default address space in the
dump.
- bdy(16,9) causes comparisons to be made with strings originating at
addresses 8 bytes past an address divisible by 16.
- LAST causes the search to begin from the end of the table and proceed to
its beginning.

FINDMOD subcommand — locate a module name

Use the FINDMOD subcommand to locate a module in the dump. IPCS searches
as follows, in order:
1. Searches the symbol table for the specified symbol name with the attribute
MODULE
2. Searches the active link pack area (LPA) queue in the dump for the module in
the MLPA/EMLPA and FLPA/EFLPA
3. Searches the LPA directory in the dump for the module in the PLPA/EPLPA

If FINDMOD finds the requested module in the symbol table, it does not create
new symbols. If it finds the requested module on the CDE chain, it creates the
symbols:
v CDEmodulename
v XLmodulename
v modulename

If it finds the requested module on the LPDE chain, it creates the symbols:
v LPDEmodulename
v modulename

Note: This subcommand can modify X, the current address.

v Related subcommands
– FIND
– FINDUCB
v Syntax

158 z/OS MVS IPCS Commands

 FINDMOD subcommand

{FINDMOD } modulename
{FMOD }
[ CHARACTER ]
[ HEXADECIMAL ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
[ VERIFY | NOVERIFY ]

v Parameters
modulename
Specifies the module name to be located.
CHARACTER
HEXADECIMAL
Indicates how the module name is specified in modulename. CHARACTER
indicates a string of 1 to 8 EBCDIC characters. HEXADECIMAL indicates a
string of 2 to 16 hexadecimal digits.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the FINDMOD subcommand.

FINDSWA subcommand — locate a scheduler work area (SWA) block

Use the FINDSWA subcommand to locate a Scheduler Work Area (SWA) block,
including a SWA block prefix, in a dump.

Note: This subcommand can modify X, the current address.

v Related subcommands
– “CBFORMAT subcommand — format a control block” on page 72
– “FIND subcommand — locate data in a dump” on page 153
– “FINDMOD subcommand — locate a module name” on page 158
– “FINDUCB subcommand — locate a UCB” on page 160
v Syntax

{ FINDSWA } data-descr
{ FSWA }
[ CONTEXT ( JSCBACTIVE | symbol ) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.

v Parameters

Chapter 5. IPCS subcommands 159

FINDSWA subcommand

data-descr
Describes the location of a 3-byte SWA virtual token (SVA) for the SWA
block of interest.
CONTEXT(JSCBACTIVE)
CONTEXT(symbol)
Describes the context in which the SVA is to be interpreted. If a symbol
other than JSCBACTIVE is designated, it must describe either a
STRUCTURE(JSCB) or a STRUCTURE(TCB).
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the FINDSWA subcommand.

FINDUCB subcommand — locate a UCB

Use the FINDUCB subcommand to locate the unit control block (UCB) for a
specified device. When the subcommand finds the control block, it creates an entry
in the symbol table for UCBdddd, where dddd is the device number.

FINDUCB processes the specified device number as follows:

1. Searches the symbol table for the symbol UCBdddd. If found, IPCS displays the
storage associated with that symbol.
2. Verifies that the device was defined during system initialization.
3. Locates the device's UCB.

Note:
1. This subcommand may modify X, the current address.
2. Casual use of the FINDUCB subcommand is not recommended because
FINDUCB's processing requires a great deal of time.
v Related subcommands
– FIND
– FINDMOD
v Syntax

{FINDUCB } device-number
{FINDU }

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]

[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
[ VERIFY | NOVERIFY ]

v Parameters

160 z/OS MVS IPCS Commands

 FINDUCB subcommand

device-number
Specifies the device number of the device whose UCB is to be found. The
number is 1 to 4 hexadecimal digits; leading zeros are optional.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the FINDUCB subcommand.
v Example: Locate the UCB for device number 8000.
– Action
COMMAND ===> FINDUCB 8000
– Result
Even if you are using captured UCBs, FINDUCB returns the address of the
actual UCB. In this example, the actual UCB address is 01D0E028.
UCB8000 - UNIT CONTROL BLOCK FOR CHANNEL TO CHANNEL ADAPTER
LIST 01D0E028 ASID(X’0001’) POSITION(X’-0008’) LENGTH(48) STRUCTURE(UCBCTC)

GO subcommand — resume IPCS trap processing

Use the GO subcommand to resume trap processing after the STOP trap option is
encountered on the TRAPON subcommand. See “TRAPON subcommand —
activate IPCS traps” on page 318 for more information. The GO subcommand is
valid only during STOP processing for an exit debugging trap. When GO is used
and STOP processing is not in effect, IPCS issues message BLS21006I.

Note: The GO subcommand can be entered only in line mode. It cannot be entered
while in the IPCS dialog.
v Related subcommands
– TRAPON
– TRAPOFF
– TRAPLIST
v Syntax

GO

v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the GO subcommand.

GRSDATA subcommand — format Global Resource Serialization data

Use the GRSDATA subcommand to format reports showing serialization effected
by the ENQ, DEQ, ISGENQ, RESERVE, and latch service interfaces.

Note that when the GRS is running in STAR mode, the output of the GRSDATA
subcommand is dependent on the GRSQ option setting of the parmlib member
GRSCNFxx. For more information about the GRSCNFxx GRSQ setting, see the
z/OS MVS Planning: Global Resource Serialization.
v Related subcommands
– ANALYZE
– STATUS
v Syntax

Chapter 5. IPCS subcommands 161

GRSDATA subcommand

GRSDATA
The parameters are:

Data Selection Parameters:

[DETAIL]
[SUMMARY]

Additional Filter Parameters:

[SYSNAME(sysname)]
[QNAME(qname)]
[RNAME(rname)]
[STEP] [ SYSTEM] [ SYSTEMS]
[JOBNAME(jobname)]
[ASID(asid)]
[TCB(tcb)]
[RESERVE]
[CONTENTION]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Data selection parameters

DETAIL
Provides a detailed GRSTRACE report.
SUMMARY
Provides a summary GRSTRACE report.

Note: DETAIL and SUMMARY with GRSDATA produce the same report.
v Additional Filter Parameters
Use these parameters to limit the scope of the data in the report. If no data
selection parameter is selected, the default is DETAIL.
SYSNAME(sysname)
Displays all ENQ resources with the given specified system name. Note in
GRS=STAR, if the specified GRSQ option is LOCAL, only resource requests
from the dumped system will be displayed.
QNAME(qname)
Displays all ENQ resources with the specified QNAME (major name).
RNAME(rname)
Displays all ENQ resources with the specified RNAME (minor name).
[STEP] [ SYSTEM] [ SYSTEMS]
Displays all ENQ resources with a scope of STEP, SYSTEM, or SYSTEMS.
JOBNAME(jobname)
Displays all ENQ resources associated with the specified job name.
ASID(asid)
Displays all ENQ resources associated with the specified address space ID.

162 z/OS MVS IPCS Commands

 GRSDATA subcommand

TCB(tcb)
Displays all ENQ resources associated with the specified task
RESERVE
Displays only RESERVE requests that have not been converted to global
ENQs.
CONTENTION
Displays only ENQ resources that are in ENQ contention. Device RESERVE
contention is not taken into consideration.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the GRSDATA subcommand.
v Example: Format a global resource serialization report.
– Action
COMMAND ===> GRSDATA
– Result
IPCS produces the following output when SDATA=GRSQ information is
found in a dump.

Global system resources ▌1▐

Major.. CL8’RESERVEQ’ ▌2▐

Minor.. CL008’RESERVEM’ ▌3▐

SCOPE. SYSTEMS SYSNAME. SY1 JOBNAME. GRSTOOL ▌4▐

ASID.. 001B TCB..... 008F1B90 STATUS.. EXCLUSIVE ▌5▐

SCOPE. SYSTEMS SYSNAME. SY1 JOBNAME. GRSTOOL RESERVE. 0273

ASID.. 001C TCB..... 008F1B90 STATUS.. WAITEXC
ECB..... 05004614

Major.. CL8’RESERVEZ’ >

Minor.. CL009’RESERVEZ4’

SCOPE. SYSTEMS SYSNAME. SY2 JOBNAME. RTARGET4

ASID.. 0020 TCB..... 008F1B90 STATUS.. SHARED

SCOPE. SYSTEMS SYSNAME. SY2 JOBNAME. GRSTOOL

ASID.. 0021 TCB..... 008F1B90 STATUS.. WAITEXC
SVRB..... 008FF738

SCOPE. SYSTEMS SYSNAME. SY2 JOBNAME. MRGUY RESERVE

ASID.. 0022 TCB..... 008F1B90 STATUS.. WAITEXC
ECB..... 05004614

Major.. CL8’SYSZWLM’

Minor.. CL0019’WLM_SYSTEM_SY1’
XL019’E6D3D46D E2E8E2E3 C5D46DE2 E8F14040 404040’

SCOPE. SYSTEMS SYSNAME. SY1 JOBNAME. WLM

ASID.. 000B TCB..... 008FD7C0 STATUS.. EXCLUSIVE

Minor.. CL0019’WLM_SYSTEM_SY2’
XL019’E6D3D46D E2E8E2E3 C5D46DE2 E8F24040 404040’

SCOPE. SYSTEMS SYSNAME. SY2 JOBNAME. WLM

ASID.. 000B TCB..... 008FD7C0 STATUS.. EXCLUSIVE

Chapter 5. IPCS subcommands 163

GRSDATA subcommand

▌1▐ Resources are presented in the following order:

1. ASID(X'xxxx') (STEP) resources (ordered by ASID)
2. Local (SYSTEM) resources
3. Global (SYSTEMS) resources
This is consistent with the order used by verb exit QCBTRACE in
prior releases and with the order used by the GRSDATA subcommand
in the current release when GRS control blocks are used instead of the
data collected with the SDATA=GRSQ option of SDUMP.
▌2▐ Major resource names are presented using notation similar to that
used by assembler language coders. GRSDATA expects that uppercase
letters, including national characters, decimal digits, blanks and a
small number of punctuation characters are printable on all media. If
there is reason to believe that the major name cannot be accurately
shown on all media, a comma is placed after the EBCDIC
representation and a precise hexadecimal representation is added. For
example,
XL8’D9C5E2C5 D9E5C5D4’
▌3▐ Minor resource names are presented using notation familiar to
assembler language coders with trailing blanks, a common occurrence
not shown literally. The same test is made of minor names for
printability that is made for major names. If there is reason to believe
that the minor name cannot be accurately shown on all media, the
hexadecimal representation of the minor name is shown directly after
the EBCDIC representation.
▌4▐ The line beginning with the SCOPE caption introduces each
paragraph that discusses a TCB that owns or is awaiting ownership of
a resource. If the resource is associated with RESERVE processing on
a system other than the one dumped, the word RESERVE is added by
itself at the end of this line. If the resource is associated with
RESERVE processing on the dumped system, RESERVE is used as a
caption for a device address.
▌5▐ The line beginning with the ASID caption adds system internal status
to what was provided on the line beginning with the SCOPE caption.
The following status values shown in Table 13 may appear:
Table 13. GRS resource status values
Value Meaning
EXCLUSIVE Exclusive status held
MCEXC Exclusive must-complete status held
MCSHR Shared must-complete status held
SHARED Shared status held
WAITEXC Awaiting exclusive status
WAITMCE Awaiting exclusive must-complete status
WAITMCS Awaiting shared must-complete status
WAITSHR Awaiting shared status
Note: When the status value begins with a ‘WAIT’, either the SVRB or the
ECB address used by GRS for notification is also presented.

Paragraphs that discuss a TCB may also contain a line beginning with a
MASID caption, showing the MASID ENQ ASID and TCB address for those
164 z/OS MVS IPCS Commands
 GRSDATA subcommand

resource requests using the MASID option. Similarly, paragraphs that discuss
a TCB may also contain a line beginning with a SASID caption when a server
address space has performed an ENQ or RESERVE operation on behalf of a
requester address space.

GTFTRACE subcommand — format GTF trace records

Use the GTFTRACE subcommand to format generalized trace facility (GTF) records
contained in a dump or in a trace data set. The GTF records must be in a single
source. If you have multiple GTF trace data sets, use the COPYTRC subcommand
to combine the trace records into one data set.
v Syntax

{GTFTRACE } [ ASCB(ascb-address-list) ]
{GTF } [ ASID(asidlist) ]
[ JOBNAME(joblist) | JOBLIST(joblist) ]
[ BEGINFIRST ]
[ BEGINOLD ]
[ CICS((text)) ]
[ CPU(cpu-address) ]
[ DEBUG ]
[ EOF ]
[ EXIT(pgmname) ]
[ START(ddd,hh.mm.ss) ]
[ STOP(ddd,hh.mm.ss) ]
[ STARTLOC(ddd,hh.mm.ss) ]
[ STOPLOC(ddd,hh.mm.ss) ]
[ SYSNAME(name-list) ]

-------------- Data Selection Parameters -------------------

[ CCW[(record-type)] ]
[ DSP ]
[ EXT ]
[ IO[(device-number-list)] ]
[ SSCH[(device-number-list)] ]
[ IOSSCH|SSCHIO[(device-number-list)] ]
[ IOX[(device-number-list)] ]
[ PCIE[(pfid-list)] ]
[ PI[(codelist)] ]
[ RNIO ]
[ RR ]
[ SLIP ]
[ SRM ]
[ SVC[(svclist) ] ]
[ SYS ]
[ USR {(symbol-list) } ]
[ {(idvalue-list) } ]
[ {(idrange-list) } ]
[ {(ALL) } ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
[ FLAG(severity) ]

Chapter 5. IPCS subcommands 165

GTFTRACE subcommand

Note: The PATH keyword is only intended to refer to a dump data set, not an
external trace.
v Parameters
If you need more than one physical line to enter the GTFTRACE subcommand,
continue it with a plus or minus sign as you do with any TSO/E command.
Command ===>GTFTRACE DD(SYSTRACE) IO(D34,D0C,ED8,+
FFF,2A0,2E4)
Standard TSO/E continuation techniques apply to all GTFTRACE subcommand
parameters.
ASCB(ascb-address-list)
Specifies ASCB addresses corresponding to the trace entries and user records
you want to format. Specify the ASCB address list as one or more 1- to
8-digit hexadecimal addresses, separated by commas.
ASID(asidlist)
Specifies a list of ASIDs for the address spaces for which trace entries and
user records are to be formatted. The asidlist can be a single ASID or a list of
noncontiguous ASIDs. When you specify a list, separate the list members
with commas. The ASID can be 1 through 65535.

Note: ASID is ignored when processing data from a trace data set.
JOBNAME(joblist) or JOBLIST(joblist)
Specifies one or more job names for which trace entries and user records are
formatted. Each job name can be up to 8 characters long. Job names
specified for SYSMDUMP data sets are ignored. SYSMDUMPS do not
contain the job name field.
Both generic and specific job names may be used in the joblist. A generic job
name may use the following wildcards:
– Asterisks to denote any string of valid characters, including no characters.
You may use one or more asterisks in any position.
– Percent signs to denote one valid character. Use one percent sign for each
character position.
For example, given the following job names:
MPA MPPA MPP1A MAP1A
M00PA MPP01A MPPABA MPPABCA
– MPP*A will match these job names: MPPA, MPP1A, MPPABA, MPPABCA
– M*P*A will match all job names in the list.
– MPP%%A will match these job names: MPP01A, MPPABA

Note: *MASTER* represents the master address space.

BEGINFIRST
Requests that formatting start with the first block of records in a trace data
set, regardless of TAPE/DASD or wrapping. BEGINFIRST is the default for
tape data sets; it is ignored for dumps. BEGF may be used as the short form
of this parameter.
BEGINOLD
Requests that formatting start with the oldest block of records in a trace data
set. The command determines the oldest time stamp record, regardless of
where the data set resides (TAPE/DASD). GTFTRACE creates the symbol
GTFWRAP to save the number of the oldest block across IPCS sessions.

166 z/OS MVS IPCS Commands

 GTFTRACE subcommand

However, the GTFWRAP symbol will not be created if both of the following
are true:
– The trace data set has been placed in IPCS fast path access mode (that is,
normal initialization of the trace data set has been bypassed).
– The trace data set is wrapped (the first trace record in the data set is not
the oldest trace record in the data set).
BEGINOLD is the default for DASD data sets; it is ignored for dumps.
BEGO may be used as the short form of this parameter.
CICS((text))
Specifies that the entered text be placed in a buffer, preceded by a
fullword-length field, and that the address of this text buffer be placed in the
work area list entry corresponding to the format identification disk (X'EF')
assigned to the Customer Information Control System (CICS®) This
processing makes the text string addressable by the CICS formatting
appendage, AMDUSREF.
CPU(cpu-address)
Specifies that events occurring on the central processor whose physical
identifier is cpu-address be formatted. The cpu-address can be any CPU
address supported by the current release. And you can use decimal,
hexadecimal (X'xxx...'), or binary (B'bbb...') notations to specify the
cpu-address.
CPU filtering is only effective with IO-related trace records. Records which
are subject to CPU filtering are SSCH, CSCH, HSCH, MSCH, RSCH, IO,
EOS, PCI, and CCW.
DEBUG
Specifies the display of the internal control table after parsing the parameters
entered on the GTFTRACE subcommand.
EOF
Specifies that the exit routine identified by the EXIT parameter is to receive
control on all GTFTRACE normal and abnormal ending conditions.
EXIT(pgmname)
Specifies the program name of a user-written exit routine that inspects all
trace data records. When the EOF parameter is specified, IPCS also passes
control to this routine at the logical end of the trace data. If the routine does
not exist or if IPCS cannot successfully load it, GTFTRACE processing ends
and IPCS processes the next subcommand.
START(ddd,hh.mm.ss) or STARTLOC(ddd,hh.mm.ss)
STOP(ddd,hh.mm.ss) or STOPLOC(ddd,hh.mm.ss)
Specifies that the blocks for processing lie between times. The times for
START and STOP are GMT; STARTLOC and STOPLOC indicate local time.
IPCS formats only those records that you request with trace data selection
parameters. When you do not specify START or STARTLOC, GTFTRACE
starts at the beginning of the data set, or at the first block in a dump. When
you do not specify STOP or STOPLOC, GTFTRACE completes processing
after it reads the end of the data set, or the last block in a dump. The record
timestamps are not used, and can have times greater than the block
timestamp. ‘ddd’ is Julian day, and ‘hh.mm.ss’ is the hours, minutes and
seconds as set in the TOD clock.

Note: You do not need to specify leading zeros.

Chapter 5. IPCS subcommands 167

GTFTRACE subcommand

SYSNAME(name-list)
Filters the GTF data merged from several data sets. When SYSNAME is
specified, the GTF data will be formatted only if its system name agrees
with one of the values in the name-list. SYSNAME will accept up to 16
names in the name-list.
v Data Selection Parameters
Use these parameters to limit the kinds of trace records processed. For these
parameters, the phrase “base record” means the first record of the many records
that form one logical record. If you omit data selection parameters, the default is
SYS.
CCW(record-type)
Requests that channel program trace records be formatted. To format CCW
trace records, IPCS formats either SSCH base records or I/O base records, or
both. For record-type, you can specify:
I Requests formatting of all the CCW trace records for I/O events, and, if
present, program-controlled interrupt (PCI) events. IPCS formats I/O
base records even if you do not specify the IO parameter. When you
specify both the IO parameter and CCW(I), IPCS formats only the CCW
trace records for events on the devices identified on the IO parameter.
S Requests formatting of all CCW trace records for start subchannel and
resume subchannel operations. IPCS formats SSCH base records even if
you do not specify the SSCH parameter. When you specify both the
SSCH parameter and CCW(S), IPCS formats only the CCW trace records
for events on the devices identified by the SSCH parameter.
SI Requests formatting of all CCW, I/O, start subchannel, and resume
subchannel trace records in the specified data set. IPCS formats SSCH
and I/O base records even if you do not specify the SSCH and IO
parameters. When you specify the SSCH and IO parameters, with either
CCW or CCW(SI), IPCS formats only the CCW trace records for events
on the devices identified by the SSCH and IO parameters.
DSP
Requests that IPCS format all dispatching event trace records.
EXT
Requests that IPCS format all trace records for external interruptions.
IO[(device-number-list)]
SSCH[(device-number-list)]
IOSSCH|SSCHIO[(device-number-list)]
Request formatting of I/O trace records, SSCH trace records, or both.
Supplied alone, the IO parameter specifies formatting of IO, PCI, HSCH,
CSCH, and MSCH trace records. The SSCH parameter tells IPCS to format
start and resume subchannel trace records. SSCHIO and IOSSCH are
synonymous. Either one requests formatting of both I/O and start and
resume subchannel records.
The device-number-list can contain from 1 to 50 device numbers, for which
you want either or both types of trace records formatted. IPCS formats trace
records only for the specified devices. If you do not specify any device
numbers, IPCS formats trace records for all devices.
IOX(device-number-list)
Requests formatting of I/O Summary trace records. The device-number-list
can contain from 1 to 50 three-digit device numbers, for which you want

168 z/OS MVS IPCS Commands

 GTFTRACE subcommand

records formatted. IPCS formats trace records only for the specified devices.
If you do not specify any device numbers, IPCS formats trace records for all
devices.
PCIE[(pfid-list)]
Requests formatting of PCIE-related events. The pfid-list specifies the PCIE
function identifiers (PFIDs) for which records are to be formatted. PFIDs are
1 to 8 hexadecimal digits. If you do not specify any PFIDs, IPCS formats the
trace records for all of the PFIDs found in the trace.
PI[(codelist)]
Specifies formatting of program interruption trace records, for the
interruption codes in codelist. codelist can contain 0 to 255 decimal
interruption codes of one to three digits each. If you do not specify any
codes, IPCS formats trace records for all the program interruption codes
found in the dump.
RNIO
Requests formatting of all the records for VTAM remote network activities.
RR Requests formatting of all recovery routine event records.
SLIP
Requests formatting of all SLIP trace records.
SRM
Requests formatting of system resources manager (SRM) event records.
SVC[(svclist)]
Requests display of the formatted trace records associated with the numbers
specified in svclist. The svclist can contain 0 to 255 decimal SVC numbers of
1 to 3 digits each.
SYS
Requests formatting of all system event trace records. SYS, the default,
formats all the GTF trace records that were recorded in a dump or trace data
set except for USR records.
USR ({symbol-list | idvalue-list | idrange-list | ALL})
Requests formatting of user/subsystem trace records created by the
GTRACE macro. The symbol-list or idvalue-list denote trace records belonging
to one component or subsystem. GTRACE data consists of user event trace
records or IBM subsystem event records from these subsystems:
– OPEN/CLOSE/EOV
– SAM/PAM/DAM
– VTAMVSAM
The symbol-list contains 1 through 20 symbols, with multiple symbols
separated by commas. When ID values are assigned to a subsystem, the
component defines the symbol that is used. The following table shows valid
symbols and their corresponding ids and subsystems:

Symbol ID Subsystem
AM01 FF5 VSAM
APTH FE2 TSO/VTAM TGET/TPUT trace
APTR FE3 VTAM reserved
CL01 FF1 VTAM buffer contents trace (USER)
CL02 FF0 VTAM SMS (buffer use) trace

Chapter 5. IPCS subcommands 169

GTFTRACE subcommand

Symbol ID Subsystem
DB2V F5F DB2/VSAM transparency
DMA1 FFF OPEN/CLOSE/EOV
FSI4 F54 FSI trace
FSI5 F55 FSI trace
FSI6 F56 FSI trace
FSI7 F57 FSI trace
FSI8 F58 FSI trace
FSI9 F59 FSI trace
FSIA F5A FSI trace
FSIB F5B FSI trace
FSIC F5C FSI trace
FSID F5D FSI trace
INT1 FE1 VTAM internal table
OSIC F53 OSI Communication Subsystem
SPD1 FF3 SAM/PAM/DAM
SPD2 FF4 SAM/PAM/DAM
SPD3 FF6 SAM/PAM/DAM
SPD4 FF7 SAM/PAM/DAM
SPD5 FF8 SAM/PAM/DAM
SPD6 FF9 SAM/PAM/DAM
SPD7 FFA SAM/PAM/DAM
SPD8 FFB SAM/PAM/DAM
SPD9 FFC SAM/PAM/DAM
SPDA FFD SAM/PAM/DAM
SPDB FFE SAM/PAM/DAM
TPIO FEF VTAM buffer contents trace

The idvalue-list contains 1 through 20 values, which are 3-digit hexadecimal

identifiers assigned to a subsystem. If more than one value is specified,
separate them with commas. The following table shows valid identifiers and
their corresponding subsystems:

ID Issued by
000-3FF GTF user program
400-5F0 Reserved for IBM Use
5F1 PVM
5F2-5F3 Reserved for IBM Use
5F4-5F5 NetView® System Monitor
5F6-F47 Reserved for IBM Use
F48 IOS
F49 BDT
F4F OSAM

170 z/OS MVS IPCS Commands

 GTFTRACE subcommand

ID Issued by
F50-F52 Reserved for IBM Use
F53 OSI Communications Subsystem
F54-F5D FSI
F5E Reserved for IBM Use
F5F DB2®
F60 JES3
F61 VSAM Buffer Manager
F62 Dynamic output SVC installation exit
F63 Converter/Interpreter installation exit
F64 APPC/VM VTAM Support (AVS)
F66-F6A VTAM
F6C CICS
FAA VTAM VM/SNA Console Services (VSCS)
FAB-FAE

The idrange-list contains 1 through 20 ID value ranges, which are the first
and last 3-digit values of the id range, separated by a hyphen. If more than
one range is specified, separate them with a comma.
ALL requests formatting of all user and subsystem trace records. ALL
overrides any idvalue, idrange, or symbol specification.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the GTFTRACE subcommand.
v Example: For examples of GTFTRACE output, see the GTF trace in z/OS MVS
Diagnosis: Tools and Service Aids.

HELP subcommand — get information about subcommands

Use the HELP subcommand to obtain information about the function, syntax, and
parameters of the IPCS subcommands. If you enter HELP with no parameters, all
the IPCS subcommands are listed.

Note: In the IPCS dialog, use only the abbreviated form, H, of this subcommand.
See the z/OS MVS IPCS User's Guide for more information.
v Syntax

{ HELP|H } [subcommand [ALL | FUNCTION | SYNTAX| &cont;

OPERANDS[(list)]] ]

v Parameters
subcommand
Specifies the name of the IPCS subcommand about which you want
information. If you omit this parameter, the subcommand displays
information about all IPCS subcommands.

Chapter 5. IPCS subcommands 171

HELP Subcommand

ALL
Specifies that you want all the information available about the specified
subcommand.
If you omit the FUNCTION, SYNTAX, and OPERANDS parameters, ALL
provides information about all IPCS subcommands.
FUNCTION
Specifies that you want to know more about the purpose and operation of
the specified subcommand.
SYNTAX
Specifies that you want to know more about the syntax of the specified
subcommand.
OPERANDS[(list)]
Specifies that you want to know more about the parameters of the specified
subcommand. If you specify a list of parameters, HELP displays information
about those parameters. If you specify no parameters, HELP displays
information about all the parameters of the specified subcommand.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the HELP subcommand.

INTEGER subcommand — format or list a number

Use the INTEGER subcommand to:
v Convert a number from decimal to hexadecimal representation or vice versa.
v Format a value having a specified length for CLIST, REXX, or ISPF dialog usage.
The formatted values may be used to compose tabular reports or to construct
symbols such as those generated by the RUNCHAIN subcommand.
v Syntax

INTEGER integer

[ CLIST (STORAGE(storage)) ]
[ DIALOG (STORAGE(storage)) ]
[ REXX (STORAGE(storage)) ]
[ LIST ]
[ CHARACTER ]
[ OFFSET [(precision)] ]
[ POINTER [(precision)] ]
[ SIGNED [(precision)] ]
[ UNSIGNED [(precision)] ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ LENGTH(length) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
integer
Specifies the integer to be converted. The integer must be signed and
between -231 and 231-1. The notation of the integer can be:
– Decimal: [+|-]nnn

172 z/OS MVS IPCS Commands

 INTEGER subcommand

– Hexadecimal: X‘[+|-]xxx’
– Binary: B‘[+|-]bbb’
CLIST(STORAGE(storage))
DIALOG(STORAGE(storage))
REXX(STORAGE(storage))
Specifies where IPCS is to store the value of the converted integer.
CLIST directs that the value be stored in CLIST variable storage.
DIALOG directs that the value be stored in ISPF function pool dialog
variable storage.
REXX directs that the value be stored in REXX variable storage.
LIST
Specifies that the value is to be displayed. If CLIST, DIALOG, or REXX is
omitted, the default is LIST.
CHARACTER
OFFSET [(precision)]
POINTER [(precision)]
SIGNED [(precision)]
UNSIGNED [(precision)]
Specifies the notation into which the integer is to be converted.
CHARACTER specifies that the 4 bytes of a signed binary fullword
containing a number integer are to be formatted as 4 EBCDIC characters.
Characters present on neither the 1403 TN print chain nor the 3211 T11 print
train are to be translated to EBCDIC periods.
OFFSET specifies that the number integer is to be formatted using a leading
plus or minus sign plus hexadecimal digits.
POINTER specifies that the 4 bytes of a signed binary fullword containing a
number integer are to be formatted as an unsigned binary fullword using
hexadecimal digits.
SIGNED specifies that the number integer is to be formatted using a leading
blank or minus sign plus decimal digits.
UNSIGNED specifies that the 4 bytes of a signed binary fullword containing
a number integer are to be formatted as an unsigned binary fullword using
decimal digits.
precision is the number of digits in the formatted result. If no precision is
specified, all leading zero digits are removed from the result.
LENGTH(length)
Specifies the number of characters for the formatted result. Leading blanks
are supplied to attain the specified length. If length is not specified, no
leading blanks are supplied.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the INTEGER subcommand.

IOSCHECK subcommand — format I/O supervisor data

Use the IOSCHECK subcommand to format the contents of specific I/O supervisor
(IOS) control blocks and related diagnostic information.

Chapter 5. IPCS subcommands 173

IOSCHECK subcommand

You request diagnostic information about a captured unit control block (UCB) with
the CAPTURE parameter on IOSCHECK. IOSCHECK produces different diagnostic
reports for captured UCBs with the address space selection parameter(s) (ALL,
CURRENT, ERROR, TCBERROR, ASIDLIST, and JOBLIST).
v Address Space Selection Parameters
– ALL processes all address spaces.
– CURRENT processes active address spaces of the dump.
– ERROR processes any address space with an error indicator or containing a
task with an error indicator.
– TCBERROR processes any address space containing a task with an error
indicator.
– ASIDLIST processes address spaces associated with ASID(s).
– JOBLIST or JOBNAME processes address spaces associated with job names.
If you do not specify an address space selection parameter, CURRENT is the
default. Address space selection parameters only apply with the CAPTURE
parameter.
v Syntax

{ IOSCHECK } [ ACTVUCBS ]
{ IOSK }
[ ALLUCBS ]
[ CAPTURE ]
[ CHAR(device-number-list) ]
[ CHPR ]
[ COMM(device-number-list) ]
[ CTC(device-number-list) ]
[ DASD(device-number-list) ]
[ DISP(device-number-list) ]
[ EXCEPTION ]
[ HOTIO ]
[ MIH ]
[ RECOVERY ]
[ SMGRBLKS ]
[ TAPE(device-number-list) ]
[ UCB(device-number-list) ]
[ UREC(device-number-list) ]
[ VALIDATE ]

-------- Address Space Selection Parameters ----------------

[ ALL ]
[ CURRENT ]
[ ERROR ]
[ TCBERROR ]
[ ASIDLIST(asidlist) ]
[ JOBLIST(joblist)|JOBNAME(joblist) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters

174 z/OS MVS IPCS Commands

 IOSCHECK subcommand

In the parameters, device-number-list is one of the following:

– A single hexadecimal device number of up to four digits.
- Parentheses are accepted but are not required.
- Leading zero digits are accepted but are not required.
– A range of device numbers defined by the lowest and highest device numbers
separated by a colon.
- Parentheses are accepted but are not required.
- Leading zeros are accepted but are not required.
- The second device number must be equal to or greater than the first, for
example, 193:198.
– A list containing either single device numbers or ranges of device numbers.
Parentheses are required. In the list, separate list members with blanks,
commas, or horizontal tabulation (X'05') characters. The separators are
permitted, but not required, between the left parenthesis and the first member
and between the last member and the right parenthesis.
v Report Type Parameters
Use these parameters to select the type of report.
ACTVUCBS
Validates I/O control blocks, formats active UCBs and these associated
control blocks:
– IOQ
– IOSB
– SRB
– EWA
– CRWQ
– SRWQ
ALLUCBS
Validates the I/O control blocks and formats all UCBs, along with these
associated control blocks:
– IOQ
– IOSB
– SRB
– EWA
– CRWQ
– SRWQ
CAPTURE
Formats the captured UCB pages in an address space (based on the address
space selection parameters) along with these associated control blocks:
– IOQ
– IOSB
– SRB
– EWA
– CRWQ
– SRWQ
An application program can access an above 16 megabyte UCB with a 24-bit
address through a view of the UCB captured in the program's address space.

Chapter 5. IPCS subcommands 175

IOSCHECK subcommand

The report also displays the captured UCB pages in common storage, if any
exist. The report gives you the address space identifier (ASID) and
information about each captured page. The report provides the following
information for each captured page:
– Actual page address
– Captured page address
– Captured UCB count
The captured UCB count is the number of captures of UCBs, these can be
captures of the same UCB.
CHAR(device-number-list)
Requests formatting of selected channel-to-channel attention routine (CHAR)
UCBs.
CHPR
Requests formatting of the installation channel path table (ICHPT), the
channel recovery block (CHRB), and the global channel report word queue
(CRWQ) elements.
COMM(device-number-list)
Requests formatting of selected communication (COMM) UCBs.
CTC(device-number-list)
Requests formatting of selected channel-to-channel (CTC) UCBs.
DASD(device-number-list)
Requests formatting of selected direct access storage device (DASD) UCBs.
DISP(device-number-list)
Requests formatting of any dispatcher (DISP) UCBs that you have selected
(using device-number-list).
EXCEPTION
Specifies that IPCS check the validity of the IOS control blocks and print
diagnostic error messages for blocks that are not valid. This parameter
formats these control blocks:
– I/O communications area (IOCOM)
– I/O communications writeable area (IOCW)
– IOS level definitions
– I/O work area (IOWA) for each processor, and the IOS module work
areas for each IOWA
– I/O prevention table (IOPT), if accessible
EXCEPTION is the default.
For additional information about IOS level definitions see z/OS MVS
Diagnosis: Reference.
HOTIO
Requests formatting of the hot I/O detection table (HIDT) and the associated
status collector data areas (SCDs).
MIH
Requests formatting of the missing interrupt handler work area (MIHA) and
the associated time interval control blocks (TICBs).
RECOVERY
Requests formatting of the control blocks for the HOTIO, MIH, and CHPR
parameters.

176 z/OS MVS IPCS Commands

 IOSCHECK subcommand

SMGRBLKS
Requests formatting of entries in the IOS storage manager page table for
IOQ, RQE, and large blocks, and formatting of the queue of pages for each
entry. The string LGA will appear in the formatted output instead of LGE to
distinguish between a below the line large block and above the line large
block.
SMGR: 0188CB70
+0000 BLKID.... LGEB PGID..... LGAPOOL IOS SMGR
+0014 PGESZE... 00001000 PGFLG1... 00 PGFLG2... 00
+001A PGPOOL... 00E2 SYNCA.... 0188C1D0 BLKCNT... 000F
+0022 TBLKLN... 0100 BLKLEN... 00F8 POFSET... 0100
+0028 PTOLE.... 0002 LINKOF... 00F4 HDROF.... 00F8
+002E BIDOF.... 00F0 PGEINC... 0001000F ALLOCW... 00000076
...

PAGE: 02FCC000
+0000 RCNT..... 0000000F BLKP..... 00FCC100 FLG1..... 80
+0009 FLG2..... 00 MCNT..... 000F CHN...... 02FCB000
+0010 ID....... LGAPOOL IOS SMGR WKAR..... 00000000
+0024 EXTP..... BACK..... 00000000

LGAB at 01FCC100
+0000 00000000 C5E7D7D9 00FCBF68 00000000 | ....EXPR........
+0010 00000000 00000000 00000000 00000000 | ................
+0020 00000000 00000000 00000000 00000000 | ................
...
TAPE(device-number-list)
Requests formatting of selected TAPE UCBs and ranges.
UCB(device-number-list)
Requests formatting of selected unit control blocks (UCBs).
UREC(device-number-list)
Requests formatting of selected unit record (UREC) UCBs.
VALIDATE
Requests validity checking of the following IOS control blocks:
– Device class queue chain (DCQ)
– Unit control blocks (UCB) queued off the DCQ
– I/O request blocks (IOQ) chained off the UCB and the associated IOQ
chain
– I/O supervisor block (IOSB) pointed to from each IOQ
– Service request block (SRB) pointed to from each IOSB
– IOS error recovery procedure (ERP) work area (EWA) pointed to from the
IOSB
When IOS detects a control block that is not valid, IOS formats the control
block, and prints a diagnostic error message.

Note: For SVC dumps, not all the data pertaining to IOSCHECK is saved at
the time of error. As a consequence, many control blocks may be reused
before the data is dumped. Informational messages indicate that the data is
not from the time of error. For example, the following message indicates that
the IOQ has been reused:
IOS10107I IOQ AT xxxxxxxx does not point to UCB at yyyyyyyy
v Address Space Selection Parameters
Use these parameters to obtain captured page data from particular address
spaces, which you specify by their ASIDs. These parameters only apply with the

Chapter 5. IPCS subcommands 177

IOSCHECK subcommand

CAPTURE parameter. If you specify CAPTURE but omit these parameters, the
default is CURRENT. For more information, see the select ASID service in z/OS
MVS IPCS Customization.
ALL
Specifies processing of captured pages for all address spaces in the system at
the time the dump is generated.
CURRENT
Specifies processing of captured pages for each address space that is active
(for example, dispatched on some central processor) when the dump is
generated.
ERROR
Specifies processing of captured pages for any address space with an MVS
error indicator or containing a task with an error indicator.
TCBERROR
Specifies processing of captured pages for any address space containing a
task with an error indicator. Blocks for address spaces with an error
indicator are not processed.
ASIDLIST(asidlist)
Specifies a list of ASIDs for the address spaces to be in the report.
The asidlist can be a single ASID, a range of ASIDs, or a list of
noncontiguous ASIDs. When you specify a range, separate the first and last
ASIDs in the range with a colon. When you specify a list, separate the list
members with commas.
The ASID can be 1 through 65535. An ASID can be expressed using the
notation X'nnn', F'nnn', or B'nnn'. An unqualified number is assumed to be
fixed.
This subcommand does not process summary dump records (ASID X'FFFA').
JOBLIST(joblist) or JOBNAME(joblist)
Specifies a list of job names whose associated address spaces are to be in the
report. Use commas to separate the job names in the list; do not enclose job
names in apostrophes; and do not specify a range of job names.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the IOSCHECK subcommand.
v Example 1: Display IOS-related control blocks.
– Action
COMMAND ===> IOSCHECK UCB(2D0,2E0,410:440,620)
– Result
This example formats UCBs for 3 device numbers and one range. For an
example of IOSCHECK output, see the IOS component in z/OS MVS
Diagnosis: Reference.
v Example 2: Display captured UCB information for address spaces that are active.
– Action
COMMAND ===> IOSCHECK CAPTURE
– Result
This example formats the captured UCB information for any address space
that is active. The output looks similar to the following for each address
space:

178 z/OS MVS IPCS Commands

 IOSCHECK subcommand

* * * ADDRESS SPACE CAPTURE DATA * * *

ASID 000F

ACTUAL CAPTURE CAPTURE

PAGE ADDRESS PAGE ADDRESS UCB COUNT
------------ ------------ ------------

01D0E000 006F8000 00000005

01D0F000 006F7000 00000003

Two pages were captured in address space 000F. The first page had five
captures of UCBs and the second had three.

IPCSDATA subcommand — request a report about IPCS activity

Use the IPCSDATA subcommand to generate reports about data maintained by
IPCS in a dump:
v IPCS sessions may have been active in various ASIDs dumped. If not and
IPCSDATA is asked to process an ASID, a very brief report will be generated
saying:
No IPCS session data was found in ASID(X’xxxx’)

If you do not specify an address space selection parameter, CURRENT is the

default.
v Most dumps include the ECSA storage in which BLSJPRMI stores tables that
identify the sysplex dump directory name and enumerate materials available for
use during SNAP/ABDUMP formatting. Ask IPCSDATA to process COMMON
storage to format this data.

Address space selection and data selection parameters limit the scope and extent of
the information that appears in the report.
v Syntax

Chapter 5. IPCS subcommands 179

IPCSDATA subcommand

IPCSDATA
------- Data Selection Parameters -----------------------
[ COMMON | NOCOMMON ]
[ PRIVATE | NOPRIVATE ]
[ PARMLIB | NOPARMLIB ]
[ OPEN | NOOPEN ]
[ TASK | NOTASK ]

------- Address Space Selection Parameters --------------

[ ALL ]
[ ASIDLIST(asidlist) ]
[ CURRENT ]
[ ERROR ]
[ JOBLIST(joblist) | JOBNAME(joblist) ]
[ TCBERROR ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Data selection parameters

COMMON or NOCOMMON
Requests or suppresses a report pertaining to common storage data
maintained to support SNAP and ABDUMP formatting in the dumped
system.
PRIVATE or NOPRIVATE
Requests or suppresses reports pertaining to IPCS sessions, if any, in the
address spaces selected.
PARMLIB or NOPARMLIB
Requests or suppresses reports showing information obtained from parmlib
members.
OPEN or NOOPEN
Requests or suppresses reports pertaining to open data sets.

Note: Dump directory performance statistics are only produced by

IPCSDATA when it is run against ACTIVE storage. Statistics are acquired
through the VSAM SHOWCB ACB programming interface, and no
equivalent interface is supported for ACB images retrieved from a dump.
TASK or NOTASK
Requests or suppresses reports pertaining to tasks associated with IPCS
session activity.
v Address Space Selection Parameters
Request address spaces for which IPCSDATA private storage reports should be
produced. See “SELECT subcommand — generate address space storage map
entries” on page 259.
v SETDEF-Defined Parameters

180 z/OS MVS IPCS Commands

 IPCSDATA subcommand

Overrides defaults established through the SETDEF subcommand or the Defaults

option of the IPCS dialog. See “SETDEF subcommand — set defaults” on page
262.
v Diagnosis — Sample IPCSDATA Reports
– Example 1: Sample IPCSDATA Common Storage Report. The following
sample includes parmlib information. Use of the NOPARMLIB option
eliminates all lines of the report following the one beginning “BLSQXBT”.
Common storage report

BLSQXBT at 0D35CCC0 LENGTH(4927)

SYSDDIR ’MVSSPT.SYSPLEX.DMPDIR’

DATA STRUCTURE(ALE) MODEL(IEAALEP)

DATA STRUCTURE(ASCB) FIND(BLSSASCB) MODEL(IEAASCBP) SCAN(BLSVASCB)
DATA STRUCTURE(ASSB) MODEL(IEAASSBP) SCAN(BLSVASSB)
DATA STRUCTURE(AST) FIND(BLSSASTE) GROUP(ASTE) MODEL(IEAASTEP) SCAN(+
BLSVASTE)
DATA STRUCTURE(ASTE) FIND(BLSSASTE) MODEL(IEAASTEP) SCAN(BLSVASTE)
DATA STRUCTURE(ASXB) FIND(BLSSASXB) MODEL(IEAASXBP) SCAN(BLSVASXB)

DATA STRUCTURE(CDE) FIND(BLSSCDE) MODEL(CSVFMCDE) SCAN(BLSVCDE)

DATA STRUCTURE(CDEMAJOR) FIND(BLSSCDE) GROUP(CDE) MODEL(CSVFMCDE) SCAN(+
BLSVCDE)
DATA STRUCTURE(CDEMINOR) FIND(BLSSCDE) GROUP(CDE) MODEL(CSVFMCDE) SCAN(+
BLSVCDE)
DATA STRUCTURE(CVT) FIND(BLSSCVT) MODEL(IEACVTP) SCAN(BLSVCVT)

DATA STRUCTURE(IRB) FORMAT(IEARBF,JBB2125) GROUP(RB) SCAN(BLSVRB)

DATA STRUCTURE(JSAB) FIND(IAZJSABF) MODEL(IAZJSABM) SCAN(IAZJSABV)

DATA STRUCTURE(LLE) MODEL(CSVFMLLE)

DATA STRUCTURE(LPDE) FIND(BLSSCDE) GROUP(CDE) MODEL(CSVFMCDE) SCAN(+
BLSVCDE)
DATA STRUCTURE(LPDEFINAL) FIND(BLSSCDE) GROUP(CDE) MODEL(CSVFMCDE) SCAN(+
BLSVCDE)
DATA STRUCTURE(LPDEMAJOR) FIND(BLSSCDE) GROUP(CDE) MODEL(CSVFMCDE) SCAN(+
BLSVCDE)
DATA STRUCTURE(LPDEMINOR) FIND(BLSSCDE) GROUP(CDE) MODEL(CSVFMCDE) SCAN(+
BLSVCDE)
DATA STRUCTURE(LPDENULL) FIND(BLSSCDE) GROUP(CDE) MODEL(CSVFMCDE) SCAN(+
BLSVCDE)
DATA STRUCTURE(LS) FORMAT(IEAVD3A)
DATA STRUCTURE(LSE) MODEL(IEALSEP)
DATA STRUCTURE(LSEH) MODEL(IEALSEHP)
DATA STRUCTURE(LSET) MODEL(IEALSETP)
DATA STRUCTURE(LSSA) MODEL(IEALSSAP)
DATA STRUCTURE(LSSD) MODEL(IEALSSDP) SCAN(IEACLSSD)
DATA STRUCTURE(LSSG) MODEL(IEALSSGP) SCAN(IEACLSSG)
DATA STRUCTURE(PRB) FORMAT(IEARBF,JBB2125) GROUP(RB) SCAN(BLSVRB)
DATA STRUCTURE(PSW) FIND(BLSSPSW) FORMAT(BLSQPSWF,JBB2125)

DATA STRUCTURE(RB) FORMAT(IEARBF,JBB2125) SCAN(BLSVRB)

DATA STRUCTURE(REGACC) FIND(BLSSREGA) MODEL(BLSBREGA)
DATA STRUCTURE(REGCTL) FIND(BLSSREGC) MODEL(BLSBREGC)
DATA STRUCTURE(REGFLT) FIND(BLSSREGF) MODEL(BLSBREGF)
DATA STRUCTURE(REGGEN) FIND(BLSSREGG) MODEL(BLSBREGG)
DATA STRUCTURE(REGS) MODEL(BLSBREGS)
DATA STRUCTURE(REGSAVIM) MODEL(BLSBREGI)
DATA STRUCTURE(RTM2WA) MODEL(IEAVTRP2) SCAN(IEAVTRV2)
DATA STRUCTURE(SCB) FORMAT(IEAVTRF4,JBB2125) SCAN(IEAVTRVS)
DATA STRUCTURE(SDWA) MODEL(IEAMSDWA)
DATA STRUCTURE(SIRB) FORMAT(IEARBF,JBB2125) GROUP(RB) SCAN(BLSVRB)
DATA STRUCTURE(SSAT) MODEL(IEASSATP)
DATA STRUCTURE(STCB) MODEL(IEASTCBP) SCAN(BLSVSTCB)
DATA STRUCTURE(SVRB) FORMAT(IEARBF,JBB2125) GROUP(RB) SCAN(BLSVRB)

DATA STRUCTURE(TCB) FIND(BLSSTCB) MODEL(IEATCBP) SCAN(BLSVTCB)

DATA STRUCTURE(TIOT) FORMAT(BLSQTIOF)
DATA STRUCTURE(TIRB) FORMAT(IEARBF,JBB2125) GROUP(RB) SCAN(BLSVRB)

Chapter 5. IPCS subcommands 181

IPCSDATA subcommand

DATA STRUCTURE(UCB) FIND(IOSVUCBS) FORMAT(IOSVFMTU,JBB2125) SCAN(IOSVUCBV)

DATA STRUCTURE(UCBCTC) FIND(IOSVUCBS) FORMAT(IOSVFMTU,JBB2125) GROUP(+
UCB) SCAN(IOSVUCBV)
DATA STRUCTURE(UCBDA) FIND(IOSVUCBS) FORMAT(IOSVFMTU,JBB2125) GROUP(UCB) +
SCAN(IOSVUCBV)
DATA STRUCTURE(UCBGFX) FIND(IOSVUCBS) FORMAT(IOSVFMTU,JBB2125) GROUP(+
UCB) SCAN(IOSVUCBV)
DATA STRUCTURE(UCBTAPE) FIND(IOSVUCBS) FORMAT(IOSVFMTU,JBB2125) GROUP(UCB+
) SCAN(IOSVUCBV)
DATA STRUCTURE(UCBTP) FIND(IOSVUCBS) FORMAT(IOSVFMTU,JBB2125) GROUP(UCB) +
SCAN(IOSVUCBV)
DATA STRUCTURE(UCBUR) FIND(IOSVUCBS) FORMAT(IOSVFMTU,JBB2125) GROUP(UCB) +
SCAN(IOSVUCBV)
DATA STRUCTURE(UCB3270) FIND(IOSVUCBS) FORMAT(IOSVFMTU,JBB2125) GROUP(UCB+
) SCAN(IOSVUCBV)

DATA STRUCTURE(VF) FORMAT(IEAVSSA2)

DATA STRUCTURE(XSB) MODEL(IEAXSBP)

DATA STRUCTURE(XTLST) FIND(BLSSXTLS) MODEL(CSVFMXTL) SCAN(BLSVXTLS)
– Example 2: Sample IPCSDATA Private Storage Report. The following sample
includes parmlib, open data set and task information.
- Use of the NOPARMLIB option eliminates all lines of the report starting
with the line beginning “SYSDDIR” and ending with the line beginning
“SYMBOL PREFIX(Z)”.
- Use of the NOOPEN option eliminates the paragraphs starting with lines
beginning “Dump directory” and “BLSRZZ6 at”.
The lines in the “Dump directory” paragraph starting with the line
beginning “NLOGR” only appear when IPCSDATA is run against ACTIVE
storage. Most of these statistics are also maintained by VSAM in the catalog
and can be formatted by LISTCAT. SHRPOOL, BFRFND and BUFRDS are
accumulated within a single session and can only be obtained through
IPCSDATA against ACTIVE storage.
- Use of the NOTASK option eliminates the report lines starting with the line
beginning “Master BLSUZZ2”.
ASID(X’0305’), JOBNAME(RLW)

BLSUZZ1 at 000388B0

Dump directory BLSUZZ4 at 00050E00

FILE(IPCSDDIR) DSNAME(’RLW.DDIR’)
NLOGR(6135) NRETR(52452) NINSR(13209) NUPDR(253) NDELR(19792)
CINV(22528) NCIS(208) NSSS(6) SHRPOOL(15)
BFRFND(39103) BUFRDS(7) NEXCP(4744)

BLSQXBT at 0DAE20C0 LENGTH(61245)

SYSDDIR ’MVSSPT.SYSPLEX.DMPDIR’

DATA STRUCTURE($CADDR) MODEL(HASMCADR)

DATA STRUCTURE($CKB) MODEL(HASMCKB)
DATA STRUCTURE($CKG) MODEL(HASMCKG)
.
.
.

DATA STRUCTURE(ACE) MODEL(ILRMACE)

DATA STRUCTURE(AFT) FIND(BLSSAFT) GROUP(AFTE) SCAN(BLSVAFT)
DATA STRUCTURE(AFTE) FIND(BLSSAFT) SCAN(BLSVAFT)
DATA STRUCTURE(AIA) MODEL(ILRMAIA)
DATA STRUCTURE(ALE) MODEL(IEAALEP)
DATA STRUCTURE(AMDCPMAP) MODEL(BLSBCPST)
DATA STRUCTURE(AR) FORMAT(IEAVXD02)
DATA STRUCTURE(ASCB) FIND(BLSSASCB) MODEL(IEAASCBP) SCAN(BLSVASCB)

EXIT CBSTAT(ASCB) EP(BLSAFLG)

EXIT CBSTAT(ASCB) EP(IEAVTRCA)
EXIT CBSTAT(ASCB) EP(IRARMCBS)

182 z/OS MVS IPCS Commands

 IPCSDATA subcommand

EXIT CBSTAT(ASCB) EP(BPXGMCBS)

EXIT FORMAT(ASCB) EP(IEASRBQ2)

DATA STRUCTURE(ASEI) MODEL(ASEASEIP)

DATA STRUCTURE(ASMHD) MODEL(ILRMASMH)
DATA STRUCTURE(ASMVT) FIND(ILRFASMV) MODEL(ILRMASMV)
DATA STRUCTURE(ASPCT) FORMAT(ILRPASPC)
DATA STRUCTURE(ASSB) FIND(BLSSASSB) MODEL(IEAASSBP) SCAN(BLSVASSB)

EXIT FORMAT(ASSB) EP(CSVPDLCB)

EXIT FORMAT(ASSB) EP(IAZJSABP)

DATA STRUCTURE(AST) FIND(BLSSASTE) GROUP(ASTE) MODEL(IEAASTEP) SCAN(+

BLSVASTE)
DATA STRUCTURE(ASTE) FIND(BLSSASTE) MODEL(IEAASTEP) SCAN(BLSVASTE)
DATA STRUCTURE(ASVT) FIND(BLSSASVT) SCAN(BLSVASVT)
DATA STRUCTURE(ASXB) FIND(BLSSASXB) MODEL(IEAASXBP) SCAN(BLSVASXB)

DATA STRUCTURE(BLSLNTRC) SCAN(BLSVNTRC)

DATA STRUCTURE(BLSQXBT) FIND(BLSSXBT) SCAN(BLSVXBT)
DATA STRUCTURE(BLSRARQ) SCAN(BLSVARQ)
.
DATA STRUCTURE(CACHE) MODEL(ILRMCACH)
DATA STRUCTURE(CDE) FIND(BLSSCDE) MODEL(CSVFMCDE) SCAN(BLSVCDE)
DATA STRUCTURE(CDEMAJOR) FIND(BLSSCDE) GROUP(CDE) MODEL(CSVFMCDE) SCAN(+
BLSVCDE)
DATA STRUCTURE(CDEMINOR) FIND(BLSSCDE) GROUP(CDE) MODEL(CSVFMCDE) SCAN(+
BLSVCDE)
DATA STRUCTURE(CIBAL) FIND(IATIFBAL) MODEL(IATIPBAL)
.
.
.
DATA STRUCTURE(STORESTATUS)

EXIT CBSTAT(STORESTATUS) EP(IEAVNIPW)

EXIT CBSTAT(STORESTATUS) EP(IXCFMCBS)

DATA STRUCTURE(SUPVT) MODEL(IEASVTP)

DATA STRUCTURE(SVRB) FORMAT(IEARBF,JBB2125) GROUP(RB) SCAN(BLSVRB)
DATA STRUCTURE(SVT) MODEL(IEASVTP)
DATA STRUCTURE(SVTX) MODEL(IEASVTXP) SCAN(IEACSVTX)

DATA STRUCTURE(TCB) FIND(BLSSTCB) MODEL(IEATCBP) SCAN(BLSVTCB)

EXIT CBSTAT(TCB) EP(BLSAFLG)

EXIT CBSTAT(TCB) EP(IEAVTRCA)
EXIT CBSTAT(TCB) EP(IEAVG701)
EXIT CBSTAT(TCB) EP(BPXGMCBS)

EXIT FORMAT(TCB) EP(IECDAFMT)

EXIT FORMAT(TCB) EP(IECIOFMT)
EXIT FORMAT(TCB) EP(IEAVTFMT)
EXIT FORMAT(TCB) EP(IEAVD30)
EXIT FORMAT(TCB) EP(IEAVXD01)
EXIT FORMAT(TCB) EP(IEAVSSA1)

DATA STRUCTURE(TDCM) MODEL(IEEMB904)

.
.
.
DATA STRUCTURE(XTLST) FIND(BLSSXTLS) MODEL(CSVFMXTL) SCAN(BLSVXTLS)

DATA AREA(COMMON) FIND(BLSSCOMM)

DATA AREA(CSA) FIND(BLSSCSA)

DATA AREA(DATOFFNUCLEUS) FIND(BLSSDONU)

DATA AREA(ECSA) FIND(BLSSECSA)

DATA AREA(EFLPA) FIND(BLSSEFLP)
DATA AREA(EMLPA) FIND(BLSSEMLP)
DATA AREA(ENUCLEUS) FIND(BLSSENUC)
DATA AREA(EPLPA) FIND(BLSSEPLP)
DATA AREA(ESQA) FIND(BLSSESQA)

DATA AREA(FLPA) FIND(BLSSFLPA)

Chapter 5. IPCS subcommands 183

IPCSDATA subcommand

DATA AREA(MLPA) FIND(BLSSMLPA)

DATA AREA(NUCLEUS) FIND(BLSSNUC)

DATA AREA(PLPA) FIND(BLSSPLPA)

DATA AREA(PRIVATE) FIND(BLSSPRIV)
DATA AREA(PRIVATEX) FIND(BLSSPRIX)

DATA AREA(RONUCLEUS) FIND(BLSSRONU)

DATA AREA(SQA) FIND(BLSSSQA)

EXIT ANALYZE EP(IARZANAL)

EXIT ANALYZE EP(IEAVESLX)
EXIT ANALYZE EP(IEFAB4WX)
EXIT ANALYZE EP(IOSVFMTH)
EXIT ANALYZE EP(ISGDCONT)
EXIT ANALYZE EP(IXCFMLAN)

EXIT VERB(ALCWAIT) EP(IEFAB4WX) HELP(IEFAB4WP) ABSTRACT(’Allocation wait +

summary’)
EXIT VERB(AOMDATA) EP(AOMIPCS) ABSTRACT(’AOM analysis’)
DIALOG NAME(APPCDATA) HELP(ATBH999) ABSTRACT(’APPC/MVS Data Analysis’) +
PARM(’PANEL(ATBH000)’)
DIALOG NAME(ASCHDATA) HELP(ASBH999) ABSTRACT(’APPC/MVS Scheduler Data +
Analysis’) PARM(’PANEL(ASBH000)’)
DIALOG NAME(ASMCHECK) HELP(ILRASMCH) ABSTRACT(’Auxiliary storage paging +
activity’) PARM(’PGM(BLSGSCMD) PARM(ASMCHECK TERMINAL NOPRINT)’)
EXIT VERB(ASMDATA) EP(ILRFTMAN) HELP(ILRASMDH) ABSTRACT(’ASM control +
block analysis’)
EXIT VERB(AVMDATA) EP(AVFRDFMT) HELP(AVFHELP) ABSTRACT(’AVM control +
block analysis’)

EXIT VERB(CICSDATA) EP(DFHPDX) ABSTRACT(’CICS analysis’)

EXIT VERB(CICS212) EP(DFHPD212) ABSTRACT(’CICS Version 2 Release 1.2 +
analysis’)
EXIT VERB(CICS321) EP(DFHPD321) ABSTRACT(’CICS Version 3 Release 2.1 +
analysis’)
EXIT VERB(CICS330) EP(DFHPD330) ABSTRACT(’CICS Version 3 Release 3 +
analysis’)
EXIT VERB(CICS410) EP(DFHPD410) ABSTRACT(’CICS Version 4 Release 1 +
analysis’)
.
.
.
EXIT VERB(VTAMMAP) EP(ISTRAFD1) ABSTRACT(’VTAM control block analysis’)

DIALOG NAME(XESDATA) HELP(IXLHDIA) ABSTRACT(’XES analysis’) PARM(’PANEL(+

IXLF1PMN)’)
PANDEF SUBCOMD(CTRACE) COMPONENT(SYSXCF) INPUT(IXCF1PTI) HELP(IXCHTDI)
PANDEF SUBCOMD(CTRACE) COMPONENT(SYSXES) INPUT(IXLF1PTI) HELP(IXLHTDI)
PANDEF SUBCOMD(CTRACE) COMPONENT(SYSOMVS) INPUT(BPXCTPAN) HELP(BPXHCTP1)

SYMBOL NAME(AFT) STRUCTURE(AFT)

SYMBOL PREFIX(ASCB) SUFFIX(COUNT1) STRUCTURE(ASCB)
SYMBOL NAME(ASMVT) STRUCTURE(ASMVT)
SYMBOL PREFIX(ASSB) SUFFIX(COUNT1) STRUCTURE(ASSB)
SYMBOL PREFIX(AST) SUFFIX(COUNT0) STRUCTURE(ASTE)
SYMBOL PREFIX(ASTE) SUFFIX(COUNT1) STRUCTURE(ASTE)
SYMBOL NAME(ASVT) STRUCTURE(ASVT)
SYMBOL PREFIX(ASXB) SUFFIX(COUNT1) STRUCTURE(ASXB)

SYMBOL NAME(BLSQXBT) STRUCTURE(BLSQXBT)

SYMBOL PREFIX(BLSQXBT) SUFFIX(COUNT1) STRUCTURE(BLSQXBT)

SYMBOL PREFIX(BLSUZZ1) SUFFIX(COUNT1) STRUCTURE(BLSUZZ1)

SYMBOL PREFIX(CDE) SUFFIX(NAME) STRUCTURE(CDE)

.
.
.
SYMBOL PREFIX(TCB) SUFFIX(DUALCOUNT) STRUCTURE(TCB)
SYMBOL NAME(TITLE)

SYMBOL PREFIX(UCB) SUFFIX(UNIT) STRUCTURE(UCB)

SYMBOL NAME(UCM) STRUCTURE(UCM)

184 z/OS MVS IPCS Commands

 IPCSDATA subcommand

SYMBOL PREFIX(WTRFSCB) SUFFIX(COUNT1NAME) STRUCTURE(WTRFSCB)

SYMBOL PREFIX(XL) SUFFIX(NAME) STRUCTURE(XTLST)

SYMBOL PREFIX(Z) SUFFIX(COUNT1)

Master BLSUZZ2 at 00038AB0 and BLSUZZ7 at 000399F0 for TCB at 008CC988

Processing BLSUZZ2 at 00040000 and BLSUZZ7 at 0DAB8000 for TCB at 008CC6F0

BLSRZZ6 at 0005C000 for ACTIVE

BUFPOOL(0DB08C80) BUFL(4160) BUFNO(2)

BLSRZZ6 at 00072000 for DSNAME(’H44IPCS.W4BG.PMR0X980.B519.MD520’)

BUFPOOL(0DD2A100) BUFL(24960) BUFNO(42)
INUSE(42) REQUESTS(2225) READS(117)

IPLDATA subcommand — request IPL reports

Use the IPLDATA subcommand to request reports about the IPL process and
options.
v Syntax

IPLDATA

-------- Report Selection Parameters ----------------------------

[ INFORMATION | STATUS ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
INFORMATION
Selects the INFORMATION report, the default. This report has nearly the
same format as the output of the DISPLAY IPLINFO system command.
STATUS
Selects the STATISTICS report. This is the same report produced by verb exit
BLSAIPST. The report contains status data collected during IPL, NIP, and
Master Scheduler Initialization (MSI) during system initialization.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the IPLDATA subcommand.
v Example: Select the INFORMATION report.
– Action
COMMAND ===> IPLDATA INFORMATION

Chapter 5. IPCS subcommands 185

IPLDATA subcommand

– Result
System IPLed at 10:38:23.552 on 10/03/2011
Release z/OS 02.01.00
Used LOADTH in SYS0.IPLPARM on 0343
IEASYM LIST=(TH,L)
IEASYS LIST=TE (OP)
IODF device 0343
IPL device: original 0980 current 0810 volume BO0810

ISPEXEC subcommand — request an ISPF dialog service

Use the ISPEXEC subcommand to request services supplied by the Program
Development Facility (PDF) Program Product and the ISPF Dialog Manager
Program Product. The function of the IPCS ISPEXEC subcommand is the same as
the ISPF ISPEXEC command.

Before requesting PDF services, make sure your installation has installed PDF.

ISPEXEC can be entered only in the IPCS dialog. If you enter the ISPEXEC
subcommand outside the IPCS dialog, ISPEXEC abnormally ends with a return
code of 16.
v Syntax
The syntax of the IPCS ISPEXEC subcommand is the same as the syntax of the
ISPF ISPEXEC command. The ISPEXEC command is documented in z/OS ISPF
Reference Summary.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the ISPEXEC subcommand.

LIST subcommand — display storage

Use the LIST subcommand to display storage from the current dump. You can
display storage from one or several dump locations. Specify the amount of storage
and its format with the appropriate data description parameters.

Note: This subcommand might modify X, the current address.

v Related subcommands
– EQUATE
– FIND
– FINDMOD
– FINDUCB
– LISTMAP
– LISTSYM
– STATUS
v Syntax

186 z/OS MVS IPCS Commands

 LIST subcommand

{ LIST } { data-descr }
{ L } { (data-descr...) }

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
data-descr or (data-descr...)
Specifies that either one data description or a list of data descriptions be
entered. A list of data descriptions consists of multiple address expressions
and one group of data description parameters that apply to all addresses in
the list. The data description parameter consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.
Use the following data description parameters to obtain particular
information:
– TITLE to obtain the title of an SVC dump.
– COMPDATA(IEASLIP) to obtain the SLIP command parameters in
EBCDIC for an SVC dump requested by a SLIP command. If the SLIP
command parameters are not available, the following appears:
SLIP TRAP TEXT NOT AVAILABLE
DISPLAY[(display-options)]
NODISPLAY[(nodisplay-options)]
Specifies if IPCS is to display or not display the storage identified in the
data-descr parameter. For the LIST subcommand, the default is
DISPLAY(STORAGE). See the SETDEF subcommand for other values for
DISPLAY.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the LIST subcommand.
v Example 1: Display the title of the dump.
– Action
COMMAND ===> list title
– Result
Using the special symbol TITLE, the LIST subcommand generates the
following output, including the dump title, “Hang After Hotstart”. IPCS also
displays the dump title during dump initialization.

Chapter 5. IPCS subcommands 187

LIST subcommand

TITLE
LIST 00000000. HEADER POSITION(X’+0020’) LENGTH(19) CHARACTER
00000020. | HANG AFTER HOTSTART |
v Example 2: Display all PSAs when running the 3090 model 400.
– Action
COMMAND ===> list (psa0, psa1, psa2, psa4) structure(psa)
– Result
LIST displays the PSA for each central processor that is online.
v Example 3: Display SQA storage.
– Action
COMMAND ===> list sqa
– Result
LIST displays SQA storage.
v Example 4: Display multiple system storage areas.
– Action
Specify the appropriate symbols with LIST, enclosing them in parentheses:
COMMAND ===> list (sqa csa private)
– Result
LIST displays the storage for the areas.
v Example 5: Display central storage. There are several ways to do this. One way
is to request a range of absolute addresses, like this:
– Action
COMMAND ===> list 0:7fffffff absolute
– Result
LIST displays all of ABSOLUTE storage, without performing storage
prefixing.
v Example 6: Another way to display central storage is to request a range of
central storage for a given central processor.
– Action
COMMAND ===> list 0:7fffffff CPU(0) real
– Result
LIST displays the same storage as Example 5, replacing the ABSOLUTE PSA
(the storage at 0:0FFF) with the PSA of central processor CPU(0). The
ABSOLUTE PSA appears where the PSA for CPU(0) appeared in the Example
5.

Note: If you want to print the dump quickly, you can break your request into
pieces, as shown in the following examples:

To Get This Result Make This Request

Absolute PSA list 0:0fff absolute
Real PSAs for each central processor list 0:0fff cpu(n) real
Absolute storage above the PSA list 1000:7fffffff absolute

v Example 7: Display storage in instruction format.

– Action
COMMAND ===> list 081A8C14. instruction
– Result

188 z/OS MVS IPCS Commands

 LIST subcommand

LIST 081A8C14. ASID(X’0060’) LENGTH(X’1000’) INSTRUCTION

081A8C14 | D203 E000 A01C | MVC X’0’(X’4’,R14),X’1C’(R10)
081A8C1A | 90FD E004 | STM R15,R13,X’4’(R14)
081A8C1E | 58E0 A01C | L R14,X’1C’(,R10)
081A8C22 | E803 B490 B247 | MVCIN X’490’(X’4’,R11),X’247’(R11)
081A8C28 | 5810 B00C | L R1,X’C’(,R11)

LISTDUMP subcommand — list dumps in dump directory

Use the LISTDUMP subcommand to:
v Display the names of the sources described in a dump directory
v Produce a dumped storage summary report

A source description is for an unformatted source that IPCS can format, for
example, an SVC dump, a stand-alone dump, an SYSMDUMP dump, a trace data
set, a data set, or active storage. The source descriptions are in the dump directory
allocated with ddname IPCSDDIR and is your current dump directory. The current
dump directory is your user dump directory or, for users with write access
authority, might be the sysplex dump directory.
v Related subcommands
– COPYDUMP
– DROPDUMP
– EVALDUMP
– SUMMARY
v Syntax

{ LISTDUMP } [ SUMMARY | NOSUMMARY ]

{ LDMP }

[ SELECT [ (ATTRIBUTES ) ] ]
[ [ (BACKING ) ] ]
[ [ (DUMPED ) ] ]
[ [ (TRANSLATION ) ] ]
[ ]
[ NOSELECT ]
[ SYMPTOMS | NOSYMPTOMS ]
[ INDATASET(dsname) | INFILE(ddname) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
SUMMARY or NOSUMMARY
SUMMARY indicates that a processing summary (a final total line) is to be
produced. NOSUMMARY suppresses the processing summary. The
NOSUMMARY parameter is useful for turning summary messages off when
the subcommand is invoked within a CLIST or a REXX exec.
SELECT[(options)]

Chapter 5. IPCS subcommands 189

LISTDUMP subcommand

NOSELECT
Specifies whether dumped storage is to be provided.
SELECT provides dumped storage; NOSELECT provides only a list of the
sources for the source descriptions and the number of storage locks and
bytes for the source.
The options control the amount of information included in the summary.
When specifying more than one option, separate options with a blank and
enclose the list of options in parentheses. The options are:
ATTRIBUTES
Requests that the attributes of each range of storage in the report be
included on the output line for that range. Where applicable, one or
more of the following attributes appear in the generated report:
ABSOLUTE
Represents a storage frame that was in processor storage when a
stand-alone dump was requested.
COMMON
Represents common virtual storage.
MISSING
Represents storage not available in the dump.
PREFIXED
Represents storage to which access is affected by central storage
prefixing.
RECLAIMED
Represents storage that was marked not valid in the page table
but was located in a reclaimable storage frame.
SUMLIST
Represents storage recorded in response to the summary dump
options (SUMLIST, SUMLISTA, and so on) of the SDUMP macro.
TRANSLATED
Represents storage located using an IPCS translation algorithm
and retained in the dump directory to avoid repeated
translation. These translation processes use the following
mechanisms:
– Simulation of dynamic address translation when IPCS
processes a stand-alone dump.
– Simulation of central storage prefixing when IPCS processes a
stand-alone dump.
– Simulation of the page reclamation process performed by the
RSM component.
BACKING
Specifies that the dump storage summary report indicate where the
dumped information is backed in the dump records. In other words, it
provides record numbers of, and offsets into, the records where the
storage can be found.
For example, the following portion of a line of the report output
indicates that 4096 consecutive dump records, beginning with
RECORD(5), each contain 4096 bytes of consecutive storage:
RECORD(5:4100) POSITIONS(48:4143)

190 z/OS MVS IPCS Commands

 LISTDUMP subcommand

This option is most useful for diagnosing problems within the dump
records.

Note: For data sets that are not RECFM=F or RECFM=FBA, the relative
track address (TTR) will appear instead of RECORD.
DUMPED
Requests that the storage summary report include storage explicitly
described by the dumping program.
TRANSLATION
Specifies that the storage summary report include translation results that
IPCS retained in the dump directory. TRANSLATION suppresses the
output from the DUMPED option unless both options are explicitly
specified.

Note: IPCS can record storage that cannot be accessed in the dump. In the
report output for requests that produce only storage ranges — such as
LISTDUMP SELECT (DUMPED TRANSLATION) — the only way to
distinguish accessible storage from missing storage is by checking the
separators between the first and last addresses in the range. Accessible
storage ranges use colons as separators:
00F0C000:00F0EFFF
while missing storage range addresses are separated by a dash:
00F0C000-00F0EFFF
SYMPTOMS
NOSYMPTOMS
Specifies whether LISTDUMP is to add two lines of information to that
displayed for each dump selected:
– The first line shows the dump title (symbol TITLE) or indicates that none
is available from the dump directory.
– The second line show symptoms in addition to the title or indicates that
none are available from the dump directory. The symptoms chosen are
indicated by the caption and are, in order of preference:
- Trap — SLIP trap text (symbol SLIPTRAP)
- Psym — Primary symptom string (symbol PRIMARYSYMPTOMS)
- Ssym — Secondary symptom string (symbol
SECONDARYSYMPTOMS)
If an output medium is selected that is too narrow to display the dump
directory data available for either line, as much data is shown as will fit on
one line.
The default NOSYMPTOMS keyword suppresses this output.
INDATASET(dsname)
INDSNAME(dsname)
Requests allocation of directory dsname and use of the contents of that
directory by the subcommand.
INFILE(ddname)
INDDNAME(ddname)
Requests use of a directory that the IPCS user has allocated to ddname and
use of the contents of that directory by the subcommand.
ACTIVE or MAIN or STORAGE
DATASET(dsname-list) or DSNAME(dsname-list)

Chapter 5. IPCS subcommands 191

LISTDUMP subcommand

FILE(ddname-range-list) or DDNAME(ddname-range-list)
Specifies the source or sources of the source descriptions to be selected from
the dump directory. Use these parameters with the SELECT parameter. If
these parameters are omitted, the report is for all sources in the user dump
directory.
ACTIVE, MAIN, or STORAGE specifies central storage as the source.
DSNAME or DATASET specifies the names of one or more data set as the
sources.
FILE or DDNAME specifies one, several, or a range of ddnames for data sets
as the sources.
When specifying more than one data set name or ddname, separate the
names with commas or blanks. When specifying a range of ddnames,
separate the first and last ddname with a colon.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the LISTDUMP subcommand.
v Example 1: List the dump sources described in the dump directory.
– Action
COMMAND ===> listdump
This command has the defaults of SUMMARY, NOSELECT, and
NOSYMPTOMS.
– Result
The following output is produced. Notice that the last line, which is produced
by the SUMMARY parameter, provides a total number of the displayed dump
data sets.

Source of Dump Blocks Bytes

ACTIVE . . . . . . . . . . . . . . . . . . . . 2 . . . . . 8,208
FILE(CLIC) . . . . . . . . . . . . . . . . . . 10 . . . . . 2,640
FILE(MENUS) . . . . . . . . . . . . . . . . . . 10 . . . . . 2,640
DSNAME(’D46RLW1.LOG.MISC’) . . . . . . . . . . 79 . . . . 187,809
DSNAME(’D46RLW1.RLW.CLIST’) . . . . . . . . . . 25 . . . . . 6,600
DSNAME(’D46RLW1.SYSMDUMP’) . . . . . . . . 1,218 . . . 4,998,672
DSNAME(’D46RLW1.XMIT.NAMES’) . . . . . . . . . 2 . . . . . 3,520
DSNAME(’D46RLW1.THIS.IS.A.LONG.DSNAME.FOR.TESTING(TESTMEMB)’)
1,040 . . . . 31,200
DSNAME(’D83DUMP.DUMPC.PB06511’) . . . . . . 1,346 . . . 5,523,984
DSNAME(’D83DUMP.DUMPC.PB07251’) . . . . . . 24,142 . . 99,078,768
10 Dumps described

v Example 2: Obtain a dumped storage summary report with retained translation

data, attributes, and storage described by the dumping program for a particular
dump data set, MY.DUMP.
– Action
COMMAND ===> listdump select(dumped attributes translation) dsname(my.dump)
– Result
The following output is produced.

192 z/OS MVS IPCS Commands

 LISTDUMP subcommand

Source of Dump Blocks Bytes

DSNAME(’RLW.HBB5520.SAMPLE.SVCDUMP’) . . 994 . . . . 4,135,040
ABSOLUTE
00A95000:00A95FFF ABSOLUTE
00CD3000:00CD3FFF ABSOLUTE
010A7000:010A7FFF ABSOLUTE
012A8000:012A8FFF ABSOLUTE
01539000:01539FFF ABSOLUTE
01756000:01757FFF ABSOLUTE
0175A000:0175CFFF ABSOLUTE
40,960, X’0000A000’, bytes described in ABSOLUTE

ASID(X’0001’)
00000000:00000FFF COMMON PREFIXED TRANSLATED
006F6000:006FBFFF
00AF2000:00B0CFFF COMMON TRANSLATED
00F4A000:00F4DFFF COMMON TRANSLATED
00F8B000:00F90FFF COMMON TRANSLATED
00F9C000:00FA0FFF COMMON TRANSLATED
00FA6000:00FA6FFF COMMON TRANSLATED
00FBF000:00FC9FFF COMMON TRANSLATED
00FCF000:00FD2FFF COMMON TRANSLATED
00FD3000-00FD5FFF COMMON MISSING TRANSLATED
00FD6000:00FD6FFF COMMON TRANSLATED
.
.
.
020F6000:02106FFF COMMON TRANSLATED
1,589,248, X’00184000’, bytes described in ASID(X’0001’)

ASID(X’0004’)
7F735000:7F745FFF
69,632, X’00011000’, bytes described in ASID(X’0004’)
ASID(X’0015’)
00000000:00000FFF COMMON PREFIXED
006D4000:006D5FFF
006DC000:006DCFFF
006E2000:006E3FFF
006EA000:006FFFFF
00AF2000:00B0CFFF COMMON
00F0C000:00F4DFFF COMMON
.
.
.
7FFFB000:7FFFEFFF
3,928,064, X’003BF000’, bytes described in ASID(X’0015’)

HEADER
00000000:0000103F
4,160, X’00001040’, bytes described in HEADER

COMPDATA(IARCDR01)
00000000:00000FFF
4,096, X’00001000’, bytes described in COMPDATA(IARCDR01)

DOMAIN(SUMDUMP)
00001000:00006FFF
24,576, X’00006000’, bytes described in DOMAIN(SUMDUMP)

ASID(X’0015’) SUMDUMP
01E8CDD8:01E8CDF3 COMMON SUMLIST
01EB9000:01EB91FF COMMON SUMLIST
7F702F80:7F702FFF SUMLIST
7F704000:7F708FFF SUMLIST
7FFFB040:7FFFB07F SUMLIST
7FFFC008:7FFFC037 SUMLIST
21,260, X’0000530C’, bytes described in ASID(X’0015’) SUMDUMP

1 Dump described

v Example 3: List the dump sources described in the dump directory with
additional title and symptom information.
– Action

Chapter 5. IPCS subcommands 193

LISTDUMP subcommand

COMMAND ===> listdump symptoms

This command has the defaults of SUMMARY and NOSELECT.
– Result
The following output is produced.

Source of Dump Blocks Bytes

ACTIVE 2 8,320
No title
No symptoms

Source of Dump Blocks Bytes

DSNAME(’C89.BLSRMVCL.SOC4DUMP’) 26,544 110,423,040
Title=JOBNAME C89 STEPNAME SMPROC SMPROC SYSTEM 0C4
Psym=RIDS/BLSRVEC3#L RIDS/BLSRMVCL PIDS/5752SC132 AB/S00C4 RIDS/BLSUSTAI#R V

Source of Dump Blocks Bytes

DSNAME(’H44IPCS.R38A.PMR00137.B379.EH603’) 12,762 53,089,920
Title=COMPON=COMPONENT TRACE,COMPID=SCTRC,ISSUER=ITTAWRIT
Psym=RIDS/NUCLEUS#L RIDS/ITTAWRIT PIDS/5752SCTRC AB/S001D RIDS/ITTAWRIT#R VA

Source of Dump Blocks Bytes

DSNAME(’H44IPCS.R38A.PMR00137.B379.EH603A’) 573,996 2,387,823,360
Title=SLIP DUMP ID=0005
Trap=SLIP SET,COMP=01D,NUCMOD=IARDS,DN=(3.*,15.SYSLOGR0),SD=(ALLNUC,PSA,SQA,

Source of Dump Blocks Bytes

DSNAME(’H44IPCS.R38A.PMR00218.B677.DUMP1’) 10,574 43,987,840
Title=SLIP DUMP ID=X05C
Trap=SLIP SET,C=05C,ID=X05C,A=SVCD,RE=308

Source of Dump Blocks Bytes

DSNAME(’NHAN.FBS29K.DUMP’) 438,123 1,822,591,680
Title=’MVSPROD1 02/27/97’
No symptoms

6 Dumps described
IPCS

The output medium to which the preceding output was directed was 78
characters wide. This caused the lines beginning “Psym=RIDS/BSLRVEC3#L”,
“Psym=RIDS/NUCLEUS#L”, and “Trap=SLIP” to be truncated.

LISTEDT subcommand — format the eligible device table (EDT)

Use the LISTEDT subcommand to display information from the eligible device
table (EDT). You can access the EDT in a dump data set or in active storage.

The system can have two EDTs during a dynamic configuration change. You must
distinguish between formatting a primary EDT and a secondary EDT.

Each EDT is divided into subtables, which you can format separately with
LISTEDT.

See the allocation/unallocation component in z/OS MVS Diagnosis: Reference for

information about primary and secondary EDTs. Also, see z/OS MVS Data Areas in
the z/OS Internet library (www.ibm.com/systems/z/os/zos/library/bkserv) for
information about the EDT.
v Syntax

194 z/OS MVS IPCS Commands

 LISTEDT subcommand

LISTEDT
[ PRIMARY | SECONDARY ]

-------- Data Selection Parameters -------------------------

[ COMPGENS[(index-number-list)] ]
[ DETAIL ]
[ DEVNUM[(index-number-list)] ]
[ DEVPOOL[(index-number-list)] ]
[ GENERIC[(index-number-list)] ]
[ GROUP[(index-number-list)] ]
[ GRPMSK[(index-number-list)] ]
[ GRPPTR[(index-number-list)] ]
[ GRPCONV[(index-number-list)] ]
[ HEADER ]
[ LIBRARY[(index-number-list)] ]
[ LUV[(index-number-list)] ]
[ PREF[(index-number-list)] ]
[ SHOWDEVN(device-number-list) ]
[ SHOWGRPN[(group-number-list)] ]
[ SUMMARY[(unit-name-list)] | SHOWUNIT[(unit-name-list)] ]
[ TAPE ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
PRIMARY or SECONDARY
Specifies the EDT that is to be formatted. The types of EDTs are:
– Primary EDT: processes all current and new allocation requests.
– Secondary EDT: processes all allocation requests issued before a dynamic
configuration change.
PRIMARY is the default. If you specify SECONDARY and no secondary EDT
exists in the source storage or dump, IPCS displays message IEF10010I in the
report.
v Data Selection Parameters
Use these parameters to limit the scope of the data in the report. If you omit a
data selection parameter, the default is HEADER.
In the data selection parameter descriptions, index-number-list is one or more 1-
to 4-digit hexadecimal numbers, ranges of numbers, or both. Each index number
corresponds to an index for a sub-table entry. If you omit index-number-list, IPCS
formats the entire sub-table.
The index-number-list can be a single number, a range of numbers, or a list of
numbers. When you specify a range, separate the first and last numbers in the
range with a colon. When you specify a list, separate the numbers with commas.
The number or numbers are enclosed in parentheses.

Chapter 5. IPCS subcommands 195

LISTEDT subcommand

COMPGENS
Specifies that the compatible-generic section of the EDT appears in the
output. Generics are compatible when a data set can be allocated to any
generic.
DETAIL
Specifies that all the subtables in the EDT appear in the output.
DEVNUM[(index-number-list)]
Specifies that the device number section appears in the output.
DEVPOOL[(index-number-list)]
Specifies that the system-managed type library device pool entries in the
EDT appear in the output. Each pool represents a set of tape drives within a
library. In the output, look-up-value entry indexes refer to the output of the
LUV parameter of the LISTEDT subcommand.
GENERIC[(index-number-list)]
Specifies that the generic section of the EDT appears in the output.
GROUP[(index-number-list)]
Specifies that the group section of the EDT appears in the output.
GRPCONV[(index-number-list)]
With Version 4.2.0 or a later release, specifies that the group mask
conversion table appears in the output. This table exists only after a dynamic
configuration change.
GRPMSK[(index-number-list)]
Specifies that the group mask table appears in the output.
GRPPTR[(index-number-list)]
Specifies that the group pointer table of the EDT appears in the output.
HEADER
Specifies that the EDT header appears in the output.
LIBRARY[(index-number-list)]
Specifies that the system-managed tape library entries in the EDT appear in
the output. The entries include indexes for the related system-managed tape
library device pool entries.
LUV[(index-number-list)]
Specifies that the look-up value section of the EDT appears in the output.
PREF[(index-number-list)]
Specifies that the preference table appears in the output.
SHOWDEVN(device-number-list)
Lists the group number to which each device number in the
device-number-list belongs. device-number-list must be specified and should
consist of one or more 1- to 4-digit hexadecimal device numbers, ranges of
numbers, or both.
SHOWGRPN[(group-number-list)]
Lists the unit names associated with each of the group numbers in the
group-number-list. The group-number-list is one or more 1- to 4-digit
hexadecimal numbers, ranges of numbers, or both. If you do not supply
group-number-list, IPCS formats information for all the device groups in the
system.
SUMMARY[(unit-name-list)] | SHOWUNIT[(unit-name-list)]
Produces a summary report for all the unit names in the unit-name-list. The

196 z/OS MVS IPCS Commands

 LISTEDT subcommand

unit-name-list is one or more 1- to 8-character alphanumeric unit names.

Separate multiple list items with one or more commas, blanks, or tab
characters (X'05'). If you do not supply unit-name-list, IPCS formats
information for all unit names in the system.
TAPE
Requests formatting of the tape maximum eligibility table. The output
includes tape device information such as density and device type.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the LISTEDT subcommand.
v Example: Display information for device numbers 0001 through 0006 and 0021
through 0028 in the secondary EDT.
– Action
COMMAND ===> listedt secondary devnum(0001:0006,0021:0028)
– Result
See the allocation/unallocation component in z/OS MVS Diagnosis: Reference
for an example of LISTEDT output.

LISTMAP subcommand — list storage map entries

Use the LISTMAP subcommand to produce output using the storage map:
v Generate dump displays of blocks within a range of addresses (VERIFY option).
v Repeat diagnostic messages pertaining to blocks within a range of addresses
(RESCAN option).

The storage map is part of a source description. A source description is for an

unformatted source that IPCS can format, for example, an SVC dump, a
stand-alone dump, an SYSMDUMP dump, a trace data set, a data set, or active
storage. The source description is in the dump directory allocated with ddname
IPCSDDIR and is your current dump directory. The current dump directory is your
user dump directory or, for users with write access authority, might be the sysplex
dump directory.

For information about using the storage map, see the z/OS MVS IPCS User's Guide.
v Related subcommands
– DROPMAP
– SCAN
v Syntax

Chapter 5. IPCS subcommands 197

LISTMAP subcommand

{ LISTMAP } [ RANGE(address:address)] [data-descr ]

{ LMAP }
[ RESCAN | NORESCAN ]
[ SUMMARY | NOSUMMARY ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
[ VERIFY | NOVERIFY ]

v Parameters
RANGE(address:address)
Specifies a range of addresses in the dump for which map entries are to be
listed.
data-descr
Specifies the data description parameter, which consists of five parts:
– An address (specified with the RANGE parameter and required when
data-descr is explicitly specified on the subcommand)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.
If you specify address processing parameters (which are optional) but omit
the address (which is required), the subcommand lists all map records for
the address space.
If you omit the range parameter, the subcommand lists all map records for
the dump.
RESCAN or NORESCAN
Requests or suppresses retransmission of diagnostic messages pertaining to
blocks in the range selected, subject to the restriction imposed by the FLAG
parameter.
RESCAN requests retransmission.
NORESCAN suppresses retransmission.
SUMMARY or NOSUMMARY
SUMMARY indicates that a processing summary (a final total line) is to be
produced.
NOSUMMARY specifies that a processing summary is to be suppressed. The
NOSUMMARY parameter is useful to turn off summary messages when the
subcommand is invoked within a CLIST or a REXX exec.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the LISTMAP subcommand.

198 z/OS MVS IPCS Commands

 LISTMAP subcommand

v Example: Display storage map entries for a range of addresses.

– Action
listmap range(5000.:10000.) terminal noprint
– Result
The subcommand requests a display, at the terminal only, of the storage map
entries that originate between the addresses X'5000' and X'10000'.

LISTSYM subcommand — list symbol table entries

Use the LISTSYM subcommand to display the definitions of symbols for a source
or to produce a display using symbols for a source.

The symbols are in a symbol table that is part of a source description. A source
description is for an unformatted source that IPCS can format, for example, an
SVC dump, a stand-alone dump, an SYSMDUMP dump, a trace data set, a data
set, or active storage. The source description is in the dump directory allocated
with ddname IPCSDDIR and is your current dump directory. The current dump
directory is your user dump directory or, for users with write access authority,
might be the sysplex dump directory.
v Related subcommands
– DROPSYM
– EQUATE
– RENUM
– STACK
v Syntax

{ LISTSYM } [ (symbol-list) | * ]
{ LSYM }
[ SELECT [(ALL | DROP | NODROP)] ]
[ SUMMARY | NOSUMMARY ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
symbol-list or *
Specifies the symbols to be displayed:
– symbol-list specifies one or more particular symbols.
– * specifies all the symbols in the symbol table. If you omit this parameter,
the default is *.
The symbol-list can be a single symbol, a range of symbols, a list of symbols,
or any combination of these. When you specify a range, separate the first
and last symbols in the range with a colon. When you specify a list, separate

Chapter 5. IPCS subcommands 199

LISTSYM subcommand

the symbols with commas. If you specify more than one symbol or range,
enclose them in parentheses. The list can contain a maximum of 31 symbols,
ranges, or both.
The symbols must follow the IPCS naming conventions for symbols if a
range is specified. See Appendix A, “IPCS symbols,” on page 445.
For a range, IPCS displays all symbols whose names begin with the first
character string through all symbols whose names begin with the second
character string. A range of symbols is inclusive; IPCS displays all the
symbols in the range and at both ends of the range.
SELECT(ALL | DROP | NODROP)
Specifies a selection criterion for symbols to be displayed:
– ALL specifies that all symbols are to be displayed.
– DROP specifies that only symbols with the DROP attribute are to be
displayed.
– NODROP specifies that only symbols with the NODROP attribute are to
be displayed.
If you omit ALL, DROP, or NODROP, the default is ALL.
SUMMARY or NOSUMMARY
SUMMARY indicates that a processing summary (a final total line) is to be
produced.
NOSUMMARY specifies that a processing summary is to be suppressed. The
NOSUMMARY parameter is useful to turn off summary messages when the
subcommand is invoked within a CLIST or a REXX exec.
DISPLAY[(display-options)]
NODISPLAY[(display-options)]
Specifies the display options. The defaults are:
DISPLAY(NOMACHINE NOREMARK REQUEST NOSTORAGE SYMBOL AlIGN)

LISTSYM uses a special, tabular display format unless you specify one of the
following display options:
DISPLAY(MACHINE NOREQUEST STORAGE NOSYMBOL)

If you specify none of these options, IPCS uses the general-purpose dump
display format.
In addition, the archaic REMARKS parameter can be specified as a separate
parameter. REMARKS is the equivalent of DISPLAY(REMARK). It causes the
display to include any remarks associated with a symbol.
ACTIVE or MAIN or STORAGE
DSNAME(dsname) or DATASET(dsname)
FILE(ddname) or DDNAME(ddname)
Specifies the source of the source description containing the symbol. If one
of these parameters is not specified, the default is your current source.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the LISTSYM subcommand.
v Example 1: List a range of symbols.
– Action
COMMAND ===> listsym (my:my title acvt)
– Result

200 z/OS MVS IPCS Commands

 LISTSYM subcommand

The following output is produced.

SYMBOL ADDRESS ATTRIBUTES

ACVT 1D418. ASID(X’0001’) POSITION(-24) LENGTH(1248) STRUCTURE(CVT) DROP
MY#LONG#SYMBOLIC
0. ASID(X’0078’) LENGTH(96) AREA DROP
MYARRAY F0000. ASID(X’0078’) POSITION(+64) LENGTH(4) ENTRIES(52:77)
SIGNED DROP
MYCVT 1D418. ASID(X’0001’) POSITION(-24) LENGTH(1248) STRUCTURE(CVT) DROP
TITLE 0. HEADER POSITION(20) LENGTH(53) CHARACTER NODROP
5 DEFINITIONS LISTED

– Explanation
- Symbols are always processed alphabetically. Specifying “acvt” after the
other selection criteria produces the same result as moving it to the
beginning of the list.
- A caption line is provided for the special, tabular format of the LISTSYM
display. Symbol and address captions describe the values that will appear
beneath. Attributes are shown in a self-describing format using standard
IPCS parameters plus decimal or hexadecimal values. Underscores are
added to the caption line when transmitted to a print data set.
- The entire definition of a symbol is typically displayed on one line. The
format resembles that of the EQUATE subcommand parameters.
- When the symbol and the address overlap, if both are displayed on a single
line, the symbol will appear alone on the initial line, and the address and
attributes will begin on a second line.
- When the full complement of attributes will not fit on one line, they may
overflow onto an additional line.
v Example 2: List a range of ASCB symbols.
– Action
COMMAND ===> listsym (ascb00001 : ascb00050)
– Result
LISTSYM displays the ASCB symbols for ASID 1 through 50.
v Example 3: List a range of TCB symbols.
– Action
COMMAND ===> listsym (tcb00001aaaaa : tcb00001baaaa)
– Result
LISTSYM displays the specified range of TCBs.

LISTTOD subcommand — list TOD clock image

Use the LISTTOD subcommand to translate a hexadecimal GMT TOD clock value
to the specified time stamp. The LISTTOD command supports three types of STCK
or STCKE time stamps using the time-zone adjustments from your dump:
v ABSOLUTE time stamps are produced by the STCK or STCKE instructions
directly.
v UTC time stamps are produced by adjusting the STCK or STCKE time stamps
using a leap second adjustment factor maintained by the z/OS timer services.
v LOCAL time stamps are produced by adjusting the UTC time stamps using a
time zone adjustment factor maintained by the z/OS timer services.

An INPUT option is now supported to allow the IPCS user to say which
interpretation applies to the time stamp being entered, and LISTTOD now formats
26-character values corresponding to all three interpretations.

Chapter 5. IPCS subcommands 201

LISTTOD subcommand

Use the INPUT option to specify the interpretation type for the time stamp. If you
omit this option, the default value is ABSOLUTE. The system translates the TOD
clock value to the time stamp as you specified, and it also formats other time
stamps if the corresponding adjustment factors can be retrieved from the current
dump. The first one to be displayed is for the specified option, and the other two
are to be shown in the following order: ABSOLUTE, UTC, and LOCAL.
v Syntax

{ LISTTOD|LTOD }(gmt-tod-value)[ EXTENDED ]

[ INPUT ({ ABSOLUTE | UTC | LOCAL })]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE|MAIN|STORAGE ]
[ DSNAME(dsname)|DATASET(dsname)]
[ FILE(ddname)|DDNAME(ddname) ]
[ PATH(hfspath) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
gmt-tod-value
Specifies the first 1-32 hexadecimal digits of a TOD clock value associated
with a dump.
EXTENDED
Specifies that the value should be treated as a 16-byte STCKE value rather
than an 8-byte TOD clock value that are stored by the STCK instruction. In
the output line for each time stamp, the 8-byte STCK or 16-byte STCKE
value used to format the time stamp is also displayed.
INPUT( { ABSOLUTE | UTC | LOCAL } )
Specifies the interpretation appropriate for the STCK or STCKE value
entered.
ABSOLUTE
Specifies that the value is the direct product of STCK or STCKE
instructions. If you omit the INPUT option, ABSOLUTE is the default
value.
UTC
Specifies that the value is adjusted with leap second factor.
LOCAL
Specifies that the value is adjusted with both leap second and local time
zone factors.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the LISTTOD subcommand.
v Example 1: Translate the TOD clock value from a dump.
– Action
listtod BDC613404B435A0A

The command treats the value as STCK value, translates it to the absolute
time stamp and then formats the other two time stamps.
202 z/OS MVS IPCS Commands
 LISTTOD subcommand

– Result
10/17/2005 10:46:26.479157 STCK X’BDC61340 4B435A0A’
10/17/2005 10:46:04.479157 UTC X’BDC6132B 502B5A0A’
10/17/2005 03:46:04.479157 LOCAL X’BDC5B54A B86B5A0A’
v Example 2: Translate the TOD clock value to local time stamp.
– Action
listtod BDC613404B435A0A input(local)

The command treats the value as STCK value, translates it to the local time
stamp and then formats the other two time stamps.
– Result
10/17/2005 10:46:26.479157 LOCAL X’BDC61340 4B435A0A’
10/17/2005 17:46:48.479157 STCK X’BDC67135 DE1B5A0A’
10/17/2005 17:46:26.479157 UTC X’BDC67120 E3035A0A’
v Example 3: Translate the TOD clock value that is stored by the STCKE
instruction.
– Action
listtod 00BDC613404B435A0A extended

The command treats the value as STCKE value, translates it to the absolute
time stamp and then formats the other two time stamps.
– Result
10/17/2005 10:46:26.479157 STCKE X’00BDC613 404B435A 0A000000 00000000’
10/17/2005 10:46:04.479157 UTC X’00BDC613 2B502B5A 0A000000 00000000’
10/17/2005 03:46:04.479157 LOCAL X’00BDC5B5 4AB86B5A 0A000000 00000000’
v Example 4: Translate the TOD clock value to local time stamp, treating the value
as stored by the STCKE instruction.
– Action
listtod 00BDC613404B435A0A extended input(local)

The command treats the value as STCKE value, translates it to the local time
stamp and then formats the other two time stamps.
– Result
10/17/2005 10:46:26.479157 LOCAL X’00BDC613 404B435A 0A000000 00000000’
10/17/2005 17:46:48.479157 STCKE X’00BDC671 35DE1B5A 0A000000 00000000’
10/17/2005 17:46:26.479157 UTC X’00BDC671 20E3035A 0A000000 00000000’

LISTUCB subcommand — list UCBs

Use the LISTUCB subcommand as a convenient means to request the display of
one or more unit control blocks (UCBs).
v Syntax

Chapter 5. IPCS subcommands 203

LISTUCB subcommand

{ LISTUCB } (device-number-list)
{ LISTU }

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
device-number-list
Specifies the device number for one or more devices for which UCBs are to
be displayed. device-number-list can be:
– A single hexadecimal device number of up to 4 digits with a subchannel
set identifier digit specified on qualified devices.
- Parentheses are accepted but are not required.
- Leading zero digits are accepted but are not required.
– A range of device numbers defined by the lowest and highest device
numbers separated by a colon.
- Parentheses are accepted but are not required.
- Leading zeros are accepted but are not required.
- The second device number must be as large as the first.
– A list containing either single device numbers or ranges of device
numbers. Parentheses are required. In the list, separate list members with
blanks, commas, or horizontal tabulation (X'05') characters. The separators
are permitted, but not required, between the left parenthesis and the first
member and between the last member and the right parenthesis.
IPCS processes the list from the left to the right, displaying UCBs in that
order. IPCS displays UCBs in a range starting with the lowest device
number. An individual UCB can be specified as often as you want and is
displayed again each time it is specified.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the LISTUCB subcommand.
v Example: Format the device for device 0410.
– Action
COMMAND ===> LISTUCB 0410
– Result

204 z/OS MVS IPCS Commands

 LITERAL subcommand

UCBPRFIX: 02103290
-0008 LOCK..... 00000000 IOQ...... 02438400
UCBOB: 02103298
+0000 JBNR..... 00 FL5...... 88 ID....... FF
+0003 STAT..... 84 CHAN..... 0410 FL1...... 00
+0007 FLB...... 00 NXUCB.... 00000000 WGT...... 08
+000D NAME..... 410 TBYT1.... 30 TBYT2.... 30
+0012 DVCLS.... 20 UNTYP.... 0E FLC...... 00
+0015 EXTP..... 103271 VTOC..... 00010100 VOLI..... BOZO40
+0022 STAB..... 10 DMCT..... 00 SQC...... 00
+0025 FL4...... A0 USER..... 0000 BASE..... 02103098
+002C NEXP..... 02103558
UCBCMXT: 02103270
+0000 ETI...... 00 STI...... 00 FL6...... 09
+0003 ATI...... 40 SNSCT.... 20 FLP1..... 2A
+0006 STLI..... 00 FL7...... 08 IEXT..... 02129040
+000C CHPRM.... 00 SATI..... 00 ASID..... 0000
+0010 RSV...... 00 WTOID.... 000000 DDT...... 00FCF228
+0018 CLEXT.... 02103230 DCTOF.... 0000 CSFLG.... 00
+001F RSV...... 00
UCBXPX: 02129040
+0000 RSTEM.... 00 MIHKY.... 04 MIHTI.... 00
+0003 HOTIO.... 40 IOQF..... 00000000 IOQL..... 00000000

Subchannel-Identification:
+000C CSS id 00
+000D Iid/SSid 01
+000E Number 003A

+0010 PMCW1.... 289C MBI...... 006A LPM...... F0

+0015 RSV...... 00 LPUM..... 80 PIM...... F0
+0018 CHPID.... 60708090 00000000 LEVEL.... 01
+0021 IOSF1.... 08 IOTKY.... 00 MIHFG.... 00
+0024 LVMSK.... 00000001

Actual UCB Common segment address 02103298

Device is dynamic
Base UCB of a parallel access volume
Base UCB has bound alias UCB 00418 at address 02103758
Base UCB has bound alias UCB 00419 at address 021037B8
Base UCB has bound alias UCB 10410 at address 02120568
Base UCB has bound alias UCB 10411 at address 021205C8
Base UCB has bound alias UCB 10418 at address 02120868
Base UCB has bound alias UCB 10419 at address 021208C8

Figure 21. LISTUCB command report for device 0410

LITERAL subcommand — assign a value to a literal

Use the LITERAL subcommand to assign a general value to a literal, which you
identify with a symbol. IPCS stores the symbol and its value in the symbol table
that is in a source description in your user dump directory.

If the source is a dump, IPCS does not initialize it. If the source has not been
added to your user dump directory when you enter LITERAL, IPCS performs
ADDDUMP processing for it, then stores the symbol and its value in the newly
created source description.
v Syntax

Chapter 5. IPCS subcommands 205

LITERAL subcommand

LITERAL symbol general-value

[ DROP | NODROP ]
[ NOREMARK | REMARK(’text’) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ TEST | NOTEST ]

v Parameters
symbol
Specifies the symbol that is to represent a literal. When specifying symbol, do
not include the ampersand (&) or the period (.) that are normally part of
symbolic notation. The symbol is 1 through 31 alphanumeric characters; the
first character must be a letter or one of the following characters:
$ (X’5B’)
# (X’7B’)
@ (X’7C’)
general-value
Specifies the value of the literal. See “General values” on page 10 for the
types of values and for how to specify them.
DROP
NODROP
Specifies whether the created symbol can be deleted or not from the symbol
table by a DROPSYM subcommand without a PURGE parameter:
– DROP specifies that the symbol can be deleted. The default is DROP.
– NODROP specifies that the symbol cannot be deleted. However,
NODROP can be overridden by a PURGE parameter on the DROPSYM
subcommand.
REMARK('text')
NOREMARK
Specifies or suppresses a remark associated with a symbol:
– REMARK specifies the remark. The text of the remark must be enclosed in
parentheses and apostrophes.
– NOREMARK suppresses the remark.
ACTIVE or MAIN or STORAGE
DSNAME(dsname) or DATASET(dsname)
FILE(ddname) or DDNAME(ddname)
Specifies the source of the source description that is to contain the symbol. If
one of these parameters is not specified, IPCS stores the symbol in the
source description for your current source.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the LITERAL subcommand.
v Example: Create a literal and place it in the symbol table of your current user
dump directory.
– Action
literal data2 x’ff34a’ nodrop

206 z/OS MVS IPCS Commands

 LITERAL subcommand

– Result
IPCS places the literal X'FF34A' into the symbol table and identifies it the
symbol DATA2.

LOGGER subcommand — format system logger address space data

The LOGGER subcommand formats data in the system logger address space in a
dump. Status is provided about the state of the address space, coupling facility
structures in use by system logger, logstreams and logstream connections

The LOGGER command can help in diagnosing errors in the system logger
address space, when the dump includes system logger private storage.

The LOGGER subcommand has no parameters.

v Syntax

LOGGER

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the LOGGER subcommand.

LPAMAP subcommand — list link pack area entry points

Use the LPAMAP subcommand to list the entry points in the active link pack area
(LPA) and pageable link pack area (PLPA), including the modified link pack area
(MLPA). IPCS flags duplicate entry points in the modified link pack area (MLPA).
v Related subcommands
– FINDMOD
– WHERE
v Syntax

Chapter 5. IPCS subcommands 207

LPAMAP subcommand

LPAMAP [ EPA ]
[ MODNAME ]
[ ALL ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
EPA
Requests a report containing an entry point listing that is sorted by entry
point address.
MODNAME
Requests a report containing an entry point listing that is sorted
alphabetically.
ALL
Requests both the MODNAME and the EPA entry point reports.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the LPAMAP subcommand.
v Example: Obtain the LPA entry points.
– Action
LPAMAP
– Result
The output follows.

208 z/OS MVS IPCS Commands

 LPAMAP subcommand

* * * L I N K P A C K A R E A M A P * * *
SORTED ALPHABETICALLY BY MODULE NAME

NAME EPA ADDRESS LENGTH MAJOR NOTE

-------- -------- -------- -------- -------- ------------
ADYPRED 81F9C260 01F9C260 00000DA0
AHLACFV 81B9B95C AHLTVTAM
AHLDMPMD 81B49F5C AHLSETD
AHLDSP 81B8A968 AHLTXSYS
AHLEXT 81F6765E AHLTSYSM
AHLFFP 81B44000 AHLFVEC
AHLFIO 81F7C0CC AHLTSYFL
AHLFPI 81F7C1A2 AHLTSYFL
AHLFRR 81F677E8 AHLTSYSM
AHLFSSCH 81F7C0EC AHLTSYFL
AHLFSVC 81F7C17E AHLTSYFL
AHLFVEC 81B44000 01B44000 00004C38
AHLMCER 81B494C0 AHLSETD
AHLPINT 81F67746 AHLTSYSM
AHLREADR 81C7FBE8 01C7FBE8 00000418
AHLRNIO 81B8A858 AHLTXSYS
AHLSBCU1 81B92F5E AHLWSMOD
AHLSBLOK 81B926C0 AHLWSMOD
AHLSBUF 81B92A88 AHLWSMOD
AHLSETD 81B49000 01B49000 000017B0
AHLSETEV 81B4B000 01B4B000 000019C0
AHLSFEOB 81B927FE AHLWSMOD
AHLSRB 81B8A9F4 AHLTXSYS
AHLSRM 81B8AA68 AHLTXSYS
AHLSTAE 81F678C6 AHLTSYSM
AHLSVC 81F67618 AHLTSYSM
AHLTACFV 81B9B968 AHLTVTAM
AHLTCCWG 81B4D000 01B4D000 00002468
AHLTDIR 81B49AF8 AHLSETD
AHLTDSP 81B5463E AHLTPID
AHLTEXT 81F75928 01F75928 000006D8
AHLTFCG 81B50000 01B50000 000016F0
AHLTFOR 81EBD570 01EBD570 00000A90
AHLTFRR 81EBD692 AHLTFOR
AHLTLSR 81B547CA AHLTPID
AHLTPI 81B5445E AHLTPID
AHLTPID 81B54448 01B54448 00000BB8
AHLTRNIO 81EBD570 AHLTFOR
AHLTSLIP 81B52000 01B52000 00002440
AHLTSRB 81B5475C AHLTPID
AHLTSRM 81EBD58A AHLTFOR
AHLTSTAE 81EBD7B4 AHLTFOR
AHLTSVC 81B55000 01B55000 00002AC8
AHLTSYFL 81F7C0B0 01F7C0B0 000006F0
AHLTSYSM 81F67508 01F67508 00000AF8
AHLTUSR 81B84978 01B84978 00000688
AHLTVTAM 81B9B940 01B9B940 000006C0

The LPAMAP output continues with data similar to this.

MERGE and MERGEEND subcommands — merge multiple traces

Use the MERGE subcommand to merge multiple component traces and
generalized trace facility (GTF) traces chronologically. MERGE combines formatted
trace entries produced by CTRACE subcommands, GTFTRACE subcommands, or
both, into chronological order in a single report. Use the MERGEEND
subcommand to stop merging traces.

Chapter 5. IPCS subcommands 209

MERGE and MERGEEND subcommands

Start the merging by entering MERGE in IPCS line mode. Next, format the traces
to be merged by entering, one at a time, CTRACE and GTFTRACE subcommands.
You can enter up to 16 subcommands. To mark the end of the merging, enter
MERGEEND.

Note: It is recommended that you use the MERGE option in the IPCS Dialog. See
z/OS MVS IPCS User's Guide for more information.

MERGE can process any of the dump or trace data sets that CTRACE and
GTFTRACE can process; however, MERGE has one restriction. Only one of the
trace sources may be on tape. The rest must be on direct access storage device
(DASD).

Do not specify different output locations on the CTRACE and GTFTRACE

subcommands. Each subcommand must contain the same output specifications. For
example, do not specify PRINT on one subcommand and TERMINAL on another.

Any syntax errors on the CTRACE and GTFTRACE subcommands will result in
unsuccessful processing of MERGE.
v Syntax

MERGE
..
.
1. to 16 CTRACE and GTFTRACE subcommands
..
MERGEEND

v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the MERGE subcommand.
v Example: Merge a component trace and GTF trace.
– Action
MERGE
CTRACE COMP(SYSRSM) FULL LIMIT(1) DSN(’MYDUMP1’)
GTFTRACE DSN(’COPY.TRACE1’)
MERGEEND
– Result
MERGE produces a report similar to the following.

210 z/OS MVS IPCS Commands

 MERGE and MERGEEND subcommands

********** MERGED TRACES ***********

01. GTF dsn(copy.trace1)
02. CTRACE dsn(rsm.ctrace) limit(5) comp(sysrsm) summary

**** GTFTRACE DISPLAY OPTIONS IN EFFECT ****

SSCH=ALL IO=ALL CCW=SI
SVC=ALL PI=ALL
EXT RNIO SRM RR DSP SLIP

**** GTF DATA COLLECTION OPTIONS IN EFFECT: ****

System resource manager events traced

**** GTF TRACING ENVIRONMENT ****

Release: SP4.2.0 FMID: HBB4420 System name: SYSTEM42
CPU Model: 3090 Version: FF Serial no. 170067

COMPONENT TRACE SUMMARY FORMAT

SYSNAME(SYSTEM41)
COMP(SYSRSM)
**** 07/23/90

MNEMONIC ENTRY ID TIME STAMP DESCRIPTION

-------- -------- --------------- -----------
02. XEPEXIT 00000002 14:18:40.000001 External Entry Point Exit
FUNC1... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... EDWTR1 ASID1... 0014 PLOCKS.. 00000000 CPU.... 0001
JOBN2... EDWTR1 ASID2... 0014 RLOCKS.. 00000000
SRM ASCB.... 00FD2E00 CPU..... 0001 JOBN.... *MASTER*
R15..... 00000000 R0...... 00010005 R1...... 00000000
01. GMT-07/23/90 14:18:40.120000 LOC-07/23/90 14:18:40.120000

02. XEPENTRY 00000001 14:18:40.130594 External Entry Point Entry

FUNC1... GENIOCMP General I/O Completion
JOBN1... JES2 ASID1... 0012 PLOCKS.. 08000081 CPU.... 0001
JOBN2... *ALL* ASID2... FFFE RLOCKS.. 08000000
SRM ASCB.... 00FD2E00 CPU..... 0001 JOBN.... *MASTER*
R15..... 00000000 R0...... 00010005 R1...... 00000000
01. GMT-07/23/90 14:18:40.142505 LOC-07/23/90 14:18:40.142505

SRM ASCB.... 00FD2E00 CPU..... 0001 JOBN.... *MASTER*

R15..... 00000000 R0...... 00010005 R1...... 00000000
01. GMT-07/23/90 14:18:40.814690 LOC-07/23/90 14:18:40.814690
02. PAGEA2R 0000001D 14:18:40.891890 Page Request Auxiliary to Real
FUNC1... GENIOCMP General I/O Completion
FUNC2... FLTAEPAG Enabled Addr Space Page Faults
JOBN1... JES2 ASID1... 0012 PLOCKS.. 08004081 CPU.... 0001
JOBN2... EDWTR1 ASID2... 0014 RLOCKS.. 08004000
SRM ASCB.... 00FD2E00 CPU..... 0001 JOBN.... *MASTER*
R15..... 00000000 R0...... 00010005 R1...... 00000000
01. GMT-07/23/90 14:18:40.901011 LOC-07/23/90 14:18:40.901011
02. XEPEXIT 00000002 14:18:40.952534 External Entry Point Exit
FUNC1... GENIOCMP General I/O Completion
JOBN1... JES2 ASID1... 0012 PLOCKS.. 08004081 CPU.... 0001
JOBN2... *ALL* ASID2... FFFE RLOCKS.. 08004000
02. XEPENTRY 00000001 14:18:40.964644 External Entry Point Entry
FUNC1... PGFIX Page Fix
JOBN1... EDWTR1 ASID1... 0014 PLOCKS.. 80000001 CPU.... 0001
JOBN2... EDWTR1 ASID2... 0014 RLOCKS.. 80000000
.
.
.

– Explanation
The output from the MERGE subcommand begins with a numbered list of
CTRACE and GTFTRACE subcommands that were input to MERGE. In the
trace output, these numbers appear in the first two columns to identify each
formatted trace entry with the trace subcommand that produced it. In the
example:
- 01. identifies a GTF trace entry

Chapter 5. IPCS subcommands 211

MERGE and MERGEEND subcommands

- 02. identifies an RSM component trace entry

The number for a component trace entry is on the first line of the entry. The
number for a GTF entry is on the time-stamp line at the end of the entry.

NAME subcommand — translate an STOKEN

Use the NAME subcommand to identify the address space, data space, or subspace
related to an STOKEN, and return the ASID and name associated with the space.

IPCS can identify the data space for an STOKEN if the data space is accessible in
the dumped environment; storage from the data space does not need to be
dumped to enable the identification.
v Related subcommands
– SELECT
v Syntax

NAME STOKEN(value)

[ LIST | NOLIST]
[ CLIST (QUALIFICATION(variable-name)) ]
[ DIALOG (QUALIFICATION(variable-name)) ]
[ REXX (QUALIFICATION(variable-name)) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameter
STOKEN(value)
Specifies the 8-byte STOKEN value of the address space, data space, or
subspace you want to identify. When you specify STOKEN, use the IPCS
rules for expressing general values; see “General values” on page 10.
LIST or NOLIST
LIST indicates that a report is to be generated. LIST is the default. NOLIST
suppresses the generation of a report.
CLIST(QUALIFICATION(variable-name))
DIALOG(QUALIFICATION(variable-name))
REXX(QUALIFICATION(variable-name))
Specifies where IPCS is to store the unedited value of STOKEN.
variable-name specifies the name of the variable into which the information
is stored. If the token cannot be successfully resolved by the NAME
subcommand, no change is made to the specified command procedure
variable.
CLIST directs that the value be stored in CLIST variable storage.
DIALOG directs that the value be stored in ISPF function pool dialog
variable storage.

212 z/OS MVS IPCS Commands

 NAME subcommand

REXX directs that the value be stored in REXX variable storage.

v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the NAME subcommand.
v Example: Obtain the name of the address space, data space, or subspace
associated with the hexadecimal STOKEN value, 11223344 55667788.
– Action
COMMAND ===> name stoken(x’11223344 55667788’)
– Result
NAME produces a listing that displays the address space, data space, or
subspace associated with the hexadecimal STOKEN value, 11223344 55667788.

NAMETOKN subcommand — display the token from a name/token pair

Use the NAMETOKN subcommand to obtain the token from a name/token pair in
a dump. Specify the name and the level of the name/token pair; in response,
NAMETOKN returns the following:
v The token data
v Whether the name/token pair is persistent
v Whether an authorized program created the name/token pair
v The address space identifier (ASID) for the address space associated with the
name/token pair
v Syntax

NAMETOKN data-descr

{ NAME((name)) }
[ LIST | NOLIST]
[ CLIST (TOKEN(variable-name) ) ]
[ DIALOG (TOKEN(variable-name) ) ]
[ REXX (TOKEN(variable-name) ) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See
“SETDEF subcommand — set defaults” on page 262.
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
data-descr
Describes the level of the name/token pair. The data description parameter
consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.

Chapter 5. IPCS subcommands 213

NAMETOKN subcommand

To retrieve the token from a task-level name/token pair, specify a TCB on

data-descr. For example:
NAMETOKN TCB65A NAME((TASKLEV_NAME_003))
NAMETOKN 0F8640. STRUCTURE(TCB) ASID(65) NAME((TASKLEV_NAME_003))
To retrieve an primary- or home-address-space-level name/token pair,
specify an ASCB on data-descr. For example:
NAMETOKN ASCB65 NAME((ASCBLEV_NAME_003))
NAMETOKN 0F2200. STRUCTURE(ASCB) NAME((ASCBLEV_NAME_003))
If you specify a data-descr other than an ASCB or TCB, NAMETOKN
assumes the token you want to retrieve is from a system-level name/token
pair. For example:
NAMETOKN 0 NAME((SYSTLEV_NAME_003))
NAMETOKN CVT NAME((SYSTLEV_NAME_003))
If you do not specify a data-descr parameter, NAMETOKN assumes the token
you want to retrieve is from a system-level name/token pair.
NAME((name))
Specifies the name to be translated. NAMETOKN treats all text inside the
parentheses, including blanks, literally. Enclose the name in double
parentheses.
If the name contains non-printing hexadecimal characters or lowercase
EBCDIC characters, then specify the name using hexadecimal characters. For
example:
NAMETOKN NAME((X’007D3A23’))
In this case, NAMETOKN does not treat the apostrophes and the letter X
literally.
LIST or NOLIST
LIST indicates that a report is to be generated. LIST is the default. NOLIST
suppresses the generation of a report.
CLIST(TOKEN(variable-name))
DIALOG(TOKEN(variable-name))
REXX(TOKEN(variable-name))
Specifies where IPCS is to store the unedited value of the token associated
with the name. variable-name specifies the name of the variable into which
the information is stored. If the token cannot be successfully resolved by the
NAMETOKEN subcommand, no change is made to the specified command
procedure variable.
CLIST directs that the value be stored in CLIST variable storage.
DIALOG directs that the value be stored in ISPF function pool dialog
variable storage.
REXX directs that the value be stored in REXX variable storage.

Note: Many binary values can produce unintended results when placed into
a CLIST variable. Only names associated with fully-printable EBCDIC tokens
should be handled by a CLIST. Command procedures that need to handle
arbitrary token values should be written using ISPF DIALOG or REXX
services.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the NAMETOKN subcommand.

214 z/OS MVS IPCS Commands

 NAMETOKN subcommand

v Example 1: Retrieve a system-level token from the name/token pair

SYSTLEV_NAME_003.
– Action
COMMAND ===> NAMETOKN CVT NAME((SYSTLEV_NAME_003))
– Results
The following output is produced.
System level
TOKEN.... SYSTLEV_NAME_003_token
NAME..... SYSTLEV_NAME_003_name
ASID..... 000F
Persistent
Created by authorized program
v Example 2: Obtain the logrec data set name by retrieving a system-level token
from the name/token pair DSNLOGREC. This example has 5 actions.
– Action 1
In the IPCS dialog, specify your dump data set and options.
– Action 2
In the IPCS primary menu, choose the COMMAND option. In the
COMMAND panel, enter:
===> NAMETOKN 0 NAME((DSNLOGREC))
– Results
The following NAMETOKN output is produced.
System level
TOKEN.... 01CE0020 0100002C 00000000 00000000
NAME..... DSNLOGREC
ASID..... 0010
Persistent
Created by authorized program
– Explanation
The fields in the output contain:
- Field 1: Address of area that contains the name of the logrec data set. The
data set name field is 44 bytes.
- Field 2:
v Byte 1: Version
v Byte 2: Reserved
v Bytes 3 and 4: Length of data area pointed to by field 1
- Field 3: Reserved
- Field 4: Reserved
– Action 3
Browse your dump data set to look at the address in the NAMETOKN
output.
– Result
ASID(X’0010’) is the default address space
PTR Address Address space Data type
00001 00000000 ASID(X’0010’) AREA
Remarks:
– Action 4
Add a pointer entry that has the address from field 1 in the NAMETOKN
output.
– Results

Chapter 5. IPCS subcommands 215

NAMETOKN subcommand

ASID(X’0010’) is the default address space

PTR Address Address space Data type
00001 00000000 ASID(X’0010’) AREA
Remarks:
s0002 01CE0020 ASID(X’0010’) AREA
Remarks:
– Action 5
Select a new pointer to obtain a display of the logrec data set name.
– Results
01CE0020 E2E8E2F1 4BD3D6C7 D9C5C340 40404040 | SYS1.LOGREC |
01CE0030 TO 01CE004F (X’00000020’ bytes)--All bytes contain X’40’, C’ ’

NOTE subcommand — generate a message

Use the NOTE subcommand to direct messages to the IPCSPRNT data set,
IPCSPDS data set, your terminal, or all three, and to control spacing and
pagination.

The maximum length of the message depends on its destination:

v Terminal display: The message is truncated to 250 characters.
v Print output data set: The message is truncated to the data set's logical record
length, minus 5.
v Print output partitioned data set: The message is truncated to the data set’s
logical record length, minus 5.

Thus, a message may be truncated to a different length for each destination.

NOTE directs the message to the IPCSPRNT data set, IPCSPDS data set, your
terminal, or all three, depending on the PRINT, PDS, and TERMINAL parameters.
If you omit the PRINT, PDS, and TERMINAL parameters, NOTE uses the current
local defaults for these parameters.

You can also assign a message severity level, which determines whether the
message is sent to its destination. If the assigned message level is below the user's
current default FLAG setting (see the SETDEF subcommand), the NOTE
subcommand does not send the message. If the message level assigned to a
message equals or exceeds the default FLAG setting, the subcommand sends the
message.
v Syntax

216 z/OS MVS IPCS Commands

 NOTE subcommand

{ NOTE } [’text’]
{ N }
[CAPS | ASIS ]
[PAGE | NOPAGE ]
[ SPACE[(count)] ]
[ NOSPACE ]
[ OVERTYPE ]
[ TOC ([indentation | 1] [toc-text ]) | NOTOC ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ PDS | NOPDS ]
[ TEST | NOTEST ]

v Parameters
’text’
Specifies the text of the message, enclosed in apostrophes. If the message is
directed to a terminal, it is truncated to 250 characters. If it is directed to the
IPCSPRNT or IPCSPDS data set, it is truncated to that data set's logical
record length, minus 5. If you specify a null line in this parameter, IPCS
assumes a blank line.
If you omit this parameter, IPCS transmits no message but performs the
specified spacing or paging relative to the previous line on the terminal or in
the IPCSPRNT and/or IPCSPDS data sets.
CAPS or ASIS
Specifies if the message text is to be in uppercase or in its present form,
which may be in uppercase, lowercase, or a mix.
CAPS specifies that IPCS translate the message text to uppercase.
ASIS specifies that IPCS not translate the message text, but transmit it in its
present form.
If you use this subcommand in a CLIST, the message text is normally
translated to uppercase by the editor or by CLIST processing before the
message text is available to IPCS, regardless if you specify ASIS. If you want
to use the ASIS option on the NOTE subcommand:
– Ensure that the editor that you use stores mixed uppercase and lowercase
text in your CLIST data set.
– Ensure that your installation has installed TSO/E support for the
CONTROL ASIS statement. Insert CONTROL ASIS in your CLIST before
the first NOTE subcommand with ASIS. This allows the text that you
entered in the CLIST to be passed to the IPCS NOTE subcommand
without editing lowercase to uppercase.
If you omit both CAPS and ASIS, the default is CAPS.
PAGE or NOPAGE
Specifies if the message is to be printed on a new page or the current page.
PAGE specifies a new page. PAGE affects printed output only. If the message
is printed, NOTE precedes the message with a page eject. If the message is
displayed on a user's terminal, NOTE ignores the PAGE parameter.

Chapter 5. IPCS subcommands 217

NOTE subcommand

NOPAGE specifies that a new page not be forced before printing the
message.
If you omit both PAGE and NOPAGE, the default is NOPAGE.
SPACE[(count)]
NOSPACE
OVERTYPE
Specifies if blank lines are to be added before printing the message or if the
message is to overlay the previous message.
SPACE specifies the number of blank lines to be inserted before the message.
The count may be specified as a decimal number. If you specify a count
greater than PAGESIZE - 2 (as specified in the session parameters member),
IPCS uses PAGESIZE - 2. If this parameter causes a page eject, you may lose
1 or 2 blank lines.
If you specify SPACE but omit the count, it defaults to 1.
NOSPACE inserts no blank lines before the message. The message becomes
the next line in the output.
OVERTYPE overlays this message on the previous message. For example,
you may use this parameter to underscore all or part of the previous
message. The subcommand ignores this parameter if you specify no text or
if the output is directed to a terminal.
If you omit SPACE, NOSPACE, and OVERTYPE, the default is NOSPACE.
TOC [([indentation] [toc-text])]
NOTOC
Specifies if a table of content entry is to be generated when the message
associated with NOTE is routed to the IPCSPRNT data set. TOC specifies
that a table of contents entry is to be generated.
indentation
Indicates that the entry in the table of contents is to be indented.
Indentation is an integer from 1 through 4 and can be specified in
decimal (n), binary (B'n'), or hexadecimal(X'n') notation. The default
indentation is 1.
toc-text
One to 40 bytes of text that is to be associated with the table of contents
entry. The text can be enclosed in single quotation marks if you want.
The default toc-text is the text of the note, truncated to 40 characters
where necessary.

NOTOC specifies that no table of contents entry is to be generated. NOTOC

is the default.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the NOTE subcommand.

OMVSDATA subcommand — format z/OS UNIX data

Use the OMVSDATA subcommand to generate diagnostic reports about z/OS
UNIX System Services (z/OS UNIX) users and resources.
v Syntax

218 z/OS MVS IPCS Commands

 OMVSDATA subcommand

OMVSDATA

-------- Data Selection Parameters -------------------------

[ COMMUNICATIONS ]
[ FILE ]
[ IPC ]
[ PROCESS ]
[ STORAGE ]

-------- Report Type Parameters ----------------------------

[ DETAIL ]
[ EXCEPTION ]
[ SUMMARY ]

-------- Address Space Selection Parameters ----------------

[ ASIDLIST(asidlist) ]
[ USERLIST(userlist) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Data Selection Parameters

Use these parameters to limit the scope of the data in the report. IPCS produces
a report for each data selection parameter. If you omit a data selection
parameter, the default is PROCESS.
COMMUNICATIONS
Specifies that communication services information appears in the report.
FILE
Specifies that file systems information appears in the report.
IPC
Specifies that the report is to contain information about interprocess
communication for shared memory, message queues, and semaphores.
PROCESS
Specifies that information about all dubbed processes appears in the report.
The report includes information about serialization, signaling, and, if the
DETAIL parameter is also specified, open files.
STORAGE
Specifies that storage services information appears in the report.
v Report Type Parameters
Use these parameters to select the type of report. If you omit a report type
parameter, the default is SUMMARY.

Chapter 5. IPCS subcommands 219

OMVSDATA subcommand

DETAIL
Requests the detail report, which includes detailed information about the
data area selected.
EXCEPTION
Requests the exception report, which contains exceptional or unusual
conditions for the data area selected. The exception report contains
diagnostic information for IBM use.
SUMMARY
Requests a summary report for the data area selected.
v Address Space Selection Parameters
Use these parameters to obtain data from particular address spaces, which you
specify by their address space identifiers (ASIDs) or by the TSO/E user IDs
associated with the address space.
ASIDLIST(asidlist)
Specifies a list of ASIDs for the address spaces for which you want IPCS to
process the requested data.
The asidlist can be a single ASID, a range of ASIDs, or a list of
noncontiguous ASIDs, When you specify a range, separate the first and last
ASIDs in the range with a colon. When you specify a list, separate the list
members with commas.
An ASID can be 1 through 65535. An ASID can be expressed in the notation
X'nnn', F‘nnn’, or B'nnn'. An unqualified number is assumed to be fixed.
USERLIST(userlist)
Specifies a list of TSO/E user IDs associated with the address spaces for
which you want IPCS to process the requested data. The userlist can be a
single user ID or a list of user IDs. When you specify a list, separate the list
members with commas. For example:
USERLIST(userid)

USERLIST(userid,userid...,userid)
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the OMVSDATA subcommand.
v Example: See z/OS MVS Diagnosis: Reference for examples of the OMVSDATA
subcommand and its output.

OPCODE subcommand — retrieve operation code

Use the OPCODE subcommand to retrieve the mnemonic operation code
associated with an instruction.
v Syntax

220 z/OS MVS IPCS Commands

 OPCODE subcommand

OPCODE

-------- Data Selection Parameters ----------------------------

search-argument

-------- Result Distribution Parameters ----------------

[ CLIST(var-list) ]
[ DIALOG(var-list) ]
[ REXX(var-list) ]
[ LIST ]
[ NOLIST ]
[ SCREEN ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
search-argument
The first 2-12 hexadecimal digits of the instruction of interest. If less digits
are entered than needed to complete an instruction, trailing zero digits are
supplied. Excess digits are ignored.
CLIST(var-list)
DIALOG(var-list)
REXX(var-list)
Requests that the information retrieved be made available to a command
procedure or ISPF dialog. The syntax for var-list is as follows:

MNEMONIC(variable-name)

LIST
NOLIST
SCREEN
Specifies whether the information retrieved is to be displayed and, if it is,
whether it is to appear as part of a line mode report or as an ISPF message
on the logical screen.
v Example: In z/OS V1R4, IPCS enhances the display of the multi-byte operation
codes associated with z/Architecture. The split-opcode instructions beginning
with E3, EB, or ED are displayed as follows:
Command ===> opcode e303

00000000 000A0000 000130E1 00000000 00000000 | ...............

00000010 00FC6FC0 00000000 00000000 00000000 | ..?{...........

00000020.:3F.--All bytes contain X’00’

The response to the command opcode e303 is as follows:
BLS18350I Split operation code X’E303’ occupies bytes 0 and 5

Mnemonic for X’E303’ is LRAG

Chapter 5. IPCS subcommands 221

OPEN subcommand

OPEN subcommand — prepare resources for use by IPCS

Use the OPEN subcommand to prepare one or more resources for use by IPCS.
You can prepare:
v One or more source data sets containing dumps or traces
v Active storage, to be used as the source for IPCS processing
v A print data set with the ddname IPCSPRNT or a substitute name
v A table of contents (TOC) data set with the ddname IPCSTOC or a substitute
name

See z/OS MVS IPCS User's Guide for information about using the OPEN
subcommand for the print and TOC data sets.
v Syntax

OPEN
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dslist) | DATASET(dslist) ]
[ FILE(ddlist) | DDNAME(ddlist) ]
[ PATH(path-name ...) ]
[ DEFAULT ]
[ CONDITIONALLY | UNCONDITIONALLY ]
[ PRINT [(options) ] ]

-------- SETDEF-Defined Parameter -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ TEST | NOTEST ]
[ CONFIRM | NOCONFIRM ]

v Parameters
ACTIVE or MAIN or STORAGE
DSNAME(dslist) or DATASET(dslist)
FILE(ddlist | IPCSDDIR) or DDNAME(ddlist)
Specifies the source to be prepared for use. If one of these parameters in not
specified, IPCS opens the current source. IPCS opens the data sets in the
order in which they are specified in the OPEN subcommand.
ACTIVE, MAIN, or STORAGE directs IPCS to prepare to access central
storage as the source.
DSNAME or DATASET specifies the name of one or more cataloged data
sets to be opened.
FILE or DDNAME specifies the ddname of one or more data sets to be
opened.
When specifying more than one data set or ddname, separate the names
with commas or blanks. When specifying a range of ddnames, separate the
first and last ddname with a colon.
OPEN FILE(IPCSDDIR) indicates that you want to open the data set for
your dump directory. You have to specify IPCSDDIR explicitly; specifying a
range of ddnames does not include the dump directory. For further
information about default values and restrictions for dump directories, see
the CLOSE subcommand.
PATH(path-name ...)
Specifies one or more z/OS UNIX file paths to be processed. The

222 z/OS MVS IPCS Commands

 OPEN subcommand

PATH(path-name ...) option permits a list of path names to be processed in

addition to any ddnames and dsnames listed on the subcommand.
Partially-qualified path names may be used.
DEFAULT
Specifies that the final source listed in the subcommand is to become the
current source. If the subcommand specifies a data set name with a
password, the data set name and password become the name of the current
source.
IPCS changes the current source in both the local and global defaults. If you
omit this parameter, or if the subcommand fails, the current source is not
changed in the defaults.
CONDITIONALLY or UNCONDITIONALLY
Determines how IPCS should handle a data set that is already open when
the OPEN subcommand is processed.
For CONDITIONALLY, IPCS does not issue messages about the data being
open.
For UNCONDITIONALLY, IPCS issues messages about the data set being
open. UNCONDITIONALLY is the default.
PRINT[(options)]
Specifies the IPCS print data set. The syntax for options is as follows:

[ FILE(ddname|IPCSPRNT ]
[ DDNAME(ddname|IPCSPRNT ]
[ TITLE(’text’ [’time-stamp’]) ]
[ TOC(FILE(ddname|IPCSTOC)) ]
[ CAPS ]
[ ASIS ]
[ CHARS(DUMP) ]
[ DISP|EXTEND|REUSE ]

If you omit CAPS, ASIS or CHARS(DUMP), ASIS is the default.

If the logical record length for the IPCS print data set will not accommodate
the text of the title plus a time stamp and a page number, the text is
truncated.
FILE(ddname|IPCSPRNT) or DDNAME(ddname|IPCSPRNT)
Specifies that the designated ddname be opened as the IPCS print data
set. If this parameter is omitted, FILE(IPCSPRNT) is used.
TITLE(text[time-stamp])
Specifies the title of the dump. The text appears on each page produced
from the IPCS print data set. Enclose the text in single quotation marks.
If text is omitted, IPCS uses the title extracted from the default dump
data set. When processing multiple dumps during a single session, IPCS
uses the default titles for each new dump encountered.
If IPCS cannot use the title from the default data set, but a userid is
available, IPCS places on each page “IPCS PRINT LOG FOR userid” and
the date and time that IPCS began problem analysis. If the userid is
unavailable, “IPCS PRINT LOG” appears.
Restriction: When using IPCS in the background, the title will not
contain the phrase “FOR userid” unless you use the TSO/E TMP and
specify a USER parameter in the JCL JOB statement.

Chapter 5. IPCS subcommands 223

OPEN subcommand

The time-stamp is the time that a problem occurred rather than the time
that the problem analysis started.
Enclose the time stamp in single quotation marks.
If time-stamp is omitted, IPCS provides a date and time on the first line
of each printed page indicating the time that the problem analysis
started.
TOC(FILE(ddname|IPCSTOC))
Specifies that the data set be opened as the IPCS table of contents (TOC).
If TOC is omitted, FILE(IPCSTOC) is used.

Note: The TOC data set must be different from the PRINT data set in
order for both data sets to contain the correct data.
CAPS
Directs IPCS to change lowercase EBCDIC letters to uppercase before
writing each line to the print and table of contents data sets.
ASIS
Directs IPCS to write text exactly as entered (uppercase and lowercase
letters) to the data sets.
CHARS(DUMP)
Directs IPCS to format any text transmitted to the data sets in the IBM
3800 CHARS(DUMP) font. Use this option only for:
– Data sent to the print or TOC data sets, or both
– Data that has a data-type attribute of AREA

Note: AREA is the IPCS default attribute parameter when a literal

storage address is used and is the data-type associated with
IPCS-defined symbols such as CSA.
DISP|EXTEND|REUSE
Permits an IPCS user, tailored dialogs, or command procedures to defer
decision to overlay or extend a print file until a transaction that will use
the file is requested.
DISP
Open the print and table of contents files with no attempt to
influence positioning.
EXTEND
Requests that data management add additional records to the end of
the print and table of contents files.
REUSE
Requests that data management reuse the print and table of contents
files to contain new reports.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the OPEN subcommand.
v Example 1: Open the IPCS TOC data set.
– Action
COMMAND ===> open print (toc(file(mytoc)) caps)
– Result
File mytoc contains entries, which are written in uppercase.
v Example 2: Open a print data set and give it a title.
224 z/OS MVS IPCS Commands
 OPEN subcommand

– Action
COMMAND ===> open print (title (’A Troubled Dump’ ’12-07-81’))
– Result
‘A Troubled Dump 12-07-81’ appears on each page of the IPCS default print
data set (IPCSPRNT).

PATCH subcommand
Use the PATCH subcommand to repair data residing in a RECFM=F or
RECFM=FBS data set or to manage the list of patches in effect for a dump.

Patching may impact IPCS performance and is intended to be used very sparingly.
The reason that a patching capability has been included is the following scenario:
1. You attempt to run a high level report against a dump. The report is important
for your analysis.
2. The report writer encounters a block that appears to be damaged. Rather than
using the contents of the damaged block and risking the production of a
misleading report, the report writer identifies the block and the damage
detected.
3. You examine the damaged block, verify that its damage is not the root problem
that you sought, and are able to determine values that repair damage to it.
4. You use the PATCH subcommand to identify the repairs to IPCS. IPCS does not
alter the dump data set in any way. The alterations are stored in your dump
directory.
Patching storage that IPCS knows can be seen from multiple perspectives, such
as both common virtual storage and real storage visible to each CPU in the
dumped system, affects all perspectives.
v Restrictions
– IPCS may access dump data before application of a patch, recording
conclusions regarding that data in the dump directory before application of a
patch. The PATCH subcommand does not attempt to locate and alter any
such data. Some of this data may be affected using other subcommands such
as
- DROPDUMP RECORDS(TRANSLATION)
- DROPMAP
- DROPSYM
– The current implementation of PATCH support directly uses data in dump
records for most information associated with DISPLAY(MACHINE) output
and the related data that may be extracted from a dump using the
EVALUATE subcommand. Processing of storage by EVALUATE does honor
PATCH requests.
– Storage may be added to what was dumped, such as from ASID(75), through
PATCH processing, but PATCH will not attempt to identify the absolute or
real storage locations where that storage would have resided in the dumped
system. If this is important to your analysis, you must use PATCH to add it
from all perspectives important to your analysis.
v Qualifier
The following qualifiers distinguish the functions performed by the PATCH
subcommand:
Qualifier
Function

Chapter 5. IPCS subcommands 225

PATCH subcommand

ADD Causes the PATCH subcommand to store a new patch. See “Adding or
replacing a patch” for more information. Existing, overlapping patches
are considered to be an error and cause the new patch to be rejected.
DELETE
Causes the PATCH subcommand to delete patches. See “Deleting
patches” on page 227 for more information.
LIST Causes the PATCH subcommand to list patches. See “Listing patches” on
page 227 for more information.
REPLACE
Causes the PATCH subcommand to store a patch, replacing one or more
existing ones whose descriptions overlap the new one. See “Adding or
replacing a patch” for more information. At least one existing,
overlapping patch is expected. If there is none, it is considered to be an
error, and the new patch is rejected.
STORE
Causes the PATCH subcommand to store a patch, replacing any existing
ones whose descriptions overlap the new one. See “Adding or replacing
a patch” for more information.

Adding or replacing a patch

v Syntax

PATCH { ADD | REPLACE | STORE }

general-value
[ data-descr ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
[ TEST | NOTEST ]

v Parameters
ADD
REPLACE
STORE
Indicates whether the patch may replace existing patches that describe
overlapping storage.
general-value
Specifies the patch using general value notation.
data-descr
Specifies the data description parameter, which consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
The following applies to PATCH ADD and PATCH REPLACE only:

226 z/OS MVS IPCS Commands

 PATCH subcommand

– Patch uses the address space, address and offset to determine the origin
of the storage to be patched. The number of bytes affected by the
patching request are indicated by the general value entered.
– If you omit the ADDRESS parameter, the default for the ADD and
REPLACE options of the PATCH subcommand is ADDRESS(X), the most
recently accessed address.

Deleting patches
v Syntax

PATCH DELETE

[ data-descr ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
[ TEST | NOTEST ]

v Parameters
DELETE
Indicates that patches affecting the storage described by data-descr are to be
deleted.
data-descr
Specifies the data description parameter, which consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
The following applies to PATCH DELETE only:
– All patches affecting the range of storage described are deleted.
– If you omit the ADDRESS parameter, the default for PATCH DELETE is
ADDRESS(X), the most recently accessed address.

Listing patches
v Syntax

PATCH LIST
[ data-descr ]
[ DETAIL ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
[ TEST | NOTEST ]

v Parameters
LIST
Indicates that patches affecting the storage described by data-descr are to be
listed.

Chapter 5. IPCS subcommands 227

PATCH subcommand

data-descr
Specifies the data description parameter, which consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
The following applies to PATCH LIST only:
– All patches affecting the range of storage described are listed.
– If you omit the ADDRESS parameter, the default for PATCH LIST is all
patches.
DETAIL
Requests a detailed description of the data supporting patches.

Return codes
v Return Codes
The PATCH subcommand generates standard IPCS return codes.
Code Meaning
X'00' Normal completion of the request.
X'0C' Request not completed for reasons related to user actions. Examples of
such actions are:
– Specifying PATCH ADD processing for a location where a patch has
already been applied.
– Use of the TSO attention mechanism to terminate PATCH processing
when IKJPARS solicits operand correction.
X'10' Request not completed because of problems with the IPCS execution
environment. Examples of such problems are:
– Insufficient virtual storage to complete the request.
– An I/O error when accessing the dump directory.
IPCS transmits error messages, when possible, to identify the underlying
cause of this return code.

PROFILE subcommand — set preferred line and page size defaults

Use the PROFILE subcommand to establish defaults for reports generated under
IPCS:
v A preferred line size
v Preferred lines per printed page

The defaults you specify with PROFILE are recorded in your dump directory and
remain in effect until you change them. You can issue PROFILE at any time during
an IPCS session to view your default values. To change one or more of your
defaults, enter the PROFILE subcommand with the parameters for the defaults.

Except for NOPAGESIZE, a newly established default is used for both the current
session and any subsequent sessions in which you use the same dump directory.
NOPAGESIZE does not become effective until the beginning of your next IPCS
session.

228 z/OS MVS IPCS Commands

 PROFILE subcommand

Unlike the defaults set by a SETDEF subcommand, the PROFILE defaults cannot
be overridden by parameters on other IPCS subcommands. The defaults can be
changed only by entering a PROFILE subcommand.

The PROFILE-defined defaults shipped with IPCS are:

/*---------------------- IPCS Profile Data ------------------------*/

PROFILE NOEXCLUDE /* No dump analysis excluded */
PROFILE NOLINESIZE /* Limit for variable-width reports */
PROFILE NOPAGESIZE /* Line limit for print file pages */
PROFILE STACK(NODUPLICATES) /* Duplicate stack entry screening */

Figure 22. PROFILE-Defined Defaults

Note:
1. The NOLINESIZE parameter is the equivalent to a line size of 250 characters
per line. Variable-width reports can appear somewhat different when the
output is directed to the terminal or the IPCS print data set.
2. The NOPAGESIZE parameter causes IPCS to use the PAGESIZE supplied in the
IPCS session parameters member. If PAGESIZE is not supplied in the session
parameters member, IPCS uses a default of 60 lines per page.

See z/OS MVS IPCS User's Guide for information about using the PROFILE
subcommand to set print data set report defaults,
v Related subcommands
– ANALYZE
– EVALPROF
– OPEN
– WHERE
v Syntax

{ PROFILE } [ EXCLUDE(name[ :name]...) | NOEXCLUDE ]

{ PROF } [ LINESIZE(nnn) | NOLINESIZE ]
[ PAGESIZE(nnn) | NOPAGESIZE ]
[ LIST | NOLIST ]
[ STACK {(DUPLICATES | NODUPLICATES)} ]

-------- SETDEF-Defined Parameter --------------------------

Note: You can override the following SETDEF parameter.
See “SETDEF subcommand — set defaults” on page 262.
[TEST | NOTEST ]

v Parameters
EXCLUDE(name[:name]...) or NOEXCLUDE
Controls optional analysis performed by IPCS.
Using a single name explicitly designates a single type of analysis. Names
can be 1-31 characters in length. They must begin with a letter or the
characters $, @, or #. The same characters can be used in the remaining
positions and decimal digits.
You are not limited to the names specified in Table 12. If you designate a
name that is not supported by the current release, the name is recorded but
has no effect on processing by IPCS.

Chapter 5. IPCS subcommands 229

PROFILE subcommand

Using name:name describes all types of analysis that collate within the
range described. For example, the range A:B, excludes all types of analysis
for which the name begins with either the letter A or the letter B.
Any list that you enter will be edited before being displayed by the LIST
option of this subcommand or by the EVALPROF subcommand. The edited
list is shown after it has been sorted and edited for efficient searching
incorporating merging overlapping ranges. The implementation limits this
list to 48 ranges.
Table 14 describes the naming conventions for the names supported by z/OS
R7 MVS IPCS.
Table 14. EXCLUDE parameter naming conventions
Name Meaning
ANALYZEexit-name The combination of the prefix ANALYZE and a suffix
matching the name of an ANALYZE exit excludes that
exit from the process of gathering contention data. This
pertains to all places within IPCS where contention
analysis may be performed, not only the ANALYZE
subcommand.
WHERECSVCOMMON Excludes WHERE processing that forces common area
modules into the IPCS storage map before searching for
associations.
WHERECSVPRIVATE Excludes WHERE processing that forces private area
modules into the IPCS storage map before searching for
associations.
WHEREIGVPRIVATE Excludes WHERE processing that forces private area
pages for virtual storage manager subpools into the
IPCS storage map before searching for associations.

LINESIZE(nnn) or NOLINESIZE
Controls the width of variable-width reports generated by IPCS. IPCS.
LINESIZE limits the width to nnn. Specify nnn in decimal ([+]nnn),
hexadecimal (X'['X'+'X']xxx'), or binary (B'['B'+'B']bbb') notation. The
minimum line size is 78 and the maximum is 250.
If variable-width reports are sent to any medium that is narrower than nnn
characters, IPCS limits the output lines of the report to the width of the
medium or 78 characters, whichever is larger.
NOLINESIZE specifies that variable-length reports use the full width of the
medium to which they are written.
NOLINESIZE is equivalent to LINESIZE(250). NOLINESIZE is the default.
PAGESIZE(nnn) or NOPAGESIZE
Controls the number of lines per page in reports generated by IPCS.
PAGESIZE specifies the number of lines per page as nnn. Specify nnn in
decimal ([+]nnn), hexadecimal (X'['X'+'X']xxx'), or binary (B'['B'+'B']bbb')
notation. A nnn less than 3 is equivalent to NOPAGESIZE. The maximum
page size is 231-1.
IBM recommends that you specify the number of lines that will fit on the
forms typically used at your installation.

230 z/OS MVS IPCS Commands

 PROFILE subcommand

IPCS can generate normal, ascending page numbers if the printed output
consumes less than 232 lines of output medium. If you use a large
PAGESIZE, the page number will wrap back to zero once the maximum is
reached.
IPCS obtains the number of lines per page for the IPCS print output data set
by checking the following in order:
1. The PAGESIZE specified on the PROFILE subcommand.
2. The PAGESIZE specified in the session parameters member for the IPCS
session. (If PROFILE NOPAGESIZE is in effect, IPCS checks here first.)
3. When neither of the preceding is available, IPCS uses a default of 60
lines per page.
NOPAGESIZE specifies that a default not be established for the number of
lines per page for the IPCS print data set. IPCS uses the PAGESIZE specified
in the session parameters member or a default of 60 lines per page.

Note: Entering PROFILE NOPAGESIZE does not alter the default for your
current IPCS session. It becomes effective at the beginning of your next IPCS
session.

NOPAGESIZE is the default.

LIST or NOLIST
Specifies if IPCS is to display your current PROFILE defaults on your
terminal regardless of the current value for the TERMINAL parameter.
LIST specifies that the subcommand is to display all of the default values
and parameters that are in effect. For an example, see Figure 22 on page 229.
NOLIST specifies that the subcommand not display the default values and
parameters.
If you enter PROFILE without any parameters, the default is LIST. If you
omit LIST and NOLIST but specify any other parameter, the default is
NOLIST.
STACK(DUPLICATES | NODUPLICATES)
Controls duplication of stack entries for your current IPCS session and for
future IPCS sessions that use the same dump directory.
STACK(DUPLICATES) allows stack entries to be duplicated.
STACK(NODUPLICATES) suppresses duplication of stack entries.

Note:
1. To be considered a duplicate, a stack entry must have all the same
attributes, including remarks, as an existing entry.
2. Specifying NODUPLICATES will not affect duplicate entries created as a
result of:
– The EQUATE subcommand and primary commands
– The RUNCHAIN subcommand
– The I and R line commands issued from the IPCS dialog BROWSE
option pointer panel
– From the BROWSE option pointer panel, editing that overstrikes a
pointer stack entry
3. No messages result when duplicate entries are suppressed. The request is
considered satisfied without action if the entry already exists.

Chapter 5. IPCS subcommands 231

PROFILE subcommand

v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the PROFILE subcommand.
v Example: Change your line, page, and stack defaults.
– Action
COMMAND ===> profile linesize(78) pagesize(90) stack(duplicates) list
– Result
You normally use a graphics terminal with a physical screen width of 80
characters but with an actual display screen of 78 characters. LINESIZE (78)
tells IPCS to produce variable-width reports with a line length of 87,
regardless of whether the report output is directed to your terminal or to the
print data set.
Each printed page contains 90 lines of data.
By specifying STACK(DUPLICATES), you authorize IPCS to add entries to the
pointer stack that have exactly the same attributes as other entries in the
pointer stack.
The LIST parameter displays the following:
/*---------------------- IPCS Profile Data ------------------------*/
PROFILE LINESIZE(78) /* Limit for variable-width reports */
PROFILE PAGESIZE(90) /* Line limit for print file pages */
PROFILE STACK(DUPLICATES) /* Duplicate stack entry screening */

RENUM subcommand — renumber symbol table entries

Use the RENUM subcommand to renumber all address pointer entries in the
symbol table in your dump directory. IPCS renumbers the entries in ascending
order, from Z1 to Z99999.

The symbol table is part of a source description. The source description is in the
dump directory allocated with ddname IPCSDDIR and is your current dump
directory. The current dump directory is your user dump directory or, for users
with write access authority, might be the sysplex dump directory.
v Related subcommands
– EQUATE
– DROPSYM
– LISTSYM
– STACK
v Syntax

{RENUM } [ SUMMARY | NOSUMMARY ]

{REN }

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE| MAIN | STORAGE ]
[ DSNAME(dsname)| DATASET(dsname) ]
[ FILE(ddname)| DDNAME(ddname) ]
[ PATH(path-name) ]
[ TEST | NOTEST ]

v Parameters

232 z/OS MVS IPCS Commands

 RENUM subcommand

SUMMARY or NOSUMMARY
SUMMARY specifies that a summary of RENUM's processing is to be
produced. If so, IPCS issues one of the following comments (where n is a
number):
– The stack contains no entries.
– The stack contains 1 entry, none was renumbered.
– The stack contains 1 entry, 1 was renumbered.
– The stack contains n entries, 1 was renumbered.
– The stack contains n entries, n of which was renumbered.
– The stack contains n entries, none of which was renumbered.
NOSUMMARY specifies that a processing summary is to be suppressed. The
NOSUMMARY parameter is useful to turn off summary messages when the
subcommand is invoked within a CLIST or REXX exec.
ACTIVE or MAIN or STORAGE
DATASET(dsname) or DSNAME(dsname)
FILE(ddname) or DDNAME(ddname)
Specifies the source of the source description containing the symbols. If one
of these parameters is not specified, the source is your current source.
ACTIVE, MAIN, or STORAGE specifies central storage as the source.
DSNAME or DATASET specifies the name of a cataloged data set as the
source.
FILE or DDNAME specifies the ddname for a data set as the source.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the RENUM subcommand.
v Example: Renumber the address pointer entries in the symbol table.
– Action
COMMAND ===> renum
– Result
The subcommand produces the following summary output line:
The stack contains 4 entries, 3 of which were renumbered

RSMDATA subcommand — analyze real storage manager data

Use the RSMDATA subcommand to generate reports about the attributes and
status of the real storage manager (RSM) at the time of a dump. This subcommand
produces the following types of reports:
v Address spaces report
v Common Pools
v Data-in-virtual mapped range report
v Data space report
v Exception report
v Execution status report
v Expanded storage report
v High virtual common
v High virtual page report
v High virtual shared data report

Chapter 5. IPCS subcommands 233

RSMDATA subcommand

v Real frames report

v RSM requests report
v RSM shared data report
v Subspace report
v Summary report
v Trace
v Virtual pages report

Address space selection, data selection, and report type parameters limit the scope
and extent of the information that appears in a report.
v Syntax

234 z/OS MVS IPCS Commands

 RSMDATA subcommand

RSMDATA

-------- Report Type Parameters -----------------------------

{ ADDRSPACE }
{ DIVMAP }
{ DSPACE }
{ EXCEPTION }
{ EXECUTION }
{ EXPFRAME }
{ HIGHVIRTUAL}
{ HVSHRDATA }
{ HVCOMMON }
{ REALFRAME }
{ RSMREQ }
{ SHRDATA }
{ SUBSPACE }
{ SUMMARY }
{ VIRTPAGE }

-------- Data Selection Parameters -------------------------

[ COMMON ]
[ DATASPACES ]
[ DETAIL ]
[ HVCOMM ]
[ HVSHARED ]
[ PERMCOMM ]
[ RANGE(rangelist) ]
[ SAVEAREA(address) ]
[ SHARED ]
[ SHORT ]
[ STATUS(statuslist) ]
[ TOKEN(token) ]
[ TOTONLY ]

-------- Address Space Selection Parameters ----------------

[ ALL ]
[ ASIDLIST(asidlist) ]
[ CURRENT ]
[ ERROR ]
[ JOBLIST(joblist) | JOBNAME(joblist) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report type parameters

Use these parameters to select the type of report. Specify only one; if you specify
more than one, RSMDATA processes only the right-most parameter. If you omit
a report type parameter, the default is SUMMARY.
Some of the selection parameters do not apply to all reports. Matrix of report
type parameters and other parameters summarizes the parameters you can
specify with a given report.

Chapter 5. IPCS subcommands 235

RSMDATA subcommand

ADDRSPACE
Requests the RSM address spaces report. This report summarizes real
storage usage for specified address spaces. The report is sorted by ASID.
Usage note: The only data selection parameters that apply to this report are
STATUS, SHORT, and TOTONLY.
DIVMAP
Requests the data-in-virtual mapped range report. This report displays
information relating to areas of storage that are identified to data-in-virtual
and that have been mapped. The information is sorted by address space
identifier (ASID) and by the status of each data-in-virtual mapped range.
Usage note: The only data selection parameters that apply to this report are
STATUS and TOTONLY.
DSPACE
Requests the data space report. This report displays information about all
data spaces in the system. All installation-defined and RSM-defined data
spaces are summarized.
Usage note: The only data selection parameter that applies to this report is
TOTONLY.
EXCEPTION
Requests the RSM diagnostics report. This report verifies RSM global data
structures and generates information about areas that are in error. You can
also request verification of local data structures for specific address spaces
using address space selection parameters.
Usage note: The only data selection parameters that apply to this report are
DATASPACES and SAVEAREA.

Note: The EXCEPTION report might take an excessive amount of time to

run when one or both of these conditions is true:
– You specify more than 3 address spaces.
– You have specified DATASPACES and any of the specified address space
owns more than 3 data spaces.
You might consider submitting a batch job to obtain an EXCEPTION report
under these circumstances.
EXECUTION
Requests the RSM execution status report. This report contains information
for IBM internal use. IBM might ask you to run this report for use in
problem determination.
Usage note: The only data selection parameter that applies to this report is
SAVEAREA. Address space selection parameters do not apply to this report.
HVCOMMON
Requests the high virtual common report. This report displays the status of
high virtual common memory objects including owner, size, and status.
Usage note: The only selection parameter that applies to this report is
RANGE.
HIGHVIRTUAL
Requests the high virtual page report. This report identifies the page owner,
the location and status for virtual pages in the system that are above 2
Gigabytes, and a summary of the memory objects.

236 z/OS MVS IPCS Commands

 RSMDATA subcommand

Usage note: The only data selection parameters that apply to this report are
RANGE, STATUS, and TOTONLY.

Note: The VIRTPAGE report might take an excessive amount of time to run
when large ranges are specified.
HVSHRDATA
Requests the high virtual shared data report. This report provides
information about virtual storage above 2 gigabytes that is shared using the
IARV64 macro.
Usage note: The only data selection parameters that apply to this report are
RANGE and DETAIL.
REALFRAME
Requests the real frame report. This report displays information about each
frame's status, location, and current/most recent owner. The information is
sorted by the ASID of the current/most recent owner unless you specify the
ALL address space selection parameter. In this case the information is sorted
by frame number.
Usage note: The only data selection parameters that apply to this report are
COMMON, PERMCOMM, RANGE, SHARED, HVCOMM, HVSHARED,
STATUS, and TOTONLY.
RSMREQ
Requests the RSM requests report. This report summarizes asynchronous
RSM activity in the system or for a particular job. It identifies the requester,
lists the request's status, and identifies the requested pages for asynchronous
requests.
Usage note: The only data selection parameters that apply to this report are
COMMON, SHARED, HVCOMM, HVSHARED, STATUS, and TOTONLY.
SHRDATA
Requests the RSM shared data report. This report provides information
about the virtual storage locations that are defined as shared through the
IARVSERV macro.
Usage note: The only data selection parameters that apply to this report are
COMMON, STATUS, TOKEN, and TOTONLY.
SUBSPACE
Requests the subspace report. This report displays information about
subspaces in an address space. The information is sorted by ASID and,
within the address space, by the address at the lower limit of the range.
Usage note: The only data selection parameters that apply to this report are
RANGE and STATUS.
SUMMARY
Requests the RSM summary report and is the default. This report provides
statistics about system-wide real and auxiliary storage usage. It also contains
information about any unusual RSM conditions that exists in the dump.
Usage note: Data selection and address space parameters do not apply to
this report.
VIRTPAGE
Requests the virtual page report. This report identifies the page owner and
its location and status for virtual pages in the system.

Chapter 5. IPCS subcommands 237

RSMDATA subcommand

Usage note: The only data selection parameters that apply to this report are
COMMON, DATASPACES, PERMCOMM, RANGE, STATUS and TOTONLY.

Note: The VIRTPAGE report might take an excessive amount of time to run
when one or both of these conditions is true:
– You specify more than 3 address spaces.
– You have specified DATASPACES and any of the specified address space
owns more than 3 data spaces.
You might consider submitting a batch job to obtain a VIRTPAGE report
under these circumstances.
v Matrix of report type parameters and other parameters
The following two tables summarize for each report type use of address space
selection parameters and data selection parameters.

Report Type ALL COMMON DATASPACES DETAIL HVCOMM HVSHARED PERMCOMM

Parameter ASIDLIST
CURRENT
JOBLIST/
JOBNAME
ADDRSPACE X
DIVMAP X
DSPACE X
EXCEPTION X X
EXECUTION
HIGHVIRTUAL X
HVCOMMON
HVSHRDATA X
REALFRAME X X X X X
RSMREQ X X X X
SHRDATA X X
SUBSPACE X
SUMMARY
VIRTPAGE X X X X

Report Type RANGE SAVE AREA SHARED STATUS TOKEN TOTONLY SHORT
Parameter
ADDRSPACE X X X
DIVMAP X X
DSPACE X
EXCEPTION X
EXECUTION X
HIGHVIRTUAL X X X
HVCOMMON X
HVSHRDATA X
REALFRAME X X X X
RSMREQ X X X
SHRDATA X X X
SUBSPACE X X
SUMMARY X

238 z/OS MVS IPCS Commands

 RSMDATA subcommand

Report Type RANGE SAVE AREA SHARED STATUS TOKEN TOTONLY SHORT
Parameter
VIRTPAGE X X X

v Data selection parameters

Use these parameters to limit the scope of the data in the report.

Note: Common area data is not included when you specify ASIDLIST,
JOBNAME, or JOBLIST. You need to specify COMMON or PERMCOMM with
the report parameters that accept them if you want to see common area
resources in the report. High virtual shared data is not included when you
specify ASIDLIST, JOBNAME, or JOBLIST. You need to specify HVSHARED
with the report parameters that accept them if you want to see high virtual
shared resources in the report.
COMMON
Requests that any non-permanently-assigned common area page found in
CSA, SQA, PLPA, MLPA, or common disabled reference storage appear in
the report. Use COMMON to select data in the EXPFRAME, REALFRAME,
RSMREQ, SHRDATA, and VIRTPAGE reports.
DATASPACES
Requests information about data spaces for the VIRTPAGE and EXCEPTION
reports. (For these reports, data space-related information will not appear
unless you explicitly request it.)
DETAIL
Requests that more detailed information be reported. For the HVSHRDATA
report this information includes the view of segments from each address
space sharing the memory object. Use DETAIL with the HVSHRDATA
report.
HVCOMM
Requests that the report contain information about data defined as high
virtual common. Use HVCOMM to select data in the REALFRAME or
RSMREQ reports.
HVSHARED
Requests that the report contain information about data defined as high
virtual shared (shared storage above two gigabytes). Use HVSHARED to
select data in the REALFRAME or RSMREQ reports.
PERMCOMM
Requests that permanently assigned pages in the nucleus, absolute frame
zero, PSAs, HSA, or FLPA appear in the report. Use PERMCOMM to select
data in the REALFRAME and VIRTPAGE reports.
RANGE(rangelist)
Specifies a range of real frames or virtual pages to include in the report. Use
RANGE with the REALFRAME, SUBSPACE, VIRTPAGE, HIGHVIRTUAL,
HVCOMMON, and HVSHRDATA reports.
The rangelist is one or more ranges. In each range, the lower and upper
limits are separated by a colon character (:).
The value to specify for rangelist depends on the report:
Report Parameter
Value for rangelist

Chapter 5. IPCS subcommands 239

RSMDATA subcommand

HIGHVIRTUAL
Hexadecimal virtual addresses from 80000000 to
FFFFFFFF_FFFFFFFF. The default range for this report is
1_00000000:1_80000000.

Note: Each range limit can be 17 characters each and may contain
underscores.
HVCOMMON
Hexadecimal virtual addresses from 80000000 to
FFFFFFFF_FFFFFFFF. The default range for this report is the defined
common area for the system which is dumped.
HVSHRDATA
Hexadecimal virtual addresses from 80000000 to
FFFFFFFF_FFFFFFFF. The default range for this report is the defined
shared area for the system which is dumped.
REALFRAME
Hexadecimal real frame numbers from 0 to the number of real
frames in the system (up to 8 hexadecimal digits).
VIRTPAGE
Hexadecimal virtual addresses from 0 to 7FFFFFFF.
SUBSPACE
Hexadecimal virtual addresses from 0 to 7FFFFFFF.

Note: Hexadecimal notation (X'n...') is optional, that is, 7FFF as opposed to

X'7FFF'.
SAVEAREA(address)
Requests that the report contain information about the RSM module save
area at the specified address. Use SAVEAREA for the EXCEPTION and
EXECUTION reports.
SHARED
Requests that the report contain information about data defined as shared.
Use SHARED to select data in the REALFRAME and RSMREQ reports.
SHORT
Requests that the report contain abbreviated information that can be
obtained quickly. Use SHORT to select data in the ADDRSPACE report.
STATUS(statuslist)
Requests that the report include the status of each object.
The statuslist is a list of one or more object states, separated by blanks or
commas. The following is a list of report parameters and the object states for
each report. If you do not specify STATUS, the report will contain
information about all possible states for a given object.
– Object states for ADDRSPACE report:
NONSWAP
Indicates that you want to see the address spaces that are
non-swappable.
RESWPIP
Indicates that you want to see the address spaces that are in the
process of in-real swap (real swap).

240 z/OS MVS IPCS Commands

 RSMDATA subcommand

SWAUX
Indicates that you want to see the address spaces that are swapped to
auxiliary storage.
SWAUXIP
Indicates that you want to see the address spaces that are in the
process of being swapped to auxiliary storage.
SWIN
Displays the address spaces that are swapped in.
SWINIP
Displays the address spaces that are in the process of being swapped
in.
TERM
Displays the address spaces that are in the process of terminating.
– Object states for DIVMAP report:
MAPIP
Displays the data-in-virtual mapped ranges that are involved in a DIV
MAP request
MAPRPIP
Displays the data-in-virtual mapped ranges that are involved in a DIV
MAP-reprime request
UNMAPIP
Displays the data-in-virtual mapped ranges that are involved in a DIV
UNMAP request
SAVEIP
Displays the data-in-virtual mapped ranges that are involved in a DIV
SAVE request
RESETIP
Displays the data-in-virtual mapped ranges that are involved in a DIV
RESET request
MAPPED
Displays the data-in-virtual mapped ranges that are not involved in a
DIV request
– Object states for HIGHVIRTUAL report:
AUX
Displays pages that have their most recent copies on a DASD paging
data set or on storage-class memory (SCM).
DASD
Displays pages that have their most recent copies on a DASD paging
data set.
FREF
Displays all 4 KB pages that are in first-reference state. That is, one of
the following conditions is true for a given 4 KB page:
- It was never referenced.
- It was released through the IARV64 macro.
FRFM
Displays all 1 MB pages that are in a first-reference state. That is, one
of the following conditions is true for a given 1 MB page:
- It was never referenced.

Chapter 5. IPCS subcommands 241

RSMDATA subcommand

- It was released through the IARV64 macro.

GUARD
Displays pages that are in the guard area of a memory object.
HIDE
Displays pages that are hidden.

Note: Hidden pages that are part of globally shared memory objects
may not show up as hidden in this report. Run the HVSHRDATA
report to see the global view of those memory objects.
REAL
Displays all 4 KB pages that reside in real storage. They are either
valid or have output paging I/O in progress.
RL_M
Displays 1 MB pages that reside in real storage. They are either valid
or have output paging I/O in progress.
RL2G
Displays 2 GB pages that reside in real storage.
SCM
Displays pages that have their most recent copies on storage-class
memory (SCM).
SCMM
Displays 1 MB pages that have their most recent copies on
storage-class memory (SCM).
SIAI
Displays pages that are in the process of being swapped in from
auxiliary storage.
SOAI
Displays pages that are in the process of being swapped out to
auxiliary storage.
SWAX
Displays pages that have their most recent copies swapped to
auxiliary storage.
– Object states for REALFRAME report:
ALLOC
Displays the 4 KB frames that are allocated.
ALLOC1M
Displays the 1 MB pages that are allocated.
ALLOC2G
Displays the 2 GB pages that are allocated.
ALLOCSM
Displays only frames backing pages of shared segments.
ALLOCVR
Displays frames allocated to V=R jobs that are either running or
waiting for additional frames.
AVAIL
Displays the 4 KB frames that are available.

242 z/OS MVS IPCS Commands

 RSMDATA subcommand

AVAIL1M
Displays the 1 MB pages that are not allocated.
AVAIL2G
Displays the 2 GB pages that are not allocated.
OFFINT
Displays the frames that will be taken offline when freed from the
current owner.
OFFINTPL
Displays the frames that are offline intercepted and currently in use
by a job that is polluting the V=R area with a long term resident
page.
OFFINTVR
Displays frames that are offline intercepted and allocated to a V=R
job.
OFFLINE
Displays frames that are offline.
POLLUTE
Displays frames that are part of the V=R area, but are allocated to a
long-term resident page that is not V=R.
VRINT
Displays frames that will be assigned to a waiting V=R job when
freed from the current owner.
– Object states for RSMREQ report:
CANCEL
Displays any canceled requests.
COMPLETE
Displays non-fast path PGSER FIX requests that have completed and
are awaiting the corresponding PGSER FREE request.
DBLFRAME
Displays requests that are waiting for a real frame pair.
FAIL
Displays requests that had failures other than I/O or cross memory
access failures.
FRAMEAA
Displays requests that are waiting for any type of real frame.
FRAMEAB
Displays requests that are waiting for a real storage frame that resides
below 16 megabytes.
FRAMEPA
Displays requests that are waiting for a real frame that resides in the
preferred area.
FRAMEPB
Displays requests that are waiting for a real frame that resides in the
preferred area below 16 megabytes.
INPROGR
Displays requests that are in progress. These requests may or may not

Chapter 5. IPCS subcommands 243

RSMDATA subcommand

be waiting for a frame or I/O. The presence or absence of other

entries in this report for the same request indicates if a wait for a
frame or I/O exists.
IOFAIL
Displays requests that had I/O failures.
PGREAD
Displays requests that are waiting for a page to be read in from a
paging data set, or some other data set.
PGWRITE
Displays requests that are waiting for a page to be written to a paging
data set or some other data set.
XMFAIL
Displays requests that had cross memory access errors.
– Object states for SHRDATA report:
AUX
Displays pages that have their most recent copies on a DASD paging
data set or in storage-class memory (SCM).
DASD
Displays pages that have their most recent copies on a DASD paging
data set.
DSN
Displays pages that have their most recent copies on a data set
containing the data-in-virtual object of which the pages are a part.
FREF
Displays all 4 KB pages that were in a first-reference state. That is,
one of the following conditions is true for a given page:
- It was never referenced.
- It was released through the PGSER macro.
- It was released through the DSPSERV macro.
REAL
Displays all 4 KB pages that reside in real storage. They are either
valid or have output paging I/O in progress.
SCM
Displays 4 KB pages that have their most recent copies on
storage-class memory (SCM).
– Object states for SUBSPACE report:
GLOBAL
Displays the storage that is addressable by all subspaces within this
address space.
ASSIGN
Displays the storage in this address space that is assigned to
subspaces. In the report, the names of the subspaces to which the
storage is assigned appear in the SSP NAME column.
UNASSIGN
Displays the storage in the address space that is not assigned to any
subspace.
– Object states for VIRTPAGE report:

244 z/OS MVS IPCS Commands

 RSMDATA subcommand

AUX
Displays pages that have their most recent copies on a DASD paging
data set or in storage-class memory (SCM).
DASD
Displays pages that have their most recent copies on a DASD paging
data set.
DSN
Displays pages that have their most recent copies on a data set
containing the data-in-virtual object of which the pages are a part.
FREF
Displays all 4 KB pages that are in first-reference state. That is, one of
the following conditions is true for a given 4 KB page:
- It was never referenced.
- It was released through the PGSER macro.
- It was released through the DSPSERV macro.
FRFM
Displays all 1 MB pages that are in a first-reference state. That is, one
of the following conditions is true for a given 1 MB page:
- It was never referenced.
- It was released through the PGSER macro.
MIG
Displays pages for which both of the following conditions are true:
- The most recent copies are migrated to auxiliary storage from
expanded storage.
- The most recent copies reside in incorrect segments.
REAL
Displays all 4 KB pages that reside in real storage. They are either
valid or have output paging I/O in progress.
RL_M
Displays 1 MB pages that reside in real storage. They are either valid
or have output paging I/O in progress.
SCM
Displays pages that have their most recent copies on storage-class
memory (SCM).
SCMM
Displays 1 MB pages that have their most recent copies on
storage-class memory (SCM).
SMEG
Displays pages that are part of a shared segment.
VIO
Displays pages that have their most recent copies on a VIO data set.

Note: All of the following swap states apply only to working set pages.
SIAI
Displays pages that are in the process of being swapped in from
auxiliary storage.

Chapter 5. IPCS subcommands 245

RSMDATA subcommand

SIEI
Displays pages that are in the process of being swapped in from
expanded storage.
SOAI
Displays pages that are in the process of being swapped out to
auxiliary storage.
SOEI
Displays pages that are in the process of being swapped out to
expanded storage.
SWAX
Displays pages that have their most recent copies swapped to
auxiliary storage.
SWEX
Displays pages that have their most recent copies swapped to
expanded storage.
SWMG
Displays pages that are in the process of migrating from expanded
storage to auxiliary storage.
TOKEN(token)
Requests that the SHRDATA report be run only for the input token.
Usage note: The system ignores all other data selection parameters when
you specify TOKEN.
TOTONLY
Requests that for tabular reports, only the totals should be produced. All
other output is suppressed. If you do not specify TOTONLY, RSMDATA
prints all report data. Use TOTONLY for the ADDRSPACE, DIVMAP,
DSPACE, REALFRAME, RSMREQ, SHRDATA, and VIRTPAGE tabular
reports.
v Address space selection parameters
Use these parameters to obtain data from particular address spaces, which you
specify by their address space identifiers (ASIDs). Use these parameters for
ADDRSPACE, DIVMAP, DSPACE, EXCEPTION, REALFRAME, RSMREQ,
SHRDATA, SUBSPACE, and VIRTPAGE reports. In these reports, if you omit an
address space selection parameter, the defaults are CURRENT and ERROR. For
more information, see the select ASID service in z/OS MVS IPCS Customization.
ALL
Specifies processing of RSM control blocks for all address spaces in the
system at the time the dump is generated.
ASIDLIST(asidlist)
Specifies the list of address space identifiers for which you want to process
RSM control blocks.
The asidlist can be specified as a single ASID, a range of ASIDs, or a list of
noncontiguous ASIDs. When you specify a range, separate the first and last
ASIDs in the range with a colon. When you specify a list, separate the list
members with commas.
The ASID can be 1 through 65535. An ASID can be expressed in the notation
X'nnn', F‘nnn’, or B'nnn'. An unqualified number is assumed to be fixed.
CURRENT
Specifies processing of RSM control blocks for each active address space

246 z/OS MVS IPCS Commands

 RSMDATA subcommand

(that is, address spaces dispatched on some central processor, or bound by

cross memory to an address space dispatched on some central processor) at
the time of the dump.
ERROR
Specifies processing of RSM control blocks for the error address space(s).
JOBLIST(joblist) or JOBNAME(joblist)
Specifies the list of job names whose associated address spaces are to be
processed for RSM control blocks. Use commas to separate the job names in
the list; do not enclose job names in apostrophes; and do not specify a range
of job names.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the RSMDATA subcommand.
v Examples: See z/OS MVS Diagnosis: Reference for detailed descriptions and
examples of RSMDATA output.
When viewing RSMDATA output through the IPCS dialog, you can enter the
HELP primary command (or PF key). Choosing option 6 from the HELP
selection panel will display full help text on the contents of the RSMDATA
report.
v Example 1: Generate a report on virtual pages, including data space pages,
residing on expanded storage for job MYJOB.
– Action
COMMAND ===> RSMDATA VIRTPAGE JOBNAME(MYJOB) DATASPACES STATUS(EXP)
v Example 2: Generate a report showing all real frames (not just CURRENT and
ERROR) in the V=R region that are intercepted for use by a V=R job, or are
polluting the V=R region.
– Action
COMMAND ===> RSMDATA REALFRAME ALL STATUS(VRINT,POLLUTE) RANGE(5:86)

Note:
1. Determine the range of the V=R region using RSMDATA SUMMARY.
2. In this case, specify ALL to override the default CURRENT address space
selection parameters, so that the report will contain all the real frames that
satisfy the selection criteria.
v Example 3: Generate a report showing all RSM requests for the CURRENT
address space.
– Action
COMMAND ===> RSMDATA RSMREQ
v Example 4
Generate a report showing real storage usage summary for every address space
in the dump.
– Action
COMMAND ===> RSMDATA ADDRSPACE ALL
v Example 5: Generate a report showing the storage in address space X'023' that is
assigned to a subspace, not assigned to a subspace, or available to all subspaces.
– Action
COMMAND ===> RSMDATA SUBSPACE STATUS(GLOBAL,ASSIGN,UNASSIGN) ASIDLIST(X’ 023’)

Chapter 5. IPCS subcommands 247

RUNARRAY subcommand

RUNARRAY subcommand — process an array of control blocks

Use the RUNARRAY subcommand to process an array of control blocks. You can
specify the order that subscripts should be processed.

RUNARRAY optionally displays each control block.

You can specify additional subcommand, CLIST, or REXX exec processing with the
EXEC parameter. For each entry in the array, RUNARRAY will display the storage,
set the value of X to describe the entry, and then process the EXEC parameter for
that entry.
v Related subcommands
– RUNCHAIN
– RUNCPOOL
v Syntax

RUNARRAY

[ data-descr | ADDRESS(X) ]
[ ASCENDING | DESCENDING ]
[ EXEC((clist|rexx-exec|subcommand)) ]
[ SUMMARY | NOSUMMARY ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
[ VERIFY | NOVERIFY ]

v Parameters
data-descr
ADDRESS(X)
Specifies the data description parameter, which consists of five parts:
– An address (required when data-descr is explicitly specified on the
subcommand)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter. However, the following applies to
RUNARRAY only:
– The address is not a positional parameter. You must use the ADDRESS
parameter to specify an address.
– If you omit the ADDRESS parameter, the default for the RUNARRAY
subcommand is ADDRESS(X), the most recently accessed address.
– If you describe a block that is not an array, RUNARRAY treats it as an
array containing one entry, ENTRY(1).
ASCENDING

248 z/OS MVS IPCS Commands

 RUNARRAY subcommand

DESCENDING
Specifies the order in which subscripts are to be processed.
EXEC((clist))
EXEC((rexx-exec))
EXEC((subcommand))
Specifies that a CLIST, a REXX exec, or an IPCS subcommand is to be
appended to the RUNARRAY subcommand invocation. The appended
CLIST, REXX exec, or subcommand runs for each control block in the chain.
Parameters or keywords can accompany the CLIST, REXX exec, or IPCS
subcommand. The symbol X will point to the current array entry before each
EXEC invocation.
The RUNARRAY subcommand generates a return code that consists of its
own return code plus the return code from the CLIST, REXX exec, or IPCS
subcommand designated on the EXEC parameter. If the CLIST, REXX exec,
or IPCS subcommand returns with a serious condition, RUNARRAY
processing ends with the current array entry.
SUMMARY
NOSUMMARY
Controls the formatting of a processing summary after normal completion of
RUNARRAY processing. A processing summary is always produced if
abnormal conditions force termination of RUNARRAY.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the RUNARRAY subcommand.
The RUNARRAY subcommand generates a return code that consists of its own
return code plus the return code from a CLIST, REXX exec, or IPCS
subcommand if designated by the EXEC parameter. If the CLIST, REXX exec, or
IPCS subcommand returns with a serious condition, RUNARRAY processing
ends with the current control block.

RUNCHAIN subcommand — process a chain of control blocks

Use the RUNCHAIN subcommand to process a chain of control blocks. You can
specify the links to follow and a mask to apply to the links. You can also limit the
length of the chain to prevent infinite loops. With z/OS Release 3 and higher, you
can also specify that attributes and data within a chain of data areas is to
determine their order of processing by the RUNCHAIN subcommand.

RUNCHAIN displays each control block and creates entries for each control block
in the symbol table that is part of the source description for your current source.
You can specify a control block name for each symbol.

You can specify additional subcommand, CLIST, or REXX exec processing with the
EXEC parameter. For each control block in the chain, RUNCHAIN will display the
storage, set the value of X to the address of the control block, and then process the
EXEC parameter for that control block.

You can also process multiple levels of control block chains by specifying another
RUNCHAIN subcommand on the EXEC parameter.
v Related subcommands
– DROPSYM
– EQUATE
– LISTSYM

Chapter 5. IPCS subcommands 249

RUNCHAIN subcommand

– RUNCPOOL
– RUNARRAY
v Syntax

{ RUNCHAIN | RUNC }
[ data-descr | ADDRESS(X) ]
[ AMASK(mask) ]
[ CHAIN [(nnn|999)] ]
[ DROP | NODROP ]
[ EXEC((clist|rexx-exec|subcommand)) ]
[ LINK(range[LENGTH(integer)])] [ MASK(mask) ]
[ NAME(prefix) ]
[ NULL [(value|0)] ]
[ SORTBY(sort-key [ ASCENDING | DESCENDING ] ...) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
[ VERIFY | NOVERIFY ]

v Parameters
data-descr or ADDRESS(X)
Specifies the data description parameter, which consists of five parts:
– An address (required when data-descr is explicitly specified on the
subcommand)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter. However, the following exceptions
apply to RUNCHAIN only:
– The address is not a positional parameter. You must use the ADDRESS
parameter to specify an address.
– If you omit the ADDRESS parameter, the default for the RUNCHAIN
subcommand is ADDRESS(X), the most recently accessed address.
AMASK(mask)
Specifies an unsigned integer mask that RUNCHAIN is to AND to the link
field before using that field as the address of the next block in the chain.
IPCS accepts 64-bit values and interprets all values entered as having 64-bit
precision. If the chain originates below 224, the default is X'00FFFFFF'. If the
chain originates above 224, the default is X'7FFFFFFF'. If the chain originates
above the bar, the default is X'FFFFFFFF_FFFFFFFF'.
CHAIN[(nnn|999)]
Specifies the maximum number of blocks the subcommand is to process. The
number can be a maximum of 16,777,215 and can be specified in decimal,
hexadecimal (X'xxx...'), or binary (B'bbb...').
If you omit this parameter, the default is CHAIN(999).

250 z/OS MVS IPCS Commands

 RUNCHAIN subcommand

DROP or NODROP
Specifies the DROP or NODROP attribute for the names RUNCHAIN places
in the symbol table. RUNCHAIN places the names of the control blocks it
finds in the symbol table when you specify the NAME parameter.
DROP specifies the DROP attribute. This attribute allows the symbols to be
deleted from the symbol table by a DROPSYM subcommand.
NODROP specifies the NODROP attribute. This attribute prevents the
symbols from being deleted from the symbol table by a DROPSYM
subcommand, unless DROPSYM contains a PURGE parameter.
EXEC((clist|rexx-exec|subcommand))
Specifies that a CLIST, a REXX exec, or an IPCS subcommand is to be
appended to the RUNCHAIN subcommand invocation. The appended
CLIST, REXX exec, or subcommand runs for each control block in the chain.
Parameters or keywords can accompany the CLIST, REXX exec, or IPCS
subcommand. The symbol X will point to the current control block on the
chain before each EXEC invocation.
The EXEC parameter also accepts another RUNCHAIN invocation to process
multiple levels of control blocks. See the BLSCRNC2 CLIST in
SYS1.SBLSCLI0 for an example.
The RUNCHAIN subcommand generates a return code that consists of its
own return code plus the return code from the CLIST, REXX exec, or IPCS
subcommand designated on the EXEC parameter. If the CLIST, REXX exec,
or IPCS subcommand returns with a serious condition, RUNCHAIN
processing ends with the current control block.
LINK(range[LENGTH(integer)])
Defines a range of offsets that contain a 1-8 byte pointer from one block in
the chain to the next.
LINK(0:3) 4-byte pointer at the origin of the block
LINK(8:15) 8-byte pointer at displacement 8 in the block
LINK(8:4) Error. Descending range

Range consists of one or two an unsigned integers. The end of the range
may be omitted or can be designated using LENGTH(integer). For
compatibility with earlier releases, RUNCHAIN treats this as a description of
a 4-byte pointer.
The link pointer is always extended to 8-bytes before masking, nullity
checking, and use for access to the next block on the chain.
If you omit this parameter, the default is LINK(0).
MASK[(mask)]
Specifies an unsigned integer mask that RUNCHAIN is to AND to the link
field before comparing it to the value specified with the NULL parameter.
IPCS accepts 64-bit values and interprets all values entered as having 64-bit
precision.
The length of the mask must be eight bytes. If it is less than eight bytes, the
subcommand right-justifies it and pads it on the left with zeros. If it exceeds
eight bytes, the subcommand rejects it.
You can specify the mask in decimal, hexadecimal (X‘xxx...’), or binary
(B‘bbb...’). If you specify it in decimal or binary, the value is converted to its
hexadecimal equivalent and padded if needed.

Chapter 5. IPCS subcommands 251

RUNCHAIN subcommand

If you omit this parameter, the default for all chains is

MASKX'FFFFFFFF_FFFFFFFF'.
NAME(prefix)
Specifies the prefix RUNCHAIN uses to generate names for each control
block it finds. The subcommand places the generated names in the symbol
table. The generated name can be 1 to 31 alphanumeric characters and the
first character must be a letter or the characters “$”, “@”, or “#”.
RUNCHAIN appends a sequence number to the prefix to produce a unique
control block name. The sequence number starts at 1 and is limited by the
value specified with the CHAIN parameter.
The prefix for any control block may not exceed 30 characters.
If you omit this parameter, RUNCHAIN does not generate names for the
control blocks it finds.
NULL[(value|0)]
Specifies the unsigned integer doubleword value that indicates the end of
the chain. IPCS accepts 64-bit values and interprets all values entered as
having 64-bit precision.
For each control block on the chain, RUNCHAIN:
– Locates the link field at the offset specified in the LINK parameter.
– ANDs the mask with the contents of the link field.
– Compares the result of the AND with the NULL value.
– When the result of the comparison is equal, chaining ends.
– When the result of the comparison is not equal, chaining continues.
SORTBY(sort-key [ASCENDING|DESCENDING)...]
Controls the order of processing for chain elements.
sort-by
A list of sort-keys directs RUNCHAIN to make two passes over the
chain. The first pass internally enumerates the blocks on the chain and
collects up to 256 bytes of aggregate sort key data.
If any data described as a sort key cannot be retrieved, the chain is
logically terminated at the preceding block during the first pass.
Each sort-key may be designated in one of the following ways:
signed-integer[:signed-integer]
Designates a range of offsets from the origin of the block. A string or
unsigned binary number at those locations is used as a sort key. If
the end of the range is not specified, four bytes are selected.
ADDRESS
DIMENSION
LENGTH
MULTIPLE
These keywords designate an unsigned attribute of the block. Each
of these attributes uses 8 bytes of the 256 available.
ENTRY
POSITION
These keywords designate a signed attribute of the block. A signed
comparison between thers attributes is performed. Each of these
attributes uses 8 bytes of the 256 available.

252 z/OS MVS IPCS Commands

 RUNCHAIN subcommand

DATATYPE
The DATATYPE keyword designates the type of block, for example,
STRUCTURE(UCBDASD) versus STRUCTURE(UCBTAPE). Each of
these attributes uses 34 bytes (see Data Area BLSRDATT) of the 256
available.
ASCENDING
DESCENDING
These keywords designate the sort order for the preceding key.
Ascending sort order is the default.
v Return codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the RUNCHAIN subcommand.
The RUNCHAIN subcommand generates a return code that consists of its own
return code plus the return code from a CLIST, REXX exec, or IPCS
subcommand if designated by the EXEC parameter. If the CLIST, REXX exec, or
IPCS subcommand returns with a serious condition, RUNCHAIN processing
ends with the current control block.
v Example: The BLSCRNCH CLIST runs the chain of task control blocks (TCB) for
an address space. It displays the following information:
– The current TCB
– The TCBs that are lower on the priority chain in that address space
– The currently dispatched RB for each of the TCBs
This CLIST, written for SVC dumps, uses the RUNCHAIN subcommand as
follows:
PROC 0 TCB(21C.%)
RUNCHAIN ADDRESS(&TCB) STRUCTURE(TCB) /* Process TCBs */+
LINK(X’74’) /* Connected by field TCBTCB */+
VERIFY DISPLAY /* Maximum display for each TCB */+
EXEC((LIST X+0% STRUCTURE(RB) DISPLAY))/* Show RB for TCB*/
The logic of this CLIST is as follows:
PROC 0 TCB(21C.%)
This line indicates that the default path to the first TCB is the fullword
pointer at location X‘21C’.
RUNCHAIN ADDRESS(&TCB) STRUCTURE(TCB)
This line processes the first TCB that can be found by using the default path
or an alternate path to a TCB, described when the CLIST is invoked. IPCS
validates the TCB and creates a storage map entry for it. The STRUCTURE
attribute parameter identifies that a TCB is being processed.

Note: If SDUMP writes the dump, IPCS does not require address processing
parameters. IPCS establishes the dumped ASID as the default address space.
LINK(X'74')
This line establishes addressability to the TCBTCB field at offset X'74' for
each TCB, thereby providing the address of the next TCB on the chain to be
processed.
VERIFY DISPLAY
This line lists all TCBs found on the chain and displays the maximum
amount of information for each TCB. The VERIFY and DISPLAY parameters
each override the defaults established by the SETDEF subcommand for the
corresponding parameter.

Chapter 5. IPCS subcommands 253

RUNCHAIN subcommand

EXEC((LIST X+0% STRUCTURE(RB) DISPLAY))

This line updates the current TCB that is currently being processed,
establishes addressability to the TCBRBP field at offset X'0' within the
current TCB, and accesses the RB related to the current TCB.

RUNCPOOL subcommand — process a CPOOL

Use the RUNCPOOL subcommand to process a cell pool created and managed by
the CPOOL macro. Cells are partitioned into the following categories:
v Used cells are those that contained current data when a dump was produced.
v Available cells are those that were not currently in use when a dump was
produced. CPOOL services use the first four bytes in each such cell, but residual
data useful for analysis may remain in the other part of such a cell.
v Indeterminate cells are those that IPCS cannot place in either of the preceding
categories.
The most common reason for this is that the pool was actively being changed
during the dumping process, producing a “blurred picture” of this part of the
dumped system. Storage overlays and storage missing from a dump may also
produce indeterminate cells.
You can specify which categories of cells should be processed.

Establishing categories of cells is done before processing the cells themselves, and
an optional report may be formatted that identifies data areas used to manage the
cell and data extracted from those data areas.

RUNCPOOL optionally displays each cell.

You can specify additional subcommand, CLIST, or REXX exec processing with the
EXEC parameter. For each cell, RUNCPOOL will display the storage, set the value
of X to the address of the cell, and then process the EXEC parameter for that cell.
v Related subcommands
– RUNARRAY
– RUNCHAIN
v Syntax

254 z/OS MVS IPCS Commands

 RUNCPOOL subcommand

RUNCPOOL cpid-general-value

[ ASID(asid) ]
[ DATABLKS | NODATABLKS ]
[ USED | NOUSED ]
[ INDETERMINATE | NOINDETERMINATE ]
[ AVAILABLE | NOAVAILABLE ]
[ EXEC((clist|rexx-exec|subcommand)) ]
[ SUMMARY | NOSUMMARY ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
[ VERIFY | NOVERIFY ]

v Parameters
cpid-general-value
Specifies a fullword cell pool identifier (CPID used in conjunction with the
| CPOOL macro). If F'0' is specified, all private storage CPOOLs are processed
| for the specified ASID. If F'1' is specified, all common storage CPOOLs are
| processed.
ASID(asid)
Specifies the ASID of a CPOOL in private storage as a positive integer. This
may be omitted if the default IPCS address processing parameters specify an
ASID.
DATABLKS
NODATABLKS
Controls the formatting of a report that identifies data areas used to control
the cell pool and extracts information from them regarding the status of the
cell pool.
USED
NOUSED
Specifies whether cells in the pool that are in use are to be included in
RUNCPOOL processing.
INDETERMINATE
NOINDETERMINATE
Specifies whether cells known to be in the pool but whose status as used or
available cannot be determined are to be included in RUNCPOOL
processing.
AVAILABLE
NOAVAILABLE
Specifies whether cells in the pool that are available are to be included in
RUNCPOOL processing.
EXEC((clist))
EXEC((rexx-exec))
EXEC((subcommand))
Specifies that a CLIST, a REXX exec, or an IPCS subcommand is to be

Chapter 5. IPCS subcommands 255

RUNCPOOL subcommand

appended to the RUNCPOOL subcommand invocation. The appended

CLIST, REXX exec, or subcommand runs for each control block in the chain.
Parameters or keywords can accompany the CLIST, REXX exec, or IPCS
subcommand. The symbol X will point to the current cell on the chain before
each EXEC invocation.
The RUNCPOOL subcommand generates a return code that consists of its
own return code plus the return code from the CLIST, REXX exec, or IPCS
subcommand designated on the EXEC parameter. If the CLIST, REXX exec,
or IPCS subcommand returns with a serious condition, RUNCPOOL
processing ends with the current control block.
SUMMARY
NOSUMMARY
Controls the formatting of a processing summary after normal completion of
RUNCPOOL processing. A processing summary is always produced if
abnormal conditions force termination of RUNCPOOL.
v Return codes
The RUNCPOOL subcommand generates a return code that consists of its own
return code plus the return code from a CLIST, REXX exec, or IPCS
subcommand if designated by the EXEC parameter. If the CLIST, REXX exec, or
IPCS subcommand returns with a serious condition, RUNCPOOL processing
ends with the current control block.

Examples
Example 1 - Small private area CPOOL
Example 1 shows a small private area CPOOL in which all of the cells are
currently unused.
runcpool x’0F188300’

PPD at 7F7E8F88
ASID(X’036E’) CPID(X’0F188300’) in loc(any,any) subpool(78)
Csize(3,072) primary(5) secondary(40)
PXT at 0F188300
SPD at 7F7E8FC0
Cells(5) used(0)

IGV18094I No cells processed

Example 2 - Larger private area CPOOL

Example 2 shows (part of) a larger private area subpool, one that has expanded
into a secondary extent. Slightly more than half of the cells are currently in use
and are displayed.
runcpool x’008B6000’ display

PPD at 7F7E8F10
ASID(X’036E’) CPID(X’008B6000’) in loc(below) subpool(236)
Csize(80) primary(101) secondary(102)
PXT at 008B6000

SPD at 7F7E8F48
SXT at 00887000
Cells(203) used(126)

CPOOLCELL - Cell in use

LIST 00887018 ASID(X’036E’) LENGTH(80) AREA(CPOOLCELL)
ASID(X’036E’) ADDRESS(00887018) KEY(10)
00887018. C4E2C1C2 00887428 | DSAB.h..|
00887020. 008B7F68 00500000 008BC9C8 008A2070 00000000 00000000 0000CA00 00000000 |.."..&;...IH....................|
00887040. 008F9E50 00000000 00000000 00000000 00000000 00000200 008A2080 00000066 |...&;...........................|
00887060. 00000200 00000000 |........ |

256 z/OS MVS IPCS Commands

 RUNCPOOL subcommand

CPOOLCELL - Cell in use

LIST 00887068 ASID(X’036E’) LENGTH(80) AREA(CPOOLCELL)
ASID(X’036E’) ADDRESS(00887068) KEY(10)
00887068. C4E2C1C2 008870B8 008B7A18 00500000 008BC798 0089DB50 | DSAB.h....:..&;...Gq.i.&|
00887080. 00000000 00000000 0000CA00 00000000 0086FD50 00000000 00000000 00000000 |.................f.&;...........|
008870A0. 00000000 000003D8 0089DB60 00000067 000003D8 00000000 |.......Q.i.-.......Q.... |

CPOOLCELL - Cell in use

LIST 008870B8 ASID(X’036E’) LENGTH(80) AREA(CPOOLCELL)
ASID(X’036E’) ADDRESS(008870B8) KEY(10)
008870B8. C4E2C1C2 00887748 | DSAB.h..|
008870C0. 00887068 00500000 008BC7AC 0089D6A0 00000000 00000000 0000CA00 00000000 |.h...&;...G..iO.................|
008870E0. 0086FD50 00000000 00000000 00000000 00000000 000003E0 0089D6B0 00000068 |.f.&;..................\.iO.....|
00887100. 000003E0 00000000 |...\.... |

CPOOLCELL - Cell in use

LIST 00887108 ASID(X’036E’) LENGTH(80) AREA(CPOOLCELL)
ASID(X’036E’) ADDRESS(00887108) KEY(10)
00887108. C4E2C1C2 00887158 008B76A8 00500000 008BC3C4 0089D1F0 | DSAB.h.....y.&;...CD.iJ0|
00887120. 00000000 00000000 0000CA00 00000000 0088CE88 00000000 00000000 00000000 |.................h.h............|
00887140.
.. 00000000 00000188 0089D200 00000069 00000188 00000000 |.......h.iK........h.... |
.
CPOOLCELL - Cell in use
LIST 008B7F68 ASID(X’036E’) LENGTH(80) AREA(CPOOLCELL)
ASID(X’036E’) ADDRESS(008B7F68) KEY(10)
008B7F68. C4E2C1C2 00887018 008B7798 00500000 008BC9B4 008A25E0 | DSAB.h.....q.&;...I....\|
008B7F80. 00000000 00000000 0000CA00 00000000 008F9E50 00000000 00000000 00000000 |...................&;...........|
008B7FA0. 00000000 000001F8 008A25F0 00000065 000001F8 00000000 |.......8...0.......8.... |

IGV18094I 126 cells processed

Example 3 - Common area CPOOL

Example 3 shows a summary of a common area CPOOL.
runcpool a’2D37000’

PPD at 02EBF068
CPID(X’02D37000’) in loc(any) subpool(248)
Csize(32,640) primary(1) secondary(1)
PXT at 02D37000

SPD at 02EBF0A0
SXT at 0412B000
SXT at 04582000
SXT at 049CF000
SXT at 0273B000

Cells(5) used(0)

IGV18094I No cells processed

SCAN subcommand — validate system data areas

Use the SCAN subcommand to validate system data and make storage map entries
for that data. Appendix C, “Control blocks and data areas scanned, mapped, and
formatted,” on page 455 lists the data areas that IPCS scans, maps, and formats.
SCAN validates a control block by checking:
v Boundary alignment. (Certain control blocks must begin on word, doubleword,
or other special boundaries.)
v Standard fields in the control block, such as:
– Acronyms
– Count fields
– Masks or bit maps
v Pointers that address other system data

Chapter 5. IPCS subcommands 257

SCAN subcommand

SCAN initiates its processing from your storage map and validates control blocks
listed in the storage map that are within the address range you specified. As it
does this, SCAN makes new map entries for control blocks pointed to by the block
being validated. Depending on the DEPTH and PASSES parameters, new entries
(control blocks) in the map may or may not be validated; however, if the new
control blocks are found to be not valid, their entries remain in the map.

The process of validating one control block and following its pointers to other
control blocks to the indicated depth is called a scan probe. If you specify a large
number for DEPTH, the scan probe of one control block can add many entries to
the map. If this control block is the CVT or an ASCB, one scan probe can map all
the AREAs and STRUCTUREs in the dump. Dump initialization provides entries in
the map for the current dump. SCAN requires at least one entry to begin its
processing.

If a control block does not appear valid, IPCS issues a message that gives the
control block name, its address, and the apparent error; the control block's entry
remains in the storage map.

If SCAN, in validating a control block, follows a pointer to a new control block,

and finds that the new control block is not valid, IPCS issues two messages. The
first message has a severity level of ERROR to inform you that the original control
block contains a bad pointer. The second message has a severity level of SEVERE
to inform you that the (alleged) new control block is not valid.
v Syntax

SCAN [ limit|100 ]
[ RANGE(address:address) ] [data-descr]
[ DEPTH(n|2) ]
[ PASSES(n|1) ]
[ SUMMARY | NOSUMMARY ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
limit
Specifies the maximum number of scan probes that SCAN is to perform. The
limit can range from 1 through 231 and can be specified in decimal,
hexadecimal (X'xxx...'), or binary (B'bbb...').
This parameter, if specified, it must precede any parameters. If you omit this
parameter, the default is 100.
RANGE(address:address)
Specifies the range of addresses, the types of entries, or both, in the storage
map from which SCAN is to perform scan probes. When validating a control
block, SCAN may access other control blocks outside the specified range.
The RANGE parameter specifies the addresses from which the SCAN probes
start. When the RANGE parameter is omitted, SCAN validates all control
blocks that have not been validated.

258 z/OS MVS IPCS Commands

 SCAN subcommand

data-descr
Specifies the data description parameter, which consists of five parts:
– An address (required with the RANGE parameter and when data-descr is
explicitly specified on the subcommand)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.
If you specify the STRUCTURE attribute parameter with a data type, it
causes the subcommand to create a map record. This new map record does
not otherwise change the results of this subcommand.
If you omit this parameter, SCAN validates all storage map entries not
previously validated. A control block may be only partially validated
because of limits on DEPTH and PASSES on previous scans.
DEPTH(n|2)
Specifies the maximum level of indirection for each scan probe. For example,
the new control blocks that a given control block points to are at depth 1.
The control blocks that the new control blocks point to are at depth 2, and
so on.
The n can be 1 through 65535. The number can be specified in decimal,
hexadecimal (X'xxx...'), or binary (B'bbb...'). An unqualified number is
decimal.
If you omit this parameter, the default is DEPTH(2).
PASSES(n|1)
Specifies the number of times SCAN processes the storage map entries in the
specified address range. As SCAN reprocesses the storage map, it does not
revalidate control blocks previously validated.
The n can be 1 through 231. The number can be specified in decimal,
hexadecimal (X'xxx...'), or binary (B'bbb...'). An unqualified number is
decimal.
If you omit this parameter, the default is PASSES(1).
SUMMARY or NOSUMMARY
SUMMARY indicates that a processing summary (a final total line) is to be
produced. NOSUMMARY specifies that a processing summary is to be
suppressed. The NOSUMMARY parameter is useful to turn off summary
messages when the subcommand is invoked within a CLIST or a REXX exec.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the SCAN subcommand.

SELECT subcommand — generate address space storage map entries

Use the SELECT subcommand to:
v Create storage map entries that describe address spaces. Storage map entries
include the address space address, address space identifier (ASID), length, and
AREA data type.

Chapter 5. IPCS subcommands 259

SELECT subcommand

v Produce a report that displays the ASID, associated job name, ASCB address,
and selection criteria for each address space selected.

The storage map is part of a source description. A source description is for an

unformatted source that IPCS can format, for example, an SVC dump, a
stand-alone dump, an SYSMDUMP dump, a trace data set, a data set, or active
storage. The source description is in the dump directory allocated with ddname
IPCSDDIR and is your current dump directory. The current dump directory is your
user dump directory or, for users with write access authority, might be the sysplex
dump directory.
v Related subcommands
– EVALMAP
– LISTMAP
– LIST
– SUMMARY
v Syntax

SELECT [ LIST | NOLIST ]

-------- Address Space Selection Parameters ----------------

[ ALL ]
[ CURRENT ]
[ ERROR ]
[ TCBERROR|ANOMALY ]
[ ASIDLIST(asidlist) ]
[ JOBLIST(joblist)|JOBNAME(joblist) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
LIST or NOLIST
Specifies if IPCS should generate a report. LIST specifies a report. NOLIST
specifies no report. NOLIST is provided mainly for CLIST processing, for
example, when a CLIST might want to generate a storage map entry without
creating a report. When NOLIST is specified, NOPRINT and NOTERM are
assumed.
v Address Space Selection Parameters
Use these parameters to obtain data from particular address spaces, which you
specify by their address space identifiers (ASIDs). If you omit these parameters,
the defaults is CURRENT.
These parameters also control the name portion for the AREA attribute of the
storage map entries. (For a refresher on the AREA attribute parameter, see
“Attribute parameters” on page 29.) Table 15 on page 261 shows what to specify
for name.

260 z/OS MVS IPCS Commands

 SELECT subcommand

Table 15. Address space parameter and AREA(name)

When You Specify This Address Space You Get This AREA(name) Storage Map
Parameter Entry Attribute
CURRENT AREA(CURRENT)
ERROR AREA(ERROR)
TCBERROR AREA(TCBERROR)
JOBLIST AREA(JOBxxxx)

Note:
1. Storage map entries are created when you specify the CURRENT, ERROR,
TCBERROR, and JOBNAME/JOBLIST address space selection parameters.
2. For an address space to be mapped when you select it with JOBLIST, it must
have a standard alphanumeric job name.
3. When you use JOBLIST to select the master scheduler address (*MASTER*)
space, IPCS maps it with an AREA name of JOBMASTER.
For more information, see the select ASID service in z/OS MVS IPCS
Customization.
ALL
Specifies processing of all address spaces in the dump. Not valid with
ACTIVE storage.
CURRENT
For dump data sets, shows the address space that generated the dump. For
ACTIVE storage, shows the address of the TSO user who invoked IPCS.
ERROR
Specifies processing of control blocks for any address space with an MVS
error indicator or containing a task with an error indicator. Not valid with
ACTIVE storage.
TCBERROR or ANOMALY
Specifies processing of control blocks for any address space containing a task
with an error indicator. Blocks for address spaces with an error indicator are
not processed. Not valid with ACTIVE storage.
ASIDLIST(asidlist)
Specifies a list of ASIDs for the address spaces to be processed, The asidlist
can be a single ASID, a range of ASIDs, or a list of noncontiguous ASIDs.
When you specify a range, separate the first and last ASIDs in the range
with a colon. When you specify a list, separate the list members with
commas. The ASID can be 1 through 65535. An ASID can be expressed in
the notation X'nnn', F'nnn', or BB'nnn'. An unqualified number is assumed to
be fixed. Not valid with ACTIVE storage
JOBLIST(joblist) or JOBNAME(joblist)
Specifies a list of job names whose associated address spaces are to be
processed. Use commas to separate the job names in the list; do not enclose
job names in apostrophes; and do not specify a range of job names. Not
valid with ACTIVE storage.
v SETDEF-Defined Parameters
ACTIVE or MAIN or STORAGE
DATASET(dsname) or DSNAME(dsname)

Chapter 5. IPCS subcommands 261

SELECT subcommand

FILE(ddname) or DDNAME(ddname)
Specifies the source of the source description containing the storage map. If
one of these parameters is not specified, the source is your current source.
ACTIVE, MAIN, or STORAGE specifies central storage as the source. When
active storage is specified, the SELECT subcommand can process only
current address spaces.
DSNAME or DATASET specifies the name of a cataloged data set as the
source.
FILE or DDNAME specifies the ddname for a data set as the source.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the SELECT subcommand.
v Example: Generate a report containing information for the current, error, master
scheduler, and JES3 address spaces.
– Action: COMMAND ===> select current error joblist(*master* jes3) list
– Result: SELECT produces the output in Figure 23.

ASID JOBNAME ASCBADDR SELECTION CRITERIA

---- -------- -------- ------------------
0001 *MASTER* 00123456 CURRENT JOBNAME
0010 JES3 00234567 JOBNAME CURRENT
01BB USERJOB 00789ABC ERROR

Figure 23. Example: SELECT output

It also generates the storage map entries shown in Figure 24, which describe
the selected address spaces. You can access these entries with the EVALMAP
subcommand.

LIST 00001000. ASID(X’0001’) LENGTH(11530240) AREA(CURRENT)

LIST 00001000. ASID(X’0001’) LENGTH(11530240) AREA(JOBMASTER)
LIST 00001000. ASID(X’0010’) LENGTH(11530240) AREA(CURRENT)
LIST 00001000. ASID(X’0010’) LENGTH(11530240) AREA(JOBJES3)
LIST 00001000. ASID(X’01BB’) LENGTH(11530240) AREA(ERROR)

Figure 24. Example: SELECT output (storage map entries)

SETDEF subcommand — set defaults

Use the SETDEF subcommand to set, change, and display your default values for
certain parameters on IPCS subcommands. You can run SETDEF at any time
during an IPCS session to display your default values. To set or change the value
for a default, enter a SETDEF subcommand with the parameter and its new value.
IPCS uses the new default value for both your current session and any subsequent
sessions in which you use the same user dump directory, until you change the
value. SETDEF sets two types of default values:
v Local defaults. These values are currently in use for an ISPF screen in the IPCS
dialog, for a batch IPCS session, or for an IPCS interactive line-mode session.
v Global defaults. These values are used to establish the local defaults when IPCS
processing starts in an ISPF screen, a batch IPCS session, or an IPCS interactive
line-mode session.

262 z/OS MVS IPCS Commands

 SETDEF subcommand

Your global defaults are obtained from the dump directory being used. IPCS
uses as the global defaults the following, in this order:
1. The last value specified as a global default in a SETDEF subcommand or on
the IPCS Default Values panel in the IPCS dialog.
2. The value in the IPCSPRxx parmlib member
3. The IBM-supplied value

The IBM-supplied values for global SETDEF-defined defaults are shown in

Figure 25.

/*-------------- Default Values for IPCS subcommands -------------*/

SETDEF NOPRINT TERMINAL NOPDS /* Routing of displays */
SETDEF FLAG(WARNING) /* Optional diagnostic messages */
SETDEF CONFIRM /* Double-checking major acts */
SETDEF NOTEST /* IPCS application testing */
SETDEF NODSNAME /* No data set name */
SETDEF LENGTH(4) /* Default data length */
SETDEF VERIFY /* Optional dumping of data */
SETDEF DISPLAY(NOMACHINE) /* Include storage keys, .... */
SETDEF DISPLAY( REMARK) /* Include remark text */
SETDEF DISPLAY( REQUEST) /* Include model LIST subcommand */
SETDEF DISPLAY(NOSTORAGE) /* Include contents of storage */
SETDEF DISPLAY( SYMBOL) /* Include associated symbol */
SETDEF DISPLAY( ALIGN) /* Align output to byte */

Figure 25. IBM-supplied values for global SETDEF-defined defaults

ASID and CPU, the address processing parameters, are not listed and are null until
you specify a source data set or storage. SETDEF rejects any attempt to set these
values before you specify a source. When you specify a source and access it with
any of the analysis subcommands, that subcommand sets your local default
address processing value to describe an address space contained in that data set or
storage.

When you specify a source data set or storage on a SETDEF subcommand, your
next analysis subcommand causes IPCS to initialize the specified source data set or
storage.

If all parameters on a SETDEF subcommand are valid, IPCS sets the specified
values. However, if IPCS rejects any parameter, the subcommand ends without
IPCS changing any values.

Many subcommands can override a current local default by specifying a SETDEF

parameter and value. For each subcommand, the SETDEF-defined parameters are
grouped in the syntax diagram, thereby identifying the SETDEF-defined
parameters that apply specifically to the subcommand. These overriding values
apply only to the subcommand, are not saved in your user dump directory, and
are not retrieved by an EVALDEF subcommand.
v Syntax

Chapter 5. IPCS subcommands 263

SETDEF subcommand

{SETDEF } [ LIST | NOLIST ]

{SETD }

[ LOCAL ]
[ GLOBAL ]

-------- SETDEF-Defined Parameters --------------------------

[ address-processing-parameters ]
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ NODSNAME | NODATASET ]
[ PATH(path-name) ]
[ CONFIRM | NOCONFIRM ]
[ DISPLAY[(display-options)] ]
[ NODISPLAY[(display-options)] ]
[ FLAG(severity) ]
[ LENGTH(length) ]
[ PRINT | NOPRINT ]
[ PDS | NOPDS ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
[ VERIFY | NOVERIFY ]

v Parameters
LIST or NOLIST
Specifies whether IPCS is to display all of your local and global default
values. LIST requests IPCS to display the values at your terminal, regardless
of the current value for the TERMINAL parameter. NOLIST specifies that
IPCS is not to display the values.
If you enter SETDEF without any parameters, the default is LIST. If you
omit LIST and NOLIST but specify any other parameter, the default is
NOLIST.
LOCAL
Specifies local default values:
– If LIST is also specified, IPCS lists your local default values.
– If LIST is not also specified, IPCS changes any local default to the value
specified on this SETDEF subcommand. Your global default values are not
changed.
GLOBAL
Specifies global default values:
– If LIST is also specified, IPCS lists your global default values.
– If LIST is not also specified, IPCS changes any global default to the value
specified on this SETDEF subcommand. Your local default values are not
changed; also, these new global values do not override any local default
values currently being used.
If you omit or specify both LOCAL and GLOBAL, IPCS lists or changes both
local and global default values.
v SETDEF-Defined Parameters
Default values for the following parameters are defined and shipped with IPCS.
Your default values are kept in your dump directory. To change your defaults,
enter a SETDEF subcommand with your own values for the parameters.
address-processing-parameter
Specifies address processing values, which are a part of the data description
(data-descr) parameter. “Address processing parameters” on page 23 explains

264 z/OS MVS IPCS Commands

 SETDEF subcommand

how to specify address processing parameters. Chapter 3, “Data description

parameter,” on page 17 explains the use and syntax of the data description
parameter.
ASID(X‘0000’) and CPU(0) are the IPCS-defined defaults.
CONFIRM or NOCONFIRM
Specifies if certain subcommands are to request confirmation before
performing their function. CONFIRM requests your confirmation before:
– Deleting a problem
– Dissociating and scratching a data set
– Modifying a data set's attributes, if the data set is associated with more
than one problem
– Accessing summary dump data during dump initialization
The subcommands affected by CONFIRM are:
– Any subcommand that starts initializing a dump that contains summary
dump data.
NOCONFIRM does not request your confirmation before running these
subcommands. When NOCONFIRM is specified, IPCS uses summary dump
data.
CONFIRM is the IPCS-defined default.
ACTIVE or MAIN or STORAGE
DSNAME(dsname) or DATASET(dsname)
FILE(ddname) or DDNAME(ddname)
NODATASET or NODSNAME
Specifies the source. If one of these parameters is not specified, the
IPCS-defined default is NODSNAME.
ACTIVE, MAIN, or STORAGE specifies the central storage for the address
space in which IPCS is currently running and allows you to access that
active storage as the dump source. You can access private storage and any
common storage accessible by an unauthorized program.
You might use one of these parameters to, for instance:
– Display individual control blocks and examine how they are chained
within the executing IPCS address space
– Compare system control blocks (such as the CVT) that were formatted in
a dump data set with system control blocks that are currently being used
in the IPCS address space
– Examine a field in the read-only nucleus that does not appear in a dump
report
– Diagnose an error in IPCS processing
You should not use these parameters for:
– Volatile common or private storage
– Prefixed storage
If IPCS is running as an MVS system migration aid, IPCS rejects these
parameters.
IPCS does not create a storage map when this parameter is entered. IPCS
does maintain a symbol table but limits its automatic creation of symbols
into the table.

Chapter 5. IPCS subcommands 265

SETDEF subcommand

DSNAME or DATASET specifies the source with the name of a cataloged

data set. If the data set is password protected, also specify the password. If
you omit the password and it is required, IPCS prompts you for it.
IPCS dynamically allocates and opens the data set when it is first accessed.
When an IPCS session completes, IPCS dynamically closes and releases the
data set, restoring the data set to its status before being accessed.
FILE or DDNAME specifies the source with the ddname of a data set. The
data set can reside on tape or a direct access storage device (DASD). If the
data set is password protected, IPCS ignores the password.
The data control block (DCB) attributes (BLKSIZE, DSORG, KEYLEN,
LRECL, and RECFM) designated when the data set was defined override the
following:
– For DASD data sets, these attributes in the data set control block (DSCB)
– For data sets on standard-labeled tapes, these attributes on the tape label
IPCS opens the data set when it is first accessed and closes the data set,
restoring it to its original status. However, IPCS does not allocate or
deallocate (release) the data set. The data set must be allocated before being
requested in a FILE or DDNAME parameter on an IPCS subcommand. To
allocate the data set, enter a TSO/E ALLOCATE command or the
appropriate JCL statement before using the subcommand. To deallocate the
data set, enter a TSO/E FREE UNALLOC command or use the parameter
FREE=CLOSE on the JCL DD statement.

Note: IPCS processing does not allow the concatenation of data sets.
NODATASET or NODSNAME specifies that the subcommand is to set the
source name in the local or global defaults to a null value. If you do not
specify a source, the null value remains in effect.
DISPLAY[(display-options)]
NODISPLAY[(nodisplay-options)]
Specifies if the source is to be displayed or not. DISPLAY, entered alone,
requests that all parts of a dump be displayed. It is equivalent to entering
DISPLAY(MACHINE REMARK REQUEST STORAGE SYMBOL ALIGN)

DISPLAY, entered with one or more display-options, selects parts of a source

to be displayed.
NODISPLAY, entered alone, is the same as DISPLAY(REQUEST). It is
equivalent to entering:
DISPLAY(NOMACHINE NOREMARK REQUEST NOSTORAGE NOSYMBOL NOALIGN)
NODISPLAY entered with one or more values, suppresses (or selects) parts
of a display.

Note: If VERIFY is specified or defaulted, and the NODISPLAY parameter is

also specified, a conflict exists. In this case, IPCS responds as if you had
entered DISPLAY(REQUEST).
DISPLAY(NOMACHINE REMARK REQUEST NOSTORAGE SYMBOL
ALIGN) are the IPCS-defined defaults.
The DISPLAY and NODISPLAY parameter options and their meanings are:

266 z/OS MVS IPCS Commands

 SETDEF subcommand

{ DISPLAY } [ ( MACHINE | NOMACHINE ) ]

{ NODISPLAY }
[ ( REMARK | NOREMARK ) ]
[ ( REQUEST | NOREQUEST ) ]
[ ( STORAGE | NOSTORAGE ) ]
[ ( SYMBOL | NOSYMBOL ) ]
[ ( ALIGN | NOALIGN ) ]

MACHINE or NOMACHINE
MACHINE displays the address processing parameters, address, storage
key, and absolute address of the data area being displayed.
DISPLAY(MACHINE) and NODISPLAY(NOMACHINE) request this
data.
For information about storage key values, see the section “Storage
Key”in Chapter 3 of z/Architecture Principles of Operation.
NOMACHINE suppresses the address processing parameters, address,
storage key, and absolute address of the data area being displayed.
DISPLAY(NOMACHINE) and NODISPLAY(MACHINE) suppress it.
REMARK or NOREMARK
REMARK displays the remark associated with a symbol requested by
the SYMBOL value. DISPLAY(REMARK) and
NODISPLAY(NOREMARK) request this data.
NOREMARK suppresses the remark associated with a symbol requested
by the SYMBOL value. DISPLAY(NOREMARK) and
NODISPLAY(REMARK) suppress it.

Note: If both NOREMARK and SYMBOL are selected, IPCS displays as

much of the remark text as possible on the same line as the symbol with
which the remark is associated.
REQUEST or NOREQUEST
REQUEST displays a model LIST subcommand that is used to display
the information you requested. The LIST subcommand parameters
include the data description parameters you specify and other relevant
default parameters (for example, CPU is relevant only for multiprocessor
dumps, REMARK is never relevant).
To modify the attributes of the displayed data, modify the parameters on
the model LIST subcommand and run it. DISPLAY(REQUEST) and
NODISPLAY(NOREQUEST) request this data.
NOREQUEST suppresses the model LIST subcommand.
DISPLAY(NOREQUEST) and NODISPLAY(REQUEST) suppress it unless
no data is requested. In that case, IPCS forces the DISPLAY(REQUEST)
option into effect.
STORAGE or NOSTORAGE
STORAGE displays the storage at the specified or default address, for
the specified or default length. The subcommand displays the storage as
in a printed dump: four words in hexadecimal followed by the EBCDIC
equivalent. DISPLAY(STORAGE) and NODISPLAY(NOSTORAGE)
request this data.
NOSTORAGE suppresses the storage display. DISPLAY(NOSTORAGE)
and NODISPLAY(STORAGE) suppress it.

Chapter 5. IPCS subcommands 267

SETDEF subcommand

SYMBOL or NOSYMBOL
SYMBOL displays the symbol (if any) associated with the dump data
displayed. DISPLAY(SYMBOL) and NODISPLAY(NOSYMBOL) request
this storage.
NOSYMBOL suppresses the symbol associated with the dump data
displayed. DISPLAY(NOSYMBOL) and NODISPLAY(SYMBOL) suppress
it.
ALIGN or NOALIGN
ALIGN displays the storage for LIST output for AREA, STRUCTURE,
BIT, and CHAR pointers aligned to a previous double word boundary.
For example, IP LIST 3. generates this:
LIST 03. ASID(X’0024’) LENGTH(X’1000’) AREA
00000003. 00 000130E1 00000000 00000000 | .............|
00000010. 00FD9A48 00000000 7FFFF000 7FFFF000 |........".0.".0.|
00000020. 7FFFF000 7FFFF000 7FFFF000 7FFFF000 |".0.".0.".0.".0.|

NOALIGN displays the storage for LIST output for AREA,

STRUCTURE, BIT, and CHAR pointers aligned to the requested bit
boundary. For example, IP LIST 3. formats the same storage as this:
LIST 03. ASID(X’0024’) LENGTH(X’1000’) AREA
00000003. 00000130 E1000000 00000000 0000FD9A |................|
00000013. 48000000 007FFFF0 007FFFF0 007FFFF0 |.....".0.".0.".0|
00000023. 007FFFF0 007FFFF0 007FFFF0 00000000 |.".0.".0.".0....|
FLAG(severity)
Specifies that IPCS subcommands eliminate some problem analysis
diagnostic messages based upon the severity of the problem indicated by the
message. Use FLAG to make a report easier to read by eliminating some
messages. The following messages can be suppressed with FLAG:
– Messages produced by IPCS services during the production of a report,
but are not part of the report itself. For example, you can suppress the
following message with FLAG(TERMINATING):
BLS22020I ASCBASCB not equal C’ASCB’
Although FLAG can make a report easier to read, it may eliminate useful
information. For example, message BLS22020I may help you to
understand why a report does not contain information you expected and
may help you locate a storage overlay condition that requires further
analysis.
– Messages produced by an IPCS CLIST or REXX exec. For example, you
can suppress the following message:
BLS18104I Symbol xxx not found
Again, FLAG can make a report easier to read, but it may eliminate
useful information. The author of a CLIST or REXX exec may use FLAG
on FIND and NOTE subcommands to make message suppression and
transmission conditional.
Messages that do not detract from the legibility of a report are generally not
affected by the FLAG value.
The FLAG severity parameters and the messages transmitted follow.
WARNING is the IPCS-defined default.

268 z/OS MVS IPCS Commands

 SETDEF subcommand

FLAG { (ERROR) }
{ (INFORMATIONAL) }
{ (SERIOUS | SEVERE) }
{ (TERMINATING) }
{ (WARNING) }

ERROR
Transmits ERROR, SERIOUS (SEVERE), and TERMINATING messages
and suppresses INFORMATIONAL and WARNING messages. Error
messages describe control blocks or data that point to incorrect control
blocks or data.
INFORMATIONAL
Transmits all messages to your terminal.
SERIOUS or SEVERE
Transmits SERIOUS (SEVERE) and TERMINATING messages and
suppresses INFORMATIONAL, WARNING, and ERROR messages.
Serious or severe messages describe control blocks or data that are not
valid.
TERMINATING
Transmits only TERMINATING messages and suppresses
INFORMATIONAL, WARNING, ERROR, and SERIOUS (SEVERE)
messages.
WARNING
Transmits WARNING, ERROR, SERIOUS (SEVERE), and
TERMINATING messages and suppresses INFORMATIONAL messages.
WARNING messages describe unusual conditions that are not
necessarily wrong but might indicate errors.
LENGTH(length)
Specifies the length of the storage area to be used by dump analysis
subcommands. The length may be 1 through 231 bytes and may be specified
in decimal (nnn), hexadecimal (X'nnn'), or binary (B'nnn') notation.
LENGTH(4) is the IPCS-defined default.
PRINT or NOPRINT
Specifies whether a subcommand's output is to be sent to the print data set,
IPCSPRNT. PRINT sends the subcommand's output to the print data set.
Note that IPCS always sends certain non-report type messages to your
terminal or the TSO/E SYSTSPRT data set.
NOPRINT suppresses sending output to the print data set. NOPRINT is the
IPCS-defined default.
PDS or NOPDS
Specifies whether a subcommand output is to be sent to a member of the
defined partitioned data set (PDS), allocated by ddname IPCSPDS. PDS
sends the subcommand output to the defined member of PDS. The defined
member of PDS means that the name of this member will be equivalent to
the name of the used IPCS subcommand. Note that IPCS always sends
certain non-report type messages to your terminal or the TSO/E SYSTSPRT
data set.
NOPDS suppresses sending output to the PDS.NOPDS is the IPCS-defined
default.

Chapter 5. IPCS subcommands 269

SETDEF subcommand

TERMINAL or NOTERMINAL
Specifies whether a subcommand's output is to be sent to your terminal or,
for a batch job, to the TSO/E SYSTSPRT data set.
TERMINAL sends the subcommand's output to your terminal in an
interactive IPCS session and to the TSO/E SYSTSPRT data set if IPCS is
being run in a batch job.
NOTERMINAL suppresses sending output. However, if NOPRINT is also in
effect, all IPCS subcommands, except the SUMMARY subcommand, override
the NOTERMINAL option and send their output as if the TERMINAL
option had been specified. NOTERMINAL is the IPCS-defined default.

Note: You may want to use the SETDEF subcommand to set the defaults to
NOTERMINAL and NOPRINT. When these defaults are in effect, you need
to specify only the PRINT parameter on a subcommand to send its output to
the print data set, but not to the terminal. In contrast, with the standard
defaults of NOPRINT and TERMINAL, the same subcommand with PRINT
sends its output to both destinations. Both PRINT and NOTERMINAL are
needed to selectively send output to only the print data set.
See Table 2 on page 3 for a summary of the output possibilities.
TEST or NOTEST
Specifies if IPCS is supporting testing of IPCS code or is being used to
analyze problem data. TEST places IPCS in a mode designed to support
interactive testing of code that operates in the IPCS environment. It is not
recommended that you use this mode for any other purpose.
If you anticipate an abnormal ending while testing a new exit routine
written to function in the environment provided by the ASCBEXIT,
TCBEXIT, or VERBEXIT subcommands and you want to use TSO/E TEST
facilities to isolate the cause of any problems, you should specify the TEST
parameter. When TEST is in effect, IPCS allows the TMP, the TSO/E TEST
ESTAI functions, or both, to gain control when an abnormal ending occurs.
TEST mode also activates error-detection functions that have been developed
to isolate dump data examination problems. Detected errors cause IPCS to
abend, so that problems may be trapped close to the point of error.
NOTEST places IPCS in the production mode of operation. Automatic error
recovery is attempted should errors occur in the IPCS environment.
When the NOTEST parameter is in effect, IPCS automatically recovers from
most abnormal endings without permitting TSO/E TEST to gain control.
NOTEST is the IPCS-defined default.
VERIFY or NOVERIFY
Specifies whether subsequent subcommands are to produce output and send
it to the destination or destinations specified by the PRINT and TERMINAL
parameters.
VERIFY specifies that subcommands should produce output and send it.
VERIFY is the IPCS-defined default.
NOVERIFY specifies that subsequent subcommands are not to produce
output or send it anywhere, regardless of the PRINT and TERMINAL
parameters.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the SETDEF subcommand.

270 z/OS MVS IPCS Commands

 SETDEF subcommand

v Example: Change the IPCS-defined defaults.

– Action: COMMAND ===> setd dsn(’d4.dmp.svc20’) asid(X’0008’) list
– Result: IPCS produces the output shown in Figure 26.

/*------------ Default Values for IPCS Subcommands ---------------*/

SETDEF NOPRINT TERMINAL NOPDS /* Routing of displays */
SETDEF FLAG(WARNING) /* Optional diagnostic messages */
SETDEF CONFIRM /* Double-checking major acts */
SETDEF NOTEST /* IPCS application testing */
SETDEF DSNAME(’D4.DMP.SVC20’)
SETDEF LENGTH(4) /* Default data length */
SETDEF VERIFY /* Optional dumping of data */
SETDEF DISPLAY(NOMACHINE) /* Include storage keys, .... */
SETDEF DISPLAY( REMARK) /* Include remark text */
SETDEF DISPLAY( REQUEST) /* Include model LIST subcommand */
SETDEF DISPLAY(NOSTORAGE) /* Include contents of storage */
SETDEF DISPLAY( SYMBOL) /* Include associated symbol */
SETDEF ASID(X’0008’) /* Default address space */

Figure 26. Example: results of changing IPCS-defined values

SMFDATA subcommand — obtain system management facilities

records
Use the SMFDATA subcommand to recover system management facilities (SMF)
records from buffers in the dump and transfer them to a pr-eallocated SMF
(VSAM) data set or a log stream if RECORDING(LOGSTREAM) had been in use at
the time of the dump.

The output data set must be:

v Pre-allocated to the data set with a ddname of SMFDATA
v Using the same control interval size as the defined SMF data sets
v Large enough to accommodate all the SMF data in the dump
v Allocated and used for only this purpose
v Defined with a low offload threshold (for example HIGHOFFLOAD(10)) to
account for heavy utilization of the coupling facility structure.

The output log stream must be:

v Defined with the administrative data utility (IXCMIAPU or IXCM2APU) with a
log stream name of IFASMF.DUMP00
v Defined with a MAXBUFSIZE that matches or exceeds the defined
MAXBUFSIZE value of the logstream data that resides in the dump.
v Accessible from the local system
v Sized large enough to hold the data in the dump
v Allocated and used for only this purpose.
v Syntax

SMFDATA

v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the SMFDATA subcommand.

Chapter 5. IPCS subcommands 271

SSIDATA subcommand

SSIDATA subcommand — display subsystem information

Use the SSIDATA subcommand to display information about subsystems defined
to the subsystem interface (SSI), including:
v The number of subsystems defined to the SSI
v The subsystem name
v Whether the subsystem is the primary subsystem
v Whether the subsystem is dynamic
v The status of the subsystem
v Whether the subsystem accepts or rejects the SETSSI operator command
v The address of the subsystem request router
v The function routines that the subsystem supports
v Syntax

SSIDATA

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[FLAG(severity)]
[PRINT | NOPRINT]
[TERMINAL | NOTERMINAL]
[TEST | NOTEST]

v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the SSIDATA subcommand.
v Example: The SSI component topic in z/OS MVS Diagnosis: Reference shows an
example of SSIDATA output.

STACK subcommand — create a symbol in the stack

Use the STACK subcommand to add a symbol to the symbol table for the current
source in your dump directory. The STACK subcommand adds a created symbol in
the form Znnnnn to the end of the stack in the symbol table. To determine the
number nnnnn, IPCS uses the smallest numeric suffix that is greater than the suffix
currently in use. See the z/OS MVS IPCS User's Guide for more information about
stack symbols.
v Related subcommands
– EQUATE
– DROPSYM
– LISTSYM
– RENUM
v Syntax

272 z/OS MVS IPCS Commands

 STACK subcommand

STACK [ data-descr | X ]
[ DROP | NODROP ]

-------- SETDEF-Defined Parameter --------------------------

Note: You can override the following SETDEF parameter.
See “SETDEF subcommand — set defaults” on page 262.
[ TEST | NOTEST ]

v Parameters
data-descr or X
Specifies the address and attributes to be associated with the symbol being
defined. The data description parameter consists of five parts:
– An address (required when data-descr is explicitly specified on the
subcommand)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter. However, the following exception
applies only to STACK:
– If you omit the data description parameters, the default for the STACK
subcommand is X, which is the most recently accessed address.
DROP or NODROP
Specifies whether the created symbol can be deleted or not from the symbol
table by a DROPSYM subcommand without a PURGE parameter:
– DROP specifies that the symbol can be deleted.
– NODROP specifies that the symbol cannot be deleted. However,
NODROP can be overridden by a PURGE parameter on the DROPSYM
subcommand.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the STACK subcommand.

STATUS subcommand — describe system status

Use the STATUS subcommand to display data that are typically examined during
the initial part of the problem determination process. STATUS produces different
diagnostic information depending on the report type parameter or parameters
entered: SYSTEM, CPU, WORKSHEET, and FAILDATA.

The information displayed by STATUS for each central processor is helpful in

problem analysis for most dumps. However, the ANALYZE or SUMMARY
subcommands can be more helpful:
v If a dump is taken as a result of operator intervention, such as an SVC dump
from a DUMP operator command or a stand-alone dump. In these dumps, IPCS
might not be able to identify appropriate units of work from which analysis can
proceed. In fact, by the time the operator has recognized the need for a dump
and requested one, the unit of work that caused the problem might no longer
exist.

Chapter 5. IPCS subcommands 273

STATUS subcommand

v Some problems involve the interaction of multiple units of work. If one of the
units of work detects a problem and requests a dump, the analysis of the
STATUS subcommand focuses primarily on the unit of work that requested the
dump.
v Related subcommands
– ANALYZE
– CBSTAT
– LIST
– SUMMARY
v Syntax

{ STATUS }
{ ST }

-------- Report Type Parameters ----------------------------

[ SYSTEM | NOSYSTEM ]
[ CPU[(cpu)] [REGISTERS | NOREGISTERS ] ]
[ [VECTOR | NOVECTOR ] ]
[ [CONTENTION | NOCONTENTION] ]
[ [DATA | NODATA ] ]
[ ]
[ NOCPU ]
[ WORKSHEET | NOWORKSHEET ]
[ FAILDATA | NOFAILDATA ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report Type Parameters

Use these parameters to select the type of report. If you omit a report type
parameter, the default is SYSTEM, CPU, WORKSHEET, and FAILDATA. For
more information about defaults, see Defaults.
SYSTEM or NOSYSTEM
Specifies or suppresses the system status information. The SYSTEM
parameter displays:
– The nucleus member name
– I/O configuration data
– The sysplex name
– Time-of-day (TOD) clock in both local and Greenwich mean time (GMT)
– The name of the program that produced the dump
– The name of the program that requested the dump
SYSTEM specifies the information. See Example 1 for an example of the
SYSTEM report. NOSYSTEM suppresses the information.

274 z/OS MVS IPCS Commands

 STATUS subcommand

CPU[(cpu)] or NOCPU
Specifies or suppresses the CPU status information. The CPU parameter
displays for each central processor:
– The PSW and its analysis
– A description of the current unit of work by its type of control block, for
example, the address space control block (ASCB), the task control block
(TCB), or the system request block (SRB)
– A list of locks held
– A summary of the current function recovery routine (FRR) stack
– The contents of the general purpose registers and control registers
– The contents of the access registers
– The contents of the vector registers for each central processor that has a
Vector Facility installed
– A breakdown of resources held by the unit of work
NOCPU suppresses the information.
The following parameters modify the CPU report. If any of these parameters
are specified and CPU is not specified, CPU is the default.
REGISTERS or NOREGISTERS
Specifies or suppresses the formatting of the general purpose and control
registers for the specified central processors. REGISTERS specifies the
register data. The abbreviation REGS can be used for REGISTERS.
NOREGISTERS suppresses register data and is the default.
VECTOR or NOVECTOR
Specifies or suppresses the formatting of the vector registers for the
specified central processors. VECTOR specifies the vector register data.
NOVECTOR suppresses vector register data and is the default.
CONTENTION or NOCONTENTION
Specifies or suppresses the formatting of contention information for the
unit of work that was active on the central processor(s) at the time of the
dump. CONTENTION requests contention information.
NOCONTENTION suppresses contention information and is the default.

Note: If you want to format contention information for the entire

dumped system, use the ANALYZE subcommand instead of STATUS.
DATA or NODATA
Specifies or suppresses formatting of central processor-related control
blocks and global system control blocks. DATA requests the control
blocks. Global system control blocks that are not central
processor-related appear before individual central processor-related
information. If you specify a particular central processor number, global
system control blocks are not formatted.
The central processor-related control blocks for this subcommand are:
– Logical configuration communication area (LCCA)
– Physical configuration communication area (PCCA)
– Prefixed save area (PSA)
– Supervisor control FLIH save area (SCFS)
– The linkage stack for the active unit of work
The global system control blocks for this subcommand are:

Chapter 5. IPCS subcommands 275

STATUS subcommand

– Common system data (CSD)

– System verification table (SVT)
NODATA suppresses the control blocks and is the default.
WORKSHEET or NOWORKSHEET
Specifies or suppresses the diagnostic worksheet, which contains central
processor information. The WORKSHEET diagnostic report describes the
state of the system and each central processor in the system, and includes:
– The CPU serial number
– The CPU version
– The CPU address
– The SDUMP parameter list, if the dump is an SVC dump or a
SYSMDUMP
– The current wait state messages
WORKSHEET specifies the diagnostic worksheet. All central processors in
the system are in the report. For stand-alone dumps, IPCS obtains much of
the information from the store status records. For SVC dumps, the
processor-related data does not contain the store status data. The
WORKSHEET parameter displays the SDUMP parameter list for SVC
dumps. See Example 3 for an example of the WORKSHEET report.
NOWORKSHEET suppresses the diagnostic worksheet.
FAILDATA or NOFAILDATA
Specifies or suppresses formatting of the system diagnostic work area
(SDWA), which is in the SVC dump header. FAILDATA specifies formatting
of the SDWA. See Example 4 for an example of the FAILDATA report.
NOFAILDATA suppresses formatting of the SDWA.
v Defaults
Table 16 lists the defaults for the STATUS report type parameters.
Table 16. Defaults for the STATUS report type
Parameters on the STATUS Reports Requested Example Command and Results
subcommand
No report type parameter SYSTEM, CPU, WORKSHEET, COMMAND ===> status
and FAILDATA
STATUS displays SYSTEM, CPU, WORKSHEET,
and FAILDATA reports.
One or more of the report type The requested report or COMMAND ===> status system cpu(1)
parameters: SYSTEM, CPU, reports: SYSTEM, CPU,
WORKSHEET, FAILDATA WORKSHEET, or FAILDATA STATUS displays SYSTEM and CPU(1) reports.
One or more of the negative Not specifying the suppressed COMMAND ===> status nosystem
report type parameters: reports
NOSYSTEM, NOCPU, STATUS displays CPU and WORKSHEET
NOWORKSHEET, NOFAILDATA reports.
No report type parameter, but CPU report COMMAND ===> status noregisters
one or more CPU parameters:
REGISTERS, NOREGISTERS, STATUS displays a CPU report.
VECTOR, NOVECTOR,
CONTENTION,
NOCONTENTION, DATA,
NODATA

v Return Codes

276 z/OS MVS IPCS Commands

 STATUS subcommand

See “Standard subcommand return codes” on page 46 for a description of the

return codes produced by the STATUS subcommand.
v Example 1: Produce a system status report.
– Action: COMMAND ===> status system
– Result: Figure 27 shows the output produced by this action. Note that a list of
the SVC dump options will follow the output shown.

SYSTEM STATUS ▌1▐

Nucleus member name: IEANUC01 ▌2▐
I/O configuration data: ▌3▐
IODF data set name: SYS0.IODF52
IODF configuration ID: CONFIG00
EDT ID: 00
Sysplex name: PLEX01 ▌4▐
TIME OF DAY CLOCK: A9B7540D 54AD1405 08/12/1994 10:54:28.305617 local
▌5▐
TIME OF DAY CLOCK: A9B789B2 3DAD1405 08/12/1994 14:54:28.305617 GMT
Program Producing Dump: SVCDUMP ▌6▐
Program Requesting Dump: DATSVY02
Incident token: LOCAL S520 08/12/1994 14:54:23.888770 GMT

Figure 27. Example output from STATUS SYSTEM command

▌1▐ Identifies the STATUS report type, SYSTEM.

▌2▐ Identifies the nucleus member name, IEANUC01, that was initialized
at system installation.
▌3▐ Gives information about the I/O configuration that was active when
the dump was produced. IPCS identifies the name of the IODF data
set, the configuration identifier, and the eligible device table (EDT)
definition.
▌4▐ Identifies the sysplex name, PLEX01, specified in the COUPLExx
parmlib member.
▌5▐ Displays a TOD clock value placed in the dump to indicate when the
dump was produced. The TOD clock value is in hexadecimal and in a
date and time of day for local time and Greenwich mean time (GMT).
To determine local time, the system uses field CVTTZ in the CVT.
▌6▐ Identify the programs that are requesting and producing the dump.
v Example 2: Produce a CPU status report.
– Action: COMMAND ===> status cpu registers contention
– Result: Figure 28 on page 278 shows the output that is produced.

Chapter 5. IPCS subcommands 277

STATUS subcommand

CPU STATUS: ▌1▐

PSW=070C1000 83D00B72 (RUNNING IN PRIMARY, KEY 0, AMODE 31, DAT ON, SUPERVISOR STATE)
DISABLED FOR PER ▌2▐
ASID(X’0015’) 03D00B72. DATSVY02+03CA IN EXTENDED PRIVATE
ASCB21 at F9CD80, JOB(DAESVY01), for the home ASID ▌3▐
ASXB21 at 6FE038 for the home ASID. No block is dispatched
HOME ASID: 0015 PRIMARY ASID: 0015 SECONDARY ASID: 0015
GPR VALUES ▌4▐
0-3 00000000 03D017B0 00000000 03D01A12
4-7 03D00EC1 03D00CE8 006D4FF8 FD000000
8-11 03D025BF 83D007A8 03D015C0 03D017A7
12-15 03D01830 03D015C0 03D019EB 03D00DA9
IEA11015I The requested ALETs are zero. ▌5▐
CONTROL REGISTER VALUES ▌6▐
0-3 5EB1EE40 00C0407F 002B5040 00800015
4-7 00000015 01756540 FE000000 00C0407F
8-11 00000000 00000000 00000000 00000000
12-15 01F7C27F 00C0407F DF881755 7F704008
THE PRECEDING STATUS CPU INCLUDED THE REGS OPTION

Figure 28. Example output from STATUS CPU command

▌1▐ Identifies the STATUS report type, CPU. The CPU address is omitted
because a virtual dump is being processed.
▌2▐ Displays the program status word (PSW) followed by a description of
what the PSW indicates. IPCS extracts the current PSW from the
dump header record for virtual storage dumps and from the store
status record for absolute storage dumps. One of the following
descriptions providing PSW status might appear after the PSW:
- NO WORK WAIT
- DISABLED WAIT STATE CODE xxx SUPPLEMENT CODE yyyyy
v xxx is the wait state code in hexadecimal
v yyyyy is supplemental information in hexadecimal for the wait
state code. The format is dependent on the particular wait state.
See z/OS MVS System Codes for more information.
- RUNNING IN mode, KEY k, AMODE aa, datmode, state
v mode is the address space addressability of either primary or
secondary.
v k is the current storage key of 0 through F.
v aa is the current addressing mode of either 24 or 31 bit.
v datmode is either DAT-ON or DAT-OFF
v state is either PROBLEM STATE or SUPERVISOR STATE
- ENABLED | DISABLED
When the PSW is enabled or disabled, a list of the interrupts is
displayed.

Note: For dumps generated by a stand-alone dump, the system

operator must perform the store status operation before IPLing the
stand-alone dump program. If the store status operation is not done,
the PSW will not be accurate.
▌3▐ Displays the current ASCB, ASXB, or TCB. The output might also
display the processor status. One of the following descriptions can
appear:

278 z/OS MVS IPCS Commands

 STATUS subcommand

- HOME ASID: hhhh PRIMARY ASID: pppp SECONDARY ASID:

ssss IPCS identifies the applicable address spaces (in hexadecimal)
relevant to the unit of work running on the CPU at the time of the
dump.
v hhhh is the home address space identifier
v pppp is the primary address space identifier
v ssss is the secondary address space identifier
- HOLDING LOCK(S): lockname1 lockname2 ...
IPCS identifies the locks that are held by the unit of work that is
running on the CPU at the time of the dump. See z/OS MVS
Diagnosis: Reference for the list of locks.
- CURRENT FRR STACK IS: stack-name
PREVIOUS FRR STACK(S): stack-name1 stack-name2 ...
STATUS identifies the current FRR stack and the previous FRR
stack names and displays the previous FRR stack names in the
order that the stack will get control.

Note: If the CURRENT stack is the NORMAL stack, the

PREVIOUS FRR STACK(S) is not displayed.
▌4▐ Displays the general register (GPR) contents in hexadecimal.
▌5▐ Displays the access register contents in hexadecimal or displays a
message that all ALETs are zero.
▌6▐ Displays the control register contents in hexadecimal.
Not shown
If the VECTOR parameter is specified and if a Vector Facility is
installed on the processor, the vector registers are displayed in
hexadecimal following the control registers.
Not shown
If this dump had contention data, the contention report follow the
register information. The contention data report lists the held
resources, resources being waited on, and any contention data related
to other units of work.
v Example 3: Produce a diagnostic worksheet.
– Action: COMMAND ===> status worksheet
– Result: Figure 29 on page 280 shows the output that is produced.

Chapter 5. IPCS subcommands 279

STATUS subcommand

MVS Diagnostic Worksheet ▌1▐

Dump Title: SERV2_DUMP1 ▌2▐

CPU Model 3090 Version FF Serial no. 176280 Address 01 ▌3▐

Date: 05/05/1994 Time: 16:59:35.414381 Local

Original dump dataset: SERV2.DMP00001

Information at time of entry to SVCDUMP:

HASID 0001 PASID 0001 SASID 0001 PSW 070C1000 83930B82

CML ASCB address 00000000 Trace Table Control Header address 7F731000

System reset nondispatchability Trace Table Control header address 7F5B5000 ▌4▐

Dump ID: 001 ▌5▐

Error ID: N/A

SDWA address N/A

SYSTEM RELATED DATA ▌6▐

CVT SNAME (154) S520 VERID (-18) HBB5520 DRIVER08

CUCB (64) 00FCF8F8 PVTP (164) 00FDDED0 GDA (230) 01D551A0

RTMCT (23C) 00FC0780 ASMVT (2C0) 00FD3250 RCEP (490) 014D9F80

CSD Available CPU mask: 4000 Alive CPU mask: 40000000 00000000
Number of active CPUs: 00000001
System set non-dispatchable by SVC dump

PROCESSOR RELATED DATA ▌7▐

NAME OFFSET | CPU 01

------ LCCA --------------+-----------------------------------------
IHR1 Recursion 208 | 00
SPN1/2 Spin 20C | 0000
CPUS CPU WSAVT 218 | 00F8AA48
DSF1/2 Dispatcher 21C | 0080
CRFL ACR/LK flgs 2B4 | 00000000
------ PSA ---------------+-----------------------------------------
TOLD Curr TCB 21C | 00000000
AOLD Curr ASCB 224 | 00F4A580
SUPER Super Bits 228 | 00000000
CLHT Lock Table 280 | 00FCDA18
LOCAL Local lock 2EC | 00000000
CLHS Locks held 2F8 | 80000000
CSTK FRR stack 380 | 00000C00
SMPSW SRB Disp PSW 420 | 070C0000
424 | 8267AE00
PSWSV PSW Save 468 | 070C0000
46C | 8264BFFC
MODE Indicators 49F | 04

Figure 29. Example output from STATUS WORKSHEET command

The SDUMP parameter list appears if this is an SVC dump; Figure 30 on page
281 shows as example.

280 z/OS MVS IPCS Commands

 STATUS subcommand

SDUMP Parameter List

+0000 FLAG0.... 1E FLAG1.... A1 SDATA.... 9920 DCBAD.... 00000000 STORA.... 00000000

+000C HDRAD.... 01E29BC0 ECBAD.... 036F4288 SRBAD.... 036F4288 CASID.... 0001 TASID.... 0001
+0018 ASIDP.... 00000000 SUMLP.... 00000000 SDDAT.... 00000000 FLAG2.... 00 CNTL1.... C0
+002A TYP1..... 10 VERSN.... 03 SDTA2.... 65004000 EXIT..... 6500 SDAT3.... 40
+002F SDAT4.... 00 SPLST.... 00000000 KYLST.... 00000000 RGPSA.... 00000000 DCBA..... 00000000
+0040 STRAL.... 00000000 HDRA..... 00000000 ASDLA.... 00000000 SMLA..... 00000000 SBPLA.... 00000000
+0054 KEYLA.... 00000000 LSTDP.... 00000000 LSTDA.... 00000000 SMLLP.... 00000000 SMLLA.... 00000000
+0068 PSWRP.... 00000000 PSWRA.... 00000000 SYMAD.... 00000000 SYMA..... 00000000 IDAD..... 00000000
+007C IDA...... 00000000 SLADR.... 00000000 SLALT.... 00000000 ITADR.... 01E27578 ITALT.... 00000000
+0090 RMADR.... 00000000 RMALT.... 00000000 PDADR.... 00000000 PDALT.... 00000000 JLADR.... 00000000
+00A4 JLALT.... 00000000 DLADR.... 00000000 DLALT.... 00000000

Figure 30. Example of an SDUMP parameter list for an SVC dump

▌1▐ Identifies the STATUS report type, WORKSHEET.

▌2▐ Displays the title, date, and time from the dump header record.
▌3▐ This section identifies the CPU model, version, serial number, and
address. The end of this section will also display wait state messages,
if they are current.
▌4▐ Displays the Trace Table Control Header address of the SNAPTRC,
which was issued if the system was reset to be dispatchable because
the system has been kept non-dispatchable longer than the
MAXSNDSP value.
▌5▐ The identifiers of the dump and the error.
▌6▐ Lists system-related data by displaying key fields and their
hexadecimal offsets in the CVT and by displaying information about
the processors in the system that appears in the CSD. The SYSTEM
RELATED DATA section:
- Provides information for both SVC dumps and stand-alone dumps.
- Displays “N/A” for any missing data.
- May display the following texts after the CSD data:
v System set non-dispatchable by SVC Dump
v ACR in progress
▌7▐ Lists processor-related data. For each CPU, IPCS displays the contents
of the PSW, control registers (CR) 0 and 6, and selected fields from
the LCCA and PSA. The PROCESSOR RELATED DATA section:
- Does not display the store status data for SVC dumps
- Fills in a CPU header and column for each nonzero PCCAVT entry
- Displays “N/A” for any missing data.
- Repeats the PROCESSOR RELATED DATA section as many times
as necessary to include all processor-related data that was dumped.
The number of CPU columns depends on the recommended
display width that is set by IPCS to be the lesser of the terminal
width and the print data set LRECL.
v Example 4: Produce an SDWA report.
– Action: COMMAND ===> status faildata
– Result: Figure 31 on page 282 shows the output that is produced.

Chapter 5. IPCS subcommands 281

STATUS subcommand

▌1▐ * * * DIAGNOSTIC DATA REPORT * * *

▌2▐ SEARCH ARGUMENT ABSTRACT

RIDS/DMPSD998#L RIDS/DMPSD998 AB/S00C1 PRCS/00000001 REGS/0B5CA

RIDS/DMPESTAE#R

Symptom Description
------- -----------
RIDS/DMPSD998#L Load module name: DMPSD998
RIDS/DMPSD998 Csect name: DMPSD998
AB/S00C1 System abend code: 00C1
PRCS/00000001 Abend reason code: 00000001
REGS/0B5CA Register/PSW difference for R0B: 5CA
RIDS/DMPESTAE#R Recovery routine csect name: DMPESTAE
▌3▐ SERVICEABILITY INFORMATION NOT PROVIDED BY THE RECOVERY ROUTINE

Program id
Recovery Routine Label
Date Assembled
Module Level
Subfunction
▌4▐ Time of Error Information

PSW: 070C2000 81E0D616 Instruction length: 02 Interrupt code: 0001

Failing instruction text: 920A1005 00000000 5870A1F8

Registers 0-7
GR: 40000004 00C13300 00000004 00C13300 00C13304 00C13300 00C136E8 00C1349C
AR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Registers 8-15
GR: 00C13350 00C13300 01E01260 81E0D04C 01E0E04B 01E01260 00000000 80AD5A88
AR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Home ASID: 000C Primary ASID: 000C Secondary ASID: 000C

PKM: 0080 AX: 0000 EAX: 0000

RTM was entered because of a program check interrupt.

The error occurred while an enabled RB was in control.
No locks were held.
No super bits were set.
▌5▐ STATUS FROM THE RB WHICH ESTABLISHED THE ESTAE EXIT

PSW and registers are the same as those from the time of error.

▌6▐ RECOVERY ENVIRONMENT

Recovery routine type: ESTAE recovery routine

Recovery routine entry point: 01E0D8A8
FRR parameter area on entry to FRR:
+00 00C13350 00C13300 01E01260 81E0D04C 01E0E04B 01E01260
There were no outstanding I/O operations to purge.

▌7▐ NO DATA EXISTS IN THE VARIABLE RECORDING AREA

Figure 31. Example output from STATUS FAILDATA command

▌1▐ Identifies the report type, DIAGNOSTIC DATA REPORT.

▌2▐ The search argument abstract is generated from the error-related
information in the SDWA. It is useful for problem searches against
customer or IBM problem-reporting data bases.

Note: If you report the problem to IBM, include symptoms from this
abstract in the problem report.
▌3▐ Indicates information that was not available because the recovery

282 z/OS MVS IPCS Commands

 STATUS subcommand

routine did not provide it. When this information is available, it

appears in section ▌2▐ under the title “Other Serviceability
Information”.
▌4▐ Provides PSW, register, and ASID-related error information, along
with failure reasons and environments and, if applicable, super or
spin bit settings.

Note: The locks that were held at the time of error might have been
released by RTM, thus resulting in the statement of No locks were
held in the Time of Error Information report.
▌5▐ Presents second-level status information as indicated by the second
set of registers and their corresponding PSW, which are located in the
SDWA.
▌6▐ Provides details about the recovery environment for the error. This
section may include one or more of the following items:
- Recovery routine type
- PSW at entry to functional recovery routine (FRR)
- Recovery routine entry point (ESTAE/ESTAI/ARR)
- FRR parameter area contents
- Information relevant to the previous recovery environment
- Error entry information
- Status of I/O operations
▌7▐ Indicates that the variable recording area is empty. If the area
contained data, it is displayed here in hexadecimal and EBCDIC
format. When this area is in key-length-data format, each
key-length-data structure is individually formatted.

STRDATA subcommand — format coupling facility structure data

Use the STRDATA subcommand to format coupling facility structure data.
Depending on the parameters you specify, you can obtain information at the
summary or detail level and about one or more coupling facility structures.

If duplexing rebuild is supported for a structure, duplexing control information is

returned in addition to the dump header information for each structure instance.
The control information is returned regardless of whether duplexing is currently
active for the structure.

For more information about the reports generated by the STRDATA subcommand,
see the XES chapter of z/OS MVS Diagnosis: Reference.

Note: To diagnose problems related to XES, you may also want to use the
XESDATA and COUPLE subcommands.
v Syntax

Chapter 5. IPCS subcommands 283

STRDATA subcommand

STRDATA

-------- Data Selection Parameters --------

{ DETAIL }
{ SUMMARY }

-------- Report Type Parameters --------

{ ALLSTRS }
{ STRNAME(strname,strdumpid),... }

-------- Additional Filter Parameters --------

[ ALLDATA ]
[ ARB ]
[ COCLASS(coclass) ]
[ EMCONTROLS(emcontrols) ]
[ ENTRYID(entryid) ]
[ ENTRYNAME(entryname) ]
[ EVENTQS(conid) ]
[ LISTNUM(listnum) ]
[ LOCKENTRIES(lockentries) ]
[ STGCLASS(stgclass) ]
[ USERCNTLS(usercntls) ]

-------- Cache Specifier Parameters --------

[ ENTRYPOS(entrypos) ]
[ ORDER ]

-------- List Specifier Parameters --------

[ ENTRYPOS(entrypos) ]
[ ORDER ]
[ ENTRYKEY(entrykey) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
If you omit all parameters, the defaults are SUMMARY and ALLSTRS.
v Data Selection Parameters
Use these parameters to limit the scope of the data in the report. If you omit
these parameters, the default is SUMMARY.
SUMMARY
Requests summary information for each report you specify. The report
output is STRDATA ALL STRUCTURES SUMMARY REPORT. The output
fields for each structure are:
– Structure name

284 z/OS MVS IPCS Commands

 STRDATA subcommand

– Structure type
– Structure dump ID
– Coupling facility information
– Facility name
– A summary of coupling facility structure controls
An example is:
COMMAND ===> STRDATA SUMMARY
DETAIL
Requests detailed information for each report you specify. The report output
is STRDATA ALL STRUCTURES DETAIL REPORT The output fields for each
structure are:
– Structure name
– Structure type
– Structure dump ID
– Coupling facility information
– Facility name
– All of the coupling facility structure controls
– List of assigned users
– If applicable, duplexing control information including
- Duplexing-active indicator
- Remote facility node descriptor (ND) and system identifier (SYID)
- Remote structure identifier (SID) and structure authority (SAU)
An example is:
COMMAND ===> STRDATA DETAIL
v Report Type Parameters
Use these parameters to select the type of report. If you omit a report type
parameter, the default is ALLSTRS.
ALLSTRS
Requests information about all coupling facility structures found in the
dump. The report output is STRDATA ALL STRUCTURES SUMMARY
REPORT. The output fields for each structure are:
– Structure name
– Structure type
– Structure dump ID
– Coupling facility information
– Facility name
– A summary of coupling facility structure controls
COMMAND ===> STRDATA ALLSTRS
STRNAME ((strname,strdumpid),(strname,strdumpid),...)
Requests information about the coupling facility structures listed. Structures
may be list, cache, or any combination of list and cache.

Note: Lock structures are not dumped.

The report output is CACHE STRUCTURE SUMMARY REPORT The output
fields for each structure name specified are:
– Structure name

Chapter 5. IPCS subcommands 285

STRDATA subcommand

– Structure type
– Structure dump ID
– Coupling facility information
– Facility name
– A summary of coupling facility cache structure controls
The strname specifies the name of a structure. For example:
COMMAND ===> STRDATA STRNAME((CACHE01))

Note: If you specify a list structure in strname, the report output is a List
Structure Summary Report.
At the end of a strname, an asterisk (*) may be used as a generic character to
include in the report all structure names having the specified characters in
common. The following subcommand specifies all structure names
beginning with the characters ‘LIST’ and the report includes structures
LIST01, LIST02, LIST03, and so forth.
COMMAND ===> STRDATA STRNAME((LIST*))
The strdumpid specifies an instance of the structure in the dump. A reason
you may have more than one instance of a structure in a dump is if a
structure is in rebuild processing or is in the Duplex Established phase,
when the dump is captured. If a structure dump ID is not provided,
information for all the structures in the dump with the same name are
displayed. The strdumpid is specified in hexadecimal and without quotation
marks, as this example shows:
COMMAND ===> STRDATA STRNAME((CACHE01,0101))
The STRDATA STRNAME parameter is associated with the STRNAME
parameter of the IXLCONN macro.
ALLDATA
Requests the display of all data found in the dump for the specified
structures. When ALLDATA is specified with STRNAME, all the data
regarding the specified structure is presented. When ALLDATA is specified
with ALLSTRS, all the data found for all the structures in the dump is
presented. The report output is:
– LIST STRUCTURE ALLDATA SUMMARY REPORT
– ASSOCIATED REQUEST BLOCK REPORT
– EVENT MONITOR CONTROLS REPORT
– EVENT QUEUE CONTROLS REPORT
– LIST NUMBER ENTRY POSITION SUMMARY REPORT
– LOCK ENTRIES REPORT
– USER CONTROLS REPORT
For the output fields in the report, see the output fields for ARB,
ENTRYPOS, LOCKENTRIES, and USERCNTLS. If a cache structure had
been specified, then all reports pertaining to cache structures would have
been displayed.
An example is:
COMMAND ===> STRDATA STRNAME((LIST02)) ALLDATA
v Additional data selection parameters
COCLASS (ALL | coclass,coclass:coclass,...)
Requests information by cast-out class for a coupling facility cache structure.

286 z/OS MVS IPCS Commands

 STRDATA subcommand

The coclass can be a single cast-out class, a range of classes, or a list of

noncontiguous classes. When you specify a range, separate the first and last
classes in the range with a colon. When you specify a list, separate the list
members with commas.
The report output is:
– STRDATA ALL STRUCTURES SUMMARY REPORT
– CASTOUT CLASS SUMMARY REPORT
The output fields for each coclass specified are:
– Class type
– Class
– Class status
– Cast-out class controls
The STRDATA COCLASS parameter is associated with:
– The NUMCOCLASS parameter of the IXLCONN macro
– The COCLASS parameter of the IXLCACHE macro
An example is:
COMMAND ===> STRDATA COCLASS(01)
STGCLASS (ALL | stgclass,stgclass:stgclass,...)
Requests information by storage class for a coupling facility cache structure.
The stgclass can be a single storage class, a range of classes, or a list of
noncontiguous classes. When you specify a range, separate the first and last
classes in the range with a colon. When you specify a list, separate the list
members with commas.
The report output is:
– STRDATA ALL STRUCTURES SUMMARY REPORT
– STORAGE CLASS SUMMARY REPORT
The output fields for each storage class specified are:
– Class type
– Class
– Class status
– Class control information
The STRDATA STGCLASS parameter is associated with:
– The NUMSTGCLASS parameter of the IXLCONN macro
– The STGCLASS parameter of the IXLCACHE macro
An example is:
COMMAND ===> STRDATA STGCLASS(01)
LISTNUM (ALL | listnum,listnum:listnum,...)
Requests information by list number in a coupling facility list structure. The
listnum can be a single list number, a range of numbers, or a list of
noncontiguous numbers. When you specify a range, separate the first and
last numbers in the range with a colon. When you specify a list, separate the
list members with commas.
The report output is:
– STRDATA ALL STRUCTURES SUMMARY REPORT
– LIST NUMBER SUMMARY REPORT

Chapter 5. IPCS subcommands 287

STRDATA subcommand

The output fields for each list number specified are:

– List number
– List number status
– Summary of the list controls
The STRDATA LISTNUM parameter is associated with:
– The LISTHEADERS parameter of the IXLCONN macro
– The LISTNUM parameter of the IXLLIST macro
An example is:
COMMAND ===> STRDATA LISTNUM(01)
EMCONTROLS(ALL | listnum,listnum:listnum,...)
Requests information about event monitor controls (EMCs) associated with a
list structure identified by its list number. The listnum can be a single list
number, a range of list numbers, or a list of noncontiguous list numbers.
When you specify a range, separate the first and last identifiers in the range
with a colon. When you specify a list number, separate the list numbers with
commas.
The report output is:
– STRDATA ALL STRUCTURES SUMMARY/DETAIL REPORT
– EVENT MONITOR CONTROLS SUMMARY/DETAIL REPORT
The output fields for each list number are:
– Event monitor controls list number
– Event monitor controls status
– For each EMC associated with the list number, the following EMC Detail
Report information:
- Connection ID
- List number
- List entry key
- Event queue status
- User notification controls.
An example is:
COMMAND ===> STRDATA EMCONTROLS(01)
EVENTQS(ALL | conid,conid:conid,...)
Requests information about event monitor controls (EMCs) on the event
queue associated with a list structure connector. The conid can be a single
connection identifier, a range of connection identifiers, or a list of
noncontiguous connection identifiers. When you specify a range, separate
the first and last identifiers in the range with a colon. When you specify a
connection identifier, separate the connection identifiers with commas.
The report output is:
– STRDATA ALL STRUCTURES SUMMARY/DETAIL REPORT
– EVENT QUEUE CONTROLS SUMMARY/DETAIL REPORT
The output fields for each connection ID are:
– Connection ID
– Number of EMCs dumped
– Event queue controls status
– Event queue transition exit status

288 z/OS MVS IPCS Commands

 STRDATA subcommand

– Event queue monitoring status

– Event notification vector index
– Number of EMCs queued
– Number of state transitions
– For each EMC on the event queue:
- EMC Detail Report information as described for EMCONTROLS
An example is:
COMMAND ===> STRDATA EVENTQS(1)
USERCNTLS (ALL | conid,conid:conid,...)
Requests information by user connection identifier about the user of a
structure. The conid can be a single connection identifier, a range of
identifiers, or a list of noncontiguous identifiers. When you specify a range,
separate the first and last identifiers in the range with a colon. When you
specify a list, separate the list members with commas.
The report output is:
– STRDATA ALL STRUCTURES SUMMARY REPORT
– USER CONTROLS REPORT
The output fields for each connection identifier (ID) specified are:
– Connection ID status
– Connection name
– Connection ID
– Connection status
– User authority
– User control information
An example is:
COMMAND ===> STRDATA USERCNTLS(01)
LOCKENTRIES (ALL | lockentry,lockentry:lockentry,...)
Requests information by the entries specified for the lock table entries of a
coupling facility list structure. The lockentry can be a entry, a range of entries,
or a list of noncontiguous entries. When you specify a range, separate the
first and last entries in the range with a colon. When you specify a list,
separate the list members with commas.
The report output is:
– STRDATA ALL STRUCTURES SUMMARY REPORT
– LOCK ENTRIES REPORT
The output fields for each entry into the lock table are:
– Lock entries status
– Lock entries
– Owners connection ID
– Held By system indicator
The STRDATA LOCKENTRIES parameter is associated with:
– The LOCKENTRIES parameter of the IXLCONN macro
– The LOCKINDEX parameter of the IXLLIST macro
An example is:
COMMAND ===> STRDATA LOCKENTRIES(ALL)

Chapter 5. IPCS subcommands 289

STRDATA subcommand

ENTRYID (entryid,X'entryid',...)
Requests the display of information by list entry identifiers for a coupling
facility list structure. The entryid can be expressed in decimal or in
hexadecimal (X'nnn').
The report output is:
– STRDATA ALL STRUCTURES SUMMARY REPORT
– LIST ENTRY IDENTIFIER SUMMARY REPORT
The output fields for each entry ID specified are:
– List entry identifier
– List entry controls
– Adjunct data
– Structure serialization indicator
The STRDATA ENTRYID parameter is associated with the ENTRYID
parameter of the IXLLIST macro.
An example is:
COMMAND ===> STRDATA ENTRYID(X’000000000000000100000009’)
ENTRYNAME (entryname,entryname...)
Requests information by list entry names in a coupling facility list structure
or by data entry names in a coupling facility cache structure.
The report output is:
– STRDATA ALL STRUCTURES SUMMARY REPORT
– ENTRY NAME SUMMARY REPORT
The output fields for each entry name specified are:
– Entry name
– Directory information (for cache)/ list entry controls (for list)
– Adjunct data
– Structure serialization indicator
The STRDATA ENTRYNAME parameter is associated with:
– The ENTRYNAME parameter of the IXLLIST macro
– The NAME parameter of the IXLCACHE macro
An example is:
COMMAND ===> STRDATA ENTRYNAME(ELEMENT2)
ARB
Requests formatting of the associated request block (ARB), which contains a
list of all the valid ranges specified on the STRLIST option of the DUMP,
CHNGDUMP, or SLIP operator command. If the dump was taken by a
recovery routine, the ARB contains the data derived from the IHABLDP
macro.

Note: The actual dump parameters may have been modified to be consistent
with the structure specifications. For example, if castout classes 1 to 2000
were requested to be dumped, but only castout classes 1 to 10 were valid,
the ARB input were modified before the dump was taken.
The report output is:
– STRDATA ALL STRUCTURES SUMMARY REPORT
– ASSOCIATED REQUEST BLOCK REPORT

290 z/OS MVS IPCS Commands

 STRDATA subcommand

The output fields are:

– Total ranges requested in ARB
– Last range dumped
– Range number
– Dump object type for each range requested. For example, list number or
lock entries.
An example is:
COMMAND ===> STRDATA ARB
ENTRYPOS (ALL | entrypos,entrypos:entrypos,...)
Requests information about an entry in a particular position, or range of
positions. This parameter is valid only with COCLASS, STGCLASS, or
LISTNUM. The position of an entry is counted from the head or tail of the
queue, depending on the ORDER parameter. The entrypos can be a single
position, a range of positions, or a list of noncontiguous positions. When
you specify a range, separate the first and last positions in the range by a
colon. When you specify a list, separate the list members with commas.
The report output is:
– STRDATA ALL STRUCTURES SUMMARY REPORT
– LIST NUMBER ENTRY POSITION SUMMARY REPORT

Note: If STGCLASS is also specified, IPCS also displays the STORAGE

CLASS ENTRY POSITION SUMMARY REPORT. If STGCLASS or COCLASS
is specified, IPCS also displays the CASTOUT CLASS ENTRY POSITION
SUMMARY REPORT.
The output fields for each entry specified are:
– List number
– List number status
– Summary of the list controls
– Entry key, if requested
– Order indicator
– For each entry requested:
- Entry position
- List entry controls
- Adjunct data
- Serialization indicator
The STRDATA ENTRYPOS parameter is associated with:
– The LISTDIR parameter of the IXLLIST macro
– The COCLASS and STGCLASS parameters of the IXLCACHE macro
An example is:
COMMAND ===> STRDATA LISTNUM(ALL) ENTRYPOS(2)
ORDER (HEAD | TAIL)
Specifies the order for entries to be displayed. Specify ORDER only with
ENTRYPOS. The position number specified in ENTRYPOS depends on
whether you are counting from the head or the tail of the queue.

Chapter 5. IPCS subcommands 291

STRDATA subcommand

HEAD is the default and specifies that entries be located from at the top of a
list or the head of a queue. For a storage class, the head of a queue is the
least recently referenced entry. For a cast-out class, the head of a queue is the
least recently changed entry.
TAIL specifies that entries be located from the end of a list or the tail of a
queue. For a storage class, the tail of a queue is the most recently referenced
entry. For a cast-out class, the tail of a queue is the most recently changed
entry.
For example, if there are 35 entries on list number 2, and you want the 30th
entry from the start of the queue, specify either of the following to display
the same entry:
COMMAND ===> STRDATA LISTNUM(2) ENTRYPOS(30) ORDER(HEAD)

COMMAND ===> STRDATA LISTNUM(2) ENTRYPOS(6) ORDER(TAIL)

ENTRYKEY(entrykey,entrykey...)
Requests the display of a list entry with the specified key or the event
monitor controls (EMCs) associated with a list entry and the specified key.
This parameter can be used only for LISTNUM (when ENTRYPOS is
specified) and EMCONTROLS processing.
The report output is
– STRDATA ALL STRUCTURES SUMMARY REPORT
– LIST NUMBER ENTRYKEY ENTRY POSITION SUMMARY REPORT
The output fields are:
– List number
– List number status
– Summary of the list controls
– Entry key
– Order indicator
– For each entry requested:
- Entry position
- List entry controls
- Adjunct data
- Serialization indicator
The STRDATA ENTRYKEY parameter is associated with:
– The LISTCNTLTYPE=ENTRY and REFOPTION=KEY parameters of the
IXLCONN macro
– The ENTRYKEY parameter of the IXLLIST macro
For example, the entry positions are in an order that is relative to the entry
key. Table 17 shows queue 1, which is a list with 5 entries:
Table 17. Example of queue and entry postions
LIST 2
Head of Queue
entry 1 key 1
entry 2 key 2
entry 3 key 2
entry 4 key 2
entry 5 key 3

292 z/OS MVS IPCS Commands

 STRDATA subcommand

Table 17. Example of queue and entry postions (continued)

LIST 2
Tail of Queue

To display the second and third entries for key 2 from the head of list 2,
enter the following command:
COMMAND ===> STRDATA LISTNUM(2) ENTRYPOS(2,3) ENTRYKEY(02) ORDER(HEAD)

Table 18 shows how entries with the same key are considered a separate
queue, queue 2, so you get back entry 3 as entry position 2 and entry 4 as
entry position 3.
Table 18. Example of entries considered as a separate queue
LIST 2
entry 1 key 1
Head of Queue
entry 2 key 2 position 1
entry 3 key 2 position 2
entry 4 key 2 position 3
Tail of Queue
entry 5 key 3

Another example is:

COMMAND ===> STRDATA ENTRYKEY(02) LISTNUM(ALL) ENTRYPOS(ALL)

SUMMARY subcommand — summarize control block fields

Use the SUMMARY subcommand to display or print dump data associated with
one or more specified address spaces. SUMMARY produces different diagnostic
reports depending on the report type parameter, FORMAT, KEYFIELD,
JOBSUMMARY, and TCBSUMMARY, and the address space selection parameters,
ALL, CURRENT, ERROR, TCBERROR, ASIDLIST, and JOBLIST. Specify different
parameters to selectively display the information you want to see.

Note: Installation exit routines can be invoked at the system, address space, and
task level for each of the parameters in the SUMMARY subcommand.
v Related subcommands
– LISTSYM
– RUNCHAIN
– SCAN
– SELECT
– STATUS
v Syntax

Chapter 5. IPCS subcommands 293

SUMMARY subcommand

{ SUMMARY }
{ SUMM }

-------- Report Type Parameters ----------------------------

[ KEYFIELD [REGISTERS | NOREGISTERS] ]
[ FORMAT ] [ DIALOG ]
[ EXCLUDE(GLOBAL | JPQ | LOADLIST) ]
[ TCBADDR(address-list) ]
[ TCBSUMMARY ]
[ JOBSUMMARY ]

-------- Address Space Selection Parameters ----------------

[ ALL ]
[ CURRENT ]
[ ERROR ]
[ TCBERROR | ANOMALY ]
[ ASIDLIST(asidlist) ]
[ JOBLIST(joblist) | JOBNAME(joblist) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report Type Parameters

Use these parameters to select the type of report. If you omit a report type
parameter, the default is KEYFIELD.
KEYFIELD
Presents the information in the ASCB, TCB, and RB key fields associated
with the specified address space(s). Information included pertains to the
fields listed in Table 19.
Table 19. ASCB, TCB, RB key fields associated with specified address spaces

ASCB fields:
AFFN FLG2
ASID FWDP
ASSB LOCK
ASXB SRBS
CSCB TSB
DSP1
TCB fields:
BITS NDSP
CMP PKF
DAR RTWA
DSP STAB
FBYT1 STCB

294 z/OS MVS IPCS Commands

 SUMMARY subcommand

Table 19. ASCB, TCB, RB key fields associated with specified address
spaces (continued)

JSCB TSFLG
LMP
RB fields:
WLIC OPSW
LINK
CDE fields:
NAME
ENTPT

REGISTERS or NOREGISTERS
Specifies or suppresses display of the general purpose registers for each
TCB/RB. Specify this parameter only when you specify KEYFIELD or
default to KEYFIELD. If you specify FORMAT, JOBSUMMARY, or
TCBSUMMARY and either REGISTERS or NOREGISTERS, IPCS processing
ignores REGISTERS or NOREGISTERS.
REGISTERS specifies that registers are to be shown. The abbreviation REGS
is accepted for this parameter. NOREGISTERS suppresses the registers. The
abbreviation NOREGS is accepted for this parameter. If you omit both
REGISTERS and NOREGISTERS, the default is NOREGISTERS.
FORMAT
Specifies a report containing the major control blocks associated with the
specified address space or spaces. The blocks are, for example:
– ASCB
– ASSB
– ASXB
– Authorization table
– CDE
– DEB
– EED
– ENQ/DEQ suspend queue
– Extent list (XLIST)
– General CMS suspend queue
– Global service manager queue
– Job pack queue
– Linkage stack
– List of control blocks associated with open data sets
– Load list
– Local lock suspend queue
– Local service manager queue
– Local suspended SRB queue
– Processor related work unit queues
– RB
– RSM suspended SRB deferred requests list
– RSM suspended SRB I/O wait list

Chapter 5. IPCS subcommands 295

SUMMARY subcommand

– RSM suspended SRB cross memory deferred requests list

– RSM suspended SRB cross memory I/O wait list
– RTCT (only if CURRENT is specified or defaulted)
– SMF CMS suspend queue
– STCB
– STKE
– System work unit queue
– TCB and TCBEXT2
– TIOT
– XSB

Note: For ASCBs, TCBs, CDEs, the extent list, and the load list, the bits in
significant flag byte fields are explained (decoded).
After these items are formatted, IPCS invokes additional
installation-supplied or other IBM-supplied exits to format control blocks.
If access registers are formatted, IPCS can identify the data space associated
with the access register if the data space is accessible in the dumped
environment; storage from the data space does not need to be dumped to
enable the identification.
DIALOG
Directs the SUMMARY subcommand to present a data entry panel rather
than accepting options in subcommand format.
EXCLUDE(GLOBAL | JPQ | LOADLIST)
Directs SUMMARY FORMAT to omit portions of the report that it normally
produces.
– EXCLUDE(GLOBAL) causes global SRB formatting to be omitted.
– EXCLUDE(JPQ) causes job pack queue formatting to be omitted.
– EXCLUDE(LOADLIST) cause load list formatting to be omitted.
TCBADDR(address-list)
Directs SUMMARY FORMAT to limit its formatting related to TCBs to those
whose addresses are listed. You can enter TCB addresses using decimal,
hexadecimal (X'xxx'), or binary (B'bbb') format. ADDRTCB is an alias of the
TCBADDR keyword.
TCBSUMMARY
Specifies a report containing a summary of the task control blocks (TCBs) for
each address space processed. Each TCB summary contains:
– Job name
– ASCB name and address
– TCB name and address
– CMP field
– PKF field
– TSFLG field
If the TCBRTWA field is nonzero, the following fields are also displayed for
each TCB:
– DAR field
– RTWA field
– FBYT1 field

296 z/OS MVS IPCS Commands

 SUMMARY subcommand

JOBSUMMARY
Specifies a report containing a summary of the status of address spaces for a
job. The report contains:
– Active CPU list
– For each CPU, one of the following values:
- NORMAL MODE
- SERVICE REQUEST MODE, which means SRB (Service Request Block)
MODE
– Scheduled services
– For each address space specified:
- Jobname
- ASCB location
- ASID
- Status of the address space
- Local service manager queue
- Local service priority queue
- TCB locations, completion codes, and the active indicator
- A problem list of TCBs
- Local lock suspend queue
- Local suspended SRB queue
v Address Space Selection Parameters
Use these parameters to obtain data from particular address spaces, which you
specify by their address space identifiers (ASIDs). If you omit these parameters,
the default is CURRENT. For more information, see the select ASID service in
z/OS MVS IPCS Customization.
You can specify several address space selection parameters. An address space
might meet more than one selection criterion. The selection criterion (or criteria)
that is met for each address space appears in the output. No address space is
processed more than once.
ALL
Specifies processing of all address spaces in the dump.
CURRENT
Specifies the processing of each address space that was active when the
dump was generated.
ERROR
Specifies processing of control blocks for any address space with an MVS
error indicator or containing a task with an error indicator.
TCBERROR or ANOMALY
Specifies processing of control blocks for any address space containing a task
with an error indicator. Blocks for address spaces with an error indicator are
not processed.
ASIDLIST(asidlist)
Specifies a list of ASIDs for address spaces to be processed. The asidlist can
be a single ASID, a range of ASIDs, or a list of noncontiguous ASIDs. When
you specify a range, separate the first and last ASIDs in the range with a
colon. When you specify a list, separate the list members with commas.
The ASID can be 1 through 65535. An ASID can be expressed in the notation
X'nnn', F‘nnn’, or B'nnn'. An unqualified number is assumed to be fixed.

Chapter 5. IPCS subcommands 297

SUMMARY subcommand

This subcommand does not process summary dump records (ASID X‘FFFA’).
JOBLIST(joblist) or JOBNAME(joblist)
Specifies a list of job names whose associated address spaces are to be
processed. Use commas to separate the job names in the list; do not enclose
job names in apostrophes; and do not specify a range of job names.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the SUMMARY subcommand.
v Example 1: Produce a KEYFIELD report.
– Action: COMMAND ===> summary keyfield current
– Result: IPCS produces the output shown in Figure 32 on page 299.

298 z/OS MVS IPCS Commands

 SUMMARY subcommand

▌1▐ * * * * K E Y F I E L D S * * * *
JOBNAME TC
▌2▐ SELECTED BY: CURRENT ERROR

ASCB: 00F6AD00
FWDP..... 00F6E800 ASID..... 0021 CSCB..... 02DAE530
TSB...... 00000000 AFFN..... FFFF ASXB..... 007FE038 DSP1..... 00
FLG2..... 00 SRBS..... 0000 LOCK..... 00000000
ASSB..... 01A72280

TCB: 007FE240
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 007FF6E0 NDSP..... 00000000
JSCB..... 007FFDFC BITS..... 00000000 DAR...... 00
RTWA..... 00000000 FBYT1.... 00
Task non-dispatchability flags from TCBFLGS4:
Top RB is in a wait

PRB: 007FFF98
WLIC..... 00020001 OPSW..... 070C1000 810234C0
LINK..... 017FE240
EP....... IEAVAR00 ENTPT.... 82B6CED0

TCB: 007FF3B8
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 007FF6B0 NDSP..... 00000000
JSCB..... 007FFDFC BITS..... 00000000 DAR...... 00
RTWA..... 00000000 FBYT1.... 00
Task non-dispatchability flags from TCBFLGS4:
Top RB is in a wait
PRB: 007FF0A0
WLIC..... 00020078 OPSW..... 070C2000 823E55D0
LINK..... 017FF3B8
EP....... IEAVTSDT MAJOR.... IGC0005A ENTPT.... 823E52D8

TCB: 007FF128
CMP...... 00000000 PKF...... 80 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 007FF620 NDSP..... 00000000
JSCB..... 007FCC14 BITS..... 00000000 DAR...... 00
RTWA..... 00000000 FBYT1.... 00
Task non-dispatchability flags from TCBFLGS4:
Top RB is in a wait

PRB: 007FCC30
WLIC..... 00020001 OPSW..... 070C1000 80E11948
LINK..... 017FCE30
EP....... IEFSD060 ENTPT.... 80E08880

PRB: 007FCE30
WLIC..... 00020006 OPSW..... 070C1000 80E1A706
LINK..... 007FF128
EP....... IEESB605 ENTPT.... 00E1A000

Figure 32. Sample output from SUMMARY KEYFIELD CURRENT command

▌1▐ Indicates the report type.

▌2▐ Indicates the selection criteria that were met.
v Example 2: Produce a FORMAT report.
– Action: COMMAND ===> summary format current
– Result: IPCS produces the output shown in Figure 33 on page 300.

Chapter 5. IPCS subcommands 299

SUMMARY subcommand

▌1▐ * * * * F O R M A T * * * *

▌2▐ GLOBAL SERVICE MANAGER QUEUE

QUEUE IS EMPTY

LOCAL SERVICE MANAGER QUEUE

QUEUE IS EMPTY

SYSTEM WORK UNIT QUEUE

WEB QUEUE IS EMPTY

CMS SMF LOCK SUSPEND WEB QUEUE

WEB QUEUE IS EMPTY

CMS ENQ/DEQ LOCK SUSPEND WEB QUEUE

WEB QUEUE IS EMPTY

GENERAL CMS LOCK SUSPEND WEB QUEUE

WEB QUEUE IS EMPTY

CPU = 01
PROCESSOR RELATED WORK UNIT QUEUE
WEB QUEUE IS EMPTY

RSM processing on a non-stand-alone dump may generate inconsistent

data and false validity check failures.
Data space information may be incomplete for RSM. Storage not in
dump.

RSM SUSPENDED SRB DEFERRED REQUESTS LIST

SSRB LIST IS EMPTY

RSM SUSPENDED SRB I/O WAIT LIST

SSRB LIST IS EMPTY

RSM SUSPENDED SRB CROSS MEMORY DEFERRED REQUEST LIST

SSRB LIST IS EMPTY

RSM SUSPENDED SRB CROSS MEMORY I/O WAIT LIST

SSRB LIST IS EMPTY
ASXB: 007FE038
+0000 ASXB..... ASXB FTCB..... 007FE240 LTCB..... 007FC378
+000C TCBS..... 0004 R00E..... 0000 MPST..... 00000000
+0014 LWA...... 00000000 VFVT..... 00000000 SAF...... 00000000
+0020 IHSA..... 007FE598 FLSA..... FE0000D8 00F77500 00FD1770
+0030 812ED762 00000040 012EE761 00F77500 812ED896
+0044 00000000 00FFA848 000000D8 00F77508 00F77400
+0058 7FFE44F0 81161DC2 7FFE493C 00000C60 812B0132
+006C OMCB..... 00000000 SPSA..... 007FEA68 RSMD..... 00000000
+0078 RCTD..... 007FE480 DECB..... 807FF0A0 OUSB..... 7FFFD1C0
+0084 CRWK..... 00000000 PRG...... 00000000 00000000 00000000
+0094 00000000 PSWD..... 00000000 00000000
+00A0 SIRB..... 007FE3D8 ETSK..... 007FE240 FIQE..... 00000000
+00AC LIQE..... 00000000 FRQE..... 00000000 LRQE..... 00000000
+00B8 FSRB..... 00000000 LSRB..... 00000000 USER..... TC
+00C7 SFLG..... 00 SENV..... 007FCF58 R0CC..... 00000000
+00D0 NSSA..... 7FFFCDE0 NSCT..... 0000000D CRB1..... 00
+00D9 CRB2..... 00 CRB3..... 00 CRB4..... 00
+00DC PT0E..... 00000000 R0E0..... 00000000 JSVT..... 00000000
+00E8 DIVW..... 00000000 R0EC..... 00000000
.
.
.

Figure 33. Sample output from SUMMARY FORMAT CURRENT command

▌1▐ Indicates the report type.

▌2▐ Shows the status of the various queues and SSRB lists.
▌3▐ Indicates the selection criteria that were met.

300 z/OS MVS IPCS Commands

 SUMMARY subcommand

v Example 3: Produce a TCBSUMMARY report.

– Action: COMMAND ===> summary tcbsummary current
– Result: IPCS produces the output shown in Figure 34.

▌1▐ * * * * T C B S U M M A R Y * * * *

▌2▐ JOB TC ASCB021 AT 00F6AD00

▌3▐ SELECTED BY: CURRENT ERROR

▌4▐ TCB: 007FE240

CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 007FF6E0 NDSP..... 00000000
JSCB..... 007FFDFC BITS..... 00000000 FBYT1.... 00

TCB: 007FF3B8
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 007FF6B0 NDSP..... 00000000
JSCB..... 007FFDFC BITS..... 00000000 FBYT1.... 00

TCB: 007FF128
CMP...... 00000000 PKF...... 80 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 007FF620 NDSP..... 00000000
JSCB..... 007FCC14 BITS..... 00000000 FBYT1.... 00

TCB: 007FC378
CMP...... 88522000 PKF...... 80 FLGS..... 84000000 00
LMP...... FF DSP...... FF TSFLG.... 20
STAB..... 007FF5F0 NDSP..... 00000000 JSCB..... 007FCA0C
BITS..... 00000000 DAR...... 00 RTWA..... 7F6FE090 ABCUR.... 00
FBYT1.... 88

Figure 34. Example output from SUMMARY TCBSUMMARY CURRENT

▌1▐ Indicates the report type.

▌2▐ Provides the name of the job, the address space, and its address.
▌3▐ Indicates the selection criteria that were meet.
▌4▐ Provides the address of the first TCB in the chain.
v Example 4
Produce a JOBSUMMARY report.
– Action: COMMAND ===> summary jobsummary current
– Result: IPCS produces the output shown in Figure 35 on page 302.

Chapter 5. IPCS subcommands 301

SUMMARY subcommand

▌1▐ * * * * S Y S T E M S U M M A R Y * *
*** ACTIVE CPU LIST ***
CPU 0001 - SERVICE REQUEST MODE

*** SCHEDULED SERVICES ***

GLOBAL SERVICE MANAGER QUEUE

QUEUE IS EMPTY

LOCAL SERVICE MANAGER QUEUE

QUEUE IS EMPTY

SYSTEM WORK UNIT QUEUE

WEB QUEUE IS EMPTY

CMS SMF LOCK SUSPEND WEB QUEUE

WEB QUEUE IS EMPTY

CMS ENQ/DEQ LOCK SUSPEND WEB QUEUE

WEB QUEUE IS EMPTY

GENERAL CMS LOCK SUSPEND WEB QUEUE

WEB QUEUE IS EMPTY

CPU = 01
PROCESSOR RELATED WORK UNIT QUEUE
WEB QUEUE IS EMPTY

RSM processing on a non-stand-alone dump may generate inconsistent

data and false validity check failures.
Data space information may be incomplete for RSM. Storage not in
dump.

RSM SUSPENDED SRB DEFERRED REQUESTS LIST

SSRB LIST IS EMPTY

RSM SUSPENDED SRB I/O WAIT LIST

SSRB LIST IS EMPTY

RSM SUSPENDED SRB CROSS MEMORY DEFERRED REQUEST LIST

SSRB LIST IS EMPTY

RSM SUSPENDED SRB CROSS MEMORY I/O WAIT LIST

SSRB LIST IS EMPTY

Figure 35. Example output from SUMMARY JOBSUMMARY CURRENT

▌2▐ *** JOB SUMMARY ***

---------------------------------------------------------------------

▌3▐ SELECTED BY: CURRENT

JOBNAME TC ASCB 00F6AD00 NEXT 00F6E800 PREV 00F63D00 ASID 0021

TCB 007FE240 NEXT 007FF3B8 PREV 00000000 COMP 00000000

TCB 007FF3B8 NEXT 007FF128 PREV 007FE240 COMP 00000000
TCB 007FF128 NEXT 007FC378 PREV 007FF3B8 COMP 00000000
TCB 007FC378 NEXT 00000000 PREV 007FF128 COMP 88522000
----------------------------------------------------------------------
*** PROBLEM LIST ***

JOB TC ASID 0021 TCB 007FC378 ABEND CODE- 88522000 DAR 00

JOB TC ASID 0021 TCB 007FC378 SET TEMPORARY NON-DISPATCHABLE
FLGS4 00 FLGS5 00 SCNDY 00000000 DAR 00 STPCT 00
▌4▐NO MACHINE CHECKS IN PROCESS
NO ABENDS DETECTED FOR ASCBS
NO NON-DISPATCHABLE ASCBS DETECTED

302 z/OS MVS IPCS Commands

 SUMMARY subcommand

▌1▐ Provides a summary of the system.

▌2▐ Indicates the report type.
▌3▐ Indicates the selection criteria that were meet.
▌4▐ Provides a problem list.

SYMDEF subcommand — display an entry in the system symbol table

Use the SYMDEF subcommand to display an entry in the system symbol table,
which contains static system symbols. You can use IPCS-supplied traps with the
SYMDEF command.

Note:
1. SYMDEF displays the static system symbols in the system symbol table, which
are specified (or the defaults accepted) in the IEASYMxx parmlib member.
System symbols are different from the IPCS symbols described in Appendix A,
“IPCS symbols,” on page 445.
2. The output that SYMDEF generates contains information for diagnostic use.
The IBM Support Center might ask you to provide this information for use in
problem determination.
v Related subcommands
None.
v Syntax

SYMDEF [ NAME(symbol) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
NAME(symbol)
Displays the symbol table entry for the specified system symbol. When
specifying symbol, do not include the ampersand (&) or the period (.) that
are normally part of symbol notation. If you do not specify this parameter,
the system displays the entire symbol table.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the SYMDEF subcommand.

SYSTRACE subcommand — format system trace entries

Use the SYSTRACE subcommand to format system trace entries for all address
spaces.
v Syntax

Chapter 5. IPCS subcommands 303

 SYSTRACE subcommand

{ SYSTRACE [ TIME(HEX | GMT | LOCAL) ]

-------- Report Type Parameters ----------------------------

[ PERFDATA([SHOWTRC] [DOWHERE] [SIGCPU(sss.dddddd)]) ]

-------- Data Selection Parameters -------------------------

[ EXCLUDE(BR) ]
[ EXCLUDE(MODE) ]
| [ EXCLUDE(BEFOREALL) ]
| [ EXCLUDE(AFTERALL) ]
[ SORTCPU[(mm/dd/yy,hh:mm:ss:dddddd,N) | (mm/dd/yy,hh:mm:ss:dddddd)] ]
[ START(mm/dd/yy,hh.mm.ss.dddddd) ]
[ STOP(mm/dd/yy,hh.mm.ss.dddddd) ]
[ CPU(cpu-address-range-list) ]
[ CPUMASK(cpu-hexadecimal-mask) ]
[ CPUTYPE(ZAAP|ZIIP|STANDARD) ]
[ STATUS ]
[ TCB(TCB-list) ]
[ TTCH(TTCH-address | LIST) ]
[ WEB(WEB-list) ]

-------- Address Space Selection Parameters ----------------

[ ALL ]
[ CURRENT ]
[ ERROR ]
[ TCBERROR ]
[ ASIDLIST(asidlist) ]
[ JOBLIST(joblist) | JOBNAME(joblist) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
TIME(HEX | GMT | LOCAL)
Specifies the type of time stamp for the system trace entries, as follows:
– HEX specifies a hexadecimal time stamp.
– GMT specifies a time stamp in Greenwich mean time.
– LOCAL specifies a time stamp in local time.
v Report Type Parameters
Use these parameters to select the type of report.
PERFDATA ([SHOWTRC] [ DOWHERE] [ SIGCPU(time)])
Requests summary information for the performance data report. The intent
of the PERFDATA parameter is to help identify which trace entries are using
large amounts of time as derived from the output of SYSTRACE ALL
TIME(LOCAL) where it is also determined that trace data is available from
all processors. As SYSTRACE entries are the sole source of the PERFDATA
calculations, output is not as precise as other forms of time use reporting

304 z/OS MVS IPCS Commands

 SYSTRACE subcommand

(such as RMF™ reports). PERFDATA output is reported against the job

running in the address space at the time of the dump.
SHOWTRC
Requests that a system trace table be displayed in the output. If you
do not specify this parameter, the default is to exclude the system
trace table.
DOWHERE
Requests WHERE commands to be issued for PSWs within CLKC
and SRB analysis sections of PERFDATA option output, in order to
display the area in a dump in which these addresses reside. This
information may include the name of the load module, the name of
a control block or the name of an area of storage containing the PSW
address along with an offset. It is displayed in an extra field on the
same row of a PERFDATA table as the PSW address.
SIGCPU(sss.dddddd)
Requests that CLKC analysis and WHERE analysis for SRB events
are to be bypassed for events with CPU usage less than the specified
time (in seconds). If you do not specify this parameter, the default is
SIGCPU(0.1).
sss Represents seconds. You can specify one to three decimal
digits.
dddddd
Represents decimal fractions of seconds. You can specify one
to six decimal digits.

If a hexadecimal time stamp type is selected when specifying the PERFDATA

parameter, the time values in the PERFDATA report are generated in GMT
format.
v Data Selection Parameters
Use these parameters to limit the scope of the data in the report. If you omit
these parameters, the default is to include all trace entries.
EXCLUDE(BR)
Suppresses formatting of trace table entries for branch tracing if any were
present in the dump. When you do not specify EXCLUDE(BR), the
formatted trace table shows all the types of trace table entries.
EXCLUDE(MODE)
Suppresses formatting of trace table entries for mode tracing if any were
present in the dump. When you do not specify EXCLUDE(MODE), the
formatted trace table shows all the types of trace table entries.

Note: Specifying EXCLUDE(BR,MODE) suppresses formatting of trace table

entries for both branch and mode tracing if any were present in the dump.
| EXCLUDE(BEFOREALL)
| Suppresses formatting of trace entries before the message:
| ******** Trace data is not available for all processors before this time.
| EXCLUDE(AFTERALL)
| Suppresses formatting of trace entries after the message:
| ******** Trace data is not available for all processors after this time.
SORTCPU[(mm/dd/yy,hh:mm:ss:dddddd,N) | (mm/dd/yy,hh:mm:ss:dddddd)]
When the SORTCPU option is specified, IPCS displays trace entries for each

Chapter 5. IPCS subcommands 305

SYSTRACE subcommand

CPU separately in ascending order by CPU address. N indicates the number

of the trace entries before and after a specified time, which are displayed for
each CPU.
If (mm/dd/yy,hh:mm:ss:dddddd,N) is not specified, or if N is zero (0), or if
the number of system trace entries are less than what were specified in N,
all entries are shown. If you omit N, the default value is 10. Specify the date
and time in the mm/dd/yy,hh:mm:ss:dddddd format.
mm Represents month; requires two decimal digit format.
dd Represents day; requires two decimal digit format.
yy Represents year; requires two decimal digit format.
hh Represents hour; requires two decimal digit format.
mm Represents minutes; requires two decimal digit format.
ss Represents seconds; requires two decimal digit format.
dddddd
Represents decimal fractions of seconds; you can specify one to six
decimal digits.
These rules apply to the date and time specifications:
– You need to specify both a time and a date on the SORTCPU parameter,
but you do not have to specify the time down to the milliseconds.
– If you specify TIME(HEX) or TIME(GMT) in the SYSTRACE
subcommand, the specified time is in GMT format. If you specify
TIME(LOCAL), the time is in the local time zone. When TIME is not
specified, a default of TIME(HEX) leads to time in GMT format.
– To allow for copying and pasting of time from the systrace output, use
colons or periods to delimit the time field.
Examples:
1. Show all data in CPU order:
SYSTRACE ALL SORTCPU
2. Show data in CPU order, showing a default of 10 entries around 11 am
GMT:
SYSTRACE ALL TIME(GMT) SORTCPU(12/30/09,11)
3. Show data in CPU order, showing 5 entries around 11:45:21:939233 am
local:
SYSTRACE ALL TIME(LOCAL) SORTCPU(12/30/09, 11:45:21.939233,5)

Note: When SORTCPU is specified, a default of ALL (address spaces) is

assumed and any other specification for filtering by ASID is incompatible,
such as the CURRENT, ERROR, TCBERROR, ASIDLIST, JOBLIST and
JOBNAME keywords. The SORTCPU parameter is compatible with the
following existing SYSTRACE parameters: TCB, WEB, CPU, TIME,
EXCLUDE, TTCH, START, STOP and ALL.
START(mm/dd/yy,hh.mm.ss.dddddd)
Specifies the beginning date and time for the trace entries to be formatted.
When you do not specify START, IPCS starts at the beginning of the trace
entries. Specify the date and time in the mm/dd/yy.hh.mm.ss.dddddd
format.
mm represents months

306 z/OS MVS IPCS Commands

 SYSTRACE subcommand

dd represents days
yy represents years
hh represents hours
mm represents minutes
ss represents seconds
dddddd
represents decimal fractions of seconds
These rules apply to the date and time specifications:
– You must specify a date and time on the START parameter.
– The month and day can be specified in either single or double digits.
– Separate the date from the time with a comma.
– The time can be GMT, by default or specified in a GMT parameter, or
local, if specified in a LOCAL parameter.
– Hours, minutes, and seconds can be specified in single or double digits.
– The time can be truncated anywhere on the right.
– The time can be left off completely, in which case, it will default to
00:00:00.000000 (midnight).
– To allow for copying and pasting of time from the systrace output, use
colons or periods to delimit the time field.
Table 20 shows examples of valid date and time formats.
Table 20. Examples of valid date and time formats
Valid date formats Valid time formats
m/dd/yy hh.mm.ss.dddddd
mm/d/yy hh.mm.ss.dd
m/d/yy hh.mm.ss
mm/dd/yy h.m.s
hh.mm
hh

Use START and STOP to reduce the number of trace entries formatted.
STOP(mm/dd/yy,hh.mm.ss.dddddd)
Specifies the ending date and time for the trace entries to be formatted.
When you do not specify STOP, IPCS stops formatting after the last trace
entry. For guidelines on how to specify the date and time, see the START
parameter.
CPU(cpu-address-range-list)
Limits formatting to trace entries for the central processors whose addresses
are specified by cpu-address-range-list. Use a Store CPU Address (STAP)
instruction to obtain the processor address.
When specifying the processor address range list, you can use a single
address, a range of addresses, or a combination of individual addresses and
address ranges. The eligible processor address is 1 through 255. You can
specify the addresses in decimal (nn), hexadecimal (X'h'), or binary (B'bbbb')
format. And you can use mixed format when multiple addresses are
involved. The following examples provide more details:
– CPU(5) or CPU(X'3d') designates a single processor. Only the trace entries
captured by the processor whose address is designated are selected.

Chapter 5. IPCS subcommands 307

SYSTRACE subcommand

– CPU(5:7), CPU(X'3d':X'3e'), or CPU(15:X'10') designate a range of

processor addresses. The first processor address in a range must be less
than or equal to the second. In the case of CPU(15:X'10'), both the decimal
and hexadecimal format are used to specify the range.
– CPU(5 X'3d':X'3e' 15:X'10') designates a list. In this case the individual
processor addresses and the address ranges are mixed.
– If you do not specify a processor on the option, the default is to format
trace entries from all central processors.
CPUMASK(cpu-hexadecimal-mask)
Limits formatting to only the trace entries produced on the processors
specified in the CPU (cpu-hexadecimal-mask). Specify the processors using a
string of hexadecimal characters. Each hexadecimal character identifies four
processors, leftmost bit designates lower processor address starting from
zero. The processor maximum in z/OS defines a length of this hexadecimal
string. The current processor maximum is 256. Therefore, the maximum
length of the hexadecimal mask string is 64. See example 4. You can combine
CPUMASK, CPU, and CPUTYPE as a union of sets. If all of the parameters
are omitted, all processors are included as the default.
Examples:
1. To show all data for processors from 0 to 11:
SYSTRACE ALL CPUMASK(FFF)
2. To show all data for processors from 0 to 3 and from 8 to 11:
SYSTRACE ALL CPUMASK(F0F0)
3. To show all data for processor 0 and for processors from 5 to 10:
SYSTRACE ALL CPUMASK(80) CPU(5:10)
4. To show data for processors from 0 to 127:
SYSTRACE CPUMASK(FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF)
5. To show all data for processors 2, 3, 5, 8, 9, 10, 11:
SYSTRACE ALL CPUMASK(34F)
CPUTYPE(ZAAP|ZIIP|STANDARD)
Limits the entries to specific processor types. CPUTYPE(ZAAP) selects all
IBM zEnterprise® Application Assist Processor (zAAP) in the configuration.
CPUTYPE(ZIIP) selects all IBM z™ Integrated Information Processor (zIIP) in
the configuration. CPUTYPE(STANDARD) selects all standard processors.
You can use the following abbreviations:
– ZA for ZAAP
– ZI for ZIIP
– CP or S for STANDARD.
To view a combination of CPU types, you can combine, in any order, the
ZAAP, ZIIP, and STANDARD keywords. Use a space or comma as the
delimiter. You can combine CPUTYPE, CPU, and CPUMASK as a union of
sets. If all of the parameters are omitted, all processors are included as the
default.
Examples:
1. To show all data for standard processors:
SYSTRACE ALL CPUTYPE(STANDARD)
2. To show all data for ZAAP and ZIIP processors:
SYSTRACE ALL CPUTYPE(ZAAP ZIIP)
3. To show all data for standard and ZAAP processors:

308 z/OS MVS IPCS Commands

 SYSTRACE subcommand

SYSTRACE ALL CPUTYPE(S ZAAP)

4. To show all data for ZIIP processors and for processors from 5 to 10:
SYSTRACE ALL CPUTYPE(ZI) CPU(5:10)
5. To show all data for ZAAP and ZIIP processors, for processor 0, 2, 5, 7,
and for processor from 8 to 11:
SYSTRACE ALL CPUTYPE(ZA ZIIP) CPU(0,2,5,7) CPUMASK(00F)
STATUS
Displays a table of processor-related information, as seen at the time of the
dump. This information includes: CPU number, CPU type, start and end
time in the system trace. When running in HiperDispatch mode, a
processor's parked status and processor share are also included in the report.
The STATUS subcommand can only be specified with the TIME and TTCH
parameters. If STATUS is combined with other options, the SYSTRACE
command will fail and the following message will appear: The STATUS
option is not compatible with any SYSTRACE options except TIME and
TTCH. Time information will be displayed in hexadecimal, local, or GMT
format, depending on the value specified for the TIME parameter. Also, the
TTCH parameter can be used to select the trace table to be summarized.
For example, SYSTRACE STATUS can produce the output shown in
Figure 36.

TRACE SERVICES ARE AVAILABLE.

TRACE IS ACTIVE.
ST=(ON,0001M,00002M) AS=ON BR=OFF EX=ON MO=OFF ▌1▐

Currently active snapshots: 00000001

SNAPTRC high water mark: 00000001
SNAPTRC high water mark TOD: CB5E3EF009306903

THE EARLIEST TIMESTAMP IN SYSTRACE IS FROM CPU xxx: MM/DD/YYYY HH:MM:SS.NNNNNN

THE LATEST TIMESTAMP IN SYSTRACE IS FROM CPU xxx: MM/DD/YYYY HH:MM:SS.NNNNNN
TRACE DATA REPORTING FROM ALL CPUs STARTS AT MM/DD/YYYY HH:MM:SS.NNNNNN (CPU xxx) ▌2▐
TRACE DATA REPORTING FROM ALL CPUs ENDS AT MM/DD/YYYY HH:MM:SS.NNNNNN (CPU xxx)

-----+------+------+------+-----------------------------+--------------------------------
CPUN | TYPE | POL | PARK | SYSTRACE FIRST LOCAL TIME | SYSTRACE LAST LOCAL TIME ▌3▐
-----+------+------+------+-----------------------------+--------------------------------
00 | CP | HIGH | NO | 07/28/2008 14:56:27.411146 | 07/28/2008 14:56:40.442719
01 | CP | MED | NO | 07/28/2008 14:56:35.735473 | 07/28/2008 14:56:40.442707
02 | CP | LOW | NO | 07/28/2008 14:56:39.588797 | 07/28/2008 14:56:45.360940
03 | CP | LOW | YES | 07/28/2008 08:48:19.070479 | 07/28/2008 14:56:45.362579

Figure 36. Example output from SYSTRACE STATUS

▌1▐ Provides status about tracing on the system; for example, Figure 36
shows the following information:
– ST=(ON,0001M,00002M) shows that System Trace is ON, the
system trace size for each active processor is 1 megabyte, and the
combined size of system trace tables on all active processors is 2
Megabytes.
– AS=ON indicates that implicit address space tracing is turned on.
– BR=OFF indicates that branch tracing is off.
– EX=ON indicates that explicit tracing is turned on.
– MO=OFF indicates that Mode tracing is off (traces entering and
leaving 64-bit mode).

Chapter 5. IPCS subcommands 309

SYSTRACE subcommand

▌2▐ Displays information about the trace period; the format of the time
depends on the value set by the TIME parameter (LOCAL, GMT, or
HEX). This information will not be displayed if system trace
information is not available.
If there is no time period when status information is reported for all
processors, this section will contain the following messages.

THE LAST ENTRY FROM CPU xx (MM/DD/YYYY HH:MM:SS.NNNNNN)IS BEFORE THE FIRST ENTRY
FROM CPU xx (MM/DD/YYYY HH:MM:SS.NNNNNN) SO TRACE DATA REPORTING FROM ALL CPUs
IS NOT AVAILABLE.

▌3▐ Displays information about the processor, as shown in Table 21.

Table 21. Summary of processor status information
Field Contents Possible Values
CPUN Physical processor number 0 - 128
TYPE Processor type: STANDARD, ZIIP or ZAAP CP, ZI, ZA
POL Amount of physical processor share for this HIGH, MED, LOW
processor: Vertical High, Vertical Medium or
Vertical Low. If the system is not in
HIPERDISPATCH mode, this column is omitted.
PARK Indicates if this processor was parked at the time NO, YES
of the dump. If the system is not in
HIPERDISPATCH mode, this column is omitted.
SYSTRACE FIRST The first and last time this processor was seen in Date and time, such
LOCAL TIME SYSTRACE. This information is displayed in as: 07/28/2008
and SYSTRACE HEX, LOCAL or GMT format, depending on the 14:56:40.442719 or
LAST LOCAL value of the TIME option. The column header C646942BCCCF4D66
TIME changes to match the format of the displayed
time. The default is HEX for the IPCS
SYSTRACE command.

When this information is displayed as part of the

output of the IPCS STATUS command, the time
is always displayed as LOCAL.

TCB(TCB-list)
Specifies the formatting of trace entries for the listed TCB address.
TTCH(TTCH-address | LIST)
Specifies the formatting of the trace table snapshot designated by the
specified TTCH address. The TTCH address must be designated by a
positive integer. See “Positive integers” on page 10 for a description of the
notation allowed for a positive integer. If LIST is specified, a list of available
TTCHs is produced and no trace entries are formatted. Within a standalone
dump, there may be older trace table snapshots containing information that
may be related to the problem for which the dump was taken.
For example, SYSTRACE TTCH(LIST) produces the list of trace table
snapshots shown in Figure 37 on page 311.

310 z/OS MVS IPCS Commands

 SYSTRACE subcommand

TTCH ASID TCB TIME

7F77D000 0022 006F4B90 4/23/1966 16:48:55.683827
*7F786000 0021 006F4A98 4/23/1966 16:48:31.718191
7F78F000 0020 006F4B90 4/23/1966 16:48:31.171256

Figure 37. Example of trace table snapshots

TTCH Shows the address of the trace table snapshot in the dump. The '*' in
front of the TTCH address indicates that it is a mini trace table
snapshot. A mini trace table snapshot only contains the most current
64K of data for each CPU. System trace data requested by RTM and
ABDUMPs will receive the mini snapshot when the number of
concurrent snapshots could impact system availability.
ASID Shows the ASID the trace table in the dump.
TCB Shows the address of the TCB associated with this ASID.
TIME Shows the time that the trace table snapshot was taken.
A SYSMDUMP and IEATDUMP only contains the TTCH for that dump. To
see if the trace table snapshot is a mini trace, look in the output of the IPCS
Status Worksheet command. The WORKSHEET shows the Trace Table
Control Header (TTCH) address. The SYSTRACE TTCH(TTCH-address)
command displays “MINI SYSTEM TRACE TABLE” as the title for a mini
trace.
WEB(WEB-list)
Specifies the formatting of trace entries running on behalf of the listed WEB
(work element block) addresses.
v Address Space Selection Parameters
Use these parameters to obtain trace entries from particular address spaces,
which you specify by their address space identifiers (ASIDs). If you omit these
parameters, the default is CURRENT. For more information, see the select ASID
service in z/OS MVS IPCS Customization. You can specify several address space
selection parameters.
ALL
Requests formatting of system trace entries for all address spaces.
CURRENT
Requests formatting of trace entries for the current address spaces on the
following, depending on the dump being formatted:
– For an SVC dump, on the processor that requested the dump.
– For a stand-alone dump, on any processor at the time of the dump.
The current address spaces include the home, primary, and secondary
address spaces. CURRENT is the default when you do not specify any other
parameters.
ERROR
Specifies formatting of trace entries for any address space with an error
indicator or containing a task with an error indicator.
TCBERROR
Specifies formatting of trace entries for any address space containing a task
with an error indicator. Entries for address spaces with an error indicator are
not formatted.

Chapter 5. IPCS subcommands 311

SYSTRACE subcommand

ASIDLIST(asidlist)
Requests formatting of trace entries for the specified address spaces or
ranges of address spaces. An address space identifier (ASID) is 1 through
65535 and is specified in decimal (nnn or F'nnn'), hexadecimal (X'hhh'), or
binary (B'bbbb'). In a range, separate the first and last ASIDs by a colon (:).
In the list of ASIDs, the ranges can overlap and duplicate asids can be
specified.
JOBLIST(joblist)
JOBNAME(joblist)
Requests formatting of trace entries for the address spaces associated with
the specified jobs. You can specify an unlimited number of job names.
v SETDEF-Defined Parameters
ACTIVE or MAIN or STORAGE
DATASET(dsname) or DSNAME(dsname)
FILE(ddname) or DDNAME(ddname)
Specifies the source of the source description containing the system trace. If
one of these parameters is not specified, the source is your current source.
ACTIVE, MAIN, or STORAGE specifies central storage as the source.
DSNAME or DATASET specifies the name of a cataloged data set as the
source.
FILE or DDNAME specifies the ddname of a data set as the source.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the SYSTRACE subcommand.
v Example
For a list of system trace entries and an example of SYSTRACE output, see z/OS
MVS Diagnosis: Tools and Service Aids.

TCBEXIT subcommand — run a TCB exit routine

Use the TCBEXIT subcommand to run an IBM-supplied or an installation-supplied
exit routine.
v Syntax

{ TCBEXIT } { pgmname | * }
{ TCBX }
data-descr
[ AMASK(mask) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
pgmname or *
Specifies an IBM-supplied or installation-supplied exit routine, which
processes system control blocks. The pgmname specifies the name of a

312 z/OS MVS IPCS Commands

 TCBEXIT subcommand

routine. * specifies the following IBM-supplied TCB exit routines; these exit
routines are specified by parmlib members embedded in the BLSCECT
parmlib member.
Exit Routine
Data Processed
IECDAFMT
Data management control blocks
IECIOFMT
Input/output supervisor (IOS) and execute channel program (EXCP)
control blocks
IEAVTFMT
Recovery termination management (RTM) control blocks
IEAVSSA1
Vector Facility data file.IEAVSSA1 exit routine
IEAVXD01
Access registers
IEAVD30
Linkage stack
An installation-supplied TCB exit routine that you can specify must:
– Be named with a maximum of 8 characters. The first character must be
alphabetic.
– Reside in a library available to IPCS, such as a step library, job library, or
link library.
For more information about writing installation TCB exit routines, see z/OS
MVS IPCS Customization.
data-descr
Specifies the address of the TCB to be passed to the exit routine. The data
description parameter consists of five parts:
– An address (required)
– Address processing parameters (optional)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.
AMASK(mask)
Specifies an integer mask that TCBEXIT is to AND to the dump addresses
passed by the exit to the storage access and format service routines. The
values of the mask can be only X'00FFFFFF' or X'7FFFFFFF' or the
corresponding decimal or binary values.
v Return Codes

Code Explanation
12 Severe error, an error condition or user request forced early end to the
subcommand processing.
16 Ending error, an error condition from a called service routine forced an
early end to the subcommand processing.

Chapter 5. IPCS subcommands 313

TCBEXIT subcommand

Code Explanation
other An exit generated return code.

v Example 1: Invoke an IBM-supplied TCB exit to display RTM-related control

blocks.
– Action
COMMAND ===> tcbexit ieavtfmt 21C.%
– Result
This example invokes the IBM-supplied TCB exit routine (IEAVTFMT) that
processes recovery termination management (RTM) control blocks. Using the
indirect addressing notation (21C.%), addressability is established to the
current TCB.

*** NOT ALL EED’S AVAILABLE COULD BE ACCESSED ***

INVALID EED TYPE ENCOUNTERED AT LOCATION 009FF750

EED1: 009FF750
+0000 E2E3D2C5 009FEA68 00000000 00000000 | STKE.þ.......... |
+0010 0000001B 00000000 00000000 00000000 | ................ |
+0020 00000000 00000000 00000000 00000000 | ................ |
+0030 00000000 00000000 00AA0400 00000000 | ................ |
+0040 009FBE00 009FAFB0 00000000 00006EF4 | .--..---......>4 |
+0050 00000000 00006F40 00000000 00000000 | ......? ........ |
+0060 00000000 00000000 00000000 00000000 | ................ |
+0070 00000000 00000000 00000000 00000000 | ................ |
+0080 00000000 00000000 00000000 00000000 | ................ |
+0090 00000000 00000000 00000000 00000000 | ................ |
+00A0 00000000 00000000 00000000 00000000 | ................ |
+00B0 00000000 00000000 00000000 00000000 | ................ |
+00C0 00000000 00000000 00000000 00000000 | ................ |
+00D0 00000000 00000000 00000000 00000000 | ................ |
+00E0 00000000 00000000 D4E2E3D9 40404040 | ........MSTR |
+00F0 D3D3C140 40404040 40404040 40404040 | LLA |
+0190 00000000 00000000 00000000 00000000 | ................ |

v Example 2: Invoke all IBM-supplied TCB exits.

– Action
COMMAND ===> tcbexit * 21C.%
– Result
This example invokes all of the IBM-supplied TCB exit routines to process
TCBs and related control blocks. Using the indirect addressing notation
(21C.%), addressability is established to the current TCB.
v Example 3: Invoke an installation-supplied TCB exit.
– Action
COMMAND ===> tcbexit testtcb 715b0.
– Result
This example invokes an installation-supplied routine TESTTCB, passing it
the TCB address X'715B0'.

TRAPLIST subcommand — list the status of IPCS traps

Use the TRAPLIST subcommand to display the status of IPCS-supplied traps.

314 z/OS MVS IPCS Commands

 TRAPLIST subcommand

If you write your own installation exit and use one of the exit service routines,
which are described in z/OS MVS IPCS Customization, use the TRAPON, TRAPOFF,
and TRAPLIST subcommands to obtain diagnostic input and output information.
You can also use these subcommands to set traps when executing IPCS code that
uses the exit service routines.
v Related subcommands
– TRAPON
– TRAPOFF
– GO
v Syntax

TRAPLIST { ALL }
{ code }
{ (code-list) }

v Parameters
ALL
code
code-list
Identifies the IPCS-supplied traps whose status is to be displayed. ALL
specifies all IPCS-supplied traps. All is the default; if you do not specify any
codes, IPCS displays the status of all traps.
code specifies a code that identifies an IPCS-supplied exit service routine.
code-list specifies a list of codes. When you specify a list, separate the list
members with commas and enclose the list in parentheses. Otherwise,
parentheses are optional.
The codes are:
Code Exit Service Routine
ACC Storage access service
ADS Add symptom service
CBF Control block formatter service
CBS Control block status service
CQE Contention queue element create service
CSI CSVINFO macro
ECT ECT exit service
EQS Equate symbol service
FMT Format model processor service
GTS Get symbol service
MAP Map service
NAM Name service
NDX Table of contents service
NTK NAME/TOKEN lookup service
PRT Standard print service

Chapter 5. IPCS subcommands 315

TRAPLIST subcommand

PR2 Expanded print service

SEL Select ASID service
SYM Symbol service
WHS WHERE service
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the TRAPLIST subcommand.
v Example 1: List the traps and the options associated with all the exit service
routines.
– Action
COMMAND ===> traplist all
– Result
TRAPLIST generates the following output, after the TRAPON ALL INPUT
OUTPUT subcommand activated all the trap options for each of the exit
service routines.

ACC INPUT(ABDPL PARMS STOP) OUTPUT(RETC DATA PARMS STOP ERROR)

ADS INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
CBF INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
CBS INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
CQE INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
CSI INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
ECT INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
EQS INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
FMT INPUT(ABDPL PARMS DATA STOP) OUTPUT(RETC PARMS STOP ERROR)
GTS INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
MAP INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
NAM INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
NDX INPUT(ABDPL STOP) OUTPUT(RETC STOP )
NTK INPUT(ABDPL STOP) OUTPUT(RETC STOP )
PRT INPUT(ABDPL STOP) OUTPUT(RETC STOP )
PR2 INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
SEL INPUT(ABDPL PARMS STOP) OUTPUT(RETC DATA PARMS STOP ERROR)
SYM INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)
WHS INPUT(ABDPL PARMS STOP) OUTPUT(RETC PARMS STOP ERROR)

v Example 2: List the trap options associated with the storage access service.
– Action
COMMAND ===> traplist acc
– Result
TRAPLIST generates the following output line, after the TRAPON ACC
subcommand activated the trap options for the storage access service.
ACC INPUT(ABDPL PARM STOP) OUTPUT(RETC PARM DATA STOP ERROR)

TRAPOFF subcommand — deactivate IPCS traps

Use the TRAPOFF subcommand to deactivate IPCS-supplied traps. If you write
your own installation exit and use one of the exit service routines, which are
described in z/OS MVS IPCS Customization, use the TRAPON, TRAPOFF, and
TRAPLIST subcommands to obtain diagnostic input and output information. You
can also use these subcommands to set traps when executing IPCS code that uses
the exit service routines.
v Related subcommands
– TRAPON
– TRAPLIST

316 z/OS MVS IPCS Commands

 TRAPOFF subcommand

– GO
v Syntax

TRAPOFF { ALL }
{ code }
{ (code-list) }

v Parameters
ALL
code
code-list
Identifies the IPCS-supplied traps to be deactivated. ALL specifies all
IPCS-supplied traps. All is the default; if you do not specify any codes, IPCS
deactivates all traps.
code specifies a code that identifies an IPCS-supplied exit service routine.
code-list specifies a list of codes. When you specify a list, separate the list
members with commas and enclose the list in parentheses. Otherwise,
parentheses are optional.
The codes are:
Code Exit Service Routine
ACC Storage access service
ADS Add symptom service
CBF Control block formatter service
CBS Control block status service
CQE Contention queue element create service
CSI CSVINFO macro
ECT ECT exit service
EQS Equate symbol service
FMT Format model processor service
GTS Get symbol service
MAP Map service
NAM Name service
NDX Table of contents service
NTK NAME/TOKEN lookup service
PRT Standard print service
PR2 Expanded print service
SEL Select ASID service
SYM Symbol service
WHS WHERE service
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the TRAPOFF subcommand.

Chapter 5. IPCS subcommands 317

TRAPOFF subcommand

v Example 1: Turn off all traps associated with the exit service routines.
– Action
COMMAND ===> trapoff all
– Result
All IPCS-supplied traps are deactivated.
v Example 2: Turn off the traps for the storage access and control block formatter
service routines.
– Action
COMMAND ===> trapoff (acc cbf)
– Result
Traps for the storage access and the control block formatter services are
deactivated.

TRAPON subcommand — activate IPCS traps

Use the TRAPON subcommand to activate IPCS-supplied traps. If you write your
own installation exit and use one of the exit service routines, which are described
in z/OS MVS IPCS Customization, use the TRAPON, TRAPOFF, and TRAPLIST
subcommands to obtain diagnostic input and output information. You can also use
these subcommands to set traps when executing IPCS code that uses the exit
service routines.

If a TRAPON subcommand requests several traps, IPCS activates only supported

traps. Whenever an unsupported trap is requested, IPCS issues the following
message:
BLS17014I Trap of INPUT/OUTPUT(trap) is not supported for service(sss)

where sss is the name of the requested exit service routine.

Note: Activated traps are not retained between IPCS sessions.

During STOP processing, all traps are temporarily deactivated until the GO
subcommand is entered to resume the stopped operation. This temporary
deactivation of traps is done because some of the subcommands available during
STOP processing also use exit services and therefore are also trapped.
v Related subcommands
– TRAPOFF
– TRAPLIST
– GO
v Syntax

318 z/OS MVS IPCS Commands

 TRAPON subcommand

TRAPON { ALL }
{ code }
{ (code-list) }
[INPUT [([ABDPL] ) ]]
[ [ [DATA] ]]
[ [ [PARMS] ]]
[ [ [STOP] ]]
[ ]
[NOINPUT ]
[OUTPUT [([RETC] ) ]]
[ [ [DATA] ]]
[ [ [PARMS] ]]
[ [ [STOP] ]]
[ [ [ERROR] ]]
[ ]
[NOOUTPUT ]

v Parameters
ALL
code
code-list
Identifies the IPCS-supplied traps to be activated. ALL specifies all
IPCS-supplied traps. All is the default; if you do not specify any codes, IPCS
activates all traps.
code specifies a code that identifies an IPCS-supplied exit service routine.
code-list specifies a list of codes. When you specify a list, separate the list
members with commas and enclose the list in parentheses. Otherwise,
parentheses are optional.
The codes are:
Code Exit Service Routines
ACC Storage access service
ADS Add symptom service
CBF Control block formatter service
CBS Control block status service
CQE Contention queue element create service
CSI CSVINFO macro
ECT ECT exit service
EQS Equate symbol service
FMT Format model processor service
GTS Get symbol service
MAP Map service
NAM Name service
NDX Table of contents service
NTK NAME/TOKEN lookup service
PRT Standard print service
PR2 Expanded print service
SEL Select ASID service

Chapter 5. IPCS subcommands 319

TRAPON subcommand

SYM Symbol service

WHS WHERE service
INPUT
Specifies that trap processing is to be done before performing a requested
service. If the INPUT parameter is specified without any options, all
supported input trapping options are activated. The options are:
Option Processing
ABDPL
Displays the common exit parameter list and its extension that are
passed to all services.
DATA Displays data passed to a service in addition to basic parameters.
The DATA option can be used only if the FMT code is specified.
PARMS
Displays parameters passed to a service. The PARMS option cannot
be used if the PRT and NDX codes are specified.
STOP Halts IPCS processing and prompts you for input before performing
a service. If the TSO/E NOPROMPT mode is in effect when STOP
processing is attempted, processing is not interrupted. During STOP
processing, only the following may be entered:
– IPCS subcommands GO, HELP, NOTE, TRAPLIST, TRAPOFF,
TRAPON, and TSO. Use the GO subcommand to resume
processing; the END subcommand is not valid.
– CLISTs and REXX execs that contain only the previously
mentioned subcommands.
– TSO/E commands that are normally accepted during an IPCS
session. The use of authorized TSO/E commands requires the
installation of TSO/E Release 2 or a later release.
Restriction: If you specify INPUT(STOP) or OUTPUT(STOP) when
running IPCS in the background or in a full-screen dialog, it is
ignored.
See Example 1 for a list of the trap options supported by the INPUT and
OUTPUT parameters for each exit service routine.
NOINPUT
Specifies that no trap processing is to be done before performing a requested
service. NOINPUT is the default.

Note: If both NOINPUT and NOOUTPUT are specified, IPCS issues a

diagnostic message, and the TRAPON subcommand ends without alteration
to the status of the traps.
OUTPUT
Specifies that trap processing is to be done before returning to the caller of a
service. If the OUTPUT parameter is specified without any options, all
supported output trapping options are activated. The options are:
Option Processing
RETC Displays the return code from the service and the service code-list.
DATA Displays the data returned by a service in addition to basic
parameters. The DATA option can be used only if the ACC and SEL
codes are specified.

320 z/OS MVS IPCS Commands

 TRAPON subcommand

PARMS
Displays parameters returned by a service. This is the same
parameter list that is displayed as input, but it will show any values
changed by the service. The PARMS option cannot be used if the
PRT and NDX codes are specified.
STOP Halts IPCS processing and prompts you for input before returning
from a service. If the TSO/E NOPROMPT mode is in effect when
STOP processing is attempted, processing is not interrupted, and no
message is issued. During STOP processing only the following may
be entered:
– IPCS subcommands GO, HELP, NOTE, TRAPLIST, TRAPOFF,
TRAPON, and TSO. Use the GO subcommand to resume
processing; the END subcommand is not valid.
– CLISTs and REXX execs that contain only the previously
mentioned subcommands.
– TSO/E commands that are normally accepted during an IPCS
session. The use of authorized TSO/E commands requires the
installation of TSO/E Release 2 or a later release.
Restriction: If you specify OUTPUT(STOP) or INPUT(STOP) when
running IPCS in the background or in a full-screen dialog, it is
ignored.
ERROR
Specifies that the other output trap actions are to take place only
when the return code from the service is not zero. This is a
convenient means of reducing the output from the trap facility, but
still seeing important failure-related information.
See Example 1 for a list of the trap options supported by the INPUT and
OUTPUT parameters for each exit service routine.
NOOUTPUT
Specifies that no trap processing is to be done before returning to the caller
of a service. NOOUTPUT is the default.

Note: If both NOINPUT and NOOUTPUT are specified, IPCS issues a

diagnostic message, and the TRAPON subcommand ends without alteration
to the status of the traps.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the TRAPON subcommand.
v Example 1: Turn on all traps associated with the exit service routines.
– Action
COMMAND ===> trapon all input(abdpl,parms)
– Result
This example activates the trap for all the exit services. When a trap is hit, the
ABDPL and the parameter list (if used) are displayed.
v Example 2: Turn on all traps and all options associated with the storage access
and the control block formatter service routines and display the return code on
exit.
– Action
COMMAND ===> trapon (acc cbf) output(retc)
– Result

Chapter 5. IPCS subcommands 321

TRAPON subcommand

This example activates the traps for the storage access and the control block
formatter service routines and displays the return code on exit from these
services.

TSO subcommand — run a TSO/E command

Use the TSO subcommand to:
v Invoke a TSO/E command whose name is identical to an IPCS subcommand.
See the description of the tsocmd parameter for information concerning
authorized TSO/E commands.
v Invoke a CLIST or REXX exec containing TSO/E commands whose names are
identical to IPCS subcommands.
v Enter TSO/E mode.
v Invoke a TSO/E Command
Use the TSO subcommand to enter TSO/E commands whose names are
identical to IPCS subcommands except when invoking ISPF.
For example, to request the display of status for all batch jobs whose job name
begins with your TSO/E userid, enter:
tso status
If you do not precede the STATUS command with TSO, the system does not
interpret the command as a TSO/E command. Note, however, that the system
does not allow TSO/E commands, when invoked by IPCS, to request ISPF
services. For example, using the TSO/E ALTLIB command with the QUIET
option causes ALTLIB to use ISPF services, which the system does not permit.

ISPF under IPCS

Do not invoke the ISPF command with the TSO prefix. Instead, invoke ISPF by entering
ISPF on the command line. If you enter TSO ISPF, you may obtain unpredictable results.

If TSO/E Release 2 or later is installed, you can enter installation-defined

authorized commands and authorized TSO/E commands, such as TRANSMIT
and RECEIVE (as determined by your installation). Otherwise, such commands
end abnormally.
v Invoke a CLIST or REXX Exec Containing TSO/E Commands
You can use the TSO subcommand to invoke a CLIST or REXX exec containing
TSO/E commands. You can do this in any of the three IPCS processing modes.
A CLIST or REXX exec invoked with the TSO subcommand can contain any or
all of the following:
– TSO/E commands whose names are identical to IPCS subcommands. Using
the TSO subcommand ensures that the TSO/E command is invoked instead
of an IPCS subcommand of the same name.
– Any TSO/E command. Any TSO/E command can be included in a CLIST
invoked using the TSO subcommand.
– TSO/E authorized commands in conjunction with a TSO/E function such as
SYSOUTTRAP. While in the IPCS dialog, the SYSOUTTRAP will not trap the
output from the authorized command correctly unless you use the TSO
subcommand to invoke the CLIST. However, such a CLIST can be invoked
successfully in batch or line mode without using the TSO subcommand.

322 z/OS MVS IPCS Commands

 TSO subcommand

– IPCS subcommands. To run IPCS subcommands from within a CLIST invoked

using the TSO subcommand, use the BLSGSCMD dialog program to invoke
the IPCS subcommands.
– ISPF commands. Invoke a CLIST containing ISPF commands from within
IPCS dialog or in IPCS batch mode if ISPF is active in batch.
Restriction: You can define and use up to 10 global variables in CLISTs invoked
through the IPCS dialog, if CLIST BLSCLIBD started the IPCS dialog. IPCS does
not restrict the number of global variables you can define when the IPCS dialog
is started using other approved methods. If CLIST BLSCLIBD started the IPCS
dialog, and if you require more than 10 global variables, create your own copy
of CLIST BLSCALTL and add more global variables. Modify CLIST BLSCLIBD to
point to your copy of BLSCALTL rather than to SYS1.SBLSCLI0(BLSCALTL). For
information about defining and using global variables, see z/OS TSO/E CLISTs.
v Enter TSO/E Mode
In line mode or batch mode IPCS, you can enter the TSO subcommand without
a command or CLIST or REXX exec invocation to suspend IPCS subcommand
processing and enter TSO/E mode. Then, commands entered in TSO/E mode
are processed as TSO/E commands until END is entered to resume IPCS
processing. When the END subcommand is entered, the highest return code
from the TSO/E command processing is returned.
v Syntax

TSO [ [ [%]clistnm | [%]rexxnm | tsocmd ] [operands] ]

v Parameters
clistnm
Specifies the name of the CLIST to be run. If the CLIST name is the same as
the name of a TSO/E or IPCS command, a % must precede the name.
rexxnm
Specifies the name of the REXX exec to be run. If the REXX exec name is the
same as the name of a TSO/E or IPCS command, a % must precede the
name.
tsocmd
Specifies the name of a TSO/E command to be run. If TSO/E Release 2 is
installed, tsocmd may specify the name of an installation-defined authorized
command or an authorized TSO/E command, such as TRANSMIT or
RECEIVE (as determined by your installation). See z/OS TSO/E Customization
for more information.
operands
Specifies the operands of the TSO/E command or CLIST to be run.
v Return Codes

Code Explanation
12 Severe, an error condition or user request forced early ending of
subcommand processing.
16 Ending error, an error condition from a called service routine forced an
early end to the processing.
any The return code is generated by the TSO/E command.

v Example 1: Display the status of all batch jobs.

Chapter 5. IPCS subcommands 323

TSO subcommand

– Action
COMMAND ===> tso status
– Result
This example requests the display of status for all batch jobs whose job name
begins with your TSO/E user ID. If you do not preceded the command name,
STATUS, with TSO, the IPCS STATUS subcommand are processed.
v Example 2: Send a data set to a node and user ID.
– Action
COMMAND ===> tso transmit nodeb.user2 da(’sys1.parmlib’)
or
COMMAND ===> transmit nodeb.user2 da(’sys1.parmlib’)
– Result
These commands request that a copy of a data set (SYS1.PARMLIB) be sent to
a specified node and user (nodeb.user2). It is not necessary to precede the
command name (TRANSMIT) with TSO because there is no IPCS
subcommand with the name TRANSMIT. IPCS processes both of the
commands in this example as TSO/E commands.

VERBEXIT subcommand — run an installation-supplied or an

IBM-supplied verb exit routine
Use the VERBEXIT subcommand to run an installation-supplied or IBM-supplied
verb exit routine.
v Syntax

{ VERBEXIT } { pgmname }
{ VERBX } { verbname }
[ ’parameter [,parameter]...’ ]
[ AMASK(mask) ]
[ SYNTAX | NOSYNTAX ]
[ TOC | NOTOC ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
pgmname
Specifies a verb exit routine. The pgmname can be a maximum of 8
alphanumeric characters; the first character must be alphabetic. An
installation-supplied verb exit routine must reside in a load module library
available to IPCS, such as a step library, job library, or link library. For
information about writing verb exit routines, see z/OS MVS IPCS
Customization.
verbname
Specifies the name of a verb exit routine. For IPCS to access an

324 z/OS MVS IPCS Commands

 VERBEXIT subcommand

installation-supplied verb exit through a verb name, your installation needs

to either create or modify the BLSCUSER parmlib member.
An installation-supplied verb exit routine must reside in a load module
library available to IPCS, such as a step library, job library, or link library.
For information about the BLSCUSER parmlib member and on writing verb
exit routines, see z/OS MVS IPCS Customization.
Table 22 lists the verb names of IBM-supplied verb exit routines. These verb
exit routines are defined in SYS1.PARMLIB members. For each verb name,
the table provides a cross reference telling where you can find an
explanation of the verb name, its optional parameters if applicable, and
information concerning the component, function, or product-specific data
that these verb exit routines process.

Note: Other products might have a dump formatter available for use with
IPCS. Check the related product documentation for information.
Table 22. Verb name summary
Verb Name Component, Product, or Function Where Documented
ALCWAIT Allocation See “VERBEXIT ALCWAIT subcommand — list jobs
waiting for devices” on page 328
AOMDATA Asynchronous operations manager z/OS DFSMSdfp Diagnosis
ASMDATA Auxiliary storage management See “VERBEXIT ASMDATA subcommand — format
auxiliary storage manager data” on page 328
AVMDATA Availability manager See “VERBEXIT AVMDATA subcommand — format
availability manager data” on page 328
BLSAIPST System initialization See “VERBEXIT BLSAIPST subcommand — format
system initialization data” on page 328
CBDATA Component Broker See “VERBEXIT CBDATA subcommand — format
component broker data” on page 329
CICSDATA Customer Information Control System CICS Transaction Server for z/OS Knowledge Center
(www.ibm.com/software/htp/cics/tserver/v52/
library/index.html)
DAEDATA Dump analysis and elimination See “VERBEXIT DAEDATA subcommand — format
dump analysis and elimination data” on page 330
DSNWDMP DB2 IMS in IBM Knowledge Center (www.ibm.com/
support/knowledgecenter/SSEPH2)
GRSTRACE Global resource serialization See “VERBEXIT GRSTRACE subcommand — format
Global Resource Serialization data” on page 331
HASMFMTM JES2 See z/OS JES2 Diagnosis
| IEAVTFCB Dumping services See “VERBEXIT IEAVTFCB subcommand — format
| SVC dump system-scope statistics” on page 334
IEAVTSFS Dumping services See “VERBEXIT IEAVTSFS subcommand — format SVC
dump measurements and statistics report” on page 335
IEFENFVX Event notification facility (ENF) See “VERBEXIT IEFENFVX subcommand — list ENF
listeners” on page 340
IEFIVAWT Allocation See “VERBEXIT IEFIVAWT subcommand — list
pending XCF work for tape allocation” on page 340
IEFIVIGD Allocation See “VERBEXIT IEFIVIGD subcommand — list global
tape device information” on page 341

Chapter 5. IPCS subcommands 325

VERBEXIT subcommand

Table 22. Verb name summary (continued)

Verb Name Component, Product, or Function Where Documented
IMSDUMP Information Management System (IMS) IMS in IBM Knowledge Center (www.ibm.com/
support/knowledgecenter/SSEPH2)
IRLM Information Management System (IMS) IMS in IBM Knowledge Center (www.ibm.com/
support/knowledgecenter/SSEPH2)
JESXCF JES common coupling services MVS See “VERBEXIT JESXCF subcommand — format data
component (JES XCF) for JES XCF component” on page 342
JES3 JES3 z/OS JES3 Diagnosis
®
LEDATA Language Environment See “VERBEXIT LEDATA subcommand — format
Language Environment data” on page 342
LOGDATA Logrec buffer records See “VERBEXIT LOGDATA subcommand — format
logrec buffer records” on page 345
MMSDATA MVS message service See “VERBEXIT MMSDATA subcommand — format
MVS message service data” on page 348
MTRACE Master trace table See “VERBEXIT MTRACE subcommand — format
master trace entries” on page 348
NUCMAP Modules in the nucleus See “VERBEXIT NUCMAP subcommand — map
modules in the nucleus” on page 349
SADMPMSG Stand-alone dump message log See “VERBEXIT SADMPMSG subcommand — format
stand-alone dump message log” on page 353
SMSDATA DFP Storage Management Subsystem z/OS DFSMSdfp Diagnosis
SMSXDATA
SRMDATA System resource manager See “VERBEXIT SRMDATA subcommand — format
System Resource Manager data” on page 353
SUMDUMP SVC summary dump data See “VERBEXIT SUMDUMP subcommand — format
SVC summary dump data” on page 354
SYMPTOM Symptom string See “VERBEXIT SYMPTOM subcommand — format
symptom string” on page 355
TSODATA Time Sharing Option z/OS TSO/E System Diagnosis: Data Areas in the z/OS
Internet library (www.ibm.com/systems/z/os/zos/
library/bkserv)
VSMDATA Virtual storage management See “VERBEXIT VSMDATA subcommand — format
virtual storage management data” on page 356
VTAMMAP Virtual Telecommunications Access VTAM Diagnosis
Method (VTAM)

parameter
Specifies a parameter string to be passed to either an IBM-supplied or an
installation-supplied verb exit routine.
Enclose the parameter string in apostrophes. When IPCS passes the string to
the exit routine, it omits the apostrophes. If the string parameter itself
includes an apostrophe, enter a pair of apostrophes; IPCS will convert them
to a single apostrophe when passing the string to the exit routine.
Verb exits are responsible for parsing the string. When specifying keyword
strings, be aware of the following conditions:
– Spell out the full form of the keyword strings expected by the verb exit.
Not all of the verb exits recognize truncated keywords.

326 z/OS MVS IPCS Commands

 VERBEXIT subcommand

– Use commas to separate parameters when you specify more than one
parameter and the verb exit syntax indicates comma separators are
appropriate. Avoid using blanks or horizontal tabulation character to
separate parameters, even if the TSO syntax rule says they are
interchangeable with commas.
– Follow the special syntax rules required by verb exit routines, if any.
Authors of verb exit routines are allowed to implement special syntax
rules for the parameters, depending on the primary usage of the routines.
For example, verb exit routines provided by DB2 might implement SQL
rules rather than TSO rules.
For IBM-supplied verb exit routines, the parameter string that can be
specified is described in this book under the corresponding verb name.
For installation-supplied verb exit routines, the parameter string that can be
specified must have its content and meaning defined by the
installation-supplied exit routine.
AMASK(mask)
Specifies an integer mask that VERBEXIT is to AND to the dump addresses
passed by the exit to the storage access and format service routines. Only
X'00FFFFFF', X'7FFFFFFF' or the corresponding decimal or binary values are
accepted.
SYNTAX or NOSYNTAX
Specifies or suppresses a syntax check of the parameter string passed to the
verb exit routine. SYNTAX specifies the syntax check. NOSYNTAX
suppresses the syntax check and is the default.
TOC or NOTOC
Specifies or suppresses table or contents, print file, and terminal output.
The TOC option anticipates that the exit will write a report. IPCS writes a
standard table of contents entry before giving the exit control. An error
message is written if no report is written.
The NOTOC option suppresses the output.
v Return Codes

Code Explanation
12 Severe error, an error condition or user request forced early termination of
the subcommand.
16 Terminating error, an error condition from a called service routine forced an
early termination of the subcommand.
other An exit generated return code.

v Example: Invoke an installation-supplied verb exit represented by the verb name

HISTORY.
– Action
COMMAND ===> verbexit history ’rb,56b34’
– Result
The installation-supplied verb exit routine HISTORY receives the parameter
string RB,56B34.

Chapter 5. IPCS subcommands 327

VERBEXIT ALCWAIT subcommand

VERBEXIT ALCWAIT subcommand — list jobs waiting for devices

Specify the ALCWAIT verb name on the VERBEXIT subcommand to format a list
of jobs waiting for devices.

Note: To obtain a list of jobs holding a device group and the jobs waiting for a
device group, use the ANALYZE subcommand with the RESOURCE parameter.
v Parameters
The VERBEXIT ALCWAIT subcommand has no parameters.
v Example: For an example of ALCWAIT output, see the allocation/unallocation
component in z/OS MVS Diagnosis: Reference.

VERBEXIT ASMDATA subcommand — format auxiliary storage

manager data
Specify the ASMDATA verb name and optional parameters on the VERBEXIT
subcommand to format diagnostic data from the auxiliary storage manager (ASM).
v Syntax

VERBEXIT ASMDATA [ ’parameter [,parameter]...’ ]

The parameters are:

[FULL]
[SUMMARY]
[VIO]

v Parameters
Use the parameters to select the type of report. If you omit the parameters, the
default is FULL.
FULL
Produces a full report of ASM control blocks.
SUMMARY
Produces a summary report of the paging-related control blocks.
VIO
Produces a summary report of the VIO-related control blocks.
v Example: For an example of ASMDATA output, see the ASM component in z/OS
MVS Diagnosis: Reference.

VERBEXIT AVMDATA subcommand — format availability manager data

Specify the AVMDATA verb name on the VERBEXIT subcommand to format
diagnostic data from the availability manager.
v Parameters
The VERBEXIT AVMDATA subcommand has no parameters.

VERBEXIT BLSAIPST subcommand — format system initialization data

Specify the BLSAIPST verb name on the VERBEXIT subcommand to format status
data collected during IPL, NIP, and Master Scheduler Initialization (MSI) during
system initialization.
v Parameters

328 z/OS MVS IPCS Commands

 VERBEXIT BLSAIPST subcommand

The VERBEXIT BLSAIPST subcommand has no parameters.

v Example: For an example of BLSAIPST output, see the system initialization
component in z/OS MVS Diagnosis: Reference.

VERBEXIT CBDATA subcommand — format component broker data

Specify the CBDATA verb name and optional parameters on the VERBEXIT
subcommand to format diagnostic data for the Component Broker element in
WebSphere® Application Server Enterprise Edition for z/OS. CBDATA displays the
following:
v Display of the Component Broker Global control blocks
v Display of Component Broker address space control blocks
v Display of Component Broker address space control blocks with only one
Component Broker TCB
v Display of ORB control block information
v Syntax

VERBEXIT CBDATA [ ’parameter [,parameter]...’ ]

The parameters are:

[GLOBAL]
[ASID(asid-number)]
[ASID(asid-number BTCB(btcb-address)]
[ASID(asid-number ORB(orb-address)]

v Parameters
Use these parameters to format the data areas. If you omit the parameters, the
default is GLOBAL.
GLOBAL
Displays the following formatted Component Broker control blocks
– BGVT address - Component Broker Global Vector table
– ASR Table and ASR Table entries - Active Server Respository information
ASID(asid-number)
Displays the following formatted Component Broker control blocks
– BACB - Component Broker address space control block
– BTRC,TBUFSET,TBUF - Component Broker component trace control
blocks
– BOAM,BOAMX - CB BOA control blocks
– ACRW queue- Application Control Region work element control blocks
– DAUE- DB2 ASR Table
– BTCB queues - Component Broker TCB
ASID(asid-number) BTCB(btcb_address)
Displays the following formatted Component Broker control blocks and the
specified BTCB
– BACB - Component Broker address space control block
– BTRC,TBUFSET,TBUF - CB component trace control blocks
– BOAM,BOAMX - CB BOA control blocks
– ACRW queue- Application Control Region work element control blocks
– DAUE- DB2 ASR Table

Chapter 5. IPCS subcommands 329

VERBEXIT BLSAIPST subcommand

– BTCB - Component Broker TCB

– Displays ORB information for the Component Broker TCB
ASID(asid-number) ORB(orb_address)
Displays ORB information

VERBEXIT DAEDATA subcommand — format dump analysis and

elimination data
Specify the DAEDATA verb name on the VERBEXIT subcommand to format the
dump analysis and elimination (DAE) data in an SVC dump or SYSMDUMP
dump. DAEDATA formats and prints the DAE data in the dump header record for
the dump. If DAE data is available, DAEDATA displays the following:
v Explanation of the DAE action taken for this dump
v The number of occurrences
v The original dump identification data, including the sequence number, data,
time, and the CPU serial number
v The unique identification criteria
v The MVS symptom string and symptom parameters
v The RETAIN symptom string and symptom parameters
v The symptom string verbal description
v Any additional symptoms from the SDWA
v Parameters
The VERBEXIT DAEDATA subcommand has no parameters.
v Example: Obtain DAE information from the dump.
– Action
VERBEXIT DAEDATA
– Result

330 z/OS MVS IPCS Commands

 VERBEXIT GRSTRACE subcommand

****** DUMP ANALYSIS AND ELIMINATION (DAE) ******

THIS DUMP WAS NOT SUPPRESSED BECAUSE

THE VRA KEY TO ALLOW SUPPRESSION OF DUPLICATE DUMPS WAS ABSENT.

CRITERIA FOR USE AS A UNIQUE DUMP IDENTIFIER BY DAE:

MINIMUM NUMBER OF SYMPTOMS: 05 FOUND: 09

MINIMUM TOTAL STRING LENGTH: 025 FOUND: 144

SYMPTOMS REQUIRED TO BE PRESENT:

MOD/ CSECT/
SYMPTOMS THAT ARE TO BE USED IF AVAILABLE, BUT ARE NOT REQUIRED:
PIDS/ AB/S AB/U REXN/ FI/ REGS/ HRC1/ SUB1/

MVS SYMPTOM STRING:

MOD/NUCLEUS CSECT/IARUVXCH PIDS/5752SC1CR AB/S00C4 REXN/IARRR

FI/18F4B22100EF181BBF2FD0F0 REGS/0A8D0 HRC1/00000004

SUB1/REAL#STORAGE#MANAGEMENT

RETAIN SEARCH ARGUMENT:

RIDS/NUCLEUS#L RIDS/IARUVXCH PIDS/5752SC1CR AB/S00C4 RIDS/IARRR#R

VALU/HBF2FD0F0 REGS/0A8D0 PRCS/00000004 VALU/CNAGEMENT

SYMPTOMS PRESENT FOR USE AS A UNIQUE DUMP IDENTIFIER BY DAE:

RETAIN
MVS KEY KEY SYMPTOM DATA EXPLANATION
------- ------ ------------ -----------
MOD/ RIDS/ NUCLEUS LOAD MODULE NAME
CSECT/ RIDS/ IARUVXCH ASSEMBLY MODULE CSECT NAME
PIDS/ PIDS/ 5752SC1CR PRODUCT/COMPONENT IDENTIFIER
AB/S AB/S S00C4 ABEND CODE-SYSTEM
REXN/ RIDS/ IARRR RECOVERY ROUTINE CSECT NAME
FI/ VALU/H 18F4B22100EF181BBF2FD0F0
FAILING INSTRUCTION AREA
REGS/ REGS/ 0A8D0 REG/PSW DIFFERENCE
HRC1/ PRCS/ 00000004 REASON CODE
SUB1/ VALU/C REAL#STORAGE#MANAGEMENT
COMPONENT SUBFUNCTION
ADDITIONAL SYMPTOM DATA NOT USED BY DAE TO IDENTIFY THIS DUMP:

RETAIN
MVS KEY KEY SYMPTOM DATA EXPLANATION
------- ------ ------------ -----------
VCBI2/ VALU/H 3C7800F2D80001B017C800000000011BE84401ACDC90
CONTROL BLOCK ID AND DATA
CID1/ VALU/C SC1CR COMPONENT IDENTIFIER
AMD1/ VALU/C 04#14#87 MODULE ASSEMBLY DATE
VRS1/ VALU/C HBB3310 VERSION-PRODUCT/PTF IDENTIFIER
RRL1/ FLDS/ IARRRCV RECOVERY ROUTINE LABEL
CDB1/ VALU/C 5752 BASE COMPONENT IDENTIFIER
HLH1/ VALU/H 0800C000 HIGHEST LOCK HELD INDICATOR
SUP1/ VALU/H 10000000 PSASUPER FLAGS
FRR1/ VALU/H 01ACFC90 FRR PARAMETER AREA
ASID1/ VALU/H 00DE TASK RELATED ASID
ORCC1/ PRCS/ 0C4000 ORIGINAL COMPLETION CODE
ORRC1/ PRCS/ 00000004 ORIGINAL REASON CODE

*********************** END OF DATA *****************************

VERBEXIT GRSTRACE subcommand — format Global Resource

Serialization data
Specify the GRSTRACE, QCBTRACE, or Q verb name on the VERBEXIT
subcommand to format diagnostic data from the major control blocks for global
resource serialization.

Chapter 5. IPCS subcommands 331

VERBEXIT GRSTRACE subcommand

v Syntax

VERBEXIT GRSTRACE [ ’parameter [,parameter]...’ ]

The parameters are:

Data Selection Parameters:

[DETAIL]
[SUMMARY]

Time format Parameters:

[TIME(LOCAL|GMT|UTC)]

Additional Filter Parameters:

[START(mm/dd/yy,hh.mm.ss.dddddd)]
[STOP(mm/dd/yy,hh.mm.ss.dddddd)]
[SYSNAME(sysname)]
[QNAME(qname)]
[RNAME(rname)]
[STEP] [ SYSTEM] [ SYSTEMS]
[JOBNAME(jobname)]
[ASID(asid)]
[TCB(tcb)]
[RESERVE]
[CONTENTION]

SETDEF-Defined Parameters:
Note: You can override the following SETDEF parameters.

[DSNAME(dsname) | DATASET(dsname) ]
[FILE(ddname) | DDNAME(ddname) ]
[PATH(path-name) ]
[FLAG(severity)]
[PRINT | NOPRINT]
[TERMINAL | NOTERMINAL]
[TEST | NOTEST]

v Data Selection Parameters

DETAIL
Provides a detailed GRSTRACE report. The detailed report contains ENQ
diagnostic data in addition to all the important ENQ context information
that the summary report displays.
SUMMARY
Provides a summary GRSTRACE report. The summary report contains all
the relevant context information such as QName, RName, Sysname, Scope,
Jobname, Asid, Tcb, Disposition, ownership status, wait and grant times.
SUMMARY is the default.
v Time format Parameters
TIME(LOCAL|GMT|UTC)
Specifies the time format to use for the GRSTRACE report.
– LOCAL: All ENQ relevant times should be formatted in local time.
– GMT: All ENQ relevant times should be formatted in GMT time.
– UTC: All ENQ relevant times should be formatted in UTC time. This is
the exact store clock timestamp.
v Additional Filter Parameters
Use these parameters to limit the scope of the data in the report. If no data
selection parameter is selected, the default is NO FILTERING. At least one
requestor in a resource chain must match all of the filtering options in order for

332 z/OS MVS IPCS Commands

 VERBEXIT GRSTRACE subcommand

a resource to be displayed. Wildcard values are allowed for the SYSNAME,

JOBNAME, QNAME, and RNAME filters. Use * to match zero or more
characters and ? for exactly one character. See here for an example.
START(mm/dd/yy,hh.mm.ss.dddddd)
Specifies the date and time used to display ENQ resources with requests that
occurred at or after this time. The time format must match the time format
specified with the TIME keyword. When you do not specify START, IPCS
starts with the oldest ENQ request. Specify the date and time in
mm/dd/yy,hh.mm.ss.dddddd format.

Note: The following rules apply to the date and time specifications:
– The month and day can be specified in single or double digits.
– Separate the date from the time with a comma.
– The time can be local, by default or specified in a TIME(Local) parameter,
or GMT or UTC, if specified in a Time(GMT) or Time(UTC) parameter.
– Hours, minutes, and seconds can be specified in single or double digits.
– The time can be truncated anywhere on the right.
– The time can be left off completely, in which case, it defaults to
00:00:00.000000 (midnight).
STOP(mm/dd/yy,hh.mm.ss.dddddd)
Specifies the date and time used to display ENQ resources with requests that
occurred up to or before this time. The time format must match the time
format specified with the TIME keyword. When you do not specify STOP,
IPCS ends with the newest ENQ request.
See the START parameter for guidelines on how to specify the time and
date.
SYSNAME(sysname)
Displays all ENQ resources with the given specified system name. Note in
GRS=STAR, resource requests from other systems are not maintained in local
storage. Thus, a query specifying another system name may only receive
data back from GRSDATA, not GRSTRACE.
QNAME(qname)
Displays all ENQ resources with the specified QNAME (major name).
RNAME(rname)
Displays all ENQ resources with the specified RNAME (minor name).
[STEP] [ SYSTEM] [ SYSTEMS]
Displays all ENQ resources with a scope of STEP, SYSTEM, or SYSTEMS.
JOBNAME(jobname)
Displays all ENQ resources associated with the specified job name.
ASID(asid)
Displays all ENQ resources associated with the specified address space ID.
TCB(tcb)
Displays all ENQ resources associated with the specified task
RESERVE
Displays only RESERVE requests that have not been converted to global
ENQs.

Chapter 5. IPCS subcommands 333

 VERBEXIT GRSTRACE subcommand

CONTENTION
Displays only ENQ resources that are in ENQ contention. Device RESERVE
contention is not taken into consideration.
v Example: Match any resource requests that have the following:
– A QNAME starting with SYS, followed by zero or more characters until an R
is found, followed by two specific characters and ending in an F (for example,
SYSZRACF)
– RNAME is SOMESPECIFICRNAME
– SCOPE=SYSTEMS
– JOBNAME starts with DB2
– Action
IP VERBX GRSTRACE 'QNAME(SYS*R??F) RNAME(SOMESPECIFICRNAME)
SYSTEMS JOBNAME(DB2*)'
– Result
For an example of GRSTRACE output, see the global serialization resource
component in z/OS MVS Diagnosis: Reference.

| VERBEXIT IEAVTFCB subcommand — format SVC dump

| system-scope statistics
| Specify the IEAVTFCB verb name on the VERBEXIT subcommand to format the
| SVC system-scope statistics.
| v Parameters
| The VERBEXIT IEAVTFCB subcommand has no parameters.

| Note: The report that is generated from VERBX IEAVTFCB does not include the
| data from the current dump. To include the data of the current dump, you can
| issue IPCS VERBX IEAVTFCB STORAGE.
| v Example: Format the SVC dump system-scope statistics.
| – Action
| VERBEXIT IEAVTFCB
| – Result
| SVC DUMP SYSTEM SCOPE STATISTICS REPORT
|
| NUMBER OF SDUMPS TAKEN 4
| NUMBER OF PARTIAL DUMPS 2
| LONGEST CAPTURE TIME 00:00:00.118459
| DUMP NUMBER 1
| START TIME 04/29/2016 15:54:38.288400
| NUMBER OF ADDRESS SPACES CAPTURED 1
| COMPLETE DUMP
| LARGEST DUMP SIZE IN BLOCKS 00000000 00002632
| DUMP NUMBER 2
| START TIME 04/29/2016 16:23:43.553687
| NUMBER OF ADDRESS SPACES CAPTURED 1
| COMPLETE DUMP
| MAXIMUM EXIT DATA PAGES 00000000 00000053
| INTERESTING PARTIAL DUMPS STATISTICS:
| SDRSPMX 2
| In the results, note that there were two partial dumps with the reason code
| SDRSPMX.

334 z/OS MVS IPCS Commands

 VERBEXIT IEAVTSFS subcommand

VERBEXIT IEAVTSFS subcommand — format SVC dump

measurements and statistics report
Specify the IEAVTSFS verb name on the VERBEXIT subcommand to format the
SVC dump measurements and statistics report. The VERBEXIT IEAVTSFS output
might be requested by the IBM Support Center to understand where SDUMP spent
its time collecting a dump.
| v Syntax
|

| VERBEXIT IEAVTSFS [ ’parameter’ ]

| v Parameters
| If you omit the parameters, the default is:
| – For an SVC dump, the statistics that were captured in the dump are
| displayed.
| – For a SADMP, no statistics data is displayed.
| The optional parameters, applicable to SVC dump and SADMP, display more
| specific measurements and statistics:
| MEMORY
| Displays the dump statistics that are in the SQA storage of the dump.
| HISTORY
| Displays the history of SVC dump statistics for up to the last 254 dumps
| that were captured. The first set of statistics presented may not be the oldest
| set of statistics.
| LS Displays the SVC dump statistics for the dump that has the largest
| dynamically allocated data set except the current dump.
| LT Displays the SVC dump statistics for the dump that has the largest total
| capture time.

| Note: If VERBEXIT IEAVTSFS is issued for a SADMP, the report will indicate:
| *** The dump is a Standalone dump.
| v Example 1: Obtain the SVC dump measurements and statistics from an SVC
| dump:
| – Action
| VERBEXIT IEAVTSFS
| – Result
| Option = none
| Capture phase partial dump reason codes (IHASDRSN):
| Are all zeros.
|
| Dump Number 4
| Dump start 03/28/2016 17:21:17.671854
| Dump end 03/28/2016 17:21:17.724626
| Total dump capture time 00:00:00.052771
|
| Snap trace start 03/28/2016 17:21:17.671894
| Snap trace end 03/28/2016 17:21:17.674658
| Elapsed time 00:00:00.002763
| System nondispatchability start 03/28/2016 17:21:17.674770
| System set nondispatchable 03/28/2016 17:21:17.674777
| Time to become nondispatchable 00:00:00.000006
|

Chapter 5. IPCS subcommands 335

 VERBEXIT IEAVTSFS subcommand

| Global storage start 03/28/2016 17:21:17.674664

| Global storage end 03/28/2016 17:21:17.702846
| Global storage capture time 00:00:00.028182
|
| Defers for frame availability 0
| Pages requiring input I/O 34
| Source page copied to target 4746
| Source frames re-assigned 34
| Source AUX slot IDs re-assigned 0
| System reset dispatchable 03/28/2016 17:21:17.705046
| System was nondispatchable 00:00:00.030275
|
| Asid 0001:
| Local storage start 03/28/2016 17:21:17.675383
| Local storage end 03/28/2016 17:21:17.724573
| Local storage capture time 00:00:00.049189
| Tasks reset dispatchable 03/28/2016 17:21:17.724595
| Tasks were nondispatchable 00:00:00.049212
|
| Defers for frame availability 0
| Pages requiring input I/O 0
| Source page copied to target 2698
| Source frames re-assigned 0
| Source AUX slot IDs re-assigned 0
| Dump Exits
| Exit address 06A096D0
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.675260
| Exit end 03/28/2016 17:21:17.675264
| Exit time 00:00:00.000003
| Exit attributes: Sdump, Early Global
|
| Defers for frame availability 0
| Pages requiring input I/O 0
| Source page copied to target 127
| Source frames re-assigned 0
| Source AUX slot IDs re-assigned 0
| Exit address 0749FB10
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.675264
| Exit end 03/28/2016 17:21:17.675272
| Exit time 00:00:00.000007
| Exit attributes: Sdump, SYSMDUMP, Early Global
|
| Exit module / Exit name CEAMDMPX / IEASDUMP.SERVER
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.675272
| Exit end 03/28/2016 17:21:17.675297
| Exit time 00:00:00.000024
|
| Exit module / Exit name CNZM1SSX / IEASDUMP.SERVER
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.675297
| Exit end 03/28/2016 17:21:17.675310
| Exit time 00:00:00.000012
| Exit module / Exit name IGG0CLSD / IEASDUMP.SERVER
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.675310
| Exit end 03/28/2016 17:21:17.675324
| Exit time 00:00:00.000013
|
| Exit module / Exit name ITZTSVC / IEASDUMP.SERVER
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.675324
| Exit end 03/28/2016 17:21:17.675336
| Exit time 00:00:00.000012
|

336 z/OS MVS IPCS Commands

 VERBEXIT IEAVTSFS subcommand

| Exit module / Exit name HASJ273D / IEASDUMP.SERVER

| Home ASID 0005
| Exit start 03/28/2016 17:21:17.675336
| Exit end 03/28/2016 17:21:17.675349
| Exit time 00:00:00.000012
|
| Exit address 07557BF8
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.702847
| Exit end 03/28/2016 17:21:17.702904
| Exit time 00:00:00.000056
| Exit attributes: Global, Sdump, SYSMDUMP
|
| Exit address 031C87B8
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.702904
| Exit end 03/28/2016 17:21:17.703101
| Exit time 00:00:00.000197
| Exit attributes: Global, Sdump
|
| Exit address 0701E000
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.703101
| Exit end 03/28/2016 17:21:17.704004
| Exit time 00:00:00.000902
| Exit attributes: Global, Sdump, SYSMDUMP
|
| Exit address 0192FD30
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.704004
| Exit end 03/28/2016 17:21:17.705021
| Exit time 00:00:00.001016
| Exit attributes: Global, Sdump, Nucleus Resident
|
| Exit address 05548000
| Home ASID 0005
| Exit start 03/28/2016 17:21:17.705021
| Exit end 03/28/2016 17:21:17.705045
| Exit time 00:00:00.000024
| Exit attributes: Global, Sdump, SYSMDUMP
|
| Exit address 06D62128
| Home ASID 0001
| Exit start 03/28/2016 17:21:17.722738
| Exit end 03/28/2016 17:21:17.722804
| Exit time 00:00:00.000065
| Exit attributes: Local, Sdump, DFP
| Exit address 06F6E5A0
| Home ASID 0001
| Exit start 03/28/2016 17:21:17.722804
| Exit end 03/28/2016 17:21:17.722826
| Exit time 00:00:00.000022
| Exit attributes: Local, Sdump, SYSMDUMP
|
| Exit address 0192EAD8
| Home ASID 0001
| Exit start 03/28/2016 17:21:17.722826
| Exit end 03/28/2016 17:21:17.724572
| Exit time 00:00:00.001745
| Exit attributes: Local, Sdump, Nucleus Resident
|
| Exit address 0701E028
| Home ASID 0001
| Exit start 03/28/2016 17:21:17.724601
| Exit end 03/28/2016 17:21:17.724608
| Exit time 00:00:00.000007
| Exit attributes: Sdump, SYSMDUMP, One Time

Chapter 5. IPCS subcommands 337

 VERBEXIT IEAVTSFS subcommand

| Exit address 05549078

| Home ASID 0001
| Exit start 03/28/2016 17:21:17.724609
| Exit end 03/28/2016 17:21:17.724624
| Exit time 00:00:00.000015
| Exit attributes: Sdump, SYSMDUMP, One Time
| v Example 2: Obtain the history of the SVC dump measurements and statistics:
| – Action
| VERBEXIT IEAVTSFS ’HISTORY’
| – Result
| SVC Dump Measurements and Statistics Report
|
| Option = History
| =============================================================
| Capture phase partial dump reason codes (IHASDRSN):
| Are all zeros.
|
| SMB Number 1
| Dump Number 1
| Dump start 03/28/2016 13:44:04.015638
| Dump end 03/28/2016 13:44:04.139764
| Total dump capture time 00:00:00.124125
|
| Snap trace start 03/28/2016 13:44:04.015774
| Snap trace end 03/28/2016 13:44:04.019963
| Elapsed time 00:00:00.004189
| Total dump capture time 00:00:00.124125
|
| Snap trace start 03/28/2016 13:44:04.01577
| Snap trace end 03/28/2016 13:44:04.01996
| Elapsed time 00:00:00.004189
|
|
| System nondispatchability start 03/28/2016 13:44:04.02081
| System set nondispatchable 03/28/2016 13:44:04.02084
| Time to become nondispatchable 00:00:00.000022
|
| Global storage start 03/28/2016 13:44:04.02002
| Global storage end 03/28/2016 13:44:04.07857
| Global storage capture time 00:00:00.058555
|
| Defers for frame availability 0
| Pages requiring input I/O 33
| Source page copied to target 4759
| Source frames re-assigned 34
| Global storage end 03/28/2016 13:44:04.078576
| Global storage capture time 00:00:00.058555
|
| Defers for frame availability 0
| Pages requiring input I/O 33
| Source page copied to target 4759
| Source frames re-assigned 34
| Source AUX slot IDs re-assigned 0
| System reset dispatchable 03/28/2016 13:44:04.088641
| System was nondispatchable 00:00:00.067823
|
| Asid 0001:
| Local storage start 03/28/2016 13:44:04.078635
| Local storage end 03/28/2016 13:44:04.139494
| Local storage capture time 00:00:00.060859
| Tasks reset dispatchable 03/28/2016 13:44:04.139561
| Tasks were nondispatchable 00:00:00.060926
|
| Defers for frame availability 0
| Pages requiring input I/O 0

338 z/OS MVS IPCS Commands

 VERBEXIT IEAVTSFS subcommand

| Local storage end 03/28/2016 13:44:04.139494

| Local storage capture time 00:00:00.060859
| Tasks reset dispatchable 03/28/2016 13:44:04.139561
| Tasks were nondispatchable 00:00:00.060926
|
| Defers for frame availability 0
| Pages requiring input I/O 0
| Source page copied to target 2688
| Source frames re-assigned 0
| Source AUX slot IDs re-assigned 0
| Dump Exits
| Exit address 06A096D0
| Home ASID 0005
| Exit start 03/28/2016 13:44:04.026957
| Exit end 03/28/2016 13:44:04.027718
| Exit time 00:00:00.000761
| Exit attributes: Sdump, Early Global
|
| Defers for frame availability 0
| Pages requiring input I/O 0
| Exit attributes: Sdump, Early Global
|
| Defers for frame availability 0
| Pages requiring input I/O 0
| Source page copied to target 129
| Source frames re-assigned 0
| Source AUX slot IDs re-assigned 0
| Exit address 0749FB10
| Home ASID 0005
| Exit start 03/28/2016 13:44:04.027723
| Exit end 03/28/2016 13:44:04.028426
| Exit time 00:00:00.000703
| Exit attributes: Sdump, SYSMDUMP, Early Global
|
| Exit module / Exit name CEAMDMPX / IEASDUMP.SERVER
| Home ASID 0005
| Exit start 03/28/2016 13:44:04.028432
| Exit end 03/28/2016 13:44:04.029667
| Exit time 00:00:00.001235
| Exit address 0749FB10
| Home ASID 0005
| Exit start 03/28/2016 13:44:04.027723
| Exit end 03/28/2016 13:44:04.028426
| Exit time 00:00:00.000703
| Exit attributes: Sdump, SYSMDUMP, Early Global
|
| Exit module / Exit name CEAMDMPX / IEASDUMP.SERVER
| Home ASID 0005
| Exit start 03/28/2016 13:44:04.028432
| Exit end 03/28/2016 13:44:04.029667
| Exit time 00:00:00.001235
|
| Exit module / Exit name CNZM1SSX / IEASDUMP.SERVER
| Home ASID 0005
| Exit start 03/28/2016 13:44:04.029667
| Exit end 03/28/2016 13:44:04.029738
| Exit time 00:00:00.000071
|
| Exit module / Exit name IGG0CLSD / IEASDUMP.SERVER
| ----------------------
| ----------------------
| ----------------------
| Home ASID 0001
| Exit start 03/28/2016 13:44:04.139598
| Exit end 03/28/2016 13:44:04.139675
| Exit time 00:00:00.000077
| Exit attributes: Sdump, SYSMDUMP, One Time

Chapter 5. IPCS subcommands 339

 VERBEXIT IEAVTSFS subcommand

|
| Exit address 05549078
| Home ASID 0001
| Exit start 03/28/2016 13:44:04.139680
| Exit end 03/28/2016 13:44:04.139753
| Exit time 00:00:00.000073
| Exit attributes: Sdump, SYSMDUMP, One Time
|
| =============================================================
| Capture phase partial dump reason codes (IHASDRSN):
| Are all zeros.
|
| SMB Number 2
| Dump Number 2
| Dump start 03/28/2016 16:54:06.280338
| Dump end 03/28/2016 16:54:06.314874
| Total dump capture time 00:00:00.034535
|
| Snap trace time is unavailable.
|
| System was not set nondispatchable
|
| Global storage start 03/28/2016 16:54:06.280573
| Global storage end 03/28/2016 16:54:06.294719
| Global storage capture time 00:00:00.014145
|
| Defers for frame availability 0
| Pages requiring input I/O 0
| Source page copied to target 2236
| Source frames re-assigned 0
|
| ................................
| ................................
| ................................

VERBEXIT IEFENFVX subcommand — list ENF listeners

Specify the IEFENFVX verb name on the VERBEXIT subcommand to format a list
of Event Notification Facility (ENF) listeners.
v Parameters
The VERBEXIT IEFENFVX subcommand has one optional parameter: an ENF
event code.
v Examples:
– To obtain a list of ENF listeners for all the event codes:
VERBEXIT IEFENFVX
– To obtain a list of ENF listeners for an event code 4:
VERBEXIT IEFENFVX ’4’

VERBEXIT IEFIVAWT subcommand — list pending XCF work for tape

allocation
Specify the IEFIVAWT verb name on the VERBEXIT subcommand to format a list
of pending XCF work for tape allocation.
v Parameters
The VERBEXIT IEFIVAWT subcommand has no parameters.
v Example: Obtain a list of pending XCF work for tape allocation.
– Action
VERBEXIT IEFIVAWT

340 z/OS MVS IPCS Commands

 VERBEXIT IEFIVAWT subcommand

– Result

IEFHTSWT AWTR Request Queue

IEFOAWTR: 7E721540
ID....=... Version.. 0001 Length... 0055
Next...00000000 FuncVal.. 0004 Flags....0000
Function: Merge
SendMemT.E5010000 007FFBF8 MsgBufA.. 00B67618
MsgBufl.. 982F3CAC MsgBufSP .20 MsgBufKy. 00
MsgBufT.. 010B0002
MhETOD... C7D9E2F1 F2F14040 00000000 00000001

VERBEXIT IEFIVIGD subcommand — list global tape device

information
Specify the IEFIVIGD verb name on the VERBEXIT subcommand to format the
global tape devices.
v Parameters
The VERBEXIT IEFIVIGD subcommand has no parameters.
v Example: Obtain information about global tape devices from the dump.
– Action
VERBEXIT IEFIVIGD
– Result

Chapter 5. IPCS subcommands 341

VERBEXIT JESXCF subcommand

TSRA IGDE Hash Table

Hash Value 0141

IEFZIGDE: 7EC57288
ID....IGDE Version.. 01 Length... 04D8
GILen... 0060 SIELen... 0020
HashVal.. 00000140 UCBAddr.. 7FFFFBAD DevNum... 0000
UHashVal.. 00
DevType.. ... EpiValue.00000000 EnqASID.. 0000
EnqTCB... 00000000
MinorNam.D5C5C440 F0F0F3F4 F9F0C2F4 F0E5E2E2 C7C1E5F3
F4F9F0C1 E3E2C2F5 F7F10000 40404040
UpdtETOD. 00000000 00000000 00000000 00000001
AllSysID. 00
AllASID.. 0000 AllSysmn. ...... AllJobN.. .......
Device supports self-description.
CurVol... .... LastVol.. .... FileSeqN. 0000

System Interest Entry 02

DevNum... B571 DevType.. 349S
UpdtETOD. 00B6A244 D554198F 07080000 00010002
Hash Value 01D5

IEFZIGDE: 7EC4D2B0
ID....IGDE Version.. 01 Length... 04D8
GILen... 0060 SIELen... 0020
HashVal.. 000001D5 UCBAddr.. 021B2420 DevNum... 05A9
UHashVal.. A9
Device is online AS on this system.
DevType.. 3480 EpiValue. F3F4F8F0 EnqASID.. 0000
EnqTCB... 00000000
MinorNam.C4C5E540 F0F5C1F9 40404040 40404040 40404040
40404040 40404040 40404040 40404040
UpdtETOD. 00B6A247 FCC981AC 01080000 00010001
AllSysID. 00
AllASID.. 0000 AllSysmn. ...... AllJobN.. .......
Device supports self-description.
CurVol... .... LastVol.. .... FileSeqN. 0000

System Interest Entry 00

DevNum... 05A9 DevType.. 348S
UpdtETOD. 00B6A245 1DEFDE79 02080000 00010001

System Interest Entry 02

DevNum... 0589 DevType.. 348S
UpdtETOD. 00B6A244 D5475DD7 07080000 00010002

VERBEXIT JESXCF subcommand — format data for JES XCF

component
Specify the JESXCF verb name on the VERBEXIT subcommand to format coupling
and consoles information from the JESXCF address space in the dump. This
address space is for the JES common coupling services MVS component (JES XCF
component).
v Parameters
The VERBEXIT JESXCF subcommand has no parameters.
v Example: The VERBEXIT JESXCF output may be requested by the IBM Support
Center for diagnosis.

VERBEXIT LEDATA subcommand — format Language Environment

data
There is one version of the LEDATA subcommand for AMODE 31/24 format, and
another for AMODE 64 format. For the latest version of each IPCS LEDATA
subcommand, see the following topics:

342 z/OS MVS IPCS Commands

 VERBEXIT LEDATA subcommand

v For AMODE 31/24 format, see the topics about Formatting and analyzing
system dumps and Understanding Language Environment IPCS VERBEXIT
LEDATA AMODE 31/24 in z/OS Language Environment Debugging Guide.
v For AMODE 64 format, see the topics about Formatting and analyzing system
dumps and Understanding Language Environment IPCS VERBEXIT LEDATA
AMODE 64 in z/OS Language Environment Debugging Guide.

Specify the LEDATA verb name and optional parameters on the VERBEXIT
subcommand to format diagnostic data for the Language Environment component
of z/OS. LEDATA displays the following:
v A summary of the Language Environment at the time of the dump
v Runtime options
v Storage management control blocks
v Condition management control blocks
v Message handler control blocks
v C Runtime Library control blocks
v Syntax

VERBEXIT LEDATA [ ’parameter [,parameter]...’ ]

The parameters are:

Report type parameters:

[SUMMARY]
[HEAP | STACK | SM]
[HPT(value)]
[CM]
[MH]
[CEEDUMP]
[COMP(value)]
[PTBL(value)]
[ALL]

Data selection parameters:

[DETAIL | EXCEPTION]

Control block selection parameters:

[CAA(caa-address)]
[DSA(dsa-address)]
[TCB(tcb-address)]
[ASID(address-space-ID)]
[NTHREADS(value)]

v Report Type Parameters

Use these parameters to select the type of report. You can specify as many
reports as you want. If you omit the parameters, the default is SUMMARY.
SUMmary
Specifies a summary of the Language Environment at the time of the dump.
The following information is included:
– TCB address
– Address space identifier
– Language Environment release
– Active members
– Formatted CAA, PCB, RCB, EDB, and PMCB

Chapter 5. IPCS subcommands 343

VERBEXIT LEDATA subcommand

– Runtime options in effect.

HEAP | STACK | SM
HEAP
Specifies a report on Storage Management control blocks pertaining to
HEAP storage.
STACK
Specifies a report on Storage Management control blocks pertaining to
STACK storage.
SM Specifies a report on Storage Management control blocks. This is the
same as specifying both HEAP and STACK.
HPT(value)
Specifies the heappools trace (if available) be formatted. If the value is 0 or *,
the trace for every heappools poolid is formatted. If the value is a single
number (1-12), the trace for the specific heappools poolid is formatted. If the
HPT keyword is specified with no value, the HPT value defaults to 0.
CM Specifies a report on Condition Management control blocks.
MH Specifies a report on Message Handler control blocks.
CEEdump
Specifies a CEEDUMP-like report. Currently this includes the traceback, the
Language Environment trace, and thread synchronization control blocks at
process, enclave, and thread levels.
COMP(value)
Specifies component control blocks to be formatted, where value is one of the
following options:
C Specifies a report on C/C++ Run-Time Control Blocks.
CIO
Specifies a report on C/C++ I/O Control Blocks.
COBOL
Specifies a report on COBOL-specific Control Blocks.
PLI
Specifies a report on PL/I-specific Control Blocks.
ALL
Request a report on all the control blocks. If the value specified in
COMP is not valid, the COMP value defaults to ALL.

Note: When LEDATA report type ALL is specified, the COMP value defaults
to ALL.
PTBL(value)
Specifies the PreInit tables to be formatted, where value is one of the
following options:
CURRENT
The PreInit table associated with the current or specified TCB is
displayed.Note that when report type ALL is specified, the PTBL value
defaults to CURRENT.
address
The PreInit table at the specified address is displayed.

344 z/OS MVS IPCS Commands

 VERBEXIT LEDATA subcommand

* All active and dormant PreInit tables within the current address space
are displayed. This option is time consuming.
ACTIVE
The PreInit tables of all TCBs in the address space are displayed.
ALL
Specifies all above reports, in addition to a report on C Runtime Library.
v Data Selection Parameters
Use these parameters to limit the scope of the data in the report. If no data
selection parameter is selected, the default is DETAIL.
DETAIL
Specifies the formatting of all control blocks for the selected components.
Only significant fields in each control block are formatted.
EXCEPTION
Specifies validating all control blocks for the selected components. The
output produced names only the control block and its address for the first
control block in a chain that is not valid. Validation consists of control block
header verification at the very least.

Note: For the Summary, CEEDUMP, and C Runtime Library reports, only
the DETAIL output is available.
v Control Block Selection Parameters
Use these parameters to select the CAA and DSA control blocks used as the
starting points for formatting.
CAA(caa-address)
Specifies the address of the CAA. If not specified, the CAA address is
obtained from the TCB.
DSA(dsa-address)
Specifies the address of the DSA. If not specified, the DSA address is
assumed to be the general purpose register (GPR) 13 value for the TCB.
TCB(tcb-address)
Specifies the address of the TCB. If not specified, the TCB address of the
current TCB from the CVT is used.
ASID(address-space-ID)
Specifies the hexadecimal address space ID. If not specified, the IPCS default
address space ID is used. This parameter is not needed when the dump only
has one address space.
NTHREADS(value)
Specifies the number of TCBs for which the traceback will be displayed. If
NTHREADS is not specified, value will default to (1). If value is specified as
asterisk (*), all TCBs will be displayed.
v Example: For an example of the LEDATA output, see z/OS Language Environment
Debugging Guide.

VERBEXIT LOGDATA subcommand — format logrec buffer records

Specify the LOGDATA verb name on the VERBEXIT subcommand to format the
logrec buffer records that were in storage when the dump was generated.
LOGDATA locates the logrec records in the logrec recording buffer and invokes the
EREP program to format and print the logrec records. The records are formatted as
an EREP detail edit report.

Chapter 5. IPCS subcommands 345

VERBEXIT LOGDATA subcommand

Use the LOGDATA report to examine the system errors that occurred just before
the error that caused the dump to be requested.
v Parameters
The VERBEXIT LOGDATA subcommand has no parameters.
v Example: Format the logrec buffer records in the dump.
– Action
VERBEXIT LOGREC
– Result
DUMP FOR DATSVY02 1 11:12:04 11/29/94
______________________________________________________________________________

* * * * L O G D A T A * * * *
DUMP FOR DATSVY02 2 11:12:05 11/29/94
______________________________________________________________________________

TYPE: SOFTWARE RECORD REPORT: SOFTWARE EDIT REPORT DAY.YEAR

(SVC 13) REPORT DATE: 333.94
FORMATTED BY: IEAVTFDE HBB5520 ERROR DATE: 224.94
MODEL: 3090 HH:MM:SS.TH
SERIAL: 176280 TIME: 10:38:59.69

JOBNAME: *MASTER*
ERRORID: SEQ=00012 CPU=0041 ASID=0001 TIME=10:38:59.6

SEARCH ARGUMENT ABSTRACT

AB/S00F4 PRCS/00000024 REGS/0E00A REGS/0C8B2

SYMPTOM DESCRIPTION
------- -----------
AB/S00F4 SYSTEM ABEND CODE: 00F4
PRCS/00000024 ABEND REASON CODE: 00000024
REGS/0E00A REGISTER/PSW DIFFERENCE FOR R0E: 00A
REGS/0C8B2 REGISTER/PSW DIFFERENCE FOR R0C: 8B2
SERVICEABILITY INFORMATION NOT PROVIDED BY THE RECOVERY ROUTINE
PROGRAM ID
LOAD MODULE NAME
CSECT NAME
RECOVERY ROUTINE CSECT NAME
RECOVERY ROUTINE LABEL
DATE ASSEMBLED
MODULE LEVEL
SUBFUNCTION
TIME OF ERROR INFORMATION
PSW: 075C1000 8251832E INSTRUCTION LENGTH: 02 INTERRUPT CODE: 000D
FAILING INSTRUCTION TEXT: CCB418F6 0A0D4110 CC2C45E0
REGISTERS 0-7
GR: 6204000C 440F4000 00000000 7F70C658 00FCF420 6204000C 00000024 00FD1CD0
AR: 015209B8 00000000 00000000 00000000 00000000 00000000 00000000 00000000
REGISTERS 8-15
GR: 00000000 7F70C4C8 00FCF3EC 02518A7B 82517A7C 7F70C6A8 82518324 00000024
AR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
HOME ASID: 0001 PRIMARY ASID: 0001 SECONDARY ASID: 0001
PKM: 8000 AX: 0001 EAX: 0000
RTM WAS ENTERED BECAUSE AN SVC WAS ISSUED IN AN IMPROPER MODE.
THE ERROR OCCURRED WHILE AN ENABLED RB WAS IN CONTROL.
NO LOCKS WERE HELD.
NO SUPER BITS WERE SET.
RECOVERY ENVIRONMENT
RECOVERY ROUTINE TYPE: FUNCTIONAL RECOVERY ROUTINE (FRR)
PSW AT ENTRY TO FRR: 070C0000 82098DD0
FRR PARAMETER AREA ON ENTRY TO FRR:
+00 C9C7E6C6 C5C6D740 7F70B028 7F70B250 00000000 00000000
RECOVERY ROUTINE ACTION
THE RECOVERY ROUTINE RETRIED TO ADDRESS 8209C8E0.
AN SVC DUMP WAS NOT REQUESTED.
NO LOCKS WERE REQUESTED TO BE FREED.
THE SDWA WAS REQUESTED TO BE FREED BEFORE RETRY.
THE REGISTER VALUES TO BE USED FOR RETRY:
REGISTERS 0-7
GR: 1E050019 7F70C4BC 00000000 7F70C658 7F70B250 7F70B0A8 7F70C858 7F70C830

346 z/OS MVS IPCS Commands

 VERBEXIT LOGDATA subcommand

AR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

REGISTERS 8-15
GR: 006E5F1C 020C1598 00000001 02518A7B 82517A7C 7F70C6A8 7F70B478 8251AB48
AR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
HEXADECIMAL DUMP

HEADER
+000 40831820 00000000 0094224F 10385969 | C.......M.|....|
+010 FF176280 30900000 |........ |

JOBNAME
+000 5CD4C1E2 E3C5D95C |*MASTER* |

SDWA BASE
+000 00000C60 440F4000 00000000 00000000 |...-.. .........|
+010 00000000 00000000 6204000C 440F4000 |.............. .|
+020 00000000 7F70C658 00FCF420 6204000C |....".F...4.....|
+030 00000024 00FD1CD0 00000000 7F70C4C8 |.......}....".DH|
+040 00FCF3EC 02518A7B 82517A7C 7F70C6A8 |..3....#B.:@".FY|
+050 82518324 00000024 00000000 00000000 |B.C.............|
+060 00000000 00000000 075C1000 8251832E |.........*..B.C.|
+070 0002000D 03C96001 070C0000 82098DD0 |.....I-.....B..}|
+080 0002000D 03C96001 1E050019 7F70C4BC |.....I-.....".D.|
+090 00000000 7F70C658 7F70B250 7F70B0A8 |....".F."..&"..Y|
+0A0 7F70C858 7F70C830 006E5F1C 020C1598 |".H.".H..>^....Q|
+0B0 00000001 02518A7B 82517A7C 7F70C6A8 |.......#B.:@".FY|
+0C0 7F70B478 8251AB48 00000000 00000000 |"...B...........|
+0D0 00000000 00000000 00000000 00000000 |................|
+0E0 00000000 00000000 04040001 00000041 |................|
+0F0 8209C8E0 00F93AFC 00000000 048C0000 |B.H\.9..........|
+100 00000000 00000000 00000000 00000000 |................|
+110 00000000 00000000 00000000 00000000 |................|
+120 0001000C 00000000 00000000 00000000 |................|
+130 00000000 00000000 00000000 00F93AA8 |.............9.Y|
+140 00000000 00000000 00000000 00000000 |................|
+150 00000000 00000000 00000000 00000000 |................|
+160 00000000 00000000 00000000 FFFF0006 |................|
+170 00F93DF8 80000001 00010001 00000000 |.9.8............|
+180 00000000 00000000 00000000 0005D9A4 |..............RU|
+190 00FF0000 |.... |
NO DATA EXISTS IN THE VARIABLE RECORDING AREA
SDWA FIRST RECORDABLE EXTENSION (SDWARC1)
+000 00000000 00000000 00000000 00000000 |................|
+010 00000000 00000000 00000000 00000000 |................|
+020 00000000 00000000 00000000 00000024 |................|
DUMP FOR DATSVY02 3 11:12:05 11/29/94
______________________________________________________________________________
+030 00000000 00000000 00000000 00000001 |................|
+040 00000000 00000000 00000000 82098DD0 |............B..}|
+050 C9C7E6C6 C5C6D740 7F70B028 7F70B250 |IGWFEFP "..."..&|
+060 00000000 00000000 00000000 00000000 |................|
+070 00000000 00000001 006EBB20 CCB418F6 |.........>.....6|
+080 0A0D4110 CC2C45E0 00FCFF00 01FFE07F |.......\......\"|
+090 440F4000 00000024 5EB1EE40 01FFE07F |.. .....;.. ..\"|
+0A0 00786180 80000001 00010001 01756040 |../...........- |
+0B0 FE000000 01FFE07F 00000000 00000000 |......\"........|
+0C0 00000000 00000000 010E1233 01FFE07F |..............\"|
+0D0 DF881755 7F6A7158 015209B8 00000000 |.H.."...........|
+0E0 00000000 00000000 00000000 00000000 |................|
+0F0 00000000 00000000 00000000 00000000 |................|
+100 00000000 00000000 00000000 00000000 |................|
+110 00000000 00000000 00000000 00000000 |................|
+120 00000000 00000000 00000000 00000000 |................|
+130 00000000 00000000 00000000 00000000 |................|
+140 00000000 00000000 00000000 00000000 |................|
+150 00000000 00000000 01756040 00000000 |..........- ....|
+160 00000000 00000000 0175E680 00000000 |..........W.....|
+170 00000000 00000000 00000000 00000000 |................|
+180 00000000 00000000 00000000 00000000 |................|
+190 00000000 00000000 00000000 00000000 |................|
+1A0 00000000 7F6A7158 00000000 00000000 |...."...........|
+1B0 00000000 00000000 00000000 00000000 |................|
+1C0 00000000 00000000 |........ |
SDWA SECOND RECORDABLE EXTENSION (SDWARC2)
+000 00000000 00000000 00000000 00000000 |................|

Chapter 5. IPCS subcommands 347

VERBEXIT LOGDATA subcommand

SDWA THIRD RECORDABLE EXTENSION (SDWARC3)

+000 00000000 00000000 00000000 00000000 |................|
+010 00000000 00000000 00000000 00000000 |................|
ERRORID
+000 000C0041 00010005 D9A4 |........RU |

IEA24050I LOGDATA processing completed successfully.

VERBEXIT MMSDATA subcommand — format MVS message service

data
Specify the MMSDATA verb name on the VERBEXIT subcommand to format
diagnostic data from the MVS message service (MMS).
v Parameters
The VERBEXIT MMSDATA subcommand has no parameters.
v Example: For an example of the MMSDATA output, see the MMS component in
z/OS MVS Diagnosis: Reference.

VERBEXIT MTRACE subcommand — format master trace entries

Specify the MTRACE verb name on the VERBEXIT subcommand to display:
v The master trace table entries for the dumped system. This table is a
wraparound data area that holds the most recently issued console messages in a
first-in, first-out order.
v The NIP hard-copy message buffer.
v The branch entry and NIP time messages on the delayed issue queue.
v Parameters
The VERBEXIT MTRACE subcommand has no parameters.
v Example: Format master trace table entries in the dump.
– Action
VERBEXIT MTRACE
– Result

348 z/OS MVS IPCS Commands

 VERBEXIT MTRACE subcommand

*** NIP MESSAGE TABLE ***

UNABLE TO ACCESS UCM - NIP MESSAGE TRACE TERMINATED

*** MASTER TRACE TABLE ***

TAG IMM DATA |--------------------------------------------- MESSAGE DATA --------------------------------------------|

0001 00999BF8 N 0000000 NONAME 88251 13:31:45.65 00000090 IEF196I SRB 0MIN 00.00SEC VIRT 476K SYS
88K EXT 12K SYS
0001 00999BF8 N 0000000 NONAME 88251 13:31:45.65 00000090 IEF196I 9176K
0001 00999BF8 N 0000000 NONAME 88251 13:31:45.66 00000090 IEF196I IEF375I JOB /LLA / START 88251.1331
0001 00999BF8 N 0000000 NONAME 88251 13:31:45.67 00000090 IEF196I IEF376I JOB /LLA / STOP 88251.1331
CPU 0MIN 00.08SEC
0001 0099C478 N 0000000 NONAME 88251 13:31:45.67 00000090 IEF196I SRB 0MIN 00.00SEC
0001 0099C478 N 0000000 NONAME 88251 13:31:45.67 00000090 IEF196I IEF358I INITIATOR TERMINATED DUE TO
OUTSTANDING CROSS MEMORY
0001 0099C478 N 0000000 NONAME 88251 13:31:45.68 00000090 IEF196I BIND.
0001 00999BF8 N 4020000 NONAME 88251 13:31:45.67 00000090 IEF358I INITIATOR TERMINATED DUE TO OUTSTANDING
CROSS MEMORY BIND.
0001 0099C478 N 0000000 NONAME 88251 13:31:45.71 00000090 IEA989I SLIP TRAP ID=X33E MATCHED
0001 0099C478 N 8040000 NONAME 88251 13:31:45.83 00000090 *CSV218E LIBRARY LOOKASIDE CRITICAL FAILURE
(ABEND=SFF0 U000, REASON=--NONE--)
0001 00999BF8 NC0000000 NONAME 88251 13:45:19.66 04 00000090 S LLA,SUB=MSTR
0001 00999BF8 N 0000000 NONAME 88251 13:45:20.36 00000090 IEF196I 1 //LLA JOB MSGLEVEL=1
0001 00999BF8 N 0000000 NONAME 88251 13:45:20.37 00000090 IEF196I 2 //STARTING EXEC LLA
0001 00999BF8 N 0000000 NONAME 88251 13:45:20.42 00000090 IEF196I 3 XXLLA PROC LLA=
0001 00999BF8 N 0000000 NONAME 88251 13:45:20.42 00000090 IEF196I 4 XXLLA EXEC PGM=CSVLLCRE,
PARM=’LLA=&LLA’
0001 00999BF8 N 0000000 NONAME 88251 13:45:20.42 00000090 IEF196I IEF653I SUBSTITUTION JCL -
PGM=CSVLLCRE,PARM=’LLA=’
0001 0099C478 N 0000000 NONAME 88251 13:45:20.89 00000090 IEF196I IEF236I ALLOC. FOR LLA LLA
0001 0099C478 M 4000000 NONAME 88251 13:45:24.32 00000090 *IEA911E COMPLETE DUMP ON SYS1.DUMP06
0001 00999BF8 D 837 00000090 FOR ASID (0017)
0001 00999C58 E 837 00000090 ERROR ID = SEQ00039 CPU00 ASID0017
TIME13.45.20.9
0001 00998530 N 4000000 NONAME 88251 13:45:24.32 00000090 IEA994E ALL SYS1.DUMP DATA SETS ARE FULL
0001 0099C844 N 0000000 NONAME 88251 13:45:24.35 00000090 IEF196I IEA995I SYMPTOM DUMP OUTPUT
0001 0099A390 N 0000000 NONAME 88251 13:45:24.35 00000090 IEF196I SYSTEM COMPLETION CODE=FF0
0001 0099A390 N 0000000 NONAME 88251 13:45:24.36 00000090 IEF196I TIME=13.45.20 SEQ=00039 CPU=0000
ASID=0017
0001 0099A390 N 0000000 NONAME 88251 13:45:24.36 00000090 IEF196I PSW AT TIME OF ERROR 070C1000
80FE5CFC ILC 2 INTC 0D
0001 0099C844 N 0000000 NONAME 88251 13:45:24.36 00000090 IEF196I NO ACTIVE MODULE FOUND
0001 0099C844 N 0000000 NONAME 88251 13:45:24.36 00000090 IEF196I DATA AT PSW 00FE5CF6 - 00181610
0A0D4110 016D182F
0001 0099A390 N 0000000 NONAME 88251 13:45:24.36 00000090 IEF196I GPR 0-3 80000000 80FF0000
009FF5A0 00FC4E88
0001 0099A390 N 0000000 NONAME 88251 13:45:24.36 00000090 IEF196I GPR 4-7 009F8E88 009FD358
80FE5CD6 00F40400
0001 0099C844 N 0000000 NONAME 88251 13:45:24.37 00000090 IEF196I GPR 8-11 00000000 80FE579C
009FD418 7FFFE2C0
0001 0099C844 N 0000000 NONAME 88251 13:45:24.37 00000090 IEF196I GPR 12-15 7FFE0000 00006730
00FE6200 80014910
0001 0099C844 N 0000000 NONAME 88251 13:45:24.37 00000090 IEF196I END OF SYMPTOM DUMP
0001 0099C844 M 0020000 NONAME 88251 13:45:24.35 00000090 IEA995I SYMPTOM DUMP OUTPUT
0001 0099A390 D 850 00000090 SYSTEM COMPLETION CODE=FF0
0001 0099A3F0 D 850 00000090 TIME=13.45.20 SEQ=00039 CPU=0000 ASID=0017
0001 0099CACC D 850 00000090 PSW AT TIME OF ERROR 070C1000 80FE5CFC ILC
2 INTC 0D
0001 0099CB2C D 850 00000090 NO ACTIVE MODULE FOUND
0001 00999E80 D 850 00000090 DATA AT PSW 00FE5CF6 - 00181610 0A0D4110
016D182F
0001 00999EE0 D 850 00000090 GPR 0-3 80000000 80FF0000 009FF5A0
00FC4E88

The VERBEXIT MTRACE continues with messages like those shown in the
preceding example.

VERBEXIT NUCMAP subcommand — map modules in the nucleus

Specify the NUCMAP verb name and optional parameters on the VERBEXIT
subcommand to format a map of the modules in the nucleus when the dump was
loaded. The map gives for each module the name, entry point, entry point
attributes, and length. When the input data set does not contain the nucleus, IPCS
issues an error message.

Chapter 5. IPCS subcommands 349

VERBEXIT NUCMAP subcommand

v Syntax

VERBEXIT NUCMAP [ ’parameter [,parameter]...’ ]

The parameters are:

[ EPA ]
[ MODNAME ]

v Parameters
If you omit the parameters, the output is sorted and listed twice: first, by the
module entry point addresses, and second, by the module names.
EPA
Sorts the output according to module entry point addresses.
MODNAME
Sorts the output according to module names.
v Example: Obtain a map of the modules in the nucleus.
– Action
VERBEXIT NUCMAP
– Result

350 z/OS MVS IPCS Commands

 VERBEXIT NUCMAP subcommand

* * * * N U C L E U S M A P * * * *

NUCLEUS MAP SORTED NUMERICALLY BY EPA

NAME LOCATION ATTR LENGTH CSECT-NAME NAME LOCATION ATTR LENGTH CSECT-NAME

IEAVFX00 00000000 10 001000 IEATSELM 00FC55C0 00 00014C IEATPC

IEATCBP 00000218 00 000DE8 IEAVFX00 IEFQMWR 00FC5710 10 000038
IECVDDT4 00F4A000 10 000048 IEFENFDM 00FC5748 11 000030
IECVPRNT 00F4A048 12 000438 IEABEND 00FC5778 10 0000D0
PRTDSE 00F4A04E 02 000432 IECVPRNT IEAPATCH 00FC5848 10 0000D5
PRTSIO 00F4A054 02 00042C IECVPRNT IEAIHASU 00FC5910 00 00000D IEAPATCH
PRTEOS 00F4A05A 02 000426 IECVPRNT IEFJESCT 00FC5920 10 000080
PRTTRAP 00F4A060 02 000420 IECVPRNT IFDOLT0A 00FC59A0 10 00004C
PRTDDT 00F4A066 02 00041A IECVPRNT IEASMFEX 00FC59F0 13 000370
DDT1403 00F4A1F4 02 00028C IECVPRNT IEAVESVT 00FC5D80 10 000258
DDT3203 00F4A228 02 000258 IECVPRNT IEAGSMQ 00FC5DA0 00 000238 IEAVESVT
DDT3211 00F4A264 02 00021C IECVPRNT IEAGSPL 00FC5DA4 00 000234 IEAVESVT
DDT3800 00F4A2A0 02 0001E0 IECVPRNT IEALSMQ 00FC5DA8 00 000230 IEAVESVT
DDT4248 00F4A2E8 02 000198 IECVPRNT ICYMMVT 00FC5FD8 10 000458
PRTCCW 00F4A324 02 00015C IECVPRNT ICYMMVTC 00FC604C 00 0003E4 ICYMMVT
IECVDDTR 00F4A480 10 00022C ICYPATCH 00FC60B8 00 000378 ICYMMVT
DDTR3480 00F4A4F4 00 0001B8 IECVDDTR ICYIOSB 00FC61B8 00 000278 ICYMMVT
DDTR342C 00F4A534 00 000178 IECVDDTR ICYMMSV1 00FC6230 00 000200 ICYMMVT
DDTR3400 00F4A570 00 00013C IECVDDTR ICYMMPT1 00FC6330 00 000100 ICYMMVT
TAPECCW 00F4A5AC 00 000100 IECVDDTR IECVAFP1 00FC6430 12 000230
IECVDDTP 00F4A6B0 10 000048 AFPSIO 00FC6490 02 0001D0 IECVAFP1
IGGDDT01 00F4A6F8 10 0001F2 AFPTRAP 00FC6496 02 0001CA IECVAFP1
IGGDDTA1 00F4A734 00 0001B6 IGGDDT01 AFPDDT 00FC649C 02 0001C4 IECVAFP1
IGGDDT02 00F4A778 00 000172 IGGDDT01 DDTAFP1 00FC650C 02 000154 IECVAFP1
IGGDDT04 00F4A7AC 00 00013E IGGDDT01 AFPCCW1 00FC6554 02 00010C IECVAFP1
IGGDDTA4 00F4A7E8 00 000102 IGGDDT01 DDTAFP22 00FC6660 10 00004E
IGGDDT05 00F4A82C 00 0000BE IGGDDT01 VSIMFLIH 00FC66B0 10 00041A
IGGDDT30 00F4A860 00 00008A IGGDDT01 VSFLIH 00FC66B0 00 00041A VSIMFLIH
IGGDDT3V 00F4A894 00 000056 IGGDDT01 VSIMRTRN 00FC68A6 00 000224 VSIMFLIH
IECDPERF 00F4A8F0 10 0000D2 IEAVBK00 00FC6AD0 10 000044
IECDPC01 00F4A8F0 00 0000D2 IECDPERF IEFLINK 00FC6AD4 00 000040 IEAVBK00
IECDPC02 00F4A900 00 0000C2 IECDPERF LINKDCB 00FC6AD4 00 000040 IEAVBK00
IECDPC03 00F4A910 00 0000B2 IECDPERF IEASVDCB 00FC6ADC 00 000038 IEAVBK00
IECDPC04 00F4A920 00 0000A2 IECDPERF SVCDCB 00FC6ADC 00 000038 IEAVBK00
IECDPC05 00F4A930 00 000092 IECDPERF IEAQLPAQ 00FC6B10 00 000004 IEAVBK00
IECDPC06 00F4A940 00 000082 IECDPERF VSIM 00FC6B18 10 00FAC2
IECVDDT5 00F4A9C8 10 000048 VSIMGPRS 00FC7400 00 00F1DA VSIM
IECVDDT7 00F4AA10 10 000048 VSIMFPRS 00FC7440 00 00F19A VSIM
IECVOPTB 00F4AA58 10 000118 VMSKMODE 00FC7490 00 00F14A VSIM
IECVDDTE 00F4AB70 10 000048 SS 00FC7494 00 00F146 VSIM
IECVDDT2 00F4ABB8 10 000048 PS 00FC7498 00 00F142 VSIM
IECZDTAB 00F4AC00 10 0000B0 VCT 00FC749C 00 00F13E VSIM
IOSUCB 00F4ACB0 10 07A0C0 VIX 00FC74A0 00 00F13A VSIM
IOSDCQ 00FC4D70 10 0000D8 VIU 00FC74A4 00 00F136 VSIM
IEAVCVT 00FC4E48 10 000620 VCBITS 00FC74A8 00 00F132 VSIM
IEACVT 00FC4E88 00 0005E0 IEAVCVT VMASK 00FC74AC 00 00F12E VSIM
IEFAUSDM 00FC5468 10 000028 VIPSW 00FC752C 00 00F0AE VSIM
IEEMSER 00FC5490 10 0000D4 VSIMCC 00FC7530 00 00F0AA VSIM
BAIPL 00FC549C 00 0000C8 IEEMSER PSCOUNT 00FC7534 00 00F0A6 VSIM
IEAMSLNK 00FC54A0 00 0000C4 IEEMSER VINTCODE 00FC7538 00 00F0A2 VSIM
IEATPC 00FC5568 10 0001A4 VSIMVECT 00FC8E18 00 00D7C2 VSIM
TPCMFTQE 00FC55A8 00 000164 IEATPC V00 00FC8E18 00 00D7C2 VSIM
V01 00FC9618 00 00CFC2 VSIM IGC045 00FDAA60 00 0000A4 IGC037
V02 00FC9E18 00 00C7C2 VSIM IEAMSWCB 00FDAB80 10 0015E0
V03 00FCA618 00 00BFC2 VSIM IEASTKH 00FDABA0 00 0015C0 IEAMSWCB
V04 00FCAE18 00 00B7C2 VSIM IEALSPC 00FDABB8 00 0015A8 IEAMSWCB
V05 00FCB618 00 00AFC2 VSIM IEAISSAT 00FDABC8 00 001598 IEAMSWCB
V06 00FCBE18 00 00A7C2 VSIM IEAMASCB 00FDAC00 00 001560 IEAMSWCB
V07 00FCC618 00 009FC2 VSIM IEAMSTCB 00FDAFA0 00 0011C0 IEAMSWCB
V08 00FCCE18 00 0097C2 VSIM IEAMPRB 00FDB260 00 000F00 IEAMSWCB
V09 00FCD618 00 008FC2 VSIM IEAMSIRB 00FDB360 00 000E00 IEAMSWCB
V10 00FCDE18 00 0087C2 VSIM IEAWASCB 00FDB538 00 000C28 IEAMSWCB
V11 00FCE618 00 007FC2 VSIM IEAWTCB 00FDB778 00 0009E8 IEAMSWCB

The nucleus map sorted numerically by entry point address (EPA) continues
with data like that shown in the preceding example.

Chapter 5. IPCS subcommands 351

VERBEXIT NUCMAP subcommand

* * * * N U C L E U S M A P * * * *

NUCLEUS MAP SORTED ALPHABETICALLY BY NAME

NAME LOCATION ATTR LENGTH CSECT-NAME NAME LOCATION ATTR LENGTH CSECT-NAME

ABN0000 011F012C 0E 000854 ISGJDI AVFFS 01157FC0 1E 000AD8

ACMSRALH 00FF41A0 0B 0004E0 IEAVELIT AVFFSFRR 01157FE0 0E 000AB8 AVFFS
ACRRETRY 01188FB4 0E 00049C IEAVTCR1 AVFIS 01158A98 1E 0008C8
ACRSTART 01187E16 0E 000D0A IEAVTACR AVFISRB 01158AB8 0E 0008A8 AVFIS
ACRSUPER 01188FAE 0E 0004A2 IEAVTCR1 AVFISXIT 01159008 0E 000358 AVFIS
ADISP 00FF3F00 0B 000780 IEAVELIT AVFIX 00FF43A4 0B 0002DC IEAVELIT
AFPCCW1 00FC6554 02 00010C IECVAFP1 AVFRM 01159360 1E 000930
AFPDDT 00FC649C 02 0001C4 IECVAFP1 AVFRMTRP 01159720 0E 000570 AVFRM
AFPSIO 00FC6490 02 0001D0 IECVAFP1 AVFRMTRT 01159380 0E 000910 AVFRM
AFPTRAP 00FC6496 02 0001CA IECVAFP1 AVFTB 01159C90 1E 0009E8
AHLHEAD 00FDC978 02 000048 AHLMCIH AVFTBACK 01159CB0 0E 0009C8 AVFTB
AHLMCIH 00FDC710 12 0002B0 AVFTBRTY 0115A452 0E 000226 AVFTB
AHLMCIHB 00FDC8B6 02 00010A AHLMCIH AVFTC 0115A678 1E 000550
AHLSTCLS 00FDC94E 02 000072 AHLMCIH AVFTCLPE 0115A7D8 0E 0003F0 AVFTC
AHLVCCR8 00FDC94E 02 000072 AHLMCIH AVFTCLPM 0115A698 0E 000530 AVFTC
AOMAFRR 010982C8 1E 000818 AVFTD 0115ABC8 1E 000900
AOMAIO 01097C18 1E 0006B0 AVFTDCPB 0115ABE8 0E 0008E0 AVFTD
AOMARQ 010955D0 1E 0009C8 AVFTDCPS 0115B020 0E 0004A8 AVFTD
AOMARQ2 0109593A 0E 00065E AOMARQ AVFTE 0115B4C8 1E 000C70
AOMATTN 01095F98 1E 0011E0 AVFTERTY 0115BDB6 0E 000382 AVFTE
AOMATTNP 01097178 1E 000AA0 AVFTEXT1 0115B4E8 0E 000C50 AVFTE
AOMATTN1 01096410 0E 000D68 AOMATTN AVFTF 0115C138 1E 0008B8
AOMATTN2 010964C0 0E 000CB8 AOMATTN AVFTFINT 0115C158 0E 000898 AVFTF
AOMATTN3 0109686E 0E 00090A AOMATTN AVFTFRNT 0115C3F0 0E 000600 AVFTF
AOMCBLKS 01211020 16 000128 AVFTG 00FF1788 1B 000038
AOMGTRCE 01098AE0 1E 0004C8 AVFTGLUE 00FF17A8 0B 000018 AVFTG
AOMMTERM 0109A9C8 1E 0001D0 AVFTM 0115C9F0 1E 000BF0
AOMQERR 01098FA8 1E 000A68 AVFTMAIN 0115CA10 0E 000BD0 AVFTM
AOMQMGR 01099A10 1E 000FB8 AVFTMRTY 0115D252 0E 00038E AVFTM
AOMSSSVT 012110C8 06 000080 AOMCBLKS AVFTS 0115D5E0 1E 0005D8
ASALLOC 00FF40B0 0B 0005D0 IEAVELIT AVFTSRBR 0115D600 0E 0005B8 AVFTS
ASMGLP 00FF4610 0B 000070 IEAVELIT AVPAG 00FF4254 0B 00042C IEAVELIT
ASMP 00FF4550 0B 000130 IEAVELIT BAIPL 00FC549C 00 0000C8 IEEMSER
ASMVT 00FD8930 00 000500 ILRASM00 CBBRANCH 00FFE7FC 0B 00000C IGVVSCAP
ASRGLTAB 01205218 16 000040 CLRDIE 011E1EB4 0E 000F8C IOSRMIHR
ASRM 00FF40E0 0B 0005A0 IEAVELIT CMLCIOBT 00FE7232 0B 000ECE IEAVESLK
ASRSERVA 011548DC 0E 001264 ASRSERVP CMLCOBT 00FE7244 0B 000EBC IEAVESLK
ASRSERVE 011552EA 0E 000856 ASRSERVP CMLP 00FF4590 0B 0000F0 IEAVELIT
ASRSERVM 011552EC 0E 000854 ASRSERVP CMLREL 00FE7674 0B 000A8C IEAVESLK
ASRSERVP 01153D88 1E 001DB8 CMLUOBT 00FE7370 0B 000D90 IEAVESLK
ASRSERVR 01154AD0 0E 001070 ASRSERVP CMSCOBT 00FE7932 0B 0007CE IEAVESLK
ASRSERVX 01154ACC 0E 001074 ASRSERVP CMSEDLK 00FDCA70 00 000048 IEAVESLA
ASRSERVZ 011554DE 0E 000662 ASRSERVP CMSFIRST 00FDCA60 00 000058 IEAVESLA
AVFFA 01155B40 1E 0007B8 CMSFRSQH 00FDCA64 00 000054 IEAVESLA
AVFFAFRE 01155B60 0E 000798 AVFFA CMSLOCK 00FDCA80 00 000038 IEAVESLA
AVFFAFSE 01155E00 0E 0004F8 AVFFA CMSP 00FF45A0 0B 0000E0 IEAVELIT
AVFFD 011562F8 1E 000780 CMSRALL 00FE7D8C 0B 000374 IEAVESLK
AVFFDIAG 01156318 0E 000760 AVFFD CMSRALLH 00FE7D8C 0B 000374 IEAVESLK
AVFFL 01156A78 1E 000620 CMSREL 00FE7A00 0B 000700 IEAVESLK
AVFFLOOP 01156A98 0E 000600 AVFFL CMSRELI 00FE7A1C 0B 0006E4 IEAVESLK
AVFFR 01157098 1E 000F28 CMSSMFLK 00FDCA60 00 000058 IEAVESLA
AVFFRR 011570B8 0E 000F08 AVFFR CMSSQH 00FDCA84 00 000034 IEAVESLA
CMSUOALL 00FE7AB4 0B 00064C IEAVESLK CSVSBCHK 01162304 0E 00061C CSVSBRTN
CMSUOBT 00FE7880 0B 000880 IEAVESLK CSVSBLDF 01161A38 0E 000EE8 CSVSBRTN
CMSUOBTI 00FE789C 0B 000864 IEAVESLK CSVSBLDL 01162100 0E 000820 CSVSBRTN
COFMESTA 0115DBB8 1E 0012C8 CSVSBLFD 011620CC 0E 000854 CSVSBRTN
COFMIDEN 0115EE80 1E 000B68 CSVSBMFD 01161E46 0E 000ADA CSVSBRTN
COFMMTGR 0115F9E8 1E 0002E8 CSVSBRTN 01161A38 1E 000EE8
CPUAFF 00FF74F4 0B 000624 IEAVESTS CSVSRCH 00FF17C0 1B 000072
CPUOBT 00FF2846 0B 000FDA IEAVELK CSVSYNCH 01162920 1E 000570
CPUP 00FF4640 0B 000040 IEAVELIT CSVS2CDQ 011637F8 0E 000230 CSVS2RTN
CPUREL 00FF2862 0B 000FBE IEAVELK CSVS2GWK 01163708 0E 000320 CSVS2RTN
CRBRANCH 00FFE7E4 0B 000024 IGVVSCAP CSVS2LIB 01163580 0E 0004A8 CSVS2RTN
CSRABEND 01030050 0E 000018 CSRABRTN CSVS2LSR 011636D4 0E 000354 CSVS2RTN
CSRABRTN 0102F050 1E 001018 CSVS2RDQ 01163888 0E 0001A0 CSVS2RTN
CSRDWST 01205140 16 000040 CSVS2RTN 01163580 1E 0004A8
CSRTABLE 011FFDB0 16 001000 CSVVFEP1 01163AAA 0E 0009DE CSVVFNDE

352 z/OS MVS IPCS Commands

 VERBEXIT NUCMAP subcommand

The nucleus map sorted alphabetically by name continues with data similar
to the preceding example.

VERBEXIT SADMPMSG subcommand — format stand-alone dump

message log
Specify the SADMPMSG verb name on the VERBEXIT subcommand to format the
SADMP program run-time dump message log. These messages can help identify
problems with stand-alone dump output.

Note: This log does not contain messages issued following abnormal ending errors
on the SADMP output tape, or after the tape was unloaded following normal
ending of SADMP.

See z/OS MVS Diagnosis: Tools and Service Aids for information about the
stand-alone dump program.
v Parameters
The VERBEXIT SADMPMSG subcommand has no parameters.
v Example: Format the stand-alone dump program run-time dump message log.
– Action
VERBEXIT SADMPMSG
– Result

*** STAND-ALONE DUMP VIRTUAL DUMP MESSAGE LOG ***

AMD059D ENTER ’DUMP’ OR ’SET’ WITH OPTIONS, ’LIST’ OR ’END’.

>
-DUMP SP(ALL) IN ASID(ALL)
AMD059D ENTER ’DUMP’ OR ’SET’ WITH OPTIONS, ’LIST’ OR ’END’.
>
-DUMP DAT OF ASID(ALL)
AMD059D ENTER ’DUMP’ OR ’SET’ WITH OPTIONS, ’LIST’ OR ’END’.
>
-DUMP PA OF DAT
AMD059D ENTER ’DUMP’ OR ’SET’ WITH OPTIONS, ’LIST’ OR ’END’.
>
-END
AMD010I PROCESSING ASID=0001 ASCB=00FD5E80 JOBNAME=*MASTER*
AMD076I PROCESSING DATA SPACE JES2IRDS, OWNED BY ASID 0001.
AMD010I PROCESSING ASID=0002 ASCB=00F36600 JOBNAME=PCAUTH
AMD010I PROCESSING ASID=0003 ASCB=00F36400 JOBNAME=RASP
AMD010I PROCESSING ASID=0004 ASCB=00F36200 JOBNAME=TRACE
AMD010I PROCESSING ASID=0005 ASCB=00F35E00 JOBNAME=GRS
AMD057I COMPLETED SPECIFIC DUMPING FOR GRS.
AMD010I PROCESSING ASID=0006 ASCB=00F48400 JOBNAME=DUMPSRV
AMD0290 REPLY W TO WAIT AFTER NEXT FULL SCREEN, ELSE REPLY N; REPLY=
-W
AMD076I PROCESSING DATA SPACE SDUMPCSA, OWNED BY ASID 0006.
AMD010I PROCESSING ASID=0008 ASCB=00F50E00 JOBNAME=CONSOLE
..
.
AMD056I DUMPING OF VIRTUAL STORAGE COMPLETED.

VERBEXIT SRMDATA subcommand — format System Resource

Manager data
Specify the SRMDATA verb name on the VERBEXIT subcommand to format
diagnostic data from the system resources manager (SRM).

Chapter 5. IPCS subcommands 353

VERBEXIT SRMDATA subcommand

Note: If an SVC dump generated the input data set, valid queues might appear to
be incorrect because the queues can change while the SVC dump is being
generated.
v Syntax

VERBEXIT SRMDATA [ ’parameter [,parameter]...’ ]

The parameters are:

[ ASQLIM ]
[ ENCQLIM ]
[ ENQQLIM ]
[ QLIM ]

v Parameters
The parameters are provided to limit the amount of output produced.
ASQLIM
The maximum number of OUCB elements processed by SRMDATA per
OUCB queue.
ENCQLIM
The maximum number of ENCB elements processed by SRMDATA per
ENCB queue.
ENQQLIM
The maximum number of ERE/EHE elements processed by SRMDATA per
queue.
QLIM
The maximum number of all other queue elements, not listed above,
processed by SRMDATA per queue.
v Example: For an example of the SRMDATA output, see the SRM component in
z/OS MVS Diagnosis: Reference.

VERBEXIT SUMDUMP subcommand — format SVC summary dump

data
Specify the SUMDUMP verb name on the VERBEXIT subcommand to locate and
format the summary dump data that an SVC dump or a stand-alone dump
contains.

Note: For stand-alone dumps, SUMDUMP formats any summary dump records it
finds in the buffers. Such records can exist in the buffers if an SVC dump is in
progress when a stand-alone dump is generated.
v Parameters
The VERBEXIT SUMDUMP subcommand has no parameters.
v Example: Obtain the summary dump data.
– Action
VERBEXIT SUMDUMP
– Result

354 z/OS MVS IPCS Commands

 VERBEXIT SYMPTOM subcommand

STORAGE TYPE RANGE START RANGE END ASID ATTRIBUTES

023BCD70 023BCD7F 001E (COMMON)
SUMLSTA RANGE -- 017E8000 017E8FFF 0001 (COMMON)
SUMLSTA RANGE -- 01F9B000 01F9CFFF 0001 (COMMON)
SUMLSTA RANGE -- 02166000 02167FFF 0001 (COMMON)
PSA ------------ 00000000 00001FFF 001E (COMMON)
PCCA ----------- 00F43008 00F4324F 001E (COMMON)
LCCA ----------- 00F82000 00F82A47 001E (COMMON)
LCCX ----------- 021C7000 021C771F 001E (COMMON)
INT HANDLER DUCT 02232FC0 02232FFF 001E (COMMON)
I.H. LINKAGE STK 02262000 0226202F 001E (COMMON)
REGISTER AREA -- 0000E000 00010FFF 001E
REGISTER AREA -- 00FC4000 00FC6FFF 001E (COMMON)
REGISTER AREA -- 00000001_7F5AD000 00000001_7F5B0FFF 001E
REGISTER AREA -- 7FFFE000 7FFFEFFF 001E

VERBEXIT SYMPTOM subcommand — format symptom string

Specify the SYMPTOM or SYMPTOMS verb name on the VERBEXIT subcommand
to format the symptom strings contained in the header record of an SVC dump,
SYSMDUMP dump, or stand-alone dump. The symptom strings are:
v The primary symptom string, consisting of:
– Symptoms provided by dump analysis and elimination (DAE) in the dump
header record when the dump is generated
– Symptoms in a literal definition, if it exists, of the IPCS symbol
SECONDARYSYMPTOMS
v The secondary symptom string, provided by IPCS as part of post-dump
processing and including symptoms provided by the IPCS add symptom service

For the structure of symptom strings in a dump, see search arguments in z/OS
Problem Management.

There is a restriction on the space available to secondary symptom strings in the

dump header. If the display does not contain the expected information, BROWSE
the dump HEADER. Truncated secondary symptom strings end with the characters
’-Truncated’. The entire symptom string is only available if it has been explicitly
placed into the dump, or the storage pointed to by the SYMAD pointer in the
SDUMP parameter list is available.

You can use the IPCS add symptom service to add secondary symptom strings up
to 256 bytes. IPCS creates the literal definition of the symbol
SECONDARYSYMPTOMS from the full symptoms that fit in the first 256 bytes of
the new symptom string.
v Parameters
The VERBEXIT SYMPTOM subcommand has no parameters.
v Example: Obtain the symptom strings from the dump.
– Action
VERBEXIT SYMPTOM
– Result

Chapter 5. IPCS subcommands 355

VERBEXIT VSMDATA subcommand

* * * * S Y M P T O M * * * *

Primary Symptom String:

RIDS/CSVLLCRE#L RIDS/CSVLLBLD PIDS/5655CICJ AB/S0FF0 RIDS/CSVLLBLD#R

VALU/H016D182F REGS/09500 REGS/06026 VALU/COOKASIDE

Symptom Symptom data Explanation

---------------- ------------- -----------
RIDS/CSVLLCRE#L CSVLLCRE#L Routine identifier
RIDS/CSVLLBLD CSVLLBLD Routine identifier
PIDS/5655CICJ 5655CICJ Component identifier
AB/S0FF0 0FF0 ABEND code - system
RIDS/CSVLLBLD#R CSVLLBLD#R Routine identifier
VALU/H016D182F 016D182F Error related hexadecimal value
REGS/09560 09560 Program register
REGS/06026 06026 Program register
VALU/COOKASIDE OOKASIDE Error related character value

The dump does not contain a secondary symptom string.

VERBEXIT VSMDATA subcommand — format virtual storage

management data
Specify the VSMDATA verb name and optional parameters on the VERBEXIT
subcommand to format diagnostic data from virtual storage management (VSM).
v Syntax

VERBEXIT VSMDATA [ ’parameter [,parameter]...’ ]

The parameters are:

[CONTROLBLOCKS] [ALL] [DETAIL]
[SUMMARY]

[CURRENT]
[ERROR]
[TCBERROR]
[NOASIDS]
[ASIDLIST(asidlist)]
[JOBNAME(joblist) | JOBLIST(joblist)]
[GLOBAL|NOGLOBAL]

[OWNCOMM [([CSA] [SQA])]

[SUMMARY ]
[DETAIL ]
[ALL]
[ASIDLIST(asidlist)]
[SYSTEM]
[SORTBY(ASIDADDR|ASIDLEN|ADDRESS|TIME|LENGTH)]
[CONTENTS(YES|NO)]

v Report Type Parameters

Use these parameters to select the type of report. If you omit a report type
parameter, the default is CONTROLBLOCKS. Both the CONTROLBLOCKS and
OWNCOMM parameters have two additional report type parameters —
SUMMARY and DETAIL. For the CONTROLBLOCKS report, the default is
DETAIL. For the OWNCOMM report, the default is SUMMARY.
CONTROLBLOCKS
Specifies a report of VSM control blocks. The blocks formatted depend on
the associated parameters: ALL, DETAIL, SUMMARY, CURRENT, ERROR,
TCBERROR, NOASIDS, ASIDLIST, JOBNAME, GLOBAL, and NOGLOBAL.
The CONTROLBLOCKS parameter is the default; the following two
commands produce the same report:

356 z/OS MVS IPCS Commands

 VERBEXIT VSMDATA subcommand

VSMDATA ALL NOGLOBAL

VSMDATA CONTROLBLOCKS ALL NOGLOBAL
OWNCOMM [([CSA] [SQA])]
Requests CSA tracker reporting from VERBEXIT VSMDATA. OWNCOMM
may be entered with a CSA option, an SQA option, or both. When only one
of the options is entered, it indicates that the report should only contain
information pertaining to the referenced areas of common storage. Reporting
regarding both may be explicitly requested or implied by omission of all
qualifying options.
When you use an abbreviated form of OWNCOMM, enter OWNC at
minimum.
SUMMARY
Specifies a summary CONTROLBLOCKS or OWNCOMM report.
SUMMARY is the default for the OWNCOMM report but not for the
CONTROLBLOCKS report. For more information about the output produced
by the VERBX VSMDATA CONTROLBLOCKS SUMMARY report, see the
VSM component in z/OS MVS Diagnosis: Reference.
DETAIL
Specifies a detailed CONTROLBLOCKS or OWNCOMM report. DETAIL is
the default for the CONTROLBLOCKS report but not for the OWNCOMM
report.
v Address Space Selection Parameters for CONTROLBLOCKS
Use these parameters to obtain data for particular address spaces, which you
specify by their address space identifiers (ASIDs). If you omit these parameters
with CONTROLBLOCKS, the default is CURRENT. For more information, see
the select ASID service in z/OS MVS IPCS Customization.
ALL
Specifies formatting of all VSM control blocks for LSQA and the private area
for all address spaces in the dump.
CURRENT
Specifies formatting of the VSM control blocks for LSQA and the private
area for the address spaces that were current when the system wrote the
dump.
ERROR
Specifies formatting of VSM control blocks for LSQA and the private area for
any address space with an MVS error indicator or containing a task with an
error indicator.
TCBERROR
Specifies processing of VSM control blocks for LSQA and the private area for
any address space containing a task with an error indicator. Blocks for
address spaces with an error indicator are not processed.
NOASIDS
Suppresses formatting of VSM control blocks for LSQA or the private area
for any address space.
ASIDLIST(asidlist)
Specifies one or more ASIDs for the address spaces for which you want to
process VSM control blocks for LSQA and the private area.

Chapter 5. IPCS subcommands 357

VERBEXIT VSMDATA subcommand

The asidlist can be a single ASID, a range of ASIDs, or a list of

noncontiguous ASIDs, When specifying a range, separate the first and last
ASIDs in the range with a colon. When specifying a list, separate the list
members with commas or blanks.
The ASID can be 1 through 32767 (decimal). You can specify as many ASIDs
as you need; there is no system-imposed maximum.
JOBNAME(joblist) | JOBLIST(joblist)
Specifies one ore more job names whose associated address spaces are to be
processed for the VSM control blocks for LSQA and the private area. Use
commas to separate the job names in the list; do not enclose job names in
apostrophes; and do not specify a range of job names.
v Data Selection Parameters for CONTROLBLOCKS
Use these parameters to limit the scope of the data in the report. If you omit a
data selection parameter, the default is GLOBAL.
GLOBAL or NOGLOBAL
Specifies or suppresses formatting of VSM control blocks for the SQA and
CSA. GLOBAL specified the formatting; NOGLOBAL suppresses the
formatting.
v Address Space Selection Parameters for OWNCOMM DETAIL
Use these parameters to obtain data from particular address spaces, which you
specify by their address space identifiers (ASIDs). If you omit these parameters
with OWNCOMM DETAIL, the default is ALL. For more information, see the
select ASID service in z/OS MVS IPCS Customization.
ALL
Specifies formatting of data about CSA, ECSA, SQA, and ESQA storage for
all address spaces in the dump.
ASIDLIST(asidlist)
Specifies a list of ASIDs for the address spaces for which you want data
about CSA, ECSA, SQA, and ESQA storage.
The asidlist can be a single ASID, a range of ASIDs, or a list of
noncontiguous ASIDs, When you specify a range, separate the first and last
ASIDs in the range with a colon. When you specify a list, separate the list
members with commas or blanks.
The ASID can be 1 through 32767 (decimal). You can specify as many ASIDs
as you need; there is no system-imposed maximum.
v Data Selection Parameters for OWNCOMM DETAIL
Use these parameters to limit the scope of the data in the report.
SYSTEM
Requests data about CSA, ECSA, SQA, and ESQA storage that the system
uses; this storage is not "owned" by any particular address space or job.
SORTBY(ASIDADDR | ASIDLEN | ADDRESS | TIME | LENGTH)
Indicates how IPCS is to sort the list of requests for CSA, ECSA, SQA, or
ESQA storage:
ASIDADDR
Sort the output by address space identifier, in ascending order. When
two or more entries have the same ASID, IPCS sorts these entries by
storage address. If you omit a qualifying value with SORTBY, the
default is ASIDADDR.

358 z/OS MVS IPCS Commands

 VERBEXIT VSMDATA subcommand

ASIDLEN
Sort the output by address space identifier, in ascending order. When
two or more entries have the same ASID, IPCS sorts these entries by
the length of the storage at the reported address.
ADDRESS
Sort the output by storage address, in ascending order.
TIME Sort the output by the time at which the system processed the
request to obtain storage, starting with the oldest request.
LENGTH
Sort the output by the length of the storage represented by each
entry, starting with the smallest length value.
CONTENTS(YES | NO)
Indicates whether IPCS is to display the contents of the first 4 words of the
data at the storage address. If an error occurs when the system tries to
access the storage, the message Data ------] Not Available appears in this
field. If you omit CONTENTS, CONTENTS(YES) is the default.
v Example 1: Format information about CSA, ECSA, SQA, and ESQA storage for
address space identifiers 1, 6, 7, 8, and 9, and sort the output by storage length.
– Action
VERBX VSMDATA ’OWNCOMM DETAIL SORTBY(LENGTH) ASIDLIST(1,6:9)’
v Example 2: Format information about CSA, ECSA, SQA, and ESQA storage for
all address space identifiers, and sort the output by address.
– Action
VERBX VSMDATA ’OWNCOMM DETAIL ALL SORTBY(ADDRESS)’
– Result
For an example of the VSMDATA output, see the VSM component in z/OS
MVS Diagnosis: Reference.

VLFDATA subcommand — format virtual lookaside facility data

Use the VLFDATA subcommand to generate diagnostic reports about virtual
lookaside facility (VLF) activity in the system. Use the report type parameters to
choose the kinds of VLF-related information that you want to see.
v Syntax

Chapter 5. IPCS subcommands 359

VLFDATA subcommand

VLFDATA

-------- Report Type Parameters -----------------------------

[ CLASS(vlfclass) ] [ ALL ]
[ SHORT ]
[MAJOR(majorname) ]
[MINOR(minorname) ]
[ EXCEPTION ]
[ STORAGE [(vlfclass)] ]
[ SUMMARY ]
[ STATS [(vlfclass)] ]
[ USER [(vlfclass)] ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report Type Parameters

Use these parameters to select the type of report. If you omit a report type
parameter, the default is SUMMARY.

Note: In the following descriptions, vlfclass is a class name consisting of 1 to 7

alphanumeric characters or the following characters:
$ (X’5B’)
# (X’7B’)
@ (X’7C’)
CLASS(vlfclass)
Requests a report containing information about a VLF object class. Use
vlfclass to specify a particular VLF class. You can request the following
CLASS reports:
ALL Requests all major/minor information available for the specified
class.
SHORT
Requests a more detailed version of the SUMMARY report for the
specified class.
MAJOR(majorname)
Requests a report containing details about all VLF objects associated
with the specified major name. Specify this parameter alone or with
MINOR. The majorname can consist of up to 64 characters specified
in hexadecimal, character, or binary notation.
MINOR(minorname)
Requests a report containing information about all VLF objects
associated with the specified minor name. Specify this parameter
alone or with MAJOR. The minorname can consist of up to 64
characters specified in hexadecimal, character, or binary notation.
EXCEPTION
Requests a report containing information about inconsistencies detected
during verification of VLF dump data.

360 z/OS MVS IPCS Commands

 VLFDATA subcommand

STORAGE [(vlfclass)]
Requests a report describing the storage management of VLF data spaces.
The vlfclass is optional, and specifies the class for which you want to see a
STORAGE report. If you do not supply any class names, the report will
contain storage information for all classes.
SUMMARY
Requests a report containing general information about each class that uses
VLF services. The report includes the class type, its status at the time of the
dump, related data space information, and some statistics.
USER [(vlfclass)]
Requests a report containing information about all identified users for the
non-VLF address space that was using a VLF function at the time of error.
This non-VLF address space is associated with VLF through use of a user
token. The vlfclass is optional; it limits the report to identified users for the
specified class.
STATS [(vlfclass)]
Requests a report containing statistics. The vlfclass is optional; it limits the
report to the specified class.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the VLFDATA subcommand.
v Example: See the VLF component in z/OS MVS Diagnosis: Reference for examples
of VLFDATA output.

WHERE subcommand — identify an area at a given address

Use the WHERE subcommand to identify the area in a dump in which an address
resides. IPCS provides a report containing:
v The address space text
v The specified address
v The name of the area in the dump at the specified address. The name can be:
– The name of a load module. For nucleus CSECTs, the load module name is
IEANUC0x, where x is obtained from field CVTNUCLS. Externally defined
CSECTs within the nucleus are identified following the load module name.
Externally defined CSECTs in other load modules are not displayed.
To be displayed, the module name must conform to the following naming
conventions:
- The name is 1 through 8 characters.
- The first character is an uppercase EBCDIC letter or one of the following
national characters:
$ (X’5B’)
# (X’7B’)
@ (X’7C’)
- The remaining characters are uppercase EBCDIC letters, national characters,
or EBCDIC decimal digits.
If a module name does not conform to these conventions, IPCS displays:
MODULE(SPECIALNAME)
– The name of a control block. The parameter STRUCTURE is displayed
followed by the control block name.
– The name of an area of storage that is not a module or a control block. IPCS
displays AREA followed by the name of the area.

Chapter 5. IPCS subcommands 361

WHERE subcommand

v The offset into the identified area.

v The name of the system area containing the specified address, which can be:
– Common service area (CSA)
– Fixed link pack area (FLPA)
– Modified link pack area (MLPA)
– Pageable link pack area (PLPA)
– Private
– Prefixed save areas (PSA)
– Read only nucleus
– Read/write nucleus
– System queue area (SQA)

If after examining the return code, IPCS cannot identify the area pointed to by the
specified address, IPCS issues the following message:
BLS18451I Unable to identify the area at ’addr space’ address xxxxxxxx

If IPCS issues this message, enter one or more of the dump analysis subcommands,
such as SUMMARY and STATUS, then reenter the WHERE subcommand. Based
the dump processing for the analysis subcommands, IPCS may now be able to
identify the area.

The detail in the report generated by the WHERE subcommand depends to a large
extent on previous processing of the dump. For example, if after initializing a
dump, you enter WHERE, IPCS generates a minimal report. But if you reenter
WHERE after entering a number of subcommands, IPCS will probably produce a
more detailed report.

Note: The WHERE subcommand may modify X, the current address, as follows:
1. If WHERE can associate the location identified by data-descr with a block of
storage containing that location, X is set to describe the block of storage
containing the location.
2. If WHERE cannot associate the location identified by data-descr with a block of
storage containing that location, X is set to describe the location identified by
data-descr.

WHERE will not change X if error conditions occur, such as syntax errors or an
unresolvable data-descr.

When used as a primary command, WHERE stacks a pointer to the address, but
does not change the value of X. Use option 1 (BROWSE) of the IPCS dialog to find
the pointer.

You can invoke WHERE as an IPCS subcommand or as an IPCS primary

command. (This section refers to both the subcommand and the primary command
as the “WHERE command.”) The WHERE command is useful for identifying
locations of addresses found in other reports produced by IPCS subcommands.

For specified addresses in each of the system areas, the WHERE command names
different areas in the dump, some more helpful than others.
v Addresses in the LPA and Nucleus
The WHERE command has the greatest benefit when used on addresses in the
following system areas:

362 z/OS MVS IPCS Commands

 WHERE subcommand

– Fixed link pack area (FLPA)

– Modified link pack area (MLPA)
– Pageable link pack area (PLPA)
– Read-only nucleus
– Read-write nucleus.
For addresses in these areas, the WHERE command returns the name of a load
module.
The WHERE command provides the most specific information for addresses
located in the nucleus. The WHERE command provides the name of the
externally defined CSECTs within the nucleus in which the address is located.
They are identified following the load module name. For nucleus CSECTs, the
load module name is IEANUCOx, where x is obtained from field CVTNUCLS.
Externally defined CSECTs in other load modules are not displayed.
When you invoke WHERE for an address in any of the parts of the LPA, it
returns the name of a load module that contains a number of CSECTs. To find
the exact CSECT you are looking for, you must do one of the following:
– If the address is in the section of dump that fits into memory, you can enter
the WHERE subcommand from the Browse option of the IPCS dialog. When
you press F3 to exit the WHERE output, the Browse panel will scroll to the
location of that CSECT in the dump.
– If the address is not in the section of dump in memory, you can use the
AMBLIST service aid to format and print the load module. The AMBLIST
service aid gives you a list of the component CSECTs in the load module. See
z/OS MVS Diagnosis: Tools and Service Aids for more information about using
AMBLIST.
v Addresses in private storage
The WHERE primary command can also be used on addresses in private and
extended private area storage.
– Private area analysis may identify load modules and offsets within them.
– It may also associate the address of interest with data areas.
– z/OS R2 IPCS adds the ability to associate addresses with pages containing
application subpools, AREA(SUBPOOLspKEY(key), where
sp A three-digit decimal subpool number between 0 and 255.
key A two-digit decimal storage key between 0 and 15.
The IPCS storage map entries describe subpools in increments of 4096-byte
pages associated with subpools rather than the 8-byte units of allocated
storage within them.
v Addresses in other areas of storage
The WHERE primary command can also be used on addresses in other areas of
storage:
– Common storage area (CSA)
– Prefixed save area (PSA)
– System queue area (SQA).
For addresses in these areas, the information provided is less specific than the
information provided for the LPA and nucleus addresses. When issued on an
address in these areas, WHERE returns one of the following:
– The name of a control block. The parameter STRUCTURE is displayed
followed by the control block name.

Chapter 5. IPCS subcommands 363

WHERE subcommand

– The name of an area of storage (not a module or control block). The

parameter AREA is typically displayed followed by the name of the area.
– The names of the load modules that are loaded by LOAD with GLOBAL=YES
option from the current ASID, if the address is in the CSA or ECSA storage.
v When WHERE Does Not Work
If after examining the return code IPCS determines that the area pointed to by
the specified address cannot be identified, IPCS issued message BLS18451I with
the address and ASID:
BLS18451I Unable to identify the area at ASID(X’0032’) address 005CD478
This situation sometimes occurs when the dump directory does not contain
enough information about the area of the dump. Try entering the SUMMARY or
STATUS subcommand. These subcommands should fill missing information in
the dump directory. Then reenter the WHERE subcommand:
ASID(X’0032’) 005CD478. AREA(CURRENT)+5CC478 IN PRIVATE
The detail of the report generated by the WHERE command depends to a large
extent on how much you have processed the dump. For example, if after
initializing a dump, you enter WHERE, IPCS generates a minimal report. But if
you enter WHERE again later in your IPCS session, after entering a number of
subcommands, a more detailed report will probably be produced.
v Syntax

{ WHERE } data-descr
{ W }
[SELECT([AREA][MODULE][STRUCTURE])]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Parameters
data-descr
Specifies an address in a dump through the data description parameter,
which consists of five parts:
– An address (required)
– Address processing parameters (see the following note)
– An attribute parameter (optional)
– Array parameters (optional)
– A remark parameter (optional)
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter.

Note:
1. An ASID may optionally be specified as part of the data description
parameter. If the specified address is in private storage, and no ASID is
specified, the default ASID is the only ASID searched.
2. ACTIVE, MAIN, and STORAGE cannot be specified.

364 z/OS MVS IPCS Commands

 WHERE subcommand

SELECT([AREA][MODULE][STRUCTURE])
Specifies the data types to be returned as results of the WHERE command.
AREA
Allows WHERE to associate the location of interest with AREAs.
MODULE
Allows WHERE to associate the location of interest with MODULEs.
STRUCTURE
Allows WHERE to associate the location of interest with STRUCTUREs.

When no selection is specified or all selections are chosen, WHERE can

associate the location of interest with AREAs, MODULEs, or STRUCTUREs.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the WHERE subcommand.
v Example 1: Determine where an absolute address is located.
– Action
COMMAND ===> IPCS WHERE FD2834.
– Result
WHERE generates the following output line, showing that the specified
address, in address space X'0058' is X'20D14' bytes into CSECT IOSUCB,
which is located in load module IEANUC01 in the READ/WRITE NUCLEUS.

IPCS OUTPUT STREAM -------------------------------------- LINE 0 COLS 1 78

COMMAND ===> _ SCROLL ===> CSR
****************************** TOP OF DATA ***********************************
ASID(X’0058’) 00FD2834. IEANUC01.IOSUCB+020D14 IN READ/WRITE NUCLEUS
****************************** END OF DATA ***********************************

If the address you specified is in the portion of the dump in memory, the
WHERE subcommand also takes you to that address in the dump when you
press F3 to exit this screen.
If the primary command are used in this example, the item that contains the
address are added to the pointer stack. If more than one item contains the
address, the item with the smallest offset are added to the pointer stack.
v Example 2: Use WHERE from system trace table output, which provides a
history of the most recent events in the system. The WHERE command can save
you from having to leave the system trace table to find the information needed.
For example, if you are going through the table and you see a PSW that interests
you, you can use the WHERE command to find out to what module the PSW
points. Instead of having to use the VERBEXIT NUCMAP, LPAMAP, or go into
the Browse panel of the IPCS dialog, you can type WHERE directly from the
system trace table and find out the module name. Also, if you enter WHERE as
a primary command it will put a pointer to the module on the stack.
Choose option 4 from the IPCS Primary Option Menu. Then, enter the system
trace table with:
===> SYSTRACE

Now, enter WHERE on the command line of the system trace table.

Chapter 5. IPCS subcommands 365

WHERE subcommand

IPCS OUTPUT STREAM ---------------------------------------- LINE 471 COLS 1 78

COMMAND ===> WHERE 1D073D0 SCROLL ===> CSR
01 001B 009F8E88 SVCR 78 070C2000 81D07386 00000000 00000080 7FFFDD10
01 001B 009F8E88 SVC 78 070C3000 81D073B2 0000E101 00000030 7FFFDD10
01 001B 009F8E88 SVCR 78 070C3000 81D073B2 00000000 00000030 7FFFDD10
01 001B 009F8E88 SVC 78 070C1000 81D073D0 0000E101 00000010 7FFFDD80
01 001B 009F8E88 SVCR 78 070C1000 81D073D0 00000000 00000010 7FFFDD80
01 001B 009F8E88 SVCR 2A 070C1000 8001B832 00000000 00000000 009F8CF0
01 001B 009F8E88 SVC 78 070C2000 8001B93E 00000003 00000190 00006C60
01 001B 009F8E88 SVCR 78 070C2000 8001B93E 00000000 00000190 00006C60
01 001B 009F8E88 SVC 78 070C0000 80008B50 00000002 00000368 00000000
01 001B 009F8E88 SVCR 78 070C0000 80008B50 00000000 00000368 00006A88
01 001B 009F8E88 SVC 38 070C1000 80008C4E 00000000 00000006 00006C78
01 001B 009F8E88 PC ... 0 811520D2 00108
01 001B 009F8E88 PT ... 0 811520D2 001B
01 001B 009F8E88 SVCR 38 070C1000 80008C4E 00000000 00000002 00F3FB14
01 001B 009F8E88 SVC 78 070C0000 80019294 00000002 00000358 00000000
01 001B 009F8E88 SVCR 78 070C0000 80019294 00000000 00000358 00006730
01 001B 009F8E88 ?EXPL 0003 77007B16 C3629700 00000003
01 000E 009F6E88 SRB 070C0000 811A3180 0000000E 00F42200 00F4222C
80
01 000E 00000000 SSRV 2 80FFB540 000A002C 7F000000 00000000
00000000
01 000E 00000000 SSRV 12A 80007478 00B9E8B0 40000000 00000000
00000000
01 000E 009F6E88 DSP 070C0000 800073C2 00000000 000070C0 00B9E8B0 00
01 000E 009F6E88 SSRV 1 80007388 00B9E8B0 00000001 00000000
00000000
01 001B 009F8E88 DSP 070C0000 800192C8 00000000 00000002 00006B48 00
01 001B 009F8E88 SVC 78 070C2000 8001936C 0000E572 00001000 00000000
01 001B 009F8E88 SVCR 78 070C2000 8001936C 00000000 00001000 7FFE0000
01 001B 009F8E88 SVC 78 070C2000 800199B8 0000EF72 00000018 00000000
01 001B 009F8E88 SVCR 78 070C2000 800199B8 00000000 00000018 01B1E640
01 001B 009F8E88 SVC F0 070C2000 80014912 80014910 00000000 0000677C
01 001B 009F8E88 *SVC D 070C1000 80FE5CFC 80014910 80000000 80FF0000
01 001B 009F8E88 PC ... 0 811808CE 00506
01 001B 009F8E88 PC ... 0 82106B2A 00503
****************************** END OF DATA ***********************************

– Result
WHERE generates the following dump display reporter panel. It tells you that
the address is 03D0 hexadecimal bytes into load module IGC0004B in the
extended PLPA.

IPCS OUTPUT STREAM -------------------------------------- LINE 0 COLS 1 78

COMMAND ===> _ SCROLL ===> CSR
****************************** TOP OF DATA ***********************************
ASID(X’001B’) 01D073D0. IGC0004B+03D0 IN EXTENDED PLPA
****************************** END OF DATA ***********************************

Because WHERE was invoked as a primary command, WHERE also stacks a

pointer to the beginning of the load module, X'1D07000'. The pointer will
appear in the Browse option of the IPCS dialog. The following shows using
WHERE in the system trace table.

366 z/OS MVS IPCS Commands

 WHERE subcommand

DSNAME(’D46IPCS.DRVC400.SA00001’) POINTERS -----------------------------------

COMMAND ===> _ SCROLL ===> CSR
PTR Address Address space Data type
00001 00000000 ASID(X’0003’) AREA
Remarks:
00002 000006B0 ASID(X’0003’) AREA
Remarks:
00003 00FD7420 ASID(X’0001’) STRUCTURE(Cvt)
Remarks: Communications Vector Table
-------------------------------------------------------------------------------
|00004 01D07000 ASID(X’001B’) MODULE(IGC0004B) |
| Remarks: |
-------------------------------------------------------------------------------
**************************** END OF POINTER STACK *****************************

v Example 3: Use WHERE from a logrec buffer in a dump. WHERE can help you
look through this table. For example, if you are examining the error PSW in the
VERBEXIT LOGDATA report and want to know where address X'120E298' in the
error PSW points to, you can use WHERE directly from this screen.

IPCS OUTPUT STREAM -------------------------------------- LINE 0 COLS 1 78

COMMAND ===> WHERE 120E298 SCROLL ===> CSR
****************************** TOP OF DATA ***********************************

* * * * * L O G D A T A * * * * *

TYPE: SOFTWARE RECORD REPORT: SOFTWARE EDIT REPORT DAY.YEAR

(SVC 13) REPORT DATE 197.95
SVC: VS 2 REL 3 ERROR DATE 158.95
MODEL:3090 HH:MM:SS.T
SERIAL:170067 13::1:44.9
JOBNAME: D22AMSTR
ERRORID: SEQ=17095 CPU=0041 ASID=0047 TIME=13:31:43.9

< Some Output Not Shown >

TIME OF ERROR INFORMATION

PSW: 070C2000 8120E298 INSTRUCTION LENGTH: 02 INTERRUPT CODE: 000D

FAILING INSTRUCTION TEXT: 581097E6 0A0D4830 C0105800

REGISTERS 0-7
GR: 00000000 04C78000 006F72D8 0000E601 006F72D8 7FF12080 00000004 00EE5500
AR: 0124E1B8 00000000 00000000 00000000 00000000 00000000 00000000 00000000

– Result
First, all items that contain this address are displayed using the dump display
reporter panel. The following message shows that the PSW you want to
examine more closely is 200 bytes into CSECT IGVSTSKT. That CSECT is in
load module IEANUC01 in the read-only nucleus.

IPCS OUTPUT STREAM -------------------------------------- LINE 0 COLS 1 78

COMMAND ===> _ SCROLL ===> CSR
****************************** TOP OF DATA ***********************************
ASID(X’0058’) 0120E298. IEANUC01.IGVSTSKT+0200 IN READ ONLY NUCLEUS
****************************** END OF DATA ***********************************

When you press F3 to exit this screen, IPCS will stack the pointer to the
beginning of the CSECT, so when you go back into Browse you can look at all
of the detailed information in that register or PSW.

Chapter 5. IPCS subcommands 367

WHERE subcommand

DSNAME(’D46IPCS.DRVC400.SA00001’) POINTERS -----------------------------------

COMMAND ===> _ SCROLL ===> CSR
PTR Address Address space Data type
00001 00000000 ASID(X’0003’) AREA
Remarks:
00002 000006B0 ASID(X’0003’) AREA
Remarks:
00003 00FD7420 ASID(X’0001’) STRUCTURE(Cvt)
Remarks: Communications Vector Table
-------------------------------------------------------------------------------
|00004 0120E298 ASID(X’0058’) MODULE(IEANUC01) |
| Remarks: |
-------------------------------------------------------------------------------
**************************** END OF POINTER STACK *****************************

v Example 4: Determine where an absolute address is located.

– Action
COMMAND ===> where cda800.
– Result
WHERE generates the following output line, showing that the specified
address is a TCB in the PRIVATE area.
CDA800. STRUCTURE(TCB)-10 IN PRIVATE
v Example 5: Determine the name of a module in storage.
– Action
Given an address, enter a WHERE subcommand specifying the address.
COMMAND ===> where 04a8001a
– Result
IPCS identifies the address space containing the module, the module name (if
the name conforms to IPCS naming conventions), the offset of the address
into the module, and the storage area containing the module.
ASID(X’0179’) 04A8001A. IGC0006A+1A IN EXTENDED PLPA
v Example 6: Determine the name of a module in storage when the module name
does not conform to IPCS naming conventions.
– Action
Given an address, enter a WHERE subcommand specifying the address.
COMMAND ===> where 04ab001a
– Result
IPCS provides the same information shown in the previous example, but
instead of the name of the module, IPCS displays “SPECIALNAME”. IPCS
also expands the name in hexadecimal characters, and shows the module
name as an eye-catcher in the output.
ASID(X’0179’) 04AB001A. SPECIALNAME+A01A IN EXTENDED PLPA
+0000 C9C7C3F0 F0F1F3C0 | IGC0013{ |

WLMDATA subcommand — analyze workload manager data

Use the WLMDATA subcommand to generate reports about the workload manager
(WLM) component of MVS.
v Syntax

368 z/OS MVS IPCS Commands

 WLMDATA subcommand

WLMDATA

--------- Report Type Parameters ---------------------------

[ POLICY ]
[ STATUS[,SYSNAME(sysname)]]
[ WORKMANAGER[,ASID(asidlist)]
[,SUBSYSTYPE(subsystype)]
[,SUBSYSNAME(subsysname)]

-------- Data Selection Parameters -------------------------

[ DETAIL ]
[ EXCEPTION ]
[ SUMMARY ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.
See “SETDEF subcommand — set defaults” on page 262.
[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Report Type Parameters

Use these parameters to select the type of report. You can specify as many
reports as you want. If you omit a report type parameter, the default is POLICY,
STATUS, and WORKMANAGER.
POLICY
Requests information about the sysplex service policy.
STATUS
Requests information about WLM status for one or more systems. The
parameter that can limit the scope of the STATUS report is:
SYSNAME(sysname)
Requests status information about WLM for a list of system names. If
you omit the SYSNAME parameter and value, the default is status
information for all systems in the sysplex. The sysname can be a single
system name or a list of system names. When you specify a list, separate
the names with commas. A system name has 1 to 8 characters.
WORKMANAGER
Requests information about the activity associated with work requests that
are connected to WLM. The parameters that can limit the scope of the
WORKMANAGER report are:
ASID(asidlist)
Specifies a list of ASIDs for the address spaces to be in the
WORKMANAGER report. If you omit the ASID parameter, the default is
information for all address spaces.
The asidlist can be a single ASID, a range of ASIDs, or a list of
noncontiguous ASIDs. When you specify a range, separate the first and
last ASIDs in the range with a colon. When you specify a list, separate
the list members with commas. The ASID has 1 to 4 hexadecimal digits.

Chapter 5. IPCS subcommands 369

WLMDATA subcommand

SUBSYSTYPE(subsystype)
Specifies a list of subsystem types to be in the WORKMANAGER report.
If you omit the SUBSYSTYPE parameter, the default is information for
all subsystem types.
The subsystype can be a single subsystem or a list of subsystems. When
you specify a list, separate the list members with commas. The
subsystype has 1 to 4 characters.
SUBSYSNAME(subsysname)
Requests status information about WLM for a list of subsystem names. If
you omit the SUBSYSNAME parameter and value, the default is status
information for all subsystems in the sysplex.
The subsysname can be a single subsystem name or a list of subsystem
names. When you specify a list, separate the names with commas. A
subsystem name has 1 to 8 characters.
v Data Selection Parameters
Use these parameters to limit the scope of the data in the report. If you omit a
data selection parameter, the default is SUMMARY.
DETAIL
Requests a report showing detailed information for each of the selected
topics.
EXCEPTION
Requests a list of exceptional or unusual conditions for each of the selected
topics.
SUMMARY
Requests summary information for each of the selected topics. SUMMARY is
the default.
v Return Codes
See “Standard subcommand return codes” on page 46 for a description of the
return codes produced by the WLMDATA subcommand.

XESDATA subcommand — format cross system extended services

data
Use the XESDATA subcommand to request formatting of information related to
cross system extended services. The information is available in three levels:
v The summary and detail levels provide diagnostic, configuration, and resource
information about a particular area of cross system extended services.
v The exception level provides an automated way of detecting incorrect data areas
and unusual system conditions that may be helpful in problem determination.
When an error is detected in control block chains or data content, the report
contains information for the IBM Support Center.

Note: If the dump is not caused by an error in the cross system extended services
component, the system issues the following message:
IXL0200I XESDATA XESSTACK report cannot be run with the current dump.
Reason: The dump did not result from an XES module failure.

In this case, if you know the address of the stack, and if the storage is in the
dump, enter a CBFORMAT STRUCTURE(XESSTACK) subcommand.

370 z/OS MVS IPCS Commands

 XESDATA subcommand

Data selection and report type parameters limit the scope and extent of the
information that appears in a report.
v Syntax

XESDATA

{ DETAIL }
{ EXCEPTION }
{ SUMMARY }

-------- Report Type Parameters --------

[ CACHE ]
[ CONNECTION ]
[ FACILITY ]
[ LIST ]
[ LOCK ]
[ LOCKMGR ]
[ LOCKRESOURCE ]
[ TRACE ]
[ XESSTACK ]

-------- Additional Data Selection Parameters --------

[ ASID(asidlist) ]
[ CFNAME(cfname) ]
[ CONNAME(conname) ]
[ HASHVALUE(hashvalue) ]
[ JOBNAME(jobname) ]
[ LISTNUM(listnum) ]
[ LOCKMGRCONID(conid) ]
[ LTENTRY(ltentry) ]
[ REQID(reqid) ]
[ REQUESTORCONID(conid)]
[ SOURCENAME(conname) ]
[ STRNAME(strname) ]
[ SYSNAME(sysname) ]
[ TARGETNAME(conname) ]
[ TROPTS(tropts) ]

-------- SETDEF-Defined Parameters -------------------------

Note: You can override the following SETDEF parameters.

See “SETDEF subcommand — set defaults” on page 262.

[ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]

v Data Selection Parameters

Use these parameters to select the level of information in the report. If you omit
these parameters, the default is SUMMARY.
DETAIL
Requests a report showing detailed information for each of the specified
objects or processes. An example is:
COMMAND ===> XESDATA DETAIL

Chapter 5. IPCS subcommands 371

XESDATA subcommand

EXCEPTION
Requests a list of exceptional or unusual conditions for the specified objects
or processes.
COMMAND ===> XESDATA EXCEPTION
SUMMARY
Requests summary information for the specified objects or processes.
SUMMARY is the default.
COMMAND ===> XESDATA SUMMARY
v Report Type Parameters
Use these parameters to select the type of report. If you specify more than one
report type parameter, IPCS produces a report for each parameter. If you omit a
report type parameter, the default is all report types.
CACHE
Requests information about outstanding cache requests for this system.
Information is included for both the request as a whole, and operation-level
information for the operation to each of the duplexed structure instances.
The report output is:
– XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
– CACHE SUMMARY REPORT
The output fields for each connection are:
– Number of requests
– Requests passing filters
An example is:
COMMAND ===> XESDATA CACHE
CONNECTION
Requests information about connectors to structures in the coupling facility.
The report output is:
– XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
– CONNECTION SUMMARY REPORT
The output fields for each connection specified are:
– Structure type
– Structure name
– Connect token
– Connect name
– Recovery status
– Diagnostic data
– Status of a pending response for an event that was delivered to the event
exit.
– An indication of the user-managed or system-managed state of a rebuild
process (both rebuild and duplexing rebuild).
Note that for duplexed structure instances, the report information will be
split into sections that deal with the duplexed structure as a whole, and
that deal with each of the allocated structure instances.
An example is:
COMMAND ===> XESDATA CONNECTION

372 z/OS MVS IPCS Commands

 XESDATA subcommand

FACILITY
Requests information about the coupling facilities and coupling facility
structures known to the system. The report output is:
– XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
– FACILITY SUMMARY REPORT
The output fields for each coupling facility are:
– Name
– Node descriptor
– Facility ID
– Control unit
– Authority
– Total space
– Max structure ID
– Connected indicator
– Policy indicator
– Pathing information
- Paths valid
- Paths online
- Paths miscabled
- Paths not operational
– Remotely-connected coupling facilities, identified by their remote CF node
descriptor (ND) and system identifier (SYID)
The output fields for each structure are:
– Name
– Facility
– Structure ID
– Type
– Structure version
– Relationship between duplexed structure instances
An example is:
COMMAND ===> XESDATA FACILITY
LIST
Requests information about outstanding list requests for this system.
Information is included for both the request as a whole, and operation-level
information for the operation to each of the duplexed structure instances.
The report output is:
– XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
– LIST SUMMARY REPORT
The output fields for each connection are:
– Number of list headers
– Number of lock entries
– For each outstanding lock request in the serialized list:
- Lock entry number
- Lock ownership status
- Lock data, if applicable

Chapter 5. IPCS subcommands 373

XESDATA subcommand

- Queued request count

– Requests passing filters
– Number of requests
An example is:
COMMAND ===> XESDATA LIST
LOCK
Requests information about outstanding asynchronous coupling facility lock
requests. Both simplex and duplex request data is included in the status
information. An example is:
COMMAND ===> XESDATA LOCK
LOCKMGR
Requests information about lock resources managed globally by the system.
The report output is:
– XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
– LOCKMGR SUMMARY REPORT
The output fields for each globally managed resource for each connection
are:
– Lock structure entry number
– Resource name
– Hash value
– Diagnostic data
– Indication of whether there is an outstanding asynchronous coupling
facility request
An example is:
COMMAND ===> XESDATA LOCKMGR
LOCKRESOURCE
Requests information about the lock resources owned or requested by the
system. The report output is:
– XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
– LOCKRESOURCE SUMMARY REPORT
The output fields for each resource are:
– Number of lock entries
– Lock structure entry number
– Connector this entry is managed by
– Number of exclusive holders
– Number of shared holders
– Resource name
– Hash value
– Requested status
– Requested event
– Diagnostic data
– Indication of whether there is an outstanding asynchronous coupling
facility request
An example is:
COMMAND ===> XESDATA LOCKRESOURCE

374 z/OS MVS IPCS Commands

 XESDATA subcommand

TRACE
Formats component trace entries for all SYSXES subtraces defined on the
system. The report output is described in z/OS MVS Diagnosis: Tools and
Service Aids. The output consists of trace entries just as they would be
displayed by individual CTRACE commands.
An example of a request for an unfiltered report is:
COMMAND ===> XESDATA TRACE

However, the TRACE report is normally more useful when filtered to limit
the output to traces containing specific information. Since the syntax for
specifying the filter information as a line command is complex, it is
generally more convenient to invoke this command through the XESDATA
panel interface.
XESSTACK
Requests information about cross system extended services execution flow.
This report contains diagnostic data for the IBM Support Center. The report
output is:
– XESDATA (CROSS-SYSTEM EXTENDED SERVICES) REPORT
– XESSTACK SUMMARY REPORT
The output fields contain diagnostic data.
An example is:
COMMAND ===> XESDATA XESSTACK
v Additional Data Selection Parameters
The table shows the additional data selection parameters that apply to each
report type.
Data Selection Report Types
Parameter
CACHE CONNECTION FACILITY LIST LOCK MGR LOCK TRACE XESSTACK LOCK
RESOURCE
ASID X X X X X X
CFNAME X X X X X X X
CONNAME X X X X X X X
HASHVALUE X X
JOBNAME X X X X X X
LISTNUM X
LOCKMGRCONID X
LTENTRY X X X X
REQID X X
REQUESTORCONID X X
SOURCENAME X
STRNAME X X X X X X X
SYSNAME X
TARGETNAME X
TROPTS X

ASID(asidlist)
Requests that only information about the address spaces for the listed ASIDs
be included in the report.
The asidlist can be a single ASID, a range of ASIDs, or a list of
noncontiguous ASIDs. When you specify a range, separate the first and last
ASIDs in the range with a colon. When you specify a list, separate the list
members with commas.
The ASID can be 1 through 65535. An ASID can be expressed in the notation
X'nnn' or nnn for a decimal number.
An example is:
COMMAND ===> XESDATA ASID(X’001A’) LIST DETAIL

Chapter 5. IPCS subcommands 375

XESDATA subcommand

CFNAME(cfname)
Requests that only information about the specified coupling facility be
included in the report.
The cfname can be a single coupling facility name or a list of names. Use
commas to separate names in the list; do not enclose the names in
apostrophes; and do not specify a range of names. To designate coupling
facility names that begin with the same characters, use an asterisk (*) as a
suffix. The asterisk denotes zero or more characters, up to the maximum
length of the string.
An example is:
COMMAND ===> XESDATA CFNAME(TESTCF)
CONNAME(conname)
Requests that only information about the connectors with the listed
connector names be included in the report.
The conname can be a single connector name or a list of names. Use commas
to separate names in the list; do not enclose the names in apostrophes; and
do not specify a range of names. To designate connector names that begin
with the same characters, use an asterisk (*) as a suffix. The asterisk denotes
zero or more characters, up to the maximum length of the string.
An example is:
COMMAND ===> XESDATA CONNAME(MYCONNAME1) LIST DETAIL
HASHVALUE(hashvalue)
Requests that only information about the listed hash values be included in
the report. The hash value is derived from the resource name on the
IXLLOCK macro and is used to determine what entry in the lock table is
used.
The hashvalue can be a single value, a range of values, or a list of
noncontiguous values. When you specify a range, separate the first and last
values in the range with a colon. When you specify a list, separate the list
members with commas.
An example is:
COMMAND ===> XESDATA CONNECTION HASHVALUE(00000001) DETAIL
JOBNAME(joblist)
Requests that only information about the address spaces associated with the
listed job names be included in the report.
The joblist can be a single job name or a list of job names. Use commas to
separate job names in the list; do not enclose job names in apostrophes; and
do not specify a range of job names. To designate job names that begin with
the same characters, use an asterisk (*) as a suffix. The asterisk denotes zero
or more characters, up to the maximum length of the string.
An example is:
COMMAND ===> XESDATA JOBNAME(MAINASID) LIST DETAIL
LISTNUM(listnum)
Requests that only information about requests affecting the specified list
header number or its entry be included in the report.
The listnum can be a single list header number or a list of numbers. Use
commas to separate numbers in the list; do not enclose the numbers in
apostrophes; and do not specify a range of numbers.

376 z/OS MVS IPCS Commands

 XESDATA subcommand

An example is:
COMMAND ===> XESDATA LIST LISTNUM(1) DETAIL
LOCKMGRCONID(conid)
Requests that only information about resources managed by the specified
connection identifier be included in the report.
The conid can be a single connection identifier or a list of identifiers. Use
commas to separate identifiers in the list; do not enclose the identifiers in
apostrophes; and do not specify a range of identifiers.
An example is:
COMMAND ===> XESDATA LOCKRESOURCE LOCKMGRCONID(01)
LTENTRY(ltentry)
Requests that only information about the listed lock table entries be included
in the report. The ltentry can be a single entry or a list of entries. When you
specify a list, separate the entries with commas.
An example is:
COMMAND ===> XESDATA LOCKMGR LTENTRY(20)
REQID(reqid)
Requests that only information about requests with the specified identifier
be included in the report.
The reqid can be a single request identifier or a list of identifiers. Use
commas to separate identifiers in the list; do not enclose the identifiers in
apostrophes; and do not specify a range of identifiers. The identifiers can be
expressed in the notation X'nnn' or nnn for decimal. To designate request
identifiers that begin with the same numbers, use an asterisk (*) as a suffix.
The asterisk denotes zero or more numbers, up to the maximum length of
the string.
An example is:
COMMAND ===> XESDATA LIST REQID(01)
REQUESTORCONID(conid)
Requests that only information about resources requested by the specified
connection identifier be included in the report. The conid can be a single
connection identifier or a list of identifiers. Use commas to separate
identifiers in the list; do not enclose the identifiers in apostrophes; and do
not specify a range of identifiers.
An example is:
COMMAND ===> XESDATA LIST REQUESTORCONID(01)
SOURCENAME(conname)
Requests that only information about the connectors with the listed
connector names from which signals are received be included in the report.
The conname can be a single connector name or a list of names. Use commas
to separate names in the list; do not enclose the names in apostrophes; and
do not specify a range of names. To designate connector names that begin
with the same characters, use an asterisk (*) as a suffix. The asterisk denotes
zero or more characters, up to the maximum length of the string.
An example is:
COMMAND ===> XESDATA CONNECTION SOURCENAME(MYCONNAME1)
STRNAME(strname)
Requests that only information about the specified coupling facility structure

Chapter 5. IPCS subcommands 377

XESDATA subcommand

be included in the report. The strname can be a single coupling facility

structure or a list of structures. Use commas to separate structures in the list;
do not enclose the structures in apostrophes; and do not specify a range of
structures. To designate structures that begin with the same characters, use
an asterisk (*) as a suffix. The asterisk denotes zero or more characters, up to
the maximum length of the string.
An example is:
COMMAND ===> XESDATA STRNAME(LIST01)
SYSNAME(sysname)
Requests that only information about the specified system be included in the
report. The sysname can be a single system name or a list of names. Use
commas to separate names in the list; do not enclose the names in
apostrophes; and do not specify a range of names. To designate system
names that begin with the same characters, use an asterisk (*) as a suffix.
The asterisk denotes zero or more characters, up to the maximum length of
the string.
An example is:
COMMAND ===> XESDATA CONNECTION SYSNAME(D13ID04)
TARGETNAME(conname)
Requests that only information about the connectors with the listed
connector names to which signals are sent be included in the report. The
conname can be a single connector name or a list of names. Use commas to
separate names in the list; do not enclose the names in apostrophes; and do
not specify a range of names. To designate connector names that begin with
the same characters, use an asterisk (*) as a suffix. The asterisk denotes zero
or more characters, up to the maximum length of the string.
An example is:
COMMAND ===> XESDATA CONNECTION TARGETNAME(MYCONNAME1)
TROPTS(tropts)
Requests that the traces included in the report be formatted and filtered as
indicated by the specified trace options. The tropts is a quoted string passed
directly to the CTRACE command processor. It can contain both standard
CTRACE options and options that are specific to the SYSXES CTRACE
component. You can include any of the standard CTRACE options (see
“CTRACE subcommand — format component trace entries” on page 108)
except the following:
– COMP
– SUB
– Address space selection parameters.
Using the CTRACE OPTIONS keyword, you can specify options specific to
the SYSXES component. Enclose the complete set of options in a double set
of parentheses. You can specify:
– The SYSXES trace categories (such as HWLAYER and REQUEST) that are
to be included in the output (see z/OS MVS Diagnosis: Tools and Service
Aids for a complete list). You can specify 0 or more trace categories,
separated by commas.
– Up to four trace filter specifications, separated by commas. A trace entry
will be included in the report if it satisfies any of the specified filters.
Each filter is of the form
ENTRYn((entryIDn,stringn,offsetn,CPUn))

378 z/OS MVS IPCS Commands

 XESDATA subcommand

where
n Index of the filter specification (1, 2, 3, or 4).
entryIDn
Trace ID to be included in the report. Specify as eight hexadecimal
digits, or omit to permit the remainder of the nth filter specification to
apply to all trace entry IDs. If omitted, the following comma is
required to indicate the absence of a positional parameter.
stringn
A trace entry will be included in the report if it contains the specified
string. Specify as a string of up to 16 hexadecimal digits, or omit to
permit the remainder of the nth filter specification to apply regardless
of trace content. If omitted, the following comma is required to
indicate the absence of a positional parameter.
offsetn
The offset at which stringn must appear within a trace entry in order
to include the entry in the trace. Specify as two hexadecimal digits, or
omit to include the trace entry if the specified string (if any) appears
at any offset within the trace. If omitted, the following comma is
required to indicate the absence of a positional parameter.
CPUn
A trace entry will be included in the report if it occurred on the
specified CPU. Specify as two hexadecimal digits, or omit to include
the trace entry regardless of the CPU on which the traced event
occurred.
An example is:
XESDATA TRACE TROPTS(’LOCAL OPTIONS((ENTRY1((09080003,02925400,2C,**))))’)
Since the syntax for specifying the filter information as a line command is
complex, it generally is generally more convenient to invoke this command
through the XESDATA panel interface.
v Example
For an example of XESDATA output, see the XES component in z/OS MVS
Diagnosis: Reference.

Chapter 5. IPCS subcommands 379

XESDATA subcommand

380 z/OS MVS IPCS Commands

Chapter 6. IPCS dialog controls
This topic describes the IPCS dialog controls. Use these controls in the IPCS
full-screen problem analysis dialog (called the IPCS dialog in this information),
except in TUTORIAL. The controls are:
v IPCS primary commands
v Line commands
v Program function (PF) keys
v Command codes
v Selection codes
v ISPF primary commands

z/OS MVS IPCS User's Guide shows and describes the IPCS dialog and tells how to
access and modify the dialog.

Using dialog controls

v Using IPCS primary commands
Enter a primary command by typing it on the command/option line, which is
the second line of a display panel, or by pressing a PF key that is defined for the
specific command. When entering more than one parameter for a command, use
either a blank or a comma as a separator. When entering more than one
command, use a semicolon to separate the commands.
The primary commands are:
Command
Function
ASCII Display ISO-8 ASCII characters
CANCEL
End the BROWSE option
CBFORMAT
Format a control block
DOWN
Scroll data forward
EBCDIC
Display EBCDIC characters
END End a subcommand or panel
EQUATE
Create a user_defined symbol
FIND Search for a specified value
IPCS Invoke an IPCS subcommand, CLIST, or REXX exec
LEFT Scroll data left
LOCATE
Scroll the display to show specific data

© Copyright IBM Corp. 1988, 2017 381

 MORE
Scroll data
OPCODE
Display mnemonic operation code
RENUM
Renumber symbol entries
RESET
Remove pending commands
RETURN
Display the IPCS Primary Option Menu
RFIND
Repeat the FIND command
RIGHT
Scroll data right
SELECT
Select a pointer to display storage
SORT Sort an IPCS-generated report
STACK
Create an IPCS-defined symbol
UP Scroll data backward
WHERE
Identify an area at a given address
v Using line commands
Enter a line command by typing the command at the beginning of a line. Enter
the first character of the command in the first column, which is blank in a
report. The second through the sixth characters of a line command, if needed,
must be typed over the next 5 columns of report text shown on the line. Because
characters in the command may match characters of report text, exercise care to
ensure that IPCS recognizes the line commands.
When entering line commands, do one of the following:
– End the line command with a delimiter character (either a blank or a special
character) that was not displayed in the report column following the line
command.
– Type the line command and press the ENTER key, leaving the cursor under
the character following the line command.
The line commands are:
Command
Function
D Delete screen output
E Edit a pointer
F Format a defined control block
I Insert a pointer
R Repeat a pointer
S Select a pointer to display storage

382 z/OS MVS IPCS Commands

 S, F, or L
Show excluded screen output
X Exclude screen output
v Using the PF keys
Certain primary commands can be invoked through the PF keys. The PF keys
are listed in the following task tables. Note that these PF key definitions can be
modified.
v Using ISPF primary commands
You can use ISPF primary commands, such as CURSOR, HELP, SPLIT, and
SWAP. See the z/OS ISPF Dialog Tag Language Guide and Reference for these
commands.

Commands, PF keys, and codes for panels

Through interactive panels, the IPCS dialog helps you to analyze, display, and
manage data from the source. From each panel, there is a certain set of analysis
tasks you may perform.

The following tables group together the tasks you can perform from each type of
panel. The IPCS dialog uses the following types of panels:
v “Selection and data entry panels”
v “Pointer and storage panels” on page 384
v “Dump display reporter panels” on page 385
v “IPCS inventory panel” on page 386
v “Storage panel” on page 386.

Note: Commands identified as IPCS in the following tables are described in this
chapter. Commands identified as ISPF are in z/OS ISPF Dialog Tag Language Guide
and Reference.

Selection and data entry panels

Table 23 summarizes the IPCS primary commands, ISPF primary commands, and
PF keys that can be used on the selection and data entry panels.
v On a selection panel, select from a list of options by entering its number on the
command/option line.
v On a data entry panel, supply parameters by filling in labeled fields. Many
fields retain previous values.
Table 23. Selection and Data Entry Panels - Commands and PF Keys
When You Want to: Enter ===> Use PF Key
Get help HELP command (ISPF) 1 or 13
Split the screen SPLIT command (ISPF) 2 or 14
End or cancel END primary command (IPCS) 3 or 15
Return to IPCS Primary Option RETURN primary command (IPCS) 4 or 16
Menu
Swap screens SWAP command (ISPF) 9 or 21
Move the cursor to the CURSOR command (ISPF) 12 or 24
command/option line
Invoke an IPCS subcommand, IPCS primary command (IPCS) —
CLIST, or REXX exec

Chapter 6. IPCS dialog controls 383

 Pointer and storage panels
Table 24 summarizes the IPCS primary commands, IPCS line commands, ISPF
primary commands, and PF keys that can be used on the pointer panels and the
storage panels.
Table 24. Pointer and Storage Panels - Commands and PF Keys
When You Want to: Enter ===> Use PF Key
Get help HELP command (ISPF) 1 or 13
Reset entered commands RESET primary command (IPCS) —
Split the screen SPLIT command (ISPF) 2 or 14
End processing END primary command (IPCS) 3 or 15
Cancel processing CANCEL primary command (IPCS) —
Return to IPCS primary option RETURN primary command (IPCS) 4 or 16
menu
Search for a value FIND primary command (IPCS) —
Repeat the FIND command RFIND primary command (IPCS) 5 or 17
Use Symbols to: STACK primary command (IPCS) 6 or 18
v Create an IPCS defined symbol
EQUATE primary command (IPCS) —
v Create a user-defined symbol
v Renumber stack entries RENUM primary command (IPCS) —

Scroll UP primary command (IPCS) 7 or 19

v Up (toward top)
DOWN primary command (IPCS) 8 or 20
v Down (toward bottom)
Swap screens. SWAP command (ISPF) 9 or 21
Display a pointer or storage LOCATE primary command (IPCS) —

SELECT primary command (IPCS)

Browse through a dump by STACK X primary command (IPCS)
positioning the cursor
LOCATE CURSOR% primary 10 or 22
To a 24-bit address; the pointer is command (IPCS)
recorded on the pointer panel
STACK X primary command (IPCS)
To a 31-bit address; the pointer is 11 or 23
recorded on the pointer panel LOCATE CURSOR? primary command
(IPCS)
Move the cursor to CURSOR command (ISPF) 12 or 24
command/option line
Format a control block CBFORMAT primary command (IPCS) —
Identify areas of storage that WHERE primary command (IPCS) —
contain an address
Invoke an IPCS subcommand, IPCS primary command (IPCS) —
CLIST, or REXX exec
Select a pointer and display S (select) line command (IPCS) —
storage addressed by that selected
pointer
Delete pointers D (delete) line command (IPCS) —
Edit a selected pointer E (edit) line command (IPCS) —

384 z/OS MVS IPCS Commands

 Table 24. Pointer and Storage Panels - Commands and PF Keys (continued)
When You Want to: Enter ===> Use PF Key
Format a pointer with a data-type F (format) line command (IPCS) —
of STRUCTURE
Insert pointers I (insert) line command (IPCS) —
Replicate existing pointers R (repeat) line command (IPCS) —

Dump display reporter panels

Table 25 summarizes the IPCS primary commands, ISPF primary commands, and
PF keys that can be used on the dump display reporter panels.
Table 25. Dump display reporter panel - commands and PF keys
When You Want to: Enter ===> Use PF Key
Get help HELP command (ISPF) 1 or 13
Reset entered commands RESET primary command (IPCS) —
Split the screen SPLIT command (ISPF) 2 or 14
End processing END primary command (IPCS) 3 or 15
Return to IPCS primary option RETURN primary command (IPCS) 4 or 16
menu
Search for a value FIND primary command (IPCS) —

Search through the IPCS output EXCLUDE primary command

stream for text (IPCS)
Repeat the FIND command RFIND primary command (IPCS) 5 or 17
Scroll 6 or 18

To next full screen MORE primary command (IPCS) 7 or 19

Up (toward top) UP primary command (IPCS) 8 or 20

Down (toward bottom) DOWN primary command (IPCS) 10 or 22

Left LEFT primary command (IPCS) 11 or 23

Right RIGHT primary command (IPCS) —

To specific data LOCATE primary command (IPCS)

Swap screens SWAP command (ISPF) 9 or 21
Move the cursor to the CURSOR command (ISPF) 12 or 24
command/option line
Format a control block CBFORMAT primary command (IPCS) —
Identify areas of storage that WHERE primary command (IPCS) —
contain an address
Invoke an IPCS subcommand, IPCS primary command (IPCS) —
CLIST, or REXX exec
Delete screen lines permanently D (delete) line command (IPCS) —
Exclude screen lines. X (exclude) line command (IPCS) —

Chapter 6. IPCS dialog controls 385

 Table 25. Dump display reporter panel - commands and PF keys (continued)
When You Want to: Enter ===> Use PF Key
Display excluded screen lines
For excluded lines S, F, or L (show) line —
For the first line of excluded text command (IPCS)
For the last line of excluded text

IPCS inventory panel

Use the 2-character command codes listed in Table 26 to manage the inventory
panel.
Table 26. Command codes to manage inventory panel
Code Function performed
BR Browse storage. This activates the BROWSE option of the IPCS dialog. You
immediately see the BROWSE option pointer panel, without having to go
through the BROWSE option entry panel first.
CL Close the source. Resources that were obtained by dump OPEN processing
are immediately released.
DD Delete the source description of the indicated source from the dump directory.
DT Delete translation records from the source description in the dump directory.
LA List the source description, with storage attributes.
LB List the source description, with record locations.
LD List the source description, with dumped storage summary.
LT List the source description, with translation results.
LZ List the source description, with all the information from the other LIST
options.
OP OPEN the source for processing.
SD Establish a data set as the default source.
XP Export dump description to RECFM = VB data set (COPYDDIR subcommand
with EXPORT option)

Storage panel
The selection codes listed in Table 27 request IPCS to:
v Interpret the word as an address in the current address space
v Place a pointer for the word in the pointer stack on the pointer panel

For use of the selection codes, see z/OS MVS IPCS User's Guide.
Table 27. IPCS selection codes
Selection code Actions by IPCS
L v Interpret the word as a low-precision (24-bit) address of storage in the
current address space.
v Place a pointer in the pointer stack on the pointer panel.
H v Interpret the word as a high-precision (31-bit) address of storage in the
current address space.
v Place a pointer in the pointer stack on the pointer panel.

386 z/OS MVS IPCS Commands

 Table 27. IPCS selection codes (continued)
Selection code Actions by IPCS
% v Interpret the word as a low-precision (24-bit) address of storage in the
current address space.
v Place a pointer in the pointer stack on the pointer panel.
v Display the addressed storage.
v If more than one % is entered, use the first one (topmost and leftmost
in the display) for the origin of the next display, and treat the rest as
though an L had been entered.
? v Interpret the word as a high-precision (31-bit) address of storage in the
current address space.
v Place a pointer in the pointer stack on the pointer panel.
v Display the addressed storage.
v If more than one ? is entered, use the first one (topmost and leftmost in
the display) for the origin of the next display, and treat the rest as
though an H had been entered.
Note: If an incorrect selection code is entered, IPCS intensifies the error field and displays
a message in the upper-right corner of the display panel.

IPCS dialog primary commands

The following sections describe the IPCS dialog primary commands.

ALIGN primary command - display data on a X'10' or X'20'

boundary
Use the ALIGN primary command to cause BROWSE option to display addresses
in the left column to be aligned on a X'10' or X'20' boundary.
v Syntax

ALIGN

v Usage notes
– ALIGN can be used only from the storage panel of the BROWSE option.
– The BROWSE option begins options displaying storage on a X'10' or X'20'
boundary (ALIGN mode).
– ALIGN is the default and persists until the NOALIGN primary command is
issued.

Example: The following screen depicts the use of the ALIGN primary command
where the addresses are on a X'10' boundary (if your screen width is less than 136)
or X'20' boundary (if your screen width is at least 136.

Chapter 6. IPCS dialog controls 387

ASCII primary command

ASID(X’000C’) ADDRESS(8FADC8.) STORAGE --------------------------------------

Command ===>
008FADC8 8EE1A800 D4E2E3D9 | ..y.MSTR |
008FADD0 68000000 008FADB0 008DBFD0 00000000 | ...........}.... |
008FADE0 008FADB0 00000000 00000000 00000000 | ................ |
008FADF0 00000000 00000000 00000000 00000000 | ................ |
008FAE00 00000000 0083D600 00000000 00000000 | .....cO......... |
008FAE10 00000000 00000000 00000000 00000000 | ................ |
008FAE20 008FB3B8 844E7DC0 044E83E0 008FF6F8 | ....d+’{.+c\..68 |
008FAE30 008FCD98 008EE638 7FFC9DE8 008FADB0 | ...q..W."..Y.... |
008FAE40 008FAFB0 008DBFC8 008EE1B8 008FCD98 | .......H.......q |
008FAE50 008FF300 00F53D00 008DAE88 844E749A | ..3..5.....hd+.. |
008FAE60 008EE638 8EE62801 000000B0 00000000 | ..W..W.......... |
008FAE70 00000000 008EE628 00100000 008FAE60 | ......W........- |
008FAE80 008FAE7C 044E83D8 00000000 008FAE90 | ...@.+cQ........ |
008FAE90 008EE0F8 8EE0E800 000000B0 00000000 | ..\8.\Y......... |

CPU(X’01’) ASID(X’0001’) ADDRESS(18.) STORAGE ------------------------------------------------------------------------------------------

Command ===>
00000018 7FFFF000 7FFFF000 | ".0.".0. |
00000020 7FFFF000 7FFFF000 7FFFF000 7FFFF000 00000000 00000000 7FFFF000 7FFFF000 | ".0.".0.".0.".0.........".0.".0. |
00000040 00000000 00000000 00000000 00FD6D58 00000000 00000000 000A0000 000140E1 | .............._............... . |
00000060 000A0000 000150E1 000A0000 000160E1 000A0000 000170E1 000A0000 000180E1 | ......&.......-................. |
00000080 00000000 00001202 00020003 00060028 00000000 00000000 00000000 00000000 | ................................ |
000000A0 0A000001 01345C08 00000048 01081401 00000000 00000000 0001000E 02372EE0 | ......*........................\ |
000000C0 18000006 00000000 FBE3FFFB FCFF4802 780C0000 00000000 00000000 00000000 | .........T...................... |
000000E0.:FF. LENGTH(X’20’)--All bytes contain X’00’

ASCII primary command — display characters as ASCII

Use the ASCII primary command to cause the BROWSE option to display ISO-8
ASCII characters in its hexadecimal and character displays.
v Syntax

ASCII

v Usage notes
– ASCII can be used only from the storage panel of the BROWSE option.
– The BROWSE option begins operation displaying EBCDIC characters.
– ASCII persists until the EBCDIC primary command is used or until you exit
the BROWSE option.

CANCEL primary command — end the BROWSE option

Use the CANCEL primary command to leave the IPCS BROWSE option panel and
return to the previous panel. Data entered on the panel is not saved.
v Syntax

{ CANCEL }
{ CAN }

v Usage notes
– CANCEL can be used only in the BROWSE option.
– If you want to leave an IPCS dialog panel and save the data entered on the
panel, use the END primary command.

CBFORMAT primary command — format a control block

Use the CBFORMAT primary command to format a control block.
v Syntax

{ CBFORMAT } data-descr
{ CBF }

data-descr
Specifies the data description parameter, which consists of three parts:

388 z/OS MVS IPCS Commands

 CBFORMAT primary command

– A symbol
– An address
– Address processing parameters
Chapter 3, “Data description parameter,” on page 17 has more information
about the use and syntax of the data description parameter.

Note: The data-descr for the CBFORMAT primary command uses only three
of the five possible parts of the data description parameter.
v Usage notes
– CBFORMAT can be used from the BROWSE option pointer and storage
panels, and from the dump display reporter panel.
– Descriptions of the control blocks that are formatted using the CBFORMAT
primary command are added to the pointer stack.
v Example: Format the CVT.
– Action
COMMAND ===> cbformat fd7bc8. str(cvt)
– Result
The CVT is formatted and displayed, and its description is added to the
pointer stack.

CONDENSE primary command - display data using

condensing technique
Use the CONDENSE primary command to cause BROWSE option to condense
output by not individually displaying data lines that are either identical or zeros.
v Syntax

CONDENSE

v Usage notes
– CONDENSE can be used only from the storage panel of the BROWSE option.
– The BROWSE option begins options displaying storage in CONDENSE mode.
– CONDENSE is the default and persists until the VERBOSE primary command
is issued.

Example: The following screen depicts the use of the CONDENSE primary
command. As seen, lines containing zeros or identical data are condenses.
ASID(X’000C’) ADDRESS(0BF29E90.) STORAGE ------------------------------------
Command ===>
0BF29E90 01010101 01010101 01010100 00010101 | ................ |
0BF29EA0.:0BF29EDF. LENGTH(X’40’)--All bytes contain X’01’
0BF29EE0 01000000 00000000 00000101 01010101 | ................ |
0BF29EF0.:0BF29EFF. LENGTH(X’10’)--Same as above
0BF29F00 01010000 00000000 00000101 01010101 | ................ |
0BF29F10 00000000 00000000 00000101 01010101 | ................ |
0BF29F20.:0BF29FDF. LENGTH(X’C0’)--All bytes contain X’01’
0BF29FE0 01000000 00000000 00000101 01010101 | ................ |
0BF29FF0.:0BF29FFF. LENGTH(X’10’)--Same as above
0BF2A000 01010000 00000000 00000101 01010101 | ................ |
0BF2A010 00000000 00000000 00000101 01010101 | ................ |
0BF2A020 47F0F114 32C1D5E3 E4C6F0F1 F64BF2F0 | .01..ANTUF016.20 |

Chapter 6. IPCS dialog controls 389

DOWN primary command

DOWN primary command — scroll data forward

Use the DOWN primary command to scroll forward toward the bottom of data.
v Syntax

DOWN [ amount ]

v Parameters
amount
Specifies one of the following scroll amounts:
– A number from 1 through 9999, representing the number of lines to be
scrolled
– PAGE or P, indicating that a full screen should be scrolled
– HALF or H, indicating that a half-screen should be scrolled
– CSR or C, indicating that the screen should be scrolled to the line on
which the cursor resides
– MAX or M, indicating that the screen should be scrolled to the bottom
– DATA or D, indicating that the screen should be scrolled a screen minus
one line
If you do not specify an amount, IPCS uses the amount in the SCROLL
amount field in the upper right corner of the screen.
v Usage notes
– DOWN can be used on all IPCS dialog panels that display the SCROLL
amount field.
– The scroll amount is typically displayed on the screen, following the
command/option field. You can change the scroll amount by typing over the
SCROLL amount field with a new amount. The new scroll amount will
remain effective (except MAX or M) until you change it or until you begin a
new function.
– You can temporarily override the scroll amount, without changing the
SCROLL amount field, by:
- Typing an amount as part of the scroll command and pressing the ENTER
key
- Typing a scroll amount in the command/option field, and then pressing
PF8 or PF20
– The IPCS-defined PF keys 8 and 20 invoke the DOWN primary command.
v Example: Scroll using the DATA value.
– Action
COMMAND ===> down data
or
COMMAND ===> down d
– Result
The screen is scrolled toward the bottom of the data by a screen minus one
line.

EBCDIC primary command — display characters as EBCDIC

Use the EBCDIC primary command to cause the BROWSE option to display
EBCDIC characters in its hexadecimal and character displays.

390 z/OS MVS IPCS Commands

 EBCDIC primary command

v Syntax

EBCDIC

v Usage notes
– EBCDIC can be used only from the storage panel of the BROWSE option.
– The BROWSE option begins operation displaying EBCDIC characters.
– EBCDIC persists until the ASCII primary command is used or until you exit
the BROWSE option.

END primary command — end a subcommand or panel

Use the END primary command to leave an IPCS dialog panel and return to the
previous panel. All data entered on the panel is saved.
v Syntax

END

v Usage notes
– END can be used in all IPCS dialog options.
– The IPCS-defined PF keys 3 and 15 invoke the END primary command.

EQUATE primary command — create a user-defined symbol

Use the EQUATE primary command to create a user-defined symbol in the symbol
table and to associate an address and address processing parameters with the
symbol. If the specified symbol already exists in the symbol table, the new address
and address processing parameters overlay the previous information.
v Syntax

{ EQUATE } symbol
{ EQU }
{ EQ }
[ data-descr | X ]

v Parameters
symbol
Specifies the symbol being defined. When specifying symbol, do not include
the ampersand (&) or the period (.) that are normally part of symbolic
notation. The symbol is 1 through 31 alphanumeric characters; the first
character must be a letter or one of the following characters:
$ (X’5B’)
# (X’7B’)
@ (X’7C’)
data-descr or X
Specifies the data description parameter, which consists of two parts:
– An address
– Address processing parameters

Chapter 6. IPCS dialog controls 391

EQUATE primary command

Chapter 3, “Data description parameter,” on page 17 has more information

about the syntax and use of the data description parameter. If you omit the
data description parameter, the default is X, the current address.
v Usage notes
– EQUATE can be used only in the BROWSE option.
– There are two special symbols, CURSOR and X, that are accepted in the
BROWSE option on the storage panel. These symbols associate a location in a
dump and are used in the same manner as other symbols, such as the CVT
and TCB symbols.
- CURSOR indicates the word of storage at which you position the cursor.
By placing the cursor in the selection field preceding a word of storage or
by placing the cursor under a word of storage, you can reference the word
of storage. CURSOR is not in effect if the position of the cursor does not
identify a word of storage or if you leave the storage panel.
- X indicates the starting address of the data displayed on the storage panel.
X remains in effect even if you leave the storage panel.
– To add your user-defined symbol to the address pointer stack on the pointer
panel of the BROWSE option, use the STACK primary command.
v Example 1: Set X to a specific address.
– Action
COMMAND ===> equate X 522836
– Result
X, the current address, becomes X‘522836’.
v Example 2: Equate a specific address to a user-defined symbol.
– Action
COMMAND ===> equate failingtcb 51368.
– Result
A symbol table entry is created for FAILINGTCB and is identified at address
X‘51368’.

EXCLUDE primary command — exclude lines from display

Use the EXCLUDE primary command to search through visible (not excluded
already) IPCS output stream text for a specified value. When that value is found,
mark the line(s) containing the value as excluded.

All options of the EXCLUDE primary command are similar to those supported by
the FIND primary command – and very similar to the EXCLUDE primary
command supported by ISPF EDIT and VIEW. No option is supported to search
already excluded lines of a report.
v Syntax

EXCLUDE { relational-operator }
EX value
X { column { column } }
{ ALL }
{ FIRST }
{ LAST }
{ NEXT }
{ PREVIOUS }

v Usage notes
When EXCLUDE processing is successful, the following actions take place:
392 z/OS MVS IPCS Commands
 EXCLUDE primary command

– The line immediately preceding the first one excluded is displayed. The "Top
of Data" line may be shown if the line was the first in the report. This
behavior is similar to that exhibited by the EXCLUDE primary command of
ISPF EDIT and VIEW.
– An ISPF "n lines excluded" message will be shown.

FIND primary command — search for a specified value

Use the FIND primary command to search through all dump output for a single
occurrence of a specified value.
v Syntax
The syntax of the FIND primary command varies depending on whether you are
in the BROWSE option or any other option except TUTORIAL.
– Syntax for the BROWSE Option

{ FIND } [ relational-operator ]
{ F }
value
[ BOUNDARY(bdy [,index]) ]
[ BREAK | NOBREAK ]
[ MASK(mask) | NOMASK ]
[ FIRST ]
[ LAST ]
[ NEXT ]
[ PREVIOUS ]

– Syntax for searching the IPCS output stream

{ FIND } [ relational-operator]
{ F }
value
[ col [ col ]]
[ ALL ]
[ FIRST ]
[ LAST ]
[ NEXT ]
[ PREVIOUS ]
[ X ]
[ NX ]

v Parameters
relational-operator
Specifies one of the following symbolic or programming operators to be
used with the value operand:
[<|LT|<=|LE|¬>|NG|=|EQ|>=|&cont;
GE|¬<|NL|>|GT|¬=|NE]

Note: If a programming relational-operator is entered alone, such as FIND

EQ, IPCS interprets EQ not as a search value but as an operator and does
not perform a search. Enter the command with a relational-operator and a
value. For example, FIND EQ EQ causes IPCS to search for an occurrence of
EQ.
value
Specifies the general value that IPCS is to search for. See “General values”
on page 10 for more information, the syntax, and examples.

Chapter 6. IPCS dialog controls 393

FIND primary command

col [col ]
Specifies that FIND is to limit the search to specified columns. When
entering a single column number, the value must start in the specified
column. When entering a pair of column numbers, indicating the first and
last columns to be searched, the string is found if it is completely contained
within the designated columns. The column range is 1 through 250. The
default is 1.
BOUNDARY(bdy[,index])
Specifies that IPCS is to divide storage into strings bdy bytes in length. The
address of each string is divisible by bdy. FIND performs only one
comparison with data whose first byte lies within any string. The
abbreviation BDY is accepted for this parameter.
The index value designates which byte in the string FIND is to select. The
index can be a single value or a range, with the first and last values
separated by a colon. For example:
BDY(1) or BDY(1,1) or BDY(1,1:1)
FIND examines each byte.
BDY(2) or BDY(2,1) or BDY(2,1:1)
FIND performs comparisons with strings originating at even-numbered
addresses.
BDY(2,2) or BDY(2,2:2)
FIND performs comparisons with strings originating at odd-numbered
addresses.
BDY(5,5) or BDY(5,5:5)
FIND performs comparisons only with strings originating at addresses 4
bytes past an address divisible by 5.
BDY(7,6:7)
FIND performs comparisons only with strings originating at addresses 5
or 6 bytes past an address divisible by 7.
BDY(8) or BDY(8,1) or BDY(8,1:1)
FIND performs comparisons only with strings aligned on doubleword
boundaries.
Both bdy and index can be 1 through 2 raised to the thirty-first power 231 and
can be expressed in decimal, hexadecimal (X'xxx...'), or binary (B'bbb...')
notation.
When you specify this option, it remains in effect until you specify a new
search argument or you override this option. If you enter a new search
argument and omit BDY, the default is BDY(1,1).
BREAK
NOBREAK
BREAK specifies that FIND is to stop processing if it cannot retrieve storage
from the dump to continue the search. This happens if the required storage
was not acquired through the GETMAIN macro or the required storage is
not contained in the dump.
NOBREAK specifies that FIND is to continue processing if it cannot retrieve
storage from the dump. FIND continues the search with the next available
address in the dump.

394 z/OS MVS IPCS Commands

 FIND primary command

When you specify this option, it remains in effect until you specify a new
search argument or you override this option. If you enter a new search
argument and omit NOBREAK, the default is BREAK.
MASK(mask)
NOMASK
MASK defines a value that is logically ANDed with both operands before
performing the comparison. The mask must be the same size as the data
items being compared. The mask is specified using the same value notation
used for either operand. See Chapter 2, “Literal values,” on page 9 for more
information.
NOMASK suppresses masking.
ALL
FIRST
LAST
NEXT
PREVIOUS
ALL specifies that a search for all occurrences is to be done. A message "n
matches found" will display the number of matches found. Enter the HELP
primary command immediately to see a longer message showing both the
search argument and the number of matches to be shown.
FIRST specifies that a search for the first occurrence of the value is to be
done. The search starts at the beginning of the displayed report or address
space; the search finishes at the end of the report or address space.
LAST specifies that a search for the last occurrence of the value is to be
done. The search starts at the end of the displayed report or address space;
the search finishes at the beginning of the report or address space.
NEXT specifies that a search for the next occurrence of the value is to be
done. The search starts at the beginning of the line being displayed (if the
cursor is on the command/option line), or at the cursor location (if the
cursor is within the data display area). The search finishes at the end of the
displayed report or address space.
PREVIOUS specifies that a search for the previous occurrence of the value is
to be done. The search starts at the end of the line preceding the first line
being displayed (if the cursor is on the command/option line), or at the
cursor location (if the cursor is within the data display area). The search
finishes at the beginning of the displayed report or address space. The
abbreviation PREV is accepted for this parameter.
v Usage notes
– FIND can be used in all options except TUTORIAL. Note that the syntax
varies depending on which option you are using.
– The starting point for the search initiated by the FIND primary command
depends on the command parameters that control the direction of the search
(FIRST, LAST, NEXT, PREVIOUS) and on the position of the cursor.
– Use the RFIND primary command (PF key 5 or 17) to continue the search for
the specified argument.
v Example 1: Search for a value in columns 1 through 9.
– Action
COMMAND ===> find abc 1 9
– Result

Chapter 6. IPCS dialog controls 395

FIND primary command

FIND searches for the value abc only in columns 1 through 9. When found,
the value is intensified.
v Example 2: Find a search argument repeatedly.
– Action
The following screens depict use of the FIND and RFIND primary commands.
Figure 38 shows the FIND command entered on the COMMAND line to
search through the display and find the first occurrence of the search
argument “dsp”.

IPCS OUTPUT STREAM ------------------------------------------ LINE 0 COLS 1 78

---------------------
|COMMAND ===> f dsp_ | SCROLL ===> CSR
---------------------
****************************** TOP OF DATA ***********************************

* * * * K E Y F I E L D S * * * *
JOBNAME RASP
SELECTED BY: CURRENT

ASCB: 00F09E00
FWDP..... 00F09C00 ASID..... 0003 TRQP..... 80F09301
CSCB..... 00F1D3C8 TSB...... 00000000 AFFN..... FFFF
ASXB..... 00AFDF00 DSP1..... 00 FLG2..... C4
SRBS..... 0000 LOCK..... 00000000 ASSB..... 01AB6D00

TCB: 00AFE178
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 00AFD300 NDSP..... 00000000
JSCB..... 00AFDD84 BITS..... 00000000 DAR...... 00
RTWA..... 00000000 FBYT1.... 00
Task non-dispatchability flags from TCBFLGS4:
Top RB is in a wait

PRB: 00AFDD60
WLIC..... 00020001 FLCDE.... 00C12630 OPSW..... 070C1000 810D7C20

Figure 38. Using FIND on the Dump Display Reporter Panel

– Result
Figure 39 on page 397 shows the results of the FIND command. IPCS
highlights the line that contains the search argument, positions the cursor at
the beginning of the search argument, and displays a message in the upper
right corner of the display indicating in which line and column the argument
was found.
Figure 40 on page 397 is a result of pressing PF5 to invoke the RFIND
command. This screen displays the next occurrence of the search argument
following the position of the cursor. Notice that the display message is
changed, reflecting a newly found search argument.

396 z/OS MVS IPCS Commands

 FIND primary command

IPCS OUTPUT STREAM ----------------------------------- FOUND IN LINE 16 COL 17

COMMAND ===> SCROLL ===> CSR
****************************** TOP OF DATA ***********************************

* * * * K E Y F I E L D S * * * *
JOBNAME RASP
SELECTED BY: CURRENT

ASCB: 00F09E00
FWDP..... 00F09C00 ASID..... 0003 TRQP..... 80F09301
CSCB..... 00F1D3C8 TSB...... 00000000 AFFN..... FFFF
----------------------------------------------------------------------
| ASXB..... 00AFDF00: DSP1..... 00 FLG2..... C4 |
----------------------------------------------------------------------
SRBS..... 0000 LOCK..... 00000000 ASSB..... 01AB6D00

TCB: 00AFE178
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 00AFD300 NDSP..... 00000000
JSCB..... 00AFDD84 BITS..... 00000000 DAR...... 00
RTWA..... 00000000 FBYT1.... 00
Task non-dispatchability flags from TCBFLGS4:
Top RB is in a wait

PRB: 00AFDD60
WLIC..... 00020001 FLCDE.... 00C12630 OPSW..... 070C1000 810D7C20

Figure 39. Result of Using FIND

IPCS OUTPUT STREAM ----------------------------------- FOUND IN LINE 16 COL 39

COMMAND ===> SCROLL ===> CSR
****************************** TOP OF DATA ***********************************

* * * * K E Y F I E L D S * * * *
JOBNAME RASP
SELECTED BY: CURRENT

ASCB: 00F09E00
FWDP..... 00F09C00 ASID..... 0003 TRQP..... 80F09301
CSCB..... 00F1D3C8 TSB...... 00000000 AFFN..... FFFF
ASXB..... 00AFDF00 DSP1..... 00 FLG2..... C4
SRBS..... 0000 LOCK..... 00000000 ASSB..... 01AB6D00

TCB: 00AFE178
---------------------------------------------------------------------------
| CMP...... 00000000 PKF...... 00 LMP..... FF DSP.....FF|
---------------------------------------------------------------------------
TSFLG.... 00 STAB..... 00AFD300 NDSP..... 00000000
JSCB..... 00AFDD84 BITS..... 00000000 DAR...... 00
RTWA..... 00000000 FBYT1.... 00
Task non-dispatchability flags from TCBFLGS4:
Top RB is in a wait

PRB: 00AFDD60
WLIC..... 00020001 FLCDE.... 00C12630 OPSW..... 070C1000 810D7C20

Figure 40. Result of Using PF5/RFIND

IPCS primary command — invoke an IPCS subcommand,

CLIST, or REXX exec
Use the IPCS primary command to invoke an IPCS subcommand, CLIST, or REXX
exec from any of the panels of the IPCS dialog. The subcommand, CLIST, or REXX
exec is entered exactly as though it was being invoked under IPCS in line mode. If
the subcommand, CLIST, or REXX exec sends a report to the terminal, you view
the report using the dump display reporter panel.

Chapter 6. IPCS dialog controls 397

IPCS primary command

Note: Do not use the IPCS primary command to invoke a CLIST that contains a
combination of a TSO/E CLIST function, such as SYSOUTTRAP, and an authorized
TSO/E command, such as LISTD. Such a CLIST should be invoked only in IPCS
line or batch mode or in a TSO/E environment.
v Syntax

IPCS { subcommand }
IP { clist }
{ rexx-exec }

v Parameters
subcommand
Specifies the IPCS subcommand to be run.
clist
Specifies the CLIST to be run.
rexx-exec
Specifies the REXX exec to be run.
v Usage notes
– The IPCS primary command can be used in all options except TUTORIAL.
– There are two special symbols, CURSOR and X, that are accepted in the
BROWSE option on the storage panel. These symbols are associated with a
location in a dump and are used in the same manner as other symbols, such
as the CVT and TCB symbols. These symbols affect how the subcommand,
CLIST, or REXX exec processes.
- CURSOR indicates the word of storage at which you position the cursor.
By placing the cursor in the selection field preceding a word of storage or
by placing the cursor under a word of storage, you can reference the word
of storage. CURSOR is not in effect if the position of the cursor does not
identify a word of storage or if you leave the storage panel.
- X indicates the starting address of the data displayed on the storage panel.
X remains in effect even if you leave the storage panel.
– If before entering this command you were processing the overriding dump
source (as noted on the entry panel of the Browse option), IPCS will not
process that dump source but will instead process the current default dump
source.
v Example 1: Change the SETDEF default parameters.
– Action
COMMAND ===> ipcs setdef print
– Result
While in the BROWSE option, this command invokes the SETDEF
subcommand to override the existing message routing default parameters.
v Example 2: Locate a module and display its storage.
– Action
COMMAND ===> ipcs findmod iefbr14 noverify
– Result
While in the BROWSE option on the storage panel, FINDMOD locates
module IEFBR14, modifies X (the current address), and scrolls the storage
containing the module into view.
v Example 3: Display an array.

398 z/OS MVS IPCS Commands

 IPCS primary command

– Action
COMMAND ===> ipcs list x unsigned dim(5)
– Result
While in the BROWSE option on the storage panel, LIST displays an array of
5 unsigned numbers whose first entry occupies the current address, X. The
unsigned operand translates the numbers to decimal and displays the
numbers on the dump display reporter panel.

LEFT primary command — scroll data left

Use the LEFT primary command to scroll toward the first, or left-most, column of
the data.
v Syntax

LEFT [ amount ]

v Parameter
amount
Specifies one of the following scroll amounts:
– A number from 1 through 9999, representing the number of columns to be
scrolled
– PAGE or P, indicating that a full screen should be scrolled
– HALF or H, indicating that a half-screen should be scrolled
– CSR or C, indicating that the screen should be scrolled to the position on
which the cursor resides
– MAX or M, indicating that the screen should be scrolled to the left margin
– DATA or D, indicating that the screen should be scrolled a page minus
one column
If you do not specify an amount, IPCS uses the amount in the SCROLL
amount field in the upper right corner of the screen.
v Usage notes
– LEFT can be used on all IPCS dialog panels that display the SCROLL amount
field.
– The scroll amount is typically displayed on the screen, following the
command/option field. You can change the scroll amount by typing over the
SCROLL amount field with the new amount. The new scroll amount will
remain effective (except MAX or M) until you change it or until you begin a
new function.
– You can temporarily override the scroll amount, without changing the
SCROLL amount field, by:
- Typing an amount as part of the scroll command and pressing the ENTER
key
- Typing a scroll amount in the command/option field and then pressing
PF10 or PF22
– The IPCS-defined PF keys 10 and 22 invoke the LEFT primary command.
v Example: Scroll using the cursor value.
– Action
One of the following:

Chapter 6. IPCS dialog controls 399

LEFT primary command

COMMAND ===> left csr

COMMAND ===> left c
– Result
The panel is scrolled to the position of the cursor within the data.

LOCATE primary command — scroll the display to show

specific data
Use the LOCATE primary command to:
v Scroll to a particular line in the report while on the dump display reporter
panel.
v Locate a particular pointer while in the BROWSE option on the pointer panel.
v View a storage location while in the BROWSE option on the storage panel.
v Syntax

{ LOCATE } relative-line-number
{ LIST } pointer-number
{ LOC } data-descr
{ L }

v Parameters
relative-line-number
Indicates which line in the dump display reporter panel should be scrolled
to the top of the screen. The relative-line-number is a decimal number.
Use relative-line-number only on a dump display reporter panel.
pointer-number
Causes the indicated pointer to be scrolled to the top of the pointer stack on
the pointer panel. The pointer-number is a symbol entry and can be entered
without leading zeros.
Use pointer-number only on the pointer panel of the BROWSE option.
data-descr
Specifies the data description parameter, which consists of two parts:
– An address
– Address processing parameters
LOCATE an address can only be used in a BROWSE option storage panel.
Chapter 3, “Data description parameter,” on page 17 explains the use and
syntax of the data description parameter. However, the following exceptions
apply to the LOCATE primary command only:
– There are two special symbols, CURSOR and X, that are accepted in the
BROWSE option on the storage panel. These symbols associate a location
in a dump and are used in the same manner as other symbols, such as
the CVT and TCB symbols.
- CURSOR indicates the word of storage at which you position the
cursor. By placing the cursor in the selection field preceding a word of
storage or by placing the cursor under a word of storage, you can
reference the word of storage. CURSOR is not in effect if the position of
the cursor does not identify a word of storage or if you leave the
storage panel.
- X indicates the starting address of the data displayed on the storage
panel. X remains in effect even if you leave the storage panel.
400 z/OS MVS IPCS Commands
 LOCATE primary command

While browsing through a dump, use the IPCS-defined PF keys:

– 10 or 22 to invoke the primary command chain, STACK X; LOCATE
CURSOR%
The % selection code indicates a 24-bit address of storage.
– 11 or 23 to invoke the primary command chain, STACK X; LOCATE
CURSOR?
The ? selection code indicates a 31-bit address of storage.
STACK X requests that an entry to the address pointer stack on the pointer
panel be added with the address contained in the word of storage indicated
by the cursor's current position.
LOCATE CURSOR requests that IPCS locate and display the data found at
the address contained in the word of storage indicated by the cursor's
current position.
v Example 1: Display a specific line number on a dump display reporter panel.
– Action
COMMAND ===> locate 14
– Result
After pressing the ENTER key, line 14 is scrolled to the top of the screen.
v Example 2: Display a specific pointer on the pointer panel of the BROWSE
option.
– Action
COMMAND ===> locate 33
– Result
After pressing the ENTER key, IPCS displays pointer 33 in the address
pointer stack.
v Example 3: Display a literal address on a BROWSE option storage panel.
– Action
COMMAND ===> locate 0.
– Result
IPCS displays the literal request for location X‘0’.
v Example 4: Display a symbolic address on a BROWSE option storage panel.
– Action
COMMAND ===> list cvt
– Result
IPCS displays the symbolic request for the storage described by the symbol
CVT. Note that:
- Symbol CVT and numerous other IPCS symbols describe blocks of storage
including a prefix, storage preceding the nominal address of the
communications vector table. IPCS shows the prefix when such a block is
requested.
- Symbol ASVT and other IPCS symbols describe blocks of storage whose
nominal address precedes the first byte of storage occupied by the block.
IPCS begins the display at the physical origin of the block.
In all situations involving a symbolic description, IPCS attempts to begin the
display at the physical origin of the block described by the symbol.
v Example 5: Display a general purpose register on a BROWSE option storage
panel.
– Action

Chapter 6. IPCS dialog controls 401

LOCATE primary command

COMMAND ===> locate 1r

– Result
IPCS displays general purpose register 1.
v Example 6: Display an indirect address on a BROWSE option storage panel.
– Action
COMMAND ===> locate 10.%?
– Result
IPCS displays the storage accessed by both:
- The 24-bit pointer at location X'10'
- The 31-bit pointer addressed by the first pointer
v Example 7: Display an indirect address on a BROWSE option storage panel.
– Action
COMMAND ===> loc cvt+24n%
– Result
IPCS displays the storage accessed by the 24-bit pointer at decimal offset 8 in
the storage described by the symbol CVT.
v Example 8: Display a symbolic address and an ASID on a BROWSE option
storage panel.
– Action
COMMAND ===> loc private asid(57)
– Result
IPCS displays the storage in the private area for address space 57.

MORE primary command — scroll data

Use the MORE primary command to scroll to the next full screen of data or the
end of data. MORE can be used on all IPCS dialog panels that display the scroll
amount field in the upper right corner of the screen.
v Syntax

MORE

OPCODE primary command — display operation code

Use the OPCODE primary command to display one of the following mnemonic
operation codes:
v An instruction explicitly entered as a search-argument on the OPCODE primary
command.
v The operation code of the instruction identified by the cursor position when the
cursor is placed over the specific halfword where the instruction of interest
originates.
v The operation code beginning in the first halfword shown on the screen when
the previous means to identify the instruction of interest have not been used.
v Syntax

OPCODE [search-argument]

v Parameter

402 z/OS MVS IPCS Commands

 OPCODE primary command

search-argument
The hexadecimal digits representing the instruction of interest. If less digits
are entered than needed to complete an instruction, trailing zero digits are
supplied.
v Usage notes
– OPCODE can be entered while viewing the storage panel of the IPCS dialog
browse option.

NOALIGN primary command — display data without aligning

Use the NOALIGN primary command to cause the BROWSE option to display
addresses in the left column not to be aligned on a X'10' or X'20' boundary.
v Syntax

NOALIGN

v Usage notes
– NOALIGN can be used only from the storage panel of the BROWSE option.
– The BROWSE option begins options displaying storage in a X'10' or X'20'
boundary (ALIGN mode).
– NOALIGN persists until the ALIGN primary command is issued or until you
exit the BROWSE option.
– If you scroll past an area of unavailable storage while in NOALIGN mode,
the display becomes aligned again. Changing your location to an unaligned
address will return to a NOALIGN display.

Example: The following screen depicts the use of the NOALIGN primary
command where the addresses are not on a X'10' boundary (if your screen width is
less than 136) or X'20' boundary (if your screen width is at least 136).

ASID(X’000C’) ADDRESS(8FADC8.) STORAGE --------------------------------------

Command ===>
008FADC8 8EE1A800 D4E2E3D9 68000000 008FADB0 | ..y.MSTR........ |
008FADD8 008DBFD0 00000000 008FADB0 00000000 | ...}............ |
008FADE8 00000000 00000000 00000000 00000000 | ................ |
008FADF8 00000000 00000000 00000000 0083D600 | .............cO. |
008FAE08 00000000 00000000 00000000 00000000 | ................ |
008FAE18 00000000 00000000 008FB3B8 844E7DC0 | ............d+’{ |
008FAE28 044E83E0 008FF6F8 008FCD98 008EE638 | .+c\..68...q..W. |
008FAE38 7FFC9DE8 008FADB0 008FAFB0 008DBFC8 | "..Y...........H |
008FAE48 008EE1B8 008FCD98 008FF300 00F53D00 | .......q..3..5.. |
008FAE58 008DAE88 844E749A 008EE638 8EE62801 | ...hd+....W..W.. |
008FAE68 000000B0 00000000 00000000 008EE628 | ..............W. |
008FAE78 00100000 008FAE60 008FAE7C 044E83D8 | .......-...@.+cQ |
008FAE88 00000000 008FAE90 008EE0F8 8EE0E800 | ..........\8.\Y. |

CPU(X’01’) ASID(X’0001’) ADDRESS(18.) STORAGE -----------------------------------------------------------------------------------------

Command ===>
00000018 7FFFF000 7FFFF000 7FFFF000 7FFFF000 7FFFF000 7FFFF000 00000000 00000000 | ".0.".0.".0.".0.".0.".0......... |
00000038 7FFFF000 7FFFF000 00000000 00000000 00000000 00FD6D58 00000000 00000000 | ".0.".0..............._......... |
00000058 000A0000 000140E1 000A0000 000150E1 000A0000 000160E1 000A0000 000170E1 | ...... .......&.......-......... |
00000078 000A0000 000180E1 00000000 00001202 00020003 00060028 00000000 00000000 | ................................ |
00000098 00000000 00000000 0A000001 01345C08 00000048 01081401 00000000 00000000 | ..............*................. |
000000B8 0001000E 02372EE0 18000006 00000000 FBE3FFFB FCFF4802 780C0000 00000000 | .......\.........T.............. |
000000D8.:F7. LENGTH(X’20’)--All bytes contain X’00’

RENUM primary command — renumber symbol entries

Use the RENUM primary command to renumber all address pointer entries on the
pointer panel of the BROWSE option in ascending order from 00001 through 99999.
RENUM processing automatically renumbers the address pointer entries in the
symbol table in your user dump directory in ascending order from Z1 through
Z99999.

If there are any unused numbers after renumbering the symbols, RENUM
eliminates these numbers and permits the STACK primary command to add more

Chapter 6. IPCS dialog controls 403

RENUM primary command

entries to the address pointer stack of the pointer panel in the BROWSE option and
to the address pointer stack in the symbol table.
v Syntax

{ RENUM }
{ REN }

v Usage notes
– RENUM can be used only in the BROWSE option.

REPORT primary command — process IPCS output streams

Use the REPORT primary command when viewing an IPCS output stream to
initiate processing of report text. REPORT initiates a line mode session similar to
that initiated by the IPCS primary command except that the list of subcommand
accepted differs.
v Syntax

VERB OPERANDS
REPORT { subcommand }
RPT { clist }
{ rexx-exec }

v Usage notes
– This session is run with ISPF application ID ISR in effect. This activates any
personalized program function key definitions and other defaults that you
have defined during normal use of BROWSE and VIEW services.
– IPCS adds lines of output to an output stream incrementally, based on the last
line that you have viewed. When the REPORT primary command is used,
IPCS makes the current output stream available to it. In the following
discussion of the REPORT primary command, the term entire report refers to
all lines in the output stream at the time the primary command is requested.
If you want to have the primary command run against a completed report,
you must first use primary command DOWN MAX or its equivalent.
– The following subcommands are available during a REPORT session:
- BROWSE (alias B) — Use the BROWSE subcommand of REPORT to display
some or all lines of a report using ISPF BROWSE. BROWSE processing will
be performed with the application ISR command table and program
function key definitions in effect.
v Syntax of BROWSE

VERB OPERANDS
BROWSE [ line-number[:line-number] ]
B [ relative-report-number | 1 ]
------ SETDEF-Defined Parameter --------------
Note: You can override the following SETDEF parameter. See “SETDEF
subcommand — set defaults” on page 262.[ TEST | NOTEST ]

line-number[:line-number]
This option explicitly specifies the range of lines to be browsed. The
default is the entire report being referenced. The end of the range

404 z/OS MVS IPCS Commands

 REPORT primary command

may be overstated to request all lines beginning with the first to be

browsed. The initial line in a report is always line 1.
relative-report-number
This operand specifies the report number. Report 0 is reserved for
terminal output produced by the REPORT command itself. Report 1,
the default, is the report being viewed at the time that the REPORT
primary command was entered. Reports nested, if any, under the
current ISPF logical screen are numbered from 2 onward.

- CLOSE
- END
- EVALRPT
Use EVALRPT to copy information about one line in a report to a
command procedure variable. The intended use for EVALRPT is where the
common actions anticipated by IPCS are not appropriate or require
embellishment.
For example, if you combine NOTE with some command procedure logic, a
report copied to IPCSPRNT can have one or more IPCSTOC entries added
to identify pages where significant data starts.
EVALRPT will be rejected if an attempt is made to invoke it directly using
the REPORT primary command.
v Syntax of EVALRPT

VERB OPERANDS
EVALRPT [ line-number | 1 ]
[ relative-report-number | 1 ]]
{ CLIST(variable-list) }
{ DIALOG(variable-list) }
{ REXX(variable-list) )

line-number
This operand specifies the line being referenced. Lines are numbered
sequentially beginning with 1.
relative-report-number
This operand specifies the report number. Report 0 is reserved for
terminal output produced by the REPORT command itself. Report 1,
the default, is the report being viewed at the time that the REPORT
primary command was entered. Reports nested, if any, under the
current ISPF logical screen are numbered from 2 onward.
CLIST(variable-list)
DIALOG(variable-list)
REXX(variable-list)
This operand specifies the data to be accessed and used to update
command procedure variables.
v Syntax of EVALRPT variable-list

LINEMAX(variable-name)
REPORTMAX(variable-name)
TEXT(variable-name)
VISIBILITY(variable-name)

Chapter 6. IPCS dialog controls 405

REPORT primary command

LINEMAX(variable-name)
This option returns the number of lines in the referenced report.
Partially-viewed reports may not be extended during processing of
the REPORT primary command. Only those lines already written are
accessible.
REPORTMAX(variable-name)
This option returns the number of reports nested under the logical
screen when the REPORT primary command was entered.
TEXT(variable-name)
This option returns the text of the referenced line in the report. Note:
CLIST(variable-name) is supported but not recommended for
processing of a REPORT primary command. Processing free-form
text in a CLIST is feasible but requires considerable expertise.
VISIBILITY(variable-name)
This option returns VISIBLE or EXCLUDED.
- HELP (alias H)
- IPCSPRNT– Use the IPCSPRNT subcommand of REPORT to copy some or
all lines of a report to the IPCS print file. If any lines are longer than the
print file line size, they are truncated.
v Syntax of IPCSPRNT

VERB OPERANDS
IPCSPRNT [ line-number[:line-number] ]
[ relative-report-number | 1 ]
[ EXCLUDE( SUMMARIZE | DISPLAY | OMIT ) ]
------ SETDEF-Defined Parameter --------------
Note: You can override the following SETDEF parameter. See “SETDEF
subcommand — set defaults” on page 262.

line-number[:line-number]
This option explicitly specifies the range of lines to be browsed. The
default is the entire report being referenced. The end of the range
may be overstated to request for all lines beginning with the first to
be browsed. The initial line in a report is always line 1.
relative-report-number
This operand specifies the report number. Report 0 is reserved for
terminal output produced by the REPORT command itself. Report 1,
the default, is the report being viewed at the time that the REPORT
primary command was entered. Reports nested, if any, under the
current ISPF logical screen are numbered from 2 onward.
EXCLUDE(SUMMARIZE)
EXCLUDE(DISPLAY)
EXCLUDE(OMIT)
The EXCLUDE option specifies the treatment of lines within the
selected range that have been excluded from display on the screen.
– EXCLUDE(SUMMARIZE), the default, places one line into the
print file for each group of excluded lines encountered. The line
indicates the number of excluded lines within the selected range
of lines that were in exclude.
– EXCLUDE(DISPLAY) prints the excluded lines/

406 z/OS MVS IPCS Commands

 REPORT primary command

– EXCLUDE(OMIT) neither shows nor summarizes excluded lines,

printing only those lines visible.
Visible lines within the selected range are always printed as shown.
- ISPEXEC
- NOTE (alias N)
- OPEN
- VIEW (alias V) — Use the VIEW subcommand of REPORT to display some
or all lines of a report using ISPF VIEW. VIEW processing will be
performed with the application ISR command table and program function
key definitions in effect. Both visible and excluded lines within the selected
range are initially made visible in VIEW.
v Syntax of VIEW

VERB OPERANDS
VIEW [ line-number[:line-number] ]
V [ relative-report-number | 1 ]
------ SETDEF-Defined Parameter --------------
Note: You can override the following SETDEF parameter. See “SETDEF
subcommand — set defaults” on page 262.[ TEST | NOTEST ]

line-number[:line-number]
This option explicitly specifies the range of lines to be browsed. The
default is the entire report being referenced. The end of the range
may be overstated to request for all lines beginning with the first to
be browsed. The initial line in a report is always line 1.
relative-report-number
This operand specifies the report number. Report 0 is reserved for
terminal output produced by the REPORT command itself. Report 1,
the default, is the report being viewed at the time that the REPORT
primary command was entered. Reports nested, if any, under the
current ISPF logical screen are numbered from 2 onward.
END, ISPEXEC, and NOTE subcommands act the same way they do in a line
mode IPCS session. You should rarely need to enter END.
v Example: REPORT VIEW will display the entire current report using ISPF VIEW
and return to the original context when that viewing has been completed.

RESET primary command — remove pending commands

Use the RESET primary command to remove all pending primary and line
commands. After pressing the ENTER key, you can start to enter commands again.
v Syntax

RESET

v Usage notes
– RESET can be used in all IPCS dialog options (on selected panels) except
TUTORIAL.

Chapter 6. IPCS dialog controls 407

RETURN primary command

RETURN primary command — display the IPCS primary

option menu
Use the RETURN primary command to return directly to the IPCS primary option
menu, bypassing all intermediate panels.
v Syntax

RETURN

v Usage notes
– RETURN can be used in all IPCS dialog options.
– The IPCS-defined PF keys 4 and 16 invoke the RETURN primary command.

RFIND primary command — repeat the FIND command

Use the RFIND primary command to repeat a search at the location following the
position of the cursor. The search is for a single occurrence of a value that was
previously entered with the FIND command.
v Syntax

RFIND

v Usage notes
– RFIND can be used in all IPCS dialog options (on selected panels) except
TUTORIAL.
– The IPCS-defined PF keys 5 and 17 invoke the RFIND primary command.
See the FIND primary command for an example.

RIGHT primary command — scroll data right

Use the RIGHT primary command to scroll toward the last, or right-most, column
of the data.
v Syntax

RIGHT [ amount ]

amount
Specifies one of the following scroll amounts:
– A number from 1 through 9999, representing the number of columns to be
scrolled
– PAGE or P, indicating that a full screen should be scrolled
– HALF or H, indicating that a half-screen should be scrolled
– CSR or C, indicating that the screen should be scrolled to the position on
which the cursor resides
– MAX or M, indicating that the screen should be scrolled to the right
margin
– DATA or D, indicating that the screen should be scrolled a page minus
one column

408 z/OS MVS IPCS Commands

 RIGHT primary command

If you do not specify an amount, IPCS uses the amount in the SCROLL
amount field in the upper right corner of the screen.
v Usage notes
– RIGHT can be used on all IPCS dialog panels that display the SCROLL
amount field.
– The scroll amount is typically displayed on the screen, following the
command/option field. You can change the scroll amount by typing over the
SCROLL amount field with a new amount. The new scroll amount will
remain effective (except MAX or M) until you change it or until you begin a
new function.
– You can temporarily override the scroll amount, without changing the
SCROLL amount field, by:
- Typing an amount as part of the scroll command and pressing the ENTER
key
- Typing a scroll amount in the command/option field and then pressing
PF11 or PF23
– The IPCS-defined PF keys 11 and 23 invoke the RIGHT primary command.
v Example: Scroll using a numeric amount.
– Action
COMMAND ===> right 9
– Result
The panel is scrolled to the right by nine columns.

SELECT primary command — select a pointer to display

storage
Use the SELECT primary command to choose a pointer from the address pointer
stack on the pointer panel. IPCS then uses the pointer to display storage that is
addressed by that pointer. Note that you can also use the S (select) line command.
v Syntax

{ SELECT } pointer-number
{ SEL }
{ S }

v Parameter
pointer-number
Identifies the pointer being selected. The pointer-number is the number of the
pointer being selected. Leading zeros can be omitted. The pointer-number can
be used only on the pointer panel of the BROWSE option.
Usage notes:
– SELECT can only be used in the BROWSE option.
v Example: Select the third pointer from the pointer stack to view the storage
location at X'00000210'. The screen shows the SELECT primary command.

Chapter 6. IPCS dialog controls 409

SORT primary command

DSNAME(’D83DUMP.DUMPC.PB00465’) POINTERS -------------------------------------

--------------------------------------------------------------------------------
|COMMAND ===> select 3_ SCROLL ===> CSR |
--------------------------------------------------------------------------------

ASID(X’0014’) is the default address space

PTR Address Address space Data type
00001 00000000 HEADER AREA
Remarks: Comment 1
00002 00FD7BC8 ASID(X’0014’) AREA
Remarks: Comment 2
00003 00000210 ASID(X’0014’) AREA
Remarks:
00004 00FD7BA0 ASID(X’0001’) STRUCTURE(CVT)
Remarks: Communications Vector Table
**************************** END OF POINTER STACK *****************************

SORT primary command — sort an IPCS report

Use the SORT primary command to sort an IPCS report based on columns of
interest within the report.

Sorting is done as though the report were produced using ISO-8 ASCII characters.
This causes columns of equal-length hexadecimal numbers to sort in numeric
sequence since uppercase ISO-8 ASCII letters collate after decimal digits.
v Syntax

SORT [col1 [col2][A | D][...]]

[X | NX]

v Parameter
col1
Specifies the first column of a group of columns to be used as the sort key.
The column number must be entered as a decimal number between 1 and
250. If col1 is entered alone, 250 is used as the final column. If no groups of
columns are specified, the entire report line is used as a sort key.
Up to five groups of non-overlapping columns may be designated. If two or
more groups are designated, each group other than the last must include
either a col2 designation, an indication of sort order, or both.
col2
Specifies the final column of a group of columns to be used as a sort key.
The column number must be entered as a decimal number between col1 and
250.
A
D Indicates whether the columns are to be sorted in the default, ascending
sequence (A) or in the descending sequence (D). The letters may be entered
in either upper or lower case.
X
NX Restricts sort activity to excluded (X) or visible (NX) lines of the report. The
default is to sort all lines in the report.
v Example

410 z/OS MVS IPCS Commands

 STACK primary command

STACK primary command — create an IPCS-defined symbol

Use the STACK primary command to create, in the next available entry, an
IPCS-defined symbol for the address pointer stack. IPCS places the symbol in two
locations:
v On the pointer panel of the BROWSE option in ascending order from 00001
through 99999
v In the symbol table in your user dump directory in ascending order from Z1
through Z99999

If symbol entry 99999 or Z99999 is reached, IPCS suspends the stack updates. You
should use the RENUM primary command to renumber all entries.
v Syntax

STACK [ data-descr | X ]

v Parameters
data-descr or X
Specifies the data description parameter, which consists of two parts:
– An address
– Address processing parameters
If you omit the data description parameter, the default is X, the current
address. Chapter 3, “Data description parameter,” on page 17 has more
information about the syntax and use of the data description parameter.
v Usage notes
– STACK can only be used in the BROWSE option.
– The IPCS-defined PF keys 6 and 18 invoke the STACK primary command.
– There are two special symbols, CURSOR and X, that are accepted in the
BROWSE option on the storage panel. These symbols associate a location in a
dump and are used in the same manner as other symbols, such as the CVT
and TCB symbols.
- CURSOR indicates the word of storage at which you position the cursor.
By placing the cursor in the selection field preceding a word of storage or
by placing the cursor under a word of storage, you can reference the word
of storage. CURSOR is not in effect if the position of the cursor does not
identify a word of storage or if you leave the storage panel.
- X indicates the starting address of the data displayed on the storage panel.
X remains in effect even if you leave the storage panel.
While browsing through a dump, use the IPCS-defined PF keys:
– 10 or 22 to invoke the primary command chain, STACK X; LOCATE
CURSOR%
The % selection code indicates a 24 bit address of storage.
– 11 or 23 to invoke the primary command chain, STACK X; LOCATE
CURSOR?
The ? selection code indicates a 31 bit address of storage.
STACK X requests that an entry to the address pointer stack on the pointer
panel be added with the address contained in the word of storage indicated by
the cursor's current position.

Chapter 6. IPCS dialog controls 411

STACK primary command

LOCATE CURSOR requests that IPCS locate and display the data found at the
address contained in the word of storage indicated by the cursor's current
position.
v Example: Add an address pointer to the stack.
– Action
COMMAND ===> stack cvt asid(x’0001’)
– Result
This command adds a pointer entry to the pointer panel. It specifies address
space 1 and indicates that this is the communications vector table (CVT)
under the remarks column. The processing of this command updates both the
pointer panel of the BROWSE option and the symbol table.

UP primary command — scroll data backward

Use the UP primary command to scroll backward toward the top of data.
v Syntax

UP [ amount ]

v Parameter
amount
Specifies one of the following scroll amounts:
– A number from 1 through 9999, representing the number of lines to be
scrolled
– PAGE or P, indicating that a full screen should be scrolled
– HALF or H, indicating that a half-screen should be scrolled
– CSR or C, indicating that the screen should be scrolled to the line on
which the cursor resides
– MAX or M, indicating that the screen should be scrolled to the top
– DATA or D, indicating that the screen should be scrolled a page minus
one line
If you do not specify an amount, IPCS uses the amount in the SCROLL
amount field in the upper right corner of the screen.
v Usage notes
– UP can be used on all IPCS dialog panels that display the SCROLL amount
field.
– The scroll amount is typically displayed on the screen, following the
command/option field. You can change the scroll amount by typing over the
SCROLL amount field with a new amount. The new scroll amount will
remain effective (except MAX or M) until you change it or until you begin a
new function.
– You can temporarily override the scroll amount, without changing the
SCROLL amount field, by:
- Typing an amount as part of the scroll command and pressing the ENTER
key
- Typing a scroll amount in the command/option field, and then pressing
PF7 or PF19
– The IPCS-defined PF keys 7 and 19 invoke the UP primary command.
v Example: Scroll using the MAX operand.

412 z/OS MVS IPCS Commands

 UP primary command

– Action:
COMMAND ===> up max
or
COMMAND ===> up m
– Result
The panel is scrolled to the top of the data.

VERBOSE primary command — display all data without

condensing
Use the VERBOSE primary command to cause BROWSE option to display all data
without condensing.
v Syntax

VERBOSE

v Usage notes
– VERBOSE can be used only from the storage panel of the BROWSE option.
– The BROWSE option begins options displaying storage in CONDENSE mode.
– VERBOSE persists until the CONDENSE primary command is issued or until
you exit the BROWSE option.

Example: The following screen depicts the use of the VERBOSE primary command.
As seen, all lines are displayed without condensing.
ASID(X’000C’) ADDRESS(0BF29E90.) STORAGE ------------------------------------
Command ===>
0BF29E90 01010101 01010101 01010100 00010101 | ................ |
0BF29EA0 01010101 01010101 01010101 01010101 | ................ |
0BF29EB0 01010101 01010101 01010101 01010101 | ................ |
0BF29EC0 01010101 01010101 01010101 01010101 | ................ |
0BF29ED0 01010101 01010101 01010101 01010101 | ................ |
0BF29EE0 01000000 00000000 00000101 01010101 | ................ |
0BF29EF0 01000000 00000000 00000101 01010101 | ................ |
0BF29F00 01010000 00000000 00000101 01010101 | ................ |
0BF29F10 00000000 00000000 00000101 01010101 | ................ |
0BF29F20 01010101 01010101 01010101 01010101 | ................ |
0BF29F30 01010101 01010101 01010101 01010101 | ................ |
0BF29F40 01010101 01010101 01010101 01010101 | ................ |
0BF29F50 01010101 01010101 01010101 01010101 | ................ |
0BF29F60 01010101 01010101 01010101 01010101 | ................ |
0BF29F70 01010101 01010101 01010101 01010101 | ................ |
0BF29F80 01010101 01010101 01010101 01010101 | ................ |
0BF29F90 01010101 01010101 01010101 01010101 | ................ |
0BF29FA0 01010101 01010101 01010101 01010101 | ................ |
0BF29FB0 01010101 01010101 01010101 01010101 | ................ |
0BF29FC0 01010101 01010101 01010101 01010101 | ................ |
0BF29FD0 01010101 01010101 01010101 01010101 | ................ |
0BF29FE0 01000000 00000000 00000101 01010101 | ................ |
0BF29FF0 01000000 00000000 00000101 01010101 | ................ |
0BF2A000 01010000 00000000 00000101 01010101 | ................ |
0BF2A010 00000000 00000000 00000101 01010101 | ................ |
0BF2A020 47F0F114 32C1D5E3 E4C6F0F1 F64BF2F0 | .01..ANTUF016.20 |

WHERE primary command — identify an area at a given

address
Use the WHERE primary command to identify an area at a given address. See the
WHERE subcommand for more examples of the primary command.

Chapter 6. IPCS dialog controls 413

WHERE primary command

v Syntax

{ WHERE } data-descr
{ W }

v Parameter
data-descr
Specifies the data description parameter, which consists of two parts:
– An address
– Address processing parameters
Chapter 3, “Data description parameter,” on page 17 has more information
about the syntax and use of the data description parameter.

Note: The WHERE primary command uses only two of the five possible
parts of a data description parameter.
v Usage notes
– WHERE can be used from the BROWSE option pointer panel and storage
panel, and from the dump display reporter panel.
– WHERE produces a brief report describing all areas, structures, and modules
that contain the address of interest.
– The area, structure, or module with the closest address to the address of
interest is the one that will be added to the pointer stack. (More than one area
may satisfy the search criteria.)
v Example: Identify an area at a given address.
– Action
The following screen shows the WHERE primary command being issued
from the BROWSE option pointer panel. The same results occur if the
command are issued from a dump display reporter panel.

DSNAME(’D46IPCS.DRVC400.SA00001’) POINTERS -----------------------------------

-----------------------
|COMMAND ===> w 6b0_ | SCROLL ===> CSR
-----------------------
PTR Address Address space Data type
00001 00000000 ASID(X’0003’) AREA
Remarks:
00002 000006B0 ASID(X’0003’) AREA
Remarks:
00003 00FD7420 ASID(X’0001’) STRUCTURE(Cvt)
Remarks: Communications Vector Table
**************************** END OF POINTER STACK *****************************

– Result
First, all items that contain this address are displayed using the dump display
reporter panel.

414 z/OS MVS IPCS Commands

 WHERE primary command

IPCS OUTPUT STREAM -------------------------------------- LINE 0 COLS 1 78

COMMAND ===> _ SCROLL ===> CSR
****************************** TOP OF DATA ***********************************
ASID(X’0003’) 000006B0. STRUCTURE(Psa)+06B0 IN PSA
ASID(X’0003’) 000006B0. IEAVFX00+06B0 IN PSA
****************************** END OF DATA ***********************************

Then, the item with the smallest offset that contains the address ‘6b0’ – in this
case, the PSA – is added to the pointer stack. The following screen shows the
updated pointer stack.

DSNAME(’D46IPCS.DRVC400.SA00001’) POINTERS -----------------------------------

COMMAND ===> _ SCROLL ===> CSR
PTR Address Address space Data type
00001 00000000 ASID(X’0003’) AREA
Remarks:
00002 000006B0 ASID(X’0003’) AREA
Remarks:
00003 00FD7420 ASID(X’0001’) STRUCTURE(Cvt)
Remarks: Communications Vector Table
-------------------------------------------------------------------------------
|00004 00000000 ASID(X’0003’) STRUCTURE(Psa) |
| Remarks: |
-------------------------------------------------------------------------------
**************************** END OF POINTER STACK *****************************

IPCS dialog line commands

D line command — delete screen output

Use the D line command to permanently omit specific lines from the screen.
v Syntax

{ D }
{ Dn }
{ DD-DD }

v Parameters
n Represents a decimal number in the range of 1 through 9999.
- Represents an inclusive number of lines.
v Usage notes
– D can be entered on the dump display reporter panel and on the pointer
panel of the BROWSE option.
– When entering line commands, remember to do one of the following:
- End the line command with a delimiter character (either a blank or a
special character) that was not displayed in the report column following the
line command.
- Type the line command and press the ENTER key, leaving the cursor under
the character following your line command.
– If you request a report that is too large to be held in virtual storage all at
once, use D to omit sections of the report.

Chapter 6. IPCS dialog controls 415

D line command

– More than one line command can be entered at a time. For example, before
pressing the ENTER key the D, X, and S, F, or L line commands can be
entered on the same screen.
v Example: The following screens depict use of the D line command and the
resulting display output after pressing the ENTER key. The first screen shows
using D on the dump display reporter panel.

IPCS OUTPUT STREAM ----------------------------------------- LINE 0 COLS 1 78

COMMAND ===> SCROLL ===> CSR
******************************** TOP OF DATA ********************************
* * * * K E Y F I E L D S * * * *
JOBNAME D58PXE1
SELECTED BY: CURRENT

------------------
|d4ASCB: 00920200|
------------------

FWDP..... 00914E00 ASID..... 00B3 CSCB..... 00920D48

TSB...... 00922178 AFFN..... FFFF ASXB..... 005FDC20 DSP1..... 00
FLG2..... 00 SRBS..... 0000 LOCK..... 00000000
ASSB..... 01929980

TCB: 005FDE40
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 005FDDF8 NDSP..... 00000000
JSCB..... 005FDAA4 BITS..... 00000000 DAR...... 00
RTWA..... 00000000 FBYT1.... 00 STCB..... 7FFFECB0

PRB: 005FDAD8
WLIC..... 00020001 FLCDE.... 00BF9458 OPSW..... 070C1000 810203A0
LINK..... 015FDE40

CDE: 00BF9458

This next screen shows the result of using the D line command.

416 z/OS MVS IPCS Commands

 E line command

IPCS OUTPUT STREAM ----------------------------------------- LINE 0 COLS 1 78

COMMAND ===> _ SCROLL ===> CSR
******************************** TOP OF DATA ********************************
* * * * K E Y F I E L D S * * * *
JOBNAME D58PXE1
SELECTED BY: CURRENT

ASSB..... 01929980

TCB: 005FDE40
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 005FDDF8 NDSP..... 00000000
JSCB..... 005FDAA4 BITS..... 00000000 DAR...... 00
RTWA..... 00000000 FBYT1.... 00 STCB..... 7FFFECB0

PRB: 005FDAD8
WLIC..... 00020001 FLCDE.... 00BF9458 OPSW..... 070C1000 810203A0
LINK..... 015FDE40

CDE: 00BF9458
NAME..... IEAVAR00 ENTPT.... 81B3E120

TCB: 005FD080
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 005FDDD0 NDSP..... 00000000
JSCB..... 005FDAA4 BITS..... 00000000 DAR...... 00
RTWA..... 00000000 FBYT1.... 00 STCB..... 7FFFE890

E line command — edit a pointer

Use the E line command on the pointer panel of the BROWSE option to edit a
selected pointer.
v Syntax

v Usage notes
– E can be used only on the BROWSE option pointer panel.
– After entering an E next to any pointer, the editing panel appears, as shown
in Figure 42 on page 418.
Use the editing panel to edit, add, or delete information in the selected
pointer's definition by typing the requested information in the appropriate
fields.
– While the complete value of each field is displayed from the editing panel,
certain fields may be truncated when you return to the pointer stack in the
BROWSE option after editing.
v Example: Edit a pointer on the pointer panel.

Chapter 6. IPCS dialog controls 417

E line command

DSNAME(’D83DUMP.DUMPC.PB00465’) POINTERS -------------------------------------

COMMAND ===> . SCROLL ===> CSR
ASID(X’0014’) is the default address space
PTR Address Address space Data type
00001 00000000 HEADER AREA
Remarks: Comment 1

-------------------------------------------------------------------------
|e0002 00FD7BC8 ASID(X’0014’) AREA |
| Remarks: Comment 2 |
-------------------------------------------------------------------------

00003 00000210 ASID(X’0014’) AREA

Remarks:
00004 00FD7BA0 ASID(X’0001’) STRUCTURE(Cvt)
Remarks: Communications Vector Table
**************************** END OF POINTER STACK *****************************

Figure 41. Using E on the Pointer Panel

EDIT DSNAME(’D83DUMP.DUMPC.PB00465’) POINTER 00002

COMMAND ==]

Enter/verify attributes of the pointer.

Use ENTER to view updated definition,

END to save pointer and return,
CANCEL to return without saving changes.

Address ===] 00FD7BC8

Address space ===] ASID(X’0014’)
Data type ===] AREA
Remarks ===] The remark text of this pointer is being changed to
show how the comments can be truncated when the pointer stack is
displayed._

Figure 42. Pointer Editing Panel

DSNAME(’D83DUMP.DUMPC.PB00465’) POINTERS -------------------------------------

COMMAND ===> SCROLL ===> CSR
ASID(X’0014’) is the default address space
PTR Address Address space Data type
00001 00000000 HEADER AREA
Remarks: Comment 1
-------------------------------------------------------------------------
|e0002 00FD7BC8 ASID(X’0014’) AREA |
| Remarks: Comment 2 |
-------------------------------------------------------------------------

00002 00FD7BC8 ASID(X’0014’) AREA

Remarks: The remark text of this pointer is being changed to show
00003 00000210 ASID(X’0014’) AREA
Remarks:
00004 00FD7BA0 ASID(X’0001’) STRUCTURE(Cvt)
Remarks: Communications Vector Table
**************************** END OF POINTER STACK *****************************

Figure 43. Result of Using Edit

F line command — format a defined control block

Use the F line command to request the formatting of a pointer whose data type is
defined as STRUCTURE on the pointer panel of the BROWSE option.
v Syntax

418 z/OS MVS IPCS Commands

 F line command

v Usage notes
– F can only be used from the BROWSE option pointer panel.
– The pointer on the pointer panel must be defined as a control block with the
data type STRUCTURE.
v Example: Format a control block on the pointer panel.
– Action
The following screen shows where to enter the F line command.
– Result
IPCS formats the CVT.

DSNAME(’D83DUMP.DUMPC.PB00465’) POINTERS -------------------------------------

COMMAND ===> . SCROLL ===> CSR
ASID(X’0014’) is the default address space
PTR Address Address space Data type
00001 00000000 HEADER AREA
Remarks: Comment 1
00002 00FD7BC8 ASID(X’0014’) AREA
Remarks: Comment 2
00003 00000210 ASID(X’0014’) AREA
Remarks:
-------------------------------------------------------------------------
|f0004 00FD7BA0 ASID(X’0001’) STRUCTURE(Cvt) |
| Remarks: Communications Vector Table |
-------------------------------------------------------------------------
**************************** END OF POINTER STACK *****************************

I line command — insert a pointer

Use the I line command to insert a pointer in the address pointer stack on the
pointer panel of the BROWSE option. The inserted pointer describes the default
address space after the selected pointer.
v Syntax

{ I }
{ In }

v Parameter
n Represents a decimal number of 1 through 9999. If you omit n, the default is
1 pointer.
v Usage notes
– The I line command can be used only while in the BROWSE option on the
pointer panel.
– When inserting a pointer, IPCS supplies an address of 00000000.
– Entering the I line command causes IPCS to renumber the following existing
pointers.
v Example: Insert a pointer on the pointer panel.
– Action
The following screen shows use of the I line command and the resulting
display output after pressing the ENTER key.

Chapter 6. IPCS dialog controls 419

I line command

DSNAME(’D83DUMP.DUMPC.PB00465’) POINTERS -------------------------------------

COMMAND ===> _ SCROLL ===> CSR
ASID(X’0014’) is the default address space
PTR Address Address space Data type
00001 00000000 HEADER AREA
Remarks: Comment 1

--------------------------------------------------------------------
|i0002 00FD7BC8 ASID(X’0014’) AREA |
| Remarks: Comment 2 |
--------------------------------------------------------------------

00003 00000210 ASID(X’0014’) AREA

Remarks:
00004 00FD7BA0 ASID(X’0001’) STRUCTURE(Cvt)
Remarks: Communications Vector Table
**************************** END OF POINTER STACK *****************************

– Result
The following screen shows the results of using an I line command.

DSNAME(’D83DUMP.DUMPC.PB00465’) POINTERS -------------------------------------

COMMAND ===> _ SCROLL ===> CSR
ASID(X’0014’) is the default address space
PTR Address Address space Data type
00001 00000000 HEADER AREA
Remarks: Comment 1
00002 00FD7BC8 ASID(X’0014’) AREA
Remarks: Comment 2

--------------------------------------------------------------------
|00003 00000000 ASID(X’0014’) AREA |
| Remarks: |
--------------------------------------------------------------------

00004 00000210 ASID(X’0014’) AREA

Remarks:
00005 00FD7BA0 ASID(X’0001’) STRUCTURE(Cvt)
Remarks: Communications Vector Table
**************************** END OF POINTER STACK *****************************

R line command — repeat a pointer

Use the R line command to duplicate (or repeat) a selected pointer on the pointer
panel of the BROWSE option.
v Syntax

{ R }
{ Rn }

v Parameter
n Represents the number of times the pointer should be repeated. The n is a
decimal number from 1 through 9999.
v Usage notes
– R can be used only while in the BROWSE option on the pointer panel.
– Entering R causes the existing pointers to be renumbered.
v Example: Repeat an existing pointer twice on the pointer panel.
– Action

420 z/OS MVS IPCS Commands

 R line command

The following screen depicts use of the R line command.

DSNAME(’D83DUMP.DUMPC.PB00465’) POINTERS -------------------------------------

COMMAND ===> _ SCROLL ===> CSR
ASID(X’0014’) is the default address space
PTR Address Address space Data type
00001 00000000 HEADER AREA
Remarks: Comment 1

------------------------------------------------------------------------
|r2002 00FD7BC8 ASID(X’0014’) AREA |
| Remarks: Comment 2 |
------------------------------------------------------------------------

00003 00000210 ASID(X’0014’) AREA

Remarks:
00004 00FD7BA0 ASID(X’0001’) STRUCTURE(Cvt)
Remarks: Communications Vector Table
**************************** END OF POINTER STACK *****************************

– Result
The following screen shows the resulting display output after pressing the
ENTER key.

DSNAME(’D83DUMP.DUMPC.PB00465’) POINTERS -------------------------------------

COMMAND ===> . SCROLL ===> CSR
ASID(X’0014’) is the default address space
PTR Address Address space Data type
00001 00000000 HEADER AREA
Remarks: Comment 1
00002 00FD7BC8 ASID(X’0014’) AREA
Remarks: Comment 2
------------------------------------------------------------------------------
|00003 00FD7BC8 ASID(X’0014’) AREA |
| Remarks: Comment 2 |
|00004 00FD7BC8 ASID(X’0014’) AREA |
| Remarks: Comment 2 |
------------------------------------------------------------------------------
00005 00000210 ASID(X’0014’) AREA
Remarks:
00006 00FD7BA0 ASID(X’0001’) STRUCTURE(Cvt)
Remarks: Communications Vector Table
**************************** END OF POINTER STACK *****************************

S line command — select a pointer to display storage

Use the S line command to choose a pointer from the address pointer stack on the
pointer panel. IPCS then uses the pointer to display storage that is addressed by
that pointer.

Note that you can also use the SELECT primary command.
v Syntax

v Example: Select the third pointer from the pointer stack to view the storage
location at X'00000210'. The screen shows the S line command.

Chapter 6. IPCS dialog controls 421

S, F, and L line commands

DSNAME(’D83DUMP.DUMPC.PB00465’) POINTERS -------------------------------------

COMMAND ===> SCROLL ===> CSR
ASID(X’0014’) is the default address space
PTR Address Address space Data type
00001 00000000 HEADER AREA
Remarks: Comment 1
00002 00FD7BC8 ASID(X’0014’) AREA
Remarks: Comment 2

------------------------------------------------------------------------
|s0003 00000210 ASID(X’0014’) AREA |
| Remarks: |
------------------------------------------------------------------------

00004 00FD7BA0 ASID(X’0001’) STRUCTURE(Cvt)

Remarks: Communications Vector Table
**************************** END OF POINTER STACK *****************************

S, F, and L line commands — show excluded screen output

Use the S, F, or L line command to request that specific lines be displayed from
excluded lines in full screen. The lines to be shown are chosen by using the
indentation of the data. The lines that are indented closest to the left margin are
displayed. If several lines are indented equally, the first lines are shown.
v Syntax

{ S }
{ Sn }
{ F }
{ Fn }
{ L }
{ Ln }

v Operations
S Shows a selected line from a block of excluded lines.
F Shows the first line of excluded text.
L Shows the last line of excluded text.
v Parameter
n Specified the number of excluded lines to be shown. The n is a decimal
number of 1 through 9999.
v Usage notes
– S, F, or L can be entered only on the dump display reporter panel.
– When entering line commands, do one of the following:
- End the line command with a delimiter character, which can be either a
blank or a special character, that was not displayed in the report column
following the line command.
- Type the line command and press the ENTER key, leaving the cursor under
the character following your line command.
– More than one line command can be entered at a time. For example, before
pressing the ENTER key the D, X, and S, F, or L line commands can be
entered on the same screen.
v Example: Use the F line command to show 2 excluded lines of text.
– Action

422 z/OS MVS IPCS Commands

 S, F, and L line commands

The following screen shows the F line command on the dump display report
panel.

IPCS OUTPUT STREAM ----------------------------------------- LINE 0 COLS 1 78

COMMAND ===> SCROLL ===> CSR
******************************** TOP OF DATA ********************************
* * * * K E Y F I E L D S * * * *
JOBNAME D58PXE1
SELECTED BY: CURRENT

ASCB: 00920200
FWDP..... 00914E00 ASID..... 00B3 CSCB..... 00920D48
TSB...... 00922178 AFFN..... FFFF ASXB..... 005FDC20 DSP1..... 00
FLG2..... 00 SRBS..... 0000 LOCK..... 00000000
ASSB..... 01929980

TCB: 005FDE40
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 005FDDF8 NDSP..... 00000000

----------------------------------------------------------------------------
| f2_- - - - - - - - - - - - - - - - - - - - - - - 5 LINE(S) NOT DISPLAYED|
----------------------------------------------------------------------------

LINK..... 015FDE40

CDE: 00BF9458
NAME..... IEAVAR00 ENTPT.... 81B3E120

TCB: 005FD080
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 005FDDD0 NDSP..... 00000000
JSCB..... 005FDAA4 BITS..... 00000000 DAR...... 00
RTWA..... 00000000 FBYT1.... 00 STCB..... 7FFFE890

– Result
The following screen shows the resulting display output after pressing the
ENTER key.

IPCS OUTPUT STREAM ----------------------------------------- LINE 0 COLS 1 78

COMMAND ===> _ SCROLL ===> CSR
******************************** TOP OF DATA ********************************
* * * * K E Y F I E L D S * * * *
JOBNAME D58PXE1
SELECTED BY: CURRENT

ASCB: 00920200
FWDP..... 00914E00 ASID..... 00B3 CSCB..... 00920D48
TSB...... 00922178 AFFN..... FFFF ASXB..... 005FDC20 DSP1..... 00
FLG2..... 00 SRBS..... 0000 LOCK..... 00000000
ASSB..... 01929980

TCB: 005FDE40
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 005FDDF8 NDSP..... 00000000

---------------------------------------------------------------------------------
| JSCB..... 005FDAA4 BITS..... 00000000 DAR...... 00 |
| RTWA..... 00000000 FBYT1.... 00 STCB..... 7FFFECB0 |
| - - - - - - - - - - - - - - - - - - - - - - - - - - 3 LINE(S) NOT DISPLAYED|
---------------------------------------------------------------------------------

LINK..... 015FDE40

CDE: 00BF9458

Chapter 6. IPCS dialog controls 423

X line command

X line command — exclude screen output

Use the X line command to request that specific lines be suppressed from screen
output. IPCS displays a statement that indicates the number of lines not being
shown.
v Syntax

{ X }
{ Xn }
{ XX-XX }

v Parameters
n Represents a decimal number in the range of 1 through 9999.
- Represents an inclusive number of lines.
v Usage notes
– The X line command can only be entered on the dump display reporter panel.
– When entering line commands, remember to do one of the following:
- End the line command with a delimiter character, which can be either a
blank or a special character, that was not displayed in the report column
following the line command.
- Type the line command and press the ENTER key, leaving the cursor under
the character following your line command.
– More than one line command can be entered at a time. For example, before
you press the ENTER key, enter the D, X, and S, F, or L line commands on the
same screen.
v Example: The following screens depict use of the X line command and the
resulting display output after pressing the ENTER key. The first screen shows
using X on the dump display reporter panel.

424 z/OS MVS IPCS Commands

 X line command

IPCS OUTPUT STREAM ----------------------------------------- LINE 0 COLS 1 78

COMMAND ===> SCROLL ===> CSR
******************************** TOP OF DATA ********************************
* * * * K E Y F I E L D S * * * *
JOBNAME D58PXE1
SELECTED BY: CURRENT

ASCB: 00920200
FWDP..... 00914E00 ASID..... 00B3 CSCB..... 00920D48
TSB...... 00922178 AFFN..... FFFF ASXB..... 005FDC20 DSP1..... 00
FLG2..... 00 SRBS..... 0000 LOCK..... 00000000
ASSB..... 01929980

TCB: 005FDE40
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 005FDDF8 NDSP..... 00000000

-----------------------------------------------------------
|xx JSCB..... 005FDAA4 BITS..... 00000000 DAR...... 00|
-----------------------------------------------------------

RTWA..... 00000000 FBYT1.... 00 STCB..... 7FFFECB0

PRB: 005FDAD8
----------------------------------------------------------------------------
|xx_ WLIC..... 00020001 FLCDE.... 00BF9458 OPSW..... 070C1000 810203A0 |
----------------------------------------------------------------------------
LINK..... 015FDE40

CDE: 00BF9458

This screen shows the result of using the X line command.

IPCS OUTPUT STREAM ----------------------------------------- LINE 0 COLS 1 78

COMMAND ===> _ SCROLL ===> CSR
******************************** TOP OF DATA ********************************
* * * * K E Y F I E L D S * * * *
JOBNAME D58PXE1
SELECTED BY: CURRENT

ASCB: 00920200
FWDP..... 00914E00 ASID..... 00B3 CSCB..... 00920D48
TSB...... 00922178 AFFN..... FFFF ASXB..... 005FDC20 DSP1..... 00
FLG2..... 00 SRBS..... 0000 LOCK..... 00000000
ASSB..... 01929980

TCB: 005FDE40
CMP...... 00000000 PKF...... 00 LMP...... FF DSP...... FF
TSFLG.... 00 STAB..... 005FDDF8 NDSP..... 00000000
-----------------------------------------------------------------------------
|- - - - - - - - - - - - - - - - - - - - - - - - - 5 LINE(S) NOT DISPLAYED|
-----------------------------------------------------------------------------
LINK..... 015FDE40

CDE: 00BF9458

Chapter 6. IPCS dialog controls 425

X line command

426 z/OS MVS IPCS Commands

Chapter 7. IPCS CLISTs and REXX EXECs
This topic describes some of the CLISTs and REXX execs that IPCS supplies. These
CLISTs and REXX execs do the following:
v Print system storage areas
v Create problem screening reports
v Create a user dump directory or a sysplex dump directory
v Run a chain of save areas

CLISTs that are used to customize IPCS are described in z/OS MVS IPCS
Customization.

System library SYS1.SBLSCLI0 holds machine-readable copies of each CLIST and

REXX EXEC. The names of the CLISTs begin with the letters BLSC, REXX EXECs
with BLSX. This topic describes those CLISTs and REXX execs that IPCS users may
invoke directly to perform tasks. See the z/OS MVS IPCS User's Guide for more
information about invoking CLISTs and REXX execs and running them in batch
mode.

Task Directory for IPCS CLISTs and REXX EXECs

The following sections contain tables that summarize the CLISTs and REXX EXECs
supplied with IPCS and the various tasks they perform.
v Analyze a dump

When you want to Use

Obtain a stand-alone dump screening report “BLSCSCAN CLIST — obtain a stand-alone
dump screening report” on page 439.
Obtain an SVC dump screening report “BLSCBSVB CLIST — obtain an SVC dump
screening report” on page 431.
Obtain a SYSMDUMP dump screening “BLSCBSYB CLIST — obtain a SYSMDUMP
report dump screening report” on page 433.
Format save area chain “BLSCEPTR CLIST — run a save area chain”
on page 436.
List entry points with the same name “BLSXWHER REXX EXEC — find all
modules with the same entry point name”
on page 440.

v Customize an IPCS session

When you want to Use

Create or allocate a user dump directory or “BLSCDDIR CLIST — create a dump
a sysplex dump directory directory” on page 434.
Remove uncataloged dump directory entries “BLSCDROP CLIST — issue IPCS
DROPDUMP for uncataloged DSNAME
entries” on page 435.
Define IPCS dialog libraries to ISPF See BLSCLIBD CLIST in the topic about
BLSCLIBD CLIST - Activate IPCS Dialog
Services in z/OS MVS IPCS Customization.

© Copyright IBM Corp. 1988, 2017 427

 When you want to Use
Define the SYS1.SBLSCLI0 library to IPCS See BLSCALTL CLIST in the topic about
dialog BLSCLIBD CLIST - Activate IPCS Dialog
Services in z/OS MVS IPCS Customization.

v Print dump analysis reports

When you want to Use

Print a stand-alone dump screening report “BLSCBSAA CLIST — print a stand-alone
dump screening report” on page 429.
Print an SVC dump screening report “BLSCBSVA CLIST — print an SVC dump
screening report” on page 430.
Print a SYSMDUMP dump screening report “BLSCBSYA CLIST — print a SYSMDUMP
dump screening report” on page 432.
Print a stand-alone dump detailed report “BLSCBSAP CLIST — print a stand-alone
dump detailed report” on page 429.
Print an SVC dump detailed report “BLSCBSVP CLIST — print an SVC dump
detailed report” on page 431.
Print a SYSMDUMP dump detailed report “BLSCBSYP CLIST — print a SYSMDUMP
dump detailed report” on page 433.

v Print storage data

When you want to Use

Print common storage areas “BLSCPCSA CLIST — print common storage
areas” on page 436.
Print nucleus storage areas “BLSCPNUC CLIST — print nucleus storage
areas” on page 437.
Print one or more storage areas “BLSCPRNT CLIST — print a dump” on
page 437.
Print private storage areas “BLSCPRIV CLIST — print private storage
areas” on page 437.
Print global system queue areas “BLSCPSQA CLIST — print global system
queue areas” on page 439.

v Review sample CLISTs and REXX EXECs

For This Subcommand See the Example

COMPARE COMPARE example.
EVALDEF EVALDEF example.
EVALDUMP EVALDUMP example.
EVALMAP EVALMAP example. “BLSXWHER REXX
EXEC — find all modules with the same
entry point name” on page 440.
EVALSYM EVALSYM example.
RUNCHAIN RUNCHAIN example.

428 z/OS MVS IPCS Commands

 BLSCBSAA CLIST

BLSCBSAA CLIST — print a stand-alone dump screening report

Use the BLSCBSAA CLIST to print an initial screening report for a stand-alone
dump. BLSCBSAA copies the stand-alone dump from tape to DASD. The
stand-alone dump tape must be allocated to file IEFRDER. BLSCBSAA routes the
output dump report to the IPCSPRNT data set.

The IBM-supplied cataloged procedure BLSJIPCS is designed to invoke this CLIST.

You can run BLSJIPCS from JCL or from an operator console.

BLSCBSAA produces the same dump report as does the BLSCSCAN CLIST. See
“BLSCSCAN CLIST — obtain a stand-alone dump screening report” on page 439
and z/OS MVS IPCS User's Guide for other ways to obtain an initial screening
report for a stand-alone dump.

The following examples show how to run BLSCBSAA with the BLSJIPCS cataloged
procedure.
v Syntax for JCL invocation

//stepname EXEC PROC=IPCS,

//CLIST=BLSCBSAA,
//DUMP=sadump.dsname
//*
//* The following DD statement is required for CLIST=BLSCBSAA
//*
//IEFPROC.IEFRDER DD .... Input dump for copy
//*
//* The following DD statement is optional. If omitted, the
//* dump directory is dynamically allocated.
//*
//IEFPROC.IPCSDDIR DD .... IPCS dump directory

v Syntax for operator console invocation

ALLOCATE INFILE(IEFRDER) and OUTFILE(IPCSDUMP)

START BLSJIPCS,CLIST=BLSCBSAA,DUMP=’sadump.dsname’

v CLIST listing
See the BLSCBSAA member of SYS1.SBLSCLI0.

BLSCBSAP CLIST — print a stand-alone dump detailed report

Use the BLSCBSAP CLIST to print detailed storage information for a stand-alone
dump. Because this CLIST prints the storage, it should only be used in exceptional
circumstances, for example, when debugging an application that does not provide
IPCS support.

BLSCBSAP copies the stand-alone dump from tape to DASD. The stand-alone
dump tape must be allocated to file IEFRDER. BLSCBSAP routes the output dump
report to the IPCSPRNT data set.

The IBM-supplied cataloged procedure BLSJIPCS is designed to invoke this CLIST.

You can run BLSJIPCS from JCL or from an operator console.

Chapter 7. IPCS CLISTs and REXX EXECs 429

BLSCBSAP CLIST

See “BLSCSCAN CLIST — obtain a stand-alone dump screening report” on page

439 and z/OS MVS IPCS User's Guide for other ways to obtain information from a
stand-alone dump.

The following examples show how to run BLSCBSAP with the BLSJIPCS cataloged
procedure.
v Syntax for JCL invocation

//stepname EXEC PROC=IPCS,

//CLIST=BLSCBSAP,
//DUMP=sadump.dsname
//*
//* The following DD statement is required for CLIST=BLSCBSAP
//*
//IEFPROC.IEFRDER DD .... Input dump for copy
//*
//* The following DD statement is optional. If omitted, the
//* dump directory is dynamically allocated.
//*
//IEFPROC.IPCSDDIR DD .... IPCS dump directory

v Syntax for operator console invocation

ALLOCATE INFILE(IEFRDER) and OUTFILE(IPCSDUMP)

START BLSJIPCS,CLIST=BLSCBSAP,DUMP=’sadump.dsname’

v CLIST listing
See the BLSCBSAP member of SYS1.SBLSCLI0.

BLSCBSVA CLIST — print an SVC dump screening report

Use the BLSCBSVA CLIST to print an initial screening report for an SVC dump.
BLSCBSVA routes the output dump report to the IPCSPRNT data set.

The IBM-supplied cataloged procedure BLSJIPCS is designed to invoke this CLIST.

You can run BLSJIPCS from JCL or from an operator console.

This CLIST produces the same dump report as does the BLSCBSVB CLIST. See
“BLSCBSVB CLIST — obtain an SVC dump screening report” on page 431 and
z/OS MVS IPCS User's Guide for other ways to obtain an initial screening report for
an SVC dump.

The following examples show how to run BLSCBSVA with the BLSJIPCS cataloged
procedure.
v Syntax for JCL invocation
By default, the BLSJIPCS cataloged procedure invokes the BLSCBSVA CLIST.

//stepname EXEC PROC=IPCS,

//DUMP=svcdump.dsname
//*
//* The following DD statement is optional. If omitted, the
//* dump directory is dynamically allocated.
//*
//IEFPROC.IPCSDDIR DD .... IPCS dump directory

430 z/OS MVS IPCS Commands

 BLSCBSVA CLIST

v Syntax for operator console invocation

START BLSJIPCS,DUMP=’svcdump.dsname’

v CLIST listing
See the BLSCBSVA member of SYS1.SBLSCLI0.

BLSCBSVB CLIST — obtain an SVC dump screening report

Use the BLSCBSVB CLIST to create an initial screening report for an SVC dump.
Using the IPCS dialog, invoke BLSCBSVB through the SUBMIT option, then the
Prepare SVC Dump for Analysis option. IPCS submits a batch job for the CLIST
that routes the output dump report to a SYSOUT data set.

You can invoke BLSCBSVB directly from an IPCS session, but the CLIST takes a
long time to complete processing.
v IPCS batch invocation
You must supply the data set name, dump directory name, and sysout class.

-------------------- Prepare SVC Dump for IPCS Analysis ----------------------

COMMAND ===]

Enter/verify parameters for the job.

Use ENTER to submit the job, END to terminate without job submission.

DATA SET NAME ===]

DUMP DIRECTORY ===]
SYSOUT CLASS ===]

v IPCS dialog invocation

BLSCBSVB uses the current dump data set and dump directory.

------------------------- IPCS Subcommand Entry ------------------------------

Enter a free-form IPCS subcommand, CLIST, or REXX EXEC invocation below:

===] %BLSCBSVB

v CLIST listing
See the BLSCBSVB member of SYS1.SBLSCLI0.

BLSCBSVP CLIST — print an SVC dump detailed report

Use the BLSCBSVP CLIST to print detailed storage information for an SVC dump.
Because this CLIST prints the storage, it should only be used in exceptional
circumstances, for example, when debugging an application that does not provide
IPCS support.

The IBM-supplied cataloged procedure BLSJIPCS is designed to invoke this CLIST.

You can run BLSJIPCS from JCL or from an operator console.

See “BLSCBSVB CLIST — obtain an SVC dump screening report” and z/OS MVS
IPCS User's Guide for other ways to obtain information from an SVC dump.

Chapter 7. IPCS CLISTs and REXX EXECs 431

BLSCBSVP CLIST

The following examples show how to run BLSCBSVP with the BLSJIPCS cataloged
procedure.
v Syntax for JCL invocation

//stepname EXEC PROC=IPCS,

//CLIST=BLSCBSVP,
//DUMP=svcdump.dsname
//*
//* The following DD statement is optional. If omitted, the
//* dump directory is dynamically allocated.
//*
//IEFPROC.IPCSDDIR DD .... IPCS dump directory

v Syntax for operator console invocation

START BLSJIPCS,CLIST=BLSCBSVP,DUMP=’svcdump.dsname’

v CLIST listing
See the BLSCBSVP member of SYS1.SBLSCLI0.

BLSCBSYA CLIST — print a SYSMDUMP dump screening report

Use the BLSCBSYA CLIST to print an initial screening report for an SVC dump.
BLSCBSYA routes the output dump report to the IPCSPRNT data set.

The IBM-supplied cataloged procedure BLSJIPCS is designed to invoke this CLIST.

You can run BLSJIPCS from JCL or from an operator console.

This CLIST produces the same dump report as does the BLSCBSYB CLIST. See
“BLSCBSVB CLIST — obtain an SVC dump screening report” on page 431 and
z/OS MVS IPCS User's Guide for other ways to obtain an initial screening report for
an SVC dump.

The following examples show how to run BLSCBSYA with the BLSJIPCS cataloged
procedure.
v Syntax for JCL invocation
This JCL runs BLSCBSYA with cataloged procedure IPCS.

//stepname EXEC PROC=IPCS,

//CLIST=BLSCBSYA,
//DUMP=sysmdump.dsname
//*
//* The following DD statement is optional. If omitted, the
//* dump directory is dynamically allocated.
//*
//IEFPROC.IPCSDDIR DD .... IPCS dump directory

v Syntax for operator console invocation

START BLSJIPCS,CLIST=BLSCBSYA,DUMP=’sysmdump.dsname’

v CLIST listing
See the BLSCBSYA member of SYS1.SBLSCLI0.

432 z/OS MVS IPCS Commands

 BLSCBSYB CLIST

BLSCBSYB CLIST — obtain a SYSMDUMP dump screening report

Use the BLSCBSYB CLIST to create an initial screening report for a SYSMDUMP
dump. Using the IPCS dialog, invoke BLSCBSYB through the SUBMIT option, then
the Prepare SYSMDUMP Dump for Analysis option. IPCS submits a batch job for
the CLIST that routes the output dump report to a SYSOUT data set.

You can invoke BLSCBSYB directly from an IPCS session, but the CLIST takes a
long time to complete processing.
v IPCS batch invocation
You must supply the data set name, dump directory, and sysout class.

--------------------- Prepare SYSMDUMP for IPCS Analysis ------------

COMMAND ===]

Enter/verify parameters for the job.

Use ENTER to submit the job, END to terminate without job submission.

DATA SET NAME ===]

DUMP DIRECTORY ===]
SYSOUT CLASS ===]

v IPCS dialog invocation

BLSCBSYB uses the current dump data set and dump directory.

------------------------- IPCS Subcommand Entry --------------------

Enter a free-form IPCS subcommand, CLIST, or REXX EXEC invocation below:

===] %BLSCBSYB

v CLIST listing
See the BLSCBSYB member of SYS1.SBLSCLI0.

BLSCBSYP CLIST — print a SYSMDUMP dump detailed report

Use the BLSCBSYP CLIST to print detailed storage information for a SYSMDUMP
dump. Because this CLIST prints the storage, it should only be used in exceptional
circumstances, for example, when debugging an application that does not provide
IPCS support. BLSCBSYP routes the output dump report to the IPCSPRNT data
set.

The IBM-supplied cataloged procedure BLSJIPCS is designed to invoke this CLIST.

You can run BLSJIPCS from JCL or from an operator console.

See “BLSCSCAN CLIST — obtain a stand-alone dump screening report” on page

439 and z/OS MVS IPCS User's Guide for other ways to obtain information from a
stand-alone dump.

The following examples show how to run BLSCBSYP with the BLSJIPCS cataloged
procedure.
v Syntax for JCL invocation

Chapter 7. IPCS CLISTs and REXX EXECs 433

BLSCBSYP CLIST

//stepname EXEC PROC=IPCS,

//CLIST=BLSCBSYP,
//DUMP=sysmdump.dsname
//*
//* The following DD statement is optional. If omitted, the
//* dump directory is dynamically allocated.
//*
//IEFPROC.IPCSDDIR DD .... IPCS dump directory

v Syntax for operator console invocation

START BLSJIPCS,CLIST=BLSCBSYP,DUMP=’sysmdump.dsname’

v CLIST listing
See the BLSCBSYP member of SYS1.SBLSCLI0.

BLSCDDIR CLIST — create a dump directory

The IBM-supplied BLSCDDIR CLIST can be used to do the following:
v Create a sysplex dump directory
v Create a user dump directory when accessing IPCS
v Create user dump directories that satisfy special needs
v Create multiple user dump directories so that, for example, you can do
simultaneous interactive and batch processing

BLSCDDIR uses IBM-defined defaults that can be reset by your installation. For a
user dump directory, the installation determines the size and volume default
values that best suit your installation's needs using information found in z/OS
MVS IPCS Customization.

For more information about the use of BLSCDDIR, see z/OS MVS IPCS User's
Guide.
v Syntax

%BLSCDDIR [ DATACLAS(data-class) ]
[ DSNAME(dsname) ]
[ FILE(filename) ]
[ MGMTCLAS(management-class) ]
[ NDXCISZ(index-class) ]
[ NOENQ ]
[ RECORDS(records) ]
[ STORCLAS(storage-class) ]
[ VOLUME(volume) ]

v Parameters
DATACLAS(data-class)
Specifies the data class for the new directory. If you omit this parameter,
there is no data class specified for the new directory.
DSNAME(dsname)
Specifies the fully-qualified name you want to assign to the directory, If you
omit this parameter, the IBM-supplied defaults are:
– If you have a userid prefix, prefix.DDIR
– Otherwise, SYS1.DDIR
434 z/OS MVS IPCS Commands
 BLSCDDIR CLIST

FILE(filename)
Specifies the name of the file with which the ALLOCATE command
associates the DSNAME. The IBM-supplied default is IPCSDDIR.
MGMTCLAS(management-class)
Specifies the management class for the new directory. If you omit this
parameter, there is no management class specified for the new directory.
NDXCISZ(index-cisz)
Specifies the control interval size for the index portion of the new directory.
If you omit this parameter, the IBM-supplied default is 4096 bytes.
NOENQ
Suppresses ENQ processing that is intended to block other instances of IPCS
from using the directory being prepared for use by IPCSDDIR. IPCS itself
uses this option when it has already established the needed serialization.
Manual use of this option is not recommended.
RECORDS(records)
Specifies the number of records you want the directory to accommodate. If
you omit this parameter, the IBM-supplied default is 5000; your installation's
default might vary.
STORCLAS(storage-class)
Specifies the storage class for the new directory. If you omit this parameter,
there is no storage class specified for the new directory.
VOLUME(volume)
Specifies the VSAM volume on which the directory should reside. If you
omit DATACLAS, MGMTCLAS, STORCLAS, and VOLUME, the
IBM-supplied default is VSAM01. Otherwise, there is no IBM-supplied
default.
v CLIST listing
See the BLSCDDIR member of SYS1.SBLSCLI0.

BLSCDROP CLIST — issue IPCS DROPDUMP for uncataloged

DSNAME entries
Use the BLSCDROP CLIST to issue DROPDUMP against data sets that are
described through DSNAME in the currently allocated dump directory, yet are not
catalogued. This cleans out entries that are no longer associated with a cataloged
dump data set.

Note: If the data set was renamed, use the IPCS ALTER subcommand to change
the name of the dump or trace data set in the IPCS dump directory, before using
BLSCDROP (or issuing the IPCS DROPDUMP CLIST).
v Syntax

%BLSCDROP

v CLIST listing
See the BLSCDDIR member of SYS1.SBLSCLI0.

Chapter 7. IPCS CLISTs and REXX EXECs 435

BLSCEPTR CLIST

BLSCEPTR CLIST — run a save area chain

BLSCEPTR follows the forward chain of save areas. Beginning with the failing
TCB, it finds the first problem program's save area. BLSCEPTR locates the entry
point address in the save area, then goes to that address to check the entry point
identifier.

You should supply the address of the failing TCB when you invoke BLSCEPTR.
Otherwise BLSCEPTR uses the default address found in field PSATOLD
(PSA+X'21C').

The subcommands in this CLIST create the following symbols in the IPCS symbol
table:
EPnnn Entry points saved in the save area chain. For example, the symbol EP001
represents the entry point saved in the first save area on the chain.
EPIDnnn
The entry point identifier string for the entry point represented by EPnnn.
SAnnn
The save area holding the entry point address represented by EPnnn.
v Syntax

%BLSCEPTR [TCB(address)]

v Parameter
TCB(address)
The address of the TCB that BLSCEPTR uses to start chaining the save areas.
If you do not specify a TCB address, BLSCEPTR uses the address found in
PSATOLD (PSA+X'21C').
v CLIST listing
See the BLSCEPTR member of SYS1.SBLSCLI0.

BLSCPCSA CLIST — print common storage areas

Use the BLSCPCSA CLIST to print the common storage area (CSA) and extended
common storage area (ECSA) from the current dump. See z/OS MVS IPCS
Customization for more information about writing a CLIST that uses BLSCPCSA to
create a custom dump report.
v Syntax

%BLSCPCSA

v CLIST listing
See the BLSCPCSA member of SYS1.SBLSCLI0.

436 z/OS MVS IPCS Commands

 BLSCPNUC CLIST

BLSCPNUC CLIST — print nucleus storage areas

Use the BLSCPNUC CLIST to print the following nucleus storage areas from a
dump:
v Read-write nucleus
v Extended read-write nucleus
v Read-only nucleus
v Dynamic address translation (DAT) off nucleus
See z/OS MVS IPCS Customization for more information about writing a CLIST that
uses BLSCPNUC to create a custom dump report.
v Syntax

%BLSCPNUC

v CLIST listing
See the BLSCPNUC member of SYS1.SBLSCLI0.

BLSCPRIV CLIST — print private storage areas

BLSCPRIV prints the private and extended private storage areas for an address
space. See z/OS MVS IPCS Customization for more information about writing a
CLIST that uses BLSCPRIV to create a custom dump report.
v Syntax

%BLSCPRIV asid

v Parameter
asid
The address space identifier (ASID) for the address space to be printed.
v CLIST listing
See the BLSCPRIV member of SYS1.SBLSCLI0.

BLSCPRNT CLIST — print a dump

Use the BLSCPRNT CLIST to print one or more of the following storage areas from
a dump:
v Common storage areas
v Nucleus storage areas
v Global system queue areas
v Control block summary information and the private area for one or more of the
following:
– Each active address space at the time of the dump
– An address space specified by job name.
v Syntax

Chapter 7. IPCS CLISTs and REXX EXECs 437

BLSCPRNT CLIST

%BLSCPRNT [ CSA ]
[ NUCLEUS ]
[ SQA ]
[ CURRENT ]
[ JOBNAME(jobname) ]

v Parameters
Separate parameters with a comma.
CSA
Specifies BLSCPRNT is to print the common storage area (CSA) and
extended CSA (ECSA).
NUCLEUS
Specifies BLSCPRNT is to print the following areas:
– Read-write nucleus
– Extended read-write nucleus
– Read-only nucleus
– Dynamic address translation (DAT) off nucleus
SQA
Specifies BLSCPRNT is to print the global system queue area (SQA) and
extended SQA (ESQA).
CURRENT
Specifies BLSCPRNT is to print control block summary information and the
private area for each active address space at the time of the dump.
JOBNAME(jobname)
Specifies BLSCPRNT is to print control block summary information and the
private area for the address space specified by JOBNAME(jobname).
v Example of IPCS dialog invocation
Enter the following five commands in succession.

ALLOCATE DDNAME(IPCSTOC) SYSOUT(x)

ALLOCATE DDNAME(IPCSPRNT) SYSOUT(x)
SETDEF DSNAME(’dump.dsname’)
%BLSCPRNT NUCLEUS,SQA,CSA,CURRENT,JOBNAME(jobname)
CLOSE PRINT

v Example of IPCS batch invocation

//jobname JOB (acct#),’name’,MSGCLASS=A,REGION=4M

//PRTDUMP EXEC PGM=IKJEFT01
//SYSPROC DD DSN=SYS1.SBLSCLI0,DISP=SHR
//IPCSTOC DD SYSOUT=*
//IPCSPRNT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%BLSCDDIR DSNAME(userid.ddir) VOLUME(volid)... (optional)
IPCS
SETDEF DSN(’dump.dsname’) PRINT
%BLSCPRNT NUCLEUS,SQA,CSA,CURRENT,JOBNAME(jobname)
/*

v CLIST listing
See the BLSCPRNT member of SYS1.SBLSCLI0.

438 z/OS MVS IPCS Commands

 BLSCPSQA CLIST

BLSCPSQA CLIST — print global system queue areas

Use the BLSCPSQA CLIST to print the global system queue area (SQA) and the
extended SQA (ESQA) from a dump. See z/OS MVS IPCS Customization for more
information about writing a CLIST that uses BLSCPSQA to create a custom dump
report.
v Syntax

%BLSCPSQA

v CLIST listing
See the BLSCPSQA member of SYS1.SBLSCLI0.

BLSCSCAN CLIST — obtain a stand-alone dump screening report

Use the BLSCSCAN CLIST to create an initial screening report for a stand-alone
dump. The IPCS dialog option used to run BLSCSCAN depends on the location of
the stand-alone dump:
v If it is on tape, use the IPCS dialog SUBMIT option, then the Prepare
Stand-Alone Dump for Analysis option. IPCS submits a batch job for the CLIST
that copies the dump to DASD and routes the output dump report to a SYSOUT
data set.
v If it is already on DASD, use the IPCS dialog SUBMIT option, then the Perform
Supplementary Dump Analysis option. IPCS submits a batch job for the CLIST
that routes the output dump report to a SYSOUT data set.

You can invoke BLSCSCAN directly from an IPCS session, but the CLIST takes a
long time to complete processing.
v IPCS batch invocation for Tape
Use this option if the stand-alone dump is on tape.

------------------ Prepare Stand Alone Dump for Analysis ---------------

COMMAND ===]

Enter/verify parameters for the job.

Use ENTER to submit the job, END to terminate without job submission.

INPUT DUMP TAPES:

GENERIC UNIT ===] 3480 UNIT COUNT ===] 1
VOLUME SERIAL (Enter at least one, if more, separate with a comma.)
===] TAPIN1
LABEL (Separate subparameters with a comma.)
===] 1,NL

OUTPUT DASD DUMP DATA SET:

DATA SET NAME ===] DUMMY
GENERIC UNIT ===] 3380
VOLUME SERIAL (Enter at least one, if more, separate with a comma.)
===] SCR006

SPACE FOR OUTPUT DASD DUMP DATA SET (Number of blocks)

PRIMARY ===] 62000 SECONDARY ===] 1000

DUMP DIRECTORY ===] ’NHAN.IPCS410.DDIR’

SYSOUT CLASS ===] H

v IPCS batch invocation for DASD

Chapter 7. IPCS CLISTs and REXX EXECs 439

BLSCSCAN CLIST

Use this option if the stand-alone dump is on DASD. You must specify
BLSCSCAN as the CLIST to be invoked.

------------------ Perform Supplementary IPCS Dump Analysis ---------

COMMAND ===]

Enter/verify parameters for the job.

Use ENTER to submit the job, END to terminate without job submission.

DATA SET NAME ===]

DUMP DIRECTORY ===]
SYSOUT CLASS ===]

IPCS SUBCOMMAND, CLIST or REXX EXEC:

===] BLSCSCAN

ADDITIONAL CLIST or REXX EXEC LIBRARIES: (optional)

===]
===]

v IPCS dialog invocation

BLSCSCAN uses the current dump data set and dump directory.

------------------------- IPCS Subcommand Entry ------------------------------

Enter a free-form IPCS subcommand, CLIST, or REXX EXEC invocation below:

===] %BLSCSCAN

v CLIST listing
See the BLSCSCAN member of SYS1.SBLSCLI0.

BLSXWHER REXX EXEC — find all modules with the same entry point
name
Use the BLSXWHER EXEC to find all modules in dump storage associated with
the same entry point name. BLSXWHER searches for modules with the same entry
point in private area storage. For ASID(1), BLSXWHER also searches modules in
the link pack area (LPA). BLSXWHER displays the storage map entry for each
module, identifying the starting address and other attributes for the module.

Before searching for the modules, BLSXWHER maps the modules in the private
area and, for ASID(1), the LPA.
v Syntax

%BLSXWHER {epname} [ASID(asid)]

v Parameters
epname
Specifies the name of an entry point. BLSXWHER finds all modules with
this entry point.
ASID(asid)
Specifies the address space that BLSXWHER will search. If no ASID is

440 z/OS MVS IPCS Commands

 BLSXWHER REXX EXEC

specified, BLSXWHER uses the default address space for the dump. See
“Address processing parameters” on page 23 for information about
specifying asid.
v IPCS dialog invocation
BLSXWHER finds the storage map entries for load module ILRPGEXP in the
default address space, if any exist.

------------------------- IPCS Subcommand Entry ------------------------------

Enter a free-form IPCS subcommand, CLIST, or REXX EXEC invocation below:

===] %BLSXWHER ILRPGEXP

v REXX EXEC listing

See the BLSXWHER member of SYS1.SBLSCLI0.

Chapter 7. IPCS CLISTs and REXX EXECs 441

BLSXWHER REXX EXEC

442 z/OS MVS IPCS Commands

Chapter 8. IPCS batch mode
IPCS can be used in batch mode in a TSO/E environment. Consider using a batch
job when you:
v Use IPCS subcommands to print selected portions of a dump
v Load system dump data sets from tape or mass storage
v Unload system dump data sets to tape or mass storage
v Perform time-consuming dump analysis

Note that there are some subcommand restrictions for using IPCS in batch mode.
These restrictions are indicated under the applicable subcommand.

JCL needed to run IPCS in batch mode

Figure 44 shows the JCL needed to run IPCS in batch mode, and it shows how to
invoke the BLSCSCAN CLIST to format a problem screening report for a
stand-alone dump. The control information is saved in a dump directory data set
that can be used for later formatting sessions in batch mode or at a terminal. This
example assumes that you have an existing dump directory data set. For more
information, see the z/OS MVS IPCS User's Guide.

//IPCSJOB JOB ’acctinfo’,’PGMR output’,MSGLEVEL=(1,1),

// MSGCLASS=A,CLASS=J,NOTIFY=PGMR
//* ------------------------------------------------------
//*
//* Input: dump in data set ’PGMR.DUMP1.DUMP’
//* Output:
//* - IPCS dump directory data set for the input dump
//* (IPCSDDIR DD)
//* - Formatted output (SYSTSPRT DD)
//* - TSO/E messages (SYSTSPRT DD)
//* All of the output will have message identifiers
//* printed (with the PROFILE MSGID command in SYSTSIN)
//* ------------------------------------------------------
//IPCS EXEC PGM=IKJEFT01,DYNAMNBR=20,REGION=1500K
//IPCSDDIR DD DSN=PGMR.DUMP.DIR,DISP=(OLD,KEEP)
//*
//SYSPROC DD DSN=SYS1.SBLSCLI0,DISP=SHR
//SYSUDUMP DD SYSOUT=A
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
PROFILE MSGID
IPCS NOPARM
SETDEF DSN(’PGMR.DUMP1.DUMP’) LIST NOCONFIRM
%BLSCSCAN
END
/*

Figure 44. JCL required to run IPCS in batch mode

Note: If you plan to use the IPCS output at a terminal after the batch job has
completed, you may want to specify message and SYSOUT classes for held output
rather than the MSGCLASS=A and SYSOUT=A on the DD statements in the
example.

© Copyright IBM Corp. 1988, 2017 443

Batch Mode

IPCS cataloged procedure

The IPCS cataloged procedure is found in member BLSJIPCS of SYS1.PROCLIB.
The procedure performs the following actions:
v Invokes program IKJEFT01
v Allocates the dump data set, IPCS parmlib members CLIST library, and output
data sets.

BLSJIPCS has the following syntax.

//IPCS PROC CLIST=BLSCBSVA,DUMP=

//IEFPROC EXEC PGM=IKJEFT01,REGION=4M,DYNAMNBR=10,
// PARM=(’%&CLIST.’,’&DUMP.’)
//*
//* INPUT DATA SETS
//*
//IPCSDUMP DD DSN=&DUMP,DISP=SHR DUMP OR TRACE DATA SET
//SYSPROC DD DSN=SYS1.SBLSCLI0,DISP=SHR CLIST PROCEDURES
//SYSTSIN DD DUMMY,DCB=(RECFM=F,LRECL=80,BLKSIZE=80) TSO/E COMMANDS
//*
//* FORMATTED OUTPUT
//*
//SYSTSPRT DD SYSOUT=A BATCH TSO/E SESSION LOG
//IPCSTOC DD SYSOUT=A PRINT FILE TABLE OF CONTENTS
//IPCSPRNT DD SYSOUT=A PRINT FILE

Running CLISTs with BLSJIPCS

BLSJIPCS is designed to run with the following CLISTs:
v “BLSCBSAA CLIST — print a stand-alone dump screening report” on page 429
v “BLSCBSAP CLIST — print a stand-alone dump detailed report” on page 429
v “BLSCBSVA CLIST — print an SVC dump screening report” on page 430
v “BLSCBSVP CLIST — print an SVC dump detailed report” on page 431
v “BLSCBSYA CLIST — print a SYSMDUMP dump screening report” on page 432
v “BLSCBSYP CLIST — print a SYSMDUMP dump detailed report” on page 433

444 z/OS MVS IPCS Commands

Appendix A. IPCS symbols
This section lists the definitions of all symbols that IPCS may automatically define.
IBM recommends that installation-defined CLISTs and other dump analysis
procedures do not use symbols that might conflict with these names.

Defining symbols
If a dump analysis subcommand needs a control block, it automatically locates the
control block, validates it, and creates a definition for it in the symbol table and
storage map of your current user dump directory.

When a subcommand creates a definition, it uses the symbol name in the following
table. All numbers, n, are decimal numbers, except where specified differently.

Note:
1. Most symbols are defined by IPCS only for SVC dumps.
2. To provide acceptable performance, IPCS places definitions in the symbol table
for a dump only upon demand. The z/OS MVS IPCS User's Guide describes
how a data description (data-descr) parameter on a subcommand can cause
dynamic definition of a symbol, if it did not exist in the symbol table.
3. A function that accesses data for which an IPCS name exists (for example, an
ASCB) does not always associate an IPCS symbol with that data.
4. The symbol table is used only by IPCS. Note that many functions can be
performed in a non-IPCS environment where the symbol table is not available.

Creating symbols
If you explicitly create or modify one of the symbols, rather than let IPCS create or
modify it, you might bypass IPCS's validity checking process. For example, if you
create the symbol UCB000E with the following subcommand:
equate ucb000e 4140.

and later use the FINDUCB subcommand to locate the UCB for device 000E, the
FINDUCB subcommand finds the symbol in the symbol table and displays the
storage at the address associated with that symbol. Because your EQUATE
subcommand did not specify STRUCTURE(UCB), the storage at X‘4140’ was not
validity checked to ensure that it is a UCB.

IPCS symbol definitions

Table 28 lists the IPCS symbol definitions.
Table 28. Summary of IPCS symbol definitions
Symbol Associated data Data type definition
ABENDCODE ABEND code STRUCTURE(SDWAABCC)
AFT The ASN-first-table control block STRUCTURE(AFTE)
ASCBnnnnn Address space control block for address space nnnnn STRUCTURE(ASCB)
ASMVT System auxiliary storage management vector table STRUCTURE(ASMVT)

© Copyright IBM Corp. 1988, 2017 445

IPCS Symbols

Table 28. Summary of IPCS symbol definitions (continued)

Symbol Associated data Data type definition
ASTnnnn The ASN-second-table control block for address space STRUCTURE(ASTE)
group nnnn
ASTEnnnnn The ASN-second-table control block entry for address STRUCTURE(ASTE)
space nnnnn
ASVT System address space vector table STRUCTURE(ASVT)
ASXBnnnnn Address space extension block for address space nnnnn STRUCTURE(ASXB)
BLSQXBT Table of system materials built from parmlib members STRUCTURE(BLSQXBT)
BLSCECT, BLSCUSER, ....
BLSQXBTnnnnn Table of materials used by IPCS in ASID nnnnn for STRUCTURE(BLSQXBT)
processing of dumps and traces generated by an
ESA-mode system.
BLSQXBTG Table of materials used by IPCS in ASID nnnnn for STRUCTURE(BLSQXBT)
processing of dumps and traces generated by a system
supporting z/Architecture.
CDEpgmname A contents directory entry for entry point pgmname STRUCTURE(CDE)
COMMON The system common area AREA(COMMON)
COMPONENTID Component ID CHARACTER
CPUD CPU Dependent Block STRUCTURE(CPUD)
CSA The common system area AREA(CSA)
CSD The common system data area STRUCTURE(CSD)
CSECT Control section CHARACTER
CURSOR A fullword pointer identified by the position of the
cursor on the display terminal
CVT The system communications vector table STRUCTURE(CVT)
CVTVSTGX The virtual storage address extension to the system STRUCTURE(CVTVSTGX)
communications vector table
CVTXTNT2 The system communications vector table extension STRUCTURE(CVTXTNT2)
DAESYMPTOMS The symptoms provided by the program that requested CHARACTER
the dump and, possibly, by the program that produced
the dump. These are MVS symptoms, which are used
by dump analysis and elimination (DAE) to identify
duplicate dumps. If the primary symptom string is
longer than 256 bytes, this symbol contains the first 256
bytes of the symptom string.
DATOFFNUCLEUS The portion of the system nucleus that is used with AREA(DATOFFNUCLEUS)
dynamic address translation turned off
DIB A control block maintained to support the STRUCTURE(DIB)
data-in-virtual function
DIBX A control block maintained to support the STRUCTURE(DIBX)
data-in-virtual function
DUMPINGPROGRAM Name of the program that produced the dump CHARACTER
DUMPINGSYSTEM System that wrote and was represented by the dump CHARACTER
DUMPORIGINALDSNAME Name of the original data set to which the dump was CHARACTER
written
DUMPREQUESTOR Name of the program that requested the dump CHARACTER

446 z/OS MVS IPCS Commands

 IPCS Symbols

Table 28. Summary of IPCS symbol definitions (continued)

Symbol Associated data Data type definition
DUMPTIMESTAMP Time from the time-of-day (TOD) clock presented in CHARACTER
the following format:
mm/dd/yyyy hh:mm:ss.ffffff
DUMPTOD Time from the time-of-day (TOD) clock in a bit string STRUCTURE(TODCLOCK)
ECSA The extended common system area AREA(ECSA)
EFLPA The extended fixed link pack area AREA(EFLPA)
EMLPA The extended modified link pack area AREA(EMLPA)
ENUCLEUS The extended nucleus AREA(ENUCLEUS)
EPnnnnn Entry point nnnnn in an entry point trace MODULE
EPIDnnnnn Entry point identifier nnnnn in an entry point trace CHARACTER
EPLPA The extended pageable link pack area AREA(EPLPA)
ERRORID Error identifier used in logrec software records STRUCTURE(ERRORID)
associated with this dump on the same system. If
multiple dumps were requested, the same ERRORID
appears on these dumps.
ESQA The extended system queue area AREA(ESQA)
FINDAREA Area currently being searched by the FIND
subcommand. This area may be explicitly changed
with the EQUATE subcommand and implicitly
changed with the FIND subcommand. FINDAREA is
defined by the FIND subcommand for all types of
dump data sets; it is not limited to SVC dumps.
FLPA Fixed link pack area AREA(FLPA)
GDA Global data area STRUCTURE(GDA)
| GSCB Guarded-Storage Control Block at or near the error STRUCTURE(GSCB)
| point in a virtual dump.
| GSCBnnn Guarded-Storage Control Block for CPU nnn in a STRUCTURE(GSCB)
| stand-alone dump.
IARHVCOM High virtual common area AREA(IARHVCOM)
IARHVSHR High virtual shared area AREA(IARHVSHR)
IEAVESLA System lock area STRUCTURE(IEAVESLA)
IEFJESCTPX Pageable JESCT extension STRUCTURE(IEFJESCTPX)
IEFZB445 Device allocation default table STRUCTURE(IEFZB445)
IHSAnnnnn Interrupt handler save area for address space nnnnn STRUCTURE(IHSA)
INCIDENTTOKEN Incident token for all dumps initiated by a single STRUCTURE(IEAINTKN)
dump request
ISGGVT Global resource serialization vector table STRUCTURE(ISGGVT)
ISGGVTX Global resource serialization vector table extension STRUCTURE(ISGGVTX)
ISGQHTG Global resource serialization queue hash table for STRUCTURE(ISGQHT)
global resources
ISGQHTL Global resource serialization queue hash table for local STRUCTURE(ISGQHT)
(system) resources
ISGQHTS Global resource serialization queue hash table for step STRUCTURE(ISGQHT)
resources
ISGRSV Global resource serialization ring status vector STRUCTURE(ISGRSV)

Appendix A. IPCS symbols 447

IPCS Symbols

Table 28. Summary of IPCS symbol definitions (continued)

Symbol Associated data Data type definition
ITTCTAB Component trace anchor block STRUCTURE(ITTCTAB)
ITTCTQE name Component name CTRACE queue entry STRUCTURE(ITTCTQE)
LCCAnn Logical configuration communication area for processor STRUCTURE(LCCA)
nn
LCCAVT The LCCA vector table STRUCTURE(LCCAVT)
LCCXnn LCCA extension for cpu nn STRUCTURE(LCCX)
LDAnnnnn LDA for ASID nnnnn STRUCTURE(LDA)
LOADMODULE Load module CHARACTER
LPDEpgmname Link pack directory entry for pgmname STRUCTURE(LPDE)
MLPA The modified link pack area AREA(MLPA)
NUCLEUS The nucleus AREA(NUCLEUS)
NVT Nucleus initialization program (NIP) vector table STRUCTURE(NVT)
OSRELEASE Version, release, and modification level CHARACTER
PART Page address resolution table. This symbol is defined STRUCTURE(PART)
only by the ASMCHECK subcommand.
PCCAnn Physical configuration communication area for STRUCTURE(PCCA)
processor nn
PCCAVT The PCCA vector table STRUCTURE(PCCAVT)
PFT The system page frame table STRUCTURE(PFT)
pgmname A load module or portion of a load module originating MODULE(pgmname)
at entry point pgmname
PGTnnnnnaaaaa Page table for address space nnnnn, segment aaaaa STRUCTURE(PGTE)

The page table for segment 0 of address space 1 is

PGT00001AAAAA; for segment 1, PGT00001AAAAB,
....
PLPA The pageable link pack area AREA(PLPA)
PMRNUMBER Program Management Record (PMR) number CHARACTER
PRIMARYSYMPTOMS The symptoms provided by the program that requested CHARACTER
the dump and, possibly, by the program that produced
the dump. These are RETAIN symptoms, which are
used to search the RETAIN database. If the primary
symptom string is longer than 256 bytes, this symbol
contains the first 256 bytes of the symptom string.
PRIVATE The private area AREA(PRIVATE)
PRIVATEX The extended private area AREA(PRIVATEX)
PSAnn The prefixed storage area for processor nn STRUCTURE(PSA)
PSAVALID A usable PSA represented in the dump. PSAVALID is STRUCTURE(PSA)
obtained by accessing the PSA for the processor on
which a stand-alone dump was IPLed and by accessing
the PSA at location 0 for other types of dumps.
PSW Program status word at, or near, the error point in a STRUCTURE(PSW)
virtual dump
PSWnn Program status word for CPU nn in a stand-alone STRUCTURE(PSW)
dump

448 z/OS MVS IPCS Commands

 IPCS Symbols

Table 28. Summary of IPCS symbol definitions (continued)

Symbol Associated data Data type definition
PVT System paging vector table STRUCTURE(PVT)
RCE RSM Control and Enumeration Area STRUCTURE(RCE)
REASONCODE Reason code STRUCTURE(SDWACRC)
REGACC Access registers at or near the error point in a virtual STRUCTURE(REGACC)
dump
REGACCnn Access registers for CPU nn in a stand-alone dump STRUCTURE(REGACC)
REGCTL Control registers at or near the error point in a virtual STRUCTURE(REGCTL)
dump
REGCTLnn Control registers for CPU nn in a stand-alone dump STRUCTURE(REGCTL)
REGFLT Floating point registers at or near the error point in a STRUCTURE(REGFLT)
virtual dump
REGFLTnn Floating point registers for CPU nn in a stand-alone STRUCTURE(REGFLT)
dump
REGFPC Floating point control register at or near the error point STRUCTURE(REGFLT)
in an unformatted dump
REGFPCnn Floating point control register for CPU nn in a STRUCTURE(REGFLT)
stand-alone dump
REGGEN General purpose registers at or near the error point in STRUCTURE(REGGEN)
a virtual dump
REGGENnn General purpose registers for CPU nn in a stand-alone STRUCTURE(REGGEN)
dump
REGG64H High-order halves (bits 0-31) of 64-bit general registers STRUCTURE(REGG64H)
REGG64Hnn High-order halves (bits 0-31) of 64-bit general registers STRUCTURE(REGG64H)
for cpu nn
REGVEC Vector registers at or near the error point in a virtual STRUCTURE(REGVEC)
dump
REGVECnnn Vector registers for CPU nnn in a stand-alone dump STRUCTURE(REGVEC)
REG32CTL* 32-bit control registers at or near the error point in a STRUCTURE(REGCTL32)
virtual dump.
REG32CTLnn* 32-bit control registers for CPU nn in a stand-alone STRUCTURE(REGCTL32)
dump.
REG32GEN* 32-bit general purpose registers at or near the error STRUCTURE(REGGEN32)
point in a virtual dump.
REG32GENnn* 32-bit general purpose registers for CPU nn in a STRUCTURE(REGGEN32)
stand-alone dump.
REG64CTL* 64-bit control registers at or near the error point in a STRUCTURE(REGCTL64)
virtual dump.
REG64CTLnn* 64-bit control registers control registers for CPU nn in a STRUCTURE(REGCTL64)
stand-alone dump.
REG64GEN* 64-bit general purpose registers at or near the error STRUCTURE(REGGEN64)
point in a virtual dump.
REG64GENnn* 64-bit general purpose registers for CPU nn in a STRUCTURE(REGGEN64)
stand-alone dump.

Appendix A. IPCS symbols 449

IPCS Symbols

Table 28. Summary of IPCS symbol definitions (continued)

Symbol Associated data Data type definition
REMOTEDUMP Indicator that dumps on other systems in the sysplex CHARACTER
were requested:
v The request for this dump also requested dumps on
other systems
v This is a dump requested by another system
RONUCLEUS The read-only portion of the nucleus AREA(RONUCLEUS)
RTCT The recovery termination control table STRUCTURE(RTCT)
SAnnnnn Save area nnnnn in an entry point or 72-byte save area STRUCTURE(REGSAVE)
trace
SCCB The service call control block STRUCTURE(SCCB)
SCVT The secondary CVT STRUCTURE(SCVT)
SDWAHDR The SDWA saved in a dump header record STRUCTURE(SDWAHDR)
SECONDARYSYMPTOMS The symptoms provided by IPCS subcommands used CHARACTER
to analyze the dump. These are RETAIN symptoms,
which are used to search the RETAIN database. If the
secondary symptom string is longer than 256 bytes,
this symbol contains the first 256 bytes of the symptom
string.
SGTnnnnn The segment table for address space nnnnn STRUCTURE(SGTE)
SLIPTRAP The SLIP command that requested the dump. If the CHARACTER
actual command is longer than 256 bytes, it is
truncated.
SRBPT SRB Promotion Table STRUCTURE(SRBPT)
SVT Supervisor Vector Table STRUCTURE(SVT)
SVTX SVT Extension STRUCTURE(SVTX)
TCBCURRENT The current TCB. TCBCURRENT is only meaningful in STRUCTURE(TCB)
context of a system-detected problem that results in a
SYSMDUMP or system dump being recorded. The
concept doesn't work when the system operator causes
a SADUMP to be written or uses the DUMP command
nor does it work with dumps requested by programs
that are not running under a TCB.
TCBnnnnnaaaaa The task control block for address space nnnnn, in STRUCTURE(TCB)
position aaaaa in the priority queue

The highest priority TCB in address space 1 is

TCB00001AAAAA; the next TCB on the queue is
TCB00001AAAAB, ....

The last 2 characters in this name are alphabetic and

range from AAAAA through AZZZZ, BAAAA, ...
BZZZZ, ....
TITLE The dump title, which is contained in the dump CHARACTER
header. TITLE is defined only during dump
initialization for SVC dumps. IPCS does not support
dynamic location of the title if the symbol is DROPPED
from the symbol table.
UCBdddd The unit control block for device dddd. The dddd STRUCTURE(UCB)
designates the device number in hexadecimal.
UCM The unit control module STRUCTURE(UCM)

450 z/OS MVS IPCS Commands

 IPCS Symbols

Table 28. Summary of IPCS symbol definitions (continued)

Symbol Associated data Data type definition
X The “current address” in a dump. This symbol is
defined by most IPCS subcommands in all types of
dumps supported by IPCS.
XLpgmname An extent list for entry point pgmname STRUCTURE(XTLST)
Znnnnn A dump location that is added to the pointer stack as
nnnnn, whenever executing the STACK subcommand,
the STACK primary command, or the IPCS dialog. The
suffix nnnnn designates a sequenced number.
Note:
1. * These symbols are provided to support migration from 32-bit to 64-bit values.
2. The REG32 symbols describe 64 bytes of data. For dumps of z/Architecture mode systems, bits 0-31 of 64-bit
registers are eliminated.
3. The REG64 symbols describe 128 bytes of data. For dumps of ESA mode systems, the 32-bit registers are
extended with leading zeros.

Appendix A. IPCS symbols 451

IPCS Symbols

452 z/OS MVS IPCS Commands

 Appendix B. IPCS special symbols for system control blocks
Table 29 summarizes the IPCS special symbols. The following variables are used in
the chart.
a Represents 1 uppercase letter, A through Z
n Represents 1 decimal digit
x or d Represents 1 EBCDIC-hexadecimal digit, 1 decimal digit from 0 through 9,
or 1 uppercase letter, A through F
Table 29. IPCS special symbols
SYMBOL Minimum Maximum Symbol description
ASCBnnnnn ASCB1 ASCB99999 Address space control block for address space nnnnn.
ASTnnnn AST0 AST9999 Address space second table corresponding to
ENTRY(nnnn) in the address space first table. (An
equivalent definition is that this is the address space
second table for system address spaces from nnnn*16
through nnnn*16+15.)
ASTEnnnnn ASTE1 ASTE9999 Address space second table entry for address space
nnnnn.
ASXBnnnnn ASXB1 ASCB99999 Address space extension block for address space nnnnn.
| GSCBnnn GSCB0 CSCB999 The Guarded-Storage Control Block for processor nnn.
IHSAnnnnn IHSA1 IHSA9999 Interrupt handler save area for address space nnnnn.
LCCAnn LCCA0 LCCA99 Logical configuration communication area for processor
nn.
PCCAnn PCCA0 PCCA99 Physical configuration communication area for processor
nn.
PGTnnnnnaaaaa PGT1A PGT99999ZZZZZ Page table for segment aaaaa (base 26 number) in address
space nnnnn.
PSAnn PSA0 PSA99 Prefixed storage area for processor nn.
PSWnn PSW0 PSW99 Program status word for processor nn.
REGACCnn REGACC0 REGACC99 Access registers for processor nn.
REGCTLnn REGCTL0 REGCTL99 Control registers for processor nn.
REGFLTnn REGFLT0 REGFLT99 Floating point registers for processor nn.
REGFPCnn REGFPC0 REGFPC99 The floating point control register for processor nn.
REGGENnn REGGEN0 REGGEN99 General purpose registers for processor nn.
REGVECnnn REGVEC0 REGVEC999 The vector registers for processor nnn.
REG32CTLnn REG32CTL0 REG32CTL99 The 32-bit control registers for processor nn.
REG32GENnn REG32GEN0 REG32GEN99 The 32-bit general purpose registers for processor nn.
REG64CTLnn REG64CTL0 REG64CTL99 The 64-bit control registers for processor nn.
REG64GENnn REG64GEN0 REG64GEN99 The 64-bit general purpose registers for processor nn.
SGTnnnnn SGT1 SGT99999 The segment table for address space nnnnn.
TCBnnnnnaaaaa TCB1A TCB99999ZZZZZ The task control block in position aaaaa (base 26 number)
on the priority chain in address space nnnnn.
UCBdddd UCB0 UCBFFFF The unit control block for the device number dddd.

© Copyright IBM Corp. 1988, 2017 453

Special symbols

Table 29. IPCS special symbols (continued)

SYMBOL Minimum Maximum Symbol description
Znnnnn Z1 Z99999 A dump location that is added to the pointer stack as
nnnnn, whenever executing the STACK primary
command, the STACK subcommand, or the IPCS dialog.
The suffix nnnnn designates a sequenced number.

454 z/OS MVS IPCS Commands

Appendix C. Control blocks and data areas scanned, mapped,
and formatted
Table 30 lists the control blocks and data areas in system dumps that the
CBFORMAT subcommand can scan, create a storage map entry for, or format. The
notes referenced in the right column are at the end of the chart.

For some control blocks or data areas, IPCS creates a storage map entry but does
not scan the block or area.
Table 30. Control blocks and data areas that CBFORMAT can scan
Control block or data area Scanned Storage map entry Formatted Notes
ACE no no yes
AFT yes yes no
AFTE yes yes no 1 on page 461
AIA no no yes
ALE no no yes
AMDCPMAP no no yes
AR no no yes
ASCB yes yes yes 12 on page 462
ASEI no no yes
ASMHD no no yes
ASMVT no yes yes
ASPCT no no yes
ASSB yes yes yes
AST yes yes no 12 on page 462
ASTE yes yes no 2 on page 461 and 12
on page 462
ASVT yes yes no
ASXB yes yes yes 12 on page 462
CACHE no no yes
CDE yes yes yes
CDEMAJOR yes yes yes 3 on page 461
CDEMINOR yes yes yes 3 on page 461
CLTE no no yes
CQE yes yes no
CSD yes yes yes
CSRC4POL no no yes
CSRCPOOL no no yes
CVT yes yes yes
CVTVSTGX yes yes yes 16 on page 462
CVTXTNT2 yes yes yes 16 on page 462

© Copyright IBM Corp. 1988, 2017 455

 Control Blocks and Data Areas

Table 30. Control blocks and data areas that CBFORMAT can scan (continued)
Control block or data area Scanned Storage map entry Formatted Notes
DCB no yes no
DEIB no no yes
DEIE no no yes
DIB yes yes yes
DIBX yes yes yes
DOA yes yes yes
DOM no no yes
DSAB no no yes
DSNT no no yes 15 on page 462
EED no no yes
FRRS no no yes
GDA yes yes no
| GSCB no no yes 12 on page 462
GEPL no no yes
HED no no yes
HTBL no no yes
IATYDAT no no yes 10 on page 461
IATYDMC no no yes 10 on page 461
IATYDSS no no yes 10 on page 461
IATYFCT no no yes 10 on page 461
IATYIOP no no yes 10 on page 461
IATYMEME no no yes 10 on page 461
IATYMEMH no no yes 10 on page 461
IATYMPC no no yes 10 on page 461
IATYOSD no no yes 10 on page 461
IATYOSED no no yes 10 on page 461
IATYOSEF no no yes 10 on page 461
IATYOSEV no no yes 10 on page 461
IATYRQCI no no yes 10 on page 461
IATYRQCM no no yes 10 on page 461
IATYRQFX no no yes 10 on page 461
IATYRQGM no no yes 10 on page 461
IATYRQMD no no yes 10 on page 461
IATYRQOS no no yes 10 on page 461
IATYSEL no no yes 10 on page 461
IATYSPB no no yes 10 on page 461
IATYSVT no yes yes 10 on page 461
IATYTVT no no yes 10 on page 461
IEAVESLA no yes no
IEFJESCT no yes yes

456 z/OS MVS IPCS Commands

 Control Blocks and Data Areas

Table 30. Control blocks and data areas that CBFORMAT can scan (continued)
Control block or data area Scanned Storage map entry Formatted Notes
IEFJESCTPX yes yes no
IEFJSCVT no yes yes
IEFJSSVT no yes yes
IEFOAWTR no no yes
IEFZAGT no no yes
IEFZB41C no no yes
IEFZB445 yes yes yes
IEFZIGDE no no yes
IEFZTSRA no no yes
IHSA yes yes yes 12 on page 462
IORB no no yes
IOSB no no yes
IRB yes yes no 6 on page 461
ISGGVT yes yes no 9 on page 461
ISGGVTX yes yes no 9 on page 461
ISGQCB yes yes no 9 on page 461
ISGQEL yes yes no 9 on page 461
ISGQHT yes yes no 9 on page 461
ISGRPT no yes no
ISGRSV yes yes no 9 on page 461
ISGSAHT no yes no
IXCYERE no no yes
IXCYEVE no no yes
IXCYWRE no no yes
IXGARTE no no yes
IXGDIRCT no no yes
IXGINV no no yes
IXGIPSTK no no yes 14 on page 462
IXGLBCB no no yes
IXGLCB no no yes
IXGLCBVT no no yes
IXGLCCB no no yes
IXGLSAB no no yes
IXGPCNTL no no yes
IXGRQE no no yes
IXGSTRCB no no yes
JCT no no yes 15 on page 462
JCTX no no yes 15 on page 462
JESCT no yes no
JFCB no no yes 15 on page 462

Appendix C. Control blocks and data areas scanned, mapped, and formatted 457
Control Blocks and Data Areas

Table 30. Control blocks and data areas that CBFORMAT can scan (continued)
Control block or data area Scanned Storage map entry Formatted Notes
JFCBE no no yes 15 on page 462
JFCBX no no yes 15 on page 462
JQE no yes no
JSCB no no yes
LCCA yes yes yes 12 on page 462
LCCAVT yes yes no
LDA yes yes yes
LGE no no yes
LGVT no no yes
LGVTE no no yes
LLE no no yes
LPDE yes yes yes 3 on page 461
LPDEFINAL yes yes yes 3 on page 461
LPDEMAJOR yes yes yes 3 on page 461
LPDEMINOR yes yes yes 3 on page 461
LPDENULL yes yes yes 3 on page 461
LS no no yes
LSE no no yes
LSEH no no yes
LSET no no yes
LSSD yes yes yes
LSSG yes yes yes
MEPL no no yes
MGCRE no no yes
NVT yes yes no
ORE yes yes no
OUCB yes yes yes
OUSB no yes no
OUXB no yes no
PART no no yes
PARTE no no yes
PAT no no yes
PCB no yes no
PCCA yes yes yes 12 on page 462
PCCAVT yes yes no
PFT no yes no 4 on page 461
PFTE no yes no
PGT yes yes no 5 on page 461 and 12
on page 462
PGTE yes yes no

458 z/OS MVS IPCS Commands

 Control Blocks and Data Areas

Table 30. Control blocks and data areas that CBFORMAT can scan (continued)
Control block or data area Scanned Storage map entry Formatted Notes
PPD yes yes no
PRB yes yes no 6 on page 461
PSA yes yes yes 12 on page 462
PSW no yes yes 12 on page 462
PVT yes yes no
PXT no yes no
RB yes yes yes
RCE yes yes no
RDCM no no yes
REGACC no no yes 12 on page 462
REGCTL no no yes 12 on page 462
REGFLT no no yes 12 on page 462
REGGEN no no yes 12 on page 462
REGS no no yes
REGSAVIM no no yes
REGVEC no no yes 12 on page 462
RMCT no yes no
RQE no yes no
RSMHD no yes no
RTCT yes yes yes
RTM2WA no yes yes
RT1W yes yes no
SART no no yes
SARTE no no yes
SAT no no yes
SBC no no yes
SCB yes yes yes
SCCB yes yes yes
SCCW no no yes
SCFS no no yes
SCT no no yes 15 on page 462
SCTX no no yes 15 on page 462
SCVT yes yes no
SDCT no no yes
SDUMP no no yes
SDWA no no yes
SDWAHDR no no yes
SEPL no no yes
SGT yes yes no 7 on page 461 and 12
on page 462

Appendix C. Control blocks and data areas scanned, mapped, and formatted 459
Control Blocks and Data Areas

Table 30. Control blocks and data areas that CBFORMAT can scan (continued)
Control block or data area Scanned Storage map entry Formatted Notes
SGTE yes yes no
SIOT no no yes 15 on page 462
SIRB yes yes no 6 on page 461
SPD yes yes no
SPQE no yes no
SRB no yes yes
SSRB no no yes
STCB yes yes yes
STKE no no yes
SUPVT no no yes
SVRB yes yes no 6 on page 461
SVT no no yes
SVTX yes no yes
SXT no yes no
TCB yes yes yes 12 on page 462
TDCM no no yes
TIAB no no yes
TIOT no yes yes 11 on page 461
TIOTE no no yes 11 on page 461
TIRB yes yes no 6 on page 461
TODCLOCK no no yes 17 on page 462
TODCNULL no no yes 18 on page 462
TODC4 no no yes 19 on page 462
TQE no yes no
TSB no yes no
UCB yes yes no 12 on page 462
UCBCTC yes yes no 8 on page 461
UCBDA yes yes no 8 on page 461
UCBEXT no yes no
UCBGFX yes yes no 8 on page 461
UCBTAPE yes yes no 8 on page 461
UCBTP yes yes no 8 on page 461
UCBUR yes yes no 8 on page 461
UCB3270 yes yes no 8 on page 461
UCM yes yes yes
UCME no no yes
VCOM no no yes
VF no no yes
VSWK no no yes
WCB yes yes yes

460 z/OS MVS IPCS Commands

 Control Blocks and Data Areas

Table 30. Control blocks and data areas that CBFORMAT can scan (continued)
Control block or data area Scanned Storage map entry Formatted Notes
WEB yes no yes
WEE yes no yes
WQE yes yes yes
WSAVTC no yes no
WSAVTG no yes no
WSMA yes
XCFSTACK no no yes 13 on page 462
XESSTACK no no yes 13 on page 462
XSB no no yes
XTLST yes yes yes

Notes:
1. AFTE is validated as if it was specified as AFT. AFT is stored in the symbol
table and storage map.
2. ASTE is validated as if it were specified as AST. AST is stored in the symbol
table and storage map.
3. CDEMAJOR, CDEMINOR, LPDE, LPDEMAJOR, and LPDEMINOR are
validated as if they were specified as CDE. The correct structure type is stored
in the symbol table and storage map.
4. PFT is validated as if it were specified as PFTE. PFTE is stored in the symbol
table and storage map.
5. PGT is validated as if it were specified as PGTE. PGTE is stored in the symbol
table and storage map.
6. These control blocks are validated as if they were specified as RB. The correct
structure type is stored in the symbol table and storage map. IRB, PRB, SIRB,
and TIRB are validated as if they were specified as LPDE. The correct
structure type is stored in the symbol table and storage map.
7. SGT is validated as if it were specified as SGTE. SGTE is stored in the symbol
table and storage map.
8. UCBCTC, UCBDA, UCBGFX, UCBTAPE, UCBTP, UCBUR, and UCB3270 are
validated as if they were specified as UCB. The correct structure type is stored
in the symbol table and storage map.
9. ISGGVT, ISGGVTX, ISGQCB, ISGQEL, ISGQHT, ISGRPT, ISGRSV, and
ISGSAHT are referenced, without the prefix ISG, in z/OS MVS Data Areas in
the z/OS Internet library (www.ibm.com/systems/z/os/zos/library/bkserv).
For example, ISGGVT is listed under GVT.
10. These JES3 control blocks can be formatted by issuing the CBFORMAT
subcommand with the address of the requested control block. For example,
using the IPCS dialog BROWSE option or a CLIST to determine the address of
the control block, enter CBFORMAT 9FD308 STRUCTURE(IATYSEL). Only the
IATYSVT allows you to use the symbol name in the subcommand,
CBFORMAT IATYSVT STRUCTURE(IATYSVT).
11. TIOT formats the entire task input output table (TIOT). TIOTE formats a
single TIOT entry. If your system has DFP Version 3.2 with APARs OY29785
and OY29786 installed, and DB2 Version 2.2 with APAR PL59415 installed, you
must use TIOTE to format TIOT entries. TIOT will not find all TIOT entries.

Appendix C. Control blocks and data areas scanned, mapped, and formatted 461
Control Blocks and Data Areas

Otherwise, you can use either TIOT or TIOTE.

12. These symbols have a special naming convention in IPCS. See Appendix B,
“IPCS special symbols for system control blocks,” on page 453.
13. XCFSTACK and XESSTACK are dynamic area stack structures that contain
information that is internal to XES and XCF.
14. IXGIPSTK is a dynamic area stack structure that contains information internal
to system logger. For example, using the IPCS dialog BROWSE option or a
CLIST enter CBFORMAT nnnnnnnn FORMAT(IXGIPSTK), where nnnnnnnn is
the address of a system logger dynamic stack.
15. These scheduler work area (SWA) control blocks can be formatted using the
CBFORMAT command or subcommand. Specify the address of the X'10' byte
SWA prefix that precedes the control block rather than the address of the
actual SWA block itself.
16. See CVT in z/OS MVS Data Areas in the z/OS Internet library
(www.ibm.com/systems/z/os/zos/library/bkserv).
17. See Principles of Operation, topic TOD-clock. This is IPCS support for the 8-byte
value store by the STCK instruction.
18. Same as TODCLOCK except that zero values are treated as a special case that
implies the absence of a valid TOD-clock value in a data area field.
19. TODCLOCK LENGTH(4), bits 0-31 of a TOD-clock value are saved in some
data areas.

462 z/OS MVS IPCS Commands

Appendix D. Print dump to IPCS conversion summary
Table 31 describes the control statements or functions formerly available through
the print dump (AMDPRDMP) service aid, and points to the equivalent IPCS
subcommand or function.
Table 31. AMDPRDMP - IPCS conversion summary
Print dump control IPCS equivalent
statement or function
ASMDATA control ASMDATA verb exit
statement v Use VERBEXIT ASMDATA to format certain ASM control blocks.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT ASMDATA subcommand — format
auxiliary storage manager data” on page 328.
AVMDATA control AVMDATA verb exit
statement v Use VERBEXIT AVMDATA to format the contents of accessible availability manager
control blocks.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT AVMDATA subcommand — format
availability manager data” on page 328.
Copy and clear a source COPYDUMP
SYS1.DUMP data set v Use COPYDUMP CLEAR to clear a SYS1.DUMP data set after copying.
v See “COPYDUMP subcommand — copy dump data” on page 94
v For sample JCL to print, offload, and clear a dump, see the z/OS MVS IPCS User's
Guide.
CPUDATA control statement STATUS DATA subcommand
v Use the STATUS subcommand to gather processor-related debugging information.
v See “STATUS subcommand — describe system status” on page 273.
CVT control statement EQUATE subcommand
v Use EQUATE CVT address when you want to associate the address of the CVT
control block with a symbol.
v See “EQUATE subcommand — create a symbol” on page 132.
CVTMAP control statement CBFORMAT subcommand
v Use the CBFORMAT subcommand to display the contents of the CVT control block.
v See “CBFORMAT subcommand — format a control block” on page 72.
DAEDATA control statement DAEDATA verb exit
v Use VERBEXIT DAEDATA to format DAE dump data.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT DAEDATA subcommand — format
dump analysis and elimination data” on page 330.
Dumped storage summary LISTDUMP subcommand
v Use the LISTDUMP subcommand to provide a summary of the storage in one or
more dumps.
v LISTDUMP is described under “LISTDUMP subcommand — list dumps in dump
directory” on page 189.

© Copyright IBM Corp. 1988, 2017 463

Print Dump to IPCS Conversion

Table 31. AMDPRDMP - IPCS conversion summary (continued)

Print dump control IPCS equivalent
statement or function
EDIT control statement GTFTRACE subcommand
v Use the GTFTRACE subcommand to format GTF trace records in a dump or in a
separate GTF trace file. These incompatibilities are a result of the conversion:
– Equal signs in print dump are replaced by parentheses in IPCS.
– Standard IPCS data set and routing capabilities are available.
– START and STOP times will now also apply to blocks of records in dumps, and
can be specified in GMT or LOCAL time.
v See “GTFTRACE subcommand — format GTF trace records” on page 165.
END control statement END subcommand
v Use the END subcommand to end IPCS sessions, subcommand processing, and
CLIST processing.
v See “END subcommand — end an IPCS session” on page 130.
FORMAT control statement SUMMARY subcommand
v Use the SUMMARY subcommand with the FORMAT parameter to format major
control blocks. This report will include the RTM2 work area(s) in the dump.
v See “SUMMARY subcommand — summarize control block fields” on page 293.
Format the SDWA STATUS FAILDATA subcommand
v Use the STATUS FAILDATA subcommand to format the SDWA in the dump
header.
GO control statement Run a CLIST of IPCS subcommands
v Use a CLIST to run a series of predefined IPCS subcommands against a source data
set. See the subcommand descriptions to help you determine which subcommands
you want to run.
v See Chapter 8, “IPCS batch mode,” on page 443.
GRSTRACE control VERBEXIT GRSTRACE subcommand
statement (also QCBTRACE v Use the GRSTRACE or QCBTRACE or Q verb names on the VERBEXIT
or Q) subcommand to format the address of the major control blocks associated with
global resource serialization, the contents of control blocks on the global resources
queue, and latch statistics.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT GRSTRACE subcommand —
format Global Resource Serialization data” on page 331.
IMSDUMP control statement VERBEXIT IMSDUMP subcommand
v Use the IMSDUMP verb name on the VERBEXIT subcommand to format the
contents of Information Management System (IMS) control blocks in the dump.
v For more information about IMS DUMP formatting, see the following topics in the
IMS in IBM Knowledge Center (www.ibm.com/support/knowledgecenter/
SSEPH2):
– Invoking the IMS Offline Dump Formatter
– IMS Dump Formatter menus
INDEX DD statement IPCSTOC data set
v Allocate an IPCSTOC data set to capture the entries made by the IPCS TOC service.
The service makes entries to this data set whenever a subcommand is issued with
the PRINT parameter.
v See the Print and table of contents data sets topic in z/OS MVS IPCS User's Guide.

464 z/OS MVS IPCS Commands

 Print Dump to IPCS Conversion

Table 31. AMDPRDMP - IPCS conversion summary (continued)

Print dump control IPCS equivalent
statement or function
IOSDATA control statement IOSCHECK subcommand
v Use the IOSCHECK subcommand to format the contents of specific I/O supervisor
(IOS) control blocks and related diagnostic information.
v See “IOSCHECK subcommand — format I/O supervisor data” on page 173.
IRLM control statement VERBEXIT IRLM subcommand
v Use the IRLM verb name on the VERBEXIT subcommand to format IMS resource
lock manager (IRLM) control blocks in a dump.
v Use the IRLM SDUMP system services described in the IMS in IBM Knowledge
Center (www.ibm.com/support/knowledgecenter/SSEPH2)
JES2 control statement VERBEXIT HASMFMTM subcommand
v Use the VERBEXIT HASMFMTM subcommand to format control blocks associated
with JES2.
v JES2 dump formatting is described in z/OS JES2 Diagnosis.
JES3 control statement VERBEXIT JES3 subcommand
v Use the VERBEXIT JES3 subcommand to format control blocks associated with
JES3.
v JES3 dump formatting is described in z/OS JES3 Diagnosis.
LOGDATA control statement VERBEXIT LOGDATA subcommand
v Use the VERBEXIT LOGDATA subcommand to format the in-storage LOGREC
buffer records.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT LOGDATA subcommand — format
logrec buffer records” on page 345.
LPAMAP control statement LPAMAP subcommand
v Use the LPAMAP subcommand to format information about the pageable link pack
area (PLPA) and active LPA.
v See “LPAMAP subcommand — list link pack area entry points” on page 207.
MTRACE control statement VERBEXIT MTRACE subcommand
v Use the MTRACE verb name on the VERBEXIT subcommand to format the master
trace table.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT MTRACE subcommand — format
master trace entries” on page 348.
NEWDUMP control SETDEF subcommand
statement; NEWTAPE v Use the SETDEF parameters for data set source specification to alter the source you
control statement want to use for dump processing.
v See “SETDEF subcommand — set defaults” on page 262.
NUCMAP control statement VERBEXIT NUCMAP subcommand
v Use the NUCMAP verb name on the VERBEXIT subcommand to format the
modules in the nucleus at the time of the dump.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT NUCMAP subcommand — map
modules in the nucleus” on page 349.
ONGO control statement Create a CLIST of IPCS subcommands
v Create a CLIST to process a predefined series of IPCS subcommands.
v See Chapter 8, “IPCS batch mode,” on page 443. Refer also to the subcommand
descriptions to help you determine which subcommands you want to process.

Appendix D. Print dump to IPCS conversion summary 465

Print Dump to IPCS Conversion

Table 31. AMDPRDMP - IPCS conversion summary (continued)

Print dump control IPCS equivalent
statement or function
PRINT CSA, SQA, LIST subcommand and CLISTS
NUCLEUS control v Use these symbols on the LIST subcommand to format and display information for
statements the CSA, SQA, and NUCLEUS:
CSA, ECSA
CSA storage above and below 16 megabytes.
SQA, ESQA
SQA storage above and below 16 megabytes.
NUCLEUS
ENUCLEUS
RONUCLEUS
DATOFFNUCLEUS
Read/write nucleus storage below and above 16 megabytes; read-only nucleus
storage; the DAT-OFF portion of the nucleus.
PRIVATE, PRIVATEX
Private area below and above 16 megabytes.
v Use the BLSCPCSA, BLSCPNUC, BLSCPRIV, and BLSCPSQA CLISTs to print
information from these system areas.
v See “LIST subcommand — display storage” on page 186 for information about the
LIST subcommand.
v See Chapter 8, “IPCS batch mode,” on page 443 for a description of these CLISTs.
PRINT STORAGE, REAL LIST subcommand
control statements v Use the LIST subcommand to display storage contents.
v See “LIST subcommand — display storage” on page 186.
PRINT BLSCPRNT CLIST
CURRENT,JOBNAME v Use the BLSCPRNT CLIST to gather address space selection information and
control statements generate storage map entries defining the address spaces in a dump. To do this,
BLSCPRNT runs several IPCS subcommands. Among them are: EVALMAP, LIST,
LISTMAP, SELECT, and SUMMARY.
v See “BLSCPRNT CLIST — print a dump” on page 437 for a description of
BLSCPRNT and its operands.
Q or QCBTRACE control See GRSTRACE control statement.
statements
RSMDATA control statement RSMDATA subcommand
v Use the RSMDATA subcommand to format information about the real storage
management component.
v See “RSMDATA subcommand — analyze real storage manager data” on page 233.
SADMPMSG control VERBEXIT SADMPMSG subcommand
statement v Use the SADMPMSG verb name of the VERBEXIT subcommand to format the
SADMP execution-time virtual storage dump message log.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT SADMPMSG subcommand —
format stand-alone dump message log” on page 353.
SEGTAB control statement EQUATE subcommand
v Use the SGT symbol with an address on the EQUATE subcommand to associate the
segment table with its address and storage attributes.
v See “EQUATE subcommand — create a symbol” on page 132.

466 z/OS MVS IPCS Commands

 Print Dump to IPCS Conversion

Table 31. AMDPRDMP - IPCS conversion summary (continued)

Print dump control IPCS equivalent
statement or function
SMSDATA control statement VERBEXIT SMSDATA subcommand
v Use the SMSDATA verb name on the VERBEXIT subcommand to format storage
management subsystem (SMS) control blocks in a dump.
v SMSDATA is described in MVS/DFP Diagnosis Reference.
SRMDATA control statement VERBEXIT SRMDATA subcommand
v Use the SRMDATA verb name on the VERBEXIT subcommand to format certain
control blocks associated with the system resources manager component.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT SRMDATA subcommand — format
System Resource Manager data” on page 353.
SUMDUMP control VERBEXIT SUMDUMP subcommand
statement v Use the SUMDUMP verb name on the VERBEXIT subcommand to format the
summary dump data provided by SVC dumps.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT SUMDUMP subcommand —
format SVC summary dump data” on page 354.
SUMMARY control SUMMARY subcommand
statement v Use the SUMMARY subcommand to display or print dump data associated with an
address space.
Note: SUMMARY will not produce the dumped storage summary that the
SUMMARY JOBSUMMARY control statement produced. If you want to do this, use
the LISTDUMP subcommand; see “LISTDUMP subcommand — list dumps in
dump directory” on page 189.
v See “SUMMARY subcommand — summarize control block fields” on page 293.
TITLE control statement OPEN subcommand
v Use the TITLE parameter on the OPEN subcommand to specify a title you want to
appear on each page of the IPCS print file.
v See “OPEN subcommand — prepare resources for use by IPCS” on page 222.
TRACE control statement SYSTRACE subcommand
v Use the SYSTRACE subcommand to format trace entries for all address spaces.
v See “SYSTRACE subcommand — format system trace entries” on page 303.
TSODATA control statement VERBEXIT TSODATA subcommand
v Use the TSODATA verb name on the VERBEXIT subcommand to format
information about selected TSO/E address spaces.
v TSODATA is described in TSO/E V2 Diagnosis: Guide and Index.
VSMDATA control statement VERBEXIT VSMDATA subcommand
v Use the VSMDATA verb name on the VERBEXIT subcommand to format and print
the contents of certain VSM control blocks.
v See “VERBEXIT subcommand — run an installation-supplied or an IBM-supplied
verb exit routine” on page 324 and “VERBEXIT VSMDATA subcommand — format
virtual storage management data” on page 356.
VTAMMAP control VERBEXIT VTAMMAP subcommand
statement v Use the VTAMMAP verb name on the VERBEXIT subcommand to format VTAM
control blocks helpful to VTAM problem determination.
v See VTAM Diagnosis.

Appendix D. Print dump to IPCS conversion summary 467

Print Dump to IPCS Conversion

468 z/OS MVS IPCS Commands

Appendix E. Accessibility
Accessible publications for this product are offered through IBM Knowledge
Center (www.ibm.com/support/knowledgecenter/SSLTBW/welcome).

If you experience difficulty with the accessibility of any z/OS information, send a
detailed message to the Contact z/OS web page (www.ibm.com/systems/z/os/
zos/webqs.html) or use the following mailing address.
IBM Corporation
Attention: MHVRCFS Reader Comments
Department H6MA, Building 707
2455 South Road
Poughkeepsie, NY 12601-5400
United States

Accessibility features
Accessibility features help users who have physical disabilities such as restricted
mobility or limited vision use software products successfully. The accessibility
features in z/OS can help users do the following tasks:
v Run assistive technology such as screen readers and screen magnifier software.
v Operate specific or equivalent features by using the keyboard.
v Customize display attributes such as color, contrast, and font size.

Consult assistive technologies

Assistive technology products such as screen readers function with the user
interfaces found in z/OS. Consult the product information for the specific assistive
technology product that is used to access z/OS interfaces.

Keyboard navigation of the user interface

You can access z/OS user interfaces with TSO/E or ISPF. The following
information describes how to use TSO/E and ISPF, including the use of keyboard
shortcuts and function keys (PF keys). Each guide includes the default settings for
the PF keys.
v z/OS TSO/E Primer
v z/OS TSO/E User's Guide
v z/OS ISPF User's Guide Vol I

Dotted decimal syntax diagrams

Syntax diagrams are provided in dotted decimal format for users who access IBM
Knowledge Center with a screen reader. In dotted decimal format, each syntax
element is written on a separate line. If two or more syntax elements are always
present together (or always absent together), they can appear on the same line
because they are considered a single compound syntax element.

Each line starts with a dotted decimal number; for example, 3 or 3.1 or 3.1.1. To
hear these numbers correctly, make sure that the screen reader is set to read out

© Copyright IBM Corp. 1988, 2017 469

 punctuation. All the syntax elements that have the same dotted decimal number
(for example, all the syntax elements that have the number 3.1) are mutually
exclusive alternatives. If you hear the lines 3.1 USERID and 3.1 SYSTEMID, your
syntax can include either USERID or SYSTEMID, but not both.

The dotted decimal numbering level denotes the level of nesting. For example, if a
syntax element with dotted decimal number 3 is followed by a series of syntax
elements with dotted decimal number 3.1, all the syntax elements numbered 3.1
are subordinate to the syntax element numbered 3.

Certain words and symbols are used next to the dotted decimal numbers to add
information about the syntax elements. Occasionally, these words and symbols
might occur at the beginning of the element itself. For ease of identification, if the
word or symbol is a part of the syntax element, it is preceded by the backslash (\)
character. The * symbol is placed next to a dotted decimal number to indicate that
the syntax element repeats. For example, syntax element *FILE with dotted decimal
number 3 is given the format 3 \* FILE. Format 3* FILE indicates that syntax
element FILE repeats. Format 3* \* FILE indicates that syntax element * FILE
repeats.

Characters such as commas, which are used to separate a string of syntax

elements, are shown in the syntax just before the items they separate. These
characters can appear on the same line as each item, or on a separate line with the
same dotted decimal number as the relevant items. The line can also show another
symbol to provide information about the syntax elements. For example, the lines
5.1*, 5.1 LASTRUN, and 5.1 DELETE mean that if you use more than one of the
LASTRUN and DELETE syntax elements, the elements must be separated by a comma.
If no separator is given, assume that you use a blank to separate each syntax
element.

If a syntax element is preceded by the % symbol, it indicates a reference that is

defined elsewhere. The string that follows the % symbol is the name of a syntax
fragment rather than a literal. For example, the line 2.1 %OP1 means that you must
refer to separate syntax fragment OP1.

The following symbols are used next to the dotted decimal numbers.
? indicates an optional syntax element
The question mark (?) symbol indicates an optional syntax element. A dotted
decimal number followed by the question mark symbol (?) indicates that all
the syntax elements with a corresponding dotted decimal number, and any
subordinate syntax elements, are optional. If there is only one syntax element
with a dotted decimal number, the ? symbol is displayed on the same line as
the syntax element, (for example 5? NOTIFY). If there is more than one syntax
element with a dotted decimal number, the ? symbol is displayed on a line by
itself, followed by the syntax elements that are optional. For example, if you
hear the lines 5 ?, 5 NOTIFY, and 5 UPDATE, you know that the syntax elements
NOTIFY and UPDATE are optional. That is, you can choose one or none of them.
The ? symbol is equivalent to a bypass line in a railroad diagram.
! indicates a default syntax element
The exclamation mark (!) symbol indicates a default syntax element. A dotted
decimal number followed by the ! symbol and a syntax element indicate that
the syntax element is the default option for all syntax elements that share the
same dotted decimal number. Only one of the syntax elements that share the
dotted decimal number can specify the ! symbol. For example, if you hear the
lines 2? FILE, 2.1! (KEEP), and 2.1 (DELETE), you know that (KEEP) is the

470 z/OS MVS IPCS Commands

 default option for the FILE keyword. In the example, if you include the FILE
keyword, but do not specify an option, the default option KEEP is applied. A
default option also applies to the next higher dotted decimal number. In this
example, if the FILE keyword is omitted, the default FILE(KEEP) is used.
However, if you hear the lines 2? FILE, 2.1, 2.1.1! (KEEP), and 2.1.1
(DELETE), the default option KEEP applies only to the next higher dotted
decimal number, 2.1 (which does not have an associated keyword), and does
not apply to 2? FILE. Nothing is used if the keyword FILE is omitted.
* indicates an optional syntax element that is repeatable
The asterisk or glyph (*) symbol indicates a syntax element that can be
repeated zero or more times. A dotted decimal number followed by the *
symbol indicates that this syntax element can be used zero or more times; that
is, it is optional and can be repeated. For example, if you hear the line 5.1*
data area, you know that you can include one data area, more than one data
area, or no data area. If you hear the lines 3* , 3 HOST, 3 STATE, you know
that you can include HOST, STATE, both together, or nothing.

Notes:
1. If a dotted decimal number has an asterisk (*) next to it and there is only
one item with that dotted decimal number, you can repeat that same item
more than once.
2. If a dotted decimal number has an asterisk next to it and several items
have that dotted decimal number, you can use more than one item from the
list, but you cannot use the items more than once each. In the previous
example, you can write HOST STATE, but you cannot write HOST HOST.
3. The * symbol is equivalent to a loopback line in a railroad syntax diagram.
+ indicates a syntax element that must be included
The plus (+) symbol indicates a syntax element that must be included at least
once. A dotted decimal number followed by the + symbol indicates that the
syntax element must be included one or more times. That is, it must be
included at least once and can be repeated. For example, if you hear the line
6.1+ data area, you must include at least one data area. If you hear the lines
2+, 2 HOST, and 2 STATE, you know that you must include HOST, STATE, or
both. Similar to the * symbol, the + symbol can repeat a particular item if it is
the only item with that dotted decimal number. The + symbol, like the *
symbol, is equivalent to a loopback line in a railroad syntax diagram.

Appendix E. Accessibility 471

472 z/OS MVS IPCS Commands
Notices
This information was developed for products and services that are offered in the
USA or elsewhere.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
United States of America

For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

© Copyright IBM Corp. 1988, 2017 473

 This information could include missing, incorrect, or broken hyperlinks.
Hyperlinks are maintained in only the HTML plug-in output for the Knowledge
Centers. Use of hyperlinks in other output formats of this information is at your
own risk.

Any references in this information to non-IBM websites are provided for

convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
Site Counsel
2455 South Road
Poughkeepsie, NY 12601-5400
USA

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

474 z/OS MVS IPCS Commands

 COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.

Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the following
terms and conditions.

Applicability
These terms and conditions are in addition to any terms of use for the IBM
website.

Personal use

You may reproduce these publications for your personal, noncommercial use
provided that all proprietary notices are preserved. You may not distribute, display
or make derivative work of these publications, or any portion thereof, without the
express consent of IBM.

Commercial use
You may reproduce, distribute and display these publications solely within your
enterprise provided that all proprietary notices are preserved. You may not make
derivative works of these publications, or reproduce, distribute or display these
publications or any portion thereof outside your enterprise, without the express
consent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses or

rights are granted, either express or implied, to the publications or any
information, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its
discretion, the use of the publications is detrimental to its interest or, as
determined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in full
compliance with all applicable laws and regulations, including all United States
export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE

PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING
BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,

Notices 475
 NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy Statement

IBM Software products, including software as a service solutions, (“Software
Offerings”) may use cookies or other technologies to collect product usage
information, to help improve the end user experience, to tailor interactions with
the end user, or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings
can help enable you to collect personally identifiable information. If this Software
Offering uses cookies to collect personally identifiable information, specific
information about this offering’s use of cookies is set forth below.

Depending upon the configurations deployed, this Software Offering may use
session cookies that collect each user’s name, email address, phone number, or
other personally identifiable information for purposes of enhanced user usability
and single sign-on configuration. These cookies can be disabled, but disabling
them will also eliminate the functionality they enable.

If the configurations deployed for this Software Offering provide you as customer
the ability to collect personally identifiable information from end users via cookies
and other technologies, you should seek your own legal advice about any laws
applicable to such data collection, including any requirements for notice and
consent.

For more information about the use of various technologies, including cookies, for
these purposes, see IBM’s Privacy Policy at ibm.com/privacy and IBM’s Online
Privacy Statement at ibm.com/privacy/details in the section entitled “Cookies,
Web Beacons and Other Technologies,” and the “IBM Software Products and
Software-as-a-Service Privacy Statement” at ibm.com/software/info/product-
privacy.

Policy for unsupported hardware

Various z/OS elements, such as DFSMS, JES2, JES3, and MVS, contain code that
supports specific hardware servers or devices. In some cases, this device-related
element support remains in the product even after the hardware devices pass their
announced End of Service date. z/OS may continue to service element code;
however, it will not provide service related to unsupported hardware devices.
Software problems related to these devices will not be accepted for service, and
current service activity will cease if a problem is determined to be associated with
out-of-support devices. In such cases, fixes will not be issued.

Minimum supported hardware

The minimum supported hardware for z/OS releases identified in z/OS
announcements can subsequently change when service for particular servers or
devices is withdrawn. Likewise, the levels of other software products supported on
a particular release of z/OS are subject to the service support lifecycle of those
products. Therefore, z/OS and its product publications (for example, panels,
samples, messages, and product documentation) can include references to
hardware and software that is no longer supported.
v For information about software support lifecycle, see: IBM Lifecycle Support for
z/OS (www.ibm.com/software/support/systemsz/lifecycle)

476 z/OS MVS IPCS Commands

 v For information about currently-supported IBM hardware, contact your IBM
representative.

Programming interface information

This book documents information NOT intended to be used as Programming
Interfaces of z/OS.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available at Copyright and Trademark
information (www.ibm.com/legal/copytrade.shtml).

Notices 477
478 z/OS MVS IPCS Commands
Index
Special characters ALIGN primary command
description 387
* sign allocatable device
literal value notation 14 analyzing dumps 54
allocate queue 63
allocation
A obtaining dump output 340, 341
ABEND command alphabetic character
to cancel IPCS processing 3 symbol used in picture strings 12
ABENDCODE symbol ALTER IPCS subcommand
for IPCS 445 description 53
ABSOLUTE parameter ALTLIB command of TSO/E
in IPCS data description parameter 24 special considerations for an IPCS session 37
access register ANALYZE IPCS subcommand
formatting related dump data description 54
IEAVD30 exit routine 313 AOM (asynchronous operations manager)
IEAVXD01 exit routine 313 formatting dump data 325
access register data AOMDATA IPCS verb name 325
analyzing dumps 66 APPC/MVS (Advanced Program-to-Program
accessibility 469 Communications/MVS)
contact IBM 469 APPC/MVS server 62
features 469 obtaining diagnosis data 63
ACTIVE parameter APPC/MVS transaction scheduler
of SETDEF IPCS subcommand 265 obtaining diagnosis data 70
ADDDUMP IPCS subcommand obtaining diagnosis data 62
description 52 APPCDATA IPCS subcommand
examples 53 description 62
address SERVERDATA report 63
identifying where an address resides in a dump 361 ARCHECK IPCS subcommand
address expression description 66
in IPCS data description parameter 19 AREA parameter
ADDRESS parameter in IPCS data description parameter 30
in IPCS data description parameter 19 array parameter
address pointer entry description 34
renumbering 232 ASCB (address space control block)
address positional parameter analyzing with CBSTAT IPCS subcommand 80
in IPCS data description parameter 19 displaying address for an address space in a dump 259
address processing parameter displaying using SUMMARY IPCS subcommand 293
description 23 ASCB exit routine
address range running an installation-supplied routine 69
in IPCS data description parameter 19 ASCBEXIT IPCS subcommand
address space description 69
displaying ASID, job name, and ASCB address in a return codes 70
dump 259 testing installation-supplied exits 270
identifying in dump through an STOKEN 212 ASCBnnnnn symbol
address type for IPCS 445
floating-point in IPCS 21 ASCHDATA IPCS subcommand
general-purpose in IPCS 21 description 70
indirect in IPCS 22 ASCII character string
literal in IPCS 21 notation 13
relative in IPCS data description parameter 21 ASCII IPCS primary command
symbolic in IPCS data description parameter 20 description 388
address-processing-parameter ASID (address space identifier)
of SETDEF IPCS subcommand 264 displaying for each address space in a dump 259
AFT symbol ASID parameter
for IPCS 445 in IPCS data description parameter 24
ALCWAIT IPCS verb name ASM (auxiliary storage manager)
description 328 analyzing data in dump 72
ALIGN parameter formatting data in dump 328
of SETDEF IPCS subcommand DISPLAY parameter 268 ASMCHECK IPCS subcommand
description 72

© Copyright IBM Corp. 1988, 2017 479

ASMDATA IPCS verb name BLS9CALL command of TSO/E (continued)
description 328 TITLE parameter 40
ASMVT symbol BLSAIPST IPCS verb name
for IPCS 445 description 328
assistive technologies 469 BLSCALTL CLIST 427, 428
ASTEnnnnn symbol BLSCBSAA CLIST
for IPCS 446 description 429
ASTnnnn symbol BLSCBSAP CLIST
for IPCS 446 description 429
ASVT symbol BLSCBSVA CLIST
for IPCS 446 description 430
ASXBnnnnn symbol BLSCBSVB CLIST
for IPCS 446 description 431
attention processing BLSCBSVP CLIST
for IPCS CLISTs 3 description 431
for IPCS REXX execs 4 BLSCBSYA CLIST
for IPCS subcommands 3 description 432
attribute parameter BLSCBSYB CLIST
description 29 description 433
availability manager BLSCBSYP CLIST
formatting data in dump 328 description 433
AVMDATA IPCS verb name BLSCCOMP CLIST
description 328 use of COMPARE subcommand 89
BLSCDDIR CLIST 427
description 434
B BLSCDROP CLIST 427
description 435
batch job
BLSCEDUM CLIST
creating dump directory for IPCS processing 434
description 139
directing IPCS output 2
BLSCEMAP CLIST
batch mode processing 443
description 143
binary fullword
BLSCEPTR CLIST
notation 11
description 436
binary halfword
BLSCESYM CLIST
notation 12
description 149
binary number
BLSCLIBD CLIST 427
notation on subcommands 10
BLSCPCSA CLIST 466
BIT parameter
description 436
in IPCS data description parameter 30
BLSCPNUC CLIST 466
BLOCK parameter
description 437
in IPCS data description parameter 24
BLSCPRIV CLIST 466
BLS18451I message
description 437
information from WHERE IPCS subcommand or primary
BLSCPRNT CLIST 466
command 364
description 437
BLS9 command of TSO/E 38
BLSCPSQA CLIST 466
TASKLIB parameter 38
description 439
TEST parameter 38
BLSCRNCH CLIST
BLS9CALL command of TSO/E 39
description 253
HEADING parameter 40
BLSCSCAN CLIST
LIBRARY parameter 40
description 439
MEMBER parameter 40
BLSCSETD CLIST
NOHEADING parameter 40
description 137
NOTITLE parameter 40
BLSJIPCS cataloged procedure
PAGE parameter 40
description 444
parm parameter 39
use with BLSCBSAA CLIST 429
program parameter 39
use with BLSCBSAP CLIST 429
STATUS parameter 40
use with BLSCBSVA CLIST 430
SYSIN parameter 40
use with BLSCBSVP CLIST 431
SYSLIB parameter 40
use with BLSCBSYA CLIST 432
SYSLIN parameter 40
use with BLSCBSYP CLIST 433
SYSLMOD parameter 40
BLSQXBT symbol
SYSPRINT parameter 40
for IPCS 446
SYSPUNCH parameter 40
BLSQXBTnnnnn symbol
SYSTERM parameter 40
for IPCS 446
SYSUT1 parameter 40
BLSQZBTG symbol
SYSUT2 parameter 40
for IPCS 446
SYSUT3 parameter 41
SYSUT4 parameter 41

480 z/OS MVS IPCS Commands

BLSXWHER REXX EXEC command code
description 440 for IPCS inventory panel 386
BROWSE option common storage tracking function
using CANCEL IPCS primary command 388 analyzing dumps 358
using CBFORMAT IPCS primary command 388 COMMON symbol
for IPCS 446
COMMTASK (communications task)
C formatting dump data using COMCHECK IPCS
subcommand 83
CANCEL IPCS primary command
communications task data
description 388
analyze 83
cancel processing 3
COMPARE IPCS subcommand
captured UCB pages
description 87
formatting with IOSCHECK subcommand 175
example used in a CLIST 89
CB (Component Broker)
return codes 89
obtaining formatted data 329
comparing
CBDATA IPCS verb name
dump data 87
description 329
COMPDATA parameter
CBFORMAT IPCS primary command
in IPCS data description parameter 25
description 388
component trace
CBFORMAT IPCS subcommand
analyzing records in a dump or trace data set 108
description 72
copying entries 101
return codes 74
COMPONENTID symbol
CBSTAT IPCS subcommand
for IPCS 446
description 78
CONDENSE primary command
return codes 79
description 389
CDEpgmname symbol
CONFIRM parameter
for IPCS 446
of SETDEF IPCS subcommand 265
cell
console management
add entry to symbol table 254
formatting dump data using COMCHECK IPCS
search a CPOOL 254
subcommand 83
central processor
contact
displaying status in a dump 273
z/OS 469
central storage
contention data
diagnosis information 233
analyzing dumps 54
chain
control block
using RUNARRAY subcommand 248
add entry to symbol table 249
using RUNCHAIN subcommand 249
format 72
character
formatting and displaying using CBFORMAT IPCS
symbols used in picture strings 12
subcommand 72
CHARACTER parameter
formatting with CBFORMAT IPCS primary command 388
in IPCS data description parameter 30
IPCS symbol 453
character string
key fields from dump
notation 11, 13
using SUMMARY IPCS subcommand 293
CICS (Customer Information Control System)
list of control blocks scanned, mapped and formatted by
formatting dump data 325
IPCS 455
CICSDATA IPCS verb name 325
obtain status 78
clean up
search a chain 249
dump directory 435
search an array 248
CLIST
status using CBSTAT IPCS subcommand 78
add notes to output 216
TCB-related 312
description 427
validating using the SCAN IPCS subcommand 257
identifying libraries 37
control register
invoked from IPCS dialog 397
formatting in a dump 275
invoking with TSO subcommand of IPCS 322
copy
retrieving dump directory information 137
CTRACE entries 101
retrieving information into variables 135
GTF records 101
retrieving storage map information into variables 140
trace entries 101
retrieving symbol table information into variables 145
COPYCAPD IPCS subcommand
variables 149, 172
description 89
CLOSE subcommand
return codes 90
description 81
COPYDDIR IPCS subcommand
example 83
description 92
COMCHECK IPCS subcommand
COPYDUMP IPCS subcommand
description 83
description 94
command
return codes 100
syntax conventions 6

Index 481
COPYTRC IPCS subcommand data description parameter (continued)
description 101 description 17
return codes 105 NOREMARK parameter 35
COUPLE IPCS subcommand REMARK parameter 35
description 105 data entry panel
coupling facility IPCS and ISPF primary commands and PF keys 383
formatting structure data 283 data management control blocks
CPOOL formatting related dump data
using RUNCPOOL subcommand 254 IECDAFMT exit routine 313
CPU parameter data set
in IPCS data description parameter 25 close to IPCS processing 81
CPUD symbol dump directory 2
for IPCS 446 obtaining contents summary report 189
cross system extended services opening for IPCS processing 222
formatting dump information 370 data space
CSA (common storage area) describing in a dump 17
common storage tracking function displaying 26
analyzing dumps 358 identifying in dump through an STOKEN 212
print storage from a dump 436 data-in-virtual
CSA symbol formatting dump data 120
for IPCS 446 DATASET parameter
CSD data area of SETDEF IPCS subcommand 265
formatting with CBFORMAT IPCS subcommand 75 DATOFFNUCLEUS symbol
CSD symbol for IPCS 446
for IPCS 446 DB2
CSECT formatting dump data 325
information from WHERE IPCS subcommand or primary DDNAME parameter
command 363 of SETDEF IPCS subcommand 266
CSECT symbol decimal number
for IPCS 446 converting to hexadecimal 172
CTRACE IPCS subcommand notation on subcommands 10
description 108 default value
merging formatted trace entries 209 displaying IPCS default values using SETDEF IPCS
current address subcommand 262
in a dump formatted by IPCS 451 PROFILE-defined 228
X symbol in IPCS 21 setting IPCS default values using SETDEF IPCS
CURSOR symbol subcommand 262
for IPCS 446 delayed issue queue
CVT (communication vector table) branch entry and NIP time messages 348
formatting with CBFORMAT IPCS subcommand 75 deletion
CVT symbol storage map records 127
for IPCS 446 device allocation data
CVTVSTGX symbol obtaining formatted output 328
for IPCS 446 DFP (Data Facility Product)
CVTXTNT2 symbol formatting dump data 325
for IPCS 446 diagnostic worksheet
displaying from dump 273
DIB symbol
D for IPCS 446
DIBX symbol
D IPCS line command
for IPCS 446
description 415
DIMENSION parameter
DAE (dump analysis and elimination)
in IPCS data description parameter 35
formatting data in dump 330
displaying operation code
DAEDATA IPCS verb name
using OPCODE IPCS primary command 402
description 330
DIVDATA IPCS subcommand
DAESYMPTOMS symbol
description 120
for IPCS 446
DLF (data lookaside facility)
DAT-off nucleus
obtaining diagnosis data 123
print storage from a dump 437
DLFDATA IPCS subcommand
data area
description 123
list of data areas scanned, mapped and formatted by
DOCPU IPCS subcommand
IPCS 455
description 118
validating using the SCAN IPCS subcommand 257
stand-alone dump 118
data description parameter
DOMAIN parameter
address processing parameters 23
in IPCS data description parameter 25
array parameters 34
attribute parameters 29

482 z/OS MVS IPCS Commands

DOWN IPCS primary command dump header
description 390 formatting title 187
DROPDUMP dump title
clear uncataloged DSNAME 435 displaying using LIST IPCS subcommand 186
DROPDUMP IPCS subcommand displaying using SYSDSCAN command 43
description 125 formatting 187
examples 127 obtaining a summary of dump titles 94
DROPMAP IPCS subcommand dumping services
description 127 obtaining dump output 334, 335
DROPSYM IPCS subcommand DUMPINGPROGRAM symbol
description 129 for IPCS 446
examples 130 DUMPINGSYSTEM symbol
dsname entries for IPCS 446
BLSCDROP CLIST 435 DUMPORIGINALDSNAME symbol
DSNAME entries for IPCS 446
remove 435 DUMPREQUESTOR symbol
DSNAME parameter for IPCS 446
of SETDEF IPCS subcommand 265 DUMPTIMESTAMP symbol
DSNWDMP IPCS verb name 325 for IPCS 447
dump DUMPTOD symbol
analyzing for IPCS 447
access register data 66 dynamic configuration change
data-in-virtual data 120 displaying EDT data 194
ENQ contention 54
for allocatable devices 54
for contention data 54
for control block status 78
E
E IPCS line command
for real frames 54
description 417
for resource contention data 54
EBCDIC IPCS primary command
for suspend locks 54
description 390
I/O contention 54
ECSA (extended common storage area)
analyzing component trace entries 108
print storage from a dump 436
analyzing system status 273
ECSA symbol
close to IPCS processing 81
for IPCS 447
copying 89, 94
EDT (eligible device table)
data comparison 87
displaying data 194
displaying storage 186
primary EDT 194
displaying symbol definitions 199
secondary EDT 194
displaying title in dump data set 43
EFLPA symbol
extracting a single dump from a string of dumps 94
for IPCS 447
multiple dumps in a single data set 94
EMLPA symbol
printing 437
for IPCS 447
reducing the size of a dump 94
END IPCS primary command
retrieving data into variables 149
description 391
retrieving dump directory information 137
END IPCS subcommand
suppressing output 270
description 130
dump analysis
return codes 131
using IPCS commands 381
ENF
using IPCS line commands 382
list listeners 340
using IPCS primary commands 381
ENQ contention
using ISPF primary commands 383
analyzing dumps 54
dump data set
ENTRY parameter
displaying dump titles 43
in IPCS data description parameter 34
dump directory
ENUCLEUS symbol
adding source description 52
for IPCS 447
copying source description 92
EPLPA symbol
creating with BLSCDDIR CLIST 434
for IPCS 447
deleting record 125
EPTRACE IPCS subcommand
displaying list of sources 189
description 131
example of creating and initializing 2
EQUATE IPCS primary command
freeing space 129
description 391
initialize using IPCSDDIR command 42
EQUATE IPCS subcommand
multiple processors 118
return codes 132
opening for IPCS processing 222
ERROR parameter
retrieving information 137
of SETDEF IPCS subcommand FLAG parameter 269
dump display reporter panel
ERRORID symbol
IPCS and ISPF primary commands and PF keys 385
for IPCS 447

Index 483
ESQA (extended global system queue area) FIND IPCS primary command
print storage from a dump 439 description 393
ESQA symbol example using quoted-string notation 13
for IPCS 447 FIND IPCS subcommand
EVALDEF IPCS subcommand description 153
description 135 example using picture strings 12
example used in a CLIST 137 FINDAREA symbol 153
EVALDUMP IPCS subcommand for IPCS 447
description 137 FINDMOD IPCS subcommand
example used in a CLIST 139 description 158
EVALMAP IPCS subcommand FINDSWA IPCS subcommand
description 140 description 159
example used in a CLIST 143 FINDUCB IPCS subcommand
EVALPROF IPCS subcommand description 160
description 144 FLAG parameter
EVALSYM IPCS subcommand of SETDEF IPCS subcommand 268
description 145 FLOAT parameter
example used in a CLIST 149 in IPCS data description parameter 31
EVALUATE IPCS subcommand floating-point address type
description 149 in IPCS data description parameter 21
return codes FLPA symbol
CLIST, REXX, or DIALOG return codes 152 for IPCS 447
example full-screen display 381
FULL form report for RSM trace entries 116 using IPCS commands 381
QUERY FULL report fullword pointer
for the COMP1.ASID(0200).FUNC2.SVC3 trace 115 notation 11
QUERY report
COMP1 multiple-trace component trace 114
COMP1.ASID(0200) HEAD level 114
COMP1.ASID(0200).FUNC2.SVC3 trace 114
G
GDA symbol
Request a list of traces defined in a dump 113
for IPCS 447
SHORT form report for RSM trace entries 115
general purpose register
SUMMARY form report for RSM trace entries 115
formatting in a dump 275
TALLY form report 117
general value
EXCLUDE IPCS primary command
ASCII character string notation 13
description 392
binary fullword notation 11
exit routine
binary halfword notation 12
for analyzing ASCBs in a dump 69
character string notation 11, 13
invoking
fullword pointer notation 11
using ASCBEXIT IPCS subcommand 69
hexadecimal string notation 14
invoking TCB exit routine
notation types 10
using TCBEXIT IPCS subcommand 312
picture string notation 12
invoking using VERBEXIT IPCS subcommands 324
quoted string notation 13
testing installation-supplied exits 270
text string notation 14
exit service
word notation 14
activating traps 318
general-purpose address type
deactivating traps 316
in IPCS data description parameter 21
listing status of traps 314
global resource serialization
extended MCS console
formatting queue information 161
formatting dump data using COMCHECK IPCS
obtaining dump output 331
subcommand 83
GO IPCS subcommand
extended private storage area
description 161
printing storage from a dump 437
GRSDATA IPCS subcommand
extended read-write nucleus
description 161
print storage from a dump 437
GRSTRACE IPCS verb name
external interrupt
description 331
formatting GTF trace records 168
GSCB symbol
for IPCS 447
GSCBnnn symbol
F for IPCS 447
F IPCS line command GTF (generalized trace facility)
description 418, 422 copying trace records 101
F parameter formatting trace records 165
in IPCS data description parameter 32 GTFTRACE IPCS subcommand
FILE parameter description 165
of SETDEF IPCS subcommand 266 merging formatted trace entries 209

484 z/OS MVS IPCS Commands

H INFORMATIONAL parameter
of SETDEF IPCS subcommand FLAG parameter 269
HASMFMTM IPCS verb name 325 INSTRUCTION parameter
HEADER parameter in IPCS data description parameter 31
in IPCS data description parameter 26 integer
HEADING parameter of BLS9CALL command 40 converting decimal to hexadecimal 172
HELP IPCS subcommand converting hexadecimal to decimal 172
description 171 positive value notations 10
hexadecimal number signed value notations 10
converting to decimal 172 INTEGER IPCS subcommand
notation on subcommands 10 description 172
HEXADECIMAL parameter inventory panel
in IPCS data description parameter 30 IPCS command codes 386
hexadecimal string IOS (input/output supervisor)
notation 14 formatting related dump data
IECIOFMT exit routine 313
IOSCHECK IPCS subcommand 173
I IOSCHECK IPCS subcommand
I IPCS line command description 173
description 419 IPCS (interactive problem control system)
I/O contention 72-Byte save areas 131
analyzing dumps 54 access line mode 2
IARHVCOM symbol batch mode processing 443
for IPCS 447 description of subcommands 45
IARHVSHR symbol directing output 2
for IPCS 447 end a session 130
IEAVD30 exit routine interrupt processing 3
running 313 introduction 1
IEAVESLA symbol IPCS primary and line commands 381
for IPCS 447 messages 4
IEAVTFCB IPCS verb name setting session parameters 41
description 334 sources for processing 1
IEAVTFMT exit routine start a session 41
running 313 syntax conventions 6
IEAVTSFS IPCS verb name task directory for subcommands 46
description 335 TSO/E commands 37
IEAVXD01 exit routine IPCS command of TSO/E
running 313 description 41
IECDAFMT exit routine PARM parameter 41
running 313 TASKLIB parameter 41
IECIOFMT exit routine IPCS dialog
running 313 ISPF primary commands 381
IEFENFVX IPCS verb name line commands 381
description 340 task directory 383
IEFIVAWT IPCS verb name primary commands 381
description 340 task directory 383
IEFIVIGD IPCS verb name returning to previous panel 391
description 341 stand-alone dump analysis
IEFJESCTPX symbol from DASD 439
for IPCS 447 from tape 439
IEFRDER file 429 SVC dump analysis 431
IEFZB445 symbol SYSMDUMP dump analysis 433
for IPCS 447 IPCS primary command
IHSAnnnnn symbol description 397
for IPCS 447 IPCS subcommand
IKJEFT01 program invoking from IPCS dialog 397
invoked by BLSJIPCS cataloged procedure 444 IPCSDATA IPCS subcommand
IMS (Information Management System) description 179
formatting dump data 325 IPCSDDIR command of TSO/E
IMSDUMP IPCS verb name 325 CONFIRM parameter 43
INCIDENTTOKEN symbol description 42
for IPCS 447 return codes 43
indirect address REUSE parameter 42
in IPCS data description parameter 22 IPCSDDIR data set
information opening for IPCS processing 222
online help 171 output for COPYDDIR IPCS subcommand 92
IPCSINDD ddname 94

Index 485
IPCSPRnn parmlib member keyboard
specified on IPCS command 41 navigation 469
IPCSPRNT PF keys 469
subcommand 406 shortcut keys 469
IPCSPRNT data set keyword parameter
add notes to output 216 data description 17
opening for IPCS processing 222 description for IPCS 5
output from BLSCBSAA CLIST 429
output from BLSCBSAP CLIST 429
output from BLSCBSVA CLIST 430
output from BLSCBSVP CLIST 431
L
L IPCS line command
output from BLSCBSYA CLIST 432
description 422
output from BLSCBSYP CLIST 433
Language Environment
routing subcommand listing 269
LEDATA 342
IPCSTOC data set
obtaining formatted data 342
opening for IPCS processing 222
Language Environment Debugging Guide 342
IPLDATA IPCS subcommand
latch contention
description 185
analyzing dumps 58
IRLM IPCS verb name 325
LCCAnn symbol
ISGGVT symbol
for IPCS 448
for IPCS 447
LCCAVT symbol
ISGGVTX symbol
for IPCS 448
for IPCS 447
LE (Language Environment)
ISGQHTG symbol
formatting dump data 325
for IPCS 447
LE IPCS verb name 325
ISGQHTL symbol
LEDATA IPCS verb name
for IPCS 447
description 342
ISGQHTS symbol
LEFT IPCS primary command
for IPCS 447
description 399
ISGRSV symbol
LENGTH parameter
for IPCS 447
in IPCS data description parameter 18, 22
ISPEXEC IPCS subcommand
of SETDEF IPCS subcommand 269
description 186
LIBRARY parameter of BLS9CALL command 40
ISPF (Interactive System Productivity Facility)
line command
function pool dialog variables 140
IPCS dialog 381
retrieving dump directory information 137
task directory 383
retrieving session default values into variables 135
removal using RESET primary command 407
retrieving storage map information into variables 140
viewing IPCS output stream 404
retrieving symbol table information into variables 145,
line size
149
adjusting 228
invoking under IPCS 322
list
request a dialog service 186
dump title 186
request IPL reports 185
LIST IPCS subcommand
ITTCTAB symbol
description 186
for IPCS 448
LISTDUMP IPCS subcommand
description 189
LISTEDT IPCS subcommand
J description 194
JES XCF component example 197
formatting dump data 325 listeners
obtaining dump output 342 ENF code 340
JES2 subsystem LISTMAP IPCS subcommand
formatting dump data 325 description 197
JES3 IPCS verb name 325 example 199
JES3 subsystem LISTSYM IPCS subcommand
formatting dump data 325 description 199
JESXCF IPCS verb name 325 examples 200
description 342 LISTTOD IPCS subcommand
job description 201
displaying name for address space in a dump 259 example 203
LISTUCB IPCS subcommand
description 203
K literal
assign value 205
key
literal address
PF
in IPCS data description parameter 21
used in IPCS dialog 383

486 z/OS MVS IPCS Commands

LITERAL IPCS subcommand module
description 205 find in a dump 158
literal value MODULE parameter
finding in a dump 153 in IPCS data description parameter 32
general values 10 MORE IPCS primary command
positive integer 10 description 402
signed integer 10 MTRACE IPCS verb name
symbolic literal 15 description 348
types 9 MULTIPLE parameter
load module in IPCS data description parameter 35
information from WHERE IPCS subcommand or primary multiple processors
command 363 obtain dump data 118
load module library
specify search order for IPCS analysis programs 41
LOADMODULE symbol
for IPCS 448
N
name
LOCATE IPCS primary command
for IPCS symbols 445
description 400
NAME IPCS subcommand
LOGDATA IPCS verb name
description 212
description 345
NAMETOKN IPCS subcommand
LOGGER IPCS subcommand
description 213
description 207
navigation
logrec
keyboard 469
obtaining formatted output from a dump 345
NIP hardcopy message buffer 348
lowercase letter
NOALIGN parameter
symbol used in picture strings 12
of SETDEF IPCS subcommand DISPLAY parameter 268
LPA (link pack area)
NOALIGN primary command
list entry points in a dump 207
description 403
LPAMAP IPCS subcommand
NOCONFIRM parameter
description 207
of SETDEF IPCS subcommand 265
dump output 208
NOCPU parameter
LPDEpgmname symbol
in IPCS data description parameter 26
for IPCS 448
NOHEADING parameter of BLS9CALL command 40
NOLIST parameter
on the NAME subcommand 212
M on the NAMETOKEN subcommand 214
MACHINE parameter NOMACHINE parameter
of SETDEF IPCS subcommand DISPLAY parameter 267 of SETDEF IPCS subcommand DISPLAY parameter 267
MAIN parameter non-blank character
of SETDEF IPCS subcommand 265 symbol used in picture strings 12
master trace non-numeric character
formatting table from a dump 348 symbol used in picture strings 12
MCS console NOPDS parameter
formatting dump data using COMCHECK IPCS of SETDEF IPCS subcommand 269
subcommand 83 NOPRINT parameter
MEMBER parameter of BLS9CALL command 40 of SETDEF IPCS subcommand 269
MERGE IPCS subcommand NOREMARK parameter
description 209 description 35
MERGEEND IPCS subcommand in IPCS data description parameter 36
description 209 of SETDEF IPCS subcommand DISPLAY parameter 267
message NOREQUEST parameter
eliminating from IPCS reports 268 of SETDEF IPCS subcommand DISPLAY parameter 267
filtering by severity 268 NOSTORAGE parameter
generating using NOTE IPCS subcommand 216 of SETDEF IPCS subcommand DISPLAY parameter 267
issued during an IPCS session 4 NOSUMMARY parameter
message queue on the COPYDDIR subcommand 93
formatting dump data using COMCHECK IPCS on the DROPDUMP subcommand 126
subcommand 83 on the DROPMAP subcommand 128
MLPA (modified link pack area) on the DROPSYM subcommand 130
list entry points in a dump 207 on the LISTDUMP subcommand 189
MLPA symbol on the LISTMAP subcommand 198
for IPCS 448 NOSYMBOL parameter
MMS (MVS message service) of SETDEF IPCS subcommand DISPLAY parameter 268
obtaining dump output 348 NOTE IPCS subcommand
MMSDATA IPCS verb name description 216
description 348 NOTERMINAL parameter
of SETDEF IPCS subcommand 270

Index 487
NOTEST parameter PCCAVT symbol
of SETDEF IPCS subcommand 270 for IPCS 448
NOTITLE parameter of BLS9CALL command 40 PCIE
NOVERIFY parameter formatting GTF trace records 169
of SETDEF IPCS subcommand 270 PDS parameter
nucleus of SETDEF IPCS subcommand 269
obtaining formatted output 349 PF key
print storage from a dump 437 used in IPCS dialog 383
NUCLEUS symbol PFT symbol
for IPCS 448 for IPCS 448
NUCMAP IPCS verb name pgmname symbol
description 349 for IPCS 448
number PGTnnnnnaaaaa symbol
converting decimal to hexadecimal 172 for IPCS 448
converting hexadecimal to decimal 172 picture string
numeric character classes of characters 12
symbol used in picture strings 12 notation 12
numeric comparison PLPA (pageable link pack area)
by COMPARE IPCS subcommand 87 list entry points in a dump 207
NVT symbol PLPA symbol
for IPCS 448 for IPCS 448
PMRNUMBER symbol
for IPCS 448
O pointer
displaying using LOCATE IPCS primary command 400
OMVSDATA IPCS subcommand
duplicating using R IPCS line command 420
description 218
edit using E IPCS line command 417
online help
formatting under the IPCS BROWSE option 418
for IPCS subcommands 171
inserting using I IPCS line command 419
OPCODE IPCS primary command
selecting using S IPCS line command 421
description 402
selecting using SELECT IPCS primary command 409
OPCODE IPCS subcommand
sorting using SORT IPCS primary command 410
description 220
stack symbol, Znnnnn 451
OPEN IPCS subcommand
pointer panel
description 222
IPCS and ISPF primary commands, IPCS line commands,
OPEN/CLOSE/EOV
and PF keys 384
formatting GTF trace records 169
POINTER parameter
operator communications activity 83
in IPCS data description parameter 32
OSRELEASE symbol
pointer stack
for IPCS 448
renumbering entries 232
output
renumbering symbols in IPCS BROWSE 403
suppressing IPCS screen output lines
positional parameter
using X line command 424
data description 17
output routing
description for IPCS 5
SETDEF IPCS subcommand parameters 269
POSITIONS parameter
output streams 404
in IPCS data description parameter 18, 23
positive integer
binary notation 10
P decimal notation 10
PACKED parameter hexadecimal notation 10
in IPCS data description parameter 32 notation types 10
PAGE parameter of BLS9CALL command 40 signed notation 10
page size PRDMP service aid
adjusting 228 equivalent functions in IPCS 463
parameter primary command
in IPCS data description 17 invoking for IPCS through PF keys 383
types in IPCS 5 IPCS 381
parameter string IPCS dialog 381
format when passed to verb exit routine 326 task directory 383
parm parameter of BLS9CALL command 39 process IPCS output streams 404
PARM parameter of IPCS command 41 removal using RESET primary command 407
PART symbol PRIMARYSYMPTOMS symbol
for IPCS 448 for IPCS 448
PATCH subcommand 225, 228 print data set
PCCAnn symbol opening for IPCS processing 222
for IPCS 448 routing subcommand listing 269

488 z/OS MVS IPCS Commands

print dump REAL parameter
conversion to IPCS 463 in IPCS data description parameter 26
PRINT parameter 2 REASONCODE symbol
of SETDEF IPCS subcommand 269 for IPCS 449
printed report REG32CTL symbol
setting line and page size 228 for IPCS 449
printing REG32CTLnn symbol
storage areas from a dump 437 for IPCS 449
private storage area REG32GEN symbol
printing 437 for IPCS 449
PRIVATE symbol REG32GENnn symbol
for IPCS 448 for IPCS 449
PRIVATEX symbol REG64CTL symbol
for IPCS 448 for IPCS 449
problem determination REG64CTLnn symbol
displaying system status from dump 273 for IPCS 449
PROFILE IPCS subcommand REG64GEN symbol
description 228 for IPCS 449
example 232 REG64GENnn symbol
program interrupt for IPCS 449
formatting GTF trace records 169 REGACC symbol
program parameter of BLS9CALL command 39 for IPCS 449
PSAnn symbol REGACCnn symbol
for IPCS 448 for IPCS 449
PSAVALID symbol REGCTL symbol
for IPCS 448 for IPCS 449
PSW symbol REGCTLnn symbol
for IPCS 448 for IPCS 449
PSWnn symbol REGFLT symbol
for IPCS 448 for IPCS 449
PVT symbol REGFLTnn symbol
for IPCS 449 for IPCS 449
REGFPC symbol
for IPCS 449
Q REGFPCnn symbol
for IPCS 449
Q IPCS verb name
REGGEN symbol
description 331
for IPCS 449
QCBTRACE IPCS verb name
REGGENnn symbol
description 331
for IPCS 449
quoted string
relative address
notation 13
in IPCS data description parameter 21
release IPCS resource 81
REMARK parameter
R description 35
R IPCS line command in IPCS data description parameter 35
description 420 of SETDEF IPCS subcommand DISPLAY parameter 267
range REMOTEDUMP symbol
of addresses in IPCS data description parameter 19 for IPCS 450
RANGE parameter RENUM IPCS primary command
in IPCS data description parameter 19 description 403
RB (request block) RENUM IPCS subcommand
displaying using SUMMARY IPCS subcommand 293 description 232
RBA parameter REPORT
in IPCS data description parameter 26 subcommand 405
RCE symbol REPORT IPCS primary command
for IPCS 449 description 404
RDCM control block REQUEST parameter
formatting dump data using COMCHECK IPCS of SETDEF IPCS subcommand DISPLAY parameter 267
subcommand 83 RESET IPCS primary command
read-only nucleus description 407
print storage from a dump 437 resource contention data
read-write nucleus analyzing dumps 54
print storage from a dump 437 return code
real frame for most IPCS subcommands 46
analyzing dumps 54 from the EVALUATE subcommand
CHECK option 153

Index 489
return code (continued) screen output
from the EVALUATE subcommand (continued) displaying excluded lines
default option 153 using S, F, or L IPCS line command 422
RETURN IPCS primary command for IPCS
description 408 using D IPCS line command 415
REXX exec suppressing lines
description 427 using X IPCS line command 424
format a value in a variable 172 scrolling dump data
identifying libraries 37 by changing scroll amount field 390
invoked from IPCS dialog 397 using DOWN IPCS primary command 390
invoking with TSO subcommand of IPCS 322 using LEFT IPCS primary command 399
retrieving dump directory information 137 using LOCATE IPCS primary command 400
retrieving information into variables 135 using MORE IPCS primary command 402
retrieving storage map information into variables 140 using RIGHT IPCS primary command 408
retrieving symbol table information into variables 145 using UP IPCS primary command 412
variables 137, 140, 172 SCVT symbol
RFIND IPCS primary command for IPCS 450
description 408 SDWAHDR symbol
RIGHT IPCS primary command for IPCS 450
description 408 search
RIM (resource initialization manager) for a module in a dump 158
analyzing with CBSTAT IPCS subcommand 81 for a SWA block 159
RONUCLEUS symbol for a value
for IPCS 450 using FIND IPCS primary command 393
RSM (real storage manager) repeat a search
displaying diagnostic information 233 using RFIND IPCS primary command 408
RSMDATA IPCS subcommand search through output stream 392
description 233 search value
report/parameter matrix 238 repeat 14
RTCT symbol SECONDARYSYMPTOMS symbol
for IPCS 450 for IPCS 450
RTM (recovery termination manager) SELECT IPCS primary command
formatting related dump data description 409
IEAVTFMT exit routine 313 SELECT IPCS subcommand
running 313 description 259
RUNARRAY IPCS subcommand selection code
description 248 for IPCS storage panel 386
RUNCHAIN IPCS subcommand selection panel
description 249 IPCS and ISPF primary commands and PF keys 383
example used in a CLIST 253 sending comments to IBM xiii
RUNCPOOL IPCS subcommand SERIOUS parameter
description 254 of SETDEF IPCS subcommand FLAG parameter 269
SERVERDATA report 63
session default value
S displaying IPCS default values using SETDEF IPCS
subcommand 262
S IPCS line command (select)
retrieving information into variables 135
description 421
setting IPCS default values using SETDEF IPCS
S IPCS line command (show)
subcommand 262
description 422
SETDEF IPCS subcommand
SADMP message log
description 262
obtaining formatted output 353
SEVERE parameter
SADMPMSG IPCS verb name
of SETDEF IPCS subcommand FLAG parameter 269
description 353
SGTnnnnn symbol
SAM/PAM/DAM
for IPCS 450
formatting GTF trace records 169
SHORT IPCS subcommand
save area
description 240
CLIST to follow the forward chain 436
shortcut keys 469
SCALAR parameter
SHRDATA IPCS subcommand
in IPCS data description parameter 35
description 237
SCAN IPCS subcommand
signed integer
description 257
binary notation 10
SCCB symbol
hexadecimal notation 10
for IPCS 450
notation types 10
Scheduler Work Area
SIGNED parameter
locate 159
in IPCS data description parameter 32

490 z/OS MVS IPCS Commands

SLIP trace records storage map (continued)
formatting GTF trace records 169 deleting records using DROPMAP IPCS subcommand 127
SLIPTRAP symbol displaying entries 197
for IPCS 450 list of entries created for control blocks or data areas by
SMCS console IPCS 455
formatting dump data using COMCHECK IPCS retrieving information into variables 140
subcommand 83 storage panel
SMF (system management facilities) IPCS and ISPF primary commands, IPCS line commands,
displaying diagnostic information 271 and PF keys 384
SMFDATA IPCS subcommand IPCS selection codes 386
description 271 STORAGE parameter
SMS (Storage Management Subsystem) of SETDEF IPCS subcommand 265
formatting dump data 325 of SETDEF IPCS subcommand DISPLAY parameter 267
SMSDATA IPCS verb name 325 STRDATA IPCS subcommand
SMSXDATA verb name 325 description 283
SORT IPCS primary command string comparison
description 410 by COMPARE IPCS subcommand 87
source STRUCTURE parameter
types for IPCS processing 1 in IPCS data description parameter 33
SQA (global system queue area) information from WHERE IPCS subcommand or primary
print 439 command 363
SRM (system resources manager) subcommand
formatting GTF trace records 169 IPCS online help 171
obtaining control blocks from dump 353 literal values 9
SRMDATA IPCS verb name of IPCS 45
description 353 subcommand listing
SSIDATA IPCS subcommand routing to print data set 269
description 272 subcommand of REPORT
stack entry BROWSE 405
controlling duplication 228 EVALRPT 405
creating 272 IPCSPRNT 406
STACK IPCS primary command VIEW 407
description 411 subspace
STACK IPCS subcommand identifying in dump through an STOKEN 212
description 272 subsystem console
stand-alone dump formatting dump data using COMCHECK IPCS
CLIST for initial analysis subcommand 83
description 439 subsystem information
printed 429 displaying through IPCS 272
CLIST to print storage 429 SUMDUMP IPCS verb name
DOCPU 118 description 354
obtain data for multiple processors 118 SUMDUMP parameter
source for IPCS processing 1 in IPCS data description parameter 27
stand-along dump SUMMARY IPCS subcommand
formatting message log from dump 353 description 293
STATUS IPCS subcommand summary of changes xv
description 273 z/OS MVS IPCS Commands xvi
STATUS parameter Summary of changes xvi
in IPCS data description parameter 27 suppress
STATUS parameter of BLS9CALL command 40 IPCS screen output
STOKEN (space token) using X line command 424
decipher using NAME subcommand 212 suspend lock contention
storage analyzing dumps 54
describe in a dump 17 SVC dump
displaying from dump 186 CLIST for initial analysis 431
obtaining contents summary report 189 printed form 430
printing from a dump 437 CLIST to print storage 431
storage area source for IPCS processing 1
IPCS symbol 453 SVC summary dump
storage display obtaining formatted output 354
using LOCATE IPCS primary command 400 symbol
storage key creating IPCS-defined
displaying current default values 262 using STACK IPCS primary command 411
setting IPCS default values using SETDEF IPCS using STACK IPCS subcommand 272
subcommand 262 creating user-defined
storage map using EQUATE IPCS primary command 391
creating entries for address spaces 259 using EQUATE IPCS subcommand 132

Index 491
symbol (continued) system logger address space
deleting from the symbol table 129 dump 207
displaying definitions for a dump 199 system status
displaying using SYMDEF IPCS subcommand 303 displaying in a dump 273
for dump storage areas 453 system trace
IPCS naming conventions 445 formatting entries 303
IPCS special symbols 453 SYSTERM parameter of BLS9CALL command 40
renumbering pointers in IPCS BROWSE 403 SYSTRACE IPCS subcommand
X (current address) in IPCS 21 description 303
SYMBOL parameter SYSUT1 parameter of BLS9CALL command 40
of SETDEF IPCS subcommand DISPLAY parameter 268 SYSUT2 parameter of BLS9CALL command 40
symbol table SYSUT3 parameter of BLS9CALL command 41
add entries for a cell chain 254 SYSUT4 parameter of BLS9CALL command 41
add entries for a control block chain 249
adding symbol 272
deleting entries 129
displaying for IPCS 303
T
task directory
IPCS naming conventions 445
IPCS line commands 383
renumbering stack symbol entries 232
IPCS primary commands 383
retrieving entry information into variables 145
IPCS subcommands 46
retrieving information through EVALSYM IPCS
TSO/E commands for IPCS 37
subcommand 145
TASKLIB parameter of IPCS command 38, 41
symbols established by BLSCEPTR CLIST 436
TCB (task control block)
symbolic address
analyzing with CBSTAT IPCS subcommand 80
in IPCS data description parameter 20
CLIST to run the save area chain 436
SYMDEF IPCS subcommand
displaying using SUMMARY IPCS subcommand 293
description 303
TCB exit routine
SYMPTOM IPCS verb name
IBM-supplied exit routine 312
description 355
installation-supplied exit routine 312
symptom string
TCBCURRENT symbol
obtaining formatted output 355
for IPCS 450
SYMPTOMS IPCS verb name
TCBEXIT IPCS subcommand
description 355
description 312
SYS1.DUMPnn data set
return codes 313
clear 463
testing installation-supplied exits 270
SYSDSCAN command of TSO/E
TCBnnnnnaaaaa symbol
description 43
for IPCS 450
return codes 43
TDCM control block
SYSIN parameter of BLS9CALL command 40
formatting dump data using COMCHECK IPCS
SYSLIB parameter of BLS9CALL command 40
subcommand 83
SYSLIN parameter of BLS9CALL command 40
TERMINAL parameter 2
SYSLMOD parameter of BLS9CALL command 40
of SETDEF IPCS subcommand 270
SYSMDUMP dump
TERMINATING parameter
CLIST for initial analysis 433
of SETDEF IPCS subcommand FLAG parameter 269
printed form 432
TEST parameter
CLIST to print storage 433
of SETDEF IPCS subcommand 270
source for IPCS processing 1
TEST parameter of BLS9 command 38
sysplex
TEST TSO/E command
obtaining status of systems from a dump 105
testing ASCBEXIT, TCBEXIT, or VERBEXIT
sysplex dump directory
subcommands 270
adding source description 52
text string
copying source description 92
notation 14
creating with BLSCDDIR CLIST 434
TIME command
deleting record 125
during IPCS attention processing 3, 4
displaying list of sources 189
time-of-day clock
initialize using IPCSDDIR command 42
formatting from a dump 273
retrieving information 137
title
SYSPRINT parameter of BLS9CALL command 40
displaying using LIST IPCS subcommand 186
SYSPUNCH parameter of BLS9CALL command 40
TITLE parameter of BLS9CALL command 40
system console
TITLE symbol
formatting dump data using COMCHECK IPCS
for IPCS 450
subcommand 83
TOC (table of contents) data set
system data
opening for IPCS processing 222
validating using the SCAN IPCS subcommand 257
TOC entry
system initialization data
generating 216
obtaining formatted output 328
trace
formatting GTF records 165

492 z/OS MVS IPCS Commands

trace (continued) user dump directory (continued)
formatting master trace table 348 displaying list of sources 189
merging formatted entries 209 freeing space 129
trace data set initialize using IPCSDDIR command 42
analyzing component trace entries 108 retrieving information 137
source for IPCS processing 1 user interface
trademarks 477 ISPF 469
trap TSO/E 469
activating for IPCS exit service routines 318
deactivating for IPCS exit service routines 316
listing status for IPCS exit service routines 314
trap processing
V
value
resume 161
finding literal values in a dump 153
TRAPLIST IPCS subcommand
general notations 10
description 314
repeat a search
TRAPOFF IPCS subcommand
using RFIND IPCS primary command 408
description 316
searching for using FIND IPCS primary command 393
TRAPON IPCS subcommand
Vector Facility
description 318
displaying registers 273
TSO subcommand of IPCS
formatting related dump data
description 322
IEAVSSA1 exit routine 313
return codes 323
verb exit routine
TSO/E (Time Sharing Option Extensions)
invoking using VERBEXIT IPCS subcommands 324
commands for IPCS 37
VERBEXIT ALCWAIT IPCS subcommand
enter commands from an IPCS session 322
description 328
formatting dump data 325
VERBEXIT ASMDATA IPCS subcommand
invoking commands from IPCS 37
description 328
IPCS command 41
VERBEXIT AVMDATA IPCS subcommand
IPCSDDIR command 42
description 328
SYSDSCAN command 43
VERBEXIT BLSAIPST IPCS subcommand
TSO/E ALTLIB command 37
description 328
TSO/E BLS9 command 38
VERBEXIT CBDATA IPCS subcommand
TSO/E BLS9CALL command 39
description 329
using from an IPCS session 322
VERBEXIT DAEDATA IPCS subcommand
TSO/E command
description 330
authorized command
VERBEXIT IPCS subcommand
running in an IPCS environment 323
description 324
for IPCS
return codes 327
task directory 37
testing installation-supplied exits 270
TSODATA IPCS verb name 325
VERBEXIT LEDATA IPCS subcommand
TTR parameter
description 342
in IPCS data description parameter 27
VERBEXIT LOGDATA IPCS subcommand
description 345
dump output 346
U VERBEXIT MMSDATA IPCS subcommand
UCB (unit control block) description 348
displaying using LISTUCB IPCS subcommand 203 VERBEXIT MTRACE IPCS subcommand
finding with FINDUCB IPCS subcommand 160 description 348
formatting captured UCB pages with IOSCHECK 175 dump output 348
formatting with CBFORMAT IPCS subcommand 75 VERBEXIT NUCMAP IPCS subcommand
UCBdddd symbol description 349
for IPCS 450 dump output 350
UCM symbol VERBEXIT SADMPMSG IPCS subcommand
for IPCS 450 description 353
uncataloged DSNAME entries dump output 353
issue IPCS DROPDUMP 435 VERBEXIT SRMDATA IPCS subcommand
UNSIGNED parameter description 353
in IPCS data description parameter 34 VERBEXIT SUMDUMP IPCS subcommand
UP IPCS primary command description 354
description 412 dump output 354
uppercase letter VERBEXIT SYMPTOM IPCS subcommand
symbol used in picture strings 12 description 355
user dump directory dump output 355
adding source description 52 VERBEXIT VSMDATA IPCS subcommand
copying source description 92 description 356
creating with BLSCDDIR CLIST 434 VERBOSE primary command
deleting record 125 description 413

Index 493
VERIFY parameter
of SETDEF IPCS subcommand 270
VIEW
subcommand of REPORT 407
VLF (virtual lookaside facility)
obtaining diagnosis data for 359
VLFDATA IPCS subcommand
description 359
VSAM (virtual storage access method)
formatting GTF trace records 169
VSAM data set 26
access by control interval 24
access data portion of cluster 28
access index portion of cluster 28
source for IPCS processing 1
VSM (virtual storage management)
obtaining formatted data 356
VSMDATA IPCS verb name
description 356
VTAM (Virtual Telecommunications Access Method)
format dump data 325
formatting GTF trace records 169
VTAMMAP IPCS verb name 325

W
wait state message area
displaying using STATUS IPCS subcommand 273
WARNING parameter
of SETDEF IPCS subcommand FLAG parameter 269
WHERE IPCS primary command
description 413
WHERE IPCS subcommand
description 361
WLM (workload manager)
obtaining diagnosis data 368
WLMDATA IPCS subcommand
description 368
word notation 14
worksheet
diagnostic 273

X
X IPCS line command
description 424
X symbol
for IPCS 451
XCF (cross-system coupling facility)
obtaining diagnosis data for 105
XESDATA IPCS subcommand
description 370
XLpgmname symbol
for IPCS 451

Z
z/OS MVS IPCS Commands
summary of changes xvi
z/OS UNIX System Services
obtaining diagnostic data 218
Znnnnn symbol
for IPCS 451
ZONED parameter
in IPCS data description parameter 34

494 z/OS MVS IPCS Commands

IBM®

Product Number: 5650-ZOS

Printed in USA

SA23-1382-30