| 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 | 
  Hi,
  I have a customer who wishes to move his ALL-IN-1 V3.0 system to another
  disk. His main problem is that in the various data files instead of using
  a logical name he has used the disk name. This means that he has come to
  a few problems. These are:
  <FORM CM$AUTH$LOCATIONS  
  He gets the following form up and wishes to alter the site and base 
  translation
                              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 typ
  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]
  Command procedure not found   
  When he tries to tab past the field 'Protection' he gets the error mentioned
  above. Also when entering <FORM CM$MAF he has similar problems:
                            Master Area File
  App. Code:     OA
  Area Code:     SHARE               Area:    SHARE
  Receive Area:  REC_SHARE
  Description:   ALL-IN-1 SHARE Area
  Created Date:  01-May-1992       Modified Date:
  Identifier:    OA$PRVAPP
  Base root dir: DISK$FTAPPS:[ALLIN1]
  Site root dir: DISK$FTAPPS:[ALLIN1.SITE]
  Startup:
  Language:
  Area Status:   Open
  Priority:      50
  Receive area REC_SHARE is not unique, please re-enter
  The above error happens when they try to change the Base root directories, on
  attempting to tab past the field 'Receive area'. Both these error I can
  reproduce here. 
  Any help would be welcome. 
  Regards,
  Richard Simpson.
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 1398.1 | Why not use <WRITE CHANGE ? | AIMTEC::WICKS_A | It wasn't supposed to end this way | Mon Sep 14 1992 02:44 | 14 | 
|     Richard,
    
    Don't use <FORM CMmumble as they exhibit some unusual behaviour as you
    have spotted.
    
    in many cases you can use a menu option such as EA (edit Application
    area) or edit a location off the MAL (manage Authorised Location)
    index but if the field is protected against you as some of the ones
    you're trying to get to are then fail back to the tried and
    trusted <WRITE CHANGE statement it won't let you down
    
    Regards,
    
    Andrew.D.wicks
 | |||||