Execution of static Programs which contains ALTER SEQUENCE statements in which the sequence name is not fully qualified.

Customer is receiving SQLCODE -204 during execution of static Programs which contains ALTER SEQUENCE statements (in which the Sequence name is not fully qualified).
.
That SQLCODE -204 is caused due to on runtime DB2 uses the value specified as OWNER on bind time (that is the owner of the generated Package) instead on the value specified on QUALIFIER parameter at Bind time.
.
This is a known issue which is reported on Apar PM26426 in which it is written the following:
.
**************************************************************
COMMENTS:
DB2 may incorrectly qualify a static DDL statement when the object name is not explicitly qualified. When the BIND subcommand is specified with the QUALIFIER option, the default schema should be the identifier specified in the QUALIFIER option. Instead, DB2 is using the authorization ID of the owner of the package as the default schema.
.
Incorrect qualification of an object may result in various errors including but not limited to SQLCODE -204, SQLCODE -601, execution of the specified operation on the incorrect object, or the definition of an object with incorrect schema.
.
Users may circumvent the problem by explicitly qualifying the object names specified in the static DDL statements.
**************************************************************
.
That Apar PM26426 was closed as FIN (Fix In Next Db2 for Z/OS release) so it is not planned to be implemented for DB2 v10. The customer is requesting to retrofit this PTF for DB2v10 as they have just migrated to this version and the circumvention proposed is not easy to implement.