Yes, they are compatible.  Here's the explanation for that error:

      ANR0444W Protocol error on session session number for node client node
name (client platform) - out-of-sequence verb (type verb name) received.

Explanation: The server detects a protocol error on the specified session
because a verb has been received that does not adhere to the client-server
exchange sequence.

System Action: The server ends the client session.

User Response: If the client generating the error is not an API client,
contact your service representative. If the client generating the error is
an API client, contact the owner of the API client. If the client generating
the error is a client that you have created using WDSF verbs, correct the
programming error in your client program.



There's also this APAR on the Tivoli KB but I don't know if it applies to
your versions:

APAR= PQ50995  SER=                            IN INCORROUT
ANR0444W / ANR0484W IN ACTLOG DURING ARCHIVAL OF MULTIPLE
OBJECTS

Status: CLOSED                              Closed: 07/27/01

Apar Information:

RCOMP= 5698TSOCL    TIV 390 UNIX SY RREL= R417
FCOMP= 5698TSOCL    TIV 390 UNIX SY PFREL= F417  TREL= T
SRLS:      NONE

Return Codes:

Applicable Component Level/SU:
R417 PSY         UP

Error Description:

extended testing in his environment. The important factors
seems to be:
   use arch command with multiple file objects in one command

.
Impact to customer:
Customer was asked to go to 4.1.2 level, to solve TSM perform.
problems during archive and expiration. Due to this new arch.
problem customer cannot migrate his 10 servers and 1000 clients
to this level. This is critical for him.

Local Fix:
Use single object per command


Problem Summary:
****************************************************************
* USERS AFFECTED: All clients.                                 *
****************************************************************
* PROBLEM DESCRIPTION: Archive of several objects within one  *
*                      archive command may hang or cause       *
*                      ANR0444E,ANR0484E messages in the server*
*                      actlog. The problem mostly occurs when  *
*                      RESOURCEUTILIZATION option is set to 1, *
*                      or when on UNIX platforms PASSWORDACCESS*

*                      is set to GENERATE and command is issued*
*                      by non-root user.                       *
****************************************************************
* RECOMMENDATION: Apply the fix when available.                *
****************************************************************

Temporary Fix:


Comments:
MODULES/MACROS:   EXE      DSMC
                  EXE      DSM

Problem Conclusion:
At one place, in the archive branch of the code, threads
synchronization was missing when accessing resurce, shared
between several threads. That caused protocol violation when
communicating with server. Source code has been modified to
handle the situation properly.