RE: Problem with QSNDDTAQ

Sorry, I left out the defs for the parameters...

d QueueName s 10a const
d QueueLibrary s 10a const
d DataQueueData s 4296a const
Data block for DTAQ
d DataQueueLen s 5p 0 const
Data block for DTAQ

If the first several characters of DataQueueData were blank, but data is
present the rest of the way, could this cause the QSNDDTAQ to misbehave?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vinay Gavankar
Sent: Tuesday, September 08, 2009 4:17 PM
To: Midrange Systems Technical Discussion
Subject: Re: Problem with QSNDDTAQ

What is the length of the DataQueueData variable?

To Quote from IBM

*Length of data* INPUT; PACKED(5,0)

The number of characters to be sent to the data queue.

*Note:* An error occurs if the value specified is greater than the length
specified by the maximum lenght (MAXLEN) parameter on the Create Data Queue
(CRTDTAQ) command, unless optional parameter group 3 is specified. With
optional parameter group 3, the length of the data provided in the journal
entry should be specified, and it could be longer than the maximum entry
length. This will be handled appropriately by the API.
*Data* INPUT; CHAR(*)

The data to be sent to the data queue.

*Note:* If the length of this field is larger than the length of data
parameter, only the number of characters (beginning from the left) as
defined by the length of data parameter are sent to the data queue. If the
length of this variable is smaller than the length of data parameter,
unexpected results can occur.
So if your length of Data sent is less, you may have a problem.


On 9/8/09, Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:

I'm using JCRDQE to review the contents of the data queue, and I've
also used my own programs using QRCVDTAQ to retrieve entries.

The Data Queue has an entry length of 4296, sized at *MAX2GB, and is a
local data queue. It is non-keyed. Here's the command to create
it...

crtdtaq dtaq(LibraryName/QueueName) type(*std) size(*max2gb)
maxlen(4296)
force(*yes) seq(*fifo) autorcl(*yes) text('some text info')

Here's the code pertinent to the call to QRCVDTAQ...


C eval DataQueueLen = 4296
C* DataQueueData is assembled from several records of file data
C* when this program is placed in debug, just before execution of the
following line, all parameter values are correct
C call(e) 'QSNDDTAQ'
C parm QueueName
C parm QueueLibrary
C parm DataQueueLen
C parm DataQueueData
C* the following line is inserted simply to assist debugging. No
error is produced.
C if %error
C eval JournalCode = JournalCode
C endif



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Tuesday, September 08, 2009 3:09 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Problem with QSNDDTAQ

I'm having a problem with QSNDDTAQ and could use some advice.

It is a program. So is QUSRJOBI, for example. The fact that it is a
program does not make it not an API. It is an Application Program
Interface into some system function - ergo API.

data to insert). I can see the data to insert in the parameter
being passed. It's there. The entry does get inserted but the data
is blank.

My first question is: How do you know the message is blank, and
there's not some problem with the receiver? Have you dumped the queue?

Or ???

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Speak when you are angry and you will make the best speech you will
ever regret."
-- Ambrose Bierce


--
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.


--
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.

--
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.