
FUP Commands
File Utility Program (FUP) Reference Manual—523323-014
2-128
LISTOPENS Guidelines
against all protection views on the SQL base table of interest. To list the protection
views for a base table, use the command
SQLCI DISPLAY USE OF tablename
.
The only device processes that currently give LISTOPENS information are disks,
terminals, and X.25 lines.
Fields that do not contain valid data for particular files in
fileset-list
are blank
or zero filled.
The information displayed in the USERID, MODE, and SD field for X.25 lines is:
The X.25 process does not use (or keep) the accessor ID, causing it to always
return 000,000 for the accessor ID. This information appears in the USERID
field for any process that has an X.25 data communication line open.
X.25 lines are always opened for read and write access. The display always
shows R/W in the MODE field for any process that has an X.25 data
communication line open.
An X.25 process does not use sync depth, causing the display to always show
0 in the SD field for any process with an X.25 data communication line open.
If the device (controlling process) does not support a LISTOPENS request, FUP
LISTOPENS displays:
WARNING - dev name: WILL NOT RETURN OPEN INFORMATION: ERR 2
LISTOPENS does not show a file as open if it was opened and closed during a
transaction (although the transaction itself is still open). This situation occurs
because the file has no openers. The INFO command does show as open files that
have been opened and closed during a transaction (if the transaction itself is still
open). This situation occurs because the file still has outstanding locks against it.
LISTOPENS displays the message
Nonexistent process
if the process that is
opening a file stops during the execution of the LISTOPENS command.
The user running FUP must have remote access to any system, which is implicitly
referenced by the ANSI name used in the FUP command. For example, if the ANSI
name is 'CATALOG*', the user must have access to any node on which any visible
catalogs reside, and so on. If the ANSI name is 'TABLE C.S.T', the user must have
access to any node on which partitions of table C.S.T reside, and so on. Users who
want to limit the scope of the command to all SQL/MX objects on the local machine
can use a Guardian wildcard of the form: $*.ZSD*.*.
The above explanation can be used to explain both an error 8551 from ANSI
names or error 48 from the file system, depending on the command that was used.
LISTOPENS supports SQL/MX objects, CATALOG, SCHEMA, TABLE, INDEX, and
PARTITIONS.