Re: tmpnam() not unique -- RPG400-L

Subject: Re: tmpnam() not unique
From: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
Date: Tue, 14 Oct 2014 08:45:08 -0500
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

That would be very disappointing... IBM says that tmpnam() will generate a unique filename.

Does it say somewhere that this is based on the timestamp?? (which certainly isn't unique!)

On 10/14/2014 8:19 AM, McGovern, Sean wrote:

I've believe I have encountered an issue with my use of tmpnam().

If 2 jobs use tmpnam() at the same timestamp moment, I *think* the same filename is returned (though I don't know how to test this scenario).

I haven't coded to handle this possibility, and end up with two jobs trying to create the same temporary IFS file.

I was thinking that a solution could be just prefix/suffix the job number to the filename returned by tmpnam().

Does that seem like a feasible solution ?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: tmpnam() not unique , McGovern, Sean

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.