Conference cookie::archive_backup

Couple of questions:

 - Version of Motif?
 - Version of VMS?
 - There are a couple ways of creating a save request.  Does the gui
   fail when he pushes the save button at the botton, or when he
   uses the Create->Save Request pulldown option?

It will also be good information to know if LUI works for them.  

The ABS$POLICY_CONFIG.DAT probably doesn't have anything to do with this.
This is read in during the GUI startup, but the GUI itself doesn't
do anything with the values.  The information in the policy configuration
file is for the policy engine startup, message leveling, etc. con

Kim

Couple of questions:

 - Version of Motif?
     
     V1.2-4a

 - Version of VMS?
 
     V6.2-1h3

 - There are a couple ways of creating a save request.  Does the gui
    fail when he pushes the save button at the botton, or when he
    uses the Create->Save Request pulldown option?

    It fails both ways.

The Lui did not crash.  He said he exercised it pretty hard.  The only 
piece that did not work is when he did a save, he received the following 
messages:


  coordinator: sysput service failed on a TLE
  coordinator:  facility ABS:abs_sysput_failed_tle, sys$put service failed on 
                       a TLE  
  coordinator: line=59, file=RESD$:[SRC]coordinator.c;1

This sequence repeated about 5 times naming a different file each time.

He is applying a patch for MOTIF that addresses an issue whereby when DW-Motif
goes inot a fail safe condition, the login box does not reappear.  Actually,
he has applied the patch but cannot reboot the system so he has to wait
until a reboot can be scheduled - he has a call into the Motif team to see
if the is really needed.

Thanks,

Victoria

    
    Hi,
    
    Can you post the whole save log from the failed run?  The information
    is partial and the line number 59 is a comment line (it cannot singal
    error, you see).
    
    We need the whole diag dump to see how things failed.
    
    Masami

Something else to look at:

Did the customer upgrade from V2.0?  If so, make sure the catalogs have
been converted to the new format.  If this was an upgrade from V2.0 they
need to modify the following file.

ABS$SYSTEM:CONVERT_CATALOG_V21.COM

OLD:
$     Convert/FDL=ABS$SYSTEM:TLE_BRIEF.FDL -
                 ABS_CATALOG:'P1'_BTLE.DAT ABS_CATALOG:'P1'_BTLE.DAT

NEW:
$     Convert/FDL=ABS$SYSTEM:TLE_BRIEF.FDL/PAD=" " -
                 ABS_CATALOG:'P1'_BTLE.DAT ABS_CATALOG:'P1'_BTLE.DAT


Kim

Hi,

We did the convert on the catalog as per Kim's request.  We also did the
following:

  create/fdl=abs$system:aoe_brief.fdl abs_catalog:abs_cat_staged_baoe.dat
  
create/fdl=abs$system:aoe_instance_brief.fdl
abs_catalog:abs_cat_staged_baoe_ins
nc.dat
   create/fdl=abs$system:tle_brief.fdl abs_catalog:abs_cat_staged_btle.dat


   The GUI save request dumps him out completely - the Lui
returns the error I reported earlier.

I had him do a 'set host 0/log=craig.2'.  He is sending me the log file.  I will
put it in csc32::Dumps:[v_heinicke].  There will be a Craig.log and a 
Craig2.log with W:RE on it. 

I will try and remove the PABUI_SESSION.log file as it was created on FEB 26th
and does not relate to this problem.  No new files were created.

Hope this helps.  

Thanks,

Victoria

I did not see either craig.log or craig2.log, but I did find a
craig.txt and a craig1.txt.  I've got some comments on craig1.txt

Based upon the information in craig1.txt, it looks like the installation
did not work properly.  Were there any failures during the installation?


>Initializing Save Request SYSTEM_26-FEB-1997_15_50_03_38
>Storage Class SYSTEM_BACKUPS does not exist.  Please choose a known Storage Clas
>s.
>Error is: Storage class not found
>Facility ABS:  ABS_ARCH_CLASS_NOT_FOUND, Storage class not found
>   Line = 177, File = RESD$:[SRC]API_C_SHOW_ARCH_CLASS.C;1
>Facility ABS:  ABS_ARCH_CLASS_NOT_FOUND, Storage class not found
>   Line = 112, File = RESD$:[SRC]API_S_SHOW_ARCH_CLASS.C;1
>Facility ABS:  ABS_ARCH_CLASS_NOT_FOUND, Storage class not found
>   Line = 318, File = RESD$:[SRC]ARCHIVE_CLASS_READ.C;1
>Facility ABS:  ABS_ARCH_CLASS_NOT_FOUND, Storage class not found
>   Line = 562, File = RESD$:[SRC]ARCHIVE_CLASS_READ.C;1
>Facility ABS:  ABS_ARCH_CLASS_NOT_FOUND, Storage class not found
>   Line = 1583, File = RESD$:[SRC]ARCHIVE_CLASS_READ.C;1
>Facility ABS:  ABS_ARCH_CLASS_NOT_FOUND, Storage class not found
>   %RMS-E-RNF, record not found
>Facility ABS:  ABS_ARCH_CLASS_NOT_FOUND, Storage class not found
>   SQL error code = 100, Line = 2015, File = RESD$:[SRC]ARCHIVE_CLASS_READ.C;1


The storage class used by the save request is not found.  Have them
do a "$ABS SHOW STORAGE foo" using the storage class name referenced
in the save request.  If the storage class is not there, have them
run the ABS$SYSTEM:EPCOT_DB_INIT.EXE program.

> Submission of Save Request SYSTEM_26-FEB-1997_15_50_03_38 failed for the follow
>ing reason:
>Execution env not found
>Facility ABS:  ABS_EXEC_ENVIR_NOT_FOUND, Execution env not found
>   Line = 705, File = RESD$:[SRC]API_C_CRE_ARCH_REQ.C;1
>Facility ABS:  ABS_EXEC_ENVIR_NOT_FOUND, Execution env not found
>   Line = 550, File = RESD$:[SRC]API_C_CRE_ARCH_REQ.C;1
>Facility ABS:  ABS_EXEC_ENVIR_NOT_FOUND, Execution env not found
>   Line = 297, File = RESD$:[SRC]API_S_CRE_ARCH_REQ.C;1
>Facility ABS:  ABS_EXEC_ENVIR_NOT_FOUND, Execution env not found
>   Line = 112, File = RESD$:[SRC]API_S_SHOW_EXEC_ENVIR.C;1
>Facility ABS:  ABS_EXEC_ENVIR_NOT_FOUND, Execution env not found
>   Line = 344, File = RESD$:[SRC]EXECUTION_ENV_READ.C;1
>Facility ABS:  ABS_EXEC_ENVIR_NOT_FOUND, Execution env not found
>   Line = 583, File = RESD$:[SRC]EXECUTION_ENV_READ.C;1
>Facility ABS:  ABS_EXEC_ENVIR_NOT_FOUND, Execution env not found
>   Line = 1713, File = RESD$:[SRC]EXECUTION_ENV_READ.C;1
>Facility ABS:  ABS_EXEC_ENVIR_NOT_FOUND, Execution env not found
>   %RMS-E-RNF, record not found
>Facility ABS:  ABS_EXEC_ENVIR_NOT_FOUND, Execution env not found
>   SQL error code = 100, Line = 2092, File = RESD$:[SRC]EXECUTION_ENV_READ.C;1

The execution environment used by the save request is not found.  Have them
do a "$ABS SHOW ENVIRONMENT foo" using the execution environment name 
referenced in the save request.  If the environment is not there you
can run ABS$SYSTEM:EPCOT_DB_INIT.EXE to get the ABS default storage class/
execution environment pairs initialized.

>COORDINATOR:  Failed to access Storage Class
>COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage
> Class
>COORDINATOR:     Line = 736, File = RESD$:[SRC]COORDINATOR.C;1
>COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage
> Class
>COORDINATOR:     Line = 370,Press RETURN to continue_ARCHIVE_MANAGEMENT.C;1
>COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage
> Class
>COORDINATOR:     Line = 704, File = RESD$:[SRC]COORD_ARCHIVE_MANAGEMENT.C;1
>COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage
> Class
>COORDINATOR:     Line = 469, File = RESD$:[SRC]ARCHIVE_FILE_SYSTEM.C;1
>COORDINATOR:  Facility ABS:  ABS_SLS_ALLOC_FAILED, Failed to allocate a volume v
>ia SLS
>COORDINATOR:     Line = 1556, File = RESD$:[SRC]SLS_SERVICES.C;1
>COORDINATOR:  Facility ABS:  ABS_SLS_ALLOC_FAILED, Failed to allocate a volume v
>ia SLS
>COORDINATOR:     Line = 3421, File = RESD$:[SRC]SLS_SERVICES.C;1
>COORDINATOR:  Facility ABS:  ABS_SLS_ALLOC_FAILED, Failed to allocate a volume v
>ia SLS
>COORDINATOR:     Line = 3610, File = RESD$:[SRC]SLS_SERVICES.C;1
>COORDINATOR:  Facility ABS:  ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific erro
>r in diag block
>COORDINATOR:     %SLS-W-NETCONERR, failed to connect to network task !AS at !%D
>COORDINATOR:  Final status is Failed to access Storage Class

ABS tried to connect to SLS, but was not able to.  The SLS$DBX object
was not available.  Either SLS is not up and running or it is not
installed/configured properly.



>   The GUI save request dumps him out completely - the Lui
>returns the error I reported earlier.

Is the customer able to use DCL to create save requests?


The catalog configuration discussed in a previous note will not
effect the GUI.  If the catalog configuration was a problem, you
would find errors in the save request log file.

Is the customer upgrading from V2.0?  If they are *not* upgrading from
v2.0, (in other words, a new installation), the catalog conversion
is not an issue.  

Also, please provide the entire save request log file for the failing
save request.

Kim

Hi,

I've just had a customer log a call with the same stack dump but under different
circumstances. In his own words -

>We have a DEC 3000-300 running VMS 7.1 and UCX 4.1 ECO 2
>We've got some temporary PAKS for testing ABS v2.1 - what we want to do is use
>our VMS servers to back up NT systems. I've installed MDMS on to the Alpha
>followed by ABS. We can fire up the GUI interface but it keeps crashing out. It
>continually crashes on the 'Storage Class Retention' on the SAVE screen. I've
>looked at the Bookreader documentation and printed this off, but it all seems a
>bit dis-jointed. We've connected to the GUI interface via the Alpha console, a
>VXT and Exceed under Windows 3.1 - all with similar results. The NT client side
>has been installed on an NT 4 Workstation. I installed ABS from the latest CD
>distribution (ie. Mar 97).
>Am I missing something obvious here - we need to get this s/ware tested quickly
>if it's to be considered in an NT rollout backup strategy.

For completeness, I asked him for some more supporting information -

>as soon as I click on the retention period option, the
>ABS windows all disappear. The following are returned to
>the calling DECterm procedure :
>
>PGRV17::SYSCON>abs/inter=decw
>Exception                          Module                   Line
>Exception Reraised by:             PABUI_XWINDOW            848
>Exception Reraised by:             PABUI_MAINWINDOW         5028
>exception                          PABUI_MAINWINDOW         5137

As you can see, this matches the info given in the base note.

So, any ideas ?

Many thanks,

Simon R. Mills
OpenVMS Group, UK CSC

    
    There was another reply posted here from COMICS::MILLSS.  It's now
    moved to a new entry 437.
    
    Masami