Re: I got those data queue blues?

--
[ Picked text/plain from multipart/alternative ]
The QMHQRDQD Retrieve Data Queue Description API will give you all the info
you need. It could be what the TAATOOLS uses. Easiest in RPG or C, but also
easy to use in CL.

DCL &RCVVAR *CHAR 108
CALL QMHQRDQD (&RCVVAR x'0000006C' 'RDQD0100' 'queuename_queuelib__')

Then you need to determine where to substring &RCVVAR. Handle BINARY(4) ad
CHAR 4 and use the %BIN function.

Position Type      Field
1        BINARY(4) Bytes returned
5        BINARY(4) Bytes available
9        BINARY(4) Message length
13       BINARY(4) Key length
17       CHAR(1)   Sequence
18       CHAR(1)   Include sender ID
19       CHAR(1)   Force indicator
20       CHAR(50)  Text description
70       CHAR(1)   Type of data queue
71       CHAR(1)   Automatic Reclaim
72       CHAR(1)   Reserved
73       BINARY(4) Number of messages
77       BINARY(4) Number of entries currently allocated
81       CHAR(10)  Data queue name used
91       CHAR(10)  Data queue library used
101      BINARY(4) Maximum number of entries allowed
105      BINARY(4) Initial number of entries

At 09:20 AM 4/29/02 -0400, you wrote:
>The backup is the way to go. For the record, it's a queue. No data gets
>saved with a data queue (or any queue on the 400) only the description. So
>restore the data queue, dump the object (DMPSYSOBJ or DMPOBJ) and document
>the queue, then go.
>
>Another suggestion: create CL programs for creating non-source objects.
>
>===========================================================
>R. Bruce Hoffman, Jr.
>  -- IBM Certified Specialist - iSeries Administrator
>  -- IBM Certified Specialist - RPG IV Developer
>
>"Suppose you were an idiot...
>   And suppose you were a member of Congress...
>   But I repeat myself."
>     - Mark Twain
>
>----- Original Message -----
>From: "Weatherly, Howard" <hweatherly@dlis.dla.mil>
>To: <midrange-l@midrange.com>
>Sent: Monday, April 29, 2002 8:47 AM
>Subject: RE: I got those data queue blues?
>
>
> > This message is in MIME format. Since your mail reader does not understand
> > this format, some or all of this message may not be legible.
> > --
> > [ Picked text/plain from multipart/alternative ]
> > Don't know if it is in fact damaged, but if you have TAATOOLS, use
>DSPDTAQ,
> > give it the queue name and library and it will show you what is in the
> > queue, also tell you the queue length. Dennis suggested you restore from
> > backups, and if the data on the backup is in sync with what should be
>there
> > that is  a good plan, if the data is old, you would be wasting time
>because
> > it is to simple to recreate the queue once you know the size. CRTDTAQ,
>give
> > it the size location and any other info needed and you are off and
>running.
> >
> > -----Original Message-----
> > From: Rick Rayburn [mailto:the400man@hotmail.com]
> > Sent: Monday, April 29, 2002 7:59 AM
> > To: midrange-l@midrange.com
> > Subject: I got those data queue blues?
> >
> >
> > Had a system power failure.
> > Some dtaq's that are used to process orders were completely damaged.
> > How in the world can I find out the parameters used to create that Dtaq?
> >
> > I do not seem to be able to look at any data in there...
> > I cannot seem to find any normal way of displaying its attributes...
> > Why did IBM make this so difficult?
> >
--