Re: compressed save files

Hi Arnaud,

After trying a few more cases, it appears to be a bit more complicated.  I
found one library which, when saved compressed, had only one QSRDSSPC.1 after
which the object list was uncompressed--only the objects themselves were
compressed.   That was a library originally created on V3R1, whereas the
other library (with 2 QSRDSSPC.1's having the object list compressed after
the second) was created on V3R7.  So maybe it's a CISC/RISC distinction.  In
both cases, I saved the libraries with TGTRLS(*CURRENT) on a V5R1 machine.

So I think the question is: How do you tell whether the records after the
QSDSSPC.1 descriptor record are compressed?

The best I've been able to come up with is this:  If the 4 bytes at offset
x10 in the next record after the QSRDSSPC.1 record are hex zeros, the
following records containing the object list are uncompressed.  If the 4
bytes are not zeros, the records are compressed, and you'll have to
uncompress them to get the list.

--Dave


On Saturday 02 February 2002 05:45 am, arnaud wrote:
> hello Dave,
>
> _ I could verify that effectively, records are 528 byte long in compressed
> save files.
>
> _Thanks to your councils, i use the 4 byte long data at offset x48 to go to
> the next descriptor.
>
> _ List of objects is in descriptors called QSRDDSSPC.1.As you said, the
> first one is not compressed, but the others are.I assume i have to
> uncompress the descriptors called QSRDSSPC.1  ?
>
> best regards.
>
> _______________________________________________
> This is the MI Programming on the AS400 / iSeries (MI400) mailing list
> To post a message email: MI400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/mi400
> or email: MI400-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/mi400.