Guardian Procedure Calls Reference Manual

Considerations
• Purge access for RENAME
The caller must have purge access to the file for the RENAME to be successful. Otherwise, the
RENAME is rejected with file-system error 48 (security violation).
• Volume specification for new-name
The volume specified in new-name must be the same as the volume specified when opening
the file. Neither the volume name nor the system name can be changed by RENAME.
• sysnum specification for new-name
If sysnum is specified as part of new-name, it must be the same as the system number used
when the file was initially opened.
• Partitioned files
When the primary partition of a partitioned file is renamed, the file system automatically
renames all other partitions located anywhere in the network.
• Renaming a file audited by the Transaction Management Facility (TMF)
The file to be renamed cannot be a file audited by TMF. An attempt to rename such a file fails
with file-system error 80 (invalid operation attempted on audited file or nonaudited disk
volume).
• Structured files with alternate keys
If the primary-key file is renamed, it is linked with the alternate-key file. If you rename the
alternate-key file and then try to access the primary-key file, file-system error 4 occurs, because
the primary-key file is still linked with the old name for the alternate-key file. You can use the
FUP ALTER command to correct this problem.
• Support for format 2 key-sequenced files with increased limits
RENAME can be used to change the names of open format 2 legacy key-sequenced files with
increased limits and enhanced key-sequenced files with increased limits in H06.28/J06.17
RVUs with specific SPRs and later RVUs; the behavior of the API is unchanged. (For a list of
the required H06.28/J06.17 SPRs, see SPR Requirements for Increased Enscribe Limits for
the H06.28/J06.17 Release (page 31).)
Safeguard Considerations
For information on files protected by Safeguard, see the Safeguard Reference Manual.
OSS Considerations
An OSS file cannot be renamed. Error 564 (operation not supported on this file type) occurs when
an attempt is made to rename an OSS file.
RENAME Procedure (Superseded by FILE_RENAME_ Procedure) 1241