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



I would also avoid *CALLER. Because multiple job can initiate the trigger so may have several activation group. Probably not a big deal though.

If you are willing to change the code of the trigger program, here is a suggestion:
- Add a table to the program that hold the jod id (number, name ...) and it's type (batch/interactive)
- When the trigger is called, check to see if the job is already in the table
- if so, retrieve the type of job from the table
- if not, call the API to retrieve the type of the job and add this information to the table

This way you will call the API just once per job instead of once per read. My guess is that is where you will get the best performance boost.



Denis Robitaille
Chef de service TI - Solution d'entreprise
Infrastructure et opérations

CASCADES CENTRE DES TECHNOLOGIES
412 Marie Victorin
Kingsey falls(Québec) Canada J0A 1B0
Tél : 819 363 6100 Poste :52130
Cell : 819 352 9362


-----Message d'origine-----
De : MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Rich Loeber
Envoyé : 9 avril 2018 12:10
À : Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Objet : Re: File Trigger Performance

Denis,

Thanks .... would the activation group setting of *CALLER work as well?
When I display the *PGM now it reads QILE for the activation group.

Rich

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

On 4/9/2018 11:59 AM, Denis Robitaille wrote:

Here is a suggestion: make sure that the activation group for the program is not *NEW. Use a named activation group and make that the program is not closed between call.


Denis Robitaille
Chef de service TI - Solution d'entreprise Infrastructure et operations

CASCADES CENTRE DES TECHNOLOGIES
412 Marie Victorin
Kingsey falls(Quebec) Canada J0A 1B0
Tel : 819 363 6100 Poste :52130
Cell : 819 352 9362


-----Message d'origine-----
De : MIDRANGE-L [[1]mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Rich Loeber Envoye : 9 avril 2018 11:50 A : Midrange Systems Technical Discussion [2]<midrange-l@xxxxxxxxxxxx> Objet : File Trigger Performance

I have a customer using one of our products that employs a physical file
trigger program for READ. The trigger program is an ILE program that
starts up in a CLLE. The first steps in the CLLE are to retrieve the run
status (batch or interactive) and then check a setting in a data area. If
the job is running in batch and the setting from the data area tells the
program to ignore batch reads, then a RETURN is immediately issued.

Seems easy enough, but the customer is reported very poor performance now
on batch applications.

Any ideas?

Rich Loeber - @richloeber
Kisco Information Systems
[1][3]http://www.kisco.com

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

References

Visible links
1. [4]http://www.kisco.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: [5]MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: [6]https://lists.midrange.com/mailman/listinfo/midrange-l
or email: [7]MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at [8]https://archive.midrange.com/midrange-l.

Please contact [9]support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: [10]http://amzn.to/2dEadiD

References

Visible links
1. mailto:midrange-l-bounces@xxxxxxxxxxxx
2. mailto:midrange-l@xxxxxxxxxxxx
3. http://www.kisco.com/
4. http://www.kisco.com/
5. mailto:MIDRANGE-L@xxxxxxxxxxxx
6. https://lists.midrange.com/mailman/listinfo/midrange-l
7. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
8. https://archive.midrange.com/midrange-l
9. mailto:support@xxxxxxxxxxxx
10. http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD

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.