• Aucun résultat trouvé

THE CCL AND THE COMMAND DECODER

Dans le document 08/8 System Reference Manual (Page 119-124)

CHAPTER 5 THE COMMAND DECODER

5.3 THE CCL AND THE COMMAND DECODER

The CCL uses its own copy of the Command Decoder instead of the copy available from the Monitor. Thus, the CCL Command Decoder has several options not available via standard USR calls to the OS/8 Command Decoder, for example, multiple default extensions.

For complete information on the Command Decoder, see the OS/8 Software Support Manual.

CHAPTER 6 BATCH

6.1 INTRODUCTION

OS/8 BATCH provides PDP-8 users with a batch processing monitor that is integrated into the OS/8 monitor structure. The system is organized in such a way that it may be used in either a keyboard input configuration or as a batch stream processor.

BATCH may be run on any OS/8 memory. A line printer, BATCH will support up to 32K present in the system.

system equipped with at least 12K of although optional, is highly desirable.

of memory and any I/O devices that are OS/8 BATCH processing is ideally suited to frequently run production jobs, large and long-running programs, and programs that require little or no interaction with the user. BATCH permits you to prepare a job on punched cards, high-speed paper tape or the OS/8 system device and leave it for the computer operator to start and run.

Output is returned to you in the form of line printer and/or teleprinter listings that include program output as well as a comprehensive summary of all action taken by the user program, the monitor system and the computer operator.

BATCH provides optional spooling of output files. This feature serves to increase throughput on any system, but it is particularly valuable when a line printer is not available. BATCH also performs extensive command analysis and error diagnosis, as well as detailed interaction with the user/operator to facilitate initializing the system and establishing system parameters.

Almost any program that runs under interactive OS/8 may also be run under BATCH. Since BATCH is called from the keyboard in the same manner as any other system program, interactive users may use BATCH to execute multiprogram utility routines, even when continuous batch processing is not desired.

With a few exceptions, BATCH uses the standard OS/8 command set. This chapter assumes that you are familiar with the operation and use of

BATCH 6.2.1 Input Files

Each command in the BATCH input file occupies one file record. If the file is a punched card file, each punched card constitutes one record, which must contain one complete BATCH command. If the file resides on paper tape, disk, or DECtape, each record consists of one logical line or of all the characters between two line terminators, including the second terminator.

6.2.2 Output Files

The BATCH output file is a line printer listing on which BATCH prints job headers, certain messages that result from conditions within the input file, an image of each record in the input file, and certain types of user output. If a line printer is not present in the system, the output file is printed on the terminal.

6.2.3 I/O Devices

BATCH accepts user input files (i.e., program and data files) from any device in the OS/8 system; however, high-speed paper tape input files are not allowed when the BATCH input file also resides on high-speed paper tape. User output files may be directed to any output device in the system.

6.2.4 Spooling

You may optionally spool output files with BATCH. When you request spooling, every output file is assigned a file name from a list of names maintained by BATCH and directed to a file-structured spool device instead of to the user-specified device. Spooling of output files increases BATCH throughput when system resources are scarce and permits you to postpone slow output operations until a more favorable time. For example, you may initialize a batch processing run that generates many output listings so that it reroutes all listings from the terminal or line printer to a specified DECtape unit. You may then dump this DECtape onto the appropriate hard copy device after the run, when more time is available. The spool device may be any file-structured device you select.

To call OS/8 BATCH from the keyboard, type .R BATCH

in response to the dot generated by the OS/8 monitor. BATCH then calls the OS/8 Command Decoder to obtain its parameters, input device, and file name (if file-structured). If CCL is enabled, you may also invoke BATCH via the SUBMIT command, in which case the BATCH parameters, input device, and file name (if file-structured) are specified on the same line as the SUBMIT command.

6.2.5 Entering File Specifications

The format for a BATCH command string is:

*SPDV: (DEV:INPUT/option/option

where SPDV:

BATCH

is the device on which to spool nonfile-structured output. If you do not specify SPDV:, no spooling is performed. Note that spooling applies only to nonfile-structured output devices specified to the Command Decoder. BATCH does not spool the output of programs such as FOTP, which use a special mode of the Command Decoder.

DEV:INPUT is the input device and file if the input is from SYS:

or a device whose handler is coresident with SYS:.

The default extension for BATCH input files is .BI.

The Run-Time Options are used to specify input from the paper tape reader or the card reader. The Run-Time Options and their meanings are listed in Table 6-1.

Option

IC IE

IP IQ IT

IH IU

Table 6-1 Run-Time Options

Meaning

Read the input file from the card reader (CR8/1 or CR8/E) •

Treat OS/8 Keyboard Monitor and OS/8 Command Decoder errors as nonfatal errors. If

IE

is not specified, OS/8 Keyboard Monitor and OS/8 Command Decoder errors cause the current job to be aborted.

Read the input file from the paper tape reader.

Do not output a BATCH log. $JOB and $MSG are the only line output to the terminal.

Output the BATCH log to the terminal. You need only specify this option when a line printer is available.

If a line printer is not available, the BATCH log is automatically output to the terminal.

Process the batch input file without echoing and without sending the $JOB and $END batch monitor commands to either terminal or BATCH log.

BATCH will not pause for operator response to $MSG lines. Any attempt to use TTY:, PTR:, or CDR: as input devices to the Command Decoder in an unattended

Option BATCH is running produces unpredictable results. If you must SQUISH SYS under BATCH, place the BATCH input file at the

beginning of SYS so it will not move.

In addition, avoid moving SYS:BATCH.SV while BATCH is running.

OS/8 BATCH recognizes four monitor level commands. These commands allow routine housekeeping operations in a multi-job, batch processing environment and provide communication between the BATCH programmer and the computer operator. Table 6-2 lists the BATCH monitor commands, which may be considered as an extension of the OS/8 Keyboard Monitor command set. Note that the first character of the $JOB, $MSG, and

$END commands is a dollar sign. The BATCH monitor does not recognize the ALTMODE character.

In the current version, any record that begins with a dollar sign

Dans le document 08/8 System Reference Manual (Page 119-124)

Documents relatifs