Incorrect module name and library

Jon, Barbara, et al,

  I came across some ILE anomalies that I found interesting and could be a 
bug (or two).  This is under V4R5 and possibly under V4R4.

1)   I created a program (PGM) and bound module MOD into it. I then made a 
copy of the MOD source and called it MOD_TEST.  I made some changes (not to 
the interface), created module MOD_TEST, renamed module MOD_TEST to MOD, 
updated PGM via UPDPGM PGM MOD.

  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.


2)  Using a similar scenario as above, where the module was updated via 
UPDPGM, I ran
DSPPGM PGM DETAIL( *MODULE ) and put a 5 next to the module to display the 
details.  The library displayed is that of the ORIGINAL module, not the 
current module!  All other information seems to have gotten updated, 
including the source file / library and member.  This would definitely seem 
to be a bug to me.

  -mark

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