VSM DFSMSdss Restore Failure with IBM ADR351E ADR370E ADR373E ADR789W

Asset ID:	1-72-1284809.1
Update Date:	2011-01-25
Keywords:

Solution Type Problem Resolution Sure

Solution 1284809.1 : VSM DFSMSdss Restore Failure with IBM ADR351E ADR370E ADR373E ADR789W

Applies to:

Sun StorageTek VSM System - Version: 4 to 5C - Release: 4.0 to 5.0
IBM z/OS on System z
IBM operating system platform z/OS 1.11 or z/OS 1.12
IBM host software DFSMSdss

Symptoms

Error
=== ODM Issue Clarification ===

On : VSM4 VSM5 VSM5C version, Hardware

When attempting to restore data from IBM DFSMSdss backup,
one or more the following IBM errors occurs in the joblog.

ERROR
-----------------------
ADR351E (ttt)-mmmmm(yy), UNEXPECTED END OF FILE ON DDNAME ddname

ADR370E (ttt)-mmmmm(yy), INVALID SEQUENCE NUMBER ON DDNAME ddname LAST
nnnn1 NEXT nnnn2

ADR373E (ttt)-mmmmm(yy), REQUESTED TRACK { c:h | (SOME)} NOT ON INPUT
DDNAME ddname

ADR789W (ttt)-mmmmm(yy), RESTORE PROCESSING COMPLETED FOR CLUSTER
cluster_name, RECORD COUNT DOES NOT MATCH. INPUT RECORD COUNT IS
record_count OUTPUT RECORD COUNT IS record_count

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users may not be able to readily restore data.

Changes

The issue occurs in the following environment:
1. Microcode level prior to D02.11.18.00 is on the VSM.
2. Data is backed up on the VSM using IBM DFSMSdss software.
3. IBM DFSMSdss restore failures occur in z/OS 1.12 or after application of toleration maintenance APAR OA30822 in z/OS 1.11.

Cause

Cause Determination
=== ODM Cause Determination ===

The issue is caused by the following setup: IBM DFSMSdss restore failures occur in z/OS 1.12 or after application of toleration maintenance APAR OA30822 in z/OS 1.11 on the VSM hardware only with microcode prior to D02.11.18.00.

Cause Justification
=== ODM Cause Justification ===

The following justifies how the issue is related to this specific customer:
IBM DFSMSdss restore failures occur in z/OS 1.12 or after application of toleration maintenance APAR OA30822 in z/OS 1.11.

Note: The IBM DFSMSdss backup has no data integrity issues. This problem is intermittent during read of the data chains while attempting to perform restore of data.

Solution

=== ODM Solution /Action Plan ===

To implement the solution, please execute the following steps:

1. Verify field support has upgraded the microcode to D02.11.18.00 or higher on the VSM.

2. Run the restore jobs that had previously failed.

3. Once the jobs complete, confirm that the job ran successfully.

4. Once the issue is confirmed to be resolved, migrate to other environments if need be.

Note: To workaround the problem until the solution is implemented, submitting the job again will typically result in a successful restore.

Note: If the configuration includes Brocade Fabric OS, additional actions may need to be considered. Fixes for DFSMSdss errors have been identified by Brocade, particularly in configurations with channel extenders. The most recent fix is included in a maintenance build on top of v6.4.0c. This build may be needed to address issues identified after the release of v6.4.0c. The official supported code is v6.4.0c. Please contact Brocade for further information.

Attachments

This solution has no attachment