RE: I'm I talking rubbish or....

["Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>]

Steven,

A file (or record) lock would not be the likely culprit unless you've
changed the default wait time in WAITFILE and WAITRCD characteristics of
your files.  The default for WAITFILE is *IMMED and the default for
WAITRCD is 60 seconds.  Your programs will 'error out' if the file or
record cannot be allocated in the appropriate amount of time.  You would
have to have some specific coding in place to prevent an error from
occuring.

I do recall your earlier postings, but I seem to remember that I didn't
feel that there was enough information to offer a suggestion.  Can you
reiterate?

Is it your green-screen sessions in a particular network segment within
your enterprise?

Regards,
Andy Nolen-Parkhouse

> Subject: I'm I talking rubbish or....
>
> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Regular readers will know I have a problem with our Despatch Area
locking
> up, nobody knows why.
> We've had you give suggestions.
> ASsist/400...
> IBM Networking...
> Our software house...
>
> Blank all round.
>
> Now there's been an interesting thread on midrange this week, and I
was
> wondering could a user saving a Query 400 definition cause a file lock
in
> our Despatch Area WITHOUT the AS/400 reporting the job(s) as being
locked?
>
> Steven Donnellan