Re: DDS to SQL - date definition

[CRPence <crp@xxxxxxxxxxxxxxxxxxxx>]

  Using QDBRTVFD I believe would show that the SQL TABLE [which only 
supports *ISO for create] that the variable Qddfdtts has the value X'EE' 
/The implied separator is used/ whereas the DDS created file uses X'00' 
/The separator associated with the job/ ;; besides DATE data type, it 
seems the same issue would exist for TIME data type.

  That would then appear to be a variant of the problem described in 
the APAR II14134 which arose from changes provided by APAR= SE24069 and 
APAR= SE24994 [which provided _easing_ of impacts/side-effects from the 
original correction for APAR= SE22099].  I am not aware that any similar 
APAR or correction exists [yet]; such that a problem report should be 
opened with the service provider to request correction in case it has 
not been already.

  Note that if so, a 'correction' would of course have /the same/ side 
effects as alluded in that informational APAR, which describes some of 
the impacts for that /same/ issue with TIMESTAMP fields.

Regards, Chuck
-- All comments provided "as is" with no warranties of any kind 
whatsoever and may not represent positions, strategies, nor views of my 
employer

rob@xxxxxxxxx wrote:
> I simplified it down to:
>
>      A          R DMEQPRC
>      A            EQDTI           L         DATFMT(*ISO) 
>
> Record Format Information 
>   Record format . . . . . . . . . . . . . . . :  DMEQPRC 
>   Format level identifier . . . . . . . . . . :  2B4A463FAFC20 
>   Number of fields  . . . . . . . . . . . . . :      1 
>   Record length . . . . . . . . . . . . . . . :     10 
> Field Level Information 
>              Data        Field  Buffer    Buffer        Field    Column 
>   Field      Type       Length  Length  Position        Usage    Heading
>   EQDTI      DATE           10      10         1        Both     EQDTI 
>     Date Format . . . . . . . . . . . . . . . :  *ISO 
>     Coded Character Set Identifier  . . . . . :     37 
>
>
> CREATE TABLE DMEQPMST 
> (EQDTI DATE NOT NULL DEFAULT '0001-01-01')
> RCDFMT DMEQPRC 
>
> Record Format Information 
>   Record format . . . . . . . . . . . . . . . :  DMEQPRC 
>   Format level identifier . . . . . . . . . . :  2B3B575FAFC20 
>   Number of fields  . . . . . . . . . . . . . :      1 
>   Record length . . . . . . . . . . . . . . . :     10 
> Field Level Information 
>              Data        Field  Buffer    Buffer        Field    Column 
>   Field      Type       Length  Length  Position        Usage    Heading
>   EQDTI      DATE           10      10         1        Both     EQDTI 
>     Date Format . . . . . . . . . . . . . . . :  *ISO 
>     Default value . . . . . . . . . . . . . . : 
>         '0001-01-01' 
>     Coded Character Set Identifier  . . . . . :     37 
>
> Tried dropping the "default" but still no match.  It DID make a difference 
> though.
>
> Record Format Information 
>   Record format . . . . . . . . . . . . . . . :  DMEQPRC 
>   Format level identifier . . . . . . . . . . :  2B3B5767AFC20 
>   Number of fields  . . . . . . . . . . . . . :      1 
>   Record length . . . . . . . . . . . . . . . :     10 
> Field Level Information 
>              Data        Field  Buffer    Buffer        Field    Column 
>   Field      Type       Length  Length  Position        Usage    Heading
>   EQDTI      DATE           10      10         1        Both     EQDTI 
>     Date Format . . . . . . . . . . . . . . . :  *ISO 
>     Default value . . . . . . . . . . . . . . :  None 
>     Coded Character Set Identifier  . . . . . :     37 
>
> Even changed it to allow null.  Made a difference, but still no match.
>
> Rob Berendt