|
Carsten also has some examples.
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapimymymy.wordpress.com%2F%3Fs%3Dcrtusrq&data=04%7C01%7C%7C26ce7a99c89148bf539108d9d7bd41a0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637778030109777180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Fga3tFkLxHLQlVbDfK97O94PwaFMaxnjps%2BoMB%2BOcVI%3D&reserved=0
Bryan
Rich Loeber wrote on 1/14/2022 12:26 PM:
Alan,
That would be very helpful. I would love to see that code.
Rich
________________________________
On 1/14/2022 1:21 PM, Alan Campin wrote:
I have a service program that wraps functions for the user queue object
written in RPG.
Actually writing to User Queues is a lot simpler in RPG than in C.
They are
tough in C although there are a lot of examples out there using them
in C.
Let me know if you are interested.
On Fri, Jan 14, 2022 at 10:06 AM Rich Loeber
<rich@xxxxxxxxx><mailto:rich@xxxxxxxxx> wrote:
According to IBM documentation, a USRQ will have better performance
than a
DTAQ. I have an application that is experiencing performance issues on
some customer systems and we now think that this is tied to a lot of
data
going through a data queue. Unfortunately, IBM documentation on how to
work with user queues is nearly nonexistent. The only think I can
find is
an example written in C which is of little use to us. I see where
you have
to use MI to read and write to a user queue and that doesn't scare us
all
that much, but it would be good to know that diving into this project
was
going to produce tangible results.
Does anyone have any experience with user queues and have you done it
in a
language other than C? We need to be able to write to one and, in a
separate process, read from it all in FIFO sequence.
Rich Loeber
Kisco Systems
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kisco.com%2F&data=04%7C01%7C%7C26ce7a99c89148bf539108d9d7bd41a0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637778030109777180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=wjEX%2BxSE9hXyj3y%2BR9%2F4Ig5KLtsrpm0WPDEeKSpqhmc%3D&reserved=0
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
To post a message email:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=04%7C01%7C%7C26ce7a99c89148bf539108d9d7bd41a0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637778030109777180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=YOMc9AMJw5RQAFQ5noW6Ij0F%2BonCkcHyznUcDyiC4Is%3D&reserved=0
or email:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchive.midrange.com%2Fmidrange-l&data=04%7C01%7C%7C26ce7a99c89148bf539108d9d7bd41a0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637778030109777180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=wRarPbqjfW1fckKHFbaQE19zxKCyHqUZkYUUxA%2BlRYk%3D&reserved=0.
Please contact
support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for
any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Famazon.midrange.com%2F&data=04%7C01%7C%7C26ce7a99c89148bf539108d9d7bd41a0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637778030109777180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=1P5M0sUnJGy2zfz5AVgYQzYSZp%2F9G8O%2BDpcNvyf7QQQ%3D&reserved=0
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.