[Info-vax] Sanity check: SIMH , NFS and disk sizes

[JF Mezei]

Could someone confirm that the following would work properly ?

I heeded the following paragraph (all 3 options when using MAKE.)

##
To compile the VAX, you must define VM_VAX and USE_INT64 as part of the
compilation command line. To enable extended file support (files greater
than 2GB), you must define USE_ADDR64 as part of the command line as well.
##

Cluster of VAX (VELO) and ALPHA (CHAIN).
            2g drive        2 * 30gig drives.


>From CHAIN (Alpha VMS 8.3, TCPIP Services 5.6)

$TCPIP MOUNT DNFS1:/HOST=BRAKES/PATH="/"-
                    /UID=501/GID=501/SERVER=UNIX/STRUCT=5
$LD CREATE dnfs1:[000000]disk2.ods/size=<30gigs worth of blocks>
$LD CONNECT dnfs1:[000000]disk2.ods LDA1
$MOUNT/FOREIGN LDA1:
$BACKUP/IMAGE/IGNORE=INTERLOCK/NOALIAS  $disk2 LDA1:
$DISMOUNT LDA1:

Then, in SIMH:

simh> SET RQ0 rauser=<30 gigs worth of blocks>
simh> ATTACH RQ0 /disk2.ods


I know VAX-VMS 7.3 is able to access 30 gig drives. But will simh,
compiled with the above options have any problems with it ?


Also, when I do the BACKUP/IMAGE, it is possible to downgrade from ODS-5
to ODS-2 ? (since this would be accessed only by a VAX afterwards).

As well, it is possible to search a disk for any/all files whose name is
not ODS-2 compliant ? (Goal is to rename such files to ODS-2 names
before the transfer to the ODS-2 disk).

Will thsi work, or is there some show stopper because of maximum file
sizes etc ?