RE: RV: QDBSRV IN LCK, please help!

["Alexei Pytel" <pytel@xxxxxxxxxx>]

If it repeats approximately at the same time, it could be a clue.
If at this time your application is creating or deleting a very much number
of files, system may not be able to handle all these immediately. It falls
back and causes all kinds of delays with file accesses.
You may use DSPJOB OPTION(*JOBLCK) command to see what locks are being
waited on.

    Alexei Pytel



Dimitri Efimov <defimov@wiese.com.pe>@midrange.com on 02/06/2001 04:24:24
PM

Please respond to MIDRANGE-L@midrange.com

Sent by:  owner-midrange-l@midrange.com


To:   MIDRANGE-L@midrange.com
cc:
Subject:  RE: RV: QDBSRV IN LCK, please help!



Last RCLSTG run a lot of time ago (it's a baknig system 24 hours 365 days),
but it looks like there is not any damages of QADB*, but the problem
repeate
each day almoust the same time!

Thanks a lot,

Dmitri

-----Mensaje original-----
De: Pete Massiello [mailto:pmassiello@os-solutions.com]
Enviado el: martes, 06 de febrero de 2001 12:58
Para: MIDRANGE-L@midrange.com
Asunto: Re: RV: QDBSRV IN LCK, please help!


I once saw something similar when their was some damage on one of the QADB*
files.  The files needed to be rebuilt, which is one of the things that
RCLSTG
does.  The fix was to run a RCLSTG.  Not sure if that is what your problem
is,
but when was the last time you ran a RCLSTG?

    Have you recently upgraded your machine, or done anything else that may
provide a clue?

    Pete Massiello

Dimitri Efimov wrote:

> > Can somebody help me with this, please:
> > 1. Why ALL jobs QDBSRV01-25 (as far as I know, theese jobs rebuid
access
> > paths.) change status to LCKW in our system (740)? They keep this
status
> > for a 30 - 40 min.
> > 2. Can it be a cause of partial system block - looks like other
programs
> > cannot add new records in files   ?
> >
> >
> > Any ideas, please!
> >
> > Dmitri Efimov
> >
> > Banco Wiese Sudameris
> >
> >
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---