We're getting an rc 4, rsn x407 error back from the ZLogstream constructor.
No worries, we can note that we've lost some data and continue processing - except that the constructor is returning null rather than a ZLogstream object...
The description of the rc 4, rsn x407 response is:
(From: https://www.ibm.com/support/knowledgece ... 300223.htm)"X'00000407'" IXGCONN and IXGWRITE request. Explanation: Environment error. The request was successful, but there may be log blocks permanently missing between this log block and the one previously returned. This condition occurs when a system or coupling facility fails and not all of the data in the log stream could be recovered. Action: If your application cannot tolerate any data loss, stop issuing system logger services to this log stream, disconnect from the log stream, and reconnect to a new, undamaged log stream. You can continue using the log stream if your applications can tolerate data loss.
We just want to continue processing the logstream, because there is new data turning up.
As it is, we can't even connect to the logstream to try clearing it, so waiting for the user to delete and manually redefine it seems to be our only option - and that significantly increases the data loss