BRMS – displaying how much data is saved to a cart

Backup and Recovery
Guys, is there a simply and accurate way to display how much data is saved to a cartridge using BRMS, or native OS/400? We have 800GB capacity carts and need to work out how much of the cart is being used per backup. Things I have tried:


We are running OS V5R3 (Cum5298) using a 3584 MLD with LTO3 drives. All suggestions welcome. Thanks.

Answer Wiki

Thanks. We'll let you know when a new response is added.


I suspect you will have to consider such criteria as:

  1. The amount of data per object
  2. The number of objects
  3. The number of libraries
  4. Etc.

Had a similar question some time ago but never solve it accurately as the cartridge could easily hold all the data we wanted to save and an unique cartridge would be used for each save.

I also initialize the cartride each time before a save.

Best of luck



About the only way to find out is to regularly output lists of everything saved, then save more to the cartridge until it fills up. When you know how many objects were saved at the beginning and what their sizes were, you can start matching it up with how much was left over.

And then you should learn the methods used to store data on the medium and work out the relationships.

It used to be that tapefile block sizes would be a major determining factor. Along with that, the sizes of the objects and the number of objects could be used to make some general calculations. The block size was important because a large part of the tape was actually used to hold nothing — blank areas of tape were between each block and between each object. These were inter-record (or inter-block) gaps and could be significant in size compared to stretches of tape that actually had data recorded. The gaps were part of the logical mechanisms used by the tape drive to know when data was being read, where it started, where it ended.

If thousands of little objects were recorded, there’d be thousands of gaps. If a few large objects were recorded with large block sizes, there’d be very few gaps — most of the tape would contain data rather than being blank. You could save a lot more bytes if objects were large and they were written in large blocks.

Further, inconsistencies in tape surfaces and simple wear would cause tape errors. Sections of tape would regularly be marked as unusable and skipped. IIRC, many skipped areas were fixed in length with different drives skipping different lengths. Each bad area would reduce remaining capacity.

More recently, helical scans, digital recording, very fine mechanical control of tape movement, etc., have been among advancements that have raised densities and reduced wasted tape area.

Capacities have gone up so far, so fast, that I haven’t run across anyone who really seems to know how to estimate “remaining capacity”.

So, only idea I have is to save a bunch of stuff, keep track of numbers and sizes, and then see how much more you can save. The pattern of object sizes and blocks at the beginning should eventually be a useful predictor of what stuff might be added at the end.


Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • pdraebel
    I think it is really guesswork when trying to determine the capacity left on a tape cartridge. Not all cartridges are created equal. The 800Gb capacity is not the exact capacity of the tape. I have been in situations where a save one day needed an extra cartridge and the next day it would only need one cartridge for saving roughly the same data.
    7,545 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: