× 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.




On 15/02/2008, at 12:07 AM, ALopez@xxxxxxxxxx wrote:
You can prove this by creating dummy objects to consume lots of free
space. Something like:
CRTPF DUMMY/DUMMY00001 RCDLEN(32767) SIZE(2147483647) ALLOCATE (*YES)
repeated until sufficient space is consumed.


Thanks. I did want to try that, but was thinking of restoring a bunch of
items from tape to a junk library. When I try to run that I'm told that
RCDLEN has a maximum size of 32766 and SIZE a max of 2147483646. The
resulting file has a size in DSPOBJD of 16384. What am I missing?

Just me coding from memory instead of testing first. I just used the maximum values for *INT2 and *INT4. Change the sizes I specified to the limits imposed by the system. Once bitten:

CRTPF DUMMY/BIGFILE RCDLEN(32766) SIZE(2147483646) ALLOCATE(*YES)

gives:
CPC7301 - File BIGFILE created in library DUMMY.
MCH2804 - Tried to go larger than storage limit for object &1.
CPF3246 - Member BIGFILE not added to file BIGFILE in DUMMY.

NOTE the defect in message MCH2804.

A PF is capable of containing 4 294 967 294 records which is twice what SIZE allows but that's just due to signed vs. unsigned. However actual number of records allowed is a function of record length and maximum file object size.

Nett result of this appears to be the combined size of RCDLEN * SIZE + overhead exceeds the maximum size of a PF object.

The size of 16, 384 is simply the *FILE size. The member is the object that contains the records and therefore it is the member that allocates space. Because the error messages indicate the member was not added the object size is simply the *FILE size.

VRM540 Maximum Capacities show:
Number of bytes in a record 32 766 bytes
Number of records contained in a file member 4 294 967 294 records
Number of bytes in a file member 1 869 162 846 624 bytes

32 766 * 2 147 483 646 = 70,364,449,144,836 which is a lot bigger than these limits therefore we estimate and get 57 045 804 as the likely maximum for SIZE. I don't have access to any system with that much free space so you'll have to experiment--or simply pick a smaller SIZE value and repeat more often.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.