[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

2017.0. "What happens with Shared Folder during upgrade" by BERN02::MUELLERS (Stefan A. M�ller DTN 761-4864) Thu Dec 24 1992 10:17

    Hi
    
    Can someone explain me what exactly happens with shared folders from
    V2.4 when upgrading to V3.0.
    
    If a shared folder in V2.4 looks like [username]TEST how does it look
    like in V3.0's drawer and folder structure? Does SFCP_MIGRATE.SCP take
    care about shared folders or who does it?
    
    I ask you because a customer complains about loosing all documents that
    were located in V2.4 shared folders when upgrading to V3.0.
    
    Stefan
T.RTitleUserPersonal
Name		DateLines
2017.1MigrateIOSG::CARLINDick Carlin IOSG, Reading, EnglandThu Dec 24 1992 11:2310
    The quick answer is Yes you need to run sfcp_migrate. Details are in
    Installation Guide Part 1, section 10. Other references have been
    mentioned in this conference (try dir/tit=shared).
    
    Briefly:
    
    Documents in folder "[username]TEST" are refiled into folder "TEST" and
    documents in folder "[username]" are refiled into folder "username".
    
    Dick
2017.2Only if you are using SFCP!IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeThu Dec 24 1992 11:477
    Of course if you didn't use SFCP other shared folders need to be
    handled manually...
    
    The SFCP migrate script is a good place to start stealing code form
    tho'!
    
    Graham
2017.3Oy!IOSG::MAURICEIs there life on IOSG?Thu Dec 24 1992 12:2919
    No no no!!!
    
    Ordinary shared folders are not impacted by upgarding to V3.0. They
    should still work OK.
    
    SFCP shared folders are a special case and need to be handled by
    running the SFCP migration script.
    
    A common trap for shared folders to "stop working" is if the user's
    DOCDB containing the shared folders loses its access. Usually the UIC
    group protection is used to grant access, and System Managers do like
    taking it off when you're not looking ;^)
    
    Also beware that in V3.0 you can only access someone else's shared
    folder if your current drawer is your MAIN (default) drawer.
    
    Happy Christmas
    
    Stuart
2017.4What's now?BERN02::MUELLERSStefan A. M�ller DTN 761-4864Mon Jan 04 1993 09:026
Stuart,

So a common shared folder from V2.4 "[MUELLERS]TEST" has the same name 
"[MUELLERS]TEST" in V3.0?

Stefan
2017.5IOSG::MAURICEIs there life on IOSG?Mon Jan 04 1993 09:0610
    Re .4
    
> So a common shared folder from V2.4 "[MUELLERS]TEST" has the same name 
> "[MUELLERS]TEST" in V3.0?
    
    Yes - that's right.
    
    Cheers
    
    Stuart
2017.6Silly me!IOSG::CARLINDick Carlin IOSG, Reading, EnglandMon Jan 04 1993 17:3011
    Apologies.
    
    My earlier reply assumed that you were using SFCP. As Stuart quite
    rightly says you can carry on using ordinary shared folders as before.
    
    Another catch (but a more bizarre one) is that a user of another client
    could create a folder [xxx]yyy in your main drawer, which you would
    never be able to access (the shared folder mechanism would say that
    there was no user xxx).
    
    Dick