Systems Reference Library
IBM System/360
Disk Operating System Operating Guide
Program Numbers:
System Control and Basic IOCS Supervisor (10K)}
Supervisor (QK) 2311 Supervisor (8K)
Supervisor (8K) } Supervisor (10K) 2314.
Supervisor (12K)
Direct Access Method (DAM) Macros Consecutive Disk IOCS
Consecutive Tape IOCS .
Indexed Sequential File Management System (ISFMS) Macros
Consecutive Paper Tape IOCS Compiler I/O Modules
Magnetic Character Reader IOCS Optical Character Reader IOCS Group 1 Utilities (Disk and Unit
Record)
Group 2 Utilities (Magnetic Tape) Group 3 Utilities (Data Cell) Multiprogramming Support
Utility Macros
Vocabulary File Utility Program Tape Sort/Merge
Disk Sort/Merge Assembler
Report Program Generator COBOL
COBOL and PL/I DASD Macros FORTRAN IV
Autotest PL/I
Basic Telecommunications Access Method (BTAM) Queued Telecommunications
Access Method (QTAM)
360N-CL-453 360N-SV-473 360N-SV-474 360N-SV-475 360N-SV-486 360N-SV-487 360N-SV-488 360N-IO-454 360N-IO-455 360N-IO-456 360N-IO-457 360N-IO-458 360N-IO-476 360N-IO-477 360N-IO-478 360N-UT-46l 360N-UT-462 360N-UT-463 360N-UT-47l 360N-UT-472 360N-SM-400 360N-SM-450 360N-AS-465 360N-RG-460 360N-CB-452 360N-CB-468 360N-FO-45l 360N-PT-459 360N-PL-464 360N-CQ-469 360N-CQ-470 This reference pUblication describes the operating procedures to be followed when executing jobs in a multiprogramming environment using the Disk Operating System. Topics discussed in this reference publication include: stacked-job processing capability,
multiprogramming, both basic and queued
telecommunications capability, and functions the operator must perform to initiate system operation and to communicate with the system. A quick reference listing of all system-to-operator messages is included.
Prerequisite publications are: IBM System/360 Disk and Tape Operating Systems, Concepts and Facilities, Form C24-5030 and IBM System/360 Model 30 Operator's Guide, Form A24-3373 (or a corresponding publication).
File Number S360-20
Form C24-5022-4
DOS
PREFACE
This publication provides information necessary for executing all IBM-supplied programs in the IBM System/360 Disk Operating System. It should be used in conjunction with the appropriate
publication describing the operation of the installation's System/360.
The most significant change in this edition is the addition of batch job processing capabilities in either or both foreground partitions. Formerly, this capability was restricted to the background partition only. Other significant changes included are:
•
Simplified procedure for defining disk files.Files are now defined by the new DLBL and EXTENT commands/statements which can be used instead of the VOL, DLAB, and XTENT commands/statements used in earlier systems. Although the VOL,
Fifth Edition, February 1968
This edition, C24-5022-4, is a major reV1S10n of, and obsoletes, C24-5022-3 and Technical Newsletter N24-5299.
Changes are indicated by a vertical line to the left of the 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.
Significant changes or additions to the
specifications contained in this publication are continually being made. When using this
publication in connection with the operation of IBM equipment, check the latest SRL Newsletter for revisions or contact the local IBM branch office.
•
•
•
DLAB, and XTENT commands/statements can continue to be used, the user will recognize the advantage to be achieved by using the new
commands/statements wherever possible.
Support for the 2314 Direct Access Storage Facility.
Support for private libraries on disk (SYSSLB and SYSRLB).
Availability of system logical units (except SYSLNK) to foreground programs.
• Availability of program
checkpoint/restart facilities for foreground programs.
For a list of associated System/360 publications, see the IBM System/360 Bibliography, Form A22-6822.
Requests for copies of IBM publications should be made to your IBM representative or to the IBM branch office serving your locality.
A form is provided at the back of this publication for readers' comments. If the form has been removed, commen"ts may be addressed to IBM corporation, Programming Publications, Endicott, New York 13760.
REFERENCE PUBLICATIONS
Programmer diagnostics and information about setting up jobs are c~ntained in the specifications publication describing each of the BOS programs. A listing of these publications follows:
1. IBM System/360 Disk Operating System:
System Control and System Service Programs, Form C24-S036;
2. IBM System/360 Disk and Tape Operating Systems: Assembler Language,
Form C24-3414;
3. IBM System/360 Disk and Tape Operating Systems: COBOL Programmer's Guide, Form C24-S02S;
4. IBM System/360 Disk and Tape Operating Systems: Basic FORTRAN IV Programmer's Guide, Form C24-S038;
S. IBM System/360 Disk and Tape Operating Systems: PL/I Programmer's Gui?e, Form C24-9005;
6. IBM System/360 Disk and Tape Operating Systems: Report Program Generator, Form C26-3S70;
7. IBM System/360 Disk and Tape Operating Systems, Tape Sort/Merge Program
Specifications, Form C24-3438;
8. IBM System/360 Disk and Tape Operating Systems: Utility Programs
specifications, Form C24-346S;
9. IBM Systere/360 Disk operating System:
~utotest Specifications, Form C24-S062;
10. IBM Systerr./360 Disk Operating System:
Vocabulary File Utility Program, Form C27-6924;
11. IBM Systero/360 Disk Operating System User's Guide: Control Statement Technigue, Fqrm C20-168S.
Machine publications providing
information about the input/output devices on the system are as follows.
For card readers and card punches:
1. IBM 1442 Nl and N2 Card Read Punch, Form A21-902S;
2. IBM 2S01 Card Reader, Models Bl and B~, Form A21-9026;
3. IBM 2520 Card Read Punch, Model Bl an§
Card Punch, Models B2 and B3, Form A21-9027;
4. IBM 2540 Component Description and Operating Procedures, Form A21-9033.
For printers:
1. IBM 1403 Printer, Form A24-3073;
2. IBM 1404 Printer, Form A24-1446;
3. IBM 1443 Printer, Models 1, 2, N1, ang IBM 1445 Printer, Models 1, N1, Form A24-3120.
Also see IBM 2821 Control Unit, Form A24-3312.
For the printer-keyboard: IBM 1050 Operator's Guide, Form A24-3125.
For magnetic tape units: IBM 2400 Magnetic Tape Units and 2816 Switching Units--principles of Operation, Form A22-6866.
For disk storage and data cell drives:
IBM System/360 Component Description--2841 Storage Control Unit: 2302 Disk Storage, Models 3 and 4; 2311 Disk Storage Drive;
2321 Data Cell Drive, Model 1; 7320 Drum Storage, Form A26-5988 and IBM System/360 2314 Component Description, Form A26-3599.
For paper tape readers: IBM 2671 Paper Tape Reader, Form A24-3388.
For optical readers: IBM 1285 Optical Reader, Form A24-3265 and IBM 1287 Optical Reader, Form A21-9064w
For magnetic ink character readers: IBM 1219 Reader Sorter; IBM 1419 Magnetic Character Reader, Form A24-1499 and IBM 1259 Magnetic Character Reader component Description, Form A24-3500.
Reference Publications 3
INTRODUCTION • • • • • 7 Batched-Job Processing • • 7
Multiprograrr~ing • 7
Batch Processing • 8
Control Program Input. 9
Processing Program Input • • 10 I/O Device Assignments • • 10 COMMUNICATIONS • • • • • • 12 Messages from the System • 12 Communication to the System. • • • 13 Using the Request Key • • • 15 OPERATOR COMMAND FORMATS • 16
SYSTEM OPERATION • • 37
Starting the System (IPL Procedure). 37 RUNNING BATCH JOBS •
Example of a Job. •
Initiating Batch Processing in a
• • 38 46
Foreground Area • • • • • • . , . . • 48 Terminating Batch Processing in a
Foreground Area • • • • • • • • • • • • 49 Regaining Operator Control from Job
Control • • • • • • • • • • • • • • • • 49 Restarting a Job from a Checkpoint • • 50 System Operation Without A 1052 • • • • • 51 Linkage Editing Foreground Programs • • • 51 Single Program Initiation in a
Foreground Area • • • • • • •
Single Program Initiation Examples • Single Program Termination •
Printing Main Storage at EOJ for
51 52 53
Batched Jobs. • • • • • • • • 54 Autotest Disaster Continue Routine
<Operating Procedure). • • • 54 SYSTEM-TO-OPERATOR MESSAGES. • • 56
SUPERVISOR MESSAGES • • 57
IPL MESSAGES • • • • • 58
CONTENTS
DEVICE ERROR RECOVERY MESSAGES • 60 JOB CONTROL MESSAGES • • • • 69 LINKAGE EDITOR MESSAGES. • • 76 LIBRARIAN MESSAGES • • • • 79 LIOCS (TAPE) AND UNIT RECORD MESSAGES. • 82 LIOCS (DISK) & COMMON OPEN/CLOSE
MESSAGES. • • • • • • • 87
BTAM MESSAGES • • • • 94
MAGNETIC INK CHARACTER READER MESSAGES • 96
QTAM MESSAGES. • 97
VTOC MESSAGES. .102
PL/I MESSAGES. .103
DISK SORT/MERGE MESSAGES . .104 TAPE SORT/MERGE MESSAGES • • • • 115 UTILITY MESSAGES: FILE TO FILE AND
COPY/RESTORE. • • .117
INITIALIZE UTILITY MESSAGES. .123 ALTERNATE TRACK ASSIGN UTILITY
MESSAGES. • • • . • • • • • • • • 125 MULTIPROGRAMMING UTILITY MACRO
MESSAGES. .128
VOCABULARY FILE UTILITY MESSAGES • .131 VTOC DISPLAY MESSAGES • • .135 AUTOTEST MESSAGES. • • • .136 ASSEMBLER, FORTRAN, AND COBOL MESSAGES .140 APPENDIX A: JOB CONTHOL STATEMENTS . . • 142 APPENDIX B: SYSTEM COMMUNICATIONS • • • 146 APPENDIX C: OPERATOR-TO-SYSTE1\'1
COMMANDS • • . • • • • • • • • .14B APPENDIX D: STANDARD DASD FILE LABELS • . 158 APPENDIX E: STANDARD TAPE FILE LABELS • • 160 APPENDIX F: VTOC LISTINGS. .161 APPENDIX G: SEREP • • • • • .16L
Contents 5
APPENDIX H: DEFAULT OPERATION WITHOUT APPENDIX I -- CAUSES FOR MESSAGE OS04I .165 A 1052 PRINTER-KEYBOARD. . .163
APPENDIX J: MESSAGE INDEX • . .166 IPL Error Messages • • • • . • . 163
INDEX. • .174
Device Error Recovery Messages • • .163
BA~CHED-JOB PROCESSING
The IBM Systerr/360 Disk Operating System is designed to provide an orderly transition between programs executed in a stacked-job environment. In order that the time
interval between the execution of jobs be kept to a minimum, a control program remains in main storage during the execution of all programs in the system.
One of the main functions of the control program is to transfer control from one function to the next.
Batch processing capabilities, within the following limitations, are now
available to all three prograrrroing partitions (BG, Fl, and F2) in a
multiprogramming system, provided this option is specified at the time the system is generated. Formerly, this capability was restricted to the background partition only.
The two limitations that must be satisfied before batch processing can be undertaken in two or more programming partitions are:
1. Separate input/output files for each partition.
2. At least 10K bytes of storage for each partition.
Batch processing capabilities are
discussed in greater detail in the sections Multiprogramming and Job control. Two new operator commands, required to initiate and terminate batch processing, are discus~ed
in the section Operator Command Formats.
Because the control program resides on disk, i t must be read into rrain storage by an IPL (Initial Program Loading) procedure before the first job can be processed. A job may consist of either the execution of a single program in the system or the execution of more than one program. Each execution is called a job step. ThUS, a job consists of a series of one or more job steps.
In preparing to execute a job, the operator must be sure that:
1. Input for the control program is on the correct device. This can be a card reader, magnetic tape unit, or disk.
2. Input for the processing program is on the correct device. This can be a card
INTRODUCTION
reader, magnetic tape unit, or disk.
3. Any I/O devices referenced by the processing program have been readied.
After the operator has checked the
preceding items, his primary function is to monitor messages that may appear on the 1052 printer-keyboard, and to service, as required, ca~d reader9 and punches,
printers, magnetic tapes, disk units, etc.
MULTIPROGRAMMING
For those systems with main storage equal to or greater than 24K, the Disk Operating System offers multiprograrrming support.
This support is referred to as Fixed Partitioned Multiprograrrming, because the number and size of the partitions is fixed, or defined, during system generation. The size of the partitions may be redefined by the console operator for a specific program after system generation.
Background vs Foreground Programs
There are two types of problem programs in multiprograrrming: background and
foreground. Foreground programs may operate in either the batched-job mode or in the single-program mode. Background programs and batched-job foreground
programs are initiated by Job Control from the batched-job input streams.
Single-program foreground programs are initiated by the operator from the printer-keyboard. When one program completes, the operator must explicitly initiate the next program.
A multiprogramming environment is capable of concurrently operating one background program and one or two foreground programs. Priority for CPU processing is controlled by the Supervisor, with foreground programs having priority over background programs. All programs operate with interruptions enabled. When an interruption occurs, the Supervisor gains control, processes the interruption, and gives control to the highest priority program that is in a ready state. Control is taken away from a high priority prograIli when that program encounters a condition that prevents continuation of processing until a specified event has occurred. FOl
Introduction 7
exampleq this condition would occur when a WRITE operation is issued to a tape unit.
Control is taken away from a lower priority program when an event on which a higher priority program was waiting has been completed. In the previous example, control would return to the high priority program when the WRITE I/O operation has been executed. When all programs in the system are simultaneously waiting (i.e., no program can process), the system is placed in th~ wait state enabled for
interruptions. Interruptions are received and processed by the Supervisor. When an interruption satisfies a program's wait condition, that program becomes active and competes with other programs for CPU
processing tirre. During a fetch operation, all prograrrming is halted. Thus, programs requiring frequent fetches can adversely affect system throughput.
In addition to at least 24K positions of main storage, multiprogramming support requires the storage protection feature.
If the batch-job foreground option is selected when the system is generated, many types of programs may be run as foreground programs • . (Specifying the option causes the generation of individual communication regions for each partition.) However, the Linkage Editor and the maintenance
functions of the Librarian are restricted to the background partition. (Refer to the Disk and Tape Operating Systems ConceEts and Facilities publication, listed in the Preface, for the IBM-supplied programs that may be run in the foreground partitions.)
Figure 1 illustrates how storage is organized for various size machines. This figure shows that multiprograrrming requires at least 24K cf storage. Because the
background partition can never be less than 10K (refer to ALLOC command), i t is
possible in such a machine to have, in addition to the background area, one foreground area of 6K or two foreground areas of 4K and 2K respectively. SPI programs can be run in these foreground
areas within the limitations imposed by the remaining storage available. For a machine with at least 32K of storage, i t is
possible to have at most two batch
processing areas--one in the background and the other in a foreground area. An SPI program can be run in the remaining foreground area, if i t does not require more than 4K of storage. There is another possiblity for a 32K machine that is not illustrated in Figure 1. The background area can be 14K (required for the assembler with disk work file variants). In this case, there is insufficient storage remaining to support a second batch processing area. The remaining 8K of storage could, however, be used for SPI programs in one or two foreground areas.
In machines with at least 64K of storage, i t is possible to have all three
programreing areas operating in a batch processing environment.
BATCH PROCESSING
The execution of all batch processing
programs in either background or foreground areas is under the supervision of a control program.
The main function of the control program is to transfer control from one job step to the next. Job Control is called by:
1. The Initial Program Loader, to process the first batch job after an IPL
procedure.
2. The Supervisor, at the normal or abnormal end-of-job for all batch prograrrs.
A job may consist of either the
execution of a single program in the system or the execution of more than one program.
Each execution is called a job step. Thus, a job consists of a series of one or more
job steps.
{
SUPERVISOR
l
BACKGROUND16K 6K I 10K
I (Batch Job) I
I I _..&.., -I-FOREGROUND· TWO (SPJ)
SUPERVISOR I BACKGROUND: I FOREGROUND· ONE (SPJ) 8K : 10K I 4K 12K
I (Batch Job)
I :
I I I
Maximum Storage Capacity
I I I
SUPERVISOR I BACKGROUND : FOREGROUND : FOREGROUND· ONE (SPI) 8K : 10K : TWO 10K : 4K
I (Batch Job) I (Batch Job) I
I I I
SUPERVISOR 10K
BACKGROUND 22K (Batch Job)
FOREGROUND·TWO 16K
(Batch Job)
FOREGROUND.ON~E
16K(Batch Job)
• Figure 1. possible storage Allocation for System/360 with Various storage capacities CONTROL PROGRAM INPUT
The Job Control program requires certain input statements to exercise its control function. These statements, referred to as
job-control statements, describe each job
ste~ that is to be executed in the program.
The format of each of the job-control statements is shown in Appendix A (Figure 11) .
Each job normally contains Cl JOB, one or more EXEC's, and a /& control statement.
The other statements are optional,
depending upon the job requirements~ For example, if disk files are used DLBL and EXTENT statements may also be required.
The name of each statement and its fUnction are as follows:
Statement Function
II ASSGN Used to assign symbolic narres to physical inputloutput devices.
II DATE Provides a date for the job being executed.
II CLOSE Close either a system or programmer logical unit.
II DLBL Provides DASD (direct acceS3
II DLAB storage device) file label information.
II EXEC Always the last statement read before a prograre is executed.
It initiates the execution of a job step and can provide the name of the program to be executed.
II JOB Always the first job statement.
It provides the job name.
II LBLTYP Defines the amount of storage to be reserved at linkage edit time for ~rocessing tape and
nonsequential disk file labels~
II LISTIO Prints 1/0 assignment listings.
II MTC Initiates magnetic tape control operations.
II OPTION Establishes program options.
II PAUSE Causes the system to suspend the processing program input for operator intervention.
II RESET Resets 1/0 device assignments to the standard established at system generation time or modified by the operator.
Introduction 9
/ / RSTRT
/ / TLBL
II TPLAB / / UPSI
/ / VOL
111/ EXTENT XTENT
/&
*
Provides identification and location of checkpoint records for restarting a job, and starts the execution of the job.
Provides magnetic tape file label information.
Sets user program switch indicators used by the individual program.
Provides volume label information.
Indicates the limits of a file on a DASD unit.
Indicates end-of-data file input for a job step.
Always the last statement in every job. Indicates
end-of-job.
Used for programmer-to-operator corrments.
PROCESSING PROGRAM INPUT
A processing program can be a language translator (such as Assembler), a utility program, a sort program, or a user's
compiled program that is to be executed by the system.
As with control program input, all input for a processing program is prepared by the programmer. For example, this input can be a set of source statements to be assembled or compiled, or a set of statements
describing an input file for a utility program.
I/O DEVICE ASSIGNMENTS
Symbolic names are used to reference all input/output devices in the system. These names are divided into two classes: system logical units and programmer logical units.
A listing of the logical units, their functions, and the actual devices to which they can be assigned is shown in Figure 2.
System logical units (SYSIPT, SYSLNK, SYSLOG, SYSLST, SYSPCH, SYSRES, SYSRDR, SYSSLB, and SYSRLB) are used by the control program and by various IBM-supplied
processing programs. All of these units (except SYSLNK) can also be used by user
programs operating in the background or either foreground problem-program area.
Progra~mer logical units are defined at system-generation time for each class of problem program (background,
foreground-one, and foreground-two) to be run in the system. In a multiprogramming environrr.ent, the same SYSnnn can be defined for the background and both foreground areas. For example SYSOOO can be assigned to separate physical devices in all three program areas. The combined number of programmer logical units for all program classes defined for the system may not exceed SYSmax -- the highest numbered programmer logical unit available for a partition. SYSmax is determined by the installation at system generation time.
SYSmax is not a symbolic name.
For the convenience of the user, two additional system logical unit names are defined for batch processing programs.
These names are used only in certain Job Control statements (e.g., CLOSE, ASSGN, and EXTENT) •
SYSIN--Name that can be used when SYSRDR and SYSIPT are assigned to the same card reader, magnetic tape unit, or disk extent.
SYSOUT--Name that must be used when SYSPCH and SYSLST are
assigned to the same magnetic tape unit.
Some system logical units must be
assigned to certain selected devices. For example, the system logical unit SYSLOG is usually assigned to a 1052 printer-
keyboard. If a 1052 printer-keyboard is not available, SYSLOG must be assigned to a printer. SYSLOG can never be assigned to any other physical device.
When the system is generated, the symbolic names for the background problem-program area are assigned to certain standard physical devices. These assignments can be changed by the operator at any time the system will accept
operator-to-system communications. Device assignments made by the operator can be either permanent or temporary, i.e., they remain the same from job-to-job or are reset to the standard assignment by the next /& or / / JOB statement. The
assignments that were made during system generation become effective after an IPL.
The system logical unit SYSOUT must be a permanent assignment.
Symbolic
Function May be Assigned to Remarks
Name
"-
-
SYSRES System residence unit Disk Storage Drive: 2311 or 2314 Assignment is established by the system during an IPL and cannot be altered until another IPL occurs.
SYSRDR Job control botch job program Card Readers: 1442, 2501, 2520, or 2540 1. Tape units may be either 7- or 9-track (dual density). If 7- track, the data conversion input device Magnetic Tape Units: 2400 Series (Note 2) feature is required.
Disk Storage Drive: 2311 or 2314 2. If the 1052 printer- keyboard is inoperable, SYSRDR must be assigned to a card reader.
""-
SYSIPT Processing program input device Card Readers: 1442, 2501, 2520, or 2540 1. Tape units may be either 7- or 9- track (dual density). If 7- track, the data conversion Magnetic Tape Units: 2400 Series (Note 2) feature is required.
Disk Storage Drive: 2311 or 2314 2. If the 1052 printer-keyboard is inoperable, SYSIPT must be assigned to a card reader.
3. SYSIPT and SYSRDR may be assigned to the same physical device.
4. Required for system generation and maintenance, and language translators.
SYSIN A~ign SYSIPT and SYSRDR to Same units as SYSIPT 1. Tape units may be either 7- or 9- track (dual density). If 7 - track, the data conversion
the same physical device feature is required.
2. If the 1052 printer- keyboard is inoperable, SYSIN must be assigned to a card reader.
SYSPCH Punched output Card Punches: 1442, 2520 .. or 2540 1. Tape units may be either 7- or 9- track (dual density). If 7- track, the data conversion
--
Magnetic Tape Units: 2400 Series (Note 2) feature is required.
Disk Storage Drive: 2311 or 2314 2. If the 1052 printer- keyboard is inoperable, SYSPCH must be assigned to a card punch.
3. SYSLST and SYSPCH may be assigned to a single magnetic tape (see SYSOUT).
4. Required for system generation and maintenance, and for language translators.
-
SYSLST System output unit Printers: 1403, 1404, 144:" or 1445 1. Tape units may be either 7- or 9-track (dual density). If 7- track, the data conversion Magnetic Tape Units: 2400 Series (Note 2) feature is required.
Disk Storage Drive: 23110r2314 2. 1404 used for continuous forms only.
3. If SYSPCH and SYSLST are assigned to a tape unit, they can be assigned to the same physical device (see SYSOUT).
4. If the 1052 printer- keyboard is inoperable, SYSLST must be assigned to a printer.
5. The 1445 printer must be used as a 1443 printer.
6. Required for system generation and maintenance, and for language functions.
7. SYSLST must be assigned to a printer for fareground dump (SPI made).
SYSOUT Assign SYSPCH and SYSLST 2400 Series Magnetic Tapes only (Note 2) 1. Tape units may be either 7- or 9-track (dual density). If 7- track, the data conversion
--
feature is required.
2. If the 1052 printer- keyboard is inoperable, SYSOUT cannot be assigned.
SYSLNKI Compile link edit and execute Disk Storage Drive: 2311 or 2314 1. Must be a single extent.
--
system file
SYSLOq Operator messages Printer-" Keyboard: 1052 1. Can be used by any program.
Printers: 1403, 1404, 1443, or 1445 2. If the 1052 printer- keyboard is inoperable, SYSLOG must be assigned to a printer.
SYSSLB Contains source statement and/or Disk Storage Drive: 2311 or 2314 SYSRLB relocatable library
SYSOOO I/O operations for processing Cord Readers: 1442, 2501, 2520, or 2540 1. SYSOOO through SYS009 are the minimum number of units defined in any system.
~~Smax3 programs Card Punches: 1442, 2520, or 2540 2. Tape units may be either 7- or 9- track (dual density). If 7- track, the data conversion Printers: 1403, 1404, 1443, or 1445 feature is required.
Magnetic Tape Units: 2400 Series 3. The 1404 printer is used for continuous forms only.
Optical Reader: 1285, 1287 Magnetic Ink Character R(!aders: 1412,
1419, 1259
Disk Storage Drive: 2311 or 2314 Data Cell Drive: 2321 Paper Tape Readers: 2671 Printer- Keyboard: 1052 Data Collection System: 1030
Data Communication System: 1050 or 1060 Audio Response Units: 7770 or 7772 Selective Calling Stations: AT&T 83B3 Teletypewriter Terminal: AT&T Madels
33 and 35
Western Union Plan: 115A Outstation Binary Synchronous Communication:
System/360 (Madels 30,40,50,65,75) 1130 Computing System, 2780 Data Transmission Terminal Note 1. SYSLNK cannot be assigned to a foreground program.
Note 2. A tape written in 1600 bpi made must have a tape mark written on it before this tape can be used on a 7- track or 9- track drive operating in 800 bpi made.
Note 3. The highest numbered programmer logical unit available for a partition. SYSmax is not a symbolic name.
• Figure 2. Syrobolic Unit Names
Introduction 11
COMMUNICATIONS
MESSAGES FROM THE SYSTEM
The system corrmunicates with the operator by issuing messages on SYSLOG, normally assigned to the IBM 1052 Printer-Keyboard.
If no response or action is required, an I-indicator is included in the message and processing continues. If an operator action or reply is required, an action indicator A or D is included in the
message. The program issuing the message usually waits until the operator keys in a response. An exception would be a message indicating intervention-required action for a specific device, where the operator need only satisfy the condition (e.g. reader out of cards).
The system-to-operator messages have two basic forms. The first for~ (illustrated here) consists of a two-character program identifier (prefix), followed by a
four-character message code, and comments.
The comments can extend to more than cne line tut the program identifier and message code are not repeated on succeeding lines.
BG xxxxc [ ••• Corrments ••• ] [ ••• Corrments ••• ]
The following program identifiers are used in multiprogramming.
Identifier BG
Program
Background program Foreground-one program Foreground-two program Attention routine Supervisor
F1 F2 AR SP
The second form of system-to-operator message consists of two lines. The first line contains the program identifier and is followed by any comments. The second line consists of the message code and message.
BG [ ••• Comments ••• ] xxxxc [ ••• Message ••• ]
The message code is further divided as follows. The first character of the message code indicates the message origin, which can be cne of the following.
Oxxx Supervisor or IPL 7Dxx Disk Sort/Merge 1xxx Job Control 7Txx Tape sort/Merge 2xxx Linkage Editor 8xxx Utilities
3xxx Librarian 9xxx Autotest 4xxx Logical IOCS Axxx Assembler
5xxx PL/I Bxxx FORTRAN
6xxx RPG Cxxx COBOL
The second, third, and fourth characters of the message code are the message number.
The action indicator (c) following the message number specifies the type of operator action required.
The message itself contains all information pertaining to the operator's decision and/or action. Each operator message is listed under System-to-Operator Messages with a corresponding cause and action description.
A typical system-to-operator message in multiprograrrming format is:
BG lC10A PLEASE ASSIGN SYSRDR The characters, BG, indicate that this message was issued for a background
program. The character, 1, indicates that Job Control issued the message. The
characters, CI0, are the message number.
The character, A, indicates that operator action is required. (For example, the operator would respond by typing the
assignment for SYSRDR on the 1052.) PLEASE ASSIGN SYSRDR is the content of the
message.
When the operator is to respond to a message (or a series of messages) and there is no program-identifier prefix on the 1052, the response made is for the last message printed.
When a Supervisor routine such as OPEN or device-error-recovery is operating on behalf of a program, any rressages issued contain the identifier for the partition issuing the message.
The action indicators are as follows.
Action Indicator A-Action:
D-Decision:
I-Information:
Meaning
The operator must perform a specific manual action before continuing; for example# mounting a
magnetic tape, or readying an I/O device.
The operator must make a choice between alternate courses of action.
The message does not
require immediate operator action. For example, this type of message can be
W-Wait:
S-SEREP:
used to indicate the successful termination of a problem program.
Used when an error condition (such as an error on SYSRES) occurs that makes i t im~ossible
to continue processing.
This indicator is not printed on the
printer-keyboard.
Instead, a two-digit message is placed in byte o of main storage. The indicator W is placed in byte 1 of rrain storage.
(See low-core error messages under System-to-Operator
Messages.) The Wait state is entered, and all
interruptions are
disabled. The only way that the system can be restarted is to perform an IPL procedure.
Used when a machine condition occurs that makes i t impossible to continue processing. This indicator is not printed on the printer-keyboard, but may be displayed on the console. A two-digit message is placed in byte o of main storage. The indicator S is stored in byte 1 of main storage. A special diagnostic
storage-display program (SEREP) supplied to
customer engineers should be used when an
S-condition occurs (see Appendix G and low-core error messages under System-to-Operator Messages).
COMMUNICATION TO THE SYSTEM
There are two means of communicating with the system: job-control statements and
o~erator commands (see Appendix B).
Job-control statements are distinguished by the double slash (//), in columns 1 and 2.
Operator corrmands do not have this
characteristic. The following table shows the differences between these two forms of communication.
r----T---T---,
I I Job-Control Statement I I
I / / I Operation Code I Operand(s) I
I I I I
I I Operator Command I I
I I Operation Code I Operand(s) I L ____ i _______________________ ~ ____________ J
Operator corr.mands apply to either
background (where a~plicable) or foreground programs. They may be entered through either SYSRDR or SYSLOG. Job-control statements are issued for batched job processing programs only and are normally entered through SYSRDR. Because operator commands are acceptable at any time
operator-to-systero responses are enabled, i t is preferable to use the command whenever possible. If an operator forms this habit, i t is not necessary for him to remember when job-control statements are acceptable. Operator commands, if entered in accordance with their prescribed format, always produce the desired system action.
The operator communicates with the system by entering certain commands into the system. Corrmands are usually entered by using the 1052 printer-keyboard
(SYSLOG). Communication is possible in any of the following instances.
• The o~erator has pressed the REQUEST key (see Using the ReqUest Key).
• The programmer or operator has requested operator response by
< inserting a PAUSE statement in the
input stream for a problem program running in a batch job environment. (A PAUSE statement in the input job stream is not valid for SPI programs.)
• The operator is responding to Job Control action or decision type messages.
Once a command has been processed, the printer-keyboard is unlocked to permit the operator to issue further messages.
Operator-to-system Job Control commands are recognized on SYSRDR as well as on SYSLOG.
Each operator-to-system command consists of an operation code and one or more
operandS. The operation code describes the pending action and consists of from one to eight alphabetic characters. The operation code must be separated from the first
operand by at least one blank. Any operands that follow are separated by commas.
There are four types of operator-to- system commands. A listing of all operator-to-system commands is shown in Appendix C (Figures 13 through 16). A
Communications 13
description of all commands is contained in 0Ferator Command Formats.
1. Job Control--issued between jobs or job steps for batch processing in a
multiprogramming environffent.
2. Attention (ATTN)--issued at any time by pressing the request key on the 1052 printer-keyboard. Some of these commands can be issued only in a multiprogramming environment.
3. Single Program Initiation--may be issued only in a multiprogramming environment following the ATTN command: START [F1 or F21.
4. IPL--Initial Program Loading
By using the appropriate operator-to- system command, the operator can perform the following operations.
• Temporarily suspend processing. The PAUSE statement or command causes the system to pause between jobs (or job steps), while operating in a batch mode. A programmer may use a / / PAUSE statement to request operator action.
• End-of-block. The end-of-block
character
®
signifies the end of each operator command entered through the 1052 printer-keyboard. It is entered by holding the alter code key down and typing a 5.• Resume precessing. The eng-of-
communications character
®
signifies the end of all operator commands and causes processing to continue. It is entered into the 1052 by holding the alter code key down and typing a 5.• Cancel jobs. The CANCEL command, which can be issued at any time during the execution of a tackground,
foreground-one, or foreground-two program, terminates the execution of that job after all outstanding
interruptions have teen handled.
• Change input/output device assignments.
The ASSGN (ASSiGN) command assigns a symbolic name to a physical input/
output device. The DVCDN (QeYife Qow~)
command informs the system that a device is inoperative. The DVCUP
(DeViCe UP) command informs the system that
a
formerly inoperative device is new operational. The RESET command resets teffporary input/outputassignments to the standard established at system generation time. Any
temporary modifications made by the operator are also reset by this command.
• Perform magnetic tape operations. The MTC (Magnetic Tape Control) command performs magnetic tape operations such as rewinding tapes, rewinding and unloading tapes, etc.
• Closing files. The CLOSE command closes any magnetic tape unit assigned to SYSLST, SYS~CH, SYSOUT, SYSnnn, or to any disk file assigned to SYSRDR, SYSIPT, SYSIN, SYSPCH, or SYSLST, and allows a new device assignment to be made.
• Get information from the system. The LISTIO command prints a listing of input/output device assignments. The LOG corrmand prints all job-control statements and/or SPI commands as they occur on SYSLOG. (The NOLOG command suppresses the logging of most
job-control statements or SPI comrrands.)
• Set system values.
During IPL:
SET--Sets the value for date and time
ADD--Adds device to PUB table DEL--Deletes device from PUB table Between job steps:
SET--Sets the values for line count, UPSI bytes, time, date, record count for SYSLST=disk and SYSPCH=disk.
The SET, ADD, and DEL commands are described in the section Starting The System (IPL Procedure).
• Multiprogramming. The ALLOC, BATCH, HOLD, MAP, RELSE, START', STOP, UNA, and UNBATCH commands are valid only in a multiprogramming system.
ALLOC--Allows the operator to allocate main storage partitions to the desired sizes.
BATCH--Initiates batch job processing in BG, F2, or Fl, or continues batch processing in BG, F2, or F1 after a STOP coromand.
HOLD--Holds the current I/O assignments for the foreground area(s) until released by RELSE command.
MAP--Prints the current main storage partitions on SYSLOG.
TIMER--Internal timer support.
RELSE--Sets the current I/O assignments for the specified foreground
area(s) to unassigned at the completion of the active program for that area.
START--Starts SPI in F2 or Fl or continues processing after a STOP corrmand.
STOP--Halts batch job operation
temporarily. Job Control does not issue a read command to SYSLOG.
Batch job oFeration can be resumed following a STOP command by issuing either a BATCH or START command.
MSG--Gives control to a foreground program oFerator comrrunication routine.
UNA--Causes physical units currently assigned to a foreground area(s) under the HOLD command to be unassigned. The specified
foreground area must be inactive.
UNBATCH--Terminates batch job oFeration and releases partitions. All
logical IIO units are unassigned.
These corrmands are described in greater detail in Operator Command Formats.
Although the normal communication device is SYSLOG (1052 printer-keyboard),
operator-to-system commands (except multiFrogramming commands) are also recognized on SYSRDR.
USING THE REQUEST KEY
While processing in either the background or foreground problem areas, the 1052 printer-keyboard is locked. If the
operator presses the request key, message
1160A READY FOR COMMUNICATIONS is printed.
The keyboard is then unlocked and any valid ATTN command can be entered.
The attention request is ignored if:
1. The system is executing a condense function.
2. The system is executing are-allocation fUnction.
If the logical transient area in the Supervisor is active when the request is made, the request is held until the logical transient area is released by the problem program. There are some program failures that will never ~elease the logical
transient area. For example, the logical transient area will not be released if there is a loop in a user-label routine while opening a file. In such a case, the attention key may be pressed again. The following message will be issued:
l140D REQUEST CANCEL
The operator may either ignore the message (respond
®)
or respond with the CANCEL operation command. If the message is ignored, the original request remains pending.communications 15
OPERATOR COMMAND FORMATS
The valid operator-to-system commands are listed in Figure 3.
Some entries in the operand field of operator-to-system commands are represented in hexadecimal form. The hexadecimal form is signified by X'cuu'. The letters cuu represent the physical address of a device and can be the numeric characters 0-9 and the alphabetic characters A-F.
Each operator-to-system command is described in the following section. The conventions used to illustrate these commands are as follows:
1. Uppercase letters and punctuation marks (except as described in items 3 and 4 below) represent information that must be coded exactly as shown.
2. Lowercase letters and terms represent information that must be supplied by the operator.
3. Informaticn contained within brackets [ ] represents an option than can be included or omitted depending on the requirements of the program.
4. Options ccntained within braces [ } represent alternatives, one of which must be chosen.
5. Options that are underlined indicate the assumed value if no operand is provided.
ADD -- Add a Device to the PUB Table
ADD is an optional control command that is used to add a device (not assigned during system generation) to the PUB table. It is read from the operator communication device
(either the 1052 or a card reader) and is acceptable only during the IPL procedure.
The format of the ADD command is:
r---T---,
I operation I Operand I
~---.---+---~
IADD IX'cuu' [(k)],devicetype[,X'ss'] I
L _________ ~ _______________________________ J
X'cuu'= channel and unit numbers.
k= S, if the device can be switched (attached to two adjacent
channels). The designated channel (X'cuu') is the lower of the two channels.
k= 0-255 indicates the priority of a device that cannot be switched.
Th~ highe&t priority is O. If k is nat given, a priority of 255 is assumed. In a multiprogramming environment, all devices on a channel automatically have equal priority.
devicetype = (s€e following)
1050A for 1052 printer-keyboard 1285 for 1285 optical reader 1287 for 1287 optical reader 1403 for 1403 printer
1403U for 1403 printer with ues feature 1404 for 1404 printer
1412 for 1412 magnetic ink character reader
1419 for 1259 or 1419 magnetic ink character reader
1419P for 1419 primary control unit address on duel address adapter 1419S for 1419 secondary control unit
address on duel address adapter 1442Nl for 1442N1 card reader punch 1442N2 for 1442N2 card punch
1443 for 1443 printer 1445 for 1445 printer
2260 for 1. Local display station (no X'ss' operand required) 2. 1053 attached to 2848
(X'ss' operand required) 2311 for 2311 Disk Drive (DASD) 2314 for 2314 Disk Drive (DASD) 2321 for 2321 Data eell Drive (DASD) 2400T7 for 7-track magnetic tapes 2400T9 for 9-track magnetic tapes 2501 for 2501 card reader
2520Bl for 2520Bl card reader punch 2520B2 for 2520B2 card punch
2520B3 for 2520Bl card punch 2540P for 2540 punch
2540R for 2540 card reader 2671 for 2671 paper tape reader
2701 for 2701 Data Adapter Unit. The code '2701' should be used only for lines with the following Adapters:
IBM Terminal Adapters Types I, II, and III
Synchronous Data Adapter Type II Telegraph Terminal Adapters Types I and II
COMMAND MEANING IPL1 JC2 AR3 SPI4
WHEN ACCEPTED
ADD Add a device to the PUB table. X
DEL Delete a device from the PUB table. X During IPL SET date and clock only
SET Set values in the communication area. X5 X
- - - CLOSE Close magnetic tape input or output file or 2311. X
DVCDN Device down (not available to system). X
DVCUP Device up (now available to system). X
MTC Magnetic tape control X Between Jobs and Job Steps
RESET Reset temporary I/O device assignments to system standard.
STOp7 Stop execution of background job. X
UNBATCH7 Terminate batch processing X6
UCS Load universal character set buffer X
ALLOC7 Allocate core starage. X X Between Jobs and Job Steps and after pressing the request
key on 1052
MAP7 List core storage allocations. X X X
PAUSE Suppress processing (enter WAIT state). X X X
Between Jobs and Job Steps, after pressing the request key LOG Log (print) job control statements. X X X on 1052, and as response to system message, and during
single program initiation
NOLOG Suppress logging control statements. X X X
CANCEL Cancel execution of current job. X X X
® End - of - block or communications X X X X During IPL between Jobs and Job Steps, after pressing the
© request key on 1052, and as response to system message, and
Cancel terminal response (1052). X X X X during single program initiatiol)
ASSGN Assign logical name. X X
HOLD7 Hold current foreground assignments. X X
LlSTIO List current I/O assignments. X X
Between Jobs and Job Steps and during single program RELSE 7 Release current foreground assignments and unassign X X initiation.
them at the end of any job initiated for that area.
UNA7 Set all assignments for foreground area to unassigned. X X The specified area must be inactive.
MSG7 Give control to a foreground communication routine. X X
TIMER Transfers timer support to indicated program. X X After pressing the request key on the 1052 and during single program initiation
START7 Initiates a foreground program or resumes batch X After pressing request key on 1052 processing.
BATCH7 Initiate batch processing. X6
DLAB Disk label information. X
DLBL Disk label information. X
EXEC Initiate single program execution. X
EXTENT Disk extE!nt information. X
LBLTYP Label information. X During Single Program Initiation
READ7 Specifies a card reader from which further single X
program initiation commands are read.
TLBL Tape label information. X
TPLAB Tape label information. X
VOL Disk volume information. X
_.
XTENT Disk extent information X
I. Initial Program Loader (lPL). 5. Dote and clock only.
2. Job Control (JC). 6. Valid only if batch job foreground option was specified at system generation.
3. ATTN Routine (AR). 7. Valid only in a multiprogramming system.
4. Single Program Initiation for FI or F2.
• Figure 3. Valid operator Commands
Operator Corrmand Formats 17
2702 for 2702 Transmission Control Unit.
2703 for 2703 Transmission Control Unit 7770 for 7770 Audio Response Unit
7172 for 7772 Audio Response Unit UNSPB for unsu~~orted device attached
to Channel 0, which is either overrunnable or operates in burst mode.
UNSP for unsu~ported device. If attached to Channel 0, it is not overrunnable and does not operate in burst mode.
X'ss'= Device specifications. X'Ol' must be coded when the device type is a 2260 for 1053 attached to a 2848 Local. If absent, the following values are assumed, depending on the value specified in the DVCGEN macro at system generation time or by the ADD command at IPL time.
X'CO' for 9-track tapes X'90' for 7-track tapes X'OO' for non-tapes There are two possible device specifications for 9-track tape units X'CO' and X'C8'. By definition,
co
is the normal reset mode for the device. C8 is an alternate mode setting for 9-trackdual-density tapes only. When the system is generated, i t is possible to make an explicit selection of mode setting for each magnetic tape unit, or let the system take a standard action. If the latter action is chosen, the system will always assume CO fer the device.
X'OO', X'Ol', X'02', and X'03' are invalid as X'ss' for magnetic tape. This parameter is used to specify SADxxx
requirements for 2702 lines:
X'OO' for SADO X'Ol' for SAD1 X'021 for SAD2 X'03' for SAD3
The previous information is not accepted on the ASSGN statement.
The tape specifications are:
r---T---T---T---T----'
IDensity I I I I I
I (Bytes I I I I I
IPer I IConvert I I I
lInch) IParity IFeature ITranslate Iss I
~---+---+---+---+----~
1200 lodd Ion loff 110 I
1200 lodd loff loff 130 I
I 200 I odd I off I on I 38 I 1200 I even loff loff 120 I 1200 I even loff Ion 128 I
~---+---+---+---+----~
1556 lodd Ion loff 150 I
1556 lodd loff loff 17 0 I
1556 lodd loff Ion 178 I
1556 I even loff loff 160 I 1556 I even loff Ion 168 I
~---+---+---+---+----~
1800 lodd Ion loff 190 I
1800 lodd loff loff IBO I
1800 lodd loff Ion IB8 I
1800 I even loff loff lAO I 1800 I even loff Ion IA8 I
~----T---~---~---~---+----~
1800 Isingle-density 9-track tapes ICO I
~----+---+----~
11600lsingle-density 9-track tapes ICO I
~----+---+----~
11600ldual-density 9-track tapes ICO I
~----+---+----~
1800 Idual-density 9-track tapes IC8 I
L ____ ~ _______________________________ ~ ____ J
For 1412/1419/1259 magnetic ink readers, X'ss' designates the external bits
associated with this reader. These bits correspond to external interrupt PSw bits 26 through 31, respectively. For a 1419 equipped with the dual address adapter, this parameter is needed for both the primary and secondary control units (1419P and 1419S). The possible combinations for the device specification for the 1412/1419 are:
r---T---,
I Device I External I
I Specification I Line Number I
~---+---~
I X' 01' I 7 I
I X'02' I 6 I
I X'04' I 5 I
I X' 08' I 4 I
I X'10' I 3 I
I X' 20' I 2 I
L _________________ ~ __________________ J
The end-of-block character @ (alter code 5) must be given after each ADD command if the communication device is a printer-keyboard.
ALLOC -- Allocate Main Storage COI{lmand The ALLOC comrrand permits the operator to allocate main storage awong foreground programs (Figure 4). Any remaining storage is automatically assigned to the background area. The number of bytes to be allocated for one or both foreground areas is
specified in 2K (2048 bytes) increments.
If only one foreground area is referenced, i t is assumed that the amount of storage allocated to the other remains unchanged.
Batched-job areas can never be less than 10K. For COBOL and Assembler with taFe or disk work file variants, the batched-job area should never be less than 14K.
r---T---,
\ Operation \ Operand \
~---+---~
\ ALLOC L{Fl=nK [, F2=nKJ} \
\ \ F2=nK [, Fl=nKJ \
L _________ ~ _______________________ - - - ___ J
The value ~ must be an even integer.
The following considerations aPFly to storage allocation among foreground and background programs.
1. The storage areas must always be contiguous.
2. The maximum size of a foreground area is S10K. This restriction does not aFply to the background area.
3. To delete a foreground area from the system, an ALLOC command must be given specifying an area of OK (zero K).
4. If storage allocation was specified when the system was generated, the IPL routine determines the size of main storage and allocates the specified foreground areas downward from high main storage.
Storage will not be allocated in the following instances.
Rule 1. The allocation would cause a decrease in the storage allocated to an active foreground or
background program.
Rule 2. The allocation would result in the relocation of an active foreground prograro.
Rule 3A. A Job control allocation would reduce the background area (or foreground area(s) while operating in the batched foreground mode) to less than 10K bytes.
Supervisor Storage Protection Key: 0
Transient Areas Storage Protection Key: 0
Background Program Area Storage Protection Key: 1 Minimum Size:
10K
Permanent Storage Locations Used by CPU Program Information Block (PIB) Communications Region EXCP Routine
I/O Interruption Routine Start I/o Routine
Channel Scheduler Storage Protection (required for multiprogramming)
Supervisor Call Routine Program Check Routine Machine Check Routine External Interruption Routine Timer Services (optional)
System Loader (Program FETCH and LOAD) Resident Error Processing Routines I/O Units Control Tables (LUB/PUB/JIB/TEB)
Open Close Dump
Operator Communications Checkpoint
End of Job
Error Processing Routines Attention Routine
Job Control Linkage Editor Librarian
Insta Ilation Processing Programs
SPI Batch Mode
Foreground - two Save Area Job Contro I Program Area Prog Name
Return PSW
Storage Registers
Protection
Key: 2 Label Area (optional) Size:
2K Increments To 510K
Foreground - one Program Area Storage Protection Key: 3 Size:
2K Increments To 510K
Installation Processing Programs
Save Area Prog Name Return PSW Reg isters
Label Area (optional) Insta Ilation Processing Programs
Minimum Size:
10K Installation Processing Programs
Job Control
Minimum Size:
10K Insta lIation Processing Programs
.Figure 4. Main Storage Organization
Operator Command Formats J9
