[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

1752.0. "Cannot delete elements in CM" by EVOIS8::DEC_HELLAS () Wed Nov 11 1992 08:45

    
    In V2.4 we had installed the ASSET "Mail Janitor Utility" (MJU). We want to
    reinstall it in V3.0. To do so we have to delete in the Customization
    area, all the elements that made up the previous version. While in CM,
    we do an index on all elements prefixed with SM_MJU* and select
    them. When then try to delete all selected. The XD operation failed for
    some of them and we got the error message:
    
    Unexpected development location OA$SITE_DEV_LLV:SM_MJU.BLP
    
    where SM_MJU.BLP is the element we try to delete. How can we delete
    these elements?
    
    rgrds
    
    
    Nicholas
T.RTitleUserPersonal
Name
DateLines
1752.1OA$SITE_DEV_LLV not used in V3.0CESARE::EIJSAll in 1 PieceWed Nov 11 1992 12:4922
    
    Nicholas,
    
    In V3.0 the logicals:
    
    	OA$SITE_DEV_LLV
    	OA$SITE_DEV
    
    have been removed from the system. This because application areas are
    not 'ALL-IN-1 language' dependent.
    
    Try and define the logical temporarily and set it to
    OA$SITE_DEV_ENGLISH (I presume you run that system). Then try the 'XD'
    again.
    
    If it succeeds, check if there are more elements which still refer to
    OA$SITE_DEV_LLV. If so, change the CM$SITELOG records (there are a
    number of ways to do this: Script, interactively, whatever you want).
    
    Ciao,
    
    	Simon
1752.2Delete VMS file and remove record from sitelogFAILTE::EWE::LAAHSAn accumulation of CeltsWed Nov 11 1992 12:5212
Nicholas,

The check for a 'correct' development location is just a safety precaution in 
case your CM database is not 100% correct.

In your case some the the MJU entries do not point to the correct VMS file 
(this *may* be becuase of the LLV part of the device spec).

To delete manually just physically delete the underlying VMS file and delete 
the entries from CM$SITELOG by calling the form interactively.

Kevin
1752.3Yes, they were deleted.EVOIS8::DEC_HELLASWed Nov 11 1992 14:229
    
    Simon, before I posted my note I had defined the logical OA$SITE_DEV_LLV
    to point to the correct location, but that did not work. Therefore, I
    deleted all formS SM_MJU* interactively and then deleted the
    corresponding VMS files SM*MJU*.*;*, as Kevin suggested in .2
    
    Guys, thanks a lot. I will now proceed in the installation of the new
    version of the MJU ASSET.