Using KSAM/XL and KSAM 64 (32650-90886)

Chapter 9 145
KSAM Intrinsics
FRENAME
file that was created, specify any account that shares the
same volume set as the file being renamed. A permanent
file cannot be renamed across account boundaries. If other
than the current account name is specified for a
permanent file, the CCL (1) error condition is returned
and the file retains its old name.
Operation Notes
The formaldesig parameter uses MPE-escaped semantics. If a file is referenced by
filenum , you can rename it within the hierarchical directory as long as the process
invoking FRENAME has sufficient access and the restrictions are satified. FRENAME intrinsic
fully qualifies the file owner name. Only file owners and users with appropriate privilege
can manipulate a file's lockword.
If renaming a file, a process must have the following:
TD Traverse directory entry to access to all directories specified in
formaldesig .If formaldesig is specified as file.group.account, the
directories are the root directory, the account, and the MPE group.
CD Create directory entry to access to the new parent directory.
DD Delete directory entry to access to the old parent directory.
SF Save files capability.
The following restrictions apply to FRENAME:
• Directories cannot be renamed.
• Lockwords cannot be assigned to hierarchical directories.
• Files cannot be renamed across volume sets.
• Files with KSAM/3000, RIO, and CIR file types may only be assigned names in the
MPE name space.
If a file without an ACD is renamed from an MPE group to a directory (although not within
the same account), an ACD is automatically assigned to the file.
All errors will set the condition codes to CCL.
CM KSAM files cannot be renamed, but KSAM XL/64 files can be.
Condition Codes
CCE (2) Request granted.
CCG (0) Not returned.
CCL (1) Request denied. An error occurred.
Refer to this intrinsic in the MPE/iX Intrinsics Reference Manual for other codes
pertaining to KSAM files.