Re: Incorrect module name and library

[jpcarr@xxxxxxxxxxxx]

Mark
No, it's not erroneous.   Lets say you have a PF named BOB and format name
is JOHN ,  If I rename the PF to JOE, the format name is stil JOHN.   It's
that type of relationship.   Remember,  a Module can have Multiple
Procedures named  PRC1, PRC2 and PRC3.   If I rename the Module object the
procedures inside are Still called PRC1, PRC2, and PRC3.


See what I mean?    It's just that for a "Normal"  single source member,
single Procedure type thing,  the procedure name is automatically the
Module name at creation time.   For the Single Source Member, Single
Module, Single Program type of thing(like PDM option 14 CRTBNDRPG)  you
don't have the ability to specify the procedure name.   But it's there.
It will automatically be the Module Name.

See what I mean?

John Carr



John,

At 3/2/01 11:28 AM -0500, you wrote:
>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).

  That would be consistent "erroneous" behavior.



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

  No need - just have the value loaded at runtime!!


+---
| 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
+---