• Keine Ergebnisse gefunden

UTPUT BUFFER Alphanumeric output buffer

Im Dokument mitra 15 (Seite 184-190)

r~·OA #CSCAl I OlO @#CTAB, X

BINARY 0 UTPUT BUFFER Alphanumeric output buffer

Bi na ry input buffer

Alphanumeric input buffer

Read command

4057 U

M:LO Alphanumeric output

l

Input of a 16-byte binary record from M:BI

- When the %EOD group is detected in a record heading, the C B event byte (byte 0) is forced to 41 hexadecima I a nd represents a n II end-of-fi Ie" mark.

• Binary input. Code &00

- The data are read one character at a time. The transfer is terminated when the specified number of characters has been reached.

- The "TAPE OFF" or "NULL" characters included in a record heading are neither transmitted to the user nor counted in the total number of characters specified for the transfer.

- When the %EOD group is detected in a record heading, the event byte (CB byte 0) is forced to 41 hexadecima I representing an "end-of-fi Ie" mark.

VIII-5.3. 60 char./sec. paper tape punch handler (# 15 060)

• General

- This handler controls the binary or alphanumeric output on paper tape (T:PP), each of these functions being determined by the selected operational label, by its assignment and by the function byte (two elements of the I/O CB).

- For alphanumeric output, the ISO 7-bit code is used (ASCII). The ASCII-EBCDIC code conversion is performed by the handler, since the internal code is always EBCDIC.

• Functions

The avai lable command byte is &80 (write)

• Alphanumeri c output. Code &80.

- The output is made one character at a time, each character bieng converted in ASCII at transfer time without any modification of the user's buffer. The transfer is terminated when the specified number of characters has been reached. No filtering is made.

- When the %EOD group is written in a record heading, the CB event byte (byte 0) is forced to 41 hexadecimal representing an "end-of-file" mark.

• Binary output. Command &80.

- The output is made one character at a time and the transfer is terminated when the specified number of characters has been reached.

VIII-5.4. 300 char./sec. card reader handler (# 15120)

• General

- This handler controls the binary or alphanumeric input from the cards (T:CR), each of these functions being determined by the selected operational label, by its assignment and by the functio~ byte' (two elements of the I/O CB).

- For alphanumeric input, the EBCDIC card code is used on a one character per column basis (80 characters).

- For binary input, each card contains up to 120 bytes.

• Functions

The available command byte is &00 (read).

• Alphanumeric input. Code 00.

- 80 characters are read.

VIII-17

4057

U

- When the %EOD group is detected in a record heading, the CB event byte (byte 0) is forced to 41 hexadecima I representing an "end-of-fi Ie" mark.

• Binary input. Code 00.

- 120 bytes are read.

- When the %EOD group is detected in a record heading, the C B event byte (byte 0) is forced to 41 hexadecimal representing an "end-of-file" mark.

Note that, in this case, %EOD is a 4-character group, punched in the first four columns of the card (i • e. the fi rst six bytes in bi na ry rea di ng mode).

Thus, the EOD mark is the same in binary and alphanumerical reading.

VIII-S.S. 200 I.p.m. printer handler (# 15412)

• General

This handler controls the alphanumerical outputs on the line printer (T:LP).

The print line is 132 characters long.

The a Iphanumeric output code is the ISO 7-bit standard code (ASCII). The user's buffer may be coded in ASCII or EBCDIC.

- EBCDIC-coded buffer. This is the most frequent case

The user must use an alphanumeric operational label (M:LO, etc.). The EBCDIC - - ASCII conversion is performed by the handler in the buffer before the output transfer. The reciprocal ASCII - - EBCDIC conversion will be performed by the handler at the end of the transfer. This double conversion has no effect on the fi na I contents of the buffer.

- ASCII-coded buffer

The user must use a binary operational label (M:BI, etc.); no code conversion is performed.

• Functions

• Avai lable commands:

Hexadecima I code Function

80 Write without format

90 Write with format

o Write without format mode

A peper feed is executed after the requested printing.

• Write with format

The first byte in the user's buffer will specify a paper positioning operation executed before the actual printing.

This skip code is conted in the number of transferred bytes.

The printing operation is normally followed by a paper feed, except when the format byte contains EO or 60 (EBCDIC code).

Table of format byte coding (skip codes)

4057 U

0 Event byte

Indi cators

2 Command or function

3 Operational label

4

!

Buffer address

5

6

!

N umber of bytes to be transferred

7

8

!

Branch address on abnorma I end

9

10

!

Disk-address {sector number}

11

The transfer is always initiated at the beginning of a sector. If the requested byte number is not a multiple of 256, the last sector which is only partly occupied, is filled with zeroes. Thus, the modified memory area is always a multiple of 256.

The transfer being executed one word at a time, the byte count in the C B must be even.

This handler considers the disk as an ordinary device; the MTRD handler, which is more powerful, performs the disk area management tasks.

• Functions

• Avai lable commands:

Hexadecimal code Function

00 Read

10 Read and update disk-address

80 Write

90 Write and update disk-address

• Disk-address update:

For 10 and 90 command codes, the disk-address of the CB is incremented by the number of transferred-sectors. This updating function may simplify the following transfers.

mitra 15

Im Dokument mitra 15 (Seite 184-190)