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



Hi, Jon:

I am well aware of this architectural limitation. You can easily get around this by not deleting the *MODULEs themselves, after binding them into *PGMs or *SRVPGMs, and then use DSPPGMREF against the *MODULEs (only,) to extract accurate and up-to-date "where used" information.

All the best,

Mark S. Waterbury

> On 6/27/2012 6:09 PM, Jon Paris wrote:
Don't forget that (unless it changed in V7) a UPDPGM will not cause the embedded "what used" information to be updated. So if the in-house tool depends on that data to determine what needs to be recompiled then UPDPGM is not a good idea.

On 2012-06-27, at 5:43 PM, midrange-l-request@xxxxxxxxxxxx wrote:

I think it should be easy to at least change the tool to do UPDPGM if
the pgm exists already instead of crtpgm. I'll try and test that. Are
you sure that would work in all circumstances?
I know of no scenarios where this would not work.
As for changing to srvpgm, that's what I was worried about : all those
files that stay open, global and static variables,... It looks like
we'd have to go through every job to make sure that the difference in
behaviour of the new programs does not have any effect. Should we
start by eliminating the use of the dftactgrp while still using
binding by copy?
Sounds reasonable to me.
Jon Paris

www.partner400.com
www.SystemiDeveloper.com







As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.