DOCSLIB.ORG

Understanding the Other JES

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Understanding the Other JES Understanding The Other JES Greg Thompson IBM System Test March 13, 2014 Session Number 15094 JES3 Spool Management 11 Trademarks • The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. • IBM® • MVS • JES2 • JES3 • RACF® • z/OS® • zSeries® • The following are trademarks or registered trademarks of other companies. • * Registered trademarks of IBM Corporation • * All other products may be trademarks or registered trademarks of their respective 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 registered trademark of Linus Torvalds in the United States, other countries, or both. • Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation. • UNIX is a registered trademark of The Open Group in the United States and other countries. • SET and Secure Electronic Transaction are trademarks owned by SET Secure Electronic Transaction LLC. • 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. Therefore, no assurance can • be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. • IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. • All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual • environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. • This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. • Consult your local IBM business contact for information on the product or services available in your area. • All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. • Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, • or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. 2 JES3 Spool Management 2 What does JES do? • Manages SPOOL space to store JCL, SYSIN, SYSOUT • Manages jobs (started tasks, TSO users, BATCH) • Does input processing for job • Manages conversion processing • Manages JES mode initiators • Selects jobs for execution • Processes SYSOUT • Provides execution services and enquiry services • Does remote processing (NJE/RJE/RJP) • Performs these functions across multiple z/OS images • Integrates images into a single system to process work 3 The IBM z/OS operating systems use a job entry subsystem (JES) to receive jobs into the operating system, schedule them for processing by MVS or z/OS, and to control their output processing. There are two versions of the job entry subsystem concept, JES3 and JES2. Some principle differences between the two JES systems include: ° JES3 provides resource management, dependent job control, and deadline scheduling for users of the system, while JES2 in the same system would require its users to manage these activities through other means. ° In cases where multiple z/OS systems are clustered (a sysplex), JES3 exercises centralized control over its processing functions through a single global JES3 processor. The global processor provides all job selection, scheduling, and device allocation functions for all of the other JES3 systems in the sysplex. JES2 is that component of MVS that only provides the necessary functions to get jobs into, and output out of, the MVS system. JES2 is designed to provide spooling, scheduling, and management facilities for the z/OS systems in a sysplex. JES3 Spool Management 3 JES2 • Common set of work queues stored in its checkpoint • Member adds to or selects work from this common queue • Checkpoint is time sliced among members • Simple mechanisms for managing work • Resource management done by MVS • Depend on MVS (scheduling environment, etc) to determine eligibility to select jobs for execution • Jobs sit in initiators waiting for resources • Peer to Peer relationship between members • Members select work that it can process • Little regard to other members • No single point of control • No critical member • Primary communication via JES2 checkpoint data set 4 JES3 Spool Management 4 JES2 MAS SPOOL CKPT Member Devices Member SYSA SYSC All members perform: • Input processing Member • Spool Management SYSB • Job Scheduling • SYSOUT scheduling • SSI processing • NJE/RJE 5 JES3 Spool Management 5 JES3 • JES3 does resource and workflow management before and after job execution. • MVS does resource and workflow management during job execution. • JES3 exercises centralized control through the global processor. • Global performs job selection, scheduling, and device allocation functions for the local processors. • Provides increased job scheduling control, deadline scheduling capabilities, and increased control with JES3 device allocation. 6 JES3 Spool Management 6 JES3 Global and Local Function SPOOL Devices Local Local Processor Processor Global Functions: Local Functions: • Input processing Global • C/I and WTR Functional • Spool Management Processor Subsystems (FSS) • Job setup • Netserv and BDT • Job scheduling • Some SSI processing • SYSOUT scheduling • SSI processing • C/I and WTR Functional Subsystems (FSS) • Netserv and BDT 7 JES3 Spool Management 7 JES3 Global • Introduces all jobs into the system • Handles scheduling of JCL Conversion/Interpretation (C/I) • Pre-execution setup of JES3 managed devices • Schedules jobs to all main processors (locals) • Has awareness of all jobs in execution • Handles scheduling of SYSOUT data sets for writers • Manages space on the shared-spool devices • Any Local can become a Global with a Dynamic System Interchange (DSI) 8 JES3 Spool Management 8 JES Structure • JES address space • Main task • Sub-dispatched (shared) with multiple processes • Subtasks to perform tasks that must MVS wait • Auxiliary address space to own processes/objects • Allows JES address space to fail yet JES functions continue • JESXCF services • Provide XCF communications between address spaces • Primary communication between JES3 global and locals • Mainly used for enquiry/posting function for JES2 • Manages status of JES address spaces • Notifies other members of a JES failure 9 JES3 Spool Management 9 JES2 Conversion Processing • Converts JCL into internal format needed to run job • JES2 calls MVS converter in the JES2 address space • PCE selects job and sets up environment • Subtask used to call z/OS converter • JCL interpretation occurs when job executes in target address space • Certain JCL error not detected until job is in execution • Converter parms (defaults) based on JOBCLASS • Journal, BLP, SMF exits, PROCLIB, region, SWA ABOVE, etc • TYPERUN=SCAN just performs conversion processing • Errors discovered during interpretation not detected 10 JES3 Spool Management 10 JES3 Converter/Interpreter (C/I) • C/I takes place in the JES3 global address space (C/I DSP) or can be offloaded to C/I FSSes. • JES3 C/I invokes the MVS C/I function to process the JCL. • JCL interpretation is done immediately after conversion. • In the C/I DSP or FSS rather than after job selection in an initiator. • Can provide quicker feedback of JCL errors. • Converter parms (defaults) set from CIPARM statement based upon the input device. • Journal, BLP, SMF exits, PROCLIB, region, SWA ABOVE, etc • TYPRUN=SCAN will also invoke the MVS interpreter. • Parameter and specification errors can be detected and corrected before a job is submitted for execution. 11 JES3 Spool Management 11 Functional Subsystems (FSS) Writers • Interface to offload function to separate address spaces • Reduces workload on JES main task • Original use for printer/writer support • Removes printer “driver” knowledge from JES and associates them with FSS software • JES managed interface • Controlled by JES commands 12 A functional subsystem (FSS) is a collection of programs residing in an address space separate from JES that communicates with JES to provide a JES-related function, such as print processing and converter/interpreter (C/I) processing for JES3. An FSS extends the scope of JES processing. Because an FSS operates in its own address space, it functions independently of JES in several areas. An FSS is responsible for: • The management of storage resources that it needs during data set processing including print buffers. • Its own recovery and serviceability. • Its performance and accounting measurements. • The security of its own resources. JES and the FSS communicate through the functional subsystem interface (FSI) and SSI. The FSI is a one level interface which provides two way communication. The FSI
Load more

Recommended publications
  • Syncsort for Z/VSE Programmer's Guide Release
    All rights reserved. This document contains proprietary and confidential material, and is only for use by licensees of the SyncSort for z/VSE proprietary software system. PROVEN performance SyncSort for z/ VSE Programmer's Guide Release 3. 7 SI-0328-G SyncSort is a registered trademark of Syncsort Incorporated 070809 © Syncsort Incorporated, 2009 All rights reserved. This document contains proprietary and confidential material, and is only for use by licensees of the SyncSort proprietary software system. This publication may not be reproduced in whole or in part, in any form, except with written permission from Syncsort Incorporated. SyncSort is a trademark of Syncsort Incorporated. All other company and product names used herein may be the trademarks of their respective companies. Table of Contents Summary of Changes . v Performance Improvements . v Data Utility Features. v Operating System . vi Messages. vi Chapter 1. Introduction . 1.1 An Introduction to SyncSort for z/VSE. 1.1 SyncSort’s Basic Functions . 1.1 SyncSort’s Data Utility and SortWriter Features . 1.2 Join Processing Sequence . 1.5 Sample SortWriter Report. 1.6 SyncSort’s Operational Features. 1.7 Structure of the Programmer’s Guide. 1.7 Related Reading. 1.9 Chapter 2. SyncSort Control Statements . 2.1 Control Statement Summary Chart . 2.3 Data Utility Processing Sequence. 2.17 Maximum Record Length Allowed . 2.23 Control Statement Examples . 2.25 Rules for Control Statements . 2.25 ALTSEQ Control Statement . 2.30 ANALYZE Control Statement. 2.32 DUPKEYS Control Statement . 2.33 Table of Contents i END Control Statement. 2.38 INCLUDE/OMIT Control Statement .
    [Show full text]
  • Introduction-To-Mainframes.Pdf
    Mainframe The term ‘MainFrame’ brings to mind a giant room of electronic parts that is a computer, referring to the original CPU cabinet in a computer of the mid-1960’s. Today, Mainframe refers to a class of ultra-reliable large and medium-scale servers designed for carrier-class and enterprise-class systems operations. Mainframes are costly, due to the support of symmetric multiprocessing (SMP) and dozens of central processors existing within in a single system. Mainframes are highly scalable. Through the addition of clusters, high-speed caches and volumes of memory, they connect to terabyte holding data subsystems. Mainframe computer Mainframe is a very large and expensive computer capable of supporting hundreds, or even thousands, of users simultaneously. In the hierarchy that starts with a simple microprocessor at the bottom and moves to supercomputers at the top, mainframes are just below supercomputers. In some ways, mainframes are more powerful than supercomputers because they support more simultaneous programs. But supercomputers can execute a single program faster than a mainframe. The distinction between small mainframes and minicomputers is vague, depending really on how the manufacturer wants to market its machines. Modern mainframe computers have abilities not so much defined by their single task computational speed (usually defined as MIPS — Millions of Instructions Per Second) as by their redundant internal engineering and resulting high reliability and security, extensive input-output facilities, strict backward compatibility with older software, and high utilization rates to support massive throughput. These machines often run for years without interruption, with repairs and hardware upgrades taking place during normal operation.
    [Show full text]
  • IBM Z Open Automation Utilities Provides New Services to Help Developers Work with IBM Z/OS Data Sets Directly from the Shell, Java, Or Python
    IBM United States Software Announcement 220-087, dated February 18, 2020 IBM Z Open Automation Utilities provides new services to help developers work with IBM z/OS data sets directly from the shell, Java, or Python Table of contents 1 Overview 3 Technical information 2 Key requirements 3 Ordering information 2 Planned availability date 5 Terms and conditions 2 Program number 9 Prices 2 Publications 9 Order now At a glance IBM Z(R) Open Automation Utilities helps z/OS(R) developers to automate tasks that access z/OS resources. It enables easier calling of z/OS utilities compared with JCL by providing a natural coding experience on UNIX System Services (USS) and interfaces in modern programming languages. Overview Job Control Language (JCL) has been used for a long time for performing or automating a set of steps on the IBM(R) z/OS operating system. Though JCL has evolved with the times, it is inevitably foreign to people familiar with environments such as Linux(R), UNIX, and Microsoft Windows. On z/OS, as an alternative to using JCL, developers can write scripts to automate tasks in the USS environment. Such scripts are easier to understand and to manage, and many open source tools are also available in USS. However, there is a gap in some cases, and z/OS developers have to fall back to submitting JCL jobs, which requires z/OS specific knowledge. In addition, JCL jobs are asynchronous, which means you must submit them to batch and wait for the result; thus, they do not fit in well with the rest of the script, which is typically synchronous.
    [Show full text]
  • 9228 Brown/JCL 01.K.Qxd 5/1/02 11:39 AM Page 1
    9228 Brown/JCL 01.k.qxd 5/1/02 11:39 AM Page 1 CHAPTER 1 INTRODUCTION 1.1 THE SHOCK OF JCL Your first use of JCL (Job Control Language) will be a shock. No doubt you have used personal computers costing $500 or $1,000 that had wonderfully human-engineered software, giving you an expectation of how easy it is to use a computer. Now, as you use a computer costing several million dollars, you may feel like a waif in a Dickens story standing in the shadow of a mas- sive mainframe computer saying meekly, “Please, sir, may I run my job?” It will come as a shock that its software is not wonderfully human engi- neered. The hardware and software design of large IBM mainframe computers date back to the days when Kennedy was president. JCL is a language that may be older than you are. It was designed at a time when user-friendliness was not even a gleam in the eye of its designers. This is easily demonstrated by taking the simple task of copying a file and contrasting how it is done through JCL with how it is done on the most popular personal computer system, Windows. To copy a file with Windows, you left-click twice on the MY COMPUTER icon, left-click on the C: drive icon, left-click twice on the folder containing the file, and right-click on the file to copy. On the resulting menu, you click on COPY and then left-click twice on the folder into which you want the file copied.
    [Show full text]
  • Basic of Mainframe
    Basic of Mainframe Mainframe computer Mainframe is a very large and expensive computer capable of supporting hundreds, or even thousands, of users simultaneously. In the hierarchy that starts with a simple microprocessor at the bottom and moves to supercomputers at the top, mainframes are just below supercomputers. In some ways, mainframes are more powerful than supercomputers because they support more simultaneous programs. But supercomputers can execute a single program faster than a mainframe. The distinction between small mainframes and minicomputers is vague, depending really on how the manufacturer wants to market its machines. Modern mainframe computers have abilities not so much defined by their single task computational speed (usually defined as MIPS ² Millions of Instructions Per Second) as by their redundant internal engineering and resulting high reliability and security, extensive input- output facilities, strict backward compatibility with older software, and high utilization rates to support massive throughput. These machines often run for years without interruption, with repairs and hardware upgrades taking place during normal operation. Software upgrades are only non-disruptive when Parallel Sysplex is in place, with true workload sharing, so one system can take over another's application, while it is being refreshed. More recently, there are several IBM mainframe installations that have delivered over a decade of continuous business service as of 2007, with hardware upgrades not interrupting service. Mainframes are defined by high availability, one of the main reasons for their longevity, because they are typically used in applications where downtime would be costly or catastrophic. The term Reliability, Availability and Serviceability (RAS) is a defining characteristic of mainframe computers.
    [Show full text]
  • Unisys IBM Mainframe Security - Part 2
    ProTech Professional Technical Services, Inc. Unisys IBM Mainframe Security - Part 2 Course Summary Description This course is intended for individuals who need an initial, introductory understanding of IBM's mainframe operating system z/OS and the mainframe security software product Resource Access Control Facility (RACF). It is specifically designed to give attendees a solid foundation in z/OS and RACF without overloading them with advanced technical topics, yet it also serves as the ideal springboard for acquiring Course Outline Course further skills and knowledge. Attendees will gain a fundamental understanding of the components and functions of z/OS and RACF. Objectives After taking this course, students will be able to understand: What z/OS is and what functions it performs The software components of z/OS How to use TSO and ISPF Coding and submitting batch jobs What RACF is and what functions it performs The contents of each type of RACF profile What groups are and how they are used Protecting datasets and general resources How RACF decides whether to grant access Topics Introduction to z/OS Groups Time Sharing Option (TSO) Resource Protection Batch Job Control Language (JCL) Datasets Introduction to RACF General Resources Users RACF Administration Audience This course is designed for anyone requiring general, introductory knowledge of z/OS and RACF. Including; Entry-level security administrators Compliance staff Non-mainframe IT security administrators IT Auditors IT Security Supervisors Prerequisites There are no prerequisites for this course. Duration Two days Due to the nature of this material, this document refers to numerous hardware and software products by their trade names.
    [Show full text]
  • White Pape Product Review
    productwhite pape reviewr Micro Focus Studio Enterprise Edition Test Server Micro Focus Studio Enterprise Edition™ Test Server (Test Server) is a testing suite that supports pre-production testing of mainframe applications on commodity Windows platforms before they are deployed back to the mainframe for production use. PRODUCT REVIEW | Micro Focus Studio Enterprise Edition Test Server OVERVIEW Micro Focus Test Server is a fast, scalable testing environment that enables organizations to perform substantial pre- production testing of IBM mainframe applications on more cost effective Windows servers, while still deploying these back to the mainframe for final system test and release into production. Test Server is a multi-tasking, multi-user transactional and batch testing platform that supports IBM COBOL, IBM Assembler, IBM CICS, IBM IMS (TM and DB) and IBM JCL, IBM DB2, IBM z/OS file formats and SORT utilities on Windows. This means that substantial and complex mainframe applications can be comprehensively tested under Test Server without being constrained by the availability of mainframe resources. Test Server is supplied with the development tools required to compile or assemble mainframe programs as well as data access tools to support the creation or modification of vital test data. It can also be configured so that code and data can, where logical, continue to reside on the mainframe and be executed remotely from the Test Server platform. BENEFITS Complete testing phases faster and with high quality as test cycles are not constrained
    [Show full text]
  • Job Control Language
    JCL Job Control Language im z/OS-Umfeld praktisch anwenden von: Markus Karl Scheibe Informatik-/Betriebswirt (VWA) Nachtigalstr. 10 30173 Hannover Tel.: 0173/6181348 1 Inhaltsverzeichnis 1. Einleitung………………………………………………………………………………….9 1.1. Verarbeitungsmethoden………………………………………………………...….9 1.2. Was ist ein (MVS-)Betriebssystem………………………………………………..9 1.3. Der Katalogeintrag………………………………………………………...………10 1.4. Was ist JCL?..................................................................................................11 1.5. JCL im Vergleich zu anderen Programmiersprachen………………………….11 2. Job-Aufbau………………………………………………………………………………13 2.1. Job-Spezifikation…………………………………………………………………..13 2.2. Arbeitsabläufe……………………………………………………………………...13 2.3. Arbeitsmittel………………………………………………………………………...14 2.4. Der erste Job……………………………………………………………………….15 2.5. Umfeld der JCL…………………………………………………………………….17 2.6. Job Entry Subsystem……………………………………………………………...17 3. JCL in der Praxis………………………………………………………………………..18 3.1. Stepabfolge…………………………………………………………………………18 3.2. DSNAME……………………………………………………………………………18 3.3. DISP…………………………………………………………………………………22 3.3.1. Status………………………………………………………………………...23 3.3.1.1. NEW………………………………………………………………….23 3.3.1.2. OLD…………………………………………………………………..23 3.3.1.3. SHR…………………………………………………………………..23 3.3.1.4. MOD………………………………………………………………….23 3.3.2. Normal Termination………………………………………………………...24 3.3.2.1. DELETE……………………………………………………………..24 3.3.2.2. KEEP…………………………………………………………………24 3.3.2.3. PASS…………………………………………………………………24 3.3.2.4. CATLG……………………………………………………………….24 3.3.2.5.
    [Show full text]
  • Brief Intro to Mainframe and Z/OS Administration
    Brief Intro to Mainframe and z/OS Administration By Luis F. Bustamante What is a mainframe? What is a mainframe? What is a mainframe? • Developed in 1950s • First mass-produced digital, all-transistorized, business computer that could be afforded by many businesses worldwide. • 1st general purpose computers • Designed with business applications in mind What is a mainframe? • Market dominated by IBM (90%+) – Made in Poughkeepsie, NY • Large-Scale computing • Large Enterprises • z Architecture (not x86 or x64) • Run various Operating Systems – z/OS – z/VM – Linux What is a mainframe? • Runs Multiple OS instances - LPAR • Serves tens of thousands of users • Manages petabytes of data • Very reliable • Used for Mission Critical Applications • Expensive (Cost Savings from Consolidation) • Scalable (After initial investment) • Highly secure • Large Data processing • Central data repository What is a mainframe? Typical Mainframe Workloads Batch Workload •Reports •Data consolidation •Billing •Account statements •Data Analytics Transactions • Quick interactions - Seconds, or fractions of seconds • Millions/billions transactions per day • Thousand of concurrent users • Require high availability • Examples: – Banks: ATM, Tellers, Financial Records – Airline reservations – Inventory control – Government: Tax processing, license issuance and management Transactions • Usually under CICS in z/OS: • CICS – Transaction Server – HTTP (REST, SOAP) – Web – Java – Cobol – C/C++ Roles in the Mainframe World Who uses mainframes? • 80% of fortune 500 companies • Banking • Finance • Health care • Insurance • Public utilities • Government What is z/OS? • Most common mainframe OS • EBCDIC (Extended Binary Coded Decimal Interchange Code) character set as opposed to ASCII • Implements POSIX compliant UNIX kernel to run UNIX type applications. • All kinds of workloads: – COBOL: usually legacy applications – Web services/interfaces.
    [Show full text]
  • Job-Control Languages
    JOB-CONTROL LANGUAGES WHAT ARE THEY ? A language is a means of conveying information to somebody or something; it doesn't have to be text or speech, or even necessarily be parsable into words and sentences. Many deaf people can communicate very effectively by signing; at a very much lower level of sophistication, we all communicate by body language. In computer terms, many programming languages, including traditional job-control languages, are expressed in textual forms which depend strongly on our experience of using language in everyday life : they are formalised versions of written English ( usually, for historical reasons, but any language would do ). As well as that, though, we communicate with computers through menus, WIMP interfaces, touch screens, pen interfaces, and so on. These are effective languages too; there is clearly a lot more to be said about computer languages than is accounted for by the Chomsky hierarchy. ( Chomsky is a linguist, but concerned essentially with the development of conventional language. ) These other languages can be seen as more akin to manual sign languages than to written and spoken English. Here, we shall try to cover all the main sorts of Job-Control Language ( or JCL ), so we'll certainly fail. That includes textual and WIMP languages, and both interactive control of the system and control through command files. Try looking for gaps in our arguments, such as they are, and fill them in from your own experience. There's no prize, but if you find anything interesting, we'd be happy to hear about it. WHERE DID THEY COME FROM ? They were originally monitor control cards.
    [Show full text]
  • UNIX System Servicesuser's Guide
    z/OS Version 2 Release 3 UNIX System Services User's Guide IBM SA23-2279-30 Note Before using this information and the product it supports, read the information in “Notices” on page 321. This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2019-02-16 © Copyright International Business Machines Corporation 1996, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents List of Figures...................................................................................................... xv List of Tables......................................................................................................xvii About this document...........................................................................................xix Who should use z/OS UNIX System Services User's Guide?....................................................................xix What is in z/OS UNIX System Services User's Guide?........................................................................ xix Tasks that can be performed in more than one environment.............................................................xix z/OS information.................................................................................................................................. xix How to send your comments to IBM.....................................................................xxi If you
    [Show full text]
  • 83 Ztidbits(Zos Batch UNIX)
    You can access z/OS UNIX services from batch, TSO/E, or ISPF. This issue targets highlights of batch. • MVS job control language (JCL) to run shell scripts or z/OS UNIX application programs as batch (background) jobs. Aliases for BPXBATCH BPXBATSL, BPXBATA2, and BPXBATA8 are provided as aliases for BPXBATCH that use a local spawn - Executable files in batch. An executable file is any file that can be run as a program. An executable file can be a to run in the same address space. load module (which is a member of a PDS), a program object (which is either a member of a PDSE or a file in the BPXBATSL BPXBATSL performs a local spawn, but does not require resetting of environment variables. z/OS UNIX file system), or an interpreted file (such as a REXX EXEC). BPXBATSL behaves exactly like BPXBATCH and allows local spawning whether the current environment is set up or not. - For a file to be treated as an executable file, it must have execute permission allowed for the invoker. BPXBATA2 and BPXBATA8 BPXBATA2 and BPXBATA8 are provided as APF-authorized alternatives to BPXBATSL. • BPXBATCH, a utility that can do the following: – Run executable files in batch. BPXBATA2 and BPXBATA8 provide the capability for a target APF-authorized z/OS UNIX program to run in the same address space – Run shell commands and executable files from the TSO/E READY prompt. as the originating job, allowing it to share the same resources, such as allocations and the job log. JCL support for z/OS UNIX JCL data definition (DD) statements use a data definition name (ddname) to specify the data A smarter Defining standard input, output, and error streams for BPXBATCH to be used by the program that you are submitting as a batch job.
    [Show full text]