×
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 Wed, Jun 17, 2015 at 3:56 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
I was suggesting that perhaps going all the way to base 36 was overkill John and that base 16 might provide a satisfactory, and far easier to implement, alternative.
Well, he did *specifically* mention that he wanted to preserve EBCDIC
order, and standard hex (expressed as digits '0' through 'F') doesn't
do that.
It was pretty clear from his description of the problem that the field
is currently being monotonically incremented, and he wants to be able
to continue to do so (that is, not go backwards).
As to "far easier"... well, some folks already mentioned some ideas
earlier in the thread to do exactly what Gad was asking, and they
didn't strike me as too difficult. No more difficult than using system
APIs (actually quite a bit easier in my opinion). Regardless, whatever
he comes up with will presumably be wrapped up in a service program or
similarly easy-to-use package, so any initial "implementation cost"
gets amortized away anyway. (At least, this seems to be one of the
standard arguments for using RPG as an implementation language over
more expressive languages.)
John Y.
midrange.com
