[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

3240.0. "Transfer user from Starter 2.4 to Starter 3.0 via tape (PAT, MAS)" by VNOAPP::TIMA_204410 (Plus en plus seule...) Mon Sep 06 1993 17:44

Hello collegues!

My customer has two ALL-IN-1 Starter Systems, 2.4 and 3.0 on different nodes (not 
even DECnet connection). 
On both he uses VMS 5.5-2. 

Starter 2.4>
SM, MUA, PAT TT > bla bla, anything is ok!!!!

Customer inserts tape into other system:

SM, MUA, CST, > error message: error occurred ....
(If he comments out the lines of mounting the tape, in the log before the backup command
anything works fine, except the deleting of the directory)

Directory in  oa$loaduser:

Directory OA$LOADUSER:<000000>

TEST.DIR;1           [ALLIN1]              (RWE,,,RE)
          (IDENTIFIER=[A1$XFER_IN],ACCESS=READ+WRITE+EXECUTE)
          (IDENTIFIER=[A1$XFER_IN],OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE)
          (IDENTIFIER=OA$ADMIN,ACCESS=READ+WRITE+EXECUTE)
          (IDENTIFIER=OA$ADMIN,OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE)

Total of 1 file.



Here the extract of log:



$ @$DISK2:[ALLIN1.LIB_SHARE]SM_PAT_VALIDATE_TAPE.COM; 
$ !-----------------------------------------------------------------------
$ !     SM_PAT_VALIDATE_TAPE.COM
$ !
$ ! Details at the end of the file
$ !-----------------------------------------------------------------------------	
$ !
$ ! Set the error handling
$ !
$ 	on error then goto exit
$ !
$	wo := "write oamailbox"
$ 	dc := "@dclmailbox:"
$ !
$ ! Now set message suppression - the only messages should be those
$ ! translated messages called at the forms
$ !
$	message_status = f$environment("message")
$	set message/noseverity/noident/nofacility/notext
$ !
$ ! Okay get the device name from field SYSTEM on form sm$pat$tape or
$ ! sm$mult$tape
$ !
$	wo "OA GET DRIVE"
$	dc
$ RESULT=="MKA0:"
$	drive_name = result
$ !
$	if f$getdvi(drive_name, "EXISTS") then $ goto success
$ success:
$	wo "OA GET #VALID = 1"
$	dc
$ !
$ exit:
$ !
$ !	set message 'message_status'
$	exit



$ @$DISK2:[ALLIN1.LIB_SHARE]SM_PREPARE_MAS_TAPE.COM; 
$! OA$LIB_SHARE:SM_PREPARE_MAS_TAPE.COM
$! Details at the end of the file
$! Set the error handling
$!
$ 	on error then goto error_exit
$!
$! Now set message suppression - the only messages should be those
$! translated messages called at the forms
$!
$	message_status = f$environment("message")
$	set message/noseverity/noident/nofacility/notext
$!
$! Define some useful abbreviations
$!
$	wo := "write oamailbox"
$ 	dc := "@dclmailbox:"
$!
$! Set the boolean dir_created to false ie 0
$!
$	dir_created := 0
$!
$! Get the validated tape drive and tape name
$!
$	wo "OA GET #MAS_TAPE_DRIVE"
$	dc
$ RESULT=="MKA0:"
$	drive_name = result
$	drive_name = drive_name - ":" + ":"
$!
$	wo "OA GET #MAS_TAPE_NAME"
$	dc
$ RESULT=="TEST"
$	tape_name = result
$!
$! Get the transfer group name
$!
$	wo "OA GET GROUP"
$	dc
$ RESULT=="TRTEST"
$	group_name = result
$!
$! Now check for the workspace directory for this group.
$!
$	work_dir = f$search ( "oa$loaduser:[000000]TRTEST.dir" )
$	if work_dir .nes. "" then goto check_account_list
$!
$! Create the workspace directory
$!
$ create_dir:
$	create/directory/nolog oa$loaduser:[TRTEST]
$	dir_created := 1
$!
$ check_account_list:
$	accnt_list = f$search("oa$loaduser:[TRTEST]pat_TRTEST.dat")
$	if accnt_list .eqs. "" then goto mount_tape
$ mount_tape:
$	wo "OA GET OA$DISPLAY=SM$_MAS_MOUNTING_DRIVE\FORCE"
$	dc
$! find out if 2.3 transfer from the files on the tape.
$!
$	xfer_name = f$extract(0,13,group_name)
$       xfer_filename = "TRTEST.wrk"
$	if f$getdvi(drive_name,"MNT") then -
	    dismount/nounload MKA0:
$       mount  MKA0: TEST
$       if f$search("MKA0:TRTEST.wrk") .nes. "" then -
                            goto created_dir
$ created_dir:
$	set message/severity/ident/facility/text
$	if f$getdvi(drive_name,"MNT") then -
	    dismount/nounload MKA0:
$	mount/foreign MKA0: TEST
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-MOUNTED, TEST mounted on _FMSW03$MKA0:
$	wo "OA GET OA$DISPLAY=SM$_MAS_LOAD_DATA\FORCE"
$	dc
Loading the transfer user accounts data
$	backup/rewind MKA0:TRTEST.wrk -
                           oa$loaduser:[TRTEST]pat_TRTEST.dat
%BACKUP-F-DEVALLOC, unable to allocate device MKA0:
-SYSTEM-F-DEVMOUNT, device is already mounted
$ error_exit:
$	wo "OA GET #MAS_STATUS = 0\GET OA$DISPLAY=SM$_MAS_PREPARE_ERROR\FORCE"
$	dc
Error occurred in the prepare for the move account operation
$!
$! Now delete the workspace directory if an we created it here.
$!
$	if dir_created .ne. 1 then goto exit
$	delete/nolog oa$loaduser:[TRTEST]*.*;*
%DELETE-W-SEARCHFAIL, error searching for OA$LOADUSER:[TRTEST]*.*;*
-RMS-E-FNF, file not found
$	delete/nolog oa$loaduser:[000000]TRTEST.dir;
%DELETE-W-FILNOTDEL, error deleting OA$LOADUSER:[000000]TRTEST.DIR;1
-RMS-E-PRV, insufficient privilege or file protection violation
$ exit:
$	if f$getdvi(drive_name,"MNT") then -
	    dismount/nounload MKA0:
$ 	set message /NOFACILITY/NOSEVERITY/NOIDENTIFICATION/NOTEXT
$	exit
set message mess_state



Thanxx for inputs 
Marianne Schnabel
CSC Vienna
T.RTitleUserPersonal
Name
DateLines
3240.1A STARTER engineer and part-time Transfer-User engineer writes...SCOTTC::MARSHALLSpitfire Drivers Do It ToplessThu Sep 09 1993 12:5023
Hmmm,

This looks like a problem with transfer user, rather than a problem with
STARTER.  No changes were made to the transfer user code for STARTER, and the
problem seems to lie in the tape mounting logic, rather than in anything
that would be ALL-IN-1 version dependent.

However, transfer user was pretty thoroughly tested for V3.0, and I can't
imagine a problem of this scale (which would appear to prevent *any* tape
transfer from working!) slipping through the net.

I wonder if the configuration of the MKA0 device if causing a problem?  For
example does it have some sort of "noshare" attribute that prevents the BACKUP
command accessing it after the MOUNT command?  Or maybe the MOUNT and BACKUP
commands are wrong, but just happened to work with the set-up of tape devices
that were tested within engineering?  Unlikely, as I would then have expected
to see a lot more complaints about transfer user not working.

I shall have to leave this one to someone with more knowledge of mounting and
allocating tape devices.  I'll also bring it to the attention of the other
Transfer User engineers.

Scott
3240.2positional qualifier?IOSG::TYLDESLEYThu Sep 09 1993 13:4110
    Hi Scott.
    I, too, am no expert on tape mounting. Here's a long shot though:
    see the line in the log:
    $ backup/rewind MKA0:TRTEST.wrk -
    Well, it may be that /rewind is an input save-set qualifier, and should
    be placed immediately after the input specifier e.g.
    $ backup MKA0:TRTEST.wrk/REWIND -
    ... in which case this may be a bug.
    Cheers,
    DaveT 
3240.3No ideas reallyIOSG::TALLETTGimmee an Alpha colour notebook...Thu Sep 09 1993 16:0811
    Hi there!
    
    	This is very odd. Tape transfers were tested for V3.0 and worked
    okay. My only thought is that VMS V5.5 BACKUP has changed the handling
    of foreign mounted tapes, although it seems unlikely.
    
    From the look of your log, you could take out the MOUNT/FOREIGN through
    customisation to get it to work, I would have thought.
    
    Regards,
    Paul
3240.4VMS Feature ...AIMTEC::VOLLER_IGordon (T) Gopher for PresidentThu Sep 09 1993 17:1422
    Hi,
    
    	I've seen this one before.
    
    	There was (is?) a problem in OpenVMS when running BACKUP from a
    	subprocess. BACKUP will explicity ALLOCATE a device for most 
    	operations (/LIST is an exception).
    
    	Unfortunately, MOUNT/FOREIGN also ALLOCATEs the device hence the
    	DEVALLOC message.
    	
    	The workrounds are :-
    
    		Specifically ALLOCATE the device in the subprocess, or -
    
    		Remove the MOUNT command and let BACKUP do it's own thing.
    
    	See also note 2627.*
    
    Cheers,
    
    Iain.
3240.6VMS 6.0VNOAPP::TIMA_204410Plus en plus seule...Fri Sep 10 1993 17:1135

I have installed VMS 6.0 here on my node, and tested the 
procedure (CST). Seems to be no problem since 6.0
Maybe you can hava a look at this tracelog:

$! Now backup the data file which contains the users to transfer
$!
$ created_dir:
$       if f$getdvi(drive_name,"MNT") then -
            dismount/nounload MKB500:
$       mount/foreign MKB500: TEST
$       wo "OA GET OA$DISPLAY=SM$_MAS_LOAD_DATA\FORCE"
Loading the transfer user accounts data
$       backup/rewind MKB500:pat_TEST.dat -
                           oa$loaduser:[TEST]pat_TEST.dat
$ error_exit:
$       wo "OA GET #MAS_STATUS = 0\GET OA$DISPLAY=SM$_MAS_PREPARE_ERROR\FORCE"
Error occurred in the prepare for the move account operation
*** I only created dummy .dat and .bck files ***
*** so no wonder 'bout the errors, but you can't find any Backup error mess!!!***
$!
$! Now delete the workspace directory if an we created it here.
$!
$       if dir_created .ne. 1 then goto exit
$ exit:
$       if f$getdvi(drive_name,"MNT") then -
            dismount/nounload MKB500:
$       set message /NOFACILITY/NOSEVERITY/NOIDENTIFICATION/NOTEXT
$       exit
set message mess_state


Bye 
Marianne