[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

2093.0. "OAFC$MTS_PRIV_SHR.EXE -> which directory to put in?" by VNASWS::GACH (Robert Gach, NSCT Vienna, 754/1360) Fri Jan 15 1993 08:30

Hello,

Please can someone give me the right location of OAFC$MTS_PRIV_SHR.EXE?
I installed ALL-IN-1 V3.0-1 (aka Patch 701). The Postinstallationprocedure
OA$BUILD_SHARE:A1_ECO001030_RELINK.COM states that after the relink you 
have to put the OAFC$MTS_PRIV_SHR.EXE into SYS$COMMON:[SYSLIB]!

But the ALL-IN-1 Managment Guide (page 2-12, chapter 3.) says you have to 
put it in into SYS$COMMON:[SYSEXE]. Which one is correct? (So I'm a little
confused now).

Any clerification is appreciate.

Best regards,

Robert
T.RTitleUserPersonal
Name		DateLines
2093.2IOSG::STANDAGEOink...Oink...MoooooooooooooooooooooooooooooooooFri Jan 15 1993 09:3618
    
    Robert,
    
    After a relink which includes the filecabinet server, two FCS specific
    modules are produced :
    
    OAFC$MTS_PRIV_SHR.EXE which should be copied to SYS$COMMON:[SYSLIB]
    and OAFC$SERVER.EXE which should be copied SYS$COMMON:[SYSEXE].
    
    Also just make sure they have the same protections as their
    predecessors, and that no earlier versions are sitting in SYS$SYSROOT
    which would be picked up by mistake when restarting the FCS.
    
    
    Kevin.
2093.4Some more infoAIMTEC::WICKS_AA year behind in more ways than oneFri Jan 15 1993 19:0827
    Robert,       
    
    To add a little to what the experts said the ALL-IN-1 Management Guide
    unfortunately contains a number of errors in the chapter you refer to
    and I would urge you to SPR this one so it may be corrected in a PFR.
    
    One thing to watch out for if you had a Field test version of V3.0-1
    or indeed the TCP product installed is that a number of FCS images were
    inadvertently placed in the wrong directories in some baselevels
    
    So for an ALL-IN-1 v3.0-1 system check that it looks like
    
    Directory SYS$COMMON:[SYSLIB]
    OAFC$CLIENT_SHR.EXE;2   
    OAFC$MTS_PRIV_SHR.EXE;2
    OAFC$MTS_SHR.EXE;2
    
    Directory SYS$COMMON:[SYSEXE]
    OAFC$CREATE_SERVER.EXE;2 
    OAFC$PRINT_TRACE_LOG.EXE;2
    OAFC$SERVER.EXE;2 
    OAFC$SYSFOLD_SEED.EXE;2
    
    Regards,
    
    Andrew.D.Wicks