An explicit schema name can now be used with MERVA queue management for DB2 V8 to avoid conflicting sequence objects and queue sequence numbers (QSNs) when different user IDs are used for direct DB2 applications.
Resolving the problem
PTF UK42620 introduces an explicit schema name for MERVA queue management for DB2 V8. This is useful to ensure MERVA uses consistent sequence objects when different user IDs are used for MERVA direct DB2 applications. DB2 uses the user ID as the default qualifier for unqualified object references, and this can result in MERVA generating conflicting QSNs.
Even if consistent user IDs are used for direct DB2 applications using an explicit schema name is a good idea to ensure that conflicting sequence objects cannot be created when a different user ID is used inadvertently.
Two new sample REXX utilities are also provided to simplify manual definition of DB2 sequence objects, if required:
Generate the necessary SQL CREATE SEQUENCE statements to create DB2 sequence objects and grant the necessary DB2 permissions.
Drop the DB2 sequence objects for a specific schema name.
Apply PTF UK42620 for HIPER APAR PK77617 to obtain the enhancement and a detailed description from the APAR.