System Automation for z/OS - IBM · 2020. 3. 6. · Overview of Commands .. . 3 Chapter 2. Understanding T erms ... . 5 Resour ce ... DISP APG Panel ..... . 42 10. Display of Automation

System Automation for z/OS

Operator's CommandsVersion 3 Release 5

SC34-2720-00

IBM

NoteBefore using this information and the product it supports, read the information in Appendix C, “Notices,” on page 595.

Edition Notes

This edition applies to IBM Tivoli System Automation for z/OS (5698-SA3), Version 3 Release 5, an IBM licensedprogram, and to all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC34-2649-00.

© Copyright IBM Corporation 1996, 2014.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

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

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

Accessibility . . . . . . . . . . . . xiUsing assistive technologies . . . . . . . . . xiKeyboard navigation of the user interface . . . . xi

Dotted decimal syntax diagrams . . . xiii

How to send your comments to IBM . . xv

About this publication . . . . . . . xviiWho Should Use This Publication . . . . . . xviiWhere to Find More Information. . . . . . . xvii

The System Automation for z/OS Library. . . xviiRelated Product Information . . . . . . . xvii

Summary of Changes for SC34-2720-00 . . . . xviiiNew Information . . . . . . . . . . . xviiiChanged Information . . . . . . . . . . xixDeleted Information . . . . . . . . . . xix

Part 1. Introduction . . . . . . . . . 1

Chapter 1. Overview of Commands . . . 3

Chapter 2. Understanding Terms . . . . 5Resource. . . . . . . . . . . . . . . . 5

Specifying Resources . . . . . . . . . . 6

Chapter 3. Format of Syntax Diagrams . 9

Part 2. SA z/OS System OperationsCommands . . . . . . . . . . . . 11

Chapter 4. System OperationsCommands . . . . . . . . . . . . . 13Using System Operations Commands. . . . . . 13

General Information . . . . . . . . . . 13Overview of Commands that OperateSysplexwide . . . . . . . . . . . . . 13Additional Parameters for System OperationsCommands . . . . . . . . . . . . . 14Varying the Format of the Command Output . . 17

ACF . . . . . . . . . . . . . . . . . 19AOCHELP . . . . . . . . . . . . . . 26AOCTRACE . . . . . . . . . . . . . . 27ASF . . . . . . . . . . . . . . . . . 32ASFUSER . . . . . . . . . . . . . . . 34DISPACF . . . . . . . . . . . . . . . 36DISPAOPS. . . . . . . . . . . . . . . 38DISPAPG . . . . . . . . . . . . . . . 40

DISPASF . . . . . . . . . . . . . . . 42DISPAUTO . . . . . . . . . . . . . . 44DISPERRS . . . . . . . . . . . . . . . 45DISPEVT . . . . . . . . . . . . . . . 47DISPEVTS . . . . . . . . . . . . . . . 48DISPFLGS . . . . . . . . . . . . . . . 51DISPGW . . . . . . . . . . . . . . . 54DISPINFO . . . . . . . . . . . . . . . 56DISPMSGS . . . . . . . . . . . . . . 58DISPMTR . . . . . . . . . . . . . . . 59DISPSCHD . . . . . . . . . . . . . . 63DISPSFLT . . . . . . . . . . . . . . . 65DISPSTAT . . . . . . . . . . . . . . . 67DISPSYS . . . . . . . . . . . . . . . 72DISPTREE . . . . . . . . . . . . . . . 73DISPTRG . . . . . . . . . . . . . . . 75DRAINJES. . . . . . . . . . . . . . . 77EXPLAIN . . . . . . . . . . . . . . . 78INGAMS . . . . . . . . . . . . . . . 79INGAUTO. . . . . . . . . . . . . . . 93INGCF . . . . . . . . . . . . . . . . 97INGCF DRAIN . . . . . . . . . . . . . 104INGCF ENABLE . . . . . . . . . . . . 108INGCF MAINT . . . . . . . . . . . . . 111INGCF PATH . . . . . . . . . . . . . 112INGCF STRUCTURE . . . . . . . . . . . 113INGCFG . . . . . . . . . . . . . . . 115INGCFL . . . . . . . . . . . . . . . 115INGCICS . . . . . . . . . . . . . . . 117INGDB2 . . . . . . . . . . . . . . . 121INGDLA . . . . . . . . . . . . . . . 124INGEVENT . . . . . . . . . . . . . . 126INGFILT . . . . . . . . . . . . . . . 127INGGROUP . . . . . . . . . . . . . . 134INGHIST . . . . . . . . . . . . . . . 142INGHWSRV . . . . . . . . . . . . . . 144INGIMS . . . . . . . . . . . . . . . 147INGINFO . . . . . . . . . . . . . . 152INGLIST . . . . . . . . . . . . . . . 155INGLKUP . . . . . . . . . . . . . . 165INGMDFY . . . . . . . . . . . . . . 170INGMOVE . . . . . . . . . . . . . . 173INGMSGS . . . . . . . . . . . . . . 178INGNTFY . . . . . . . . . . . . . . 181INGPAC . . . . . . . . . . . . . . . 184INGPW . . . . . . . . . . . . . . . 187INGPLEX . . . . . . . . . . . . . . 191INGPLEX CDS . . . . . . . . . . . . . 196INGPLEX SYStem . . . . . . . . . . . . 202INGPLEX CONsole . . . . . . . . . . . 204INGPLEX IPL . . . . . . . . . . . . . 207INGPLEX SDUMP. . . . . . . . . . . . 208INGPLEX SVCdump . . . . . . . . . . . 211INGPLEX SLIP . . . . . . . . . . . . . 214INGRELS. . . . . . . . . . . . . . . 215INGREQ . . . . . . . . . . . . . . . 218

© Copyright IBM Corp. 1996, 2014 iii

||||

INGRPT . . . . . . . . . . . . . . . 228INGRUN . . . . . . . . . . . . . . . 231INGSCHED . . . . . . . . . . . . . . 235INGSEND . . . . . . . . . . . . . . 242INGSESS . . . . . . . . . . . . . . . 246INGSET . . . . . . . . . . . . . . . 250INGSTR . . . . . . . . . . . . . . . 255INGTHRES . . . . . . . . . . . . . . 261INGTOPO . . . . . . . . . . . . . . 265INGTRIG. . . . . . . . . . . . . . . 266INGTWS . . . . . . . . . . . . . . . 268INGVOTE . . . . . . . . . . . . . . 277MONITOR . . . . . . . . . . . . . . 281OPCAQRY . . . . . . . . . . . . . . 282RESTART. . . . . . . . . . . . . . . 285RESYNC . . . . . . . . . . . . . . . 286SETHOLD . . . . . . . . . . . . . . 288SETSTATE . . . . . . . . . . . . . . 290SETTIMER . . . . . . . . . . . . . . 293

Part 3. SA z/OS I/O OperationsCommands. . . . . . . . . . . . 299

Chapter 5. I/O Operations Commands 301Using I/O Operations Commands . . . . . . 301Consensus Processing . . . . . . . . . . 301Safe Switching . . . . . . . . . . . . . 301FICON Switches . . . . . . . . . . . . 302FICON Cascaded Switches . . . . . . . . . 302ALLOW . . . . . . . . . . . . . . . 303BLOCK . . . . . . . . . . . . . . . 305CHAIN . . . . . . . . . . . . . . . 307CONNECT . . . . . . . . . . . . . . 309DISCONNECT . . . . . . . . . . . . . 311DISPLAY CHANGECHECK . . . . . . . . 312DISPLAY CHP . . . . . . . . . . . . . 312DISPLAY DEV . . . . . . . . . . . . . 314DISPLAY HOST . . . . . . . . . . . . 316DISPLAY NAME . . . . . . . . . . . . 319DISPLAY PORT . . . . . . . . . . . . 322DISPLAY RESULTS . . . . . . . . . . . 324DISPLAY SWITCH . . . . . . . . . . . 329DISPLAY TIMEOUT . . . . . . . . . . . 333DISPLAY VARY . . . . . . . . . . . . 333GETLOCK . . . . . . . . . . . . . . 336LOGREC . . . . . . . . . . . . . . . 337PROHIBIT . . . . . . . . . . . . . . 338REMOVE CHP . . . . . . . . . . . . . 340REMOVE SWITCH . . . . . . . . . . . 342RESET CHANGECHECK . . . . . . . . . 344RESET HOST . . . . . . . . . . . . . 345RESET SWITCH . . . . . . . . . . . . 348RESET TIMEOUT . . . . . . . . . . . . 349RESTORE CHP . . . . . . . . . . . . . 349RESTORE SWITCH . . . . . . . . . . . 351SYNC SWITCH. . . . . . . . . . . . . 352UNBLOCK . . . . . . . . . . . . . . 353UNCHAIN . . . . . . . . . . . . . . 355UNLOCK . . . . . . . . . . . . . . 356WRITE . . . . . . . . . . . . . . . 357

Part 4. SA z/OS ProcessorOperations Commands . . . . . . 359

Chapter 6. Using ProcessorOperations Commands . . . . . . . 361General Information . . . . . . . . . . . 361Host-based Commands . . . . . . . . . . 361Common Commands . . . . . . . . . . . 362Ensemble Commands . . . . . . . . . . 362PSM Commands . . . . . . . . . . . . 362

Chapter 7. Host-based Commands 363ISQCCMD . . . . . . . . . . . . . . 363ISQCHK . . . . . . . . . . . . . . . 366ISQCMON . . . . . . . . . . . . . . 367ISQECMD . . . . . . . . . . . . . . 368ISQEXEC . . . . . . . . . . . . . . . 371ISQHELP. . . . . . . . . . . . . . . 372ISQIPSWT . . . . . . . . . . . . . . 373ISQOVRD . . . . . . . . . . . . . . 375ISQROUTE . . . . . . . . . . . . . . 376ISQSEND. . . . . . . . . . . . . . . 378ISQSNDH . . . . . . . . . . . . . . 380ISQSTART . . . . . . . . . . . . . . 382ISQSTOP . . . . . . . . . . . . . . . 384ISQVARS . . . . . . . . . . . . . . . 385ISQXCLS . . . . . . . . . . . . . . . 400ISQXCON . . . . . . . . . . . . . . 402ISQXDRL. . . . . . . . . . . . . . . 405ISQXDST . . . . . . . . . . . . . . . 406ISQXIII . . . . . . . . . . . . . . . 427ISQXLOC . . . . . . . . . . . . . . 429ISQXMON . . . . . . . . . . . . . . 430ISQXOPT. . . . . . . . . . . . . . . 433ISQXPSM. . . . . . . . . . . . . . . 435ISQXUNL . . . . . . . . . . . . . . 437

Chapter 8. Common Commands . . . 439ACTIVATE . . . . . . . . . . . . . . 439CBU . . . . . . . . . . . . . . . . 442CCNTL . . . . . . . . . . . . . . . 445CLRHWMSG . . . . . . . . . . . . . 448CONDATA . . . . . . . . . . . . . . 449CPCDATA . . . . . . . . . . . . . . 451CTRLCONS . . . . . . . . . . . . . . 452DEACTIVATE . . . . . . . . . . . . . 454EXTINT . . . . . . . . . . . . . . . 456GETCLUSTER . . . . . . . . . . . . . 457GETIINFO . . . . . . . . . . . . . . 459GETILDI . . . . . . . . . . . . . . . 460GETIPSW . . . . . . . . . . . . . . 461GETISTAT . . . . . . . . . . . . . . 462GETITKN . . . . . . . . . . . . . . 463GETSDGR . . . . . . . . . . . . . . 465GETSINFO . . . . . . . . . . . . . . 466GETSSTAT . . . . . . . . . . . . . . 468ICNTL . . . . . . . . . . . . . . . 469LOAD . . . . . . . . . . . . . . . . 480OOCOD . . . . . . . . . . . . . . . 483

iv System Automation for z/OS:

||

POWERMOD . . . . . . . . . . . . . 485PROFILE . . . . . . . . . . . . . . . 487RESERVE. . . . . . . . . . . . . . . 505RESTART. . . . . . . . . . . . . . . 507SECLOG . . . . . . . . . . . . . . . 508START . . . . . . . . . . . . . . . 509STOP . . . . . . . . . . . . . . . . 510STP. . . . . . . . . . . . . . . . . 511STPDATA . . . . . . . . . . . . . . 514SYSRESET . . . . . . . . . . . . . . 516TCDATA . . . . . . . . . . . . . . . 518TCM . . . . . . . . . . . . . . . . 520

Chapter 9. Ensemble Commands . . . 523ACTIVATE . . . . . . . . . . . . . . 523BCDATA . . . . . . . . . . . . . . . 525BLDATA . . . . . . . . . . . . . . . 526CONDATA . . . . . . . . . . . . . . 528DEACTIVATE . . . . . . . . . . . . . 529DISCOVERY . . . . . . . . . . . . . 532DROP . . . . . . . . . . . . . . . . 533ENSDATA . . . . . . . . . . . . . . 535GETBCSTAT. . . . . . . . . . . . . . 536GETBLSTAT . . . . . . . . . . . . . . 537GETESTAT . . . . . . . . . . . . . . 538GETVHSTAT . . . . . . . . . . . . . 539GETVSSTAT . . . . . . . . . . . . . . 541HMCSWITCH . . . . . . . . . . . . . 542LIST . . . . . . . . . . . . . . . . 544SUBSCRIBE . . . . . . . . . . . . . . 547UNSUBSCRIBE. . . . . . . . . . . . . 549VHDATA. . . . . . . . . . . . . . . 552VSDATA . . . . . . . . . . . . . . . 553WLDATA. . . . . . . . . . . . . . . 555ZBXDATA . . . . . . . . . . . . . . 556

Chapter 10. PSM Commands - SpecialRequests . . . . . . . . . . . . . 559ISQACT . . . . . . . . . . . . . . . 559ISQCLEAR . . . . . . . . . . . . . . 559ISQMSG . . . . . . . . . . . . . . . 559ISQPSM . . . . . . . . . . . . . . . 560ISQQUERY . . . . . . . . . . . . . . 560ISQSTATUS . . . . . . . . . . . . . . 560ISQTRACE . . . . . . . . . . . . . . 561STOPALL. . . . . . . . . . . . . . . 561

Part 5. Appendixes . . . . . . . . 563

Appendix A. Definitions for I/OOperations Commands . . . . . . . 565ESCON/FICON Director . . . . . . . . . 565Switch Identifiers . . . . . . . . . . . . 565Switch Unique Identifier. . . . . . . . . . 566

Logical Switch Number (LSN) . . . . . . . . 566Port Addresses . . . . . . . . . . . . . 566Switch Ports . . . . . . . . . . . . . . 566Allow or Prohibit Mask of a Port . . . . . . . 567Switch Port Hardware Status on a DisplayCommand . . . . . . . . . . . . . . 567Logical Tokens . . . . . . . . . . . . . 568Physical Tokens . . . . . . . . . . . . 568Channel Types . . . . . . . . . . . . . 568

A Parallel Channel . . . . . . . . . . 569An ESCON (CNC) Channel . . . . . . . 570An ESCON Channel Operating in Converted(CVC) Mode. . . . . . . . . . . . . 570A FICON (FC) Channel . . . . . . . . . 570Coupling Facility Channels . . . . . . . . 570OSA Channels . . . . . . . . . . . . 570

Making Connectivity Changes . . . . . . . . 570NOForce|NOCheck|Force Option Set . . . . 571Backout|Nobackout Option Set . . . . . . 572

When a Command Fails . . . . . . . . . . 572Switching Commands . . . . . . . . . . 573Types Of Channels . . . . . . . . . . . 576Remove (Quiesce) a Switch . . . . . . . . . 576Restore (Enable) a Switch . . . . . . . . . 577Using Port Names as a Tool in SwitchingCommands . . . . . . . . . . . . . . 577Chain and Unchain a Switchable Path (ESCONonly) . . . . . . . . . . . . . . . . 577Chaining a Path (ESCON only) . . . . . . . 578

Two Scenarios for a CH Chain in a CNC Path 579A "Partially-ESCON" Path . . . . . . . . . 581An ESCON-in-Converted-Mode (CVC) Path . . . 581A Parallel Channel in Block (BL) Mode . . . . . 581Processing a Vary Path Request . . . . . . . 582

General Rules . . . . . . . . . . . . 582VTAM Application Name . . . . . . . . . 583TCP/IP Host Name . . . . . . . . . . . 583

Appendix B. General Considerationsfor I/O Operations Commands . . . . 585General Information and Tips for UsingMultisystem Commands. . . . . . . . . . 585General Considerations for Using the QueryEntity|Interface|Relations Commands . . . . . 586Device and Path Status After ConnectivityCommands . . . . . . . . . . . . . . 588

Appendix C. Notices . . . . . . . . 595Trademarks . . . . . . . . . . . . . . 597Terms and conditions for product documentation 597

Glossary . . . . . . . . . . . . . 599

Index . . . . . . . . . . . . . . . 629

Contents v

||

vi System Automation for z/OS:

Figures

1. Resource Selection Panel . . . . . . . . 62. Resource Selection Panel: Non-Sysplexwide 153. Resource Selection Panel 2: Sysplexwide 164. AOCHELP Command Dialog Panel . . . . 275. AOCTRACE Main Command Dialog Panel 306. AOCTRACE Command Dialog Panel for a

Specific REXX Script . . . . . . . . . 317. Display of Automation Control File Settings

for Subsystem (DISPACF SUBSYSTEM) . . . 388. Automation Operators Panel . . . . . . . 409. DISPAPG Panel . . . . . . . . . . . 42

10. Display of Automation Status File Informationfor TSO (DISPASF TSO) . . . . . . . . 44

11. DISPAUTO Command Dialog Panel . . . . 4512. DISPERRS Command Dialog Panel . . . . 4613. DISPEVT Command Dialog Panel . . . . . 4814. DISPEVTS Command Dialog Panel . . . . 5015. DISPEVTS Command Dialog Panel: Setting an

Event . . . . . . . . . . . . . . 5116. DISPFLGS Command Dialog Panel . . . . 5317. DISPGW Command Dialog Panel 1 . . . . 5518. DISPINFO Command Dialog Panel . . . . 5719. Authorized Message Receivers (DISPMSGS)

Panel. . . . . . . . . . . . . . . 5920. DISPMTR Initial Command Dialog Panel 6121. DISPMTR Command Dialog Panel Showing

Details for a Monitor . . . . . . . . . 6322. DISPSCHD Command Dialog Panel . . . . 6423. DISPSFLT Command Dialog Panel . . . . . 6724. Display of Status of All Automated Resources

(DISPSTAT) . . . . . . . . . . . . 7025. DISPSYS Command Dialog Panel . . . . . 7326. DISPTREE Command Dialog Panel . . . . 7527. DISPTRG Command Dialog Panel . . . . . 7628. EXPLAIN Command Dialog Panel . . . . . 7929. INGAMS Command Dialog Panel . . . . . 8430. INGAMS Command Dialog Panel to Control

Secondary Automation Manager Functions . . 8631. INGAMS Command Dialog Panel to Show

Details . . . . . . . . . . . . . . 8832. INGAMS Command Dialog Panel to Refresh

the Configuration . . . . . . . . . . 9033. INGAMS Command Dialog Panel to Manage

Diagnostic Functions . . . . . . . . . 9134. INGAMS Work Item Statistics Display . . . 9235. INGAMS Work Item History Display . . . . 9336. INGAUTO Command Dialog Panel . . . . 9737. INGCF Selection Panel . . . . . . . . 10438. ENABLE Command Dialog Panel: After

Populating . . . . . . . . . . . . 11039. ENABLE Command Dialog Panel: After

Issuing Command "INGCF E cf_name" . . . 11140. MAINT Command Output . . . . . . . 11241. PATH Command Dialog Panel . . . . . . 11242. STRUCTURE Command Dialog Panel 11343. INGCICS REQ=CMD Command Dialog Panel 119

44. INGCICS REQ=BROADCAST CommandDialog Panel . . . . . . . . . . . . 120

45. INGCICS REQ=INFO Command Dialog Panel 12146. SA z/OS Discovery Library Adapter Report 12647. INGFILT Command Dialog Panel . . . . . 13248. INGGROUP Command Dialog Panel 14049. INGGROUP Command Dialog Selection

Panel . . . . . . . . . . . . . . 14150. INGGROUP Command Dialog Panel Showing

Members' Detail . . . . . . . . . . 14151. INGHIST Command Dialog Panel . . . . 14452. INGIMS Command Dialog Panel . . . . . 15053. INGIMS REQ=BROADCAST Command

Dialog Panel . . . . . . . . . . . . 15154. IMS Dependent Regions Panel . . . . . . 15255. INGINFO Command Dialog Panel . . . . 15456. INGLIST Command Dialog Panel . . . . . 16057. INGLIST Command Dialog Panel To Update

Status . . . . . . . . . . . . . . 16458. INGLKUP Command Dialog Panel . . . . 16959. INGLKUP Command Dialog Panel for the

ANALYSE Option . . . . . . . . . . 17060. INGMDFY Command Dialog Panel . . . . 17261. INGMOVE Command Dialog Panel . . . . 17662. INGMOVE Confirmation Panel . . . . . 17863. INGMSGS Command Dialog Panel . . . . 18064. INGNTFY Command Dialog Panel . . . . 18365. INGPAC Pacing Gate(s) Display Panel 18666. INGPAC Pacing Gate Detail Display Panel 18767. INGPLEX Selection Panel . . . . . . . 19468. INGPLEX CDS Command Dialog Panel 19769. Confirmation Panel for Switching from the

Current Primary CDS to the Alternate CDS . 19970. INGPLEX CDS Command Dialog Panel after

the Switch . . . . . . . . . . . . 19971. CFRM Couple Data Set Information Panel

before Policy Switch . . . . . . . . . 20072. Confirmation Panel for Policy Switch 20173. Channel Path Information for CFRM Couple

Data Sets . . . . . . . . . . . . . 20174. INGPLEX SYSTEM Command Dialog Panel 1 20375. INGPLEX SYSTEM Command Dialog Panel 2 20476. INGPLEX CONS Command Dialog Panel 20577. INGPLEX IPL Main Panel . . . . . . . 20878. INGPLEX Dump Options Panel . . . . . 20979. INGPLEX SDUMP Panel . . . . . . . . 20980. INGPLEX SDUMP Modification Panel 21081. INGPLEX SVCDUMP Target System Selection

Panel . . . . . . . . . . . . . . 21182. INGPLEX SVCDUMP Address Space

Selection Panel . . . . . . . . . . . 21283. INGPLEX SVCDUMP Address Space Detail

Panel . . . . . . . . . . . . . . 21284. INGPLEX SVCDUMP Dump Option Panel 21385. INGPLEX SVC Line Mode Sample . . . . 21486. INGPLEX SLIP Main Panel . . . . . . . 215

© Copyright IBM Corp. 1996, 2014 vii

||

||||

|||

||||

||

||||

87. INGRELS Command Dialog Panel . . . . 21788. INGRELS Command Dialog Panel with All

Details Collapsed . . . . . . . . . . 21889. INGREQ Command Dialog Panel 1 . . . . 22790. INGREQ Command Dialog Panel 2 . . . . 22891. INGRPT Command Dialog Panel . . . . . 23092. INGRUN Command Dialog Panel . . . . 23493. INGSCHED Initial Command Dialog Panel 23894. INGSCHED Command Dialog Panel Showing

Schedule Details . . . . . . . . . . 23995. INGSCHED Command Dialog Panel Showing

Schedule Overrides . . . . . . . . . 24096. INGSCHED Command Dialog Panel Showing

Resources Related to a Schedule . . . . . 24197. INGSCHED Command Dialog Panel Showing

Resource Overrides . . . . . . . . . 24298. INGSEND Command Dialog Panel . . . . 24699. INGSESS Command Dialog Panel. . . . . 247

100. INGSESS Command Dialog Detail Panel 249101. The INGSTR Panel without Structure

Conditions. . . . . . . . . . . . . 259102. The INGSTR Panel with Structure Conditions 260103. REALLOCATE Confirmation Panel . . . . 261104. INGSTR Line Command Output . . . . . 261105. Display of Threshold Settings for JES

(INGTHRES JES) . . . . . . . . . . 264106. INGTHRES Command Dialog Panel to Add

Thresholds . . . . . . . . . . . . 265107. INGTRIG Initial Command Dialog Panel 267108. INGTRIG Command Dialog Panel Showing

Resources Associated with a Trigger . . . . 268109. INGTWS Command Dialog Panel . . . . . 273110. INGTWS REQ=LIST TYPE=APPL Command

Dialog Panel . . . . . . . . . . . . 274111. INGTWS REQ=LIST TYPE=OP Command

Dialog Panel . . . . . . . . . . . . 275112. INGTWS REQ=LIST TYPE=SR Command

Dialog Panel . . . . . . . . . . . . 275113. INGTWS REQ=LIST TYPE=WS Command

Dialog Panel . . . . . . . . . . . . 276114. INGTWS REQ=LIST TYPE=CAL Command

Dialog Panel . . . . . . . . . . . . 276115. INGTWS Filter Command Dialog Panel 277116. INGVOTE Command Dialog Panel . . . . 280117. INGVOTE Command Output . . . . . . 281118. OPCAQRY Command Dialog Panel . . . . 283119. OPCAQRY Command Dialog Panel Showing

Details for a Command . . . . . . . . 284120. OPCAQRY Command Dialog Panel Showing

Details for a Command in Error . . . . . 285121. SETSTATE Command Dialog Panel . . . . 293122. SETTIMER Command Dialog Panel: Display

of Scheduled Timers . . . . . . . . . 294123. SETTIMER Command Dialog Panel: Adding

or Changing Timers . . . . . . . . . 296124. ALLOW Command: Sample 1 . . . . . . 305

125. ALLOW Command: Sample 2 . . . . . . 305126. BLOCK Command: Sample 1 . . . . . . 306127. BLOCK Command: Sample 2 . . . . . . 307128. CHAIN Command: Sample 1 . . . . . . 309129. CHAIN Command: Sample 2 . . . . . . 309130. CONNECT Command Sample . . . . . . 311131. DISPLAY CHP Command: Sample 1 . . . . 314132. DISPLAY CHP Command: Sample 2 . . . . 314133. DISPLAY DEV Command Sample. . . . . 316134. DISPLAY HOST Command: Sample 1 319135. DISPLAY NAME Command: Sample 1 321136. DISPLAY NAME Command: Sample 2 321137. DISPLAY NAME Command: Sample 3 322138. DISPLAY PORT Command: Sample 1 324139. DISPLAY PORT Command: Sample 2 324140. DISPLAY RESULTS Command: Scenario 1 328141. DISPLAY RESULTS Command: Scenario 2 329142. DISPLAY SWITCH Command: Sample 1 332143. PROHIBIT Command: Sample 1 . . . . . 339144. PROHIBIT Command: Sample 2 . . . . . 339145. REMOVE SWITCH Command Sample 344146. RESET HOST Command: Scenario 1 . . . . 347147. RESET HOST Command: Scenario 2 . . . . 347148. UNBLOCK Command: Sample 1 . . . . . 354149. UNBLOCK Command: Sample 2 . . . . . 355150. UNCHAIN Command Sample . . . . . . 356151. WRITE Command: Sample 1 . . . . . . 358152. WRITE Command: Sample 2 . . . . . . 358153. ISQXDST Status Summary Panel . . . . . 408154. Target System Summary Panel . . . . . . 411155. Target Hardware SummaryPanel for

OCF-Based Processors . . . . . . . . 416156. Ensemble Main View . . . . . . . . . 417157. ISQEZBX cursor sensitive areas . . . . . 421158. zBX Base Operation Blade View . . . . . 422159. Path Detail Panel . . . . . . . . . . 425160. Sample System Options Panel for an

OCF-Based Processor in a Basic-Mode MVSTarget System . . . . . . . . . . . 434

161. Sample System Options Panel for anOCF-Based Processor in LPAR-Mode MVSTarget System . . . . . . . . . . . 434

162. Sample of an ESCON Director Diagram 565163. Switch Port Hardware Status Format 568164. PROHIBIT Command Example . . . . . 574165. CONNECT Command Example . . . . . 574166. BLOCK Command Example . . . . . . 574167. UNBLOCK Command Example . . . . . 575168. DISCONNECT Command Example . . . . 575169. ALLOW Command Example . . . . . . 576170. Examples of Chained Paths . . . . . . . 578171. Chain: Scenario 1 . . . . . . . . . . 579172. Chain: Scenario 2 . . . . . . . . . . 580173. ESCON-in-Converted-Mode Sample . . . . 581174. Parallel Channel in Block Mode Sample 582

viii System Automation for z/OS:

||

||

||

Tables

1. System Automation for z/OS Library xvii2. Overview of Commands . . . . . . . . 33. ISQVARS Keywords Sorted by Keyword

Name . . . . . . . . . . . . . . 3924. Ensemble Connection Status . . . . . . 419

5. Device and Path Status Before and After theREMOVE SWITCH and RESTORE SWITCHCommands . . . . . . . . . . . . 589

6. Path and Device Status Summary . . . . . 592

© Copyright IBM Corp. 1996, 2014 ix

x System Automation for z/OS:

Accessibility

Accessibility features help users with physical disabilities, such as restrictedmobility or limited vision, to use software products successfully. SystemAutomation for z/OS supports several user interfaces. Product functionality andaccessibility features vary according to the interface.

The major accessibility features in this product enable users in the following ways:v Use assistive technologies such as screen reader software and digital speech

synthesizer, to hear what is displayed on screen. Consult the productdocumentation of the assistive technology for details on using those technologieswith this product and screen magnifier software

v Operate specific or equivalent features using only the keyboardv Magnify what is displayed on screen.

The product documentation includes the following features to aid accessibility:v All documentation is available to both HTML and convertible PDF formats to

give the maximum opportunity for users to apply screen-reader softwarev All images in the documentation are provided with alternative text so that users

with vision impairments can understand the contents of the images.

Using assistive technologiesAssistive technology products, such as screen readers, function with the userinterfaces found in z/OS®. Consult the assistive technology documentation forspecific information when using such products to access z/OS interfaces.

Keyboard navigation of the user interfaceUsers can access z/OS user interfaces using TSO/E or ISPF. Refer to z/OS TSO/EPrimer, z/OS TSO/E User's Guide, and z/OS ISPF User's Guide Vol 1 for informationabout accessing TSO/E and ISPF interfaces. These guides describe how to useTSO/E and ISPF, including the use of keyboard shortcuts or function keys (PFkeys). Each guide includes the default settings for the PF keys and explains how tomodify their functions.

© Copyright IBM Corp. 1996, 2014 xi

xii System Automation for z/OS:

Dotted decimal syntax diagrams

Syntax diagrams are provided in dotted decimal format for users accessing theInformation Center using a screen reader. In dotted decimal format, each syntaxelement is written on a separate line. If two or more syntax elements are alwayspresent together (or always absent together), they can appear on the same line,because they can be considered as a single compound syntax element.

Each line starts with a dotted decimal number; for example, 3 or 3.1 or 3.1.1. Tohear these numbers correctly, make sure that your screen reader is set to read outpunctuation. All the syntax elements that have the same dotted decimal number(for example, all the syntax elements that have the number 3.1) are mutuallyexclusive alternatives. If you hear the lines 3.1 USERID and 3.1 SYSTEMID, youknow that your syntax can include either USERID or SYSTEMID, but not both.

The dotted decimal numbering level denotes the level of nesting. For example, if asyntax element with dotted decimal number 3 is followed by a series of syntaxelements with dotted decimal number 3.1, all the syntax elements numbered 3.1are subordinate to the syntax element numbered 3.

Certain words and symbols are used next to the dotted decimal numbers to addinformation about the syntax elements. Occasionally, these words and symbolsmight occur at the beginning of the element itself. For ease of identification, if theword or symbol is a part of the syntax element, it is preceded by the backslash (\)character. The * symbol can be used next to a dotted decimal number to indicatethat the syntax element repeats. For example, syntax element *FILE with dotteddecimal number 3 is given the format 3 \* FILE. Format 3* FILE indicates thatsyntax element FILE repeats. Format 3* \* FILE indicates that syntax element *FILE repeats.

Characters such as commas, which are used to separate a string of syntaxelements, are shown in the syntax just before the items they separate. Thesecharacters can appear on the same line as each item, or on a separate line with thesame dotted decimal number as the relevant items. The line can also show anothersymbol giving 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 theLASTRUN and DELETE syntax elements, the elements must be separated by acomma. If no separator is given, assume that you use a blank to separate eachsyntax element.

If a syntax element is preceded by the % symbol, this indicates a reference that isdefined elsewhere. The string following the % symbol is the name of a syntaxfragment rather than a literal. For example, the line 2.1 %OP1 means that youshould refer to separate syntax fragment OP1.

The following words and symbols are used next to the dotted decimal numbers:v ? means an optional syntax element. A dotted decimal number followed by the ?

symbol indicates that all the syntax elements with a corresponding dotteddecimal number, and any subordinate syntax elements, are optional. If there isonly one syntax element with a dotted decimal number, the ? symbol isdisplayed on the same line as the syntax element, (for example 5? NOTIFY). Ifthere 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

© Copyright IBM Corp. 1996, 2014 xiii

optional. For example, if you hear the lines 5 ?, 5 NOTIFY, and 5 UPDATE, youknow that syntax elements NOTIFY and UPDATE are optional; that is, you canchoose one or none of them. The ? symbol is equivalent to a bypass line in arailroad diagram.

v ! means a default syntax element. A dotted decimal number followed by the !symbol and a syntax element indicates that the syntax element is the defaultoption for all syntax elements that share the same dotted decimal number. Onlyone of the syntax elements that share the same dotted decimal number canspecify a ! symbol. For example, if you hear the lines 2? FILE, 2.1! (KEEP), and2.1 (DELETE), you know that (KEEP) is the default option for the FILE keyword.In this example, if you include the FILE keyword but do not specify an option,default option KEEP will be applied. A default option also applies to the nexthigher dotted decimal number. In this example, if the FILE keyword is omitted,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 only applies to the nexthigher dotted decimal number, 2.1 (which does not have an associatedkeyword), and does not apply to 2? FILE. Nothing is used if the keyword FILEis omitted.

v * means a syntax element that can be repeated 0 or more times. A dotteddecimal number followed by the * symbol indicates that this syntax element canbe used zero or more times; that is, it is optional and can be repeated. Forexample, if you hear the line 5.1* data area, you know that you can include onedata area, more than one data area, or no data area. If you hear the lines 3*, 3HOST, and 3 STATE, you know that you can include HOST, STATE, bothtogether, or nothing.

Notes:

1. If a dotted decimal number has an asterisk (*) next to it and there is only oneitem with that dotted decimal number, you can repeat that same item morethan once.

2. If a dotted decimal number has an asterisk next to it and several items havethat 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 could write HOST STATE, but you could not write HOST HOST.

3. The * symbol is equivalent to a loop-back line in a railroad syntax diagram.v + means a syntax element that must be included one or more times. A dotted

decimal number followed by the + symbol indicates that this syntax elementmust be included one or more times; that is, it must be included at least onceand can be repeated. For example, if you hear the line 6.1+ data area, you mustinclude 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 only repeat a particular item if it is the only item with thatdotted decimal number. The + symbol, like the * symbol, is equivalent to aloop-back line in a railroad syntax diagram.

xiv System Automation for z/OS:

How to send your comments to IBM

We appreciate your input on this publication. Feel free to send us any commentsyou might have.

If you have feedback to the manuals

If you have comments on the manuals, like clarity, accuracy, and completeness ofthe information, use the Feedback channel on IBM Knowledge Center to send yourcomments.1. Click Feedback > Email IBM Knowledge Center support at the bottom of IBM

Knowledge Center.2. Log in to the invoked mailbox; or if the Launch Application window is

displayed, choose one mailbox and log in. A new email is displayed after login.3. In the email body, write down your feedback. Please include the specific book

and topic name that you're commenting on.4. Send the email to the default recipient.5. SA z/OS team will respond to you by email as soon as possible.

If you have a technical problem

Use one of the following feedback methods:v Contact your IBM service representativev Call IBM technical supportv Visit the IBM zSeries support web page at www.ibm.com/systems/z/support/

When you send comments to IBM, you grant IBM a nonexclusive right to use ordistribute your comments in any way it believes appropriate without incurring anyobligation to you.

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

© Copyright IBM Corp. 1996, 2014 xv

http://www.ibm.com/support/knowledgecenter/SSWRCJ_3.5.0/com.ibm.safos.doc_3.5/kc_welcome-444.htmlhttp://www.ibm.com/support/knowledgecenter/SSWRCJ_3.5.0/com.ibm.safos.doc_3.5/kc_welcome-444.htmlhttp://www.ibm.com/systems/z/support/

xvi System Automation for z/OS:

About this publication

This publication provides detailed information and reference material for operatingIBM® Tivoli® System Automation for z/OS (SA z/OS).

Throughout this publication references to MVS™ refer either to MVS/ESA, or to theMVS element of z/OS.

Who Should Use This PublicationThis information is intended primarily for operators and system programmers. Itmay also be useful for others, for example, help desk personnel and customerengineers.

Where to Find More Information

The System Automation for z/OS LibraryTable 1 shows the information units in the System Automation for z/OS library:

Table 1. System Automation for z/OS Library

Title Order Number

IBM Tivoli System Automation for z/OS Planning and Installation SC34-2716

IBM Tivoli System Automation for z/OS Customizing and Programming SC34-2715

IBM Tivoli System Automation for z/OS Defining Automation Policy SC34-2717

IBM Tivoli System Automation for z/OS User's Guide SC34-2718

IBM Tivoli System Automation for z/OS Messages and Codes SC34-2719

IBM Tivoli System Automation for z/OS Operator's Commands SC34-2720

IBM Tivoli System Automation for z/OS Programmer's Reference SC34-2748

IBM Tivoli System Automation for z/OS Product Automation Programmer'sReference and Operator's Guide

SC34-2714

IBM Tivoli System Automation for z/OS TWS Automation Programmer's andOperator's Reference Guide

SC34-2749

IBM Tivoli System Automation for z/OS End-to-End Automation Adapter SC34-2750

IBM Tivoli System Automation for z/OS Monitoring Agent Configuration andUser's Guide

SC34-2751

SA z/OS Home Page:

For the latest news on SA z/OS, visit the SA z/OS home page at:http://www-03.ibm.com/software/products/en/tivosystautoforzos

Related Product InformationFor information that supports Tivoli System Automation for z/OS, visit the z/OSlibrary in IBM Knowledge Center (https://www.ibm.com/support/knowledgecenter/SSLTBW).

© Copyright IBM Corp. 1996, 2014 xvii

|||

http://www-03.ibm.com/software/products/en/tivosystautoforzoshttps://www.ibm.com/support/knowledgecenter/SSLTBWhttps://www.ibm.com/support/knowledgecenter/SSLTBW

Summary of Changes for SC34-2720-00This document contains information previously presented in System Automationfor z/OS V3R4.0 Operator's Commands, SC34-2649-00.

You may notice changes in the style and structure of some content in thisdocument—for example, headings that use uppercase for the first letter of initialwords only, and procedures that have a different look and format. The changes areongoing improvements to the consistency and retrievability of information in ourdocuments.

This document contains terminology, maintenance, and editorial changes.

New InformationThe following information and commands have been introduced:

System OperationsINGPAC

The “INGPAC” on page 184 command is added for managing pacinggates.

INGPWThe “INGPW” on page 187 command is added for managing passwords.

DISPINFOThe UP Status Delay field is added to the DISPINFO command output. See“DISPINFO” on page 56.

INGAMSThe XSTATUS parameter is added to the INGAMS command to displayinformation denoted by the PLEXID specification for XCF groups. See“INGAMS” on page 79.

HMCSWITCHA new Ensemble command is added for switching between a Primary andan alternative Hardware Management Console (HMC). See“HMCSWITCH” on page 542.

INGFILT/INGLISTThe PGNAME parameter is added for INGFILT and INGLIST to displayinformation about Pacing Gates for resources. See INGFILT and “INGLIST”on page 155.

Processor OperationsISQSNDH

A new processor operations ISQSNDH command is added for sendinghigh priority commands. See “ISQSNDH” on page 380.

ISQVARS KeywordsTwo new keywords lparscop (LPAR scope) and pollopt (Path poll option) areadded to the list of keywords available with the processor operationscommand “ISQVARS” on page 385.

ISQVARS Keywords for SNMPv3Three new keywords snmpv3 (Use SNMPv3 protocol), v3pwd (SNMPv3Password), and v3User (SNMPv3 Username) are added for the SNMPv3settings, when using the processor operations command “ISQVARS” onpage 385.

xviii System Automation for z/OS:

Changed InformationInformation has been updated for the following commands:

System OperationsDISPAPG

The DISPAPG command panel is updated.

INGFILT/INGLISTThe Application Type and SubType parameters are replaced by theCategory and Subcategory parameters in INGFILT and “INGLIST” on page155 to cover IBM-defined and user-defined application categories.

INGMDFYThe scenarios for using these commands are redefined. See “INGMDFY”on page 170.

Processor OperationsISQXDST

The SA z/OS PATH details screen (ISQEPNVC) is updated. See “DisplayPath Details” on page 424 for new SNMPv3 security fields and parameters.

Additional value ZAWARE for ISQVARS variablesValue ZAWARE is added for variables ostype (Target operating systemtype) and tmode (Target system mode) in use with the “ISQVARS” on page385 command.

Deleted InformationThe following information has been deleted:

UOW and INIT settings for the Override parameter in INGREQ/INGRUNThe above settings are retired for the “INGREQ” on page 218/“INGRUN”on page 231 system operations commands.

About this publication xix

xx System Automation for z/OS:

Part 1. Introduction

This part gives an overview of System Automation for z/OS commands — how toenter them, their format, and the various types of commands.

© Copyright IBM Corp. 1996, 2014 1

2 System Automation for z/OS:

Chapter 1. Overview of Commands

Table 2 gives a brief overview of the System Automation for z/OS commands. Thisoverview describes the various types of commands, their functions and where theycan be entered. For detailed information about how to issue commands, see IBMTivoli System Automation for z/OS User's Guide.

Table 2. Overview of Commands

Type of command Function Where entered

System operationscommands

Control and maintainresources in the enterprisefrom a single point of control

NetView console, or NMC

I/O operations commands Control input/output devices TSO/ISPF, API, operatorconsole

Processor operationscommands

Common commands forautomation

API, NetView console, orNMCNote: Precede withISQCCMD command

Control hardware processors NetView console or NMC

Ensemble commands forSystem z® zEnterprise®

BladeCenter Extension (zBX)automation

API, NetView consoleNote: Precede withISQECMD command


Overview of Commands


Chapter 2. Understanding Terms

This section contains details of various terms that are used throughout this book.

ResourceIn SA z/OS the term resource denotes any entity that can be automated. Theautomation manager administrates resources.

A resource is identified by its name. The resource name must be unique within theautomation manager name space. The format of the resource name isname/type[/system]. The three components of the resource name can be thefollowing:

Name Specifies the name of the resource, for example the subsystem name for anapplication (APL) or the automation name for an application group (APG).

Type Specifies the type of the resource. The type parameter is optional. It canhave the following values:APL Indicates that the resource is a subsystem.APG Indicates that the resource is an application group.EVT Indicates that the resource is an event.MTR Indicates that the resource is a monitor.SVP Indicates that the resource is a service period (schedule).SYG Indicates the group of all resources of a system. SYG is created

automatically. This is the application group that contains allresources of a particular system.

SYS Indicates that the resource is a system.

SystemSpecifies the system/image name where the resource is defined. Thesystem parameter is not used for sysplex resources, for example, sysplexapplication groups, events or service periods.

If the resource that you specified is not unique within the domain of theautomation manager, a selection panel is displayed where you can select what youwant to work with, as shown in Figure 1 on page 6.


Specifying ResourcesThere are various ways of specifying automation manager resources in SystemAutomation for z/OS. The scope of the automation manager is a sysplex orSA z/OS subplex (that a group that shares the same XCF ID).

Using Components of Resource NamesComponents are the parts that make up the name of a resource using automationmanager notation.

Here are a few examples of how to specify resource names using components:

TSO All resources that have the name TSO.

TSO/APGAll resources that have the name TSO, and the type APG.

TSO/APLAll resources that have the name TSO, of the type APL, on all systems inthe sysplex.

Using WildcardsYou can also use an asterisk (*) to substitute one or more components of afully-qualified resource name. Components are optional and may be replaced by anasterisk (*).

For example, a specification for TSO expands with TSO/*/*.

Here are a few examples of how to specify resources using wildcards:

*/APL/SYS1All resources of type APL, on system SYS1.

TSO/*/SYS1All resources that have the name TSO, of any type, on system SYS1.

AOFKSEL4 SA z/OS - Command Dialogs Line 1 of 4Domain ID = IPSNO ---------- INGINFO ---------- Date = 02/24/00Operator ID = NETOP1 Time = 11:12:00

Multiple instances found for TSOSelect one item to be processed, then press ENTER.

Sel Name Type System Description--- ----------- ---- -------- ------------------------------------------

TSO APL KEY1 Time Sharing OptionTSO APL KEY2 Time Sharing OptionTSO APL KEY3 Time Sharing OptionTSO APL KEY4 Time Sharing Option

Command ===>PF1=Help PF2=End PF3=ReturnPF6=Roll PF12=Retrieve

Figure 1. Resource Selection Panel

Understanding Terms


*/SYS/*All resources of type SYS, on any system in the sysplex.

*/*/* All resources of any type on any system in the sysplex.

You can specify wildcards for a component of the fully-qualified resource name.The following shows a few examples:

TSO*/APL/KEY*All resources starting with TSO, of type APL, on the systems whose namesstart with KEY.

*TSO/AP*/*All resources whose names end with TSO, of any type starting with AP, onany system in the sysplex.

You can use the percentage sign (%) as a placeholder for one character. This meansthat any character in that position of the resource name matches. The followingshows a few examples:

%TSO*All resources whose names contain TSO starting in character two.

TSO/S%S/*All resources whose names start with TSO and where the first and lastcharacter of the type is S, on any system in the sysplex.

Understanding Terms

Chapter 2. Understanding Terms 7

Understanding Terms


Chapter 3. Format of Syntax Diagrams

The description of each command and routine includes the format of the commandin a syntax diagram. The diagram shows the operands for the commands. Useblanks to separate the operands, unless otherwise stated or diagrammed.

To construct a command from the diagram, follow the diagram from left to right,choosing the path that suits your needs. Following is a sample syntax diagram thatexplains how to construct a command. This sample command is for illustrationonly.

►►(1) (2)

ASample

(3)ALL

SOMENONE

(4)EQ

▼(5) (6)

job_number ►◄

Notes:

1 Start here. ►►─ indicates the start of the diagram.

2 You can type ASAMPLE or abbreviate it to AS. The uppercase characters are theabbreviation. Operands on the main line are required.

3 Choose one of the options. The default is always above the main line. In thiscase, ALL is the default. If the option includes punctuation marks, includethem too: =()., .

4 Choose E, Q, or neither. Operands below the main line are optional.

5 Repeat job_number any number of times. Variables are shown in italics.Replace them with a real name or value. Note that if you specify more thanone job_number you must put them in brackets.

6 End here. ─►◄ indicates the end of the command.

If a command continues to the next line, you see ─► and ►─. ├and┤ indicates afragment for a specific condition or option.

Examples:===> asample none q DAF00821 DAF00832 ELD00824===> as some DLR01445


Format of Syntax Diagrams


Part 2. SA z/OS System Operations Commands

This part describes SA z/OS system operations commands — their format, andspecifics of how to use them.

See IBM Tivoli System Automation for z/OS User's Guide for general informationabout the SA z/OS commands.


Chapter 4. System Operations Commands

Using System Operations Commands

General InformationYou can issue any system operations command by typing the command and itsparameters on the command line of any NetView or system operations panel.

You can also issue system operations commands by entering the command viaNMC. In addition, System Automation for z/OS provides a menu of commanddialogs that allows you to select a command dialog panel for a specific systemoperations command. For further information on how to issue system operationscommands, see IBM Tivoli System Automation for z/OS User's Guide.

Overview of Commands that Operate SysplexwideThe following system operations commands operate sysplexwide (which meansthat they also operate across an SA z/OS subplex):

DISPEVT/DISPEVTSDISPMTRINGAMSINGCF/INGCFLINGCFGINGCICSINGEVENTINGHISTINGIMSINGINFOINGLISTINGMOVEINGTWSINGPLEXINGRELSINGREQINGRUNINGSCHEDINGSETINGSTRINGTRIGINGVOTE

You can issue sysplexwide commands from any system within the sysplex,regardless of where the resource resides.

If no target is specified, the command that was issued will find the affectedresources in the sysplex.

Specifying the target system parameter is only required when routing thecommand from the focal-point system to a system in another sysplex or to a singleremote system.


For further information about sysplexwide commands, see IBM Tivoli SystemAutomation for z/OS User's Guide.

Additional Parameters for System Operations CommandsThe following parameters are available for a number of system operationscommands.

TARGET ParameterPurpose

The TARGET parameter lets you specify the system where the command is to beprocessed. You can direct the command to:v A particular system in the sysplex, or enterprisev A subset of systems in the sysplex, or enterprisev A sysplexv All systems currently active in the local sysplex

Format

►► Command nameTARGET= Destination

Dest_list*ALL

►◄

Destination:

system_namedomain_IDsaplex_name

Dest_list:

▼( Destination )

Values

system_nameSpecifies the name of the z/OS system

domain_IDSpecifies the NetView domain identifier

saplex_nameSpecifies the name of the sysplex

*ALL SA z/OS specifies that the command should be routed to all SA z/OSsystems that are currently active in the local sysplex.

Note that not all of the commands that support the TARGET parameteralso support the *ALL value. Refer to the syntax diagrams to find outwhether *ALL is supported.


Processing

The search sequence to locate the target is as follows:1. System name within the local sysplex2. Domain ID within the local sysplex3. Local sysplex name

If it is a human operator, the search continues in the following sequence:v Domain ID within the enterprisev System name within the enterprisev Sysplex name within the enterprise

If no value is specified, and the command does not refer to a defined resource, it isprocessed on the local system.

Non-Sysplexwide Commands:

If you do not specify the TARGET parameter, and the SA z/OS command refers toa defined resource, SA z/OS processing is as follows:v If the resource is only defined on one active system, the command is routed to

that system.v When processing the command in line mode, SA z/OS checks whether the

resource is defined on the local system. If it is, the command is processed locally.Otherwise, an error message is issued.

v If the resource is defined on more than one active system, and the command isnot running on an autotask, SA z/OS displays a selection panel such as inFigure 2 where you can select the resource or resources that the command is tobe routed to.

If you enter dispacf mvsesa a panel similar to Figure 2 is displayed.

If the target is within the local sysplex, the communication method is via XCFfacilities. Otherwise, the NetView RMTCMD command is used.

AOFKSEL1 SA z/OS - Command Dialogs Line 1 of 4Domain ID = IPUFA ---------- DISPACF ---------- Date = 06/27/00Operator ID = NETOP1 Time = 17:43:12

Multiple instances found for MVSESA in sysplex(es) AOCPLEXSelect one or more items to be processed, then press ENTER.

Sel System Domain--- -------- --------

AOCA IPUFAAOCB IPUFBAOCC IPUFCAOCD IPUFD

Command ===>PF1=Help PF2=End PF3=ReturnPF6=Roll PF12=Retrieve

Figure 2. Resource Selection Panel: Non-Sysplexwide

Additional Parameters for System Operations Commands

Chapter 4. System Operations Commands 15

Sysplexwide Commands:

Sysplexwide commands are processed locally.

If a target is specified and the resource is not defined on the specified system,SA z/OS issues an error message.

If you enter ingvote stdt000* a panel similar to Figure 3 is displayed.

OUTMODE ParameterPurpose

The OUTMODE parameter lets you specify the output mode of a command.

Format

►► Command nameOUTMODE= LINE

AUTONETLOG

►◄

Values

LINEIf you specify LINE, the output is displayed in line mode, independent of thetask type. Further characteristics are:v No color attributes are set for data that is shown in line mode.v The sequence of the fields may be different in line mode than in fullscreen.v Not all fields from the fullscreen display may be shown in line mode.v Line mode output is shown in a multiline message.v System operations commands can be issued within a NetView PIPE by using

the OUTMODE=LINE parameter, unless noted otherwise in the commanddescription.

AOFKSEL4 SA z/OS - Command Dialogs Line 1 of 32Domain ID = IPUFA ---------- INGVOTE ---------- Date = 06/27/00Operator ID = NETOP1 Time = 17:50:39

Multiple instances found for STDT000*Select one item to be processed, then press ENTER.

Sel Name Type System Description--- ----------- ---- -------- ------------------------------------------

STDT000AN00 APL AOCA Parent for all STD* appl 05/16/00 06:25STDT000AN00 APL AOCB Parent for all STD* appl 05/16/00 06:25STDT000AN00 APL AOCC Parent for all STD* appl 05/16/00 06:25STDT000AN00 APL AOCD Parent for all STD* appl 05/16/00 06:25STDT000AN1A APL AOCA Child of AN10 (child tree --- AN1B)STDT000AN1A APL AOCB Child of AN10 (child tree --- AN1B)STDT000AN1A APL AOCC Child of AN10 (child tree --- AN1B)STDT000AN1A APL AOCD Child of AN10 (child tree --- AN1B)STDT000AN1B APL AOCASTDT000AN1B APL AOCBSTDT000AN1B APL AOCC

Command ===>PF1=Help PF2=End PF3=ReturnPF6=Roll PF8=Forward PF12=Retrieve

Figure 3. Resource Selection Panel 2: Sysplexwide



v Line mode output is not processed by the NetView automation table and isnot written to the netlog. To write output from a command such asDISPSTAT to the netlog, use a PIPE command, for example:PIPE NETV DISPSTAT OUTMODE=LINE | LOGTO NETLOG

v Line mode output cannot be processed by a TRAP and WAIT.v System operations commands that support the OUTMODE=LINE option can

be used in user-written command lists. Note, however, that the format of theoutput may change in later releases.

v If you work with OUTMODE=LINE no prompt panel is displayed.

AUTOSpecifies that when the task that the command list runs on is unattended, theoutput of the command is written to the NetView log. Otherwise the output iswritten to the console.

NETLOGSpecifies that the output of the command is written to the NetView log.

Note: If no value is specified, the decision whether to display the commandoutput with a fullscreen panel or in line mode is based on the NetView task typethat the command is running on.

OUTDSN ParameterPurpose

This parameter lets you specify the name of the data set that is to contain theoutput of the command.

Format

►► Command nameOUTDSN=dsname

►◄

Values

dsnameThe data set name. You can specify a sequential data set or a member of apartitioned data set.

The record format should be variable-blocked and recommended is VB 1024.

Restrictions

The data set must already exist.

The OUTDSN parameter forces OUTMODE=LINE.

Note: If OUTDSN specifies a data set that is already allocated to NetView (forexample DSILIST), the exclusive ENQ that is issued when OUTDSN is used willnot be removed until NetView is stopped. Thus, it is recommended that you donot use pre-allocated data sets for OUTDSN.

Varying the Format of the Command OutputMost of the commands in fullscreen mode support the SORT and FINDsubcommands.



|

Sorting a ListThe SORT subcommand lets you change the order that data is displayed in.

The syntax of the SORT subcommand is as follows:

►► SORT ▼sort_order coln ►◄

sort_order:

A

D

You can specify the following:

sort_orderThe sort order. It can be:A The list is displayed in ascending order. This is the default.D The list is displayed in descending order.

coln The column to be sorted on. You can specify more than one column,separated by a comma or a blank.

For example, specifying SORT D,3 1 4 sorts the display in descending sequenceand in the order column 3, 1, and 4.

For commands that support horizontal scrolling (for example, DISPSTAT orINGLIST), the column title (header) can be used instead of column number. Thetitle can be abbreviated. First match is taken. For those commands you can alsoenter SORT without parameters which leads you to the column tailoring panel.There you can assign sort orders and sort keys to the columns. You can also hidecolumns or change the column sequence and whether a column is to be prefixed(show on every panel) or not. Refer to the online help on the column tailoringpanel for further capabilities of SORT.

Searching for StringsThe FIND subcommand searches the display data for a specified string.

It can be abbreviated to F. The RFIND (repeat find) command is used to find thenext occurrence of the string in the display data. It can be abbreviated to RF.

The syntax of the FIND subcommand is as follows:

►► FIND search_string direction ►◄

direction:

N

P

You can specify the following parameters with the FIND and RFIND commands:



||||||||

search_stringThe string that is to be searched for. The search starts at the first lineshown in the display.

directionThe direction that is used for the search. It can be:N Find the next occurrence (forward direction). This is the default.P Find the previous occurrence (backward direction).

ACFPurpose

The ACF command loads, displays, and modifies automation control file entries.You can use ACF to refresh data of a particular system if it does not affectautomation manager configuration data.

For modification and display actions to work, the automation control file must beloaded into storage. Once loaded, the displays and modifications affect anin-storage version of the automation control file, allowing you to make temporarychanges. To make permanent changes, change the automation policy using thecustomization dialogs, generate the automation control file member, then reloadthe new version using INGAMS. This ensures that the configuration matches theautomation manager and the automation agents.

Recommendations:

1. Use the INGAMS command rather than the ACF command to load or refreshan automation control file. This ensures that the configuration matches theautomation manager and the automation agents.

2. Changes to automation policy that are made using the SA z/OS commanddialogs or the ACF command are temporary. They modify the currentin-storage version of the automation control file directly. They do not modifythe automation control file that is stored on disk. To change an automationpolicy setting permanently, make sure you also change the automation policy(using the customization dialogs) that is stored on disk.

3. If the customization dialogs are used to rebuild the automation control file ondisk, the changed data on disk will replace the data in storage at ACFREFRESH.

4. Use scope-checking to limit operator use of ACF to load and displayoperations.

The following syntax diagrams show how to use the ACF command to perform thedifferent functions ACF supports. Do not combine syntax from the separatediagrams in the same ACF call.

Note: The ACF command is freeform:v Commas are optionalv More than one space can separate keywordsv Keywords can be specified in any sequencev Any parameters specified must follow the keyword that they apply to

To replace or add information in the automation control file use the followingsyntax:



Syntax

►► ACFfunction optionsdisplay request optionsdelete request optionsadd/replace request options

►◄

function options:

COLDREFRESHATLOADSTATUS

TOKEN=current_token DSN=current_dsnCHECK

TOKEN=token DSN=dataset_nameTOKEN=*

display options:

(1)REQ=DISP ENTRY=*

ENTRY=entry

▼

TYPE=*

TYPE= ( type )

delete options:

REQ=DEL ENTRY=entry TYPE=type

add/replace options:

REQ=REPL ENTRY=entry TYPE=type ▼

parms=value

Notes:

1 The specification of either REQ=DISP or ENTRY=entry is required.

Parameters

COLDReloads the currently loaded automation control file data from disk.Automation is disabled while the automation control file load is performed. Itdeletes all global variables that were associated with the Entry/type pairsdefined in the policy database. It also deletes all exceptional messages anddisabled timers. Statistical data provided by the INGRPT command is alsodeleted.

ACF


Note: It is not recommended to use ACF COLD. Especially for cleanups, usethe INGCLEAN command. For further details, refer to the INGCLEANcommand reference in IBM Tivoli System Automation for z/OS Programmer'sReference.

REFRESHUpdates the currently loaded automation control file data. Automation is notdisabled while the automation control file load is performed. Only data thathas been changed will be loaded, everything else remains the same as before.This is the safe way to update the automation control file. Refresh will not loaddata of a subsystem that is currently in the process of being started or stoppedby SA z/OS. SA z/OS will automatically retry the refresh five minutes laterfor the data that cannot currently be processed.

Note: ACF REFRESH will not delete global variables that were associated withEntry/Type pairs, that were deleted from the policy database before the lastbuild was done, if those Entry/Types were not associated with a subsystem, amonitor resource, or an application group. However, if a keyword/value isremoved from the Entry/Type, this is a change to the Entry/Type, andconsequently an ACF REFRESH will rebuild the Entry/Type with the resultthat the deleted keyword/value pair is removed from the global variables. Alldeleted Entry/Types and their associated global variables will be reset duringthe next SA z/OS NetView restart or during ACF COLD processing or byusing the INGCLEAN command. For further details, refer to the INGCLEANcommand reference in IBM Tivoli System Automation for z/OS Programmer'sReference.

ATLOADReloads the NetView automation tables that are specified in the System Infopolicy item and the message revision table, depending on the value ofAOFSMARTMAT.

STATUSDisplays information about the automation control file that is currently instorage.

CHECKVerifies the ACF for validity and tests the automation tables that are specifiedin the System Info policy and also the message revision table, depending onthe value of AOFSMARTMAT.

TOKENThe configuration token that the ACF should be validated against.

current_tokenThe token that is currently in use (displayed with ACF STATUS). This isthe default.

tokenThe configuration token used as the reference.

* Specifying an asterisk (*) means that the token validation should beomitted.

DSNThe data set name that contains the ACF data.

current_dsnThe data set that is currently in use (displayed via ACF STATUS). This isthe default.

ACF


dataset_nameThe configuration data set name containing the ACF data.

REQThe type of request for automation control file information the ACF commandperforms. This value can be one of the following:DISP

Displays information in the automation control file. This value is thedefault if this parameter is not coded.

DELDeletes information in the automation control file. This value must becoded when using ACF to delete automation control file information.

REPLReplaces or adds information in the automation control file. This valuemust be coded when using ACF to replace automation control fileinformation. REPL adds the entry specified on the ENTRY parameter if theentry does not already exist in the automation control file.

REQ=REPL will update data in place. That is, only data that is to bereplaced needs to be specified in the command. All other existing data willbe retained.

ENTRYThe entry field of the automation control file. This value can be up to 32characters long, without imbedded blanks, commas, or quotes.

If information in the automation control file is displayed (REQ=DISP), andno value is specified in the entry field, ENTRY=* is used.

TYPEThe type field in the automation control file. The following values can bespecified:* Specifying * returns all type fields that are associated with a given

entry, for example, all SUBSYSTEM or NTFYOP entries. * is the defaultvalue when REQ=DISP (display). REQ=DISP supports the use of * as awildcard character when specifying type names, with the followingrestrictions:v The wildcard character, *, must be the last character in the type

name. If an asterisk appears in any other position in a type namethen it will be treated as a literal. If an asterisk appears in any otherposition in a type name with an asterisk as the last character then nowildcard processing occurs and both asterisks are treated as literals.

v If you update an entry, you must specify the ENTRY= operandwithout a wildcard.

v If no matches are found, a final search is performed with a typename of DEFAULTS.

For other ACF request types (delete and replace), you must specify anactual type name.

typeThe name of the type field. REQ=REPL requests allow you to enteronly one type.

When ENTRY=SUBSYSTEM, type can be up to 11 bytes long. In allother cases, type can be up to 32 characters long, without imbeddedblanks, commas, or quotes.

(type,type,...)Multiple types may be specified for DISP and DEL requests. Typenames should be enclosed in parentheses and separated by commas.

ACF


For REQ=DISP, only the first type name found is displayed. ForREQ=DEL requests, all the type names will be deleted.

parms=valueThe data associated with the specified ENTRY and TYPE fields. This fieldis valid only with the REQ=REPL option. Specify this field as theparameter value, an equal (=) sign, and the value, without any spaces inbetween; for example, AUTO=NO.

The value can be any character data. It can have imbedded quotes,commas, and blanks, provided that single quotes, double quotes, orparentheses frame the value. If the value contains parentheses, then youcannot use parentheses as delimiters.

SA z/OS defines several ENTRY, TYPE, and parms=value fields. Aparms=value example is the JOB=jobname parameter in the SUBSYSTEMautomation control file entry.

Note: REQ=REPL will update data in place. That is, only modified data isupdated. All data will be retained.

Restrictions and Limitationsv If you use the COLD parameter, automation is disabled while the ACF LOAD is

in progress. If you use the REFRESH parameter, automation continues.v An automation control file cannot be loaded by an operator using the ACF

command if the automation flag for major resource MVSESA is set to ‘N’. If theautomation flag for the MVSESA.RELOAD.CONFIRM minor resource is set to‘Y’, the operator can reload the ACF.

v ACF must comply with the automation manager configuration, otherwisemessage AOF618I is issued.

v The ACF command should be used with care to change or delete automationpolicy settings. All changes are only temporary changes and may get lost duringthe next configuration refresh. The changes are definitely lost during an ACFCOLD or after processing the INGCLEAN command.

v The number of entries in the automation control file is limited only by theamount of storage in the SA z/OS address space or region. If you have a verylarge configuration, you may have to increase the REGION size in the SA z/OSprocedure.

v Not all data can be changed using ACF REQ=REPL, for example, serviceperiods, events, triggers, and dependencies cannot be changed. ACF REQ=DELand ACF REQ=REPL cannot be used to add or delete an application(subsystem), an application class, an application group or a monitor resource. Itis NOT recommended to change data of existing applications, application groupsand monitor resources via ACF REQ=REPL to avoid data mismatch betweenautomation agent and automation manager. Use the customization dialogs todefine these items and/or change those data.

v Changes to System Defaults and Application Defaults policy items are notpropagated to the instances that have inherited this data.

Security Considerations

The ACF command supports resource level security. If turned on, the followingprofiles in class SYSAUTO are checked:

ACF


|

||

Profile Authority Condition

AGT.sysplex.xcfgrp.RES.resname.restype[.ressys]

UPDATE When function option isREFRESH or ATLOAD

CONTROL When function option isCOLD and for delete(REQ=DEL) or add/replacerequests (REQ=REPL)

Usage other than listed in the table does not cause a resource level security check.For further details, refer to IBM Tivoli System Automation for z/OS Planning andInstallation.

Return Codes0 Function completed successfully.1 Control file inactive.3 ACF token mismatch.4 Invalid parameters were used in the call.12 No valid ACF member available.20 ACF reload not allowed by automation flag settings.24 Resource level security check failed100

Other error.

Usagev ACF performs two flag checks when the automation control file is reloaded. The

checks are of the Automation flags for MVSESA.RELOAD.CONFIRM andMVSESA.RELOAD.ACTION. The action flag is checked only if the reload is tocontinue.

MVSESA.RELOAD.CONFIRMThis lets you:– Turn the flag off and thus disable an automation control file reload by

an operator.– Tell SA z/OS to ask for confirmation by setting the AOFCONFIRM

TGLOBAL to YES in a flag exit.– Use a flag exit to perform additional checks and processing before

deciding to either cancel or proceed with the reload.

If the flag is found to be off, the operator cannot reload the automationcontrol file.

Note: You need to be aware of this if you turn the MVSESA automationflag off.

If the flag is on, the AOFCONFIRM task global is checked. If it is set toYES, SA z/OS will post a message requesting confirmation of the reloadrequest. If AOFCONFIRM is null, SA z/OS will proceed with the reload.

MVSESA.RELOAD.ACTIONThis provides an opportunity for you to do your own processing onceSA z/OS is committed to reloading or restoring the automation controlfile. You can use a flag exit to call your own code. Your exit shouldreturn 0, indicating that the flag is turned on. If you return a nonzeroreturn code, subsequent exits defined for the flag will not be invoked.

ACF


||||

|||||

||||||

|||

||

Note that there is no way of preventing the reload from an exit on thisflag. See IBM Tivoli System Automation for z/OS Defining Automation Policyand IBM Tivoli System Automation for z/OS Customizing and Programmingfor further information.

v When you use ACF REQ=DISP to request a certain ENTRY value with one ormore specific TYPE values, ACF searches for those types in the order specifiedin the command. When the first match is found, the information is returned tothe requester as a multiline message. If there are no matches, it performs a finalsearch with a type of DEFAULTS for that ENTRY value. If there is still no match,a message is returned to the requester. If the type DEFAULTS is found, thatinformation is returned to the requester.

v If, when ACF is used to display an automation control file entry, a specific TYPEis found, it is treated as a complete entry. Only that specific entry is displayed.

Messages

The following lists the messages that are issued during the operation of ACF.

For the load function (COLD/REFRESH):AOF042I MEMBER ACFZ999 NOT FOUNDAOF100I 16:05:09 : ’ACF REFRESH’ COMMAND ISSUEDAOF618I NO VALID ACF FOUND FOR sysname - detail descriptionAOF782I AUTOMATION CONTROL FILE PROCESSING COMPLETED

For the status function (STATUS):AOF005I MEMBER ACFZ992 CURRENTLY BEING USED FOR THE CONTROL FILEAOF006I BUILT BY OPER1 ON 04/29/12 AT 11:43:03AOF006I REFRESHED BY OPER1 ON 04/30/12 AT 08:52:20AOF006I CONFIGURATION TOKEN = 2012049090119000C6F7A2084AOF006I CONFIGURATION DATASET = OPER1.USER.V34.ACFAOF002I END OF MULTI-LINE MESSAGE GROUP

For the delete and replace function (REQ=DEL/REPL):AOF001I REQUEST REPL SUCCESSFUL FOR JES2-$HASP098

Note: In a display where the type_name is asterisk (*), multiple sets of AOF112I andAOF113I messages may be displayed. When the type is omitted or specified asasterisk (*), the DESIRED TYPE is not displayed in the AOF112I message.

For the display function (REQ=DISP):AOF041I UNABLE TO FIND entry type

AOF111I AUTOMATION CONFIGURATION DISPLAY - ENTRY= entry_nameAOF112I ACTIVE TYPE= act_type, DESIRED TYPE= desired_type ...AOF113I DATA IS data=valueAOF002I END OF MULTILINE MESSAGE GROUP

For example, the following may occur:AOF111I AUTOMATION CONFIGURATION DISPLAY - ENTRY= NTFYOPAOF112I ACTIVE TYPE= NETOP1AOF113I DATA IS OPER=’OPER 1’AOF113I DATA IS CLASS=(10,40)AOF112I ACTIVE TYPE= NETOP2AOF113I DATA IS CLASS=(10)AOF002I END OF MULTILINE MESSAGE GROUP

Note: Use of the replace parameter (REPL) adds an entry if none exists, resultingin a successful message.

ACF


Generic error messages that can occur:AOF013I SPECIFIED OPERAND operand INVALID FOR PARAMETER parameter.AOF025I SYNTAX ERROR

Examples

The ACF command to display the Start automation flag for the CICST subsystemis:ACF REQ=DISP,ENTRY=START,TYPE=CICST

The response is:AOF111I AUTOMATION CONFIGURATION DISPLAY - ENTRY= STARTAOF112I ACTIVE TYPE= CICST , DESIRED TYPE= CICSTAOF113I DATA IS AUTO=YAOF113I DATA IS NOAUTO=(TUESDAY,10:00,12:00)AOF002I END OF MULTILINE MESSAGE GROUP

In this example, a Start automation flag exists for the CICST subsystem. Theoperator or automation procedure processes the command to display the entry, andthe associated response is returned as a multiline message.

Use the following automation procedure to update ACF data for an entry. It allowsyou to modify the automation agent configuration data without affecting otherautomation agents or the automation manager./* ************************************************* **** Function: **** - Read ACF Fragment **** - Modify ACF entries **** ***************************************************/’PIPE (NAME ACFREPL)’,’QSAM (DSN) -dataset-’, /* read ACF fragment */’! NLOC 1.1 /*/’, /* skip comments */’! COLLECT’, /* collect to multiline */’! NETV ACF REQ=REPL’, /* call ACF command */’! CONS’ /* issue msgs to console */

AOCHELPPurpose

AOCHELP displays information about SA z/OS commands, and enables you toexecute them.

Syntax

►► AOCHELPcommandname

►◄

Parameters

commandname

Specifies the SA z/OS system operations command that you requireinformation about. The result is the same as if you had specified helpcommandname.

ACF


Restrictions and Limitationsv Some commands may not be executed from the AOCHELP command dialog.

Attempts to execute these commands produce SA z/OS message AOF129I.v Help is available only in fullscreen mode.v The AOCHELP command can only be used when SA z/OS has initialized.

Usage

If you type aochelp by itself, you see a list of commands to choose from, as shownin Figure 4. From this panel you can ask for help on a command by entering itsitem number.

Examples

To get help, specify the associated number of the command.

To execute the command, specify the number associated with the commandfollowed by an x, for example, 9x.

AOCTRACEPurpose

The AOCTRACE command turns the SA z/OS system operations debuggingfeature on or off. AOCTRACE allows you to activate:v Debugging globallyv Debugging for specific REXX scriptv Debugging at a certain level of detailv Tracing for a particular messagev REXX trace for a specific REXX script

AOFPH000 SA z/OS - Command Dialogs Line 1 of 62Domain ID = IPUFA ---------- AOCHELP ---------- Date = 09/01/12Operator ID = NETOP1 Time = 11:57:56

1 AOCHELP Display help for SA z/OS commands2 AOCTRACE Control the SA z/OS internal trace3 CROSS DOMAIN Dealing with other domains4 DISPACF Display control file information5 DISPAOPS Display automated operator information6 DISPAPG Display Automation group information7 DISPASF Display status file information8 DISPAUTO Display commands9 DISPERRS Display error information

10 DISPEVT Display event information11 DISPEVTS Display all events in a Sysplex12 DISPFLGS Display automation flag information13 DISPGW Display NNT gateway information14 DISPINFO Display subsystem information

Enter n for help or nX to execute the command (if possible).

Command ===>PF1=Help PF2=End PF3=Return PF6=Roll

PF8=Forward PF12=Retrieve

Figure 4. AOCHELP Command Dialog Panel

AOCHELP


Syntax

►► AOCTRACEOFFON

MSG/id OFFON

rexx_exec OFFON

level TraceTrace

►

►TARGET= system_name

domain_IDOUTMODE= LINE

AUTONETLOG

►◄

Trace:

traceroutine_name

Parameters

MSG/idThe message that is being traced.

rexx_execThe name of the REXX script that you want to debug.

ON Turns the debugging feature on.

If you do not specify a REXX script or message, AOCTRACE activates a globaldebugging flag. This causes each SA z/OS system operations REXX script thatis invoked to write a record (AOF700I) to the netlog showing the parametersthat it was invoked with.

If you do specify a REXX script or message, only that REXX script or messagewrites messages to the netlog. The netlog shows when and where the REXXscript was called, and what parameters were given.

If you specify a REXX script or message but not a trace, an intermediate levelof debugging is activated for the specified REXX script or message. This causesthe REXX script to issue a number of messages describing its actions. Note,however, that not all REXX scripts support this facility.

OFFTurns the debugging feature off.

If a REXX script is specified, this option deactivates both the intermediate andREXX tracing for the specified REXX script.

If a message is specified, this option deactivates message tracing for thespecified message.

If a REXX script or message is not specified, this option disables the globaltrace.

traceThe type of REXX trace that you want for the specified REXX script. Validvalues are:

AOCTRACE


A AllR ResultsI IntermediatesC CommandsE ErrorsF FailuresL LabelsO OffN Normal

routine_nameThe REXX script that is being traced.

levelSpecifies the debug level that allows you to limit the amount of debuginformation that is written to the netlog. The meaning of the level depends onthe particular REXX script.

NORMThis is the default. Control flow and important data area is written tothe netlog.

MAX Extensive logging of control flow and data areas and structures.

/AM Indicates that data received from the automation manager is nottraced.

/SLAVEIndicates that data received from the command slave is not traced.

TARGETFor information on the TARGET parameter, see “TARGET Parameter” on page14.

OUTMODEFor information on the OUTMODE parameter, see “OUTMODE Parameter” onpage 16.

For further information about AOCTRACE command usage, see "Appendix C -Problem Determination" of IBM Tivoli System Automation for z/OS User's Guide.

Restrictions and Limitations

The trace operand can only be used on interpreted REXX scripts.

Using the trace on certain REXX scripts can cause execution problems, particularlywith REXX scripts that trap messages.

The REXX trace setting of S (Scan) is not available.

Message tracing only works from the command line.

Note: The debugging facility is not active if REXX traces A, R, or I are used.

Examples

If you enter aoctrace on you see a message indicating that the debugging facilityhas been enabled. While the debugging facility is enabled, message AOF700I iswritten to the netlog for each procedure being processed.

AOCTRACE


If no parameter is specified Figure 5 is displayed.

The panel shows all the REXX scripts (that is, clists) and messages that have debugmode or REXX tracing turned on.

The first entry is the *GLOBAL* entry. This entry is always shown. It showswhether the global debug option is on or off. You cannot modify the setting with acommand code. To set the global debugging option specify AOCTRACE ON orAOCTRACE OFF on the command line.

*MSG* in the CLIST column indicates a message trace entry. The message ID isshown in the Subroutines/Messages being traced column. As with the Globalentry (*GLOBAL*), message trace entries cannot be modified on this panel: youmust use the AOCTRACE MSG/id,ON|OFF command entered at the commandline to do so.

The following information is shown:v The CLIST field shows the name of the REXX script.v The System field shows the name of the system where debugging or tracing is

active.v The Dbg field indicates whether or not debug mode is on. Y indicates that

debug mode is turned on.v The Level field indicates the debug level.v The T (Trace) field shows the Trace option specified for the REXX script.v The Subroutines/Messages being traced field shows the list of subroutines that

are being traced.

The Cmd field lets you specify the command codes shown on the panel. Type theappropriate letter next to the resource name and press Enter. The followingcommand codes are available:

A Allows you to add debug or trace settings for another REXX script. The panelshown in Figure 6 on page 31 is displayed where you can specify the REXXscript name and optionally overtype the other settings.

AOFKAANL SA z/OS - Command Dialogs Line 1 of 8Domain ID = IPSFP ---------- AOCTRACE ---------- Date = 08/16/08Operator ID = NETOP1 Time = 17:41:18

Enter ADD in the Command line to create an entryCmd: A Add C Change D Turn off Debug R Reset T Turn off Trace

Cmd CLIST System Dbg Level T Subroutines/Messages being traced--- -------- -------- --- -------- - -----------------------------------------

*GLOBAL* KEY4 Y*MSG* KEY4 IEF403*MSG* KEY4 IEF404EVJEATDF KEY4 Y REVJESPRQ KEY4 YEVJESPSC KEY4 YEVJESRST KEY4 YINGRMORD KEY4 YINGRYST0 KEY4 Y Y AOF_SHOW_LIST_PANEL

Command ===>PF1=Help PF2=End PF3=Return PF6=Roll

PF9=Refresh PF10=ALL_OFF PF12=Retrieve

Figure 5. AOCTRACE Main Command Dialog Panel

AOCTRACE


C Allows you to modify the debug or trace settings of the selected REXX script.The panel shown in Figure 6 is displayed showing the current settings. Hereyou can overtype the appropriate values.

D Turns off the debug option for the selected REXX script.

R Turns off the debug and trace option for the selected REXX script.

T Turns off the trace option for the selected REXX script.

Use the PF9 key to refresh the data displayed.

Use the PF10 key to turn off the debug and trace option for ALL displayed REXXscripts.

The ADD command can also be entered at the command line to define the debug ortrace settings for a REXX script.

Figure 6 is displayed when the command code A or C is specified on the panel inFigure 5 on page 30, or a REXX script name is specified as the only parameter ofthe AOCTRACE command. You can use this panel to enable and disable theautomation debugging facility for a given REXX script.

The following fields can be entered:

Clist nameSpecify the name of the clist (that is, REXX script) When turned ON, theREXX script will write debug information to the NetView log. Note that ifyou have already specified a REXX script with the AOCTRACE command,or entered the command code C next to a REXX script on the mainAOCTRACE panel, this field will contain that REXX script name andcannot be changed.

debug modeSpecify ON to turn on the REXX script's debug mode.

AOFKAAND SA z/OS - Command DialogsDomain ID = IPUN8 ---------- AOCTRACE ---------- Date = 08/16/08Operator ID = NETOP1 Time = 17:50:21

Specify or revise the following parameters:

Clist name INGRVRP0debug mode ON (ON or OFF)debug detail level (NORM, MAX, /AM, /SLAVE)REXX trace option (A, R, I, C, E, F, L, O N)

Subroutines to be traced: (* for all)

- or -

Message id ________________________________

Command ===>PF1=Help PF2=End PF3=Return PF6=Roll PF12=Retrieve

Figure 6. AOCTRACE Command Dialog Panel for a Specific REXX Script

AOCTRACE


debug detail levelSpecify the debug level for the REXX script. The meaning of the debuglevel varies from REXX script to REXX script. Standard values are:

NORMThis is the default. Control flow and important data area is writtento the netlog.

MAX Extensive logging of control flow and data areas and structures.

/AM Indicates that data received from the automation manager is nottraced.

/SLAVEIndicates that data received from the command slave is not traced.

REXX trace optionSpecify the trace setting for the REXX script. It can be one of the following:A AllR ResultsI IntermediatesC CommandsE ErrorsF FailuresL LabelsO OffN Normal_ Default

For more information about trace settings, see TRACE in z/OS TSO/EREXX Reference.

Notes:

1. The REXX script debug setting need not be ON to use REXX scripttrace.

2. Specifying REXX trace option A, I, or R makes individual REXX scriptdebugging ineffective.

Subroutines to be tracedSpecify the list of subroutines to be traced. By default, only the REXXscript main routine will be traced. You can specify more than onesubroutine name separated by a blank character. Specify '*' to trace allsubroutines.

Message idSpecify the message identifier to be traced.

ASFPurpose

The ASF command is a file manager command that displays records from theautomation status file. The automation status file records are maintained in aVSAM data set. ASF interfaces with the VSAM file to obtain control informationthat is vital to SA z/OS, such as:v Automation statusv Time and date information for specific events within the lifecycle of an

application

AOCTRACE


v Whether an error threshold has been exceededv Time and date information for error conditions

You can also use the ASF command to reset occurrences of threshold errors byupdating records in the automation status file.

Syntax

To display single or multiple records use the following syntax:

►► ASFREQ=DISP

ID=resourceFROM=resource

TO=resource

►◄

To re

Documents

System Automation for z/OS - IBM · 2020. 3. 6. · Overview of Commands .. . 3 Chapter 2. Understanding T erms ... . 5 Resour ce ... DISP APG Panel ..... . 42 10. Display of Automation