hercules-390 / hyperion

Hercules 390
Other
253 stars 70 forks source link

Standalone restore of DASD with DFSMSdss fails in z/VM 6.3 guest #257

Open fbi-ranger opened 6 years ago

fbi-ranger commented 6 years ago

Short description: Restore of ADRDSSU dump file under Hyperion with z/VM in virtual guest fails with message of unsupported dump format. Same scenario under zPDT and z/VM succeeds.

Environment OS: z/VM 6.3. IPL of SA version of DFSMSdss (SA version built from zOS 2.3) in virtual guest is successful.

Under Hyperion executing the restore (3390-9 DASD: ZASCAT 520C) fails with error:

ENTER INPUT/COMMAND: restore frmdev(tape) frmadr(761) toadr(520C) nvfy RESTORE FRMDEV(TAPE) FRMADR(761) TOADR(520C) NVFY ADRY003D 520C REPLY Y TO ALTER VOLUME CONTENTS, ELSE N ENTER INPUT/COMMAND: y Y ADRY501I 0761 DUMP DATA SET IS NOT A SUPPORTED FORMAT ADRY509D DO YOU WISH TO CONTINUE? REPLY Y OR N ENTER INPUT/COMMAND:

Doing the SAME restore under Hercule without z/VM WORKS CORRECTLY.

Assumption: DFSMSdss dump file is correct but there is a different behaviour between zPDT and Hercules either caused by SIE and CCW translation or 3590 device support.

The CCW traces are provided at https://gist.github.com/fbi-ranger/59b68a47eb73af85e085573a2bbae121

Note: The native trace does not contain the complete restore of the DASD.

UA 760: IPL device to load SA ADRDSSU UA 761: ADRDSSU tape file Both are 3590 devices

BR Florian