[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

1984.0. "Transfer of users from version 2.4 to version 3.0" by COPCLU::VAGN (Vagn Eisensee @DMO) Thu Dec 17 1992 13:35

      We have just been through a lot of trouble transferring a small number of 
      users from version 2.4 to 3.0 for one of our largest ALL-IN-1 customers. 
      
      I still dont know if the problems we had are specific for the danish 
      ALL-IN-1 versions or more general, but anyhow the problem statement and 
      solution follows: - 
      
      When a user is packed for transfer via network on version 2.4 of 
      ALL-IN-1, all shared mail files are crossfiled in an extra folder called 
      "ARCHIVED DOCUMENTS". This means that there are 2 DOCDB records for each 
      shared document with the same document number, and for this reason the 
      RESTORE_DOCUMENT function fails on version 3.0. The fix was to delete one 
      of the 2 records in DOCDB,  and make sure that fields like MAIL_STATUS 
      are correct, and then the transfer works.
      
      The fix is done in the script SM_MAS_ARCHIVE_V2.SCP on version 3.0. The 
      statements are placed right after the original restore_doc label: - 
      
      .LABEL RESTORE_DOC
          WRITE DELETE CAB$ .%KEY=OA$CURDOC
          CAB SELECT , #DOC_NUM,,OA$CURDOC
          WRITE CHANGE CAB$ .%KEY=OA$CURDOC, MAIL_STATUS="ARCHIVED"
      
      I am still wondering if there is something special in the danish ALL-IN-1 
      versions, which has caused the problem, or nobody else in the world has 
      tried a similar transfer? I would think that transfer of a small number 
      of users for testing out version 3.0 would be quite common?
      
      Another problem in connection with transfer of users is, that if the 
      username contains a "." then the packing of users for transfer does not 
      work. This is particular relevant for internal DEC installations.
      
      
      Vagn
T.RTitleUserPersonal
Name		DateLines
1984.1NO ANSWERS I'M AFRAIDIOSG::TALLETTGimmee an Alpha colour notebook...Fri Dec 18 1992 12:028
    
    	I'm afraid the guy that wrote this code has been TFSO'd and I
    	don't know the answer to your question.
    
    	It was thoroughly tested before V3.0 shipped and it worked.
    
    Regards,
    Paul
1984.2An advert for STARSIOSG::WICKSALeft alone in IOSG's rabbit warrenFri Dec 18 1992 14:028
    Vagn,
    
    Did STARS not show anything on these problems - the one about period
    characters sounds awfully familiar.
    
    regards,
    
    Andrew.D.wicks
1984.3Mails have status archived after user transferZUR01::TOLBAFri Jun 04 1993 19:12132
Hello,

I also found a problem transferring a user from A1V2.4 to A1V3.0 (without
K701). We have a German version. 

After transferred the user the mails had status archived. Next to a pointer	
GELESEN (READ) or VERSENDET (OUTBOX) there is also a 2nd pointer in a folder
called Archivierte Schriftst�cke (Archived documents).

I made then the suggested changes to SM_MAS_ARCHIVE_V2.scp according to note
1984.0. After that the duplicate pointer in the Archived Doc. Folder is 
eliminated but still the mails have status archived.

Then I enabled the trace in OA$liB:SM_MAS_ARCHIVE_V2.SCP and run 
another transfer user.

an extract of the A1Trace.log shows:

...
![SYMBOL] Symbol = OA$CURDOC, Value = ARCHIVIERTE SCHRIFTST�CKE     000001
![IO]     Getting record from DOCDB, Key = ARCHIVIERTE SCHRIFTST�CKE     999999,
!                Key-of-ref = DOCUMENT/0
![IO]     Getting field TYPE from DOCDB, Value = ARCHIVE
![IO]     Getting field MAIL_STATUS from DOCDB, Value = ARCHIVED
![IO]     Getting field DELETE from DOCDB, Value = Y
![IO]     Getting field MODIFY from DOCDB, Value = N
![IO]     Deleting record from DOCDB, Key = ARCHIVIERTE SCHRIFTST�CKE     999999
![IO]     Getting next record from TXT$TXL_DO, Text starts "CAB SELECT , #D"
![SCRIPT] OA$LIB:SM_MAS_ARCHIVE_V2 Line 196: CAB SELECT , #DOC_NUM,,OA$CURDOC
![FUNC]   Function = CAB, Cmd line = SELECT , #DOC_NUM,,OA$CURDOC
![SYMBOL] Symbol = , Value = 
![SYMBOL] Symbol = #DOC_NUM, Value = 000001
![SYMBOL] Symbol = , Value = 
![IO]     Releasing record locks on DOCDB
![IO]     Getting record from DOCDB, Key = 999999, Key-of-ref = DOCNUM/1
![IO]     Getting field TYPE from DOCDB, Value = ARCHIVE
![IO]     Getting field MAIL_STATUS from DOCDB, Value = ARCHIVED
![IO]     Getting field DELETE from DOCDB, Value = Y
![IO]     Getting field MODIFY from DOCDB, Value = N
![IO]     Getting next record from TXT$TXL_DO, Text starts "WRITE CHANGE CA"
![SCRIPT] OA$LIB:SM_MAS_ARCHIVE_V2 Line 197: WRITE CHANGE CAB$ .%KEY=OA$CURDOC, 
!               MAIL_STATUS="ARCHIVED"
![FUNC]   Function = WRITE, Cmd line = CHANGE CAB$ .%KEY=OA$CURDOC, MAIL_STATUS=
!               "ARCHIVED"
![SYMBOL] Symbol = OA$CURDOC, Value = VERSENDET                     000001
![IO]     Getting record from DOCDB, Key = VERSENDET                     999999,
!                Key-of-ref = DOCUMENT/0
![IO]     Getting field TYPE from DOCDB, Value = ARCHIVE
![IO]     Getting field MAIL_STATUS from DOCDB, Value = ARCHIVED
![IO]     Getting field DELETE from DOCDB, Value = Y
![IO]     Getting field MODIFY from DOCDB, Value = N
![SYMBOL] Symbol = "ARCHIVED", Value = ARCHIVED
![IO]     Getting field MAIL_STATUS from DOCDB, Value = ARCHIVED
![IO]     Updating current record in DOCDB
![IO]     Releasing record locks on DOCDB
![IO]     Getting next record from TXT$TXL_DO, Text starts "GET OA$FUNCTION"
![IO]     Getting next record from TXT$TXL_DO, Text starts "'#ARCHIVE_FILE "
![SCRIPT] OA$LIB:SM_MAS_ARCHIVE_V2 Line 199: GET OA$FUNCTION='RESTORE_DOCUMENT '
!                '#ARCHIVE_FILE , OA$CURDOC_DOCNUM'
![FUNC]   Function = GET, Cmd line = OA$FUNCTION='RESTORE_DOCUMENT ' '#ARCHIVE_F
!               ILE , OA$CURDOC_DOCNUM'
![FUNC]   Function = RESTORE_DOCUMENT, Cmd line = #ARCHIVE_FILE , OA$CURDOC_DOCN
!               UM
![SYMBOL] Symbol = #ARCHIVE_FILE, Value = TRANSFER$AREA:MATTRANS1621000001.ARCHI
!               VE
![SYMBOL] Symbol = OA$CURDOC_DOCNUM, Value = 000001

vvvvvvvvvvvvvvvvvvvvvvvv

![IO]     Opening ARCHIVE_SETS_DATA, File = OA$DATA_SHARE:ARCHIVE_SETS_DATA.DAT,
!                Class = DATA, Mode = UPDATE
![IO]     Rewinding ARCHIVE_SETS_DATA, Key-of-ref = AREA_ID/0
![IO]     Getting record from ARCHIVE_SETS_DATA, Key = , Key-of-ref = AREA_ID/0
![IO]     Status = record not found


![IO]     Closing ARCHIVE_SETS_DATA, File = OA$DATA_SHARE:ARCHIVE_SETS_DATA.DAT
![IO]     Getting record from DOCDB, Key = 999999, Key-of-ref = DOCNUM/1
![IO]     Getting field TYPE from DOCDB, Value = ARCHIVE
![IO]     Getting field MAIL_STATUS from DOCDB, Value = ARCHIVED
![IO]     Getting field DELETE from DOCDB, Value = Y
![IO]     Getting field MODIFY from DOCDB, Value = N
![SYMBOL] Symbol = OA$FUNCTION='RESTORE_DOCUMENT ' '#ARCHIVE_FILE , OA$CURDOC_DO
!               CNUM', Value = RESTORE_DOCUMENT #ARCHIVE_FILE , OA$CURDOC_DOCNUM
![IO]     Getting next record from TXT$TXL_DO, Text starts ".IF NOT OA$STAT"
![SCRIPT] OA$LIB:SM_MAS_ARCHIVE_V2 Line 200: .IF NOT OA$STATUS THEN .GOTO LOG_RE
!               COVERY_ERROR
![SYMBOL] Symbol = OA$STATUS, Value = 0
![SCRIPT] IF Operation starting
![SCRIPT] .IF condition NOT OA$STATUS  is TRUE
![SCRIPT] THEN Operation starting
![SCRIPT] OA$LIB:SM_MAS_ARCHIVE_V2 Line 200: .GOTO LOG_RECOVERY_ERROR
![IO]     Getting next record from TXT$TXL_DO, Text starts ".IF NOT #OLD_VE"
![IO]     Getting next record from TXT$TXL_DO, Text starts "CAB REFILE_DOCU"
![IO]     Getting next record from TXT$TXL_DO, Text starts "!"
![IO]     Getting next record from TXT$TXL_DO, Text starts ".LABEL CHECK_PT"
![IO]     Getting next record from TXT$TXL_DO, Text starts ".IF NOT #OLD_VE"
.....


In the following there is an extract of the oa$load_MAT02TRANS.LOG:

...
Starting processing MAT02TRANS
Originating Version 2.4
Opening logfiles...
NEWDIR to MAT02TRANS
Defined logical TRANSFER$AREA as oa$loaduser:[MAT02TRANS.MAT02TRANS]
Created index of private documents as SYS$LOGIN:MAS_PVT_DOCLIST0000168B_MAS.DAT
Calling SM_MAS_NEXT_SAVESET_V2.COM 
Opening archived documents listing
Consult document log - failed to process a document correctly
..
Calling SM_MAS_NEXT_SAVESET_V2.COM 
Remove auto reply file
Unlocking the account
%OA-W-ARCTARGNOTARC, Das Zieldokument befindet sich nicht im Archiv.
....


I am wondering that the script is looking for an entry in ARCHIVE_SETS_DATA.

So my question: do I have to create an Archive Area Entry before transferring 
a user. In the Mgmt Guide I did not see anything mentioned about this. 
If it has not to be done manually where else is it done - I did not see any-
thing in SM_MAS_ARCHIVE_V2.SCP neither in SM_MAS_archive_v2.com


If anybody has an idea - please let me know.

Thanks for your help and regards,
Manuela
1984.4please, check "known bugs"VAXRIO::CALL_MARCIAFri Jun 04 1993 23:2310
    Hello Manuela,
    
    I'm not sure whether this has anything to do with your problem, but
    there was a bug in the German V3.0.
    Please read Nr. 7 in
    
    	PETRUS::DIAMOND$BUGFIXES$PUBLIC:[GERMAN]README.TXT
    
    
    	Stefan (PAULUS::HOFMANN, from remote account)
1984.5Loading a V2.4 on a V3.0-1 System WORKSZUR01::TOLBAMon Jun 07 1993 13:5411
Hello Stefan,

Thanks for your reply - you are right with the K701. On a ALL-IN-1 V3.0-1
system there is no problem loading a V2.4 user. To my suprise the mails
are in OA$SHARx and not private.

The suggested changes of note 1984.0 in SM_MAS_ARCHIVE_V2.scp are not 
necessary.

Thanks and regards,
Manuela