DOCSLIB.ORG

Implementing REXX Support in SDSF

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Implementing REXX Support in SDSF Front cover Implementing REXX Support in SDSF Harness the power of SDSF with the versatility of REXX Write powerful REXX code to manage your environment Access SDSF outside of your mainframe Lydia Parziale Ludvik Drobnic Dario Facchinetti Richard Levey Amy Miu ibm.com/redbooks International Technical Support Organization Implementing REXX Support in SDSF June 2007 SG24-7419-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. First Edition (June 2007) This edition applies to z/OS Release 1 Version 9 with APAR PK43448 Note: This book is based on a pre-GA version of a product and might not apply when the product becomes generally available. We recommend that you consult the product documentation or follow-on versions of this book for more current information. © Copyright International Business Machines Corporation 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . ix Notices . xi Trademarks . xii Preface . xiii The team that wrote this book . xiv Become a published author . xv Comments welcome. xvi Introduction and overview. 1 The REXX with SDSF interface . 2 Telling SDSF to execute commands . 4 Panel display commands . 5 New capabilities of REXX with SDSF in z/OS V1.9 . 11 SDSF programming practices . 13 Host environment verses interactive environment . 13 Recommendations . 14 Tune the command processing. 16 Areas to consider . 16 Debugging tools . 17 VERBOSE parameter . 17 SDSF trace . 17 Running REXX executables . 21 TSO/E address spaces . 21 Batch non TSO/E address spaces . 28 UNIX System Services address spaces . 31 Chapter 1. Issuing a system command. 37 1.1 Command environment . 38 1.2 Considerations when issuing a system command in the host command environment . 38 1.2.1 Console name . 38 1.2.2 Console type . 39 1.2.3 Command authority. 39 1.2.4 Delay time limit . 39 1.3 Customization . 39 1.4 ISFEXEC operands . 40 1.4.1 System command . 40 © Copyright IBM Corp. 2007. All rights reserved. iii 1.4.2 Other optional parameters . 41 1.5 Command output. 41 1.6 REXX for SDSF system command executable samples. 41 1.6.1 Sample REXX exec - @SYSCMD . 42 1.6.2 Scenario 1 - Use the system-determined EMCS console . 58 1.6.3 Scenario 2 - Use an internal console . 59 1.6.4 Scenario 3 - Use a specific EMCS console. 60 1.6.5 Scenario 4 - Request for the initial command response . 61 1.6.6 Scenario 5 - Request for all command responses . 63 1.6.7 Scenario 6 - Confirm the execution of the system command . 67 1.6.8 Scenario 7 - Query for a started task status . 68 1.6.9 Scenario 8 - Query for a device status . 70 1.6.10 Scenario 9 - Reply to the system command generated WTOR . 72 1.6.11 Scenario 10 - Confirm the execution of the system command and reply to its WTOR . 74 1.6.12 Scenario 11 - Confirm the execution of the system command and the reply to the WTOR . 76 1.6.13 Scenario 12 - Suppress all outputs . 78 Chapter 2. Copying SYSOUT to a PDS . 81 2.1 Background and overview of this scenario . 82 2.2 Input to BUILDPDS . 83 2.3 Program flow . 84 2.3.1 Decoding the arguments . 85 2.3.2 Deleting and reallocating the PDS . 88 2.3.3 Interfacing with IBM z/OS System Display and Search Facility . 89 2.3.4 Writing the data to the PDS. 93 2.4 Suggestions for continued development . 96 Chapter 3. Bulk job update processor. 97 3.1 Scenario description . 98 3.1.1 Tasks that this scenario accomplishes . 98 3.1.2 Testing the scenario . 102 3.2 Programming the interface . 102 3.2.1 Program flow . 103 3.2.2 Retrieving SYSOUT information . 105 3.2.3 Generic filter processing . 111 3.2.4 Processing the CANCEL and OVERTYPE commands. 112 3.3 Processing the EXECUTE command . 115 3.3.1 A sample CLIST . 117 iv Implementing REXX Support in SDSF 3.4 Future development . 120 Chapter 4. SDSF support for the COBOL language. 123 4.1 Understanding the middleware between a REXX exec and another language . 124 4.2 The pieces of REXDRIVR and how they work together . 126 4.2.1 The REX4SDSF exec . 126 4.3 The REXDRIVR interface program . 128 4.3.1 Entry point REXDRIVR - REX4SDSF function processor. 128 4.3.2 The Application Program’s view of SDSF: The parameter list . 135 4.3.3 Entry point REXXSDSF - Application program service routine . 139 4.4 Entry point REXXDONE - REX4SDSF completion routine . 143 4.4.1 Entry point REXXFREE - storage release routine. 147 4.5 The application programs included in the additional materials . 147 4.6 The COBOL point of view . 148 4.7 Improving the interface . 151 Chapter 5. Searching for a message in SYSLOG . 153 5.1 Scenario description . 154 5.2 Solving the issue with REXX with SDSF . 154 5.3 The actual code. 154 5.3.1 Parameters . 154 5.3.2 Program flow . 155 5.3.3 Configuring the SDSF execution environment . 156 5.3.4 Obtaining the SYSLOG job names ..
Load more

Recommended publications
  • The Arcati Mainframe Yearbook 2020
    ArcatiArcati MainframeMainframe YearbookYearbook 20072020 Mainframe strategy The Arcati Mainframe Yearbook 2020 The independent annual guide for users of IBM mainframe systems SPONSORED BY: PUBLISHED BY: Arcati Limited 19 Ashbourne Way Thatcham Berks RG19 3SJ UK Phone: +44 (0) 7717 858284 Fax: +44 (0) 1635 881717 Web: http://www.arcati.com/ E-mail: [email protected] © Arcati Limited, 2020 1 Arcati Mainframe Yearbook 2020 Mainframe strategy Contents Welcome to the Arcati Mainframe Yearbook 2020 ............................................................ 3 10 Steps to True Mainframe DevOps: A Phased Approach to Cross-platform DevOps Success ................................................................................. 6 Mainframe Data Management .......................................................................................... 17 Join a Mainframe Development Revolution in 2020 – Embrace Open! ....................... 22 Indicators of Compromise and Why It Takes Six-Plus Months to ID a Breach ........... 27 Mainframe breaches: a beginner’s defensive strategy ................................................. 33 The 2020 Mainframe User Survey .................................................................................... 37 An analysis of the profile, plans, and priorities of mainframe users Vendor Directory ............................................................................................................... 55 Vendors, consultants, and service providers in the z/OS environment A guide to sources of information
    [Show full text]
  • Introduction to the New Mainframe: Z/OS Basics
    Front cover Introduction to the New Mainframe: z/OS Basics An introduction to mainframe computing on the IBM zSeries platform z/OS concepts and facilities for students and beginners zSeries hardware and peripheral devices Mike Ebbers Wayne O’Brien Bill Ogden ibm.com/ International Technical Support Organization z/OS Basics March 2005 SG24-6366-00 Note: Before using this information and the product it supports, read the information in “Notices” on page -1. First Edition (March 2005) © Copyright International Business Machines Corporation 2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Preface . xvii How this text is organized . xvii How each chapter is organized . xviii Acknowledgements . xix Comments welcome. xxi Part 1. Introduction to z/OS and the mainframe environment Chapter 1. Introduction to the new mainframe . 1-1 1.1 The new mainframe. 1-2 1.2 Evolving architecture . 1-2 1.3 Mainframes in our midst . 1-4 1.4 What is a mainframe? . 1-5 1.5 Who uses mainframe computers?. 1-7 1.6 Factors contributing to mainframe use . 1-8 1.6.1 Reliability, availability, and serviceability. 1-9 1.6.2 Security . 1-10 1.6.3 Scalability . 1-10 1.6.4 Continuing compatibility . 1-11 1.7 Typical mainframe workloads . 1-11 1.7.1 Batch processing. 1-12 1.7.2 Online transactional processing . 1-15 1.8 Roles in the mainframe world . 1-17 1.8.1 Who is the system programmer? . 1-19 1.8.2 Who is the system administrator? .
    [Show full text]
  • Z/OS Basics Preface
    Contents Preface . iii How this course is organized . iii How each topic is organized . iv Part 1. Introduction to z/OS and the mainframe environment Chapter 1. Introduction to the new mainframe . 3 1.1 The new mainframe. 4 1.2 The S/360: A turning point in mainframe history . 4 1.3 An evolving architecture . 5 1.4 Mainframes in our midst . 6 1.5 What is a mainframe? . 7 1.6 Who uses mainframe computers?. 10 1.7 Factors contributing to mainframe use . 11 1.8 Typical mainframe workloads . 14 1.9 Roles in the mainframe world . 21 1.10 z/OS and other mainframe operating systems . 27 1.11 Summary . 29 Chapter 2. z/OS overview. 31 2.1 What is an operating system? . 32 2.2 Overview of z/OS facilities. 32 2.3 What is z/OS? . 34 2.4 Virtual storage and other mainframe concepts . 39 2.5 What is workload management? . 57 2.6 I/O and data management. 60 2.7 Supervising the execution of work in the system . 60 2.8 Defining characteristics of z/OS . 68 2.9 Licensed programs for z/OS . 69 2.10 Middleware for z/OS . 70 2.11 A brief comparison of z/OS and UNIX. 71 2.12 Summary . 73 Chapter 3. TSO/E, ISPF, and UNIX: Interactive facilities of z/OS . 75 3.1 How do we interact with z/OS? . 76 3.2 TSO overview . 76 3.3 ISPF overview . 80 3.4 z/OS UNIX interactive interfaces. 99 3.5 Summary .
    [Show full text]
  • Abcs of Z/OS System Programming Volume 1
    Front cover ABCs of z/OS System Programming Volume 1 Lydia Parziale Luiz Fadel Stanley Jon Redbooks International Technical Support Organization ABCs of z/OS System Programming Volume 1 November 2017 SG24-6981-04 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. Fifth Edition (November 2017) This edition applies to version 2 release 3 of IBM z/OS (product number 5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2014, 2017. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix Authors. .x Now you can become a published author, too . .x Comments welcome. xi Stay connected to IBM Redbooks . xi Chapter 1. The World of IBM Z . 1 1.1 IBM Z hardware configuration . 2 1.2 Parallel Sysplex. 2 1.3 Coupling facility . 3 1.3.1 CF structure encryption. 3 1.4 Cryptographic hardware . 5 1.5 z/OS services . 5 1.6 ICSF . 7 1.7 z/OS security. 10 1.7.1 SAF . 10 1.7.2 RACF . 10 1.8 Data Facility Storage Management Subsystem . 11 1.8.1 z/OS Data Set Encryption . 12 1.9 IBM Health Checker for z/OS . 13 1.9.1 Health Checker for z/OS processing. 14 1.10 IBM z/OS Management Facility. 15 Chapter 2. The z/OS system programmer. 17 2.1 The role of the system programmer .
    [Show full text]
  • Enterprise Computing Mainframe
    Enterprise Computing Mainframe Dr. Shan Barkataki Chan Nguyen Viet Hoang Tu Tran Enterprise Computing Project Team Computer Science Dept California State University, Northridge 1 Contents • Two Parts – Mainframe (This set of slides) – Enterprise programming (COBOL, Tools and Techniques) • Mainframe • What is a Mainframe? Who uses them? Who runs them? • Important characteristics: reliability, availability, security • Computing power, batch, transaction, online processsing • Operating system & Programming • Jobs, internships, salary • Learning resources • Demonstrations • CSUN Enterprise Computing project 2 Why Learn Enterprise Computing? • The World economy runs on Enterprise systems • Banks, brokerage, stock exchanges – Point of sell transactions • Travel sites, air line ticketing, supermarket stock control – Healthcare & Insurance systems – Large manufacturing and commerce systems – Government computing • Enterprise systems run on Mainframes – Why? Speed, simplicity, reliability, scalability • Good part of the software is based on legacy code – COBOL 3 What is a Mainframe? • Part 1 – http://www.youtube.com/watch?v=d0-pLcgq-2M 4 People don’t know mainframes • Hollywood Myths vs. Reality 5 Modern Mainframe Physical Dimensions 79” Air flow Air flow front to rear front to rear 71” 31” 62” Business Class (BC) Enterprise Class (EC) 6 What is a mainframe • Part 2 – http://www.youtube.com/watch?v=ewsaYde59C0 7 Webopedia “A very large and expensive computer capable of supporting hundreds, or even thousands, of users simultaneously. In the hierarchy
    [Show full text]
  • JCL and SDSF
    Uni Hamburg – Mainframe Summit 2010 z/OS – The Mainframe Operating System Appendix 1 – JCL and SDSF Redelf Janßen IBM Technical Sales Mainframe Systems [email protected] © Copyright IBM Corporation 2010 Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 4.0.1 Introduction to the new mainframe Chapter 6: Using Job Control Language (JCL) and System Display and Search Facility (SDSF) © Copyright IBM Corp., 2010. All rights reserved. Introduction to the new mainframe Chapter 6 objectives Be able to: • Explain how JCL works with the system, give an overview of JCL coding techniques, and know a few of the more important statements and keywords • Create a simple job and submit it for execution • Check the output of your job through SDSF © Copyright IBM Corp., 2010. All rights reserved. 3 Introduction to the new mainframe Key terms in this chapter • concatenation • record format (RECFM) • DD statement • system display and search • Job Control Language (JCL) facility (SDSF) • JOB statement • step name • EXEC statement • system catalog • job name • system library • procedure (PROC) • utility © Copyright IBM Corp., 2010. All rights reserved. 4 Introduction to the new mainframe What is JCL? Job control language (JCL) tells the system what program to execute and provides a description of program inputs and outputs. There are three basic JCL statements: • JOB statement • EXEC statement • DD statement © Copyright IBM Corp., 2010. All rights reserved. 5 Introduction to the new mainframe Basic JCL coding syntax JCL must be uppercase Forward slash in column 1 and 2 Name (1-8 characters) follow the slashes Space separators //JOBNAME JOB //STEPNAME EXEC //DDNAME DD //* comment - upper or lower case /* ....end of JCL stream © Copyright IBM Corp., 2010.
    [Show full text]
  • Z/OS V1R1.0 Parallel Sysplex Overview Figures
    z/OS Parallel Sysplex Overview: Introducing Data Sharing and ParallelisminaSysplex SA22-7661-00 z/OS Parallel Sysplex Overview: Introducing Data Sharing and ParallelisminaSysplex SA22-7661-00 Note Before using this information and the product it supports, be sure to read the general information under “Appendix. Notices” on page 41. First Edition, March 2001 This edition applies to Version 1 Release 1 of z/OS (5694-A01), and to subsequent releases and modifications until otherwise indicated in new editions. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below. IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication, or you may address your comments to the following address: International Business Machines Corporation Department 55JA, Mail Station P384 2455 South Road Poughkeepsie, NY 12601-5400 United States of America FAX (United States & Canada): 1+845+432-9405 FAX (Other Countries): Your International Access Code +1+845+432-9405 IBMLink (United States customers only): IBMUSM10(MHVRCFS) Internet e-mail: [email protected] World Wide Web: http://www.ibm.com/servers/eserver/zseries/zos/webqs.html If you would like a reply, be sure to include your name, address, telephone number, or FAX number. Make sure to include the following in your comment or note: v Title and order number of this book v Page number or topic related to your comment When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
    [Show full text]