Figure 1-26. Attention ID (AID) Configurations
Note 1. If a SIOF is executed by the channel, unchained initial status becomes ending status
(Hex) (Hex) Display Printer Procedure Condition
All Zeros X X Normal statu~ for any
(00) command other than No
Operation, Select, or Erase All Unprotected.
CE X X Normal status for a Select
(08) or Erase All Unprotected
command.
CE,DE X X Normal status for a No
(OC) Operation command.
UC BDC X X 1 A parity check was de·
(02) (20) tected on the command
byte.
UC IR X X 2 A command other than
(02) (40) Sense was addressed to a
device that the 3272 has recorded as "unavailable"
or "not ready".
UC CR X X 3 An invalid command was
(02) (80) issued to 3272.
B X X Response to a command
(10) addressed to a device
which is being serviced by 3272 or which is com-pleting a previously issued command.
B,5M X X Response to a command
(50) addressed to a device other
than device whose status is pending or device being serviced by 3272.
Note 1. If a SIOF is executed by the channel, unchained initial status becomes ending status.
Figure 1·34, Initial Status and Sense Conditions - Local
1-62
Status Display Printer Procedure Condition
x
x
Write or Erase/Write com-mand.Addressed device detec-ted a parity or cursor check during a Write, Read Buffer, or Read Modified command.
The 3272 detected a cur-sor or parity check during receipt of data stream on a Write or Erase/Write command.
The 3272 detected a cur-sor or parity check during transmission of data stream on a Read Buffer or Read Modified com-mand.
Addressed device failed to respond in a specified period of time to an Erase/Write command or an unchained Read Buf-fer, Read Modified, or Write command.
Figure 1-35 (Part 1 of 2), Ending Status and Sense Conditions
General Reference 1-53
Error
Status Sense Recovery
(Hexl (Hexl Display _Printer Procedure Condition
CE, DE, UC 1 DC X X 3 The 3272 received an
(DEI (01) illegal buffer address in
data stream of a Write or Erase/Write command, or data stream ended before providing all characters required for an SBA, RA, SF, or EUA order on a Write or Erase/Write com-mand.
CE, DE, UE 1 ,2 X X 9 The 3272 attempted to
(001 perform a Read Buffer,
Read Modified, Write or Erase/Write command but found, after returning initial status, that the addressed device was
"busy".
Notes:
1. If this status is stacked by the channel, CUE could be generated and combined with it before the stacked status is accepted by the channel.
2. Occurs if a Start 10 Fast Release (SIOFI is executed by the channel for Select, Erase All Unprotected, or No Operation.
Figure 1-35 (Part 2 of 2)_ Ending Status and Sense Conditions - Local
'-54
Error
Status 1 Sense Recovery
(Hexl (Hexl Display Printer Procedure Condition
A X An attention·generating
(801 action (e.g., program
access key has been de·
pressedl was performed by the operator.
DE X X The 3272·ta·device but·
(041 fer transfer is completed
on a Write or EraseIWrite command which did not 5tart a printer.
The device becomes
"not busy" after com·
pleting an Erase All Un·
protected command or the printer becomes "not busy" after completing a printout.
The device-to·3272 buf-fer transbuf-fer is completed on a Select command_
A device changes from
"not available" to "avail-able" or from "not ready" to "ready".
A device becomes "not busy" after having pre-viou51y sent Unit Excep-tion when the 3272 attempted to execute a command with the device when it was "busy"_
The 3272 ONLINEI OFFLINE switch is thrown from OFFLINE to ONLlNE_ This causes each "available" device to present a Device End to the channel.
A, DE X The 3272 is thrown from
(841 OFFLINE to ONLINE
and an attention-generating action (e.g., program access key has been depressed) was per-formed by the operator.
A,UC EC X X 5 An idle 3272 polled a de·
(821 (tOl vice twice and detected a
"transmit" parity check each time on the data in the device reply.
Figure 1-36 (Part 1 of 3), Asynchronous Status and Sense Conditions - Local General Reference 1-55
Error
Status 1 Sense Recovery
(Hex) (Hex) Display Printer Procedure Condition
A,UC DC,US X X 1 An idle device detected a
(82) (OC) parity check ar cursor
check in its buffer.
A, DE, UC DC, US X X 40rB A device changes from
(86) (OC) "not available" to
"avail-able" ar from "not ready" ta "ready" and has detected a parity check or cursor check in its buffer ar a printer detected parity check while printing.
A, DE, UC IR X 6 The addressed printer
(86) (40) became Not Ready (out
of paper or cover open) before completion af a print operation.
DE,UC IR X 6 A command attempting
(06) (40) to start a printer found it
Not Ready.
A, DE, UC IR, EC, US X 6 A printer became
me-(86) (54) chanically disabled during
a printout and an auto-matic recovery was not successful, the printer CARRIAGE MOTOR POWE R switch was off, ar the switch fuse was blown.
DE, UC IR, EC, US X 6 A command attempted to
(06) (54) start a print operation,
but the printer CAR-RIAGE MOTOR POWER switch is turned off.
A, DE, UC EC, US X 7 A printer character
gener-(86) (14) ator or sync check error
occurred or the printer became mechanically dis-abled during printout, but restored itself.
Figure 1-36 (Part 2 of 3), Asynchronous Status and Sense Conditions - Local
1-56
Error
Status 1 Sense Recovery
(Hex) (Hex) Display Printer Procedure Condition
DE,UC DC X X 10 During a Select or Erase!
(06) (08) Write command the 3272
(1) detected a parity or cursor error, or (2) de-tected a parity check on data received from the addressed device in reo sponse to an intern~1 poll during a command.
DE,UC DC X X 1 During a Write command,
(061 (08) the 3272 (11 detected a
parity or cursor error, or (21 detected a parity check on data received from the addressed device in response to an internal poll during a command.
DE,UC DC, US X X 1 The addressed device de·
(06) (OC) tected a parity or cursor
check while executing a Select, Write, Erase!
Write, or Erase All Un-protected command.
DE,UC DC X X 3 A Write or Erase/Write
(061 (011 command, containing a
wee with a Start Print bit, is chained to a sub-sequent command.
DE, UC CC X X 10 The addressed device
(06) (021 failed to respond in a
specified period of time to a Select, Write, Erase!
Write, or Erase All Un·
protected command.
DE,UE X 9 The 3272 attempted to
(05) perform a Select or Erase
All Unprotected com·
mand, but found, after returning initial status, that the addressed device was busy.
CUE X X The 3272 had been
(201 addressed while busy, but
is now not busy and is free to accept a new com·
mand.
Note 1: If this asynchronous status is stacked by the channel, an asynchronous eUE could