|
Charles, There is a PTF for V5R4.
SI39816 superseded by Si41745.
http://www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d145c/98fb8b73bef067e986257752004cea1d?OpenDocument&Highlight=2,SI39816
Charles Wilt said the following on 11/29/2010 8:51 AM:
Very sweet!--
Thanks Birgitta!
Wish they would have posted it back to v5r4 though :(
Charles
On Fri, Nov 26, 2010 at 9:39 AM, Birgitta Hauser<Hauser@xxxxxxxxxxxxxxx> wrote:
but its not to easy to get it.
BTW there is a brand new UDTF Display_Journal which can be ordered via PTF
that makes it easy to directly access journal data with SQL:
http://www-01.ibm.com/support/docview.wss?rs=0&dc=DB530&dc=DA600&q1=dtaq&uid
=nas3725498ce67111ece86257752004cea2a&loc=en_US&cs=UTF-8&lang=all
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von
dieter.bender@xxxxxxxxxxxx
Gesendet: Friday, 26. November 2010 10:43
An: Midrange Systems Technical Discussion
Betreff: Re: File transaction date
Hi,
the Journal Receiver will contain this information, but its not to easy to
get it. starting journaling does not touch your applications and would be a
good idea anyway.
what about adding the timestamp (or something like this), filling it by
trigger and letting your application work with LFs ommiting this field with
identical name s to now?
Dieter
--------------------------------------------------
From: "David FOXWELL"<David.FOXWELL@xxxxxxxxx>
Sent: Friday, November 26, 2010 9:44 AM
To: "Midrange Systems Technical Discussion"<midrange-l@xxxxxxxxxxxx>
Subject: File transaction date
Hi,--
I'm currently adding a date field to an old PF which will hold the date
that a transaction gets modified. The file has 3 or 4 mentions in
different RPG modules that get bound by copy to almost everything. This
results in having to recompile pratically the whole system. The job that
migrates the file takes about 2.5 hours to run and I need to plan it in
advance so noone is using the file when ir runs. In other words, it's a
headache.
I don't know much about journals/receivers as they aren't used here. But
aren't they designed for this kind of information? I'm also thinking of
the rollback feature that they permit. I've never used that either. What
kind of preparations do we need to think about to be able to switch to
this kind of file management?
--
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.
--
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.
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.