Re: Help with cprdata

1)  no.
cprdata is a MI wrapper function and not an API (like QUSROBJD).
Like other MI functions, it lacks the error friendliness of APIs.  This is
the price of speed.  You just have to figure out the problems yourself.

As Simon indicated, the C function version uses TERSE (Algorithm=1). You'll
have to go back to the built-in version (_CPRDATA) for LZ1 (Algorithm=2).

OK, now I'm interested why you're using DSPLY (let alone compressing data
for it)
Why not use QMHSNDM/QMHSNDPM ?


Keith



----- Original Message ----- 
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
To: "Rpg400" <rpg400-l@xxxxxxxxxxxx>
Sent: Thursday, July 01, 2004 6:05 PM
Subject: Re: Help with cprdata


>
> > The problem is your variable Compressed is too small.
>
> I agree that the field is too small Keith/Simon, but isn't the function
> supposed to handle that?  I thought it was supposed to return the length
> that the compression requires but only actually fill the space provided.
> Not just blow up.  In case anyone wonders why I'm using 52 - it is because
> that is the max for DSPLY sadly.
>
> I based this test on an example that directly used the underlying MI
> built-in and it had a length of 52 for both input and result and that one
> works just fine.  Since it works I have to assume that the compression
> option it is using ( Algorithm = 2) is not the same as the one used for
the
> cprdata function.  Wonder why.  In fact using this option the full 52
> characters are indeed compressed since the reverse decompression works
just
> fine and restores the original string intact.