Db2 for z/OS

Showing 984

Column name isn't allowed after LIKE

SQL that does select * from xxx where 'value' like col1fails.

over 11 years ago in Db2 for z/OS 1 Not under consideration

Avoid Db2 failure even if it got BSDS access initialization failure (BSDS timestamp mismatch)

[Background]- Customer's GRSRNL specifies SYSVSAM in systems exclusion list because they need to share CATALOGs. [Description]Our customer got BSDS Access initialization failure and starting Db2 was failed. Please refer to PMR#55237,615,760.They c...

almost 7 years ago in Db2 for z/OS 0 Functionality already exists

2 VOTE

Zero Downtime during Online CRM Application Migration

Problem Statement : Transaction 1 (T1) is intended to delete and subsequently insert few records to a table TB1. The business logic is like, this T1 should be open and not to commit as well until the end of delete followed by insert operation. ...

over 4 years ago in Db2 for z/OS 1 Not under consideration

1 VOTE

For Dynamic Plan Stability, Only store the actual SQL statement in STMTTEXT column

While reviewing the SQL statements in SYSDYNQRY.STMTTEXT column, extra characters are added to the end of the SQL. This requires extra processing when comparing to the REAL SQL-text. In some cases, but not all, a compare like the following is need...

over 2 years ago in Db2 for z/OS 1 Not under consideration

2 VOTE

A new command "REBIND QUERY" should be made available.

When packages become invalid due to maintenance activities, they may be rebound when needed. But, when a hint is established by running a "BIND QUERY" command, that bound query may become invalid by these same events. Restoration of that bound que...

over 4 years ago in Db2 for z/OS 1 Not under consideration

2 VOTE

Add new parameter for REORG to designate different access behavior when REORG is in LOG/SWITCH phase

Let's say we have zparm IRLMRWT=15, and we have large tablespace REORG with SHRLEVEL(CHANGE) or (REFERENCE), the elapse time of LOG/SWITCH phase is greater than 15 seconds, this causes a lot of online workload timeout with -911. At that time the t...

over 4 years ago in Db2 for z/OS 1 Not under consideration

3 VOTE

Long Time to restart DB2 caused by Rollback in SYSIBM.SYSSEQUENCE

As in PMR 94522,250,631:"Yes, it'd good to ask customer to submit a RFE so that this issue can be evaluated by the DB2 development architects. The current DB2 behavior was designed and implemented before SYSIBM.SYSSEQUENCE exists. Thank you very m...

almost 7 years ago in Db2 for z/OS 3 Not under consideration

2 VOTE

DSNRLMTxx resource limit tables need column for WLM Reporting Group

The DSNRLMTxx resource limit tables aremissing column for WLM Reporting Group. This would allow for resource consumption to be managed at the WLM Reporting Group level (rather than at the userid level, for instance. As WLM is the best method of ma...

almost 5 years ago in Db2 for z/OS 1 Not under consideration

3 VOTE

modify dsntep2 to produce result set despite exceessive warnings

DB2 and IDAA do not produce the same results for the example in question. That has been explained and will be documented but we would like to see DSNTEP2 at least run and produce output instead of only returning SQL error codes (-171 in our exampl...

about 7 years ago in Db2 for z/OS 1 Not under consideration

3 VOTE

DB2 object lock - return code on the ESS Normal Call Exit interface

In the case where an object lock is not available for an External SubSystem ( ESS ) origin thread, DB2 should not return the 'temporary error" return code on the ESS Normal Call Exit interface.It would be acceptable to make this optional. Justific...

about 7 years ago in Db2 for z/OS 1 Not under consideration

Please enter your email address

FILTER BY CATEGORY