[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

1833.0. "CM cannot find A1WPSPLUS_LOGIN.COM" by UTRTSC::SCHOLLAERT (AJAX beats Feyenoord again and again) Mon Nov 23 1992 09:34

    Hello,
    
    Customer reports: accessing A1WPSPLUS_LOGIN.COM by CM fails.
    Its location on disk is : OA$LIB_SHARE:A1WPSPLUS_LOGIN.COM
    
    As we know, A1WPSPLUS_LOGIN.COM is located in SYS$MANAGER .
    
    CM is born after ALL-IN-1 so am I correct to say that this
    is a CM typo ?
    
    Regards,
    
    Jan
T.RTitleUserPersonal
Name		DateLines
1833.1By rights, the file SHOULD be in OA$LIB_SHARE:SIOG::T_REDMONDThoughts of an Idle MindMon Nov 23 1992 11:0614
    Typo in the creation of the CM$SDC contents...
    
    You'll need to change the CM$SDC record to reflect the correct
    location, or copy the file into OA$LIB_SHARE (to join the other
    A1WPSPLUS_ command procedures located there).
    
    Note that if you continue with the procedure in SYS$MANAGER you'll have
    to add this directory as an authorized location. If you don't you'll
    never be able to move a customized version back...  CM won't be too
    happy with the notion of SYS$MANAGER being an authorized location so
    some use of the OA$VAL_SET_VALID (interactive) function is probably
    going to be required.
    
    Tony
1833.2customer wants to be fully CM-compliantUTRTSC::SCHOLLAERTAJAX beats Feyenoord again and againMon Nov 23 1992 12:0616
    Tony,
    
    >You'll need to change the CM$SDC record to reflect the correct
    >location, or copy the file into OA$LIB_SHARE (to join the other
    >A1WPSPLUS_ command procedures located there).
    
    My customer wants to be fully CM-compliant.
    
    So, without discussing futures, if this is going to change in PFR,
    what would it be ? 
    
    Thanks,
    
    Jan
1833.3MoveSIOG::T_REDMONDThoughts of an Idle MindMon Nov 23 1992 12:246
    I don't know if it will change in a PFR. But I would move the file into
    OA$LIB_SHARE and leave it there rather than in SYS$MANAGER. I think the
    latter location is an old hangover from the first WPS-PLUS/VMS
    implementations.
    
    Tony
1833.5Mea CulpaIOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeMon Nov 23 1992 13:3710
    Ah, yes, a slight oversight on my part... Because the file is provided
    by code in the installation procedure, I have to guess where it will
    go, in this case wrongly :-)
    
    Actually we have traditionally always supplied the file to SYS$MANAGER,
    so that is the "right" place for it. Because there isn't a
    corresponding site directory for SYS$MANAGER, as Tony points out, I
    should really have marked it as non-modifiable too.
    
    Graham
1833.6mumble_LOGIN.COM's : SYS$MANAGERUTRTSC::SCHOLLAERTAJAX beats Feyenoord again and againMon Nov 23 1992 13:5511
    >Actually we have traditionally always supplied the file to SYS$MANAGER,
    >so that is the "right" place for it. Because there isn't a
    
    From a (VMS) system managers point of view, the preferred
    location of all mumble_LOGIN.COM's is SYS$MANAGER . Saves
    code in (SY)LOGIN.COM.
    
    Regards,
    
    Jan