A PC AUTOEXEC.BAT file containing two or three records may be used to start the DACU at power-on or system reset time. The first record invokes the bring-up diagnostics, the second invokes the DACU functional code, and the third
(optional) can invoke user set-up code.
An easy way to create an AUTOEXEC.BAT file is as follows:
Place the diskette which is to contain the AUTOEXEC.BAT file in the diskette drive and enter the following:
COPY CON AUTOEXEC.BAT
Then type the lines of the AUTOEXEC.BAT ending each line by pressing the ENTER key. When the last line has been entered, press the F6 key, and the new AUTOEXEC.BAT file will be stored.
The first record has the format RASMONn XXXX
This record invokes the bring-up diagnostics which perform a checkout of the DACU. If an error is found, the diagnostic program will display a message and wait for operator intervention before continuing.
The second record invokes the DACU functional code. It has the following format:
DACUnn uuoor
The value for "nn" is set by the manufacturer. The value for "uu" is the starting channel unit address in hexadecimal. This must match the address configuration set up as described in "DACU Channel Address Set-Up" on page 93.
The value of "00" determines some of the run-time options for the functional code.
The value is a hexadecimal representation of a bit mask where each of the bits is described below.
• Bit 7 (most significant) - Not used.
• Bit 6 - Not used.
• Bit 5 -If on, warning messages will be logged to diskette when they occur.
• Bit 4 -If off, an in-memory trace table is kept. This table contains a pointer to the last 200 messages (informational and warning) that have been issued by the functional code. If Bit 4 is on, no trace table is kept. This bit should be turned on, except when debugging, since logging of the messages uses a significant amount of the processing resource.
• Bit 3 -If on, execution will stop after displaying a message. Execution will resume when the operator presses any key.
• Bit 2 -' If on, the functional code will terminate execution and return to DOS after a warning message.
• Bit 1 - If on, display of informational messages will be suppressed, but messages will logged on diskette (if logging enabled). This bit should always be on.
• Bit 0 -If on, display of warning messages will be suppressed. If off, warning messages are displayed and an audible alarm is sounded.
The value for "r" may be either "R" or blank. If the user includes a third
(optional) record in the AUTOEXEC.BAT file to invoke user code setup, then this field must be an "R." If a blank is in this field, the third record should not be included in the AUTOEXEC.BAT file.
Following is an example of an AUTOEXEC.BAT file. In this example, the DACU is attached to the channel at base address x20, it is desired to keep an internal trace of messages, and customer supplied local code (called USER) is to be invoked.
RASMONn X DACUnn 2002R USER
DACU Keyboard Controls
Operator controls available through the keyboard of the DACU System Unit controlling the DACU are described below.
At any time that the System Unit is not servicing interrupts, the DACU functional code polls the keyboard for single keystrokes. The keystrokes are interpreted as
to be re-booted. If pressed after local code is loaded when using DOS 1.1, only the local code leaves metnory.)
0,1,2,4
=
Send attention to host for device 0, 1, 2, or 4, respectively.
5,6,7,9 =
Send Device End for device 0, 1, 2, or 4, respectively.
R
=
Return to DOS, but remain resident (same as R-option when starting DACU).I
=
Suppress informational messages (also controlled by input parameters) .W = Suppress warning messages. (also controlled by input parameters).
D
=
Display all messages. (also controlled by input parameters).P = Display trace log (if tracing is active).
Chapter 6. Customer Problem Analysis and Resolution
The customer is responsible for installation and maintenance of the DACU.
Support will be provided in the form of initialization and extended diagnostic programs and a field replacement strategy for failed replaceable units.
The power-on initialization tests (bring-up tests) are invoked by the
AUTOEXEC.BAT file by including a parameter with the call for the diagnostic (e.g., "RASMONn XXXX"). Any test, including the extended tests, can be manually executed by invoking the diagnostics with no parameters RASMONn") from the keyboard and making the necessary responses to the prompts from RASMONn.
Diagnostic selftest code of two types will be provided with the DACU
-power-on initialization tests and extended tests for problem isolation. The intent of the initialization tests is to determine if the DACU is capable of operating
correctly. If an initialization test detects an error, the operator will be notified of the error. The operator may be able to either continue the initialization sequence or abort the initialization in order to execute the extended tests. The extended tests will allow the operator to determine if the DACU is failing or if an I/O device attached to the DACU has failed. These tests are organized into logical sections such that the failure can be isolated to a replaceable unit. The extended tests may require the operator to detach cables or install wrap cables to complete the tests.
See "Diagnostic Procedures" on page 117 and "Problem Determination Procedures" on page 107 for a complete description of the diagnostics and problem determination procedures.