Conference cookie::archive_backup

434.0. "collection of ABS 2.0 to 2.1 upgrade issues" by ATZIS1::PIEBER (chaos has many faces) Thu Apr 17 1997 10:39

    Hi,
    
    maybe someone can profit from this experience:
    
    Before, during and after the upgrade from ABS 2.0 to 2.1, there are
    some issues to take care of:
    
    Before the upgrade:
    -------------------
    
    --> The ABS installation guide lists a minimum of 80 for the SYSGEN
        PROCSECTCNT parameter, the kitinstal complains, unless at a minimum
        of 100.
    
    Aktion: make sure, you have 100 to avoid the complaints from kitinstal.
            However, there are no functional restrictions, I can tell, if 
            the parameter is at 80 and you ignore the complaint. Kitinstal
    	    will continue.
    
    Status: QAR 1870. Fixed in next ABS release, according to ABS
            engineering.
    
    
    --> make sure, you have a proxy database on your system. Otherwise
        the upgrade procedure will fail.
    
    Action: create a proxy database with UAF> CREATE/PROXY
    
    Status: Fixed in next release, according to ABS engineering.
    
    
    --> ABS installation over-writes ABS UAF settings.
    
    Action: Take a snapshot of the UAF settings, before applying the
            installation and re-apply them after the upgrade.
    
    Status: QAR 1853.
    
    
    During the upgrade on a VMS client:
    -----------------------------------
    
    --> The IVP fails, since it checks the existence of Policy Engine
        files, which are only required on the Central Security Domain - CSD.
    
    Action: None.
    
    Status: Fixed in next release, according to ABS engineering.
    
    
    
    After the upgrade of ABS:
    -------------------------
    
    --> Catalog conversion fails.
    	It's required, that all catalogs from ABS 2.0 be converted to the
    	new format of 2.1. The procedure ABS$SYSTEM:CONVERT_CATALOG_V21.COM
    	fails to convert the third file, <catalog>_BTLE.DAT. The _BTLE file 
    	would then contain zero records and all informations for ABS REPORT 
    	SAVE_LOG would be lost.
    
    Action: Modify the above procedure, to use /PAD=%X20 on the
    	corresponding conversion command. This will append blanks to the
    	former 1576 bytes _BTLE records to produce the new 1822 bytes/record.
    	Then run the conversion.
    
    Status: unknown.
    
    
    Ewald.

    
    Ewald,
    
    Thank you very much for the extensive list of problems and solutions.
    I'm sure we'll all benefit from this.
    
    Masami