RE: DDS to SQL - date definition

Here's the latest on the format ID not being the same on DDL vs DDS with
date/time/timestamp fields. I have good news and bad news.

The good news: IBM has created test PTFs for V5R3 (SI27866) and V5R4
(SI27868). (As test PTFs, they're released yet.) I applied the V5R4 PTF
and it works. Format IDs are identical with no level checks.

The bad news: If I read the cover letter correctly, it gives me the
shivers. Below is the cover letter in it's entirety. Before I state my
opinion I'd like to see if anyone else thinks what I think. Supportline has
my concerns.


PTF/FIX #: SI27868 - i5/OS
LICENSED PROGRAM: 5722SS1
---------------------------------------------------------------------------
: SYSTEM : RELEASE : LEVEL : RECOMPILE : LIBRARY : MRI : APAR :
: : : MIN/MAX : : : FEATURE: FIXED :
: : : : : : : :
: iSeries : V5R4M0 : 00/00 : N : QSYS : NONE : SE29266 :
---------------------------------------------------------------------------
PRE/CO-REQUISITE PTF/FIX LIST
-----------------------------
REQ LICENSED PTF/FIX LEVEL
TYPE PROGRAM REL NUMBER MIN/MAX OPTION
---- -------- --- ------- ------- ------
PRE 5722SS1 540 SI27486 00/00 0000
DIST 5722SS1 540 SI24812 00/00 0000
DIST 5722SS1 540 SI23612 00/00 0000
NOTICE:
-------
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels. This PTF may be a
prerequisite
for future PTFs. By applying this PTF you authorize and agree to the
foregoing.
This PTF is subject to the terms of the license agreement which
accompanied, or was contained in, the Program for which you are
obtaining
the PTF. You are not authorized to install or use the PTF except as
part
of a Program for which you have a valid Proof of Entitlement.
SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS
EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR
IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.
The applicable license agreement may have been provided to you in
printed
form and/or may be viewed using the Work with Software Agreements
(WRKSFWAG
CL command.
DESCRIPTION OF PROBLEM FIXED FOR APAR SE29266 :
-----------------------------------------------
The Format Level Identifiers for Record Formats associated
with SQL Tables, SQL Indexes and Logical Files built over
the SQL Table(s), and that have one or more Date or Time
columns/fields can be incorrect. This can cause Data
Description Specification (DDS) created files versus SQL
created Tables and Indexes with identical Record Formats
to have different Format Level Identifiers.
CORRECTION FOR APAR SE29266 :
-----------------------------
The Database Create File program will be changed to generate
the correct Format Level Identifiers for Record Formats
for the Files with one or more Date or Time columns/fields
correctly when:
. The Files are actually created again with an SQL Create
Table or Create Logical File request when the logical file
does not just use the based on file format.
. New File(s) is/are created using Create Duplicate Object
using an effected File as the From Object. The Copy
Library support uses Create Duplicate Object to create
the Database File(s) in the New Library.
. An Alter Table request (or CHGPF with a SRCFILE keyword)
is done against an effected SQL Table.
The SQL Table as well as any SQL Indexes and
Logical Files that are built over the SQL Table will
have new Format Level Identifiers generated for them.
Correct Format Level Identifiers for Record Formats for the
Files with one or more Date, or Time columns/fields will Not be
corrected when:
. The Files are created again by doing a Restore request.
. the Files are created again by applying the Journal entries
to do
the create
. The Files are created again by Replaying the create using
Journal entries to actually do the create.
. Logical files are created that just use the physical file's
format
CIRCUMVENTION FOR APAR SE29266 :
--------------------------------
None.
ACTIVATION INSTRUCTIONS :
-------------------------
None.
SPECIAL INSTRUCTIONS :
----------------------
None.
DEFAULT INSTRUCTIONS :
----------------------
THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.
SUPERSEDES
PTF/FIX NO(S). APAR TITLE LINE
--------------
------------------------------------------------------------
SI27490 OSP-MSGMCH5601 To QDBCRTME When UTF16 Field And SortSeq
SI27489 OSP-DB-OTHER-INCORROUT INCORRECT LIBRARY ACCESSED FOR
SI25865 OSP-DB MSGMCH1210 QDBCRTFI with long name
SI25377 OSP-DB-MSGCPF4131 CRTDUPOBJ OVER LOGICAL FILES CAN CAUSE
FOR
SI25334 OSP-DB msgMCH1819 T/QDBCRTME CONCURRENT CRTDUPOBJ LF
SI25334 OSP-DB msgMCH1819 F/#dbxvder T/QDBCRTME on RSTOBJ LF JLF
SI25160 OSP-DB CRTDUPOBJ FROM SYSBAS TO AN IASP GENERATES A NEW
FORM
SI24880 OSP-DB IGC SETTINGS INCORRECTLY SET
SI24794 OSP-DB-JRN Use different journal on restore than used when
SI24225 OSP-DB Create File Does not wait for pending deletes
SI23611 OSP-DB-MSGCPD3223 F/QDBCRTFI CRTDUPOBJ RSTOBJ LF CONCAT
SI23611 OSP-DB QDBRPLAY MJA to update
SI23356 OSP-DB Preserve LVLID on CRTDUPOBJ
SI23108 OSP-DB Internal maintenance for QDBCRTFI
SI22348 OSP-DB FORMAT LEVEL IDENTIFIERS WITH TIMESTAMP FIELDS
SI22102 OSP-DB-MSGCPI32B0 QDBCRTFI ROWID Constraint
SI22102 OSP-DB msgCPF4131 rcdlen rcdfmt lvlid lvlchk neither fields
SI21762 OSP-DB-MSGCPF3205-F/QDBCRTFI-T/QDBCRTFI Multi-system file