[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

3749.0. "Transfering accounts with drawers created from TeamLinks" by ULYSSE::DAVID (Guy David @VBE) Tue Jan 11 1994 15:25

    Hello,
    
    I've transfered an ALL-IN-1 (and VMS) account from a v3.0-1 system to a 
    v3.0A system. The user had drawers created from his PC running TeamLinks 
    v1.1.
    The preparation (PTN) was ok. The restore on the target system (CSN) was 
    ok.
    The problem is that the user cannot access drawers originally created from 
    TeamLinks. He got the following message when using Read option on Index of 
    Drawers (ID) :
    
    Drawer name         REF02 - RECO
    
    Error               ** Drawer could not be accessed **
    Reason                 Remote Server is not licensed to export 
    information.
    
    
    The original drawer characteritics were :
    
    Drawer              REF02 - RECO
    
    System              BON2::
    
    Owner               HEMMINGS
    
    Drawer name         REF02
    
    Description
    
    Directory           USER3:[HEMMINGS.ALLIN1.ISC3JA3A]
    
    You have CONTROL access to the drawer
    
    Drawer is not shared with other users
    
    Drawer is located on this system
    
    
    Having a Look at the [.ALLIN1] subdirectory, I found 2 versions of 
    FILECAB.DAT, one, FILECAB.DAT;16 coming from the original system, the 
    other, FILECAB.DAT;1 newly created on the system.
    
    Investigating in this conference and in WINDOWS-OFFICE, I found 
    information on the different ways drawers are named if created from IOS or 
    from TeamLinks, but I didn't find how to recover from such a situation.
    
    Any lights out there ?
    
    Thanks,
    Guy.

T.R	Title	User	Personal Name	Date	Lines
3749.1	Might be a 0:: problem	IOSG::TALLETT	Gimmee an Alpha colour WinPad!	`Tue Jan 11 1994 15:44`	42
	There is a bug reported (but not fixed) against TeamLinks that drawers created from TeamLinks have the local nodename in them and not 0:: (as would be normal for ALL-IN-1 IOS). This MAY be your problem. So for example, if you create a drawer from IOS on node FOO, the FILECAB.DAT entry will contain 0 for the node, but if you create it from TeamLinks it will contain FOO. Normally you wouldn't notice the difference, but certain parts of ALL-IN-1 get confused by this setup (eg Delete drawer). I'm fairly sure transfer user will get confused by this setup too, but I'm not sure what will happen. > Drawer name REF02 - RECO > > Error Drawer could not be accessed > Reason Remote Server is not licensed to export > information. This means that the target system is still trying to access the drawer on the old source system, which will only work if you have the right licenses, which obviously you don't. What you probably wanted to do was to transfer the drawers to the new system, not access them remotely. The real problem needs fixing in both TeamLinks (CFCIOS) and the FileCab server (which currently doesn't allow 0:: on drawer creation). The workaround is to WRITE CHANGE FILECAB and get rid of the local nodename before you do the PTN. You might be able to repair your PARTITION.DAT with WRITE CHANGE on the target system, but it depends on how confused transfer user was, during the transfer. I suspect that transfer user thought that this drawer was not a local drawer, and didn't transfer it. Let us know if this nodename was indeed your problem. Regards, Paul
3749.2	FCS should decide on the 0::	CHRLIE::HUSTON		`Tue Jan 11 1994 17:57`	16
	re .1 Just a fyi nit > There is a bug reported (but not fixed) against TeamLinks that > drawers created from TeamLinks have the local nodename in them > and not 0:: (as would be normal for ALL-IN-1 IOS). The correct way to fix this (FCS) is to not allow 0:: to be passed in on create drawer, but have the FCS check the node the drawer is on, if it is on the FCS system, then substitue in 0::. The FCS will NEVER return 0:: (it switches it with its own node name), and it should never accept it. It should however put it in in place of the local node when making the filecab.dat record. --Bob
3749.3	One the right way	ULYSSE::DAVID	Guy David @VBE	`Thu Jan 13 1994 17:08`	22
	Hi, I finally got it, ...almost,... CSN is still running. The situation on the target node was that the TeamLinks created drawers didn't contain the shared files. Only private files were transfered, packed with the VMS directories. In fact there was no references to those drawers in the PTN log file. So I decided to delete everything on the target node, and start again. Before starting, I followed your advise, and changed the local nodename from BON2:: to 0::. I needed also to change the owner of each drawer from HEMMINGS to HEMMINGS.ROBIN (IOS profile entry) to have all drawers finally packed in the savesets. I hope this kind of problem will be addressed in the coming release because it's quite time consuming to get the situation back to normal, and the user couldn't use his account during 3 days. Thanks for your helpfull hints, Guy.