[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

472.0. "FCO problem" by BEJVC::MASCOTTANG () Mon Apr 13 1992 10:49

      I face a problem when I use FCO to re-organisation file. I find
    that I cannot do successfully. the error message is 
     
      "OAUSER:DOCDB.DAT;-1 file not find"
    
    After I enable the trace log functions. I find that my directory
    cannot be created a new DOCDB.DAT files. The file protection is
    (s:rwe,o:rew,g:re),and no file version limit.
    
    My system is installed ALLIN1 V2.3 with CVMS/HANZI V5.4-2. Is it
    the local language to influence the file re-organisation ?
    
                                                              
    Would anyone can solve my problem.

T.R Title User Personal
Name Date Lines

472.1 Old problem? UTRTSC::BOSMAN We're just sugar mice in the rain Mon Apr 13 1992 10:58 43

T.R	Title	User	Personal Name	Date	Lines
472.1	Old problem?	UTRTSC::BOSMAN	We're just sugar mice in the rain	`Mon Apr 13 1992 10:58`	43
	Hi, This was an old problem. The FCO code assumes that their is a previous DOCDB.DAT. Read the STARS article listed below. Sjaak. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ DCL-W-UNDSYM Errors Associated With DOCDB.DAT When User Attempts FCO COPYRIGHT (c) 1988, 1989, 1990 by Digital Equipment Corporation. ALL RIGHTS RESERVED. No distribution except as provided under contract. PRODUCT: ALL-IN-1 V2.1, V2.2, V2.3 SOURCE: Customer Support Center/Atlanta USA SYMPTOM/PROBLEM: We had OA$CAB_FILE_PURGE_COUNT set to 1 to solve a problem in ALL-IN-1 V2.1 where File Cabinet Reorganization would fail if user was low on diskquota. The ALL-IN-1 V2.2 script now checks for disk-quota, so it assumes there will be previous versions of DOCDB.DAT and DAF.DAT. This generates lots of DCL-W-UNDSYM errors associated with DOCDB.DAT;-1 and DAF.DAT;-1 - and lots of worried users. The problem is fixed by setting OA$CAB_FILE_PURGE_COUNT to 2 or more. There should be a check in the script file for the symbol value, or the problem should at least be documented. SOLUTION: The Release Notes on Page 28 for ALL-IN-1 V2.2 state that if you set OA$CAB_FILE_PURGE_COUNT to 1, you will get several DCL error messages that you can ignore, but if you need to change your File Cabinet protection (for example if you have a Shared Folder that you want other users to be able to access) you must change the default VMS protection to be the same as you want your File Cabinet protection to be. This problem is resolved in V2.4.

    Hi,
    
    This was an old problem. The FCO code assumes that their is a previous
    DOCDB.DAT. Read the STARS article listed below.
    
    Sjaak.
    
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    
DCL-W-UNDSYM Errors Associated With DOCDB.DAT When User Attempts FCO


COPYRIGHT (c) 1988, 1989, 1990 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.

PRODUCT: ALL-IN-1 V2.1, V2.2, V2.3

SOURCE: Customer Support Center/Atlanta USA

SYMPTOM/PROBLEM:

We had OA$CAB_FILE_PURGE_COUNT set to 1 to solve a problem in ALL-IN-1
V2.1 where File Cabinet Reorganization would fail if user was low on
diskquota.  The ALL-IN-1 V2.2 script now checks for disk-quota, so it
assumes there will be previous versions of DOCDB.DAT and DAF.DAT.  This
generates lots of DCL-W-UNDSYM errors associated with DOCDB.DAT;-1 and
DAF.DAT;-1 - and lots of worried users. 

The problem is fixed by setting OA$CAB_FILE_PURGE_COUNT to 2 or more.
There should be a check in the script file for the symbol value, or
the problem should at least be documented. 

SOLUTION:
  
The Release Notes on Page 28 for ALL-IN-1 V2.2 state that if you set
OA$CAB_FILE_PURGE_COUNT to 1, you will get several DCL error messages
that you can ignore, but if you need to change your File Cabinet
protection (for example if you have a Shared Folder that you want
other users to be able to access) you must change the default VMS
protection to be the same as you want your File Cabinet protection to
be. 

This problem is resolved in V2.4.