The problem with horsepower 😊
Timestamp + GUID is a nice combo although results in longer file names.
Same issues happen on other platforms. In .Net you can go out to seven millisecond levels: yyyyMMddhhmmssfffffff and we still ran into issues when fast Windows VMs came along.
Timestamp + GUID. Problem solved.
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 6
date: Tue, 24 Oct 2017 20:29:47 +0000
from: Roger Harman <roger.harman@xxxxxxxxxxx>
subject: RE: Freaky occurrence involving a print file overridden to a
PDF
I recently had a project to create files to send to an Oracle system. They said "just use a timestamp for uniqueness". Well.... as Brad mentioned, not good enough. I, too, added a sequence # to the timestamp name generation.
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bradley Stone
Sent: Tuesday, October 24, 2017 10:51 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Freaky occurrence involving a print file overridden to a PDF
I would contact IBM. or...
If it is two programs trying to create the same file, then maybe the
naming scheme you're using needs to be refreshed.
I know having written SPLTOOL over 20 years ago and creating PDFs from
spooled files I've seen similar things. When I create temp files I tried
once to use a timestamp.. not good enough.. that can easily cause a clash
too. So I always use incrementing data areas for naming unique files.
Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #13 <
https://www.bvstools.com/mailtool.html>: The ability
to use an IFS stream file as the body of the email (either text or html).
midrange.com
