RE: Calling Program information

We also use journals here to drive data feeds to other systems. What we do is process them once a day to pull out transactions we care about. It's been awhile since I looked at the process but I think what happens is a new receiver is created every day and we do the processing from the old one.

Matt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Peter Connell
Sent: Thursday, March 05, 2009 1:19 PM
To: RPG programming on the IBM i / System i
Subject: RE: Calling Program information

We journal everthing to be sent to a DR box.
Even with everything journalled the performance is very good with today's processors.
For 1 file. You won't even notice it.
You can restrict the size of that the journal will reach before the system detaches it and starts another and have some job remove detached journals.

Peter


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Friday, 6 March 2009 6:54 a.m.
To: RPG programming on the IBM i / System i
Subject: Re: Calling Program information

I doubt the journal would get that large...

Think about it, assuming your Order file's record size + the journal entry data totals 500 bytes.

At one update a second, a day's worth of journal entries takes only
(500*60*60*24) = 43,200,000 bytes or 43.2 Megs.

If you got 1GB of spare disk space, you've got room for more than 20 days of journals.

Actually, IBM has a calculator you use to determine space requirements:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzaki/rzakisizecalc.htm


Performance might be more of an issue, since journaling without the use of commitment control has a negative impact on performance. But since you're only talking about a single file, I'd be willing to bet you won't notice it.

Heck if it were me, I'd look at journalling all my important files.

I've worked for small shops, medium shops, and large shops; journalling was used by all of them.

HTH,
Charles


On Thu, Mar 5, 2009 at 10:25 AM, Kesterson, Randy <RPKesterson@xxxxxxxxxxxxxxxxxxx> wrote:

I thought about journaling but the file is our Order file and it's constantly being updated.  The journal will get quite large quickly.  I only want data in the file when I know I have found a problem.  And, I may still go with journaling.  Especially since it looks like the information I'm looking for isn't available without it.

Thanks for your input.
______________________________________________________________________
________________________
Randy Kesterson, Information Services
Market Transport Services  - a UTi Worldwide Company| 110 N Marine
Drive | Portland, OR 97217 | USA rpkesterson@xxxxxxxxxxxxxxxxxxx | D
+1 503.978.4353 | O +1 503.283.2405 x353 | F +1 503.978.4392


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob P. Roche
Sent: Thursday, March 05, 2009 6:59 AM
To: RPG programming on the IBM i / System i
Subject: Re: Calling Program information

Why not just journal the file? It gives you program name, user, time,
all sorts of useful info for this type of problem.



From:
"Kesterson, Randy" <RPKesterson@xxxxxxxxxxxxxxxxxxx>
To:
<rpg400-l@xxxxxxxxxxxx>
Date:
03/05/2009 08:53 AM
Subject:
Calling Program information
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx



Does anyone know if any of the "Information" data structures has the
name of the program, if any, that called the program you're in?



I'm going to put a trigger on one of the files in our system to save a
record in a separate file anytime a record is deleted or a specific
field within a record is blanked out.  I'm tracking down the cause of
two separate issues here and it would be nice to be able to add a
field to the saved record that says what program called, or caused,
this trigger to run.



Thanks,



______________________________________________________________________
__
______________________
Randy Kesterson, Information Services

Market Transport Services  - a UTi Worldwide Company| 110 N Marine
Drive
| Portland, OR 97217 | USA
rpkesterson@xxxxxxxxxxxxxxxxxxx
<mailto:rpkesterson@xxxxxxxxxxxxxxxxxxx>
| D +1 503.978.4353 | O +1 503.283.2405 x353 | F +1 503.978.4392



--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/rpg400-l.




--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.

#####################################################################################
This correspondence is for the named person's use only. It may contain confidential or legally privileged information, or both. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this correspondence in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of Veda Advantage. If you need assistance, please contact Veda Advantage on either :- Australia 133124 or New Zealand +64 9 367 6200