×
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.
" Now I'm curious why you believe that thread(*serialize) might be undesirable in your current project?"
Because it's multi-threaded, and a single-threaded bottleneck would be undesirable.
Thanks
-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Friday, March 06, 2020 11:46 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Java->RPG, *SERIALIZE required?
I might quibble with the assertion that you "must" thread(*serialize) in that a lot of Java processes are single threaded; No need to serialize in that case. Also it is conceivable that one could write RPG code that didn't require *serialized access. But on the whole, thread(*serialize) is good advice, in that it ensures safe access to the RPG code from multi-threaded callers.
Now I'm curious why you believe that thread(*serialize) might be undesirable in your current project?
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.
midrange.com
