[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

2669.0. "MAL not allow CM_SET_PROT" by CROCKE::YUEN (Banquo Yuen, Darwin Australia) Thu May 06 1993 08:43

    ALL-IN-1 V3.0
    
    When I try to edit the authorized location, it won't allow me to
    save my changes unless I clear the field PROTECTION which is originally
    CM_SET_PROT.
    
    What is this CM_SET_PROT?  Is this important or essential?
                                                             
    Thanks
    Banquo
T.RTitleUserPersonal
Name		DateLines
2669.1Protection: OA$LIB:CM_SET_PROTUTRTSC::SCHOLLAERTAjax, Ajax, Ajax...Thu May 06 1993 11:0734
    Perhaps this Stars article will help:
    
'Command procedure not found' Error When Attempt To Move Application Area

PROBLEM: When attempting to move an application area to another disk, one of
the forms that has to be updated is CM$AUTH$LOCATIONS.  While attempting to
update the form, the user receives the following error when trying to {TAB}
past the 'Protection' field:

     Command procedure not found

ANALYSIS: Here is the form:
                              Authorized Locations

    Application Area: BRITISH
    Type:             A1MSG
    Site Location:    OA$SITE_BUILD_BRITISH:
    Base Location:    OA$BUILD_BRITISH:
    Description:      Site BRITISH area for message symbol files A1MSG element
    Open:             Y
    Txl Location:     N    Txl Type:
    Languages:
>>  Protection:       CM_SET_PROT
    Site Translation: DISK$FTAPPS:[ALLIN1.SITE.SOURCES_BRITISH]
    Base Translation: DISK$FTAPPS:[ALLIN1.SOURCES_BRITISH]

CAUSE: The validation on this field attempts to verify that the file can be
found. Since there is no directory specification on the field, it cannot
successfully do so.

SOLUTION: Update the value in the 'Protection' field to include the directory
specification with the file specified as follows:

      Protection: OA$LIB:CM_SET_PROT