× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Rob

Thanks,

I think I'll wait with the DCR ... (-:

How about "With default User" ?
It does not work in my tests.

Gad

----------------------------------------------------------------------

message: 1
date: Fri, 21 Jun 2013 07:58:38 -0400
from: rob@xxxxxxxxx
subject: Re: Row change Timestamp

There is not a row change user capability at this time. Upon initial
thought one would think this would be easy and you should submit a DCR
and/or a COMMON requirement to get IBM on this. You still may want to.
But consider this; what about all those jobs that run under one profile
but service another? For example do this:
WRKOBJLCK youruserprofile *USRPRF
On mine I see:
Job User
QYPSJSVR QYPSJSVR
QZLSFILET QUSER
QZRCSRVS QUSER
ROBS3 ROB
...
Should a row updated by the QZRCSRVS job be listed as QUSER or ROB?
Job 077713/QUSER/QZRCSRVS started on 06/21/13 at 07:08:40
...
User ROB from client 10.10.9.21 connected to server
...

Let's take it further. You have a job in the QHTTPSVR subsystem running
under user QTMHHTTP. It is providing web access. Your supplier signs in
with email address, let's say iamyourservant@xxxxxxxxxxxxxxxxxxxxxx. He
performs a transaction. What user should row change user supply?

If you put on your DCR that your belief is that "if it isn't green, it
isn't a screen" and you don't care about those gui dweebs so IBM should
just put the job user on there it probably won't go too far down the DCR
process.


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: Gad Miron <gadmiron@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx,
Date: 06/21/2013 06:09 AM
Subject: Re: Row change Timestamp
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Hello Rob

Right you are,
I tested your demo RPG PGM and (after update) the Timestamp was updated
correctly
(i.e to the time the prgram was run and not the value in the program's
buffer).
However,
"With default User" did not work for me,
when inserting a record the change user field was not automatically
updated
to the default USER
is there a "row change USER" functionality?

Thank
Gad

message: 2
date: Thu, 20 Jun 2013 08:44:15 -0400
from: rob@xxxxxxxxx
subject: Re: Row Change Timestamp

Let me repeat. I was initially wrong. The row change timestamp is NOT
destroyed by RPG's handling of the I/O. It works as designed. You could
READ a row, set the row change timestamp to some value in the past, and
UPDATE the row. It won't care what you set it to. It will be updated
with the current timestamp. This is as it should be. This is available
with 6.1. This is the difference between "row change timestamp" and "with
default current timestamp". The latter will be affected by RPG.


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
--
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.






As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.