I've got a site that is trying to use their VM system (4.4 on an IFL) to
stage MVS volumes for disaster recovery.
They dump the MVS system off using DFDSS, and restore them onto the
disaster system using standalone DFDSS under VM
This way they don't need to actually run and licence MVS on the recovery
CPU, since MVS only runs during the actual tests. The staging allows them
to drop the recovery time considerably.
And the VM system is running on the IFL on the box.
They have dumped the MVS volumes to tape using DFDSS.
And are attempting to use a standalone version of DFDSS to place the
volumes onto DASD attached to the VM image.
The DFDSS being used is from a z/OS 1.7 system, they genned it onto a DAS
D
volume and moved it to the new VM system and IPL the DASD to bring DFDSS
up to do the restore.
The old CPU was a z900 and this worked just fine.
Since the move to a z9-BC however, they get:
HCPMCV1459E The
virtual machine is placed in check-stop state due to a system
malfunction with CPU 00.
When they attempt to IPL the Standalone DFDSS code.
Has the IBM IFL code on the z9 series changed?
Anybody have any other suggestions?
Brian
