Diagnostic Application Code Checklist

The following checklist can be helpful in ensuring successful Diagnostic Application (DA) code.

1. Code must execute Good Machine Path (GMP) testing without abending or returning an SRN under the following conditions:
   • IPL Mode: Service from hard disk.
   • Select Advanced mode.
   • Select PD mode.
   • Run a single time.

     Follow all instructions presented by the DA. If the question presented on a screen is unclear, note the ambiguity and answer the question as you understand it.

     Use wrap plugs where required. Unplug cables as required.

     Look for:

     • Spelling errors
     • Grammatical errors

2. Code must execute GMP testing without abending or returning an SRN under the following conditions:
   • IPL Mode: Service from CD-ROM and/or tape.
   • Select Advanced mode.
   • Select PD mode.
   • Run a single time.

     Use wrap plugs where required. Unplug cables as required.

3. Code must execute GMP testing without abending or returning an SRN under the following conditions:
   • IPL Mode: Normal. Run diagnostics from mounted CD-ROM.

     Note: bos.diag must be deinstalled first.

   • Select Advanced mode.
   • Select PD mode.
   • Run a single time.

     Follow all instructions presented by the DA. If the question presented on a screen is unclear, note the ambiguity and answer the question as you understand it.

     Use wrap plugs where required. Unplug cables as required.

     Look for: No system hang while DA is executing.

4. Code must execute Good Machine Path (GMP) testing without abending or returning an SRN under the following conditions:
   • IPL Mode: Service from hard disk.
   • Select PD mode.
   • Select Advanced mode.
   • Select ALL Resources.

     Follow all instructions presented by the DA. If the question presented on a screen is unclear, note the ambiguity and answer the question as you understand it.

     Look for: No interactive menus displayed while the application is executing.

Other test scenarios include:

1. Bring the device to the DEFINED State; then run diagnostics to ensure the DA causes the device to be made available. After testing is completed, ensure adapter is placed back in the DEFINED State.

2. If microcode is used by the device, rename the microcode file, run the DA, and make sure the DA reports the absence of the file.

3. Run Advanced Diagnostics on the device. When a wrap plug is called for, do not use it. Make sure an SRN is generated. Alternatively, do anything that causes an SRN to be reported. Check the SRN for accuracy.

4. Try to cause an open error by renaming device driver. Ensure that a software error is reported.

5. Place the adapter in the DEFINED state. Cause the configuration to fail by renaming the method. Observe how the DA handles this. In most instances, an SRN should be generated stating that the device could not be configured.

6. Place the adapter in the second I/O planar of a supported system. Ensure the adapter is in the DEFINED state. Run diagnostics to ensure the DA causes the device to be made available. After testing is completed, ensure adapter is placed back in the DEFINED state.