Submitting Mainframe Batch Jobs from PC SAS® Rick Andrews, Centers for Medicare and Medicaid Services, Baltimore, MD

Total Page:16

File Type:pdf, Size:1020Kb

Submitting Mainframe Batch Jobs from PC SAS® Rick Andrews, Centers for Medicare and Medicaid Services, Baltimore, MD NESUG 2006 Applications Submitting Mainframe Batch Jobs from PC SAS® Rick Andrews, Centers for Medicare and Medicaid Services, Baltimore, MD ABSTRACT The SAS System offers a host of mechanisms to interact with remote platforms. This paper discuss’ an application to submit IBM® Mainframe batch jobs from a Microsoft® Windows™ operating system using SAS/AF®, SAS/Connect®, and the Internal Reader. These tools can create applications that keep track of each job, log, and output and send email when all is complete. This provides avenues for individuals without experience on the “Big Iron” (mainframe) to submit programs with little to no knowledge of IBM’s Job Control Language (JCL) or Computer Associate’s (CA) Interactive System Productivity Facility (ISPF). The code shown below was created using version 8.2 of SAS. INTRODUCTION CONTENTS From a user’s perspective, the IBM Mainframe has remained relatively • SAS/AF the same for many years, though newcomers often find learning ISPF • CATALOGS either daunting or archaic. With so many processes and applications • FRAME ENTRIES migrating to Windows and UNIX platforms, recent college graduates are • COMPONENTS unacquainted with maneuvering “Big Blue” (mainframe) because most • PROPERTIES courses are related to the newer operating environments. • BUILD FRAME • PUSH BUTTON CONTROLS The SAS System helps bridge the gap between these new worlds and the old, by way of its application facility called SAS/AF. This robust • SAS COMPONENT LANGUAGE resource offers an object oriented approach that many are unaware even • LABELED SECTIONS exists. The SAS Component Language (SCL) contains many powerful • SUBMIT BLOCKS functions to help build user-friendly front end systems. SAS/Connect is • SAS/CONNECT the channel allowing the link between a Personal Computer (PC) and the • REMOTE SUBMIT powerful “Old Giant”. The Internal Reader is a special program, which • JOB CONTROL LANGUAGE acts like a spawner process for submitting mainframe batch jobs. • INTERNAL READER SAS/AF SAS/AF software provides a set of tools allowing for the creation of applications. It provides interactive interfaces to all of the analysis, presentation, data access and management features of SAS. These applications are stored in SAS catalogs in the form of FRAME entries, which provide visual, object-oriented components for computer environments supporting a graphical user interface (GUI). PROGRAM and MENU entries provide character-based features for systems where a GUI is not available. The SAS Component Language (SCL) entries are for object-oriented programs that interact with Frames. The CBT and HELP entries provide information and assistance to users. This paper will discuss the very basics of creating a PC SAS batch application for submitting mainframe batch jobs. Due to space limitations only an overview of FRAME and SCL entries and the SAS code necessary will be provided. An example application can be downloaded from the website listed in the References section at the end of the paper. Varying mainframe configurations will demand modifications as necessary. 1 NESUG 2006 Applications CATALOG SAS catalogs are special SAS files that store many different kinds of information in smaller units called catalog entries. A single SAS catalog may contain several different types of catalog entries. They can hold application information such as window definitions, formats, informats, macros, or graphics output. 1. Submit a Libname statement in a Program Editor pointing to the Windows folder housing the SAS catalog. 2. Click on the “Sasbatch” folder in the SAS Explorer Library 3. Click on File, New, Catalog, and name the catalog “Batchcat” 4. Click on File, New, Frame 5. Save the untitled frame as “Batch_submit” FRAME ENTRY The Frame entry (or class) is the foundation for graphical SAS applications. The Frame class provides windowing capabilities to all SAS/AF applications and serves as a container for visual controls and non- visual components that create the user interface. The Frame class (or entry) enables the creation of windows and dialog boxes, menu bars or banners, and application help. The SAS/AF development environment consists of four primary windows: - Frame Build Mode is where the GUI is designed - Component window lists available SAS/AF components - Property window is for assigning component attributes - Source window is for writing and compiling SCL code A Frame entry can be opened in Build Mode by double-clicking on the item from the SAS Explorer window. 2 NESUG 2006 Applications COMPONENTS When a Frame entry is open in build mode the Components window displays the objects available to the Frame. These objects are called components. There are two types of components: Controls are visible items on the Frame. These are objects which comprise the GUI. They are represented by an icon in color within the Components window. Models are components not visible on the Frame. They are used to describe data, usually for display by a Control component and are represented by black-and-white icons. PROPERTIES The Properties window provides the ability to assign values to component properties via a selection list or push button at build time of the Frame. The Properties window has two parts: The Properties drill-down tree on the left displays both visual and non-visual components currently on the Frame, as well as the Frame component itself. The Attributes data table displaying the selected component’s properties is on the right hand side of the Components window. This is where values can be modified. BUILD FRAME Open the SAS Explorer and double-click on the Sasbatch library, the Batchcat catalog, and the Batch_submit Frame created earlier. The BUILD procedure can also be used as shown below: 1) proc build catalog=sasbatch.batchcat.batch_submit.frame; run; 2) With the Build window active, click on the Components window button 3) Scroll down to the Text Entry Control and drag it onto the Batch_submit Frame entry. 4) With the Text Entry selected, click on the Properties window button 5) Change the Value of the “name” Attribute to: txt_SasProg Properties Attributes 3 NESUG 2006 Applications PUSH BUTTON CONTROLS 1) Drag the Push Button Control onto the Batch_submit Frame entry 2) Change the “label” Attribute in the Properties window to “Choose Program” 3) Change the “name” Attribute in the Properties window to “SELECT” SUBMIT BUTTON 1) Drag another Push Button Control onto the Batch_submit Frame entry 2) Change the “label” Attribute in the Properties window to “Submit” 3) Change the “name” Attribute in the Properties window to “SUBMITPGM” 4) Save and save often!-) SAS COMPONENT LANGUAGE SCL is a programming language enabling the development of computing applications, from simple programs accomplishing a few tasks to sophisticated, interactive applications using procedures available from other SAS products. The software can create data entry applications displaying tables and menus or sort, merge, manipulate, quantify and communicate tables, charts, graphs, and maps. In earlier releases of SAS software, SCL was called Screen Control Language. Version 7 introduced several new features enabling the design of object-oriented applications. The new name, SAS Component Language, reflects the object-oriented capabilities of the new SCL. SCL programs execute in phases, such as the initialization phase and the termination phase. During each phase, control of the entry can pass to a different segment of an SCL program. The segments of the program are identified by labels; that is, the SCL program is divided into Labeled Sections. INIT: ... SCL STATEMENTS ... RETURN; TERM: ... SCL STATEMENTS ... RETURN; Labeled Sections are program segments that are designed to be called only within the program in which they are defined. They begin with a label and end with a RETURN statement. A label may be one of the reserved labels such as INIT or TERM; it may correspond to a field name, window-variable name, or object name in the application; or it may simply identify a module that is called repetitively, such as a module that sorts data (SAS, 1999). 4 NESUG 2006 Applications RESERVED LABELS INIT: The INIT section is executed before the application window is displayed and is used to initialize variables, import values through macro variables, or open tables. MAIN: The MAIN section is executed each time the user modifies a field in the window and presses ENTER. TERM: The TERM section is executed when the END command is issued. The TERM section might be used to close tables, export values of macro variables, or construct execution statements. CREATE SCL ENTRY 1) Open the Batch_submit Frame 2) Click on the SCL button Opening the SCL entry from the Frame ensures the two entries are “linked” together. SCL PROGRAM The SCL BUILD window looks and acts very much like the SAS Program Editor, though has its own unique vocabulary and syntax. An SCL program consists of one or more SCL statements including keywords, expressions, constants, and operators. The reserved label, INIT, is an example of a keyword, as described above. SCL is the controlling language in a SAS/AF application. When submission of other SAS products is required, the keywords SUBMIT and CONTINUE are used to signify the beginning of SAS procedures and syntax. *---------------------------------------------*; * Initialize SCL Variables *; The INIT section here is designed to ensure the SAS/AF *---------------------------------------------*; window is “zoomed” to its full measure and sets the SCL INIT: variable
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]