RE: Using prototypes...

There was a limit on the # of members you could save at one time with
SAVLIB. I have hit it at multiple shops. I may not remember the #
correctly, (ie 8000) but I do know it existed at one time.

That was one reason several shops started putting source into multiple
files and separating source from production objects.

This may no longer exist, but it did at one point.

For some shops, having multiple source files may simply be a carry-over
from this restriction.

Sharon Wintermute


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Friday, May 07, 2010 10:38 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Using prototypes...

Wintermute, Sharon wrote:

One of the reasons (way back when) was the 8000 member limit on
saving of files. I don't know if that still exists. I have seen
applications that exceed that. (Working on 2 of them now).

hr wrote:

I know this is not directly the subject, but I have always
wondered why people has different source files for different
source types <<SNIP>>

If "saving of files" means SAVOBJ or SAVLIB, neither has ever had
a hard-limit like 8000; I doubt also for SAV. The database supports
up to 32766 [and remains functional for most requests, even up to
the documented limit of 32767] members in a database file; the
database save feature [which implements SAVxxx] included.

There are dozens of reasons that one could justify self-imposed
limits on the number of members, mostly performance-related; or
perhaps to avoid exceeding some application-imposed limits.

Regards, Chuck