Conference vaxaxp::vmsnotes

252.0. "BIND/NOPERMANENT different between VAX and Alpha" by UTRTSC::BARK () Wed Feb 26 1997 11:45

Hello,

According to the help in LADCP the /NOPERMANENT is default with the bind 
command.
This is what happens if you specify the default on Alpha.

On OpenVMS Alpha V6.2

$ mc ess$ladcp bind/tape/NOPERMANENT/system INFO$TK86
%LADCP-I-BIND, service bound to logical unit MAD$INFO$TK86 (_MAD8:)
$ mount/over=id MAD$INFO$TK86
%MOUNT-I-MOUNTED, TEST mounted on _MAD8: (PTGSYS)
$ dism/nounl MAD$INFO$TK86
$ backup/log/rew/ign=label login.com MAD$INFO$TK86:test.bck/save
%BACKUP-F-GETCHN, error getting device characteristics for MAD$INFO$TK86:
[000000]TEST.BCK;
-SYSTEM-F-IVDEVNAM, invalid device name

On OpenVMS Alpha V7.1

$ mc ess$ladcp bind/tape/NOPERMANENT/system INFO$TK86
%LADCP-I-BIND, service bound to logical unit MAD$INFO$TK86 (_MAD29:)
$ mount/over=id MAD$INFO$TK86
%MOUNT-I-MOUNTED, TEST mounted on _MAD29: (UTURBO)
$ dism/nounl MAD$INFO$TK86
$ backup/log/rew/ign=label login.com MAD$INFO$TK86:test.bck/save
%BACKUP-F-OPENOUT, error opening MAD$INFO$TK86:[000000]TEST.BCK; as output
-SYSTEM-F-IVDEVNAM, invalid device name

If you don't specify the /NOPERMANENT on Alpha, everything goes fine.


On OpenVMS VAX V6.2

$ mc ess$ladcp bind/tape/NOPERMANENT/system INFO$TK86
%LADCP-I-BIND, service bound to logical unit MAD$INFO$TK86 (_UTRUIN$MAD64:)
$ mount/over=id MAD$INFO$TK86
%MOUNT-I-MOUNTED, TEST mounted on _UTRUIN$MAD64:
$ dism/nounl MAD$INFO$TK86
$ backup/log/rew/ign=label login.com MAD$INFO$TK86:test.bck/save
%MOUNT-I-MOUNTED, TEST mounted on _UTRUIN$MAD64:
%BACKUP-S-COPIED, copied VMS_USER:[BARK]LOGIN.COM;42
$ dism/nounl MAD$INFO$TK86
$ mc ess$ladcp unbind MAD$INFO$TK86


Regards,

Henk Bark
Software Support Holland.

    	I believe the default was changed to /PERM for tapes but I am no
    longer associated with the project.  Your best bet is to QAR, since in
    the very least it's a doc bug.
    
    						--Doug