DOCSLIB.ORG

CA-7 3.3 Commands Guide 2.20 /OPERID

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
CA-7 3.3 Commands Guide 2.20 /OPERID CA-7® Commands Guide 3.3 This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user's informational purposes only and is subject to change or withdrawal by Computer Associates Interna- tional, Inc. (“CA”) at any time. THIS DOCUMENTATION MAY NOT BE COPIED, TRANSFERRED, REPRODUCED, DISCLOSED, OR DUPLICATED, IN WHOLE OR IN PART, WITHOUT THE PRIOR WRITTEN CONSENT OF CA. THIS DOC- UMENTATION IS PROPRIETARY INFORMATION OF CA AND PROTECTED BY THE COPYRIGHT LAWS OF THE UNITED STATES AND INTERNATIONAL TREATIES. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRAN- TIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE. THE USE OF ANY PRODUCT REFERENCED IN THIS DOCUMENTATION AND THIS DOCUMENTATION IS GOVERNED BY THE END USER'S APPLICABLE LICENSE AGREEMENT. The manufacturer of this documentation is Computer Associates International, Inc. Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227.7013(c)(1)(ii) or applicable successor provisions. First Edition, September 2000 1988-2000 Computer Associates International, Inc. One Computer Associates Plaza, Islandia, NY 11749 All rights reserved. All trademarks, trade names, service marks, or logos referenced herein belong to their respective companies. Contents Chapter 1. Introduction . 1-1 1.1 Summary of Revisions ................................ 1-2 1.1.1 Product Changes . 1-2 1.1.2 Documentation Changes . 1-5 1.2 Reading Syntax Diagrams .............................. 1-6 1.3 Commands . 1-12 1.4 General System Commands ............................ 1-13 1.5 General Inquiry Facility .............................. 1-14 1.6 Job Flow Control .................................. 1-16 1.7 Workstation Network Control ........................... 1-19 1.8 Forecasting . 1-22 1.8.1 Forecast Facility . 1-22 1.8.1.1 Forecast Options . 1-23 1.8.1.2 Forecast Commands . 1-24 1.8.1.3 Common Forecast Parameter Descriptions ............... 1-25 1.8.2 Forecasting From the Database ....................... 1-30 1.8.2.1 Commands . 1-30 1.8.2.2 Forecast Interval . 1-31 1.8.2.3 Examples . 1-32 1.8.3 Forecasting From Queues .......................... 1-33 1.8.3.1 Commands . 1-33 1.8.3.2 Forecast Interval . 1-34 1.8.4 Forecasting Job Flow Structures ....................... 1-36 1.8.4.1 Commands . 1-36 1.8.5 Forecasting Resources . 1-37 1.8.5.1 Commands . 1-37 1.8.5.2 Forecast Interval . 1-37 1.8.6 Forecasting Tape Requirements ....................... 1-38 1.8.6.1 Commands . 1-38 1.8.6.2 Forecast Interval . 1-38 1.8.7 Worksheets . 1-39 1.8.7.1 CPU Job Worksheets .......................... 1-39 Chapter 2. Commands . 2-1 2.1 /ASSIGN . 2-2 2.1.1 Format 1 . 2-2 2.1.2 Format 2 . 2-2 2.1.3 Format 3 . 2-2 2.1.4 Usage Notes . 2-3 2.1.5 Examples . 2-3 2.2 /AUTO . 2-4 2.2.1 Syntax . 2-4 2.2.2 Usage Notes . 2-4 2.2.3 Examples . 2-5 2.3 /BRO . 2-6 2.3.1 Syntax . 2-6 Contents iii 2.3.2 Examples . 2-7 2.4 /CHANGE . 2-8 2.4.1 Syntax . 2-8 2.4.2 Usage Notes . 2-9 2.4.3 Example . 2-9 2.5 /CLOSE . 2-10 2.5.1 Syntax . 2-10 2.5.2 Examples . 2-11 2.6 /COPY . 2-12 2.6.1 Syntax . 2-12 2.6.2 Usage Notes . 2-13 2.6.3 Examples . 2-13 2.7 /DISPLAY . 2-14 2.7.1 Syntax . 2-14 2.7.2 Examples . 2-19 2.8 /DMP1 . 2-26 2.8.1 Syntax . 2-26 2.9 /DUMP . 2-27 2.9.1 Syntax . 2-27 2.9.2 Usage Notes . 2-27 2.10 /ECHO . 2-28 2.10.1 Syntax . 2-28 2.10.2 Examples . 2-28 2.11 /FETCH . 2-29 2.11.1 Syntax . 2-29 2.12 /JCL . 2-30 2.12.1 Syntax . 2-30 2.13 /LOG . 2-33 2.13.1 Syntax . 2-33 2.13.2 Usage Notes . 2-33 2.13.3 Examples . 2-33 2.14 /LOGOFF . 2-34 2.14.1 Syntax . 2-34 2.15 /LOGON . 2-35 2.15.1 Syntax . 2-35 2.15.2 Usage Notes . 2-36 2.15.3 Example . 2-36 2.16 /MSG . 2-37 2.16.1 Syntax . 2-37 2.16.2 Usage Notes . 2-38 2.16.3 Examples . 2-38 2.17 /MVS . 2-39 2.17.1 Syntax . 2-39 2.17.2 Example . 2-39 2.17.3 Special Considerations . 2-39 2.18 /NXTMSG . 2-40 2.18.1 Syntax . 2-40 2.19 /OPEN . 2-41 2.19.1 Syntax . 2-41 2.19.2 Examples . 2-42 iv CA-7 3.3 Commands Guide 2.20 /OPERID . 2-43 2.20.1 Syntax . ..
Load more

Recommended publications
  • Z/OS ISPF Services Guide COMMAND NAME
    z/OS 2.4 ISPF Services Guide IBM SC19-3626-40 Note Before using this information and the product it supports, read the information in “Notices” on page 399. This edition applies to Version 2 Release 4 of z/OS (5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2021-06-22 © Copyright International Business Machines Corporation 1980, 2021. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures................................................................................................................ xv Tables................................................................................................................xvii Preface...............................................................................................................xix Who should use this document?............................................................................................................... xix What is in this document?......................................................................................................................... xix How to read the syntax diagrams..............................................................................................................xix z/OS information...............................................................................................xxiii How to send your comments to IBM...................................................................
    [Show full text]
  • OS/390 Introduction to ISPF
    z/OS Basic Skills Information Center: ISPF Course Module Module 1: Main Features of ISPF © Copyright IBM Corp., 2005. All rights reserved. z/OS Basic Skills Information Center: ISPF Course Module Introduction This module, Main Features of ISPF, introduces you to the z/OS Interactive System Productivity Facility, or ISPF, with special emphasis on the Program Development Facility, or PDF. Time to complete: 10 – 15 minutes © Copyright IBM Corp., 2005. All rights reserved. Page 2 of 15 z/OS Basic Skills Information Center: ISPF Course Module Main Features of ISPF - Objectives Upon completion of this module, you should be able to: • Describe the purpose of ISPF and its relationship to TSO • List the four major components of ISPF • Explain the function of each of the four components © Copyright IBM Corp., 2005. All rights reserved. Page 3 of 15 z/OS Basic Skills Information Center: ISPF Course Module Main Features of ISPF – Purpose of ISPF The Interactive System Productivity Facility, or ISPF, is a development tool set for the z/OS operating system. It has been used since 1975 to increase the productivity of the development of mainframe applications, because it provides an extensive set of programmer oriented facilities. © Copyright IBM Corp., 2005. All rights reserved. Page 4 of 15 z/OS Basic Skills Information Center: ISPF Course Module Main Features of ISPF – The Time Sharing Option/Extended (TSO/E) The Time Sharing Option/Extended, or TSO/E, is a base element of IBM's mainframe z/OS operating system. TSO/E allows you to communicate interactively with the MVS operating system by typing commands (one line at a time) on a computer terminal.
    [Show full text]
  • Operating Systems
    CS101 – Fundamentals of Computer and Information Sciences – LIU 1 of 2 Operating systems OS History We covered a (slightly rambling) story about the history of operating systems. Batch computing Batch systems were extraordinarily large and expensive, so that organizations could afford at most one or two. The machines had a human operator who was responsible for scheduling tasks for the machine, in order to make best use of its (very valuable) time. • Norwich council takes delivery of its first computer –@StuartSumner • Punch cards • IBM ad feat. punched cards • Keypunch machine • IBM 704 with card reader • LEGO Grace Hopper with Univac TODO: scheduling and calculating turn-around time using First-Come First-Served (FCFS) vs. Shortest Job First. (See book section 10.4, pages 350–351.) Time-sharing When mini-computers became available (just the size of a refrigerator, not a whole room), then we could have one for each workgroup or department within an orga- nization. They were powerful enough that multiple users could share the computer at the same time, by connecting multiple terminals (keyboard and monitor) to the same machine. The job of the human operator was now automated, and this was the golden ageof operating systems. Not only did they have to schedule tasks effectively, but they had to switch efficiently among serving different users, protect those users from interfer- ing with each other’s work, and so on. Some of the operating systems developed in this era were Multics, VMS, and UNIX. • PDP-11 with Ken Thompson, Dennis Ritchie • VT-101 terminal • IBM 7090 time-sharing video • Brian Kernighan on Bell Labs (Computerphile video) 2 of 2 Prof.
    [Show full text]
  • CA SOLVE:FTS Installation Guide
    CA SOLVE:FTS Installation Guide Release 12.1 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT.
    [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]
  • The FORTRAN Automatic Coding System J
    The FORTRAN Automatic Coding System J. W. BACKUS?, R. J. BEEBERt, S. BEST$, R. GOLDBERG?, L. M. HAIBTt, H. L. HERRICK?, R. A. NELSON?, D. SAYRE?, P. B. SHERIDAN?, H.STERNt, I. ZILLERt, R. A. HUGHES§, AN^.. .R. NUTT~~ system is now copplete. It has two components: the HE FORTRAN project was begun in the sum- FORTRAN language, in which programs are written, mer of 1954. Its purpose was to reduce by a large and the translator or executive routine for the 704 factor the task of preparing scientific problems for which effects the translation of FORTRAN language IBM's next large computer, the 704. If it were possible programs into 704 programs. Descriptions of the FOR- for the 704 to code problems for itself and produce as TRAN language and the translator form the principal good programs as human coders (but without the sections of this paper. errors), it was clear that large benefits could be achieved. The experience of the FORTRAN group in using the For it was known that about two-thirds of the cost of system has confirmed the original expectations con- cerning reduction of the task of problem preparation solving most scientific and engineering problems on 1 large computers was that of problem preparation. and the efficiency of output programs. A brief case Furthermore, more than 90 per cent of the elapsed time history of one job done with a system seldom gives a for a problem was usually devoted to planning, writing, good measure of its usefulness, particularly when the and debugging the program.
    [Show full text]
  • 16520: Application Development for Z/OS - Not Your Father's Green Screen
    16520: Application Development for z/OS - Not your Father's Green Screen Rosalind Radcliffe Distinguished Engineer, IBM Academy of Technology Member IBM Corporation [email protected] @RosalindRad Insert Custom Session QR if Desired. Abstract Ask most people how they write and maintain applications on z/OS and you hear "oh, you use this thing called a green screen" followed by a chuckle. In reality, application development for zEnterprise applications has been transformed over the past several years to the point where application developers enjoy the same or better features from integrated development environments as programmers who work on other platforms. Advances in remote system communication and interaction, syntax- highlighting, parsing, and code understanding for Assembler, PL/I, C/C++, and COBOL source code, as well as programming assists such as code snippets and templates are all available to application programmers. Interactive debug of applications, written in multiple programming languages and running in various runtime environments is also possible and can greatly boost programmer productivity. Come and learn about how these features can enable application developers who are new to the mainframe to interact with, update, and efficiently enhance mainframe applications. 16721: Decision Management: Making the Right Change, at the Right Time 3/4/15 3 IBM DevOps point of view Enterprise capability for continuous software delivery that enables organizations to seize market opportunities and reduce time to customer feedback Continuous
    [Show full text]
  • Mainframe to Enterprise to the Is Curriculum
    https://doi.org/10.48009/2_iis_2012_182-192 Issues in Information Systems Volume 13, Issue 2, pp. 182-192, 2012 MAINFRAME TO ENTERPRISE TO THE IS CURRICULUM Joseph Packy Laverty, Robert Morris University, [email protected] Frederick G. Kohun, Robert Morris University, [email protected] John Turchek, Robert Morris University, [email protected] David Wood, Robert Morris University, [email protected] Daniel Rota, Robert Morris University, [email protected] ABSTRACT Over the decades the concept of a mainframe has been synonymous to IBM operating systems and the COBOL programming language. While object-orientated programming languages, web interface transaction systems, web services, distributed services, and mobile application topics are frequently included in the IS/CS curriculum, this paper considers the inclusion of IBM Enterprise Systems. IBM zEnterprise has evolved into an integrated, scalable, enterprise system which supports legacy applications, open-source applications and tools, DB2, Cognos, SPSS, data mining and Rational project management tools. The growth and market penetration of IBM zEnterprise has been spectacular. This evolution of IBM Enterprise Systems provides many opportunities for IS/CS majors. A case study implementing the IBM Academic Initiative in an ABET-CAC curriculum is presented. KEYWORDS: IBM Academic Initiative, IS Curriculum, IBM zEnterprise, ABET-CAC, z/OS, COBOL, CICS, DB2, Open Source, Rational Application Developer for Z Systems, Robert Morris University, Marist College INTRODUCTION Over the decades the concept of a mainframe has been synonymous to IBM operating systems and the COBOL programming language [1]. In recent years, computer hardware evolved in various directions, e.g., desktop, blade servers, super computers and mobile devices.
    [Show full text]
  • The Future Integrated Information and Z/OS Documentation
    The Future of Integrated Information and z/OS Documentation Tuesday, August 3, 2010: 9:30 AM-10:30 AM - SHARE Boston 2010 Speaker: Geoff Smith IBM Corp ([email protected]) © 2010 IBM Corporation ZSP03047-USEN-05 IBM System z Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. Active Energy Manager FICON* Rational* System z9* CICS* IBM* Redbooks* System z10 DataPower* IBM eServer REXX Tivoli* DB2* IBM logo* RMF WebSohere* developerWorks* IMS S/390* z9 DFSMS Infoprint* SYSREXX* z/Architecture* DFSMSdfp Language Environment* System i* z/OS* DFSMShsm Lotus* System p* z/VM* DFSMSrmm MQSeries* SystemPac* z/VSE DFSORT Domino OMEGAMON* System Storage zSeries* DRDA* Parallel Sysplex* System z* DS8000* RACF* * Registered trademarks of IBM Corporation The following are trademarks or registered trademarks of other companies. Java and all Java-related trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countries Linux is a trademark of Linus Torvalds in the united States and other countries.. UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft and Excel are registered trademarks of Microsoft Corporation in the United States and other countries. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed.
    [Show full text]
  • IBM Db2 Query Monitor for Z/OS User's Guide
    3.3 IBM Db2 Query Monitor for z/OS User's Guide IBM SC27-8803 Note: Before using this information and the product it supports, read the "Notices" topic at the end of this information. 2021-04-21 edition This edition applies to Version 3 Release 3 of DB2® Query Monitor (product number 5655-V42) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 1999, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. © Rocket Software Inc. 1999, 2020. Contents About this information.......................................................................................... ix Chapter 1. Overview.............................................................................................. 1 What's new in Db2 Query Monitor............................................................................................................... 1 New and changed functions...................................................................................................................1 Db2 12 function level support................................................................................................................3 Db2 12 function level support for Db2 Data Access Common Collector..............................................4 Features and benefits.................................................................................................................................. 5 Collect
    [Show full text]
  • Chapter Three Introduction to Computer Troubleshooting
    Chapter Three Introduction to Computer Troubleshooting Welcome to the Machine Introduction to Computer Troubleshooting What are the three steps in the computer troubleshooting process? What do you do if the three steps does not solve your problem? DON’T PANIC!” When things go wrong remain calm, as most computer problems are a simple fix. Even if it is the rare serious problem, usually your data is still there waiting for you. The computer troubleshooting process at its most basic is gathering information about what is going on, drawing conclusions about the information gathered, and acting on those conclusions to solve the problem. If that does not solve the problem, then we return to the gathering information stage and go through the steps again. You might think of it as a loop which we exit when the problem is solved. At the top of the paragraph, I said that most computer problems are a simple fix and I would like you to keep that in mind as we go through this chapter. Important Words in this Chapter Cables Memory Simple-to-Complex Connectors Monitor Surge Protector CPU Motherboard System HD (Hard Drive) NIC (Network Card) Troubleshooting Input Devices Power Supply Video Card Main Troubleshooting Principle What is the principle on which we base all efficient and effective troubleshooting? All efficient and effective troubleshooting is based on the principle of proceeding from the simple-to-the- complex. Why is this true? Starting with complex items first, can cause you to draw the wrong conclusions. The complex parts of a computer depend on the simpler things.
    [Show full text]
  • NBS FORTRAN Test Programs 3^1 No "I Volume 1- Documentation for Versions 1 and 3 V.I
    j I i Vt NBS SPECIAL PUBLICATION 399 J Volume 1 U.S. DEPARTMENT OF COMMERCE / National Bureau of Standards] National Bureau of Standards Library, £-01 Admin. BIdg. ncT 1 1981 13102^1 NBS FORTRAN Test Prog Volume 1-Documentation for Versions 1 and 3 NATIONAL BUREAU OF STANDARDS The National Bureau of Standards^ was established by an act of Congress March 3, 1901. The Bureau's overall goal is to strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and technological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to promote public safety. The Bureau consists of the Institute for Basic Standards, the Institute for Materials Research, the Institute for Applied Technology, the Institute for Computer Sciences and Technology, and the Office for Information Programs. THE INSTITUTE FOR BASIC STANDARI>S provides the central basis within the United States of a complete and consistent system of physical measurement; coordinates that system with measurement systems of other nations; and furnishes essential services leading to accurate and uniform physical measurements throughout the Nation's scientific community, industry, and commerce. The Institute consists of a Center for Radiation Research, an Office of Meas- urement Services and the following divisions: Applied Mathematics — Electricity — Mechanics
    [Show full text]