RE: Errors, errors, errors...WAN or dial-up, it doesn't matter...

Reeve:

>>there are many times when I hang and no network error is reported.  I
>>have problems with unexplained client lockups as well as with the host
>>server job losing contact and holding onto the member.

      Remember the dirty flag problem you reported? That is one of the
editor problems which have also caused the 'hang' phenomenon when it
receives a communications error. For example, you might see a return code
-6 and a message in the macro log like    "Error writing file C:
\WDT400\Tmp\Q0000006.400 - original file may be corrupted or read only".
Usually network error is logged only if there is a request to the
underlying communications component. In this case, the editor itself has
failed already.
      When the network is down, the AS/400 host server job does not know.
When CODE initiates a request and finds that the corresponding host job
connection is gone, a new connection job is established. Meanwhile, the
previous server job is still waiting forever for requests, holding the
objects locked by it. This orphan QZRCSRVS job needs to be terminated.

>>is there any reengineering scheduled to solve the problem once and for
all?

As far as I understand it, there is currently no planned effort to have
the entire existing CODE communications revamped. However, we are still
working with the our underlying communications component to see if this
"object locked/hang" problem can be alleviated.


Best regards,
    Hak
_______________________
Hak Lui
AS/400 AD, IBM Canada Ltd.
e-mail: haklui@ca.ibm.com