Does any of you out there any experience with this client?

I've just started lookin into it, and as a start it seems to work fine.

When the scheduler is to run a scheduled macro, the macro is run OK.
But the result of the operation is obviously not transferred to the
server, and the client retry the operation until the schedule has elapsed.

The server actlog report a ANR0484W for each retry, and the scedule fail.

All other scheduled actions seem to work (at least the incremental and
command..)

I have run a trace on the client, but whithout the source its not much
help...

 session.c (1230): Recv Verb: ...
 commtcp.c (1097): TcpRead: Upper level requested 4 bytes
 commtcp.c (1103): TcpRead: Issuing recv for 4 bytes.
 commtcp.c (1151): TcpRead: 4 bytes read of 4 requested.
 session.c (1263): sessRecvVerb(): length=0006, verb=13, magic=a5
 commtcp.c (1097): TcpRead: Upper level requested 2 bytes
 commtcp.c (1103): TcpRead: Issuing recv for 2 bytes.
 commtcp.c (1151): TcpRead: 2 bytes read of 2 requested.
 session.c (1347): Recv Verb:
 session.c (1348):   Length:     6 Code: 00000013 Type:    <-
EndTxn
 session.c (1599): sessClose: Issuing a 'SignOff' to the server.

> This is where the "SendSchedResult"-things shoud happen...


 session.c (1424): Send Verb: Length:     4 Code: 00000014 Type: SignOff
 commtcp.c (1222): TcpWrite: 4 bytes written of 4 requested.
 session.c (1443): Sent Verb: Length:        4 Code: 00000014 Type:
SignOff           ->
 commtcp.c (1342): TcpFlush: 4 bytes written on socket 5.
 session.c (1530): sessFlushVerb: Successful flush of send data to the
server
 session.c (3185): sessClose: Transitioning: sSignedOn state ===> sInit
state
 commtcp.c (1431): TcpClose(): Closing socket
 commtcp.c (1460): TcpClose(): Deallocating send buffer
 session.c (1638): sessClose: Session closed.


ANyone had similar problems with this or other clients?

Any hits/help/suggestions would be appreciatet.

                                         Tom