home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!sgiblab!sdd.hp.com!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: Wierd BACKUP change in VMS 5.5-2
- Date: 17 Nov 1992 23:23:58 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 29
- Distribution: world
- Message-ID: <1ebuueINNc33@gap.caltech.edu>
- References: <1992Nov17.203345.23090@aplcen.apl.jhu.edu>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- In article <1992Nov17.203345.23090@aplcen.apl.jhu.edu>, rubin@procon.jhuapl.edu (Don Rubin) writes:
- =
- =We recently upgraded one of our clusters to 5.5-2, everything
- =went well and we had no complaints from the users until someone
- =ran one of my programs that is a front end to BACKUP. We have
- =a database of backups that allows the user find which tape has
- =the desired data. The restore program gets info from the user
- =and then mounts the tape (all of our programs do mounts and
- =dismounts so the users never have to worry about doing that)
- =if the label agrees with the one the user specified then a
- =subprocess is created (using smg$create_subprocess) and BACKUP
- =is spawned. UNTIL 5.5-2 this worked properly, since the drive
- =was mounted in the parent process, backup just went ahead and
- =did the restore. NOW backup aborts saying the tape drive is
- =allocated by another process (yes, the parent). After much
- =mail with DSNLINK the word is that the problem has been
- =refered to engineering.
-
- Sounds like the parent process is not only MOUNTing the tape, but is
- ALLOCATEing it as well. You might want to check your procedures for that
- possibility.
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-