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


  • Subject: Re: Incorrect module name and library
  • From: jpcarr@xxxxxxxxxxxx
  • Date: Fri, 2 Mar 2001 11:28:46 -0500


<snip>
 Within the program I have an SDS that specifies a *PROC variable.  The
value printed is MOD_TEST, not MOD, which is the current name.  This tells
me that this value is populated at compile time, not runtime.  Is this the
way OPM programs worked?  I seem to recall that it was at runtime.  This
behavior was a surprise to me.  I would think that most people would want
the current name of the module, not the original name.
<snip>

The module object may indeed be renamed from MOD_TEST to MOD but within
that module,  The procedure name is what the Module name was when you did a
CRTRPGMOD.  So,  Look at your active job and take an 11.   You will see the
name of the procedure as MOD_TEST(just like the SDS said).

So, how would you like to have a Rename Procedure function?

John Carr

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.