[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

2627.0. "MOUNT command from ALL-IN-1 subprocess" by PEARS::KRAMER (Fritz Kramer @UFC, Munich, 865-1305) Wed Apr 28 1993 17:04

    Hi,
    
    if I enter the folling DCL-commands from the ALL-IN-1 subprocess
    
    $ MOUNT/FOREIGN MUA0:
    %MOUNT-I-MOUNTED, TEST mounted on _UNHOLD$MUA0
    $ BACK/LOG SYS$LOGIN:LOGIN.COM MUA0:TEST.BCK/SAV
    
    I get the follwing error message
    
    %BACKUP-F-DEVALLOC, unable to allocate device MUA0:
    -SYSTEM-F-DEVMOUNT, device is already mounted
    
    The reason for this is that after MOUNT/FOR the tape-drive
    is allocated by the ALL-IN-1 main process and not by the subprocess
    as I would have expected
    
    The second command BACK/LOG fails because it is beeing executed
    from the ALL-IN-1 subprocess and BACKUP cannot allocate a device
    which is owned by another process (the main process).
    
    Does anybody has an explanation for this?
    
    Fritz
    
    PS. It is the scenario above why the transfer user by tape doesn't
        work on my machine
T.RTitleUserPersonal
Name		DateLines
2627.1How does Archive do it?AIMTEC::BUTLER_TWed Apr 28 1993 19:2312
    Fritz,
    
    I do not have an explanation but, I might have the pointer to how
    to do this.
    
    Look at the archive command files in oa$lib.  It is all done from
    the ALL-IN-1 managers account.
    
    
    HTH,
    
    Tim
2627.2Either $ALLOCATE or remove $MOUNT ...AIMTEC::VOLLER_IGordon (T) Gopher for PresidentWed Apr 28 1993 19:2818
    Fritz,
    
    	This is a problem due to the way BACKUP implicitly allocates
    	devices. For more information see VMS QAR database.
    
    	The workrounds are :-
    
    		o	$ALLOCATE device in sub-process before attempting
    			the $MOUNT, $BACKUP
    
    		o	Let BACKUP mount the device. Ie comment out the 
    			$MOUNT command.
    
    	Hope this helps.
    
    Cheers,
    
    Iain.
2627.3Thanks, I found the TIMA articlePEARS::KRAMERFritz Kramer @UFC, Munich, 865-1305Thu Apr 29 1993 14:2586
    Tim, Iain,
    
    thanks for your input.
    
    Originally I thought this problem has something to do with the
    specialities of the ALL-IN-1 subprocess. I didn't realized that 
    the problem also occurs with a standard VMS-subprocess.
    
    I also found the TIMA article you menationed.
    The article states that the problem is corrected in VMS V5.0-1.
    This might have been true but in VMS V5.2 the problem is either still 
    there or has been reintroduced.
    
    Nevertheless there's your workaround with which I can live.
    
    Thanks
    
    Fritz
    
    -------------------- TIMA Article --------------------------------
    
    
MOUNT-F-DEVALLOC Message Attempting Mount Of Device In Subprocess


COPYRIGHT (c) 1988, 1989, 1990 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.

COMPONENT:  MOUNT Utility                    OP/SYS:  VMS, Version 4.n
                                                      VMS, Version 5.0
LAST TECHNICAL REVIEW:  22-AUG-1990

SOURCE:  Customer Support Center/Colorado Springs  USA


SYMPTOM: 

A tape or disk device is mounted from a subprocess.  Attempts to
re-mount the device after it has been dismounted fail with the
following error message:

     %MOUNT-F-DEVALLOC, device already allocated


ANALYSIS: 

As documented in the "VMS V4.2 Release Notes", July 1985,
(AA-Z106A-TE), page 5-22, Section 5.15.1:

     "When a subprocess mounts a volume (for the job) as a
      private volume, the master process of the job becomes the
      owner of this device.  This provision is necessary because
      the subprocess may be deleted and the volume should remain
      privately mounted for this job." 

Therefore, the first MOUNT command from the subprocess works
correctly.  However, at that point, the master process becomes the
owner of the device.  Thus, a subsequent dismount and mount of the
same device returns the above error.

NOTE:  Any attempt to deallocate the device returns the message:

            %SYSTEM-W-DEVNOTALLOC, device not allocated


WORKAROUND:

Allocate the device from the subprocess before executing any MOUNT
commands.  This forces the subprocess to be the permanent owner of the
device unless the subprocess is deleted.  If the subprocess is deleted
while the device is still allocated, the master process of the job
gains ownership of the device.

NOTE:  This workaround is only applicable to VMS Version 5.0.
       In V4.n, the master process is always the owner of the
       device when it is mounted from a subprocess.


SOLUTION:

This problem is corrected in VMS Version 5.0-1.

NOTE:  There is a similar problem performing BACKUPs from a
       subprocess.  There is another database article that
       describes this in detail.