>If you can get the second copy into memory That's incomplete. You must add "and represented by a CDE". And that's basically where the thread started.
>Will my IDENTIFY trick (to assign an alias) allow the DELETE to >select the copy that the IDENTIFY points to? If it is represented by a CDE (as it would be if non-reentrant), then "yes". But in practice this is almost never an issue. If the program that did the LOAD does the DELETE, the odds are that things wil be in the right sequence (no guarantee of course). It might be of help if the OP explained their use case for loading two modules of the same name from different libraries. It's not frequent that, for example, you need two release's of a product's module "in play" at the same time. Peter Relson [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
