Re: timestamp not correct

On 5/22/2013 11:59 AM, dale janus wrote:

In your DDL did you tell it a DEFAULT of current timestamp or some such
thing?
In your RPG did you use an index or view which omitted that column?
You have to do both if you're sticking with RLA.

So what I am understanding is that I can use these great DDL tools, but
if I don't use SQL, they don't work.

Well, not really. This behaviour is exactly how DDS time stamps work
too. And any other field for that matter. Here is a quick example I
just tried.

DDS:
A R DDSR
A NBR 9P 0
A TXT 50A
A TS Z

A R DDSLR PFILE(DDS)
A NBR 9P 0
A TXT 50A

RPG:
fdds uf a e disk
fddsl uf a e disk
c eval nbr = 1
c eval txt = 'some text'
c except writedds
c eval nbr = 2
c eval txt = 'other text'
c write ddsr
c eval nbr = 3
c eval txt = 'more text'
c except writeddsl
c eval nbr = 4
c eval txt = 'the end'
c write ddslr
c eval *inlr = *on
oddsr eadd writedds
o nbr
o txt
oddslr eadd writeddsl
o nbr
o txt

call ddsrpg

select * from dds;
1 some text 0001-01-01-00.00.00.000000
2 other text 0001-01-01-00.00.00.000000
3 more text 2013-05-22-17.02.04.826949
4 the end 2013-05-22-17.02.04.826957


As you can see, ordinary RPG and DDS work the same as if you'd created
the file with DDL. SQL is a different beast from RPG + DDS, but it's
not at fault for this particular behaviour.

I suppose the correct answer is don't use record level access, use SQL.
I don't have enough time to learn everything, I must get this stuff
written by deadline. So I picked DDL and RDI as stuff to learn.

I can't speak for anyone else but I have basically learnt things by
hearing about them here and trying them at work.
--buck