File Utility Programming (FUP) Reference Manual

FUP Commands
File Utility Program (FUP) Reference Manual—523323-015
2-133
LISTOPENS Guidelines
215,01,0079 R/W-S 001,249 00 \FOXII.$LAM1.#ZWN
$SYSTEM.SYSTEM.TESTPROC
$GUEST.MYSVOL.RFILE
PID MODE USERID SD MYTERM PROGRAM FILE
NAME
215,01,0079 R/W-S 001,249 00 \FOXII.$LAM1.#ZWN
$SYSTEM.SYSTEM.TESTPROC
$GUEST.MYSVOL.SAMPLE
PID MODE USERID SD MYTERM PROGRAM FILE
NAME
215,01,0039 R/W-E 001,249 01 \FOXII.$TC1.#C13
$GUEST.FUPD00.FUP
LISTOPENS Guidelines

To get information on temporary files, you must explicitly specify temporary file
names using the # character.

When you apply LISTOPENS to an SQL/MP protection view, it displays the
processes that opened the view and the processes that opened the table view
depends on.

You cannot apply LISTOPENS to an SQL/MP shorthand view. If you include a
shorthand view in fileset-list, LISTOPENS skips that view and issues a
warning message.

An open SQL base table might not be reported by LISTOPENS as open even if a
FUP INFO command reports it is open. This situation occurs if the SQL base table
is opened indirectly by a protection view. You can issue a FUP LISTOPENS
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.