System/360 Disk Operating System User's Guide: Control Statement Techniques

System/360 Disk Operating System User's Guide: Control Statement Techniques

File No. S360-50 GC20-1685,.Q System/360 Disk Operating System User's Guide: Control Statement Techniques This publication provides guidance in the use of control statements as related to compilations, linkage editing, utilities, sorts, -and user programs. It presents tested examples with supporting explanations as an aid to under­ standing the input stream requirements for processing in the System/360 Disk Operating System environment. The control statements discussed are job control statements, linkage editor control statements, and operator commands. A list of related publications appears in the Preface. PREFACE supplements the data discussed in classes and related SRL publications by bringing it together in The objectives of this publication are: functional form. 1. To bring into perspective for the new user the The examples were tested on system release 9; Disk Operating System job stream requirements changes through system release 12 were reviewed 2. To furnish typical job stream examples and to assure validity of the information. reference data covering the normal processing Related publications are: needs of the DOS user 1. IBM System/360 Disk Operating System: Job stream examples are presented in building System Control and System Service Programs block fashion. Each new type of statement is (C24-5036) discussed when it is first used; only unusual 2. mM System/360 Disk Operating System: circumstances are pointed out in succeeding Operating Guide (C24-5022) examples. To simulate an installation environment, 3. mM System/360 Disk and Tape Operating a specific System/360 machine configuration and Systems: Utility Programs Specifications DOS system generation are assumed. The List of (C24-3465) Examples provides quick reference to specific job 4. ruM System/360 Disk Operating System: stream examples and discussions pertinent to a Sort/Merge Program Specifications (C24-3444) given control statement type. Appendices furnish 5. mM System/360 Disk and Tape Operating statement summary data. System: Tape Sort/Merge Program No attempt has been made to cover all Specifications (C24-3438) possibilities, but rather to present sufficient 6. mM System/360 Disk Operating System: information through a number of examples to enable Autotest Specifications (C24-5062) the user to modify an example for his particular 7. ruM System/360 Reference Data: TOS/DOS needs or to create his own job stream. The manual Job Control Statement and Operator does not take the place of formal training, but Communication (X20-1748) First Edition (Reprinted December 1969) Copies of this and other IBM publications can be obtained through IBM branch offices. A form is provided at the back of this publication-for . reader's comments. If the form has been removed, comments may be addressed to IBM Corporation, Technical Publications Department, 112 East Post Road, White Plains, N.Y. 10601. © International Business Machines Corporation 1967 CONTENTS The Utility Programs ................ 36 General Considerations . 36 Introduction 1 Logical Unit Assignments ......... 36 Background vs Foreground Programs . 1 Program Names ............... 36 System Flow . 1 Labels ...................... 36 I/O Device Assignment ............. 4 UPSI Statement ................ 36 Assumed Disk Resident System Preparation of Job Stream Input on Tape Configuration ................. 4 or Disk (Examples 11 and 12) ...... 38 The Input Stream -- Batched Programs .... 6 Operating Considerations ......... 41 Job Control Input ................. 6 Linkage Editing (Examples 13 to 18) ...... 42 Job Control Statements ........... 6 System Flow ................... 42 Job Control Commands ........... 6 Symbolic Units Required and Program Linkage Editor Control Statements ... 7 Name ....................... 44 Data. Input ...................... 7 Linkage Editor Control Statements ..... 44 ATTN Input . ' ................... 7 ACTION Statement .............. 44 Compile ......................... 8 PHASE Statement .............. 44 General Cons iderations . 8 INCLUDE Statement ............. 45 Required Symbolic Logical Unit ENTRY Statement .............. 45 Assignment ................. 8 LBLTYP Job Control Statement ..... 45 Program Names ............... 8 Summary of Considerations for LINK Single Compilation, SYSRDR and SYSIPT and CA TA L Options . 57 Combined (Example 1) ........... 8 Loading the Universal Character Set JOB Statement ................ 8 Buffer (Example 19) ............... 57 EXEC Statement ............... 8 UCS Job Control Command .......... 57 PAUSE Statement or Command ...... 8 Foreground Initiation (Example 20) ....... 60 * Comments Sta.tement ........... 9 General Considerations ............. 60 /* End of Data File Statement ...... 9 Allocation of Partitions ........... 60 /& End-of-Job Sta.tement ......... 9 Linkage Editing . 60 Multiple Compilations, SYSRDR and Symbolic Unit Assignments ........ 60 SYSIPT Combined (Example 2) ...... 11 Dumping Main Storage ........... 60 OPTION Sta.tement .............. 11 Labels ...................... 60 Multiple Compilations, SYSRDR and Foreground Initiation Process ......• 60 SYSIPT Separate (Example 3) .... , .. 13 Description of Commands ........... 61 ASSGN Sta.tement or Command ...... 13 STOP Command -- Job Control ..... 61 RESET Sta.tement or Command ...... 14 START Command --ATTN ........ 61 LISTIO Sta.tementor Command ...... 16 READ Command -- Foreground MTC Sta. tement or Command . .. 16 Initiation (FI) ............... 61 CLOSE Command .............. 17 ASSGN Command -- FI ........... 61 Sta.ndard Tape and DASD Labels HOLD Command -- FI or Job Control .. 62 (Examples 4 to 10) .............. ; .. 19 RELSE Command -- FI or Job Control .. 62 Physical Labels •.................. 19 UNA Command -- FI or Job Control .. 62 DASD Files .................. 19 Label Commands -- FI .......... 62 Tape Files ................•... 19 EXEC Command -- FI ........... 62 System Flow . .. 20 Appendix A. Standard Volume Label, Label Storage ................. 20 Tape or DASD . .. • . 66 Label Processmg ............... 20 Appendix B. Standard DASD File Labels, Main Storage Usage . 23 Format 1 ...................... 67 Description of Job Control Label Appendix C. Standard Tape File Label .... 70 Statements ................... 23 Appendix D. Tape Files with Standard VOL Statement ................ 23 Labels ........................ 71 TPUB Statement .............. 24 Appendix E. Summary of Job Control and DUB Statement ............... 24 Operator Communication Statements ..... 72 XTENT Statement .............. 25 Appendix F. Symbolic Unit Names . .. 74 TLBL Statement ............... 25 Appendix G. Symbolic Units Required for Summary of DASD File Location IBM -Supplied Programs . .. 75 Considerations ................. 26 FIGURES 1. System Flow Schematic ........... 2 2. Assumed Disk Resident System Configura tion . 5 3. Job Termination Schematic. 15 4. Tape and DASD Label System Flow. 21 5. Tape and DASD Label Storage Record Formats ..................... 22 6. Link-Edit System Flow Schematic 43 EXAMPLES 1. Single Compilation, SYSRDR and SYSIPT Combined . 10 2. Multiple Compilations, SYSRDR and SYSIPT Combined . 12 3. Multiple Compilations, SYSRDR and SYSIPT Separate . 18 4. Standard Label Storage. 28 5. Sequential Disk File Labels, Single Drive . .. 30 6. Sequential Disk File Labels, Multiple Drives. 31 7. Direct Access File Labels ......... 32 8. Index Sequential File Labels, Load Create. 33 9. Index Sequential File Labels, Other than Load Create. 34 10. Standard Tape Labels, Multivolume File with Alternate Assignments. 35 11. Creation of SYSIPT on Tape ........ 38 12. Creation of SYSIN on Disk ......... 40 13. Link Edit and Execute ............ 46 14. Catalog to Core Image Library ...... 48 15. Compile and Execute .. 50 16. Catalog for Phase Overlay ......... 52 17. Submodular Structure . 54 18. Self-Relocating and Multiple Link Edits. 56 19. Catalog UCS Buffer Images and Load Buffer . 58 20. Foreground Initiation. 64 INTRODUCTION Al1 IBM -supplied programs operate only as background programs. These include the language BACKGROUND VS FOREGROUND PROGRAMS translators (Assembler, COBOL, FORTRAN, PL/I, RPG), the system service programs The IBM System/360 Disk Operating System is (librarian, linkage editor), the service programs designed to handle two types of problem programs: (sorts, utilities, Autotest), and job control. In backgroWld and foregroWld. BackgroWld programs addition, Autotest requires a dedicated (no are initiated by job control from the batched job foreground partitions) system. input stream. ForegroWld programs are initiated Programs using the utility input/output macros by the operator from the printer-keyboard. A can operate as either backgroWld or foreground foregroWld initiator (in lieu of job control) interprets programs. the operator foregroWld initiation commands. ForegroWld programs do not execute from a stack. SYSTEM FLOW When one foregroWld program is completed, the operator must explicitly initiate the next program. The system flow schematic is shown in Figure 1- The system is capable of concurrently operating Because the IBM System/360 Disk Operating one background program and one or two foreground System is disk-resident, operation of the system programs. BackgroWld and foreground programs is initialized through an initial program load (IPL) initiate and terminate asynchronously from each procedure from the resident disk. The IPL loader other. Neither is aware of the other's existence. is loaded into main storage from the resident disk

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    84 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us