VSM DFSMSdss Restore Failure with IBM ADR351E ADR370E ADR373E ADR789W
(Doc ID 1284809.1)
Last updated on NOVEMBER 06, 2019
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
On : VSM4 VSM5 VSM5C Hardware
When attempting to restore data from IBM DFSMSdss backup,
one or more the following IBM errors occurs in the job log.
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
-----------------------
Due to this issue, users may not be able to readily restore data. Job resubmission may run without errors. This issue may occur intermittently or not occur at all.
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
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |