Re: CPF3708 savf file too small

Virtual Tape is your friend..

Charles

On Mon, May 18, 2026 at 3:10 PM Mark Villa <iseries.4.me@xxxxxxxxx> wrote:

Thanks everyone, this was a SAVLIB command with no compression... default
(*DEV)
It's a shame that a calculation isn't done before 2 hours of "Saving"
happens
and B) perhaps a prompt to "continue with next save file name"


On Mon, May 18, 2026 at 12:39 PM Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:

I did just do a DSPMSGD CPF3708 and also see that 2TB limitation.
My comments about compression and the 2TB save file vs 1TB stream file
still stand though.

On Mon, May 18, 2026 at 12:36 PM Rob Berendt <

robertowenberendt@xxxxxxxxx>

wrote:

The online help lists that 2TB size for a save file only for SNDNETF.
It's been a few decades since I've used SNDNETF.
However, the save/restore limits do confirm this 2TB limitation.

https://www.ibm.com/docs/en/i/7.6.0?topic=capacities-save-restore-limits

If you have a business case where you really desire to use save files

for

such a large amount then submit an "Idea". As a workaround you could

try

saving to image catalogs. Granted, for *ZLIB you'd have to use an

optical

image catalog, at least according to the help.
Then again, the maximum size of a stream file is 1TB as per

https://www.ibm.com/docs/en/i/7.6.0?topic=capacities-file-system-limits

so maybe 2TB is a little too progressive for the rest of the world.
Keep in mind that these 2TB and 1TB sizes are AFTER compression.

On Mon, May 18, 2026 at 5:40 AM Mark Villa <iseries.4.me@xxxxxxxxx>

wrote:

Hi all,
Is this because of actual SAVF limits or total system storage ?
CPF3708 - The save file is not large enough to save all of the

objects....

My assumption is that it can be both....we were passing through 92%

when

this happened. It was quite a surprise...and a plan changer.

2 Terabytes ? wow ! ....that's small these days :)

--
Thank You,
Mark Villa
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
Thank You,
Mark Villa
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.