[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

246.0. "Cannot open CM_AUTHORIZE" by KURTAN::WESTERBACK (After all, who is John Galt?) Mon Mar 16 1992 16:44

    Hi,
    
    We have a strange problem on our internal system.
    
    If I enter with allin1/nocustom I can't access CM. When I
    try I get the CM menu, but at the bottom line it says
    that scriptfile CM_AUTHORIZE cannot be opened, because
    directory is not found.  Message nr 000000.
    I have all privileges on.
    
    CM_AUTHORIZE.SCP is in [ALLIN1.LIB_SHARE] with W:RE protection,
    OA$LIB is correctly defined, the search order is [],OA$LIB.
    
    If I write <DO [ALLIN1.LIB_SHARE]CM_AUTHORIZE it fails the
    same way.
    
    Entering normal way with command allin1, there is no problem
    with CM.
    
    Any ideas?
    
    Thanks,
    Hans
T.RTitleUserPersonal
Name		DateLines
246.1Try these pointsSIOG::T_REDMONDThoughts of an Idle MindMon Mar 16 1992 17:086
    Does the OA$LIB logical search list include a reference to any
    directory that doesn't exist?
    
    Can any other script in OA$LIB be executed?
    
    Tony
246.2Solved, but why?KURTAN::WESTERBACKAfter all, who is John Galt?Mon Mar 16 1992 20:4019
    Well, seems you've got something there, Tony.
    
    There are indeed references to Lotus directories in OA$LIB search
    list, and they point to an old disk. Will try to get this sorted out.
    
    But why does this matter even when I give the full file-spec without
    logicals? 
    Other scripts are also inaccesible.
    
    BUT: Fiddling around a bit I found that OA$FILE_SEARCH_ORDER was
    indeed [],OA$LIB: in normal ALL-IN-1, but in /nocustom it was
    [],OA$LIB_LLV:,OA$LIB_SHARE: 
    Changing it to [],OA$LIB: fixed it, although I don't see why?
    This would still mean that _LLV is searched before _SHARE it 
    seems to me.
    Where is OA$FILE_SEARCH_ORDER set permanently?
    
    Thanks for your help,
    Hans
246.3Glad that some progress was madeSIOG::T_REDMONDThoughts of an Idle MindMon Mar 16 1992 20:5413
    The invalid directories placed into the OA$LIB search order by 1-2-3
    will certainly stop things working. You probably need to edit the
    L123A1_STARTUP command procedure (I think that's the name) and change
    things there.  I don't know why the full file specification didn't
    work, perhaps the code decides that something is amiss when it can't
    resolve OA$LIB....
    
    OA$LIB always resolves to LLV before SHARE, so setting your file search
    order to "[], OA$LIB:" is fine.   OA$FILE_SEARCH_ORDER is set, I
    believe, in the initialization code, but it can be redefined at any
    time.
    
    Tony