×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
1. what type of data queue? (FIFO, LIFO, or Keyed)
2. what is the max length on the data queue. (when it was created)
3. local or remote data queue.
If you can post the CRTDTAQ command that you used to create the data
queue and the snip it of code to send data to it. Also include your
field definitions.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Thomas Garvey
Sent: Tuesday, September 08, 2009 12:29 PM
To: 'Midrange Systems Technical Discussion'
Subject: Problem with QSNDDTAQ
I'm having a problem with QSNDDTAQ and could use some advice.
I'm calling the QSNDDTAQ API (actually I think it's really a program
because
it departs from the parameter passing techniques of almost all other
API's
I've used) to insert entries into a data queue. The problem is: it
always
inserts an entry when it's supposed to, but most often it's just a blank
entry. I've debugged this thing and can prove that the correct
parameters
are being sent to the QSNDDTAQ (data queue name, library, data length,
and
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.
I've called the QSNDDTAQ with call(e) and checked the program status
data
structure for some kind of error result (since the 'API' doesn't return
anything) but it's not generating any errors.
Any ideas?
Thomas Garvey
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.