Using physical names for logical files, Application compatibility issues, File information command output – HP Integrity NonStop J-Series User Manual
Page 42
Preparing to Use SMF
HP NonStop Storage Management Foundation User's Guide—523562-007
2-8
Using Physical Names for Logical Files
DCOM program on only some disks within a storage pool may find that those disks
appear to be more “empty” than others in the storage pool, even if they have the
same number of files.
File Information Command Output
The output from file information commands for direct volumes includes only information
on direct files on that volume. File information commands do not display physical file
names for logically named files unless they are explicitly requested to do so. Therefore,
any operational procedure that relies on SQLCI, FUP, or TACL FILEINFO commands,
or NEXTFILENAME or FILENAME_FIND* file system procedures, to include all files on
a physical volume must change if logically named files are to be on physical disks in
addition to the direct files. Note that the DSAP program provides storage information
for all files, both logical and direct on a physical disk.
Any application that requests all information on both direct and physical files, and that
attempts to collect information about all disks in the system, may not execute correctly.
Such applications may include logically named files twice; that is, once by logical name
and once by physical name.
Using Physical Names for Logical Files
SMF places restrictions on accessing logically named files by their physical names,
including the following:
Command interpreters and system procedures do not accept physical file names
(ZYS*.* and ZYT*.*) for normal operations. You must use logical names instead.
BACKUP and RESTORE utilities, TMFCOM utility procedures, and file name
display commands require logical names. In general, specifying physical file
names results in a syntax or operational error.
file name display commands return information on physical files only when the
command explicitly requests that information; that is, either by fully qualified name
or by using an explicit shorthand such as ZYS*.* or ZYT*.* (not ZY*.*).
Safeguard security applies only to logical file names. Also, the Safeguard product
makes no ruling on access of ZYS*.* and ZYT*.* file names.
Application Compatibility Issues
This subsection outlines application compatibility issues for systems running SMF. The
following focuses on single system migration to SMF and on issues pertaining to
various other related subsystems.
For a discussion of issues regarding remote access (in particular, RDF compatibility
issues), see