Sounds like a bug to me. It should be easy enough to fix in a PTF or at
least V4R2. Has anyone reported this to IBM support?

-Walden

> -----Original Message-----
> From: mcsnet!midrange.com!midrange-l-owner@Mcs.Net
> [mailto:mcsnet!midrange.com!midrange-l-owner@Mcs.Net]On Behalf Of
> bvining@vnet.IBM.COM
> Sent: Tuesday, January 20, 1998 9:17 AM
> To: MIDRANGE-L@midrange.com
> Subject: Data queue's
>
>
> The Retrieve Data Queue Descripton (QMHQRDQD) API found in the System
> API Reference (chapter Data Queue APIs) returns all of the requested
> information EXCEPT whether the *DTAQ is *DDM and the related attributes
> for *DDM (mode, netid, location, etc.).  The API will return the error
> CPF9511 if an attempt to access a *DDM *DTAQ is made.  Though rather
> ugly, the only way to determine the *DDM attributes that comes quickly
> to mind is to use DMPOBJ against the *DTAQ and then look at the
> primary associated space (if CPF9511 is received from the API).
> Hopefully some one else can think of something a bit more graceful than
> DMPOBJ.
>
> Bruce Vining
>
> >
> >Is there a way to see all the parameters of a dtaq (e.g. TYPE *STD or
> >*DDM, MAXLEN, FORCE *YES or *NO, SEQ *FIFO *LIFO or *KEYED).
> >
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].