Conference iosg::all-in-1_v30

    Hi,  
    
    >Are there any known problems with having the VMS SYSTEM account tied
    >to an ALL-IN-1 account?
    
    There aren't any that I am aware of as far as ALL-IN-1 IOS is concerned
    it's just another user account.
    
    >It appears that the directory mapping structure for the SYSTEM account is
    >too complex for ALL-IN-1 (i.e. SYS$SYSROOT mapping to SYS$COMMON, etc.)
    
    This is correct ALL-IN-1 IOS does not support rooted logicals and
    hasn't done so as far back as I can remember.  Change the directory
    specification to sys$sysdevice:[sys0.sysroot.sysmgr.a1] and test.
    
    Regards,
    
    Sunil

    Note however that whilst SYSTEM can be *an* ALL-IN-1 account called
    e.g SYSTEM it cannot be *the* ALL-IN-1 account as in the one that has
    the POSTMASTER, MANAGER etc profiles in it...
    
    The ALL-IN-1 account and the SYSTEM account CANNOT have the same UIC
    in ALL-IN-1 v3.0 
    
    It's in any number of STARS articles including Sam's now legendary
    "list of items to check or watch for BEFORE installing ALL-IN-1 v3.0"
    and any number of notes including number 765 in here     
    
    regards,
    
    Andrew.D.Wicks

    Hi Andrew,
    
    Thanks for the correction I just forgot.  The reason being Monday morning 
    blues ;^), well I had to find some reason didn't I !!!!!
    
    Regards,
    
    Sunil

    I'll check it out with the customer tomorrow.  They are forwarding
    their mail to the System "ALL-IN-1" user account.  The ALL-IN-1 Mgr
    account is as it should be - a different UIC. 
    
    As for changing the directory spec to SYS$SYSDEVICE..., we're talking
    about the ALL-IN-1 profile - right.
    
    Thanx,
    David

    Hi David,
    
    >As for changing the directory spec to SYS$SYSDEVICE..., we're
    >talking about the ALL-IN-1 profile - right.
    
    Yes. 
    
    Regards,
    
    Sunil

    Sunil,
    
    I changed the profile the sys$sysdevice... and that didn't seem to do
    the trick.
    
    I looked on the disk fot the Managers account information and then
    modified the profile to reflect that as:
    
    $1$dia0:[sys0.sysmgr.oa]
    
    The system still tried to look in the wrong directory (the top level
    root).  I rename the directory from
    $1$dia0:[sys0.syscommon.sysmgr]oa.dir  to
    $1$dia0:[sys0.sysmgr]oa.dir
    
    I can now bring up ALL-IN-1 without error message (such as actitem.dat
    file not found).  I can read and edit files in the main drawer. 
    However, when I try to create a document in the main drawer, I get the
    following error message:
    
    "The filename is already in use"  upon a gold W:
    
    %oa-W-CAB_USED, The filename is already in use
    %oa-I-lastline, Document could not be created
    %oa-I-lastline, No document was created
    
    When I created a new drawer, all functions work in that drawer
    including document creation.
    
    Do I have a corrupt file somewhere?
    
    Thanx,
    David
    
                                   

	David, 
		You may want to check the partition record for the 
SYSTEM account.  It's my guess that this is still pointing 
SYS$SYSROOT:[SYSMGR.OA].   The way to check is to do the following:

	From ALL-IN-1 account or privileged account from an screen type
	
		SM MFC MD IAD

	In the owner field type SYSTEM and then a carriage return.
You will see all of the drawers owned by the System account.  Select the 
main drawer.  Read the drawer information.  Check the directory.  If
it is SYS$SYSROOT:[SYSMGR.OA], you will need to remove the drawer from the
partition and then reseed for just "SYSTEM".  Type REM to remove the drawer.
To reseed do the following:

	<GET #OAFC_SEED_USER = "SYSTEM"
	<DO OAFC$PART_SEED 

	This will seed the partition for just the "SYSTEM" account based
	on the information in the profile.  

	Log into the SYSTEM account and see if the problem is corrected.


Hope this helps,


Paul

    Paul,
    
    Thanx!  That did the trick.  It's nice to see people from the hotline
    helping us out in the notes files as well as by phone.
    
    regards,
    David

    
    I have adviced customers not to make an ALL-IN-1 account for SYSTEM
    because of the risk that an administrator might delete the SYSTEM
    account including SYSTEM's UAF entry and VMS files.
    
    Elin