|
Charles, then my understanding of something is incorrect (wouldn't be--
the first time).
Here is a date field in one file in DSPFFD
Data Field Buffer Buffer Field
Field Type Length Length Position Usage
SBDATE DATE 10 10 1 Both
Field text . . . . . . . . . . . . . . . : Sales Date
Date Format . . . . . . . . . . . . . . . : *ISO
Default value . . . . . . . . . . . . . . :
'0001-01-01'
Coded Character Set Identifier . . . . . : 37
And if I look at the file in WRKMBRPDM
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7
2018-02-260030607911615300007341002632 0000004000034507122870001-01-01
2018-02-260040607911615300007341002632 0000005000034507122880001-01-01
2018-02-260100607911615300007341002632 0000003000034507122890001-01-01
2018-02-260110607911615300007341002632 0000002000034507122900001-01-01
If I do the same for the file in question...
Data Field Buffer Buffer Field
Field Type Length Length Position Usage
FRDAT DATE 10 10 11 Both
Field text . . . . . . . . . . . . . . . : From Date
Date Format . . . . . . . . . . . . . . . : *USA
Coded Character Set Identifier . . . . . : 37
And if I look at the file in WRKMBRPDM
*...+....1....+....2....+....3
á█|█ä█¤71011/01/201812/31/2022
á█|█ä█¤71411/01/201812/31/2022
á█|█ä█¤71511/01/201812/31/2022
Am I misunderstanding something?
Thank,
Rob
On 2/22/2019 2:26 PM, Charles Wilt wrote:
If it's an actual date field...the format doesn't matter...from
There's only 1 internal representation of a date data type in the DB.
Charles
On Fri, Feb 22, 2019 at 12:22 PM Robert Rogerson
<rogersonra@xxxxxxxxx>
wrote:
Steve, the problem with the sql approach is that the journaled file
has date field with DATFMT(*MDY).
So when I create the "table" the date field is created as *ISO
(from what I can find sql can not do DATFMT) so the cpyf fails as
the date field (in *MDY format) is not a valid *ISO date.
If I can't find a way to remove the keys so I can use CRTDUPOBJ
then my next option is exactly like you said and a before insert
trigger on the date field to format it correctly.
Thanks,
Rob
On 2/22/2019 2:10 PM, Steve Richter wrote:
Rob,with
I would try to use "create table xxx as ( select * from
duppedTable )
data
that should create an SQL created table. Then you can alter table and
remove the primary key?
-Steve
On Fri, Feb 22, 2019 at 2:02 PM Robert Rogerson
<rogersonra@xxxxxxxxx>
wrote:
Hi all,
I'm trying to create a journal extract file which will format
JOESD
affiliatelistDSPJRN.
I have it more or less working. I use CRTDUPOBJ of the journaled
file and then ALTER TABLE to add the journal fields.
As I said I have this working. The problem I just found was that
the CRTDUPOBJ still creates a keyed physical file.
Before I change the process to an all SQL solution I'm wondering
if anyone knows a way to remove the keys from the keyed physical file.
I haven't found a way but I thought someone else may of a way. If
not I'll use and sql approach...
Thanks,
Rob
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our
list--link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
--To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.