×
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.
David,
You haven't done something really bad. Possibly unwise, though...
If you (or rather, they) are worried about the very existence of the
*MODULE 'problem', then the answer is no. The AS/400 allows you to have
multiple objects of different types with the same name (program, data area,
file, module) with no problems (but you know that). Some people (myself
included) think this is a bad idea anyway, but that's a separate issue.
If you mean 'could this lead to problems later', then the answer is maybe:
1. Maybe someone will attempt to use the wrong source member to recreate the
wrong object
2. Maybe someone will delete one of the source members, thinking that it's
no longer used
3. (Very likely!) Maybe someone will get frustrated spending ages trying to
figure out why debugging a program doesn't seem to work (and then they'll go
with option 2 above because they're frustrated).
Before you start writing code that uses this new module, do yourself a favor
and rename it.
Rory
On Mon, May 18, 2009 at 7:45 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx>wrote:
Hi all,
I inadvertently created a module type NOMAIN without realising that the
same name was already used for an old RPGIII program. Normally I wouldn't
have, but now it's done. One or two developer's are worried about it but I
can't see the problem. Have I done something really bad?
midrange.com
