IBM B-Series, Maintenance Information

Page: 348 / 648

FID FF—Operator Action or Host Program Error
FID FF is always presented to the host. Some types of problems are also presented on the operator
panel.
|
Figure 156 on page PANEL-46 provides a log of a filtered subset of all Sense data sent to the host with a
|
FID of FF. Use this log to assist in diagnosis of a FID FF problem.
FID FF Displayed at Host and at Operator Panel
When the operator selects Force Error Dump from the Operator Services menu. Dump icon will also
light indicating that a dump is available.
Action: To remove the dump icon, the device can be powered off, then on, or the dump can be read
by the system host. The FID message can be removed without removing the dump icon by selecting
Reset Drive on the Operator Services menu.
When a FID FF appears on the operator panel with a FSC E009, it is caused by someone forcing a
check1 condition. When this happens, the service representative should look at the device error log for
ATTENTION LIBRARY messages in the same timeframe. If no relevant ATTENTION LIBRARY
messages are found in the device error log, the rest of the FID FF messages should be ignored, as
they are intended for the host program use only, and are informational in nature.
FID FF Displayed at Host Only—Not at Operator Panel
If FID FF was reported in the host error log via a SIM message, then perform the action indicated in
the SIM message codes (for example, clean drive). Refer to the MSG section.
An invalid and unsupported SCSI command or parameter was received at the device from the host.
This represents a SCSI application program software problem. Sense data exists at host.
An operator procedural problem. For example, FID FF is presented when a magazine is not in the
library and the host issues a Load command. Another example is when the operator tries to switch to
random mode when the magazine is not locked.
The service representative should look in the drive error log for any ATTENTION DRIVE or ATTENTION
LIBRARY messages (which may have caused the FID FF to be sent to the host via sense data). If any of
these ATTENTION messages are present in the error log, use that data to do further isolation for the FID
FF cause.
Suspected Microcode Problem
1. Power off, then power on the drive or library device.
2. Perform “Verify Fix” on page PROC-9, then return here.
3. If you get a FID, go to Figure 8 on page START-12 with that FID.
4. If the drive tests work OK, the fault could be a microcode problem or an intermittent hardware
problem.
Ask the customer to try to recreate the failing scenario and to collect as much job/observation
information as possible.
5. When a failure occurs, collect the information from the customer and contact your next level of
support.
PROC-8
IBM 3570 MI