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



A couple of bad ideas here IMHO...

1) using DFTACTGRP, you're not really using an ILE activation group.
You're using a special OPM compatible group. Mixing and matching with ILE
groups can be problematic.

2) Creating activation groups is a relatively expensive process, repeatedly
creating/deleting is not recommended.

If it were me, I'd simply run all programs in a named group, MYAPP or
MYCOMPANY.

Not sure where you got the idea to use *NEW to "force updates to be
"posted", assuming that with a *NEW activation group, when sqlrpgle_1
returns with LR=*ON, file updates "take effect" similar to FEOD".

The idea above is not correct. FEOD is used to force RPG RLA to flush it's
buffers to the DB. Since you're using SQL, the updates are already in the
DB. The only possible "unposted" updates with SQL would be "uncommited"
updates. But all you'd need to do is commit them. In fact, if they aren't
commited and you end the activation group, by default the would be rolled
back (thrown away)!

Charles




On Mon, Feb 3, 2014 at 3:50 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

I am curious as to why not dataques?


On 2/3/2014 2:45 PM, Gary Thompson wrote:
I have program clle_1 currently in pilot, and am reviewing activation
group design to get correct function with good efficiency.

One concern is file updates made by program sqlrpgle_1 must
be read by programs sqlrpgle_2 and sqlrpgle_3.



clle_1 runs as a (almost) never-ending program, meaning it
runs in a loop for about 24 hours, ends and re-starts minutes later.

The clle_1 loop has two phases, separated by DLYJOB(75) :


1) Call sqlrpgle_1 to collect pallet item and quantity picked from
a 3rd-party app running on our network and update custom files
on our system i. Data from the 3rd-party app is received from
IFS directory 3p_1.


Call sqlrpgle_1 to collect pallet load status from the 3rd-party
app and update custom files on the i to show pallets confirmed
for shipment. Pallet confirmation is received from the same
3rd-party app, but the data is received from IFS directory 3p_2.



DLYJOB(75)


2) Call sqlrpgle_2 to check for customer deliveries where all
pallets
are confirmed for shipment (no updates) and call sqlrpgle_3 to
load local files with delivery data, print pallet labels and transfer
an Advance Ship Notice to the customer.

DLYJOB(75)


My new activation group design:

Leave clle_1 set to *DFTACTGRP

Change sqlrpgle_1 from activation group QILE to *NEW
(to force updates to be "posted", assuming that with a
*NEW
activation group, when sqlrpgle_1 returns with
LR=*ON, file
updates "take effect" similar to FEOD ?)

Change sqlrpgle_2 from activation group *NEW to *CALLER,
Different than the *NEW activation group created by
sqlrpgle_1,
for same reasons mentioned for sqlrpgle_1.

That is a combined total of some 1,400 activation group create/delete
steps per day.

All suggestions/comments gratefully welcomed . . .



--
Booth Martin
www.martinvt.com
(802)461-5349
Skype: booth.martin

In the pitiful, multipage, connection-boxed form to which the flowchart
has today been elaborated, it has proved to be useless as a design tool
-- programmers draw flowcharts after, not before, writing the programs
they describe. -- Fred Brooks, Jr.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.