Re: HTTP API or Web Service concurrency issue

While RPG only gives you 3 digits precision on timestamps...

The OP mentioned he was using SQL to get 6, which it's always supported.

Actually, with SQL you can go all the way to 12 now...and RPG will work
with them. It just can't generated them.

Charles


On Sat, Jun 1, 2019 at 9:27 AM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Sat, Jun 1, 2019 at 10:16 AM B Stone <bvstone@xxxxxxxxx> wrote:

Timestamps are never a good unique naming method. I found this out many
years ago. Even with milliseconds.

Well, milliseconds is not a lot of precision - just three decimal
places. OP mentioned that he tried six places.

I agree with the sentiment that you cannot rely solely on timestamp to
ensure uniqueness, period. But I think the problem is possibly even
worse than meets the eye on IBM i systems, because even if you try to
get six places, the system (or perhaps the language) may only give you
three. I know for sure that I tried testing timestamp resolution in
RPG years ago, and only got down to milliseconds (any further digits
were all zero). I don't know if it's still the case on more recent
versions.

John Y.
--
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@xxxxxxxxxxxx for any subscription related
questions.

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