Tape Drive Problem Determination

Preface

This document is intended as a basic guide to Tape Drive problem determination.

Through this document, we have tried to code the main procedures and requirements numerically. This can be useful when talking over the phone and referencing specific procedures that may be useful.

The Context of the Problem

If you ask some of the following questions, you can quickly isolate or eliminate whole areas within BRMS:

1.	Is the failure intermittent or constant?
2.	What, if anything, changed just prior to the failure? o Software or PTF levels? o Configuration? o New Users? o New hardware? o New Procedures?
3.	Can the problem be easily reproduced?
4.	Has it ever worked?
5.	Can the failing function be performed successfully another way inside the BRMS environment?

Code Levels

1.	Library Manager Code (for 3494 users only): This code resides on the PC on the 3494 device itself. It can be accessed via the SERVICE menu from the Library Manager console, and then reading the first display. It is this code that drives the 3494 at the device end.
2.	Drive firmware: This code is referred to as the drive microcode or firmware. This code is normally loaded by the SSR; however, it can also be supplied using PTFs from the IBM System i products. The code level must be obtained from the drive itself. Different model drives have different methods of displaying the level, so you must refer to the drive manual. If this is an external drive and/or library .. use the web interface to determine the current drive and/or library firmware levels.
3.	Cumulative PTF package level and level of the current backup recovery group: DSPPTF The cumulative PTF package number will be prefixed in the following way: TC - Indicates that the whole cumulative PTF package has been fully applied. TA - Indicates that only HIPER IBM OS/400 or IBM i5/OS and microcode PTFs have been applied. TL - Indicates that only HIPER microcode PTFs have been applied. WRKGRPPTF SF99954 (V7R5); SF99664 (V7R4); SF99724 (V7R3) Check for required PTFs based on the type of connection and i OS version using at: https://www.ibm.com/support/pages/ibm-i-removable-media-ptfs

The Main Problem Areas

Tape drive problems can be divided into the following distinct areas. Having established the context and code installed from Read Me First, you should be able to determine which area has the problem:

o	Failing drives
o	The Tape Code, XPF or SLIC.
o	Library Manager Code (3494 users only).
o	The Media Library Hardware
o	Performance

What to Collect

Follow the below steps to gather the following information or use QMGTOOLS to collect
the information using the following TechNote N1020143: Obtaining, Installing, and Running QMGTOOLS for the Save/Restore/BRMS Data Collection

Once you have identified the likely problem area, the following guidelines can be used to determine what to collect. Below is a complete list of common requirements for standard, less complex issues.
1. The Job Log
2. The Hardware Resources Report - DSPHDWRSC TYPE(*AHW) OUTPUT(*PRINT)
3. The QTADMPDV API - Tape Dump Flight Recorder
4. PTFs: DSPPTF OUTPUT(*PRINT)
5. PTF Group: WRKPTFGRP then F6 to print a report
6. Hardware Error Logs
7. PRTERRLOG OUTPUT(*PRINT)
8. WRKPRB
9. Library Manager (LM) Code on the 3494
10. Firmware Levels of Tape Drives and Tape Media Libraries
11. Hardware PMH/PMR information



1. The Job Log

The job log is the single most important item that is needed in almost all problems. Collect the job log for the jobs that issue an error message. The best method to obtain the job log is by using the following command for interactive jobs:

DSPJOBLOG OUTPUT(*PRINT)

For jobs submitted to batch, an increase in the visibility of messages can be obtained by changing the message logging level of the job:
 

Type choices, press Enter.                                                                                                                                                                    Accounting code  . . . . . . . .   *USRPRF                      Routing data . . . . . . . . . .   'QCMDI'  Request data or command  . . . .   *NONE  CL syntax check  . . . . . . . .   *NOCHK        0-99, *SAME, *NOCHK  Initial library list . . . . . .   QUSRBRM       Name, *SAME, *SYSVAL, *                 + for more values   QBRM                                                                                          End severity . . . . . . . . . .   30            0-99, *SAME    Message logging:                Level  . . . . . . . . . . . .   4             0-4, *SAME    Severity . . . . . . . . . . .   00            0-99, *SAME        Text . . . . . . . . . . . . .   *SECLVL       *SAME, *MSG, *SECLVL, *  Log CL program commands  . . . .   *YES          *SAME, *NO, *YES  F3=Exit   F4=Prompt  F5=Refresh  F12=Cancel  F13=How to use this display  F24=More keys

2. The Hardware Resources Report

DSPHDWRSC TYPE(*AHW) OUTPUT(*PRINT)

3. The QTADMPDV API - Tape Dump Flight Recorder

This API is available at R360 and above only. A new application programming interface is provided to gather information for OS/400 or i5/OS tape to use in debugging problems. The Dump Device (QTADMPDV) API is provided to gather debugging information for tape device and Media and Storage Extension (MSE) support. You can use the QTADMPDV API to collect information for your IBM service representative. This API should be used immediately after a suspected device and/or tape management system failure. If the API is not used immediately, other device operations can cause the flight recorders to wrap, which results in lost information. After a problem is created, use the Work with Problems (WRKPRB) command and select Option 8, Work with problem, next to the problem identifier that was created. To save the library with the information that has been collected, select Option 30, Save APAR data to APAR library. The Dump Device API currently supports the following device types:

o	Tape (TAP) devices
o	Tape media library (TAPMLB) devices
o	Optical (OPT) devices
o	Optical media library (OPTMLB) devices
o	Diskette (DKT) devices

The following is an example of a call to the API from command entry for device TAP01:

CALL QTADMPDV TAP01

Note: The information provided and the number of spooled files can change at any time. The information is intended for problem determination. The spooled files are generated in QEZDEBUG output queue in library QUSRSYS if it exists. If it does not exist, they will be generated in the user's output queue.

The Dump Device (QTADMPDV) API dumps the following information into spooled files:

o	The contents of the device flight recorder for the device specified in the parameter passed to the program.
o	QSYSARB job log.
o	QSYSOPR message queue.
o	Job logs of the active jobs that have used the device, as indicated in the flight recorder data.
o	History log (QHST).
o	Device description of the device.
o	Line, controller, and device description associated with a media library device.
o	The job log running this API.
o	Work with Configuration Status (WRKCFGSTS) listing.
o	Licensed internal code logs from the last twenty four hours.
o	Error logs associated with the device resource (and each resource within a media library device).
o	Associated internal system objects.
o	Media and Storage Extensions (MSE) flight recorder, if available. This flight recorder traces the structures passed to a tape management system registered with the registration facility and traces the response from the registered program. This flight recorder can be helpful in developing and maintaining a tape management product.

Notes:

1.

This API generates multiple spooled files and might become large depending upon the job logs that are being printed and the size of the other device information. The call can be submitted to batch if system performance is a concern. If the API is called from the system console at high priority, it might degrade performance on other critical processing. Because many and potentially large spooled files may be generated, you should ensure there is enough system DASD available to handle the request.

2.

Refer to document N1019661, QTADMPDV - XPF Tape and SLIC Tape Flight Recorders, for information on how to run the command; then collect and send the generated documents to IBM iGSC for analysis.

4. DSPPTF OUTPUT(*PRINT)

5. WRKPTFGRP then use F6 to print a report

6. Hardware Error Logs

The following commands, issued on the OS/400 or i5/OS command line, can be used to create reports of reported hardware problems:

7. PRTERRLOG OUTPUT(*PRINT)

8. WRKPRB

Often, indications of a hardware problem can be investigated by obtaining the Library Manager Transaction logs (above).

9. Library Manager (LM) Code on the 3494

The LM is controlled by an adapted PC console in the back of the 3494. In addition to controlling the robot and keeping track of the physical location of all the tapes in the MLB, the LM keeps a log of all errors and transactions that occur on the 3494. Always check the time stamps of the logs you collect to ensure they include the time of the failure. These logs should be sent to the IBM Hardware Support Center.

By contacting your hardware engineer you can ascertain which levels of Library Manager Code are compatible with which levels of SLIC. This is particularly important when planning for an upgrade.

10. Firmware levels of tape drives and tape library device

Follow the manual for the drive or library to display or collect the firmware levels using Web interface or panel.

11. Hardware Problems

If you are experiencing problems with 3494 media mounts and demounts, there might be a problem with the hardware. Alert your CE if you suspect that this might be the cause of the problem.