![]() |
![]() HP OpenVMS Systemsask the wizard |
![]() |
The Question is: Am I doing something wrong or using the wrong commands? I can get the last 2 drives to mount but not the other 4. I'm stumped. The Answer is : Some of your disk devices apparently have a volume label that mimics the semantics of an OpenVMS physical disk device name, and some do not. Use the following command to MOUNT an arbitary disk device "ddcu:" and determine its volume label: MOUNT/OVERRIDE=ID ddcu: Once you know the volume label, add the command to the system startup SYSTARTUP_VMS.COM or -- if this is a cluster -- consider creating and using a locally-customized version of SYS$EXAMPLE:MSCPMOUNT.COM. If you wish, you can use the following command to change the volume label: $ SET VOLUME/LABEL=label ddcu: The typical MOUNT command is as follows: $ MOUNT ddcu: volume-label [logical-name] You could then use th logical name explicitly specified on the MOUNT command (if any) or the MOUNT-created DISK$volume-label logical name (see below) to create any additional logical names that are required. For instance: $ DEFINE/SYSTEM/EXECUTIVE new-logical-name DISK$volume-label When you mount a disk device on any recent OpenVMS version, the OpenVMS MOUNT command will transparently create both the logical name specified by the logical name parameter on the MOUNT command (if specified) and a volume logical name that is created by appending the volume label onto the string DISK$. (In the case of your volume with the volume label DKB0, the logical name generated by MOUNT would be DISK$DKB0.) For more and more specific information on MOUNT, please see HELP MOUNT or the MOUNT documentation in the OpenVMS documentation set. The OpenVMS Wizard would encourage using volume labels which related to the contents of the disk and that do not -- and this approach is solely to help reduce the confusion, there is no technical prohibition against this usage -- mimic the OpenVMS physical device naming. The OpenVMS Wizard prefers to use the DEFINE command, as the parameters on this command -- unlike the ASSIGN command -- follow the "from to" order found on most other OpenVMS commands. (ASSIGN follows the older RSX-derived parameter ordering; the "to from" parameter ordering.) This consistency can help reduce some of the confusion with parameter ordering, particularly when using parameters -- such as using device labels that closely parallel device names -- that are already somewhat confusing. Both the DEFINE and the ASSIGN commands are fully supported. When referencing devices, the OpenVMS Wizard would encourage using the DISK$label logical names and not the physical device names. This makes the effort involved in reorgnizing or in upgrading the disk storage far simpler.
|