R9 is the controller number in hexadecimal
The codes and messages for abnormal conditions that can occur when using the on-line diagnostics facilities are listed in Table 42. (The messages reside in the system error mess-age fi Ie, ERRMS G. )
(e.g., X '000071 20' ).
RlO is the type mnemonic in EBCDIC (e.g.,
DOCS
X'OOOOC3D9' for CR).
The format for the DDCB is given in Figure 16. Following each format, the parameter fields of the DDCBare described in alphabetical order by their mnemonic. All referenced addresses have word resolution.
In either case, the return is to CAL + 1.
Abnormal
Code Subcode
09 00
09 01
09 02
09 03
09 04
09 05
09 06
09 07
09 08
09 09
09 OA
09 OB
Table 42. On-line Diagnostics Abnormal Messages
Mean ing of Code
A diagnostic close is attempting to return a nonpartitioned device.
The device referenced in the DOCB is a nonexistent device.
The device referenced in the DDCB is currently in use.
The device referenced in the DDCB is currently in use by a symbiont.
The DDCB does not contain a command list.
The command I ist was inval idated by a swap.
There are more than 12 I/O command doublewords (IOCDs).
The I/O command list is invalid due to either invalid flags, an invalid TIC address, an invalid user-specified command list address, or insufficient room in the DDCB for the command list.
An error was found during the BlIST CAL. Either an invalid page was found during physical-to-virtual or physical-to-virtual-to-physical address conversion, the status address is in error, the byte count is illegal in the IOCD, or an 10CD overlaps a page boundary.
A buffer crosses a page boundary.
The user's ID does not match the ID specified on the last operator D lAG key-in, or the user privilege level was less than AO.
The amount of avai lable core is not sufficient to allow the diagnostic program to lock itself in core.
114 Abnormal Codes and Messages/DDCB
Table 42. On-Line Diagnostics Abnormal Messages (cont.) Abnormal
Code Subcode Meaning of Code
09 OC The requested controller is not partitioned.
09 OD The device specifically requested on an open is not partitioned.
09 OE A MAP CAL error occurred due to an inval id page number during a physical-to-virtual or virtual-to-physical address conversion.
09 OF Monitor buffer space (MPOOL) is unavailable for processing the command list.
TTL
o
1 2 3 4 31TYPE DEVor OPLB
20 21 22 23 24 25 26 27 28 29 30 31
0 -8
ERA
31
4
A~:
0 1 2 3 22 23 24
Figure 16. Format of the DDCB
DDCB 115
Word 6
FlP
22 23 24 25 26 27 28 29 30 31
Word 7
Word 8
0---·---0 o
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31(may not be used)
25 26 27 28 29 30 31
11
cos
or CISo 1 4 5
Figure 16. Format of the DDCB (cont.)
116 DDCB
STA
22 23 24 25 26 27 28 29 30 31
Word 15
TAB 1
. .
o
1 2 3 I 4 5 6 7 I 8 9 10 11 1 12 13 14 15T
16 17 18 19 1 20 21 22 231 24 25 26 271 28 29 30 31Word 19
SWAPCT
21 22 23 24 25 26 27 28 29 30 31
Word 21
PRI CLIST
o
1 2 3 4 22 23 24 25 26 27 28 29 30 31Words 22 - n are used for variable length parameters
Figure 16. Format of the DDCB (cont.)
DDCB 117
FIELD
Contains the address of the user's routine that will handle abnormal conditions resulting from insufficient or conflicting information. (The monitor returns to ABA in the FPT if the abnormal condition is the result of a device abnormality.)
Indicates the assignment type currently in effect for the DCB (0 = null, 1 = file, 2 = Xerox
Indicates diagnostic device DDCB.
Contains the address of the user's routine that will handle error conditions resulting from insufficient or conflicting information.
Indicates whether the DDCB is opened or closed (0
=
closed, 1 = opened).Contains the virtual address of the user's command list.
Contains the OPlB table index of the operational label assigned to the DDCB. OPlB is only meaningful if DEVF equals O.
Specifies priority of I/O request.
Contains address of user data area used to return I/O status.
9. REAL -TIME PROCEDURES
Real-time processing involves reacting to external events (including clock pulses) within microseconds. Selected ex-ternal events are allowed to interrupt the real-time user's program so that they can be processed at the time they occur. After an interrupt has been processed, control may then return to the interrupted program or may be directed elsewhere.
In CP-V real-time processing, there are three distinct types of interrupts:
1. Real, hardware interrupts.
2. Multiple clock interval interrupts derived through soft-ware from a single hardsoft-ware clock interrupt.
3. User written pseudo-interrupts that are triggered by software rather than by hardware. This type of inter-rupt is qui te usefu I for i nterprogram communi cation and synchronization. Pseudo-interrupts use interrupt addresses XI 10001 through X'7FFF'.
Note: Any interrupt connected by real-time procedures must have a hardware priority below that of the
I/o
interrupt. Note also that the swapper performs
I/o
at a software priority of X'lO'. (This would be a consideration when specifying a priority to be as-sociated with certain real-time I/O requests; e.g., M:IDEX). advances the interrupt to the waiting state.
Waiting move to the active state when the interrupt signal is received provided that it is also in the armed state. If the interrupt is already in the waiting state, it moves to the active state when it becomes enabled, provided that no higher priority interrupt is currently active.
Disabled com-puter, which then executes the contents of the assigned in-terrupt location as the next instruction.
Cleared
VYhen an interrupt is changed from the active state to the cleared state, the interrupt states are reset so that the in-terrupt can be recognized again and the priority is reset to that of the job that was runni ng when the interrupt occurred.
Interrupt Control Slocks (ICSs)
Areas of memory set aside for use by the monitor interrupt processing routines. ICSs are established at SYSGEN.
Interrupt Label
The two-character name of an interrupt. Interrupt labels are defined at SYSGEN.