[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

2847.0. "%RMS-W-TMO, %OAFC-E-INTERR, and %RMS-F-EXENQLM" by TINNIE::SETHI (Ahhhh (-: an upside down smile from OZ) Fri Jun 11 1993 02:06

    Hi yet again FCS people :-),
    
    Sorry it was a bad day for FCS problems yesterday and the system was
    unusable at times.  Same customer as topic 2846 but with a different
    error message (for those of you who want to know who the customer is
    Woodside, sends a shudder up the spine :-}).  Again version 3.0-1
    installed.
    
    The customer has had the following reported in the OAFC$SERVER.LOG:
    
    10-JUN-1993 13:28:24.65  Server: PER1::"73="  Error: %RMS-W-TMO, time
    out period expired  Message: CsiReserve; unable to get info about
    reserved doc
    
    10-JUN-1993 10:32:29.35  Server: PER2::"73="
    Error: %OAFC-E-INTERR, Internal error in File Cabinet Server
     Message: FCS has access violated, please submit an SPR.
    
    10-JUN-1993 13:20:30.94  Server: PER2::"73="  Error:
    %RMS-F-EXENQLM, exceeded enqueue quota  Message: CsiOpenRmsFileCab;
    error getting record: CAPORN,M
    
    10-JUN-1993 13:20:30.94  Server: PER2::"73="  Error:
    %RMS-F-EXENQLM, exceeded enqueue quota  Message: CsiOpenRmsFileCab;
    error getting record: CAPORN,M
    
    10-JUN-1993 13:20:31.55  Server: PER2::"73="  Error: %RMS-F-EXENQLM,
    exceeded enqueue quota  Message: CsiOpenRmsFileCab; error getting
    record: STUDENT,M46
    
    PQL_MENQLM is set to 400 and the users Enqlm is 300.
    
    The customer has:
    
    MAX CLIENT CONNECTS set to 350 was 500
    MAX DRAWERS was 50 it's now set to 130
    
    The FCS had to be stopped and restarted.  What do all of these error
    messages mean and what caused them ?
    
    Regards,
    
    Sunil

T.R Title User Personal
Name Date Lines

2847.1 My guess IOSG::CHINNICK gone walkabout Fri Jun 11 1993 12:20 34

T.R	Title	User	Personal Name	Date	Lines
2847.1	My guess	IOSG::CHINNICK	gone walkabout	`Fri Jun 11 1993 12:20`	34
	Hi Sunil... I'll have a stab at a couple of these, but I'm just coming at it from an IOS standpoint. The RMS$_TMO "timeout period expired" results from a record lock on the DOCDB file. IOS and FCS use a timeout when waiting for record locks. IOS uses a value of 30 seconds on all RMS files and FCS uses 10 seconds. Normally this message is masked back to be an OafcDocumentLocked error. Just means that some users collided trying to do some operation on a drawer - maybe while IOS was accessing it. The INTERR - who knows?? But once this happens, things may get unpredictable. I'll leave this for someone else to guess at. The RMS$_EXENQLM "exceeded enqueue quota" is probably just that. If you have been getting problems with threads dying, then locks will probably be left outstanding and files left open - resulting in a gradual decrease in available locks. There might be a problem with locks not being released - since much of the processing uses manual unlocking - but you'ld have to investigate a lot further to prove any such problem exists. The FCS startup normally runs up with 4096 for ENQLM - the customer isn't overriding this are they?? For IOS users, I'd recommend 1200 for ENQLM, but this is the FCS having problems so you could try defining OAFC$SERVER_ENQLM logical with a larger value. You might check the current server quotas using $ SHOW PROCESS/QUOTA to see what value is available. Check periodically and see if it decreases over a few hours/days. Paul.

    
    Hi Sunil...
    
    I'll have a stab at a couple of these, but I'm just coming at it from
    an IOS standpoint.
    
    The RMS$_TMO "timeout period expired" results from a record lock on
    the DOCDB file. IOS and FCS use a timeout when waiting for
    record locks. IOS uses a value of 30 seconds on all RMS files and FCS
    uses 10 seconds. Normally this message is masked back to be an
    OafcDocumentLocked error. Just means that some users collided trying to
    do some operation on a drawer - maybe while IOS was accessing it.
    
    The INTERR - who knows?? But once this happens, things may get
    unpredictable. I'll leave this for someone else to guess at.
    
    The RMS$_EXENQLM "exceeded enqueue quota" is probably just that. If you
    have been getting problems with threads dying, then locks will probably
    be left outstanding and files left open - resulting in a gradual
    decrease in available locks. There might be a problem with locks not
    being released - since much of the processing uses manual unlocking -
    but you'ld have to investigate a lot further to prove any such problem
    exists.
    
    The FCS startup normally runs up with 4096 for ENQLM - the customer
    isn't overriding this are they?? For IOS users, I'd recommend 1200 for
    ENQLM, but this is the FCS having problems so you could try defining
    OAFC$SERVER_ENQLM logical with a larger value. You might check the
    current server quotas using $ SHOW PROCESS/QUOTA to see what value is
    available. Check periodically and see if it decreases over a few
    hours/days.
    
    Paul.