Re: API QDBRtvFD and DDM files

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

There are PTFs for V5R1 and V5R2 related to this

R510 SI04540   3007
R520 SI04538   BASE

But these fix is related to getting a CPF9163 message - is that 
happening to you?

Also, the documentation says that this API does not work for *SNA 
type DDM files in multiple threaded jobs, I believe.

But I think the real problem is that the bit flag is not for DDM 
files, rather for something called distributed files - yes, that word 
is part of DDM. But the distributed file section includes information 
about node groups, etc. But I could be wrong here - sometimes IBM 
overloads a section for multiple uses.

Have you set the 8th parameter (system) to *RMT or *FILETYPE? But 
this makes me think that the DDM attribute is not returned here - you 
already know, using an object description API.

Maybe use one of the object description APIs to get the extended attribute.

HTH
Vern

At 02:31 AM 8/21/2006, you wrote:





> Hello, maybe (and hopefully) anyone can help me; searching the net didn't
> gave a suitable answer.
>
> It concerns reading file information for DDM files: i can't even decide
> wheater a file is a DDM file or not.
>
> Using DspFD a file has the following attributes:
>    system: *lcl
>    file type: device
>    device type: DDM
> and DDM attributs are shown.
>
> So far, so good. But I'll get these information with API QDBRtvFD.
>
> In format Qdb_Qdbfh, positions 68 to 69 (counting begins at zero) is field
> Qaaf2 (additional attribute flags); bit 4 (counting also begins at zero) of
> the second byte should by ON if it is the a DDM file. But this bit always
> is OFF: b'0001 0000'.
>
> Where is the error?
>
>
> Eduard Spanninger
> STAMAG Stadlauer Malzfabrik GesmbH
>
> --
> 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.