Re: include current date in logical file

I don't see this create view
Commitment control . . . . . . . *NONE
Naming convention . . . . . . . *SYS
Statement processing . . . . . . *RUN
Library option . . . . . . . . . *LIBL
List type . . . . . . . . . . . *ALL
Data refresh . . . . . . . . . . *ALWAYS
Allow copy data . . . . . . . . *YES
Date format . . . . . . . . . . *JOB
Date separator character . . . . *JOB
Time format . . . . . . . . . . *HMS
Time separator character . . . . *JOB
Decimal point . . . . . . . . . *JOB
Sort sequence . . . . . . . . . *JOB
Library . . . . . . . . . . .
Language identifier . . . . . . *JOB



On Thu, May 23, 2013 at 4:27 PM, <rob@xxxxxxxxx> wrote:

Ah, but does one REALLY need to create the view or index which omits this
field in order for it to be updated automatically even by RPG RLA? Keeping
in mind that the original thought was that if you do not then RLA will
slap an initial value in there. One workaround was to use the initialize
with external default. But what about:
IMPLICITLY HIDDEN
Indicates the column is not visible in SQL statements unless it is
referred to explicitly by name. For example, SELECT * does not include any
hidden columns in the result. A table must contain at least one column
that is not IMPLICITLY HIDDEN.

I suppose the rub here is "... in sql statements...". RLA is not SQL. So
I can't
CREATE TABLE ...
(...,
LastUpdated timestamp generated always for each row on update as row
change timestamp implicitly hidden,
...)
and expect it won't be initialized to 0001-01-01... by RLA, because RLA
does not respect "implicitly hidden", true?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 05/23/2013 04:01 PM
Subject: Re: include current date in logical file
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Seems like a silly request...

It's done so often that IBM has made it even easier to do at 6.1 with the
ROW CHANGE TIMESTAMP

http://pic.dhe.ibm.com/infocenter/iseries/v6r1m0/topic/sqlp/rbafysqlprcts.htm


Charles

On Thu, May 23, 2013 at 3:23 PM, aec <cfuture@xxxxxxxxxxx> wrote:

A word of caution, I recently discovered if you have a DDS-defined or
SQL-defined DATE or TIMESTAMP or TIME field in a file, and insert a
record using a field list but do not include that field name in the list
for the values, the write will automatically use the current timestamp.

But please please don't do that either. For inserts, use all the values.
(I like it when the column names list is used in the INSERT statement.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.