5.3 Mounting a Remote Disk
Default Mount at System Initialization
At boot up, provided that the NFS server software is already running, the Adept controller performs the necessary network initialization and mounting procedure to mount the external drive(s) defined by the MOUNT statements contained in the configuration data file. See Network Configuration for details about the MOUNT statement.
If the NFS server cannot be recognized, this mount fails. A failure occurs, for example, if the server software is not running or if the server is disconnected from the network. Use the NET monitor command after startup to determine which mounts were successful. For details, see the NET monitor command documentation.
You cannot initialize the network after the V+ system has completed its initialization. You can use the PING monitor command to verify network connectivity. If a problem exists with the network connection, correct it and restart the V+ system.
Mounting by Using the FSET Monitor Command
You can use the FSET monitor command to mount a remote disk. For example, to define a new NFS mount with the device name DISK2 to access the exported directory /c of the node (server) called PC1, type
fset nfs /mount 'DISK2' /node 'PC1' /path '/c'Mounting by Using the FSET Program Instruction
Alternatively, you can use the FSET program instruction to mount a remote disk. Consider the following code example:
; Attach logical unit number for file ATTACH (lun, 4) "NFS" error = IOSTAT (lun) IF error < 0 THEN TYPE "ATTACH error: ", $ERROR(error) GOTO 100 END ; Mount remote drive FSET (lun) "/MOUNT 'DISK1' /NODE 'SERVER1' /PATH '/c' error = IOSTAT (lun) IF error < 0 THEN TYPE "MOUNT error: ", $ERROR(error) GOTO 100 ENDNOTE: You must complete the FSET instruction on one line in the actual code.