RE: RPG Performance question -- RPG400-L

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

-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Mark S. Waterbury

In part, this will depend on how your "legacy" applications
and their menus were designed. If all originally OPM
(*DFTACTGRP), then it is likely that you may have had the
menus coded to issue RCLRSC upon return from lower levels.
This would in effect close all files opened at that call
level and below. You might want to reconsider that logic.

You are right Mark, but why exactly would we reconsider?

If a file is already open, then the path-length is somewhat
shorter for subsequent programs or modules opening the same
files, but there is still some overhead. At the machine
level, an OPEN costs around one-million instructions (more or
less). So, if your application is opening many, many files,
then closing them, and opening them again, this overhead will add up.

I will look into that, though if the time lapse is on closing the files, ie exiting, then it's not the opens that are causing the problem.
Also, I'd love to be able to quote you : where do you get that one-million instructions figure from?

Thanks.

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.