I recently did a similiar thing between our VM system running ver 2 and
our 3466/NSM (AIX) running ver 3.0.0.20 and experienced no problems.
I used the FILE designation device for both and FTP'd the file (binary)
from VM to AIX.  As others have mentioned you do have the problem of
exporting the whole thing to one (very large) file area.  The only
help in this is you can export the user's filespaces one at a time.

Also if ou can get MVS-ADSM to cooperate in writing a non-label'd tape
you may have success in reading it in on NT.

Hope this helps.     .... joe.f.

Joseph A Faracchio,  Systems Programmer, UC Berkeley
P.S>  see you at SHare in ANaheim, March 5-10. If I remember I'll be
wearing my ADSM and VM/380 license plate buttons. (sigh)


On Mon, 28 Feb 2000, Kyle Payne wrote:

> ADSMers,
>
>         Is there any way to export a node from MVS and then import it into NT?
>
>         Both ADSM servers are at V3.1.2.40.  I am using 9840 drives with both
> systems.  When you just do an export and then import you get the ANR9999D
> error "Invalid block header read from volume".   I called support and they
> mentioned that the device drivers MVS and NT use are different and as a
> result data exported from one OS can't be imported by the other using ADSM.
>
>         Basically we want to convert from ADSM on MVS to ADSM on NT or HPUX.  
> In
> either case it appears we can't move the current data over to retain the
> versioning.  Has anyone else found a solution to this problem?
>
>         I have been asked if there was some way you can use virtual volumes.  
> This
> persons idea is to send virtual volumes from MVS to NT by specifying the
> server device type for the export.  Then have NT read them in.  To my
> understanding this can't be done because there is no way to let the NT
> system use the MVS virtual volumes.
>
>         Any ideas or comments?
>
>
> Thanks,
>         Kyle
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Kyle Payne
> payne AT berbee DOT com
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>