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



On 2023-11-22 4:53 p.m., Rick Rauterkus via RPG400-L wrote:
I have been playing around with Apache and ILEastic to set up a web service
that will call a process in our existing application. I have both of them
working, but have a question on threads.

ILEastic says the RPG programs have to be compiled with
Thread(*Concurrent). I did that with the front end program I created for
the ILEastic server, but do I need to do that with all the programs in the
existing application that could be called by this process also? None of
the existing programs will use the ILEastic procedures at all. I see
ILEastic includes il_exitThreadSerialize and il_enterThreadSerialize
procedures, but I cannot find anything on how or if they should be used.


If you are running in a multi-thread environment, everything you call should be thread-safe. If you are calling something that can't be made thread-safe, you have to make sure they are only called by one thread at a time.

*CONCURRENT means that multiple threads can be running in your module at the same time, which means that multiple threads could call any other programs in your application at the same time.

So any other RPG programs and service programs called from your application, and anything THEY call, should also have the THREAD keyword, either *CONCURRENT or *SERIALIZE.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.