ERRORS I DEVICE TEST/OP PASSES I
3.6 TERMINATE COMMAND VERBS
The terminate command verbs cause normal termination for the individual diagnostic task or the Online Diagnostics Driver. They are as follows:
KD WD
aD
Kill Diagnostic Task Wait on Diagnostics Quit Online Diagnostics 3.6.1 KD - Kill Diagnostic Task
The KD command verb terminates diagnostic tasks, but does not affect the Online Diagnostics Driver (ODD). You can terminate one, several, or all diagnostic tasks with the KD command verb. If you have selected the execute continuously termination mode, you must either change the termi-nation mode with a CT verb or terminate the task with the KO command verb.
You must enter the device name for the task you want to terminate. When you enter the full four-character device name (for example OS01), only the task for that device terminates. When you enter the two-character device class (for example OS), all tasks for devices of that class terminate.
When you enter ALL, all diagnostic tasks are terminated.
3·24 2270532·9701
The prompts and default options of the KD command verb are as follows:
ENTER COMMAND VERB?
KD
ENTER DEVICE NAME? ALL
The following messages appear for each diagnostic task:
DEVICE xxxx TERMINATION STARTED.
ONLINE DRIVER AVAILABLE PRESS 'COMMAND' FOR NEXT COMMAND VERB.
DEVICE DIAGNOSTIC xxxx TERMINATED WITH nnnnn ERRORS, nnnnn PASSES.
where:
xxxx is the device name of the diagnostic task.
nnnnn represent the appropriate decimal numbers.
3.6.2 WD - Wait on Diagnostics
Although the WD verb is listed as a termination verb,it actually suspends execution rather than terminating it. For this reason, you normally use the WD command verb only for a batch input file to suspend the reading of the file until the device diagnostic completes execution. (The batch input file is the file specified in response to the COMMAND INPUT prompt of the XODD com-mand.) When the driver suspends reading of the batch file, the driver monitors the message queue, as if you entered a Check Message Queue (CO) command verb. When the device diagnostic terminates, the driver reads the remainder of the batch input file. If the remainder of the file con-tains a aD command verb, the diagnostic session ends. If it concon-tains another command verb, the driver reads the batch input file until the next WD command verb.
If there is no remainder of the file (the WD command verb is the last element of the file), you can continue the diagnostic session from the control terminal. This can be helpful when you need to execute batch diagnostics, but must return to interactive execution to view the diagnostics his-tory file or show device status after the batch execution.
The WD command verb prevents the aD command verb from ending a batch diagnostic session before diagnostic task completion. The following example shows a batch input file that does not contain a WD command verb. When reading this file, the driver reads and executes the 00 com-mand verb after reading the other input, thus ending the diagnostic session immediately. The disk diagnostic tasks do not execute.
XD OS YES aD
2270532-9701 3·25
The following example shows one correct usage of the WO verb. The diagnostic session ends after all the diagnostics are complete.
EXAMPLE XO MT02 YES XO
LP03 YES XO OS01, YES WO
QO
The following example shows another correct usage o't the WD command verb. In this example, several WD command verbs are In the batch Input file. The diagnostic session ends after the diag-nostic for LP01 is complete. This example does not allow multiple diagdiag-nostic tasks to execute concurrently. Using only one WO verb allows all tasks to execute concurrently and is the
recom-mended method.
EXAMPLE XO OS01 YES WO XO MT01 YES XO LP02 YES WO XO
LP01 YES WO
QO
The following example shows another correct usage of the WO command verb. The WO command verb ends the batch execution, but the diagnostic session does not end because the file contains no
aD
command verb. The driver returns control to the control terminal for further input after the diagnostic task for 0801 Is complete. This is an example of a diagnostic session that is bothbatch and interactive.
3·26 2270532-9701
EXAMPLE XD DS01 YES WD
3.6.3 QD - Quit Online Diagnostics
The QD command verb ends the diagnostic session, returning the control terminal to SCI. The tar-get devices placed in the diagnostic device state remain in that state even though the diagnostic session is over. (Use the ON command to place these devices back in the online state.)
Usually, all diagnostic tasks terminate before you enter the QD command verb. Either they termi-nate according to specified termination mode options, or you termitermi-nate them with the KD com-mand verb. However, when diagnostic tasks are still executing at the time you enter the QD command verb, the Online Diagnostics Driver terminates these tasks first before terminating itself. The driver cannot terminate interactive tasks awaiting I/O; therefore, it cannot terminate itself. The driver displays the following messages for each task it terminates:
DEVICE xxxx TERMINATION STARTED.
DEVICE xxxx TERMINATED WITH nnnnn ERRORS, nnnnn PASSES.
where:
xxxx is the device name of the target device.
nnnnn represent the appropriate decimal numbers.
When all the diagnostic tasks have been terminated, the driver displays the following message:
TOTAL NUMBER OF ERRORS REPORTED
=
nn:When the cursor returns to the terminal screen, the QD verb has completed execution, and the driver is terminated.
2270532·9701
NOTE
When you attempt to terminate the driver with a Quit Online Diag-nostics (QD) command, and diagDiag-nostics are still awaiting I/O (such as with the interactive terminal tests), the driver will not terminate.
In this situation, you have two possible ways of terminating the driver. One is to press any key on the target terminal awaiting I/O.
The other is to identify all tasks that have not been killed by using the Show Task Status (STS) SCI command. Once you have identified these tasks, kill them with the Kill Task (KT) SCI command.
3·27
A synonym table overflow can replace the total number of errors message with the following message:
0500 PARAMETER DOES NOT EXIST
This is a system message which appears on the screen as soon as the driver terminates and dis-places the errors message. You should delete unnecessary synonyms.