Conference iosg::all-in-1_v30

97.0. "Problems transferring users - ALL-IN-1 V2.3" by KERNEL::SMITHERSJ () Tue Feb 25 1992 16:46

    Wonder if anyone can help with this v.2.3 problem.  We don't have 
    access to a 2.3 system anymore and the log files are different for
    a 2.4 system.

    Customer has attempted a 2.3 transfer user across nodes but after 
    the PAT, the manager did not receive a mail message to say it went
    OK.  The Log file shows:

    %OA-W-BOTTOM_FOLD, You have reached the bottom of the folder
     repeated several times
    %BACKUP-S-COPIED, copied DISK:[USER.A1]ACTITEM.DAT
     repeated for each ALL-IN-1 file (except DAF and DOCDB)
    %BACKUP-S-COPIED, copied OA$TRANSFER:[USER.USER]A1.BCK
    %BACKUP-S-COPIED, copied OA$TRANSFER:[USER.USER]VMS_ACCOUNT.BCK
    %BACKUP-S-COPIED, copied OA$TRANSFER:[USER.USER]ZDOCUMENTS.BCK
    %BACKUP-I-STARTDELETE, starting file deletion pass
    xfer_name = :DAYJ:
    account = :DAYJ:
    cancel_flag = 0
    %RMS-E-RNF, record not found
    %OA-I_FLCVERERR, obselete version of 
    SYS$SYSDEVICE:[ALLIN1.SITE.DEV_BRITISH]DEVELOP.FLC - Continuing

    Manager finished using ALL-IN-1 at 17-FEB-1992 


    and that's it.  Account is left locked and in an archived state.


    Unfortunately, customer decides to do a MAS which fails with a 
    mail message which states "Failed to recover from an invalid 
    condition.

    Errors in the log file for the MAS include:

    $ write scp "get cli$admin_accnt = profil.vmsusr[cli$admin_id]"
    $ write scp "get cli$admin_dir = profil.direct[cli$admin_id]"
    $ write scp ".exit"
    $ write scp
    $ allin1/user=manager/noinit/reent
      oa$ini_init
      get oa$function="do " cli$script_file

    %OA-W-SCPSYNTAX, Incorrect syntax in SCRIPT command:
    .if #temp .eqs. "Y" then get cli$admin_flag = 1
                            *
    %OA-I-SCPLINFIL, Line !UW in script "!AS" file "!AS"
    exit

    MANAGER finished using ALL-IN-1 at 19-Feb-1992 

    $ delete/noconfirm/nolog sys$login:mua_check_admin.scp;
    $ if manager_language .eqs. "" then goto no_language
    $ if admin_language .eqs. "" then goto no_language
    %DCL-W-UNDSYM, undefined symbol - check validity and spelling
    \ADMIN_LANGUAGE\
    $ invalid condition 
    etc


    The ALL-IN-1 manager is trying to do the transfer, the language
    field is BRITISH.  I say this because later on in the log file
    it does a 

    $ close msg
    $ allin1/user=manager/noinit/reent/language=BRIITSH
     oa$ini_init
     get oa$function="do " cli$script

    MANAGER finished using ALL-IN-1 at 19-Feb-1992

    but get no error.  

    Customer is patched to 513.  I have advised her that support is
    limited because of the old version but her management have said
    otherwise.

    Can anyone cast their mind back to 2.3 - I unfortunately am not
    old enough!!

    Oh by the way in [ALLIN1.SITE.LIB_SHARE] the following files have
    been customised:

    MUA_CANCEL_TRANSFER.COM;4 3-FEB-1992 
    MUA_DEL_DIR.COM;2 14-FEB-1992
    MUA_DEL_VMS.COM;3 19-FEB-1992
    MUA_LOAD_USER.COM;4 3-FEB-1992
    MUA_PAT.COM;4 3-FEB-1992
    MUA_RENAME.COM;8 12-FEB-1992
    MUA_SAVE_UNREAD_MAIL.SCP;4 3-FEB-1992

    but without going through them do not know what changes.

    Help!  Also I read that 2.3 accounts should be restored from backup
    if the transfer goes wrong.  Is that the case or can the savesets
    be unpacked as in the STARS article but what about mail messages?

    Thanks
    julia
    CSC

    

    Hi there!
    
    	I know *NOTHING* about V2.3 transfer! But I guess it is similar
    	to V2.4.
    
    	My guess is that the %RMS-FNF is coming from the customization,
    	we had a similar one in another note recently, and I can't think
    	what would cause that in an uncustomized script.
    
    	That's about as much help as I can give you! Sorry. You could try
    	a trace if you can reproduce the problem.
    
    	Customers expect us to support old versions that they have
    	customized - I like it!
    
    Regards,
    Paul

V2.3 is still an officially supported version of ALL-IN-1 and will be for most
of the rest of this year, and I thought customizing ALL-IN-1 was supported too!

The Atlanta CSC will support ANY version of ALL-IN-1, although pre V2.3 is on 
a best effort basis only, and we encourage customers to upgrade as soon as 
they can.

I would suggest a careful examination of the customizations to see what could
have gone wrong, did the customizations ever work, and if so what has changed
since the last time it worked?

The user's account can be restored from the saveset by unpacking it and
tricking ALL-IN-1 to think the transfer area is an archive area (the STARS
artical should detail how to do this). The mail will be restored as private 
documents so the user will need more disk space, but they could be made 
shared again using CAB SHARE.

If you restore from backup you will also have to restore any documents in mail
areas (typically mail messages) that have been deleted because their usage 
counts went to 0 during the PAT, and you will have to fix the usage counts
of all the other mail area documents that this user references (TRM will do
this bit for you).

I would suggest restoring from the saveset, in the long run that will probably
be easier.

Terry

    A-ha,
    After many hours poring over the log files, customisations and
    2.3 scripts, I think I may have found the problem.

    Don't sure yet about the PAT, whether the record not found error is
    meant to be there, but I think I've cracked the MAS log file.

    The error 

    get oa$function="do " cli$script_file
    %OA-W-SCPSYNTAX, Incorrect syntax in SCRIPT command
    .if #temp .eqs. "Y" then get cli$admin_flag = 1

    is caused because the script falls over due to .EQS. in the 

    write scp ".if #temp .eqs. ""Y"" then get cli$admin_flag = 1"
                         ^^^^^
    All the other write scp statements and 2.4 script only have
    eqs not .eqs. If I add two fullstops around that in the 2.4 system,
    it falls over with the same error.

    And because this causes the script not to be run, that 
    is why the later error 

    %DCL-W-UNDSYM, undefined symbol - check validity and spelling
    \ADMIN_LANGUAGE

    is caught because that is the first symbol defined in the script
    and if it hasn't been run yet, then obviously it won't be 
    recognised.

    Next problem is getting hold of the customer - "urgent" problem
    and yet they have disappeared for the week with no-one looking after
    the call.

    Time for a lie down......

    julia