Db2 for z/OS

Showing 986 of 15639

Add commit frequency to Modify Recovery utility

If there a numerous rows in SYSCOPY to be modified out the modify job holds locks on SYSCOPY for an extended period of time and can cause timeouts for other processes and utilities that are using SYSCOPY

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

20 VOTE

IFCID amendment to include SQL Text

Currently the ifcid 366 and 376 do not always supply the SQL text, but rely on the explain statement cache to supply it. This means SMF extracts rarely supply the SQL text required for these records.

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

6 VOTE

Record usage of application plan

In our production environment we have about 15000 application plans. Most of them are probably still used but a lot of them have not been used for several years. We want to get rid of the old ones not to have to rebind them at every new release of...

almost 2 years ago in Db2 for z/OS 0 Future consideration

2 VOTE

One-Fecht Index Scan for SELECT min(), max()

At the moment only a single SELECT min(a) or a SELECT max(a) uses a suitable index I(a, ...). When selecting both, min() and max(), a tablespace scan is used to determine the minimum and maximum value. With large tables this behaviour is very expe...

8 months ago in Db2 for z/OS 1 Not under consideration

27 VOTE

Pseudo IFCID 316

When using REOPT(ALWAYS) on a batch package to deliberately avoid filling the Dynamic Statement Cache (DSC) the SQL is, correctly, not inserted into the DSC and is not exrternalized by an IFCID 316. However this then "hides" the workload from moni...

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

16 VOTE

DSNTIAUL should support input LRECL size of > 80 bytes and not ignore input beyond the first 72 bytes

It is sometimes easy to put SQL all on one record as long as the LRECL of that record is very large. It becomes difficult to parse that SQL so it is divided into 72 byte records. Currently, the IBM utilities have input files that can have a LRECL ...

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

17 VOTE

Invalid maximum timestamp value availble in DB2

Currently there is documented maximum timestamp value available in DB2 as '9999-12-31-24.00.00.000000'. However, using this value can lead to various problems which are recognized by DB2 development already as during introduction of temporal table...

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

11 VOTE

DB2 Z/OS Sync Logical and Physical Parts after full Reorg

ADD PART was used to insert a new physical partition in the middle of a tablespace. Now the Logical and Physical partitions are mismatch. If a Full Reorg on the full tablespace is performed, the utility can include an option to resync the logical ...

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

9 VOTE

DSN1COPY support for XML data in all cases

DSN1COPY does not currently supports XML table restore on another DB2 subsystem or in the case of a dropped XML tablespace. This lack can be easily bypassed by an UNLOAD / RELOAD in the case of a copy to another DB2 subsystem. But in the event of ...

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

9 VOTE

select ... from final table ( update table for portion of business time from ... )

the problem is that an update table for portition of business time can effect more than 1 row and if this is made in a bitemporal environment the System Start is set to the first change timestamp. But you didn't know the exact time you have to rea...

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

Please enter your email address

FILTER BY CATEGORY