C24 5033 7_Disk_Operating_System_System_Generation_and_Maintenance_Apr69 7 Disk Operating System Generation And Maintenance Apr69

C24-5033-7_Disk_Operating_System_System_Generation_and_Maintenance_Apr69 C24-5033-7_Disk_Operating_System_System_Generation_and_Maintenance_Apr69

User Manual: C24-5033-7_Disk_Operating_System_System_Generation_and_Maintenance_Apr69

Open the PDF directly: View PDF .
Page Count: 386

Download
Open PDF In Browser	View PDF

File Number S360-31
Form C24-S033-7

Systems Reference Library

IBM System/360
Disk Operating System
System Generation and Maintenance
This reference publication describes the specifications and
operating procedures for generating an installation-tailored
Disk Operating System. With the IBM-supplied Disk Operating
System and an IBM 2311 Direct Access Storage Device, or an
IBM 2314 Direct Access Storage Facility, a Disk Operating
System can be generated that supports those IBM-supplied
programs desired by the user, in addition to his own programs.
With the storage requirements provided, an installation-tailored
Disk Operating System can be planned. With the sample problems
provided, the generated system can be tested. A thorough
understanding of IBM System/360 Disk Operating System concepts and
machine facilities are prerequisites to the effective use of this
manual. Major topics discussed in detail are:
• Planning an Operational Pack
• System Generation and Maintenance
Macro Instructions for Generating a Supervisor
Maintenance Procedures
• Sample Problems
• Storage Requirements
Prerequisites to a thorough understanding of this manual are:
IBM System/360 Disk Operating System, System Control and System
Serv1ce Programs, Form C24-S036
IBM System/360 Disk Operating System, Supervisor and Input/Output
Macros, Form C24-S037
IBM System/360 Disk Operating System, Operating Guide,
Form C2S-S022
IBM System/360 Disk and Tape Operating Systems, Utility Programs
Specifications, Form C24-346S
IBM System/360 Basic Programming Support, DASD Utility Programs
Spec1f1cat10ns, Form C24-3363
For titles and abstracts of other associated pub~ications,
see the IBM System/360 Bibliography, Form A22-6822.

DOS

Eighth Edition (April 1969)
This edition applies to Release 20 of IBM System/360 Disk Operating system
and to all subsequent releases until otherwise indicated in new editions or
Technical Newsletters. Changes are continually made to the specifications
herein; before using this publication in connection with the operation of
IBM systems, consult the latest Systeml360 SRL Newsletter, Form N20-0360,
for the editions that are applicable and current.
This edition, C24-5033-7, is a major revision of, and obsoletes,
C24-5033-6.
Summary of Amendments
This edition reflects support for:
• Overlapping of I/O with processing for both the load and sequential
retrieve functions for indexed sequential files.
• The capability of returning additional unrecoverable I/O errors to the
problem program using the direct access, sequential disk, indexed
sequential and magnetic tape macro functions.
• The 1401/1440/1460 Emulator Program for the IBM System/360 Model 40 and
Model 25.
• The librarian copy and organize program extension that allows merging
of litraries.
• PL/I Version 4.
•

BTA~

and QTAM in a multitasking environment.

• COBOL improvements for Indexed Sequential File Management

Maintenance changes

and technical corrections are also included.

The storage estimates, formerly published in IBM Systerrv360 Disk Operating
System Performance Estimates, Form C24-5032, are now published in Appendix
~ of this manual.
Changes are indicated by a vertical line to the left of affected text and
to the left of affected parts of figures.
A dot (.) next to a figure title
or page number indicates that the entire figure or page should be reviewed.
Requests for copies of IBM publications should be made to your IBM
representative or to the IBM branch office serving your locality.
A form for readers' comments is proviced at the back of this publication.
If the form has been removed, comments may be addressed to IBM Corporation,
Programming Pul::lic~tions, End~cott, New York 13760.
@

Preface
This publication guides the user through
the generation of an installation-tailored
Disk Operating System for IBM Systeml360.
The information her:ein is of particular
interest to anyone who wants to build a
Disk Operating System, including
installation managers" system analysts,
programrr.ers and machine operators.
In particular, the user will find that
familiarity with the following system
programs and facilities is invaluable when
using this publication: the control
program, the system service programs, and
the input/output control system (IoeS)
logic modules. The control program, and
the system service programs are described
in the System COftrol and System Service
Programs publica ion. The IOCS logic
modules are described in the Supervisor and
Input/OutPUt Macros publication, both of
which are listed on the front cover.
The publication is divided into the
following major sections, and seven
appendixes:

Disk Operating Systems to maintain an
existing Disk Operating System.
section ten describes the IBM-supplied
sample problems that can be used to test a
system after it is generated.
The appendixes contain information
needed for planning a Disk Operating
System. Appendix B, IOCS Modules for
COBOL, RPG, and PLlI; Appendix C, IBM
System Components Identification; and
Appendix G, Storage Requirements are of
major importance for planning purposes.
Appendixes Band C will assist the user
when planning the contents of his
libraries, and Appendix G when estimating
the size of his supervisor, and libraries.
Closely related publications are:
IBM system/360 Disk Operating System,
Timing Estimates, Form C24-5032
IBM System/360 Disk Operating System,
Vocabulary File Utility Programs for IBM
7772 Audio Response Unit, Form C27-6924
IBM Systeml360 Basic Programming Support,
Distribution Program Specifications and
Operating Guide, Form C21-5001

1..

Introduction

Planning an Operational Pack

System Generation and Maintenance
Procedure

C24-3392

IBM BPS Utility Programs

References are made in this publication
to the following:

Macro Instructions for Generating a
Supervisor

Two 2311 Disk Drives

One 2311 Disk Drive

IBM 2314 Direct Access Storage
Facility

9.
10.

Maintenance Procedures
Disk Operating System Sample Problems

The first five sections contain required
information for most users. Sections six,
seven, and eight refer to specific machine
configurations, and present techniques for
generating a system.
They are examples
intended to guide the user through the
generation of his system. Only the section
that relates to the user's configuration
need be read.
Section nine describes maintenance
procedures and how to apply IBM-supplied

IBM System/360 Basic Programming Support,
DASD Utility Programs Operating Guide, Form

IBM Systeml360 Disk and Tape Operating
Systems, COBOL Programmer's Guide, Form
C24-5025
IBM Systerr.l'360 Disk Operating System,
FORTRAN IV Programmer's Guide, Form
C28-6397

IBM System/360 Disk and Tape Operating
systems, Basic FORTRAN IV Programmer's
Guide, Form C24-5038
IBM System/360 Disk and Tape Operating
Systems, PL/I Programmer's Guide, Form
C24-9005
IBM System/360 Disk Operating System
1401/1440/1460 Emulator Programs for IBM
System/360 Models 30 and 40; Compatibility
Support/30j Compatibility support/40, Form
C27-6940
IBM System/360 Disk Operating System
Autotest, Form C24-5062.
Preface

Contents

INTRODUCTION • • • • • • •
Planning System Generation
Planning the Libraries .
Core Image Library • • •
Relocatable Library
Source Statement Library
Private Libraries
Library Sizes . • • • .
Allocating Library Sizes
Planning a Supervisor
System Configuration • • •
Machine Requirements • •

7
7

• .

8
• .
8
•
9
• • • •
9
.
.••. 9
9
• • • .
10
•
10
•
• 10
10
•

PLANNING AN OPERATIONAL PACK.
Background Partition Storage
Requirements for Disk operating
System IBM-Supplied Programs . • • • •
One 2311 Disk Drive • • • • • •
•
At Least Two 2311 Disk Drives or a
2314 Direct Access Storage Facility •
Allocating Library Sizes for 2311
and 2314 Disk Systems • • • • • •
User Decisions and Considerations • •
variants of IBM-supplied Assembler . •
Variants of PL/ I • • • • • • • • • • •
PL/I and System Input/Output on Disk •
Warning Diagnostics • • • •
•

12
12
13
14
14
16
17
18
18
20

SYSTEM GENERATION AND MAINTENANCE
PROCEDURE • • • '. • • • • • • • •

• 22

IBM BPS UTILITY PROGRAMS •
• •
Copy and Restore • • • •
Distribution Program 360P-UT-208 •
Copying a System Tape to Disk
Restoring a System Tape to Disk • .
Initialize Disk
•••••• • •

• 27
27
28
• 29
• 29
• 29

MACEO INSTRUCTIONS FOR GENERATING A
. • • 33
SUPERVISOR • • • •
Rules for Using Supervisor
Generation Macros
'. 33
TWO IBM 2311 DISK DRIVES • • •
Input/Output Device Configuration
for Example One (See Figure 7) •
Example One: Results of system
Generation • • '. • • • •

52
• 55
55

ONE IBM 2311 DISK DRIVE
• • • 71
Input/Output Device Configuration
for Example Two (See Figure 9) • • • • 74
Example Two: Results of System
Generation • . . • • • . • . •
74
IBM 2314 DIRECT ACCESS STORAGE
FACILITY . . . . . . . . . . .
87
Input/Output Device Configuration
for Example Three (See Figure 11)
. . 88
Example Three: Results of System
Generation . . . . . . . . . . . . . . . 89

MAINTENANCE PkOCEDURhS . . . . • . . . . 91
Using the MERGE Functi on of the CORG Z
Librarian Program
. • . • . . . • 97
Replacing Identical Entries Using
MERGE Function . . • • • . • • • . • . 97
Adding Unique Entries Using MERGE
Function • • • . • • . • • • • • . . . 97
General Library Updating Techniques
using the MERGE Function of the CQRGZ
Librarian Program
• • • • . 97
Copying Se lecti ve ly t.o Merge
Libraries • . • . • . . • . •
• 97
Deleting Unwanted Entries and
MERGING an Entire Library with
Another Library . • . • • • .
• 98
Copying Selectively Merging Two
Libraries to Create a Third Library . 98
Deleting Unwanted Entries from Two
Libraries and Merging Both Libraries
to Create a Third Library • • • . . • 9£
Conventions for Merge Examples • • . . • 98
Maintenance Examples using MERGE
Function . • • • • • • • . • • • • • . • 99
Example lA: Copying Selectively to
Merge Two Libraries . • • • • . • . . 99
Example lB: Variation of Selective
Copying to Merge Two Libraries • • • . 100
Example 2A: Deleting Unwanted
Entries from A Library and Merging
Libraries by Copying One to the Other 100
Example 2B: Variation of Deleting
Unwanted Entries from A Library and
Copying (Merging) One to the Other • .100
Example 3: Copying Selectively,
Merging Two Libraries to Create a
Third Library . . • . • • . • • • • • 101
Example 4: Deleting Unwanttd Entries
from Two Libraries and Merging Both
Libraries to Create a Third Library
.101
Considerations for Merging . • • . • • .102
DISK OPERATING SYSTEM SAMPLE PROBLEMS .105
Retrieving the Sample Problems . . • . . 105
Physical and Logical I/O Assignments . .109
Tape, Disk, and Data Cell
Configurations • • • • • • • • . . . . . 110
Exanples of .Sample Problem Execution
and Output. • •
.116
Multiprogramming • • • • • • • • • • • • 195
APPENDIX A. IPL CONTROL AND ASSGN
STATEMENTS FOR SYSTEM GENERATION • • • .222
ADD (Add a Device) • • • • •
.222
SEl' (Set the Oat e) • • • • • .
.223
ASSGN (Assign Logical Narre)
.223
ALT • • • • • • • • •
.224
APPENDIX B. loeS MODULES FOR COBOL,
RPG, AND PL/I • • • • •
• • . • • • 225

contents

APPENDIX C. IBM SYSTEM COMPONENTS
IDENl'IFICATION • •
••.•• • •
Core Image Phases
• • • • • •
Relocatable Module Identification •
Telecommunications • • • • • • • • •
BTAM Relocatable Module and Core
Irrage Phase Identification • • •
QTAM Relocatable Module and Core
Image Phase Identification •
•
Preassembled Modules Used to Build
IBM components • • • • • • •

• • 233
.233
• • 238
• .257
.257
• • 262
• • 269

APPENDIX D. DISK SORT/MERGE MODULES • .277
Prirrary Processor Generation Books • • • 278
Intermediate Processor Generation Books 279
Phase Names and Relocatable Module
. .281
Names
APPENDIX E. TAPE AND DISK SORT/MERGE
MODULES • • • •
• • • • • • • . • • 282
P ri na ry Process or Generat ion Books • • .283
Intermediate Processor Generation Books 283
Phase Names and Relocatable Module
Names
.................293
APPEND!X F. BPS DEVtCE TYPE
SPECIFICATIONS (DD)
••••

• • • 295

~~ENDIX

G. STORAGE REQUIREMENTS.
.296
Internal Storage Requirements
• • • 296
supervisor • • • • '. • • • • • • • • • • 296
ComI=uting the Size of a supervisor • • .303
Supervisor Macro Instructions
.304
Foreground Save Areas • • • • • •
.306
MPS utility Macro Instructions • • • • • 306
loes Declarative Macro Instructions • • 306
DTFCD (Define the File: Card) • • • • 309
CDMOD (Card Module)
• • • • • • • 310
DTFCN (Define the File:
Console)
• • 311
DTFDA (Define the File: Direct
Access Device) • • • • • • • • • • • • 311
DAMOD (Direct Access Device Module)
.3'12
DTFIS (Define the File:
Indexed
Sequential)
• • • • • • • • • • • • • 312
ISMOD (Indexed Sequential Module)
• • 313
DTFMR (Define the File: l-lagnetic
Character Reader)
•.••.••
.315
MRMOD (Magnetic Character Reader
Module)
•••••••••••
..315
DTFDI (Define the File: Device
Independent System Units)
• • 315
DIMOD (Device Independent System
Units Modules) • • • • • . • • • • • • 315
DTFMT (Define the File: Magnetic
Tape)
................315
MTMOD (Magnetic Tape Module) . •
.317

IBM S/360 DOS Sys. Gen. and Maint.

DTFOR (Define the File: Optical
Reader)
• • . • • • • . . . • . . · .317
ORMOD (Optical Reader Module)
.31b
DTFPH (Define the File:
Physical
loeS)
• . • • • . • . • . . . • • · .318
DTFPR (Define the File: Printer)
• . 318
PRMOD (Printer I-lodule) •
.319
DTFPT (Define the File: Paper Tape
Reader)
...............319
PTMOD (Paper Tape Reader Nodule)
.319
DTFSR (refine the File: Serial
Device)
••••.•..
. . . 321
DTFBT (Define the File: BTAM) • • • .321
DTFBTND (Define the File ~nd: BTA~)
.323
DFTRMLST (Define the 'I'erminal List:
BTAM)
••••••.•.••.
..323
BTMOD (BTAt-~ Logic Module)
• .325
BTAM Data Event Control Block
.326
QTAM Storage Requirements
• . 326
Basic QTAM Logic Modules. • •
• .326
DTFQT (Define the File: QTAM)
.327
QTAM Storage Requirements for Control
Information • • • • • • • • • • • • . 329
QTAM Requirement for Buffers • • . • . 330
QTAM Storage Requirements for Device
I/O Modules
• • • • • • • . 331
Requirements for Other QTAM Macro
Instructions. • • • • • • • • •
.332
Other IOCS Macro Instructions
• • 338
Relocatable Subroutil'.e • •
• .342
COBOL Subroutines . • • . .
. .342
FORTRAN Subroutines • • • •
• .345
Basic FORTRAN Subroutines . • • . • .346
PLiI Subroutines • • • • • . . • . • • 347
IOCS Modules For The Compilers .
.349
Exte~nal storage Requirements
• . • • • 356
Core Image Library • • •
.358
Reloca table Library
• • ••
..360
Source Statement Library •
• .361
Workfile Requirements
• . 365
Workfile Requirements for Linkage
Editor and Assembler (IBM 2311 and
IBM 2314)
••••••.•.
· . 365
Assembler Workfiles • • • • •
.365
IBM 2311 Workfi1e Requirements •
• .370
Autotest Work Area (IBM 2311)
• .371
COBOL Workfiles (IBM 2311) •
• .371
FORTRAN Workfiles (IBM 2311)
.371
PL/I Workfi1es (I~M 2311)
· .371
RPG Workfiles (IBM 2311) • • •
• .371
IBM 2314 Workfi1e 'Requirements
• .372
COBOL Workfi1es (IBM 2314) • • • • • .372
.372
FORTRAN Workfiles (IBM 2314)
PLiI Workfiles (IBM 2314)
.372
RPG Workfiles (IBM 2314) • •
.372
.373
Optimum Assignment of Workfiles
INDEX

.378

In trod uction

The IBM System/360 Disk Operating System for 2311 resident systems is
suppl ied to the user in two volumes,.
The volumes can be identified as a
relocatable volume and a source statement volume. Users with a tape unit
available receive the volumes on tape reels; users without a tape unit
available receive the volumes on disk packs. These volumes are manipulated
during system generation to create an operational system.
IBM supplies the 2314 system on two tape reels. These tapes will be
restored to a 2314 disk pack to create a system consisting of a core image
library .. a relocatable library" and a source statement library. The
ca~acity of one 2314 disk pack is enough to accommodate both tape reels
shipp ed by IBM ..
The disk operating system is composed of three libraries:
Source statement Library
Relocatatle Litrary
Core Image Litrary
The source statement library contains IBM-supplied macro definitions.
When the desired parameters are chosen, the macros can be assembled. For
the user's convenience" the source statement library also contains sample
prohiems and system generation job streams that can be retrieved as needed.
The relocatable library contains IBM programs that have not been
assigned addresses for execution and assembled macros from the source
statement library. These assembled macros perform input and output
procedures for IBM-supplied programs.
These assembled macros (Logical IOCS
modules) can also te used by user programs when applicable.
The core image library contains programs that are ready for execution.
System control programs and system service programs are always shipped to
the customer in the core image library. Where i t is necessary for system
generation purposes, an assembler program is provided. The system control
programs must always be part of the system. The librarian programs are a
key set to the system and should be carefully considered before ever
removing them from the system.
During system generation the user works with the IBM-supplied system to
tailor it to his individual needs. This consists of adding to and deleting
from the libraries, IBM and user code (source, relocatable and core image).

Planning System Generation
Proper and detailed planning saves on total system generation time.
it is very important to perform a very thorough job.

Thus,

Planning system generation consists of:
1.

Planning the contents" organization, and ultimate size of the system
and/or private libraries.
This entails distributing the storage space
available (on the disk packs) between the libraries ultimately desired
for day-to-day use. Major points of consideration are:
Introduction

• the size of the core image library and, if desired, system and/or
private relocatable and source statement libraries
• workfile space needed to assemble a supervisor, and to accommodate
the linkage editor, which is needed to catalog the components
selected to the system core image library
• standard assignments (allocation of space) for workfiles
(assemblies), and linkage editing needed for every day operation.
2.

Planning the contents and estimating the size of a supervisor.
This
entails selecting from the programming services provided by IBM, those
to be included "in the supervisor, and estimating the cost of these
services in terms of bytes of storage.

PLANNING THE LIBRARIES
Two types of IBM libraries are:
1.

System libraries

Private libraries

The system libraries are the core image, the relocatable, and the source
statement.. The private libraries are the private relocatable, and the
private source statement library.
(There is no private core image
library. )

CORE IMAGE LIBRARY
Because the core image library contains the executable format of programs,
i t is the library in ~hich the user is most likely to keep his programs.
otherwise, the programs must continually be placed in the core image
library before each execution (linkage edited). Therefore, during system
generation the user expands the size of the core image library to
a ccanmoda te all the programs desi red resident and on-line.
(Both his own
programs and IBM's.)
In addition, the user should try to envision future space he may
require, and provide this space if possible. Such planning can eliminate
the need for another system generation.
Thus, to expand the core image
library means making the remaining libraries smaller on the pack.
Eefore the size of a library is reduced, the user must delete those
items that are not to be used, or those items that were transferred to
another library in the required format.
It is recommended that backup of
the system (a copy of the IBM-supplied system) be obtained to protect a
user who accidently removed something he desired from the system. It is
also recommended that after successful completion of segments of system
generation, a copy (backup) of the partially generated system be obtained,
i.e., upon the creation of a library, or the assembly of a supervisor. This
permits a user to return to a point other than the beginning of his
procedure in case of an error. The components supplied in the IBM-shipped
core image library facilitate system generation.
-8

IBM S/360 DOS Sys. Gen. and Maint.

RELOCATABLE LIBRARY
All IBM-supplied components are shipped in the relocatable library. This
libzary is the ~asis for the creation of a private relocatable library.
Thus" i t is from this library that most IBM components are directly or
indirectly extracted (indirectly in the case of the existence of a private
relocatable library and a system relocatable library).

SOURCE STATEMENT LIBRARY
All IBM-supplied macro definitions are in this library.
This library is
the basis for the creation of a private source statement library. Thus, it
is from this litrary that many users extract, direct_Iy or indirectly,
IBM-supplied component macro definitions (indirectly in the case of the
existence of both a private source statement library, and a system source
staterrent li~rary).

PRlv.ATE LIBRARIES
If the user has more than one disk drive available, it is not necessary to
decrease the size of the relocatable and source statement libraries. They
can be assigned to other disks and are then referred to as private
libraries. The user can build systems with private and system libraries
containing those items that best fit his needs.

LIBRARY SIZES
The user must choose which of the libraries he desires, and then plan their
precise content and size for daily use. Thus, the user should know the
initial. intermediate, and final sizes of the libraries throughout system
generation, and he must plan the exact contents of each library that is
created during system generation.
These contents should be listed, along
with their sizes., and then the total number of cylinders to be allocated
can be calculated.
The contents of the libraries are identified in Attachment 1 of the
Memorandum To Users that accompanies the IBM system that is shipped.
The
stor.age requirements (sizes) for these components, and macro definitions
are identified in Appendix G:
Storage Requirements.
Components shipped in
the relocatable library are also identified in Appendixes B, C, D, and E.
Those macro definitions supplied by IBM are also identified in Appendix C.
An alternate method for determining the number of cylinders to allocate
for a library is given in the discussion Allocating Library Sizes for 2311
and 2314 Disk Systems. Note that once private library sizes have been
allccated, they cannot be reallocated. Although excess room in the
libraries may not offer maximum efficiency, in case of a calculation error,
the benefits can be easily recognized when sufficient space is available.
lnt roduction

ALLOCATING LIBRARY SIZES
When the user desires to reduce the size of an existing library, it may be
imFcrtant to know the minimum library size that can be allocated.
This
size should be increased to accommodate any additional user programs to be
included in this library.
The size of any IBM component to be included in
this litrary can be determined by referring to the storage requirements
given in Appendix G..
For the details on how to allocate an existing
library, see Allocating Library Sizes for 2311 and 2314 Disk Systems.

PLANNING A SUPERVISOR
The supervisor is a control program that provides specialized services to
programs executed from the problem Frogram area of main storage. This
program is composed of a group of assembled macros (see Macro Instructions
for Supervisor Generation. The options selected in each of the supervisor
generation macros determine the size of the assembled supervisor. The size
of each option is identified in Appendix G.
The SEND macro determines the end of the supervisor.
If the user
assembles a supervisor with a SEND address larger than the previous
supervisor, some portion of the supervisor is overlaid by programs linkage
edited to the previous SEND address.
~e user must re-linkage edit programs after the new supervisor is
loaded so that the new load address follows the newly assembled supervisor.

Note that at each IPL, the user must include ADD and ASSGN statements
for each device until a system supervisor is built that describes his
machine configuration and standard I/O assignments (see DVCGEN and ASSGN
macros) •
To calculate the size of the supervisor the user must list all of the
oFtions that are chosen and then determine the sum of the sizes obtained
from the storage requirements (see Appendix G).

When choosing supervisor parameters, the user must check to see if the
chosen options are compatible. Also, the user should check to deterwine
which parameters automatically Frovide the support for another.

System Configuration
This section presents the m1n1mum system configuration required to operate
the Disk Operating system. The system control programs and basic 10CS must
always be present in order to execute any other programs.

MACHINE REQUIREMENTS
Minimum features required:
16K bytes of main storage
Standard instruction set.
10

I~l

See Note 1.

S/360 DOS Sys. Gen. and Maint.

One I/O channel (either multiplexor or selector).
One Card Reader (1442,

2501, 2520, or 2540).

Ole Card Punch (1442, 2520, or 2540) '.
One Printer (1403, 1404, or 1443).

See Note 2.

See Note 3.

One 1052 Printer-Keyboard.
One 2311 Disk storage Drive or
One 2314 Direct Access Storage facility
Note 1:

Language translators may require extended instruction sets.

Note 2: Telecommunications requires a minimum of two channels, one
multiplexor channel, and at least one selector channel. One channel is
required for telecommunications, and the other for the system resident
device.
(Telecommunication devices should not be on the same selector
channel as SYSRES.) Note that a 2701 Line Adapter Unit attached to an IBM
Systeml360 Model 2025 must be placed on the multiplexor channel.
Note 3:
One 2400-series magnetic tape unit may be substituted for this
device (7- or 9-track). If 7-track tape units are used, the data-convert
feature is required, except when substituted for a printer.

IntrodUction

Planning an Operational Pack

An operational system is one used in day-to-day operations that contains a
tailored supervisor and libraries a~~ro~riate to each customer's particular
combination of system programs and application programs. A system
"maintenance volume is one used primarily to facilitate changes to programs
su~~lied ty IBM.
Application programs can also te added to a maintenance
volume for ease of program maintenance.
Change Distributions are those changes supplied by IBM to the
IBM-shipped volume.
Proper planning is the key to successful system generations.
The time
spent in planning can save the user frustration and valuable time. The
user's planning should reflect the initial, intermediate and ultimate
ca~acity of the core image, relocatable and source staten~nt libraries.
Enough workfile capacity f[1ust be avai lable throughout system generation for
assemblies and linkage-edit steps.
Appendix G should be used to deterrrine storage requirements for the
components in the system.
IBM supplies a system containing either a 6K for 2311, or 8K for 2314
supervisor. The IBM supervisors are those described in Figure 6.

BACKGROUND PARTITION STORAGE REQUIREMENTS FOR DISK OPERATING SYSTEM
IBM-SUPPLIED PROGRAMS
All IBM-supplied programs used with Disk Operating System that are language
translators or utilities execute in the background partition. Figure 1
lists the minimum size background partition required.

IBM S/360 DOS Sys. Gen. and Maint.

r----------------------------------------------------------------------,
Minimum Size

I
I

IBM-Supplied
Program

IBM-Program
Nurober

Background
Partition (in bytes)

\Asserr.bler (IJQD16TW)
360N-AS-465
10,240
\ or (IJQD16DW)
Assembler (IJQD32)
360N-AS-465
14,336
Assembler (!JYASM)
360N-AS-466
45,056
360N-CB-452
14,336
COBOL
Basi c FORTRAN
360N-FO-451
10,240
360N-FO-479
40,960
FORTRAN
360N-RG-460
10,240
RPG
PL/I
360N-PL-464
10,240
Utilities
10,240
Group 1
360N-UT-461
360N-UT-462
10,240
Group 2
10,240
Group 3
360N-UT-463
10,240
Tape Sort/Merge
360N-SM-400
10,240
360N-SM-450
Disk Sort/Merge
360N-SM-483
Tape/Disk Sort~lerge
10,240
Tape/2311
22,528
2314
1401/1440/1460 Emulator
360N-EU-484
16,384
fer IBM Model 30
1401/1440/1460 Emulator
fer IBM Model 40
360N-EU-485
*
test
360N-PT-459
10,240
l\ Auto
______________________________________________________________________
J

The background partition storage requirement is as follows:
16,384 bytes for the supervisor plus 2,048 to 16,384 bytes for the 1400
being emulated plus the size of the emulator program defined.

eFigure 1.

Disk operating System Background Partition Storage Requirerrents
for IBM-Supplied Programs

ONE 2311 DISK DRIVE
When the user plans his operational system he decides upon the ultimate
appearance of his libraries..
The one disk drive user will find it most
convenient to tuild his operational system on the IBM volume that contains
the core image and relocatable libraries.
Many single disk drive users
will want to build operational systems appearing as one of the following:
• Core image library, small system relocatable library, and/or small
system source statement library
• Large core image library
The small system relocatable library is for users who need the compiler
subroutines and/or system IOCS modules on line at all times. If the
subroutines are to be on line, the relocatable library should also have
enough room to contain the user's largest compiler.
The samll system source statement library can contain system oontrol and
logical IOCS macros.. The system with the source statement library,
suppl ied by IBM" can be used as an assembly pack.
Planning an Operational Pack

AT LEAST TWO 2311 DISK DRIVES OR A 2314 DIRECT ACCESS STORAGE FACILITY
The user with at least two disk drives will find it
build his operational pack upon the IBM volume that
and source statement libraries.
Many multiple disk
to build operational system appearing as one of the

most convenient to
contains the core image
drive users will want
following:

• Core image li1:;rary, private relocatable, and private source statement
libraries.
• Core image library, private relocatable library, system source
statement library, and private source statement library.
• Core image library, system relocatable library, private relocatable
library, and private source statement library.
• Core image library, system relocatable and source statement libraries,
and private relocatable and source statement libraries.
• Core image library, system relocatable and system source statement
libraries.
• Core image library, system source statement library, small private
relocatable library (on the operational pack) and private relocatable
library.
IBM system control and system service programs are supplied in the core
image libraries of both volurres for the 2311 systems and in the core image
library for the 2314 system. The 2311 systems have the 10K background disk
workfile assembler supplied in the core image library of the source
statement library volume. The 2314 systems have the 14K background disk
and tape workfile assembler in the core image library. For both 2311 and
2314 systems, all IBM components are supplied in the relocatable library.
If the user" s assembled supervisor does not exceed the siz e of the IB~1
supervisor, re-linkage editing and re-cataloging of the IBM-supplied
programs shipped in the core image library are unnecessary,. Job control is
self-relocating and need never be re-linkage edited. Only the steps
required to retrieve the sample problems, delete unwanted components,
assign standard labels, assemble a user's supervisor, allocate for and
I inka ge edit IBM components, and condense libraries are necessary to
perform system generation.
When the num1:;er of tracks required for each library has been calculated,
the user should allocate a sufficient number of cylinders to each library
of each operational system. Additional cylinders may be allocated to the
core image library for application programs. Sometimes the user must
reallocate the libraries on his disk pack(s) during system generation to
ensure sufficient work file storage for assemblies and linkage-edit steps.
Users with more than one available disk drive will find it to their
advantage during system generation to define private relocatable and source
staterrent libraries for an operational system.

ALLOCATING LIBRARY SIZES FOR 2311 AND 2314 DISK SYSTEMS
When the size of an existing library is reduced, it may be important to
know the minimum size library that can be allocated. Once the minimum size
libzary is calculated, it should be increased to accommodate any user
programs to be included in the library.
The size of IBM components can be
deterrrined t¥ referring to the storage requirements given in Appendix G.
14

IBM S/360 DOS Sys. Gen. and Maint.

'!he following explanation illustICJtes how to calculate the nunJJer of
tracks required for a core irr.age, relocatable, or source statement library
for a 2311 or 2314 disk system. The formula for computing the size of a
library is:
Library (size in tracks)
where:

library

LBA

LBA/nn

either core image, relocatable or source statement
the number of L1.BRARY BLOCKS ACTIVE for thE: library of
interest and is obtained from a DIH.ECTORY (SYSTFM or
PRIVATE)

= LIBRARY LAST AVAILABLE ENTRY in the R (record) column

Using the sample PRIVATE DIRECtORY that follcws, an example of how to
compute a library size is:
Relocatable Library

LBA/nn

where:

IBA = 9849
nn = 9 , thus
Relccatable Litrary = 9849/9

1,094.3 tracks

The relocatal:le litrary size cOlnputed does not include the tracks
allocated for the directory (see Dir~ctory Allocated Tracks). The
directory size must be added to the relocatable library size computed.
Thus,
Relocatable Library Allocation
Tracks

Relocatable Library + Directory Allocated

1,094.3+9
1,103.3 Tracks

Therefore,
Relocatable Library Allocation

For a 2311, cylino€rti

Library Size (Tracks)
10

For a 2314, cylinders

Library Size ('l'racks)
20

For thi s (;xample,
the Relocatal:le Litrary Allocation for a 2311
rcunded high

1103.3 Tracks
10
110.1 or 111 cylinders,

PRIVATE DIRECTORY

PRIVATE-RELOCATABLE

02/01/69

------DECIMAL-----C H R E
01 00 01
01 05 01 08
01 08 09 19

DIRECTORY STARTING ADDRESS
DIRECTORY NEXT ENl'RY
DIRECTORY LAST ENTRY
LIBRARY
LIBRARY
LIBRARY

STARTING ADDRESS
NEXT AVAILABLE ENl'RY
LAST AVAILABLE ENTRY

01 09
111 03
127 09

01
04
09

STATUS INFORMATION
DIRECTORY ENTRIES ACTIVE
LIBRARY
LIBRARY
LIBRARY
LIBRARY

BLOCKS ALLOCATED
ACTIVE
BLOCKS DELETED
BLOCKS AVAILABLE

B~OCKS

AUTOMATIC CONDENSE LIMIT
LIBRARY
ALLOCATED CYLINDERS
DIRECTORY ALLOCATED TRACKS

903
11349
9849
00
1500
00
127
09

USER DECISIONS AND CONSIDERATIONS
The follo~ing considerations and decisions should be made before system
generation:
1.

Select supervisor options l:y coding a set of supervisor macro
instructions (see Macro Instructions for Generating a supervisor).

Determine which programs will be in the core image library of each
operational pack (e.g. COBOL, FORTRAN, etc).

Determine which assembler will be used to generate a new supervisor.
py a DOS system to tape:
• Mount the DOS system and a tape.
• The following jot control cards must be placed in the program deck
between the cards containing ID numbers C208 and D208 in columns 73-76:
• Place the deck in the card reader.
//
/ /
//
//
//
//
//
/ /

JOB nISCPY
DATE 68110
ASSGN SYSLOG,X'cuu',dd
ASSGN SYSLST.X'cuu' "dd
ASSGN SYSOOO,X'cuu',dd (disk)
ASSGN SYS001,X'cuu' ,dd£,X'ss'] (tape)
CONFG 001 (optional, 16K assumed)
EXEC

Note:

For the BPS description parameter (dd) see Appendix F.

• The following utility modifier card IDUSt be placed immediately
following the program deck:
//bUDSb'field one of format 1 DASD file label 44-characters' Col.53
• Dial on the console the address of the card reader.
• Check the units and settings; then press the System-Reset key.
• Press the console load key.
• When the Wait light comes on, press Start and EOF on the card reader.

RESTORING A SYSTEM TAPE TO DISK
The IBM-supplied system residence tape must be copied onto a disk pack
befcre system generation can be performed. The pack that is to contain the
system must be initialized with a volume label and a volume table of
contents (VTOC). If the disk pack is not initialized or if the VTOC is not
at cylinder 199., the pack must be initialized.

INITIALIZE DISK
The following instructions and control cards will allow the user to
properly initialize his disk:
• Mount the distribution tape.
• Place the following control cards in the card reader, in the sequence
shown:
IBM BPS utility Programs

Card Col. 1

Card 1

// JOB INTDSK

Card 2

// DATE yyddd

yy
ddd

= 00 to 99 decimal

001 to 366 decimal

Card 3

// ASSGN SYSOPT,X'cuu' ,Dd
cuu = channel and unit of disk drive
Dd = Dl for 2311 or D3 for 2314

Card 4

// ASSGN SYSLOG,X'cuu' ,Cl
cuu = channel unit 1052

Card 5

// EXEC

Card 6

/ / UIDbIR,Cl

Card 7

// VTOC STRTADR=(0199000),EXTENT=(y)
Y = nurrber of tracks allotted
to VTOC in decimal (1-10).

Card 8

VOLlnnnnnn

Card 9

/ / END

nnnnnn = Volume serial number
Columns 42-51 are reserved for user's
identification.

• Dial on the console the address of the tape unit containing the
distribution tape into the CPU load address switches.
• Press Load.
• When the Wait light comes on, press start and EOF on the card reader.
• The message EOJ will be printed on the 1052 printer-keyboard when
ini tializa tion is complete.
The system can then be copied on the Jisk.
BYPASS INITIALIZE DISK
If the disk has previously been properly initialized, the Initialize Disk
procedure can :be omitted and the following proced.ure performed to bypass
the initialize disk routine:
• Nount and ready the distribution tape.
• Place the following control cards in the card reader in the sequence
sho'Nn:
Card Col. 1

Card 1

JOB INl'DSK

Card 2

DATE yyddd

Card 3

/ / ASSGN SYSLOG,X'cuu'

Card 4

yy = 00 to 99 decimal
ddd = 001 to 366 decimal

LOG

IBM S/360 DOS Sys. Gen. and Maint.

,Cl

Card 5

// ASSGN SYSIPT,X'cuu',Tz[,X'90']
cuu
channel and unit
z = 2 for 9-track tape
z = 1 for 7-track tape
The X'90' entry is
required if z = 1.

Card 6

// FILES SYSIPT,l

• Dial the address of the tape drive containing the distribution tape in
the CPU load address switches.
• Press Load.
• When the Wait light comes on, ready the card reader containing the
control cards by pressing Start and EOF.
• The tape will forward-space past the initialization program and the
following message will appear on SYSLOG:
OOOC
4000A

RESTORE A SYSTEM TAPE TO DISK
Following initialization or bypassing initialization of the disk pack, the
IBM-supplied system tape can be restored to disk by this procedure:
• Do not rewind the distribution

ta~e.

• Clear the card reader.
• Place the following control cards in the card reader:
Card Col. 1

Card 1

/ / JOB DISRST

Card 2

/ / DATE yyddd

Card 3

// ASSGN SYSOOO,X'cuu',Dd
cuu = channel and unit of
the initialized disk
Dd = Dl for 2311 or D3 for 2314

Card 4

// ASSGN SYSLST,X'cuu',Ll

Card 5

// ASSGN SYSLOG,X'cuu',Cl

Card 6

// EXEC

yy
ddd

=
=

00 to 99 decimal
001 to 366 decimal

• IPL from the distribution tape and press Load on the console.
• When the Wait light comes on, ready the card reader b¥ pressing Start
and EOF.
• The following message appears in SYSLOG:
4444A
Type in 4 ~, and press INTERRUPT to continue.
IBM BPS utility Programs

• If the message END OF VOLUME ON SYSIPT 3777A occurs while restoring a
mUltivolume file, ready the next reel on SYSIPT reply 22 and press
interrupt to continue. This message will not be encountered if the
second volume of a two-volume system distribution is mounted on an
alternate drive assigned to SYS002.
// ASSGN SYS002,X'cuu' ,TZ
• When the job is finished, the following message is printed on the IBf'J
1052 Printer-Keytoard and the disk rack is ready for system generation:
DOS SYSTEM RESIDENCE FILE
nnnnnn RECORDS RESTORED FOR ABOVE FILE
3007
END OF JOB
3008

IBM S/360 DOS Sys. Gen. and Maint.

Macro Instructions for Generating a Supervisor

Using the IBM-supplied volume, each installation normally generates a more
efficient supervisor using the supervisor generation macro instructions.
The macro instructions describe the machine configuration, standard I/O
assignments, and standard processing options.
This section defines the ten rracro instructions and their parameters
required to generate an installation-tailored supervisor for the Disk
Operating System. Figure 4 is a consolidated list of the supervisor
generation macros discussed.

RULES FOR USING SUPERVISOR GENERA'!'ION MACROS
1.

The assumed value for an omitted parameter is underlined in the
following discussion and in Figure 4. Figure 5 shows device type
codes to be used for system generation.

Material enclosed in braces { } indicates a programmer option.
the enclosed values must be selected by the programmer.

Bracketed operands are optional, e.g.,

Re{:lace the letter!! in a {:ararneter with a decimal number.

The name field must be blank. The operation field always contains the
mnemonic operation code.
The operand field contains the parameters.

Several parameters may be included on one line for all macros.
Se{:arate each parameter with a comma. No embedded blanks are
permitted. Continuation cards are permitted (nonblank character in
column 72; the continue column is column 16).

In the expression X'cuu', replace cuu with the hexadecimal number for
channel and unit.

The macros must be issued in the following sequence: SUPVR, CONFG,
STDJC, FOPT, PIOCS, ALLOC, IOTAB, DVCGEN, ASSGN, SEND.

The DVCGEN, ASSGN, and ALLOC macros are not required.
They are
specified if input/output tables (OVCGEN) are being specified, if
standard assignments (ASSGN) are being made or if storage is allocated
(ALLOC) for MPS at system generation time.

10.

One of

[nl.

An END card and a /* card must follow the SEND macro instructio ••

SUPERVISOR
SUPVR

This macro instruction and its parameters define the
system as disk resident and its ability to perform
multiprogramming, t·lICR or Teleprocessing.

Macro Instructions for Generating a Supervisor

Parameters for SUPVR
SYSTEM=DISK

MPS={~}

BT~~}

TP={
,QTAMn

MICR=

•

Specify if there is to be multiprogramming support.
When YES or BJF is specified the system generated is
capable of supporting two foreground programs.
YES
or BJF must be specified if TP=QTAM. When BJF is
specified, batched job environment will be supported
for both foreground partitions. Multiple
communication regions are generated only if BJF is
specified.
MPS=YES is implied if MPS=BJF is
supplied.

Specify if Teleprocessinq support is desired and if
so, whether Basic or Queued Accpss Method (BTAM or
QTAM) is desired. When QTAM is specified, SVc
support for BTAM is also included. n is the maxirr.um
number of QTAM message processing programs in the
system at one time. n may have any value from 2 to
12.

Not

1412
1419
1419D

AP={YES
NO}

Always used with the SUPVR macro instruction.
~YSTEM=DISK is assumed if this parameter is omitted.

Specify if the supervisor is to support magnetic ink
character readers.
If both 1412's and 1419's are
present, indicate 1419. If 1259's are to be
supported, also indicate 1419.
1419D indicates Dual
Address Adapter 1419's. If 1412/1419's are attached
to the multiplexor channel, the PIOCS parameter
BMPX=YES is not supported. 1419 support gives 1259
capabi Ii ty.
Specify if there is to be multitasking support.
Multitasking allows the execution of more than one
program within a partition. MPS=YES and WAITM=YES
are assumed if AP=YES.

EU={ NO}
YES Specify if the IBM 1401/1440/1460 Emulator program i~
to be executed. The MODEL operand in the CONFG macr<
can be MODEL=25, or MODEL=30 for IBM Model 2025, and
it must be MODEL=30 and MODEL=40 for IBM Models 2030
and 2040, respectively •

CONFIGURATION
CONFG

This macro instruction and its parameters define the
system configuration and can be used to specify
generation of optional supervisor services. If the
assumed options are all satisfactory, the only entry
required is the CONFG macro itself without an)'
parameters.

IBM S/360 DOS Sys. Gen. and Maint.

Parameters for CONFG
30)
MODEL={ nn, Specify the model number of the system (nn=30, 40,
etc).
If MICR support is required on a Model 65,
MODEL=65 should be indicated for maximum performance.
If 1401/1440/1460 emulator program support is desired
for the:
• IBM Model 2025, specify MODEL=25 or MODEL=30.
• IBM Model 2030, specify MODEL=30.
• IBM Model 2040, specify MODEL=40.

SP={Y~~}

DEC={Y~~}

FP={Y~~}

Specify if the storage protection feature is
available to the system. YES is assumed if the
MPS=YES or MPS=BJF parameter is specified in the
SUPVR macro.
Specify if the decimal feature is present.
specify only if the floating point feature is
present.

TI~.ER= {Y~~} Specify

if the timer feature is present.
specified, GETIME support is provided.

If YES is

JOB CONTROL OPTIONS
STDJC

This macro instruction and its parameters specify the
standard settings for jot control. If the assumed
options are all satisfactory, the only entry required
is the STDJC macro instruction itself, without any
parameters. These standard options can be locally
overridden by an OPTION statement.

Parameters for STDJC
YES}
DECK= { NO Specify if language translators are to output object
modules on SYSPCH.
YES}
LIST={ NO Specify if language translators are to write source
module listings and diagnostics on SYSLST.

LISTX={Y~~}
SYM=

{Y~~}

Specify if compilers are to write hexadecimal object
module listings on SYSLST.
Specify if assembler is to output symbol tables on
SYSPCH. SYM=YES must be specified if the PL/I
compiler is to produce a symbol and offset table
listing.

YES}
XREF={ NO Specify if assembler is to write symbolic
cross-reference lists on SYSLST.

Macro Instructions for Generating a Supervisor

ERRS={Y~}

Specify if compilers are to summarize all errors in
source programs on SYSLST. Assembler and PLiI always
assume ERRS=YES.

48Cl

CHARSET= { 60cf Specify either the 48- or 60-character set for PLiI
translator input on SYSIPT.
YES}
LOG= { NO specify for a listing of all control statements on
SYSLST. LOG=NO suppresses the listing of all job
control statements on SYSLST.
YES}
DUMP= { NO Specify if a dump of the registers and main storage
is to be written on SYSLST in the event of an
abnormal program end, cancel, or program check.

LINES={~} Specify

the number of lines per page on SYSLST.
minimum is 30: the maximum is 99.

The

MDY}
DATE= { DMY Specify the format of the date MDY=month/day/year.
DMY=day/month/year.
OPTIONAL FEATURES IN THE SUPERVISOR
FOPT

This macro and its parameters specify additional
optional features that can be included in the
supervisor.

Parameters for FOPI'
Specify if external interruptions (except timer) can
be handled by problem programs.
If YES is specified,
the facility is available to all programs in MPS.
The Tape Compare utility program requires OC=YES.
YES is required if emulator program operator services
are to be requested through the INTERRUPT key.

specify if the interval timer can be handled by
problem programs. When interval timer facilities are
available
Note:
Information on the macro instructions STXIT, EXIT, and SETlME is
contained in the Supervisor and Input/Output Macros publication.

PHYSICAL IOCS
PIOCS

This macro instruction and its parameters define
the configuration requirements to be supported by
physical IOCS.
If the assumed options are all
satisfactory, the only entry required is the PIOCS
macro itself, without any parameters.

Parameters for PIOCS
YES}
SELCH={ NO Specify if selector channels are attached to the
system.
Specify if burst mode devices will be supported on
multiplexor channel. If YES is specified,
unbuffered devices will not multiplex. If
1412/1419s are attached to multiplexor channel,
BMPX=YES is not support ed.
CHANSW={

RWT~~}

TSWTCH

Specify if channel switching tape control unit,
RWTAU = 2404 or 2804, TSWTCH = 2816.
If either
2403 or 2803 and 2816 is specified, RWTAU must be
specified.
If a 2804 is specified, RWTAU must be
specified. If a 2816 is specified, TSWTCH must be
specified .•

TAPE=r~
}
, 7 / Indicates

required tape PIOCS support.

= nine track only.

= seven or nine track.

NO = No tape drives attached.
value.

This is the assumed

ALLOCATE
AlLOC Fl=nK,F2=nK

Specifies storage partitioning MPS, where n must
be a multiple of 2. This macro is optional. Most
IBM components require 10K bytes of background
area. Foreground area must be a minimum of 10K to
allow BJF processing.
Macro Instructions for Generating a Supervisor

INPUT/OUTPUT TABLES
IOTAB

This macro instruction and its parameters define
the area for the necessary device tables for the
system.
If the assumed options are all
satisfactory the only entry required is the IOTAB
macro itself without any parameters.

Parameters for IOTAB
Specify the number of logical unit blocks (LUBs)
for programmer units, i.e., the number of symbolic
programmer logical units (SYSOOO-SYSnnn).
The
minimum value generated is 10.. The maximum value
generated is 222.

F1PGR={~}

F2PGR=

f 5}

JIB=

{~}

til

specify the number of symbolic units of the class
SYSnnn for Fl. Valid only for MPS. Otherwise
zero is assumed. The maximum value is 222.
Specify the number of symbolic units of the class
SYSnnn for F2. Valid only for ~WS~ Otherwise
zero is assumed. The maximum valu~ is 222.
Specify the number of job information blocks for
the system (JIBs).
One is required for each
logical unit temporarily reassigned by a // ASSGN
statement that differs from standard system
assignment (i. e., established by the operator at
IPL time). One JIB is required for each alternate
logical unit assignment. One JIB is required for
each open 2311 extent with the DASD file protect
feature except for system input/output extents.
Two JIBs are required for each open 2321 extent
with the DASD file protect feature. The minimum
value generated is 5. The maximum value generated
is 255.

IBM S/360 DOS Sys. Gen. and Maint.

CHANQ= {

6 or 6+CBF}
n

IODEV={l~}
Note:

Specify the number of entries in the channel
queue.
The roinimum value generated is 6. If the
assumed option is to be taken and CBF is to be
specified., the assumed option will be six more
than the CBF entry. The number of the channel
queue should exceed the total number of I/O
requests the user wishes to accumulate
simultaneously. The start I/O comnands for all
channels are stored in this queue. The maximum
value is 255.
Specify the number of I/O devices attached to the
system.
The maximum is 255. The minimum value is
5.

The sum of BGPGR + F1 PGR + F2PGR LUB's must not exceed 222.

INPUT/OUTPUT UNITS
DVCGEN

This macro instruction and its parameters define
the physical input and output units attached to
the system. This macro instruction is optional.

Parameters for DVCGEN
CHUN=X'cuu'
DVCTYP=xxxxxx

Specify the hexadecimal number of the channel and
unit for the device .•
specify the device type. Figure 2 contains the
codes for each IBM-supported device.

NOt
CHANSW= { YES! Specify if the device is attached to more than one
selector channel. Indicates if the device can be
switched (IBM 2816, 2804 or 2404 available).

Macro Instructions for Generating a supervisor

MODE=X'ss'

2400T9. MODE is used to specify the tape
mode. X'CO' is the default value.

2400T7. MODE is used to specify the tape
mode.
X'90' is the default value.

2702.
MODE designates the SADxxx command.
X'OO' is the default value.
X' 00' SAD 0
x'Ol'
SADl
X'02'
SAD 2
X'03'
SAD3
See Appendix A for other values of SSe

2260 (Local).
MODE is used to specify the
1053 printer when CHUN=X'cuu' refers to a 1053
attached to a 2848. The operand must be
entered as MODE=X'Ol'.

1412/1419/1259. MODE designates the external
interrupt bit associated with wagnetic ink
character readers. The mode X'Ol' through
X'20' corres~ond to external interrupt PSW'
bits 31 through 26 respectively. For the dual
address adaFter 1419, this parameter is needed
for both 1419P and 1419S.
X'Ol'
X'02'
x' 04'
X'08'
X'10'
X'20'

Device
Device
Device
Device
Device
Device

attached
attached
atta.ched
attached
attached
attached

to
to
to
to
to
to

external
external
external
external
external
external

line
line
line
line
line
line

7.
6.
5.
4.
3.
2.

Rules for Using DVCGEN

A separate DVCGEN roacro instruction is required for each device.
a 2314, each individual unit needs a DVCGEN card.

The total number must not exceed the total number of devices specified
in the IODEV parilloeter of the IOTAB macro.

DVCGEN macros must be specified in ascending channel

switchable units (attached to more than one selector channel) wust be
defined once on the lowest channel by which they are addressable.

The sequence of the DVCGEN cards determines the priority of the
devices on their channel. SYSRES should be the first DVGEN card if it
is to have the highest priority. Switchable units must be the last
devices specified for each channel, and must be on consecutive
channels.

The specifications of these rracros can be altered at IPL by ADD and
DEI. statements.

IBI-i 1052 Printer-Keyboards that are not on-line but ~:iere defined by
DVCGLN statements must be deleted by DEL statements '.Nhen performing
IPL from the card reader.

IBM S/360 DeS Sys. Gen. and Maint.

a~d.r:ess

For

:.::;cquence.

ASSIGNING SYMBOLIC DEVICE NAMES TO ACTUAL I/O DEVICES
ASSGN

This macro instruction and its parameters assign
symbolic device names (LUBs) to physical I/O
devices (PUBs). A separate macro instruction is
required for each symbolic device name with a
standard system generation assignment. This macro
instruction is optional.

Parameters for ASSGN
SYSnnn.,X'cuu'

Symbolic-name will be any of the system background
logical units (SYSIPT, SYSLOG., etc) or programmer
logical units (SYSOOO, SYS001, etc). X'cuu' is
the hexadecimal number of the channel and unit to
which the symbolic device is attached. A separate
macro is required for each standard assignment
desired.
Programmer assignments are made only for
tackground jobs.

System input/output units (SYSRDR, SYSIPT, SYSLST, or SYSPCH) that are
assigned to a tape or DASD when the system is generated will be unassigned
by IPL. An unassigned device can cause a job to be canceled.
END OF SUPERVISOR MACRO INSTRUCTIONS
SEND (n)

This macro instruction indicates the end of the
supervisor. n is a multiple of 8 and cannot be
greater than 32.,760.
Figure 2 illustrates protected and unprotected
supervisor storage generated by various
combinations of supervisor options that affect
storage protection.
The supervisor consists of two parts:
•

the nucleus that extends from the address
SYSSOO to NUCEND, and

•

the combined transient area, CE Serviceability
Programs (CE=YES), and save area that extends
from the address SYSEND to PPBEG (Figure 2A).

Macro Instructions for Generating a Supervisor

SEND
A

SYSSOO

I
Supervisor

SP =YES

SP=NO

NUCEND

NUCEND = SYSEND

SYSEND

PPBEG

L....-_ _

~I Not Used

EOSSP

- - - --2K Boundary

SEND

tBJlllli Prob lem

}

Not
Protected

Program

__________________________________

I
~

NUCEND =
SYSEND

NUCEND>
SYSEND

SEND n
--Jf\~

____________________________________

NUCEND< SYSEND
____________________
____________________
JI\~

SP =NO

~A~

\
~

SP =YES

-----------A-------------_\

I__

Portion
Overlaid

Not
Protected

Figure 2.

Unprotected Supervisor Storage Generated

SEND,SP=NO (Figure 2B)
If the operand n is not specified (Figure 2B),
the address of NUCEND equals the address of
SYSEND. Programs that are linkage edited to
the end of the supervisor begin at PPBEG
(Figure 2B).
No space is provided for
supervisor expansion, and growth in the
supervisor will necessitate re-linkage editing
user programs at ~he end of the supervisor.

e44

IBM S/360 DOS Sys. Gen. and Maint.

SENDn,NUCEND>SYSEND (Figure 2F)/
SENDn,NUCEND=SYSEND (Figure 2G)/
SENDn,NUCENDing read. The hold prevents anyone else who is using track hold
from accessing that track. The maximum number of tracks that can be held at one time is 255 and the
assumed va Iue is 1O.

={~~}

WAITM =

Specify if the abnormal termination exit functian is to be supported. The abnormal termination exit allows
the user to exit ta a user's rautine befare an abnarmal end of job causes a program to be cancelled.

{~~}

Specify if the multiple wait function is to be supported. This function allaws the user to use the WAITM
macro to wait for one of a number of events to occur.

In,n, I 1/

• DASDFP c \NO

2311

2314 ,
/2321 \

,
\ NO
'SYSFIL= (J231l}lnl,n2J)
(2314,
\

Specify if supervisory DASD file protection is handled where n,n indicates the range of channels ta
wh kh DASDs may be attached. Either 2311 or 2314 indicates fi Ie protection for 2311 and 2314. 2321
indicates fi Ie protection for 2311, 2314 and 2321 .

Specify if system input and system output (SYRDR, SYSIPT, SYSLST, SYSPCH) files may be assigned to
a 2311 or 2314. Specification for either gives support for both.
nl = residual capacity for beginning of operator notification when SYSLST assigned to 2311/2314.
100~ nl ~ 65535. If nl is omitted, 1000 is assumed.
n2 = residual capacity for beginning of operation notification when SYSPCH assigned to 2311.
100 ~ n2S 65535. If n2 is omitted, 1000 is assumed.

*Valid when 24K bytes of main storage are available.

Figure 4.

Macro Instructions for Supervisor Generation (Part 2 of 4)

IBM S/360 DOS Sys. Gen. and Maint.

Operand

Operation

Explanation
Define options and configuration requirements to be included in physical 10CS.

PIOCS

SELCH=

{YES
NO

Specify if selector channels are attached to the system

Specify if burst mode devices on multiplexor channel is supported. If 1412/1419's
are attached to the multiplexor channel BMPX=YES is not supported.

BMPX= {NO}
YES

CHANSW=

NO
RWTAU
TSWTCH

ALLOC

Specify if channel switching.

TAPE=I ;
tNO\

Specify 9- or 7-track tape. 7 indicates support for both.

Fl=nK, F2=nK

Specify storage partitioning.

10TAB

Define the necessary input/output tables for the system.

!.Q}

BGPGR=i
tn.

Specify the number of logical unit blocks (LUBs) for programmer units, i.e., the
number of symbolic programmer logical units (SYSOOO-SYSnnn).

F1PGR={~ }

Specify the number of symbolic units of the class SYSnnn for Fl.

F2PGR= { -5 l(
n .

Specify the number of symbolic units of the class SYSnnn for F2.

.5
JIB={ ~

l
f

Number of JIBs for the system. Minimum value generated is 5.

CHANQ={~ }
10DEV=

{~O }

DVCGEN

Number of entries in the channel queue. Minimum value is 6.

Specify the number of

I/o

Specify the physical I/O units attached to the system.
CHUN=X 'cuu'

Hexadecimal number of channel and unit.

DVCTYP=xxxxxx

Specify the device type. See Figure 2.

CHANSW=

{~~}

MODE=X'ss'

YES indicates that the device is attached to more than one selector channel (the
device is switchable).
1. 2400T9. MODE is used to specify the tape mode. X'CO' is the default value.
2. 240OT7. MODE is used to specify the tape mode. X'90' is the default value.
3. 2702. MODE designates the SADxxx command. X'OO' is the default value.
X'OO'SADO, X'OI' SAD1, X'02' SAD2, X'03' SAD3.
4. 2260 (Local) . MODE is used to specify the 1053 printer when CHUN=X'cuu'
refers to a 1053 attached to a 2848. This operand must be entered as
MODE=X '01' .
5. 1412, 1419, 1259 MODE designates the external interrupt bit associated with
magnetic ink character reader.
X'OI' External line 7
X'02' External line 6

Figure 4.

devices attached to the system. The minimum value is 5.

X'04' External line 5
X'08' External line 4

X'10' External line 3
X'20' Externa I line 2

Macro Instructions for Supervisor Generation (Part 3 of 4)

Macro Instructions for Generating a Supervisor

Operation

Operand

Explanation

ASSGN

SEND

Figure 4.

SYSnnn,X'cuu'

Symbol ic unit is assigned a hexadecimal channel and unit number.

[ nJ

End of supervisor macro instructions. n
gram area.

beginning address of the problem pro-

Macro Instructions for Supervisor Generation (Part 4 of 4)

Device Type

Actual Device

Cord Code
24ooT9

Assign LUBs to PUBs as standard system assignments.

Nine Track Magnetic Topes

Cord Code

Device Type

Actual Device

2311

2311 Disk Drive

DASD

2314

2314 Disk Storage Facility

DASD

2321

2321 Data Cell Drive

DASD

2671

2671 Paper Tope Reader

Paper Tope Reader

2495TC

2495TC Tope Cartridge Reader

Tope Cartridge Reader

1412

1412 Magneti c Character
Reader

Magnetic Character
Reader

1419

1419 Magneti c Character
Reader or 1259 Magneti c
Reader

Magnetic Character
Reader

1419P

Primary control unit address on
1419 Dual Address Adopter

Magnetic Character
Reader

1419S

Secondary control unit address
on 1419 Dual Address Adopter

Magnetic Character
Reader

2701 ..

2701 Line Adopter Unit

2702

2702 Transmission Control Unit

2703

2703 Transmission Control Unit

2703

Tel eprocessi ng Li nes
IBM System/360 Model 25 with
the Integrated Communication I
attachment.

7770

-:770 Audio Response Unit

Topes
2400T7

Seven Track Magnetic Topes

1442Nl

1442Nl Cord Read Punch

Cord Readers - Punches
2520Bl

2520B 1 Cord Read Punch

2501

2501 Cord Reader
Cord Readers

2540R

2540 Cord Reader

2540P

2540 Cord Punch

2520B2

2520B2 Core! Punch

1442N2

1442N2 Cord Punch

2520B3

2520B3 Cord Punch

1403

1403 Printer

1403U

1403 Printer with UCS Feature

1404

1404 Printer

1443

1443 Printer

1445

1445 Printer

1050A

1052 Printer- Keyboard

1050 Control Unit

UNSP

Unsupported Device

Unsupported. No Burst
Mode on Multiplexor
Channel

Cord Punches

Printers

Teleprocessing Lines

Audio Response
UNSPB

Unsupported Device

Unsupported with Burst
Mode on Multiplexor
Channel

7772

7772 Audio Response Unit

1285

1285 Optical Reader

2260
(Local)

2260 Display Unit

Display Unit

1287

1287 Optical Reader

2260
(Local)

A 1053 attached to a 2848.
The mode operand must be
entered as MODE =X'OI'

Optical Readers

---~----~-

* Note: A 2701 Line Adopter Unit attached to on IBM

Printer

Note: The codes used in DVCGEN macros are identical to those used in IPL statements.

Figure 5.

Device Code

IBM 5/360 DOS Sys. Gen. and Maint.

System/360 Model 25 must be placed on the
multiplexor channel.

Figure 6 shows macro instructions and parameters that generate the
supervisors supplied by IBM.

2311 DISK SYSTEM SUPERVI SOR
Operand

Operation
SUPVR

SYSTEM = DI SK

2314 DIRECT ACCESS STORAGE SUPERVISOR
Operation
SUPVR

CONFG

STDJC

Operand
SYSTEM =DISK

FOPT

PC =YES

FOPT

PC =YES,SYSFIL =2314

PIOCS

SMPX =YES, TAPE = 7

PIOCS

SMPX =YES,CHANSW = RWTAU, TAPE = 7

IOTAS

IOTAS
SEND
END

• Figure 6.

6144

SEND

8192

END

IBM-Supplied Supervisor for 2311 Disk Systems
and 2314 Direct Access Storage Facility

Macro Instructions for Generating a Supervisor

Two IBM 2311 Disk Drives

The system is supplied in two volumes.
The first volume consists of a core
image library and a relocatable library. The second volume is composed of
a core image library and a source statement library. Depending upon the
user's configuration, these packs are used in varying order.
The following is an example of one of the many possible methods for
generating a system. Figure 1 illustrates the system configuration upon
which Example One (Figure 8) is based.
The following steps are keyed to
Exanple One:

Ste~

Disk-only users receive the system on disk. Disk users with at
least one tape unit available unit receive the system on ta~e.
Before generating a system, disk-only users should have at
least one initialized disk pack (VTOC on cylinder 199).
Users with two disk drives and at least one tape unit should
have at least two initialized disk packs (VTOC on cylinder 199).
Mount the IBM-supplied core image and relocatable library
volume. Users with tape must also mount a disk pack to which the
tape is to be restored.
Before restoring the tape., the us er must ta~,:e the necessary
action to perform or bypass the initialize disk routine.

Ste~

If the disk packs have not been initialized, the
IBM-supplied volume, a self-loading tape, is capable
of initializing the packs (see Figure 8). The DLBL
cards used in the following steps must contain
the volume serial number appearing in the VOL card
of the initialize disk control cards. Any volume
serial number used in the EXTENT cards for the
following steps must agree with the volume
serial number in the VOL card for initialize disk
control cards.

If the disk packs have been previously initialized, the
initialize disk routine can be bypassed (see Figure
a). Any volume serial number used in the EXTENT cards
for the following steps must agree with the volume
serial number used when the packs were
initialized.

After step 1 is completed, the user must restore the system from
the self-loading tape to the initialized pack. This step is
omitted when a system is received on disk.

step 3

When the tape has been restored, dial the address of the system
residence disk drive into the load unit switches, and IPL to pass
control to the DOS supervisor.
See Appendix A for the IPL
control statements.

Step 4

Perform a DSERV to display the directories. After determining
which components are never to be used, perform a DELETR to delete
any relocatable component never to be used.

step 5

copy the relocatable library to a second initialized disk,
defining i t as a private relocatable library. During this

IBM S/360 DOS Sys. Gen. and Maint.

copying, the user can allocate the private library to the desired
size. When allocating the size of the private library, consider
the workfile requirements discussed in step 9. To compute the
minimum size of a library, see Allocating Library Sizes for 2311
and 2314 Disk Systems,.

For techniques on copying libraries (MERGE), see Maintenance
Procedures •
step 6

Disk only users" remove the IBM-supplied core image and relocatatle library volume" and mount the IBM-supplied core irrage
and source statement library volume.
Disk users that received the IBM-supplied systems on tape
should mount the IBM-supplied core image and source statement
litrary system tape, and can either:
a.

replace the system residence pack mounted in step 1, and
ini tia Ii ze it, or

bypass initialization (because the system residence pack
mounted in step 1 is already initialized).

step 1

After the previous step is performed" the user must restore the
system from the self-loading tape to the initialized pack.
This
step is omitted when a system is received on disk.

Step 8

When the tape has been restored, dial the address of the system
residence disk drive into the load unit switches and IPL to pass
control to the DOS supervisor.
Perform a DSERV to display the directories. Then SSERV
(display and punch) all the desired sample problems from the
source statement library into cards. Punched output includes the
sample problems with BKEND and CATALS cards. Four other books in
the source statement library that should be punched out at this
time (Z.LINKEDIT" Z.DELETECL" Z.DELETERL, and Z.DELETESL) contain
the necessary control statements to selectively linkage edit and
delete all IBM components.
The sample problem program names, and
the linkage edit and the delete book names can be chosen and
punched into the DSPCH statement(s). The sample problem program
names and the linkage edit and delete book names are shown in
Appendix C.
After these sample problems and books have been punched, they
can be deleted from the source statement library, along with
unwanted macros (e.g." those macros never to be used).

Ste~

Define workfiles for SYSLNK, SYS001, SYS002, and SYS003 to the
second drive. The workfiles SYSLNK, SYS001, SYS002, and SYS003
are defined by use of the DLBL and EXTENT cards. These cards
must be preceded by the OPTION STDLABEL or OPTION PARSTD card.

Ste~

Perform all necessary assemblies. The assemblies for the
supervisor., IOCS modules" and emulator should be performed as
separate jobs. For the information required to assemble Emulator
Programs, refer to the Emulator Program manual listed in the
Preface. The user must be careful to keep all assemblies in
order.

step 11

Assemble all user-required IOCS modules. By assigning SYSPCH to
a tape unit, the lacs modules can be cataloged to the relocatable
library without punching them on cards. The IOCS modules
required by COBOL" PL/I, and RPG" as defined in Appendix B, are
supplied in the relocatable library by IBM.
Two IBM 2311 Disk Drives

Close the tape assigned to SYSPCH and reassign SYSPCH to its
permanent assignment by using the CLOSE command.
The assembly
listings should be checked for errors before proceeding.
steT) 12

Delete unwanted macros from the source statement library, and
then create a private source statement library.
If space allows,
this copy could be made to a free area of the pack to which the
relocatatle library was copied.
For techniques on creating a new library, see Maintenance
Procedures.

step 13

This step defines the creation of the core image library of the
user's operational pack.
The user can either delete the source statement library and
reallocate the system to create a large core image library, or
reallocate to create a large core image and a small system source
statement library on the operational pack.

For techniques on creating a new library, see Maintenance
Proced ures.
step 14

During this step the user must have the core image library of his
operational pack that he is building on line, as well as his
relocatatle library.
If linkage edit work files are not assigned, they must be
assigned now.
Linkage edit and catalog the assembled supervisor (object
module from step 10) to the core image library. If the SEND
address is larger than the one used by the supervisor being
replaced, certain key programs must also be linkage edited and
cataloged to the core image library in the same job step with the
new supervl.sor. These key programs are IPL, linkage editor, and
librarian. The LINKEDIT deck punched out in step 8 contains all
of the necessary control statements to linkage edit all IBM
components shipped on the system.
If the SEND address is not
exceeded, only the supervisor need be cataloged. The new
supervisor is not cataloged until a /6 statement is read.
The
user must not attempt any other operation from the time the
supervisor and these preceding programs are cataloged until IPL
time.

step 15

Re-IPL and set t.he date (and clock if the Timer Feature is
present) •
Linkage edit and catalog any additional components desired to
the core image library.
See Appendix C for a complete list of
control cards for all IBM components to be cataloged.
Before the
next step is performed, check the linkage editor listings, and
make all necessary corrections.

step 16

Reload the tape that was assigned to SYSPCH in step 11 and assign
it to SYSIPT.
With this tape the MAINT program catalogs the IOCS
modules to the relocatable library by the control card // EXEC
MAINT.
The user may set new standard labels

C24 5033 7_Disk_Operating_System_System_Generation_and_Maintenance_Apr69 7 Disk Operating System Generation And Maintenance Apr69

C24-5033-7_Disk_Operating_System_System_Generation_and_Maintenance_Apr69 C24-5033-7_Disk_Operating_System_System_Generation_and_Maintenance_Apr69

Navigation menu

Versions of this User Manual:

Views

Navigation