From: CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 22-SEP-1989 11:46 To: MRGATE::"ARISIA::EVERHART" Subj: Re: BACKUP Renames Logicals Received: From MICRO2 by CRVAX.SRI.COM with DECNET via Mail-11; Fri, 22 SEP 89 07:58:01 PDT. Date: Fri, 22 SEP 89 07:58:01 PDT From: "Micro Mauler" To: INFO-VAX@CRVAX.SRI.COM Subject: Re: BACKUP Renames Logicals Message-Id: <9613908.3555347232.MICRO2.SCHWER@CRVAX.SRI.COM> Reply-To: Richard Travsky (rtravsky@OUTLAW.UWYO.EDU) writes in Message-ID: <890921115414.20202aed@UWYO.BITNET> Z We recently upgraded from VMS 4.6 to 5.1-1. Among the many changes, major and Z minor, are of course some that are not well documented (if at all). This is Z one concerning BACKUP that we haven't been able to find in the manuals (sug- Z gestions of places to look welcome!). Briefly, BACKUP is capable of renaming Z the logical established by the user's MOUNT command to something else, which Z has voided some of our documentation and has been responsible for annoying a Z lot of users (not to mention us staff types). The basic steps we use and re- Z commend for users to backup their files is: Z Z $ mount/foreign/other_options mu: Slot_number tape: Z $ backup/options some_files tape:saveset.name /options Z $ dismount tape: Z Z where "mu:" is our generic tape device name and "tape" is the logical name Z chosen for the session. Z Z This worked fine before the upgrade. At 5.1-1, the dismount command (or Z any other command using the logical, such as a BACKUP/LIST type of thing) Z can elicit an error message stating something like "no such device..." or Z "inappropiate device...". Z Z If one executes the command "show logical tape*", lo and behold, "tape" Z is gone, and in its place is "tape$slot_number". Eg., if "slot_number" Z is T31269, the logical "tape" has become "tape$t31269". Or it could be Z transformed to "tape$saveset" where "saveset" is the first part of the saveset Z name specified on the backup call. Huh? Why!? And we can't seem to find Z this in the manuals. I'll assume your running on a MicroVAX and include the following note I made when upgrading from V4.7 to V5.0-1 (NOTE: this feature has been propagated to V5.2 as well.]. $TAPE1 Logical. On MicroVAX systems the logical $TAPE1 points to the tape drive, usually MUA0:. During system boot, under V5.0 and V5.0-1, a new procedure named SYLOGICALS.COM is executed which is intended to define all DEC and local system logicals. Unfortunately, on a MicroVAX system, this procedure is executed before the tape device is configured. The result is $TAPE1 is not defined. The Colorado CSC work around is to execute SYLOGICALS.COM again from SYSTARTUP_V5.COM, but I found it more comforting to just define $TAPE1 in SYSTARTUP_V5.COM: $ define/system/executive/nolog/trans=(terminal,concealed) $tape1 mua0