Conference iosg::all-in-1_v30

660.0. "Does FCS Require EPM$SRVSHR to be $INSTALLed?" by XLII::FDONOHUE () Fri May 08 1992 22:10

    
    In a note during the Diamond field test, it was stated that the
    File cabinet Server requires that the image SYS$SHARE:EPM$SHARE.EXE
    be installed on the system.  Can you please verify if this is
    still a requirement.  I have not seen this documented, and will
    add this information to STARS if it still applies.
    
        This information appeared in Diamondft Notes # 361
    
PROBLEM:
    

During a new installation of ALL-IN-1 V3.0 on a VMS 5.4-1A system,
the installation completed successfully but it failed to start
the File Cabinet Server with the following errors:
        .
  %OA-I-LASTLINE, "ALL-IN-1 running -- Starting local File Cabinet Server"
  %RUN-S-PROC_ID, identification of created process is 000000C4
  Error writing to server process mailbox - %RM-E-FNF, file not found
  %DCL-W-UNDFIL, file has not been opened by DCL - check logical name
  %NONAME-W-NOMSG, Message number 00000000
  %OA-I-LASTLINE, ERROR STARTING SERVER nodename::"73="
    .
    
CAUSE:

The image SYS$SHARE:EPM$SRVSHR.EXE is not installed on
the system.

SOLUTION:

This has been reported to Engineering.
    
\Basically what happened is that when we switched from EPM to EPC for
\internal statistics tools the links against EPM$SRVSHR.EXE were
\not removed.
    
For this release of the File Cabinet Server (and V3.0 of ALL-IN-1) 
the image EPM$SRVSHR.EXE in SYS$SHARE must be installed. The file is 
provided with VMS.

    

    
    
    Hi Faith,
    
    I've just retested this and it appears that the file does NOT have
    to be installed, although it MUST be present in SYS$SHARE in order
    for the server to startup.
    
    
    Kevin.
    ~~~~~~
    
    
    

    
    re .0
    
    For ALL-IN-1 V3.0 things are as Kevin said in .1. It must be on the
    system, not necessarily installed. It is referenced in the link, but
    never used during run time.
    
    --Bob
    

    
    Thanks, I'll make sure this is clear.
    
    Faith
    

    Faith,
    
    It would be a good idea if possible to include in this article a
    mention that the FCS does not get relinked when all the other images
    get relinked but only when you have changed (major) versions of VMS
    unless you take a look at the A1LINK files and work out how to
    'encourage it' to relink - what we'll probably see is when/if there's
    a new version of VMS calls that say FCS stopped working and the solution
    will be to relink as we had when we had to going past VMS v5.2.
    
    Regards,
    
    Andrew.D.Wicks

    Faith,
    
    
    To force a relink of the FCS server images you can need to edit
    OA$BUILD_SHARE:A1LINK.ANS to change the definition of symbol
    A1$LAST_VMS_VER.  If the value of this symbol is different from
    f$getsyi("VERSION") then the FCS and the IMP$IMPSHR[P] images are 
    relinked.
    
	Martin.