You need to be using the Integrated File System version of rename().  In
the V5R2 Information Center take the path Programming/APIs/APIs by
category/Unix-Type/Integrated File System APIs/rename()

What is documented there is that if you define _POSIX_SOURCE you will get a
rename() which unlinks the "new" if it exists.

                      Terrence Enger                                            
                      <tenger@iSeries-g        To:       c400-l@xxxxxxxxxxxx    
            >                 cc:                              
                      Sent by:                 Subject:  [C400-L] definition of 
                      09/22/2003 10:11                                          
                      Please respond to                                         
                      C programming                                             
                      iSeries / AS400                                           

Greetings, all.

A program failure has made me look at the definition of the
rename() function.  I find that the IBM run-time library
reference (iSeries ILE C/C++ for iSeries Run-Time Library
Functions, Version 5; SC41-5607-01) says explicitly that the
"to" parameter must not name an existing file.  The Posix
on the other hand allows this situation and specifies the
behaviour of the function in this case.

Surely rename() is a commonly used part of Posix.  Do I have
to do something special to get Posix compatibility?

Thank you for your attention.

Available for contract programming.

This is the C programming iSeries / AS400 (C400-L) mailing list
To post a message email: C400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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].