OS/VS2 HASP II Version 4 System Programmer's Guide

OS/VS2 HASP II Version 4 System Programmer's Guide

GC27-6992-0 File No. 5370-36 OS/VS2 HASP II Version 4 Systems System Programmer's Guide Program Number 370H-TX-001 VS2 SVS Release 1.7 Page ofGC27-{;992~ Revised September IS, 1976 By TNL GN27-ISS3 PREFACE This publication consists of self-contained chapters, each of whic,h provides information necessary to generate, install, and implement capabilities of the HASP program. It is designed primarily for system programmers responsible for generating, maintaining, and extending HASP features. Topics: OS SYSGEN Requirements Generating a HASP System (HASPGEN) HASPGEN Parameters Installing HASP in the System Generating HASP Remote Terminal Programs (RMTGEN) Remote Generation for Non-HASP Users RMTGEN Parameters Storage Requirements Reference Listing of HASPJCL Internal Reader HASP-TSO Interface Execution Batch Scheduling Generating More Than Fifteen Logical Partitions Multiple Devices on MULTI-L~VING Remotes HASP 2110 and 3180 RJE Support 3211 Forms Control Buffer Additional Loads HASP-SMF Interface General HASP Restrictions I HASP OVerlay Programming Rules RELATED PUBLICATIONS • IBM 3800 Printing Subsfstem Programmer's Guide for OS/VS2 SVS, GC26-3859, wh~ch conta~ns information on the 3800 for both system programmers and application programmers • • OS/VS2 HASP II Version 4 User's Guide, GC27-0052, which contains information for the programmer who uses HASP. Firat Edition (MArch, 1973) This edition, Aa amended by technicAl newsletters GN25-0121 And GN27-1553, Applies to HASP II Version 4.1 in support of OS/VS2 ReleAse 1.7 and to Any subsequent versions of HASP and releasea of SVS unless otherwise indicAted in new editions or technicAl newslettera. Information in thia publication is subject to signifiCAnt chanqe. Before usinq this publicAtion, consult the lAteat IBM System/370 Biblio9rihhY, GC20-0001, and the technical newsletters that amend e biblioqraphy, for the editiona that are applicable and current. Requests for copies of IBM publications should be made to your IBM representative or to the IBM brAnch office servinq your locality. Forms for readers' comments are provided at the back of this publication. If the forms have been removed, comments may be addressed to I~ Corporation, P. o. Box 50020, Proqramminq Publishinq, San Jose, California 95150. e copyriqht InternAtional Business Machines Corporation 1973 Page of GC27-6992"{) Revised September 15, 1976 By TNL GN27-1553 Contents OS SYSGEN Requirements • • • • • • • • 5 Pseudo Devices • • • • 5 Additional Symbolic Unit Names • 5 Installation Of The HASP SVC • _. ._ 6 Generating A HASP System (HASPGEN) -. 7 Data set Requirements For HASPGEN 7 HASPGEN Parameter Cards • • • • • 11 HASPGEN Update Cards • • • • • • • • 11 standard Complete HASPGEN Process 13 HASPGEN Completion Codes • • • 14 some HASPGEN variations • • • • • • • • • • • • • • 16 Compatible HASP SPOOL Volumes •• • • 20 HASPGEN Parameters ••• • • • • • • . 21 IBH 3800 HASPGEN PARAMETERS •••••••••••• 80 FCBs for the 3800 Printing Subsystem .•••• 80. 1 Installing HASP In The system • 81 Installing HASP SVC 81 Installing HASP Procs • • • • • • 81 Member HASP • • • • • 81 Member HOSRDR • • • • • 82 Installing HASP Program • • • • 82 Allocating SPOOL Direct-Access Space • 83 Generating HASP Remote Terminal Programs (RMTGEN) 85 HASPGEN Preparations For RMTGEN • • • • • • • • 85 Initial HASP RMTGEN Run (~erformed As Part of HASPGEN) 87 Batch HASP Remote Terminal Program Generation Run 87 RMTGEN Program Execution • • • • • • • •• 89 RMTGEN Input Card Specifications • • • • 90 RMTGEN Control Cards • 90 User Options • • • • _ 91 Update Control Cards • 92 Update Cards • • • • • 92 System/3 96-Column Card RMTGEN Output 92 RMTGEN Completion Codes • • • • 94 Remote Generation For Non-HASP Users 96 Preparation • • • • • • • • 96 Executing RMTGEN • • • • • • • • • • • 97 RMTGEN Parameters • • • • • • • • • 98 RMTGEN Parameters For System/360 Model 20 BSC • • • • 98 RMTGEN Parameters For System/360 (Except Model 20) BSC • 106 RMTGEN Parameters For 1130 •••••• 114 RMTGEN Parameters For 1130 LOader •••• 120 RMTGEN Parameters For System/3 • • • 122 RMTGEN Parameters For 2922 • • • • • • 130 Storage Requirements • • • • • • • • 131 Additional Nucleus storage Requirements 131 Additional LSQA Storage Requirements • 131 HASP Module storage Requirement 131 storage Requirement For A 'I'ypical HASP 134 HASP Fixed storage Requirement • • • • • • 135 HASP Region Requirement 136 Reference Listing Of HASPJCL • • • • 137 Sample Job HASPSVC •• 137 Sample Job HASPROCS 138 Sample Job HASP HASP 139 Sample Job HASPOOLS 140 Internal Reader • • • • • 141 Procedure For Using The HASP Internal Reader • 141 1 Page of GC27-6992-O Revised September 15, 1976 By TNL GN27-1553 JCL Considerations • • • • • • • • • • • • • 141 as SYSGEN Considerations • • • • • • • • • • • • • • 141 Deletion Of Current Job On Reader •••• • • • • • .• • 142 Tape Input To HASP Using The Internal Reader • • • • • 142 HASP-TSO Interface • • • • • • • • • • • • 144 Installation Considerations • • • • • • 144 Interface Usage • • • • • • • • • • 144 Execution Batch Scheduling • • • • • • • 147 Batch Processing Program Characteristics • 147 submission Of Batch Jobs • • • • • 148 Batch scheduling Process • • • • • • • • • • • • 148 Installing Batch scheduling •• • • • • • 149 Generating More Than Fifteen Logical Partitions • • • • • 151 Multiple Devices On MULTI-LEAVING Remotes • • • • • 153 HASP 2770 And 3780 RJE Support • • • • • • • • 155 2770 Configuration • • • • 155 I/O Formats • • • • • • • • • • • • • 155 Input 155 Output • 156 3780 Support • • 158 3211 Forms Control Buffer,Additional Loads 159 Adding And Changing FCB Loads • • • • 159 FCB Loads Provided By HASP • • • • • 159 Recommended Card Sequence Numbers. 160 HASP-SMF Interface • • • • • 161 BASPGEN Considerations • • • • • 161 SMF Considerations • • • • • • • 162 General HASP Restrictions • • 164 Unsupported as Features • • • • • • • 164 HASP-Function/Feature Restrictions • • 165 HASP Overlay Programming Rules ••• 1 66. 1 Creating Overlay Control Sections 166. 1 Calling Overlay Routines • • • • . 166.2 Coding While Using Overlay Routines . • 1 66.3 2 Illustrations Figure 1. BASPGEN Data Set Description ••••••• 8 Figure 2. Sample Job To Catalog Data Sets For HASPGEN 10 Figure 3. Sample HASPGEN Parameter And Update Deck 12 Figure 4. HASPGEN Tape First File Job Description • • 15 Figure 5. sample Batch HASPGEN Jobs • • • • • • • • • 17 Figure 6. Module Dependencies On HASPGEN Parameters 19 Figure 7. RMTGEN Data Sets • • • • • • • • • • • • • 86 Figure 8. Example Of Batch RMTGEN Run • • • • • • • • 88 Figure 9. RMTGEN Terminal Program Identification Cards ••• . 93 Figure 10. Sample Use of HASP Internal Reader For Tape Input • 143 Figure 11. sampl~ TSO Command Procedure For Output To HASP 146 Figure 12. sample Update For Eighteen Logical Partitions • 152 Figure 13. Sample JCL For Generating Second Printer And Reader • • • • • • • • • • • • • • • • • • 154 3 OS:SYSGEN REQUIREMENTS The only OS SYSGEN requirements for HASP are pseudo device generation and UNITNAME assignments. These mandatory SYSGEN requirements and other SYSGEN options are discussed in the following subsections. PSEUOO DEVICES Pseudo readers, printers and punches should be generated according to the following formulas: Number of pseudo 2540 readers = INOD*'MAXXEQS+1 Number of pseudo 1403 printers = PRDD*'MAXXEQS+1 Number of pseudo 2540 punches = PUOO*'MAXXEQS Number of pseudo 2520 punches = 'NUMINRS where: INDD = maximum number of DD • (or DD DATA) cards per job step PROD = maximum number of print data sets per job step PUOD = maximum number of punch data sets per job step 'MAXXEQS = maximum number of simultaneous job executions 'NUMINRS = number of Internal Reader interfaces. Note that the term "pseudo device" implies a physically nonexistent device. An address chosen for a pseudo device may be any device address acceptable to OS, but it should not match the address of any existent device or other pseudo device. Since the allocation of pseudo devices will affect the allocation of other devices on the same channel, it is recommended that all pseudo devices be placed on a nonexistent channel. ADOITIONAL·SYMBOLIC UNIT NAMES The symbolic unit name "A" should be assigned to all pseudo 1403 printers, except the one identified by the HASPGEN parameter 'WTR. The symbolic unit name "B" should be assigned to all pseudo 2540 punches. The symbolic name "R" should be assigned to all pseudo 2540 readers, except the one identified by the HASPGEN parameter 'RDR. OS SYSGEN Requirements 5 Page of GC27-6992-O Revised September 15, 1976 By TNL GN27-1553 The pseudo device and symbolic unit name requirements are satisfied by using the SYSGEN macros IODEVICE and UNITNAME. The following examples give a simple method of generating the required devices and names for OS/VS2: 1. Pseudo 2540 Reader (except 'RDR) IODEVICE UNIT=HASP-2540R,ADDRESS=xxx UNITNAME NAME=R,UNIT=XXX 2. Pseudo 2540 Reader (for 'RDR) IODEVICE UNIT=HASP-2540R,ADDRESS=xxx 3. Pseudo 1403 Printer (except 'WTR) IODEVICE UNIT=HASP-1403,ADDRESS=xxx UNITNAME NAME=A.UNIT=xxx 4. Pseudo 1403 Printer (for 'WTR) IODEVICE UNIT=HASP-1403.ADDRESS=xxx 5. Pseudo 2540 Punch IODEVICE UNIT=HASP-2540P,ADDRESS=xxx UNITNAME NAME=B,UNIT=XXX 6. Pseudo 2520 Punch IODEVICE UNIT=HASP-2520.ADDRESS=xxx The pseudo 2520 punches may be given a descriptive symbolic unit name, as in the following example: UNITNAME UNIT=(301,302 •••• ).NAME=INTRDR This will make allocation easier for programmers using the Internal Reader feature of HASP. INSTALLATION OF

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    192 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