AUTO MODE

NOTE

For the VAX-ll/730 SBB system which has the TU80 as the removable media drive device (no RA60), the CRDs must be copied from the magnetic tape distribution media (MT #1) to the system main-tenance area ([SYSO.SYSMAINT]) on the system disk. Refer to Chapter 8 for this procedure.

CRD AUTO mode performs the following tests in the order shown:

V AX-ll/730 Systems 1 and 2

1. Tests the CPU, memory and FPA with microdiagnostics.

2. Tests the RB730 (internal disk controller) with microdiagnostics.

3. Tests the CPU with level 4 diagnostics.

4. Boots the diagnostic supervisor from the RL02.

5. Tests the DMF32 and the RB730 disk drives with macrodiagnostics.

VAX-ll/730 SBB System

1. Tests the CPU, memory and FPA with microdiagnostics.

2. Tests the CPU with level 4 diagnostics.

3. Boots the diagnostic supervisor from the disk drive (0 or 1).

4. Tests the DMF32 and the UDA50 disk drive with macrodiagnostics.

Once AUTO mode is invoked, device testing is completed without user intervention in approximately 15 minutes. An exception to this would be when the system is improperly set up. In this instance, the AUTO mode program displays an informational message and halts (Example 7-1). The operator has a chance to properly prepare the system, and resume execution of the AUTO mode by typing a <CR>. DMF32S XGAO TESTING STARTED DMF32A TXAO-TXA7 TESTING STARTED DMF32P

DMF32P

LCAO TESTING STARTED LCAO TESTING STARTED AUTO TEST COMPLETE - NO ERRORS

7.3.1 AUTO Mode Evocation

AUTO mode is invoked after system preparation is performed. The system is prepared for testing and AUTO mode is invoked by performing the following procedures:

1. Insert TU58 tape cartridge #34, labeled VAX 11725/730 CONSOLE, into TU58 tape drive 1.

2. Insert TU58 tape cartridge #36, labeled 11725/730 MICRODIAG, into TU58 tape drive

o.

3. Insert the diagnostic distribution disk cartridge into the- user disk drive. Depress the LOAD button on the disk drive to place it on-line. The disk drive mayor may not be WRITE PROTECTed.

NOTE

For the VAX-ll/730 SBB system with no RA60 disk drive (TU80 present), CRDs will execute from the system disk drive (if CRDs were copied to that disk drive).

4. Ensure that the system disk drive contains the system disk and is on-line. The system disk may or may not be WRITE PROTECTed.

NOTE

CRD AUTO mode performs nondestructive disk testing on V AX/VMS disk cartridges. If the disk which is inserted into the disk drive is formatted under systems other than VAX/VMS, WRITE PROTECT the disk to protect that data.

5. Obtain the console prompt, »>, as described in Chapter 2.

NOTE

After the console prints VERSION xx.yy, a CTRL/C may be typed since all microcode needed to execute CRDs is loaded.

6. Invoke AUTO mode by typing T to the console prompt as shown below:

»>T <CR>

NOTE

When the command, »>T, is typed, there is a time span of approximately 35 seconds before the first message is printed on the console terminal.

If no errors are encountered, the console terminal produces a printout similar to that in Example

RB730 TESTING STARTED

RL02 PART DQA1 TESTING STARTED CPU PART 3 TESTING STARTED R80 DQAO TESTING STARTED RL02 PART 2 DQA1 TESTING STARTED DMF32S XGAO TESTING STARTED

RUN TIME DMF32A TXAO-TXA7 TESTING STARTED - RUNTIME DMF32P LCAO TESTING STARTED - RUN TIME plain English messages. These consist of progress messages, warning messages, and error messages.

Progress messages are printed to assure the user that the AUTO mode CRD is progressing properly. These messages are printed when device testing is begun and completed (Example 7-2).

Warning messages are printed to inform the user that the system is improperly set up (Example 7-1).

These messages are printed in the following situations:

1. The user disk drive does not contain the proper diagnostic disk cartridge.

2. The user disk drive is off-line (LOAD button out).

3. The system disk drive is WRITE PROTECTed.

4. The system disk drive is off-line (LOAD button out).

5. The diagnostic tape in the TU58 tape drive has missing or corrupted diagnostic program files.

After printing warning messages, AUTO mode handles each of the above situations differently. AUTO mode pauses for the first two situations above to allow the user to properly set up the disk drive (Example 7-1). However, for the third and fourth situations, AUTO mode continues testing after printing a warning message. AUTO mode executes the appropriate macrodiagnostic in NOW RITE mode for the third situation (Example 7-3) and skips over the appropriate macrodiagnostic for the fourth situation (Example 7-4). Both situations result in a message that indicates testing is incomplete. AUTO mode handles the fifth situation as an error and aborts further testing (Example 7-5).

Error messages are printed when an error occurs during the course of diagnostic testing. These messages identify the device that caused the error and the next action to be taken by the user. For more error

**** BEGIN VAX-11/730,725 AUTO TEST ****

VERSION x.x RUN TIME APPROXIMATELY 15:00 MINUTES CPU PART TESTING STARTED

MEMORY TESTING STARTED

CPU PART 2 TESTING STARTED

FPA TESTING STARTED

RB730 TESTING STARTED

RL02 PART DQA1 TESTING STARTED DMF32S XGAO TESTING STARTED DMF32A TXAO-TXA7 TESTING STARTED DMF32P LCAO TESTING STARTED AUTO TEST INCOMPLETE

7.3.3 AUTO Mode Errors

Errors detected during AUTO mode cause an error message to be printed and the current diagnostic test to be aborted. Also, depending on which diagnostic test detected the error, AUTO mode aborts. If errors are· detected during the microdiagnostic or level 4 diagnostic testing, the program that detected the error along with the remaining test programs are aborted (Example 7-6). Also, if microdiagnostics attempt to test a device that is missing, other than the FPA, AUTO mode is aborted. In contrast, errors detected during macrodiagnostic testing of a device, abort only that program and not any other programs which test that device. AUTO mode then proceeds with execution of the remaining diagnostic programs (Example 7-7). However, there are some situations where AUTO mode will abort:

• Errors encountered in the diagnostic disk drive

• Improper system setup (for example, the programs to. be executed cannot be found on the diagnostic disk)

When AUTO mode testing is aborted due to microdiagnostic errors or AUTO mode completes with macrodiagnostic errors, the user is given the option of restarting the AUTO mode testing or returning to the console I/O mode (Example 7-6). This will be announced to the user after completion of testing.

**** BEGIN VAX-11/730,725 AUTO TEST ****

VERSION x.x RUN TIME APPROXIMATELY 15:00 MINUTES

CPU PART 1 TESTING STARTED RUN TIME 3:30 PASSED

MEMORY TESTING STARTED RUN TIME 1 : 30 PASSED

CPU PART 2 TESTING STARTED RUN TIME 0:45 PASSED

FPA TESTING STARTED RUN TIME 1 : 30 PASSED

RB730 TESTING STARTED RUN TIME 0:45 *FAILED*

AUTO TEST ABORTED - RB730 BAD - CALL FIELD SERVICE ENTER 1 TO RETURN TO CONSOLE, 2 TO RESTART AUTO TEST 1

**** END OF VAX-11/730,725 AUTO TEST ****

Example 7-6 Printout of an AUTO Mode Testing Sequence in Which an Error Was Detected During

Microdiagnostic Testing

**** BEGIN VAX-11/730,725 AUTO TEST ****

VERSION x.x RUN TIME APPROXIMATELY 15:00 MINUTES CPU PART TESTING STARTED

MEMORY TESTING STARTED

CPU PART 2 TESTING STARTED

FPA TESTING STARTED

RB730 TESTING STARTED

RL02 PART DQA1 TESTING STARTED DMF32S XGAO TESTING STARTED

RUN TIME

DMF32A TXAO-TXA7 TESTING STARTED DMF32P LCAO TESTING STARTED

AUTO TEST COMPLETE - XGAO BAD - CALL FIELD SERVICE

**** END OF VAX-11/730,725 AUTO TEST ****

Example 7-7 Printout of an AUTO Mode Testing Sequence on a RL02/R80-Configured System in Which an Error Was

Detected During Macrodiagnostic Testing