Did anyone experience a deadlock between a rebind of package X and the same executing package X on DB2 v9 z/OS ?

Package X is executed many times (!) all day long, so whenever changing stats / index and trying to rebind , we have this problem and application is not so good in error handling

1) executing package X is having an X lock on SPT01 on datapage Y
2) the rebind of the same package X is taking an S lock on SYSPACKAGE on datapage Z
Than
3) the executing package X is trying to take an lock on SYSPACKAGE on datapage Z
4) the rebind of the same package X is trying to take update on SPT01

IBM detects deadlock and throws out the package execution .
Application gets a DB2 SQL Error: SQLCODE=-904, SQLSTATE=57011, SQLERRMC=00C90088;00000302;DSNDB01 .SP
T01 .X'00111'

I would think that DB2 would take a lock in the same sequence for executing package and doing the rebind so, both going first to SPT01 and than catalog table SYSPACKAGE or do I see this wrong ?