RE: Using DVD-RAM drive

[vhamberg@xxxxxxxxxxx]

Well, to mess things up a bit, there is an API at V5R2, the QSRSAVO API, that 
can use all the compression options. It is equivalent to SAVOBJ, without the 
300-object specification limit - you have to use a user space. So it's not the 
prettiest, but I think there are generic ways to use it. There is no SAVLIB 
equivalent - but SAVLIB basically just saves the library object itself along 
with all its objects.

Vern
-------------- Original message -------------- 

> Just an update... 
> 
> I opened a PMR with IBM to get this question answered. 
> 
> Apparently, though no mention of it is in the v5r2 docs or help text, the 
> v5r2 
> SAVLIB command works like the v5r3 version. Specifically, when CPRDTA(*YES) 
> is 
> specified, "Low software compression is used for all devices except optical 
> DVD, 
> which uses medium software compression." 
> 
> Too bad v5r2 doesn't support the CPRDTA(*LOW | *MEDIUM | *HIGH) options that 
> v5r3 does. 
> 
> So I don't know that this DVD-RAM is going to be useful the way we intended, 
> till we get to v5r3 and can take advantage of either the new compression 
> options 
> and/or the writable virtual optical support. 
> 
> 
> Charles Wilt 
> iSeries Systems Administrator / Developer 
> Mitsubishi Electric Automotive America 
> ph: 513-573-4343 
> fax: 513-398-1121 
> 
> 
> > -----Original Message----- 
> > From: midrange-l-bounces@xxxxxxxxxxxx 
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Wilt, Charles 
> > Sent: Wednesday, February 02, 2005 9:16 AM 
> > To: Midrange Systems Technical Discussion 
> > Subject: RE: Using DVD-RAM drive 
> > 
> > 
> > Vern, 
> > 
> > I've looked at the help. 
> > 
> > Doesn't explain why DTACPR(*YES) gives two different ratios 
> > depending on rather you are going to a save file or the 
> > DVD-RAM drive. As you and I have both mentioned the DVD-RAM 
> > drive doesn't have any built-in hardware compression/compaction. 
> > 
> > Thus, in both cases, it is only OS/400 doing the compression. 
> > 
> > Why then does the 3.27GB library end up at 795 MB when SAVLIB 
> > goes directly to the DVD-RAM and 2.14GB when SAVLIB goes to 
> > the save file?? 
> > 
> > Charles Wilt 
> > iSeries Systems Administrator / Developer 
> > Mitsubishi Electric Automotive America 
> > ph: 513-573-4343 
> > fax: 513-398-1121 
> > 
> > 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>