Open System Services Shell and Utilities Reference Manual (G06.29+, H06.08+, J06.03+)

User Commands (m - o) mv(1)
6. To use mv with pattern-matching characters, enter:
mv dir1/* .
This moves all files in the directory dir1 into the current directory (.), giving them the
same names they had in dir1. This also empties dir1. Note that you must type a space
between the * (asterisk) and the . (dot).
7. To move all OSS files on the local node to a remote node, enter:
mv -W NOG -W NOE / /E/node
where node is the Expand node name of the target remote node.
NOTES
If the source is on a different file system than the destination, mv must copy the source to the
destination’s file system and then delete the source. In this case, if the current user is not
privileged enough to change ownership to the actual user, then the user ID becomes that of the
current user, but the mode and times are not changed. The effect is equivalent to the following
command syntax:
rm -f destination && cp -pR source destination && rm -rf source
Because /G and /E both appear in your local root directory, you should be very careful when
using OSS shell commands on or from the root directory. OSS shell commands that perform
recursive actions make no distinction between Guardian and OSS files or between local and
remote files. You can use the -W NOG and -W NOE flags or the UTILSGE environment vari-
able to exclude objects in the Guardian file system or objects accessible through the Expand pro-
duct.
For H06.23 and later H-series RVUs, J06.12 and later J-series RVUs, the H06.22 RVU with the
T9194H01ˆAFA SPR installed, or the J06.11 RVU with the T9194J01ˆAEZ SPR installed, a
remote user can move an SQL object that is in the OSS file system even if the file is present in
the destination directory.
For H06.22 (without the T9194H01ˆAFA SPR installed) and earlier H-series RVUs, and J06.11
(without the T9194J01ˆAEZ SPR installed) and earlier J-series RVUs, if a remote user attempts
to move an SQL object that is in the OSS file system and the file is present in the destination
directory, the mv command fails with error "Guardian or User Defined Error 197". To move this
type of file on these RVUs, a local user must execute the mv command.
File-Label and SQL Catalog Table Inconsistencies
When you issue the mv command to move an OSS SQL program file and an SQL program with
the same name already exists in the destination directory, if the command fails due to certain
failure scenarios such as a CPU failure, disk failure, or application outage, this failure can cause
an inconsistency between the destination SQL program file label already existing and the
corresponding SQL catalog. The program can lose its SQL properties, but have SQL catalog
entries present. In this case, the following conditions occur:
• The program does not run after losing its SQL properties.
• The SQL catalog tables have stray entries for this program file. The program exists, but
its just like a normal Enscribe file.
• If any DDL command is issued on a table on which the program depends, the program
obtains partial SQL properties and remains invalid.
527188-021 Hewlett-Packard Company 6−29