Re: Strange issue with a Data Queue

Its a straight api execution.

0059.00 D SndDQname S 10 Inz('RTADJQ')
0060.00 D SndDQlib S 10 Inz('*LIBL')
0061.00 D SndDQsize S 5 0 Inz(13)
0062.00 D SndDQdata S 16
0063.00 DQSNDDTAQ PR extpgm('QSNDDTAQ')
0064.00 D Qname 10 const
0065.00 D Qlib 10 const
0066.00 D Qdtaln 5 0 const
0067.00 D Qdta 65535 const options(*varsize)
0068.00 D Qkeyln 3 0 const options(*nopass)
0069.00 D Qkeyval 65535 const options(*nopass)
0070.00 D Qasync 10 const options(*nopass)
0071.00 D QJentry 10 const options(*nopass)

0032.00 D DtaqDS DS
0033.00 D @src 2
0034.00 D @Tran# 10
0035.00 D @OA 1

...

0239.00 SndDQdata = DtaqDS;
0244.00 QSNDDTAQ (SndDQname:sndDQlib:SndDQsize:SndDQdata);

Post the code....

I'd be willing to bet there's an error, it's just being ignored..

Charles

On Thu, Jan 22, 2015 at 5:22 AM, RPG List <rpglist@xxxxxxxxxxx> wrote:

Nope, never threw a single error, the call to the API acts as though the
data was written.

We have it set to 2GB up front.

Possible corruption, max data queue object size perhaps ?

Default size looks like 16mb. Looks like you can set size to 2gb.

Was your app throwing errors on the write ?

Regards,

Richard Schoen | Director of Document Management Technologies,

HelpSystems

T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com


------------------------------

message: 6
date: Thu, 22 Jan 2015 08:59:53 -0000
from: "RPG List" <rpglist@xxxxxxxxxxx>
subject: Strange issue with a Data Queue

I'm sure I'm not the first to have experienced this, but I wanted to

at

least ask the question.

I am using the QSNDDTAQ API to write data to a data queue. Its been
working for months, yesterday it just stopped writing. The program
completes successfully, no errors are generated but no data gets

written

to the queue.

It is almost as if the data just disappears.

I was able to fix it by deleting and recreating the queue, but that
doesn't explain the issue.

Suggestions? Thoughts?

Dutch


_______________


Confidentiality Notice: This e-mail, including attachments, may

include

confidential and/or proprietary information, and may be used only by

the

person or entity to which it is addressed. If the reader of this

e-mail
is

not the intended recipient or his or her authorized agent, the reader

is

hereby notified that any dissemination, distribution or copying of

this

e-mail is prohibited. If you have received this e-mail in error,

please

notify the sender by replying to this message and delete this e-mail
immediately.

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