DN11 Device Driver for RSX-11M Author: B.Hazard Date: Jan. 18, 1981 Revision: Number 1 DN11 DEVICE DRIVER FOR RSX11M, VR 3.1 - VR 3.2 PAGE 2 B. HAZARD GENERAL: The supplied tape for this driver contains the sources and indirect file for assembly prior to inclu- sion into the system. Follow the procedures outlined in the DN.CMD file for inclusion of this driver into your system. The user should first copy the DN-11 indirect file DN.CMD to a priviledged UIC on the system disk. Use the command .... >FLX /RS=(MM:) or (MT:)[311,1]DN.CMD/DO NOTE: Read comments in DN.CMD To execute the DN.CMD file and read the comments type >@DN (carriage return) The DN11 device driver was developed to support auto-call procedures under RSX-11M .The driver is imple- mented as a user written driver,non-loadable.It supports only one physical device,with a maximum of four output ports. The DN11 device must use the standard CSR addresses as recommended by D.E.C.. The four modules are serviced by a common interrupt vector in system floating vector space (starting at 300).You may select the vector to be implemented by changing the interrupt vector field in the Status Control Blocks located in the USRTB.MAC mo- dule supplied in the furnished kit. The DN11 kit includes source files for the driver as you will notice requires the conditional DN$$04 to be satisfied this may be accomplished by using the supplied indirect assembly file. SCOPE: The DN11 driver handler uses standard RSX-11M QIO functions. ATTACHES and DETACHES are not processed by the device driver. QIO$ IO.WLB, lun,ef,pri,iosb,ast, The buffer address (ba) is the address of successive bytes in the requesting task's address space containing the digits that are to be dialed. The digits should be binary in the range of 0-9,but since the DN11 interface will accept only the four least significant bits of the byte, ASCII may also work.Depending on what ACU (801) is DN11 DEVICE DRIVER FOR RSX11M, VR 3.1 - VR 3.2 PAGE 3 B. HAZARD being used, numbers greater than 9 (decimal) may be used as control characters, such as end-of-number or tandem dialing. The byte count (bc) must be the number of digits to be presented to the ACU. It must be valid reguardless of whether an end-of number digit is used. QIO$ IO.KIL,lun,ef,pri,iosb,ast Kill will abort the current operation and clear the specified unit's status. I/O COMPLETION: The DNDRV acts as any RSX-11M device driver as far as queuing and I/O completion. The following is a list of possible I/O completions. IS.SUC (+1) The operation was successful.This indicates that the called party answered, that the answer tone was success- fully detected,and modem coupler cut-through has oc- curred. IE.TMO (-74.) After the last digit was presented to the auto-dialer, no interrupt was received from the in the system unit time-out interval.That particular value is set in the SCB of the system data base for the device and may be set to a minimal value based on what type of telephone lines are being used. IE.CNR (-73.) Data line is currently occupied, either a system error in I/O queuing or the device did not successfully clear after the last operation. IE.NFW (-69.) The ACU has interrupted with Abandon Call and Retry (ACR) set. Either it did not detect answer tone, or the ACU timed out waiting for the answer tone. The time-out period may be strapped in the ACU and should be set sim- ilar to the system data base time-out value. IE.DNR (-3) Indicates a loss of power during dialing sequence or currently. This indicates that only the ACU does not have power, not the entire system. IE.ABO (-15.) The operation was aborted by the QIO IO.KIL operation, or the system just performed a power fail recovery.