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



I am surprised that the API will allow you to do that but, of course. If
your data is 64K in size, why are you defining the data queue to only by
8192? Anything longer than 8192 is not going to be sent.


On Wed, Jan 19, 2022 at 8:21 AM Singh, Ashwani (Lake Mary) via RPG400-L <
rpg400-l@xxxxxxxxxxxxxxxxxx> wrote:

Hello,



I have a question regarding the data parameter to rule out QRCVDTAQ
involvement.



PGM 1 - Receives data with length 64512 , using a DTAQ with MAXLEN
(10240) , PGM2 which sends the data to this queue can send max 8192 Bytes
only.



D QRCVDTAQ PR EXTPGM('QRCVDTAQ')

D DataQ 10 Const

D Lib 10 Const

D QLength 5P 0 Const

D OtData 64512

D Qwait 5P 0 Const



Is there any possibility that data received in PGM1 get corrupted because
of length of OTDATA > MaxLen ?



Thanks,

Ashwani Singh


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.