[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

874.0. ""Permitted Overquota" interrrupts FCO" by JSOCSS::UNO (STOP! IN THE NAME OF DIGITAL) Tue Jun 16 1992 04:13

Hello--

I would like to ask you about FCO function.

One user tried to invoke FCO.  And there happened no error.  But we found
that DOCDB.DAT and DAF.DAT had not been renewed.  

We checked his ALL-IN-1 profile and then removed the datum from the field of
"Permitted Overquota" and retried.  After that, everything went well.

But I can't understand why "Permitted Overquota" concerns FCO.

Do you have any ideas?

							Natsuko Uno
							DEC Japan

T.R Title User Personal
Name Date Lines

874.1 IOSG::MAURICE A week is a long time in office politics Tue Jun 16 1992 09:35 11

T.R	Title	User	Personal Name	Date	Lines
874.1		IOSG::MAURICE	A week is a long time in office politics	`Tue Jun 16 1992 09:35`	11
	If FCO has not been customised then the "Permitted Overquota" field will not affect it. That it worked after blanking it would have been happenstance. The quota that can affect it is VMS disk quota. So check for customisations. Check the user's disk quota. And if you are running in Japanese check that the error messages reported by FCO have not been lost in translation. Cheers Stuart

    If FCO has not been customised then the "Permitted Overquota" field
    will not affect it. That it worked after blanking it would have been
    happenstance. The quota that can affect it is VMS disk quota.
    
    So check for customisations. Check the user's disk quota. And if you
    are running in Japanese check that the error messages reported by FCO
    have not been lost in translation.
    
    Cheers
    
    Stuart